As a long time basic phone owner I am finally decided to make the switch to android. I have done my research and have come to the conclusion that i would like to purchase the Samsung galaxy S III. However, money is always an issue and I am trying to spend as little as possible but get the most of out my phone.
With Verizon, my current service, the additional 720$ for the 2 year data contract is scary, but the phone, only 200$ is nice. My major question about Verizon is, is it possible to root the Verizon SGSIII. I have read multiple posts from outraged customers who bricked their phones due to the locked bootloader on the Verizon SGSIII. Also, from what i have read from this thread: http://forum.xda-developers.com/showthread.php?t=1756885 it is possible to root the verizon version of this phone although it is more complicated.
My second option is to purchase the Samsung Galaxy Nexus and root this phone through verizon. I would love to run Android 4.1 Jelly Bean on my device which is why i would like to root the device and flash something that would give me this enhancement. However, if i purchase the Galaxy Nexus, i am locked into a 2 year contract with a phone that came out 6 months ago and could soon be outdated by its "older brother" said to be released this december.
Which is my best option and if someone could please clear up the Root problems with the Verizon SGSIII it would be extremely helpful. Thanks for any response!
Best Regards
JSMessick
What are you guys talking about...10 seconds in the Verizon forum would turn up a root tutorial thread. So yes, root is available and there are workarounds that permit custom kernels.
Edit: there's a sticky thread in this very forum of how to obtain root on the Verizon gs3. http://forum.xda-developers.com/showthread.php?t=1762709
Sent from my SCH-I535 using xda premium
From what I understand Verizon Galaxy S3 owners will be able to root but not be able to flash kernels or use aosp roms like CM9/10 since you guys can't flash a kernel.
Unless you buy the bootloader unlocked Verizon Galaxy S3 from Samsung directly, you won't be able to flash kernels.
Again that is inaccurate. Using kexec we can boot custom kernels. We have an early version of cm9 running too. The real hold up is the ril which prevents the cm9 build from having mobile data
Sent from my SCH-I535 using xda premium
To my understanding, they released a developer version that's boot loader unlocked.
Sent from my SGH-T989
Avelnan said:
To my understanding, they released a developer version that's boot loader unlocked.
Sent from my SGH-T989
Click to expand...
Click to collapse
They are, with the release date undisclosed, however it is 600$ which is a little outrageous.
bobloblaw1 said:
Again that is inaccurate. Using kexec we can boot custom kernels. We have an early version of cm9 running too. The real hold up is the ril which prevents the cm9 build from having mobile data
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
So if i purchase the verizon version of the phone and i root it and flash CM9/10 using kexec will the phone still work? what do you mean by the RIL preventing cm9 from having mobile data? just want to clarify thanks for the help.
JSMessick said:
So if i purchase the verizon version of the phone and i root it and flash CM9/10 using kexec will the phone still work? what do you mean by the RIL preventing cm9 from having mobile data? just want to clarify thanks for the help.
Click to expand...
Click to collapse
To clarify some things, since half of the users on these boards are misinformed:
The Verizon (and pretty much every) Galaxy S3 has had root since virtually their release date.
The Verizon version does have a locked bootloader (see #3), and there is going to be a "Developer Edition" released directly from Samsung with pretty much no warranty, and it will be completely unsubsidized.
The bootloader lock has not stopped us from flashing custom ROMs or custom kernels. See below.
Here's some source links for you, in rough chronological order:
The "Root66" method for easily obtaining root
Original proof-of-concept showing custom kernels can be booted
Standard install of CyanogenMod 9 via kexec demonstrated
Functioning 3G/4G data on CyanogenMod 9 demonstrated
Unofficial guide to installing CyanogenMod 9
CVPCS states locked bootloader is a non-issue
Ongoing research & development on the locked bootloader
I could go on and on, but as you can see, development of custom ROMs (both TouchWiz and AOSP based) has not been hindered by the locked bootloader.
The community has pulled together on this, and developers from non-Verizon carriers have been tons of help in all the progress that has been made so far.
Many people, including myself, do not support the idea of the Developer Edition SGS3, and I personally doubt it will have even a tiny fraction of the community the consumer version has.
wifi hot spot on verizon galaxy iii
My question is. Even though the bootloader is locked am I still able to get root access and use the existing rom that cane with the phone originally and add the wifi hot spot feature. If so where do I find the wifi hotspot software? Sorry if it is a noob question but this is my first post.
Thanks in advance
ExodusC said:
To clarify some things, since half of the users on these boards are misinformed:
The Verizon (and pretty much every) Galaxy S3 has had root since virtually their release date.
The Verizon version does have a locked bootloader (see #3), and there is going to be a "Developer Edition" released directly from Samsung with pretty much no warranty, and it will be completely unsubsidized.
The bootloader lock has not stopped us from flashing custom ROMs or custom kernels. See below.
Here's some source links for you, in rough chronological order:
The "Root66" method for easily obtaining root
Original proof-of-concept showing custom kernels can be booted
Standard install of CyanogenMod 9 via kexec demonstrated
Functioning 3G/4G data on CyanogenMod 9 demonstrated
Unofficial guide to installing CyanogenMod 9
CVPCS states locked bootloader is a non-issue
Ongoing research & development on the locked bootloader
I could go on and on, but as you can see, development of custom ROMs (both TouchWiz and AOSP based) has not been hindered by the locked bootloader.
The community has pulled together on this, and developers from non-Verizon carriers have been tons of help in all the progress that has been made so far.
Many people, including myself, do not support the idea of the Developer Edition SGS3, and I personally doubt it will have even a tiny fraction of the community the consumer version has.
Click to expand...
Click to collapse
saedhamad said:
My question is. Even though the bootloader is locked am I still able to get root access and use the existing rom that cane with the phone originally and add the wifi hot spot feature. If so where do I find the wifi hotspot software? Sorry if it is a noob question but this is my first post.
Thanks in advance
Click to expand...
Click to collapse
Please visit the Verizon SGS3 development forum, all of your questions can be answered with a little browsing.
In short: yes you can root your phone very easily. You can install Free Wifi Tether from the Google Play store, and it works fine on a rooted phone. Finally, rooting involves installing a "stock" ROM (i.e. the one that came with your phone), the only difference being root access.
I have done all of this, so has my totally noob roommate.
saedhamad said:
My question is. Even though the bootloader is locked am I still able to get root access and use the existing rom that cane with the phone originally and add the wifi hot spot feature. If so where do I find the wifi hotspot software? Sorry if it is a noob question but this is my first post.
Thanks in advance
Click to expand...
Click to collapse
I thought my post was pretty clear that you can easily gain root access with the current ROM.
I don't know about using the built-in wifi hotspot feature, but I know apps from the Play Store like FoxFi work just fine, even without root.
The Kexec method is a bandaid solution that can easily be patched by Verizon in the future.
JSMessick said:
As a long time basic phone owner I am finally decided to make the switch to android. I have done my research and have come to the conclusion that i would like to purchase the Samsung galaxy S III. However, money is always an issue and I am trying to spend as little as possible but get the most of out my phone.
With Verizon, my current service, the additional 720$ for the 2 year data contract is scary, but the phone, only 200$ is nice. My major question about Verizon is, is it possible to root the Verizon SGSIII. I have read multiple posts from outraged customers who bricked their phones due to the locked bootloader on the Verizon SGSIII. Also, from what i have read from this thread: http://forum.xda-developers.com/showthread.php?t=1756885 it is possible to root the verizon version of this phone although it is more complicated.
My second option is to purchase the Samsung Galaxy Nexus and root this phone through verizon. I would love to run Android 4.1 Jelly Bean on my device which is why i would like to root the device and flash something that would give me this enhancement. However, if i purchase the Galaxy Nexus, i am locked into a 2 year contract with a phone that came out 6 months ago and could soon be outdated by its "older brother" said to be released this december.
Which is my best option and if someone could please clear up the Root problems with the Verizon SGSIII it would be extremely helpful. Thanks for any response!
Best Regards
JSMessick
Click to expand...
Click to collapse
Going from basic phone (I'm assuming by that u mean a NON smartphone).... And already thinking of modifying. Wow lol.... Just get the gs3 my guess is u will be amazed at its capabilities right out of the box. Welcome to android btw.
Sent str8 from my half eaten Banilla Ice Cream Samich
Just one final question, i know there are many people working on getting 4.1 Jellybean onto the SGSIII for the other versions (at&t sprint international etc.) is there a way i can get it onto the verizon one even with the locked bootloader? Like it is possible to get CM10 alpha on my phone and possible use that? or has this not been figured out yet. sorry for all the questions i just wanna try to learn as much as possible before i make a purchase.
JSMessick said:
Just one final question, i know there are many people working on getting 4.1 Jellybean onto the SGSIII for the other versions (at&t sprint international etc.) is there a way i can get it onto the verizon one even with the locked bootloader? Like it is possible to get CM10 alpha on my phone and possible use that? or has this not been figured out yet. sorry for all the questions i just wanna try to learn as much as possible before i make a purchase.
Click to expand...
Click to collapse
Idk about that BUT I do know that we should be getting the official JB pushed to our devices in Q4 of this year. I've been reading late aug-sep.
Sent str8 from my half eaten Banilla Ice Cream Samich
Related
With the release of the Fascinate we will finally know who is responsible for the encrypted bootloaders on the Droid X/2...Motorola or Verizon
I certainly hope it is not encrypted but I wouldn't put it past Verizon as being the one responsible.
Sent from my DROIDX using XDA App
FSRBIKER said:
With the release of the Fascinate we will finally know who is responsible for the encrypted bootloaders on the Droid X/2...Motorola or Verizon
I certainly hope it is not encrypted but I wouldn't put it past Verizon as being the one responsible.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Well, do a little reading and you will see that motorola locked down the milestone, which came out overseas as the droid 1's cousin, and motorola has come out saying that they will not produce open android handsets like the droid 1 ever again. I dont think the BL will be locked down on the fascinate more so than the other galaxy s phones
Did plenty of reading/flashing/modding over the year+ about Android, it's phones, Rom's, etc so I am no rookie despite my post count at XDA. We all know Motorola's stance and their comments but the Fascinate is the only way we will really know Verizon's stance on bootloaders since the other three US variants have all been unlocked easily.
So WELL if you know the FACTS not speculation then let us hear your all worldly knowledge please.
If you've done enough reading you'll know that Verizon had nothing to do with the lockdown of the bootloader if they did then the Incredible would have been locked down as well as the ally both of which have achieved root. Not to mention Verizon doesn't have a factory where they say "Hey guys we developed this fancy eFuse and tricky bootloader that works in EVERY PHONE" because that would totally make sense a bootloader that's compatible with every chipset and every handset if that was the case someone would have developed an unlocked bootloader that works on every device. Listen to what you're saying, there is no possible way that Verizon distributes an eFuse and a custom encrypted bootloader to every manufacturer. Not trying to be rude or anything it's just common sense.
Achieving Root and Unlocking a Bootloader are two different things, try reading up on that first ok?
No one ever said Verizon is manufacturing phones, but they absolutely can tell the phone manufacturers to lock the bootloaders or Verizon will not offer the phone for sale. Also read up the bootloaders for the Incredible was locked but not digitally encrypted. Since this is the first phone Verizon is offering since the Motorola DroidX/2 which have digitally encrypted bootloaders we will know if Verizon had a hand in changing anything on the Fascinate if it is different at all from the other three US Galaxy phones. That was the only point to my post, why is this a pissing match on who searches, researches, etc more?
If you have Facts/Proof on the Fascinate and its bootloader post it, this other stuff is just crap and not getting anyone anywhere.
DigitalDementia said:
If you've done enough reading you'll know that Verizon had nothing to do with the lockdown of the bootloader if they did then the Incredible would have been locked down as well as the ally both of which have achieved root. Not to mention Verizon doesn't have a factory where they say "Hey guys we developed this fancy eFuse and tricky bootloader that works in EVERY PHONE" because that would totally make sense a bootloader that's compatible with every chipset and every handset if that was the case someone would have developed an unlocked bootloader that works on every device. Listen to what you're saying, there is no possible way that Verizon distributes an eFuse and a custom encrypted bootloader to every manufacturer. Not trying to be rude or anything it's just common sense.
Click to expand...
Click to collapse
"not to be rude or anything", but your post displays little "common sense". The Incredible was released before the latest droids, so obviously the Inc's bootloader is irrelevant in this situation. And who said (or inferred) anything about a verizon factory making a bootloader (and nobody even mentioned efuse)? Verizon didn't develop Bing, but they clearly have a hand in it being the only search offered on this Android phone. So it is not unreasonable to wonder if Verizon would try to exert its influence in other ways. While, I agree that it is unlikely that the Fascinate will have an encrypted bootloader, the OP asked a valid question. Not sure some people are so quick to hate. After all we are only dealing with smartphones.
There are quite people intruded interested in knowing the truth, lets keep the thread on topic PLEASE.
Sent from my DROIDX using XDA App
I have a fascinate on hand to check if someone can let me know what they need done...
Deleted: I was wrong and no need to spread bad info.
edit: deleted, nevermind, should read the newer posts when I've got a tab open for a long time.
sic4672 said:
I believe the bootloader is locked because the same root process for the captivate and vibrant don't work for the fascinate.
Click to expand...
Click to collapse
This is no indication that it is locked or not.
It is not locked.
Sent from my SCH-I500 using XDA App
ksizzle9 said:
It is not locked.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Thank you... Short sweet answer.
Ksizzle can you link a thread where it shows its not locked, thanks in advance.
Sent from my DROIDX
i actually cannot. however we can make changes to the kernel or will be able to which actually may not mean that it isnt locked but it is definetly not encrypted like the droid x. i dont have any proof but have no other galaxy s of the six different variants have a locked bootloader and if it were locked you would have read about it somewhere already or heard peopole trashing samsung and verizon. i dont have any proof but im pretty sure its not locked becasue if it were we would have to make all these workarounds for rooting and making changes to the kernel or loading roms. a guy has already made a ROM in the development section and we dont need a BOOTSTRAPP app or anything special. trust me its not locked or we wouldnt already have a custom ROM available.
ksizzle9 said:
i actually cannot. however we can make changes to the kernel or will be able to which actually may not mean that it isnt locked but it is definetly not encrypted like the droid x. i dont have any proof but have no other galaxy s of the six different variants have a locked bootloader and if it were locked you would have read about it somewhere already or heard peopole trashing samsung and verizon. i dont have any proof but im pretty sure its not locked becasue if it were we would have to make all these workarounds for rooting and making changes to the kernel or loading roms. a guy has already made a ROM in the development section and we dont need a BOOTSTRAPP app or anything special. trust me its not locked or we wouldnt already have a custom ROM available.
Click to expand...
Click to collapse
Lack of a locked bootloader is why I chose this phone over the X. Well, that and the better processor. The post indicating that it is not locked can be found HERE.
so why is there such a convoluted method for rooting? On the Galaxy S I900, Vibrant, and Captivate you just throw an update.zip on the phones internal memory, reboot into recovery, and hit apply update. theres your root, no adb required, no shell commands. If its not locked then why is it this bad over here.
I believe because they have different types of internal memory. Cud b wrong. But the bootloader is why I chose this phone as well.
Sent from my SCH-I500 using XDA App
chaoscentral said:
so why is there such a convoluted method for rooting? On the Galaxy S I900, Vibrant, and Captivate you just throw an update.zip on the phones internal memory, reboot into recovery, and hit apply update. theres your root, no adb required, no shell commands. If its not locked then why is it this bad over here.
Click to expand...
Click to collapse
The same method would work if someone compiled it for our hardware.
Hop to it someone.
chaoscentral said:
so why is there such a convoluted method for rooting? On the Galaxy S I900, Vibrant, and Captivate you just throw an update.zip on the phones internal memory, reboot into recovery, and hit apply update. theres your root, no adb required, no shell commands. If its not locked then why is it this bad over here.
Click to expand...
Click to collapse
i dont have many posts here but i do a bunch of help at other sites. iv rooted the d1. the devour, the inc, the d2 and now the gal s....everytime the adb way comes first. it does not mean in anyway that the bootloader is locked. sammy gave us the codes and ina few days we will see clockwork and then a few weeks after that the real fun starts. the boot loader is not locked.
Hello,
I, like so many others am trying to decide between the Samsung Galaxy S3 & the HTC Evo 4G LTE. One thing that I definitely want is to be able to root and flash ROMS on whichever phone I get. I know that root has been achieved on both phones but I'd like thoughts on developer support between the two, and which one (or both) can be set back to an original state where it's not known it was rooted for warranty purposes. I know HTC lets you unlock the bootloader but unless there's a workaround it'll say relocked on the bootloader allowing anyone savvy enough to check that it's been rooted. Wondering if current root versions are S-on, S-off or either with the owner choosing. Or perhaps S-off is a must in order to truly relock the bootloader so it says locked instead of relocked. I also read in my research that you can trip a counter on the S3 the counts how many ROMS have been flashed... Although I also read it's possible to root without tripping the counter but if anything goes wrong, you can't reset the counter.
Now, it seems like the S3 would have the most dev support since it's been released globally but I'm assuming that the ROMS developed for the global quad core version won't be compatible with the dual core US version. Is this correct? Is there Evo dev community really committed so that I could expect similar work being done for both phones?
Lastly, I'm assuming that the S3 will have more accessories available for it given its release on 5 US carriers without any changes in the phone... Seems like a first for any phone but the iphone. Do you agree with this or do you expect lots of accessories and aftermarket items available for the Evo LTE as well.
I know that there's a lot of questions in this but with the phones being so similar, this may be the area that differentiates them. And I know that I definitely want to root the phone... No question on that.
Thanks in advance for any and all advice! I appreciate it so much!
my simplified answer is: get the s3. more dev support, more accessories, mor everything. you can flash beats audio for the s3 too if that is important. great cm9 and aosp/aokp support as well
Seriously?! You can flash beats audio to the S3? Will it affect all sound that comes out of the phone (phone speaker, hands free speakerphone, music, video, all of it?) like it does on the Evo LTE? That's so cool... Not so much that I'd want it for sure but that I could have one of the main selling points on an Evo LTE on an S3! Freakin' awesome. Thanks so much for that reply and info.
You can't flash the international roms
But universalizing all us rooms for all us carriers are being worked on
Sent from my SPH-D710 using xda premium
gtuansdiamm said:
You can't flash the international roms
But universalizing all us rooms for all us carriers are being worked on
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Cool. So, in theory, there could be 2-4x the devs working on S3 ROMS as the exact same phone is being released on 5 US carriers simultaneously. So, where most phones have devs from one or maybe two carriers... This will have devs from all 5. That has the potential to really make a difference and certainly add to the development synergistically. That's exciting!
Its gonna be like nexus development
But less confusing cause we have more subsections
Sent from my SPH-D710 using xda premium
I remember the HTC Evo days. Boy, I spent hours-a-day browsing the development section on XDA to get my flash fix. That carried over with my Samsung Galaxy S2 and then the S3. Now that I'm considering coming back to HTC for a fresher experience, I found myself jaw-dropped at how ghostly the development forums are. I figured this could be a result of the phone being so young; so I went to the GS4 to see if that holds true. Wow... what a difference. Those forums seem busier than hell. And it's only been about a month since it was released as well.
Anyone have any idea why that is? I've been trying to convince myself to get the HTC One. I got over the fact that it lacks a replaceable battery, a MicroSD card, and recently, I got over the fact that the images are just not all that it's hyped up to be. I figured I'd be transitioning to the Moto X Phone when that comes out later in the year, so I might as well put-up with these shortcomings. But not having the development support that I experienced with the earlier HTC devices, and recently with the Samsung devices is just not something I think I can get over.
I am constantly thinking of the word "potential" when referring to this phone. What a shame. HTC had all the tools to flip the market on its feet, but it seems as if they came up short... again.
Check out the non-carrier-specific forum...it's pretty active.
EDIT: HTC didn't come up short, this phone is considered quite a success.
My theory for this specific forum being dead is that T-Mobile's national release of this phone was yesterday (06/05/2013). Before that, it was only available in their "high-volume" locations.
Oh wow. And all of those will work with the Tmo version?
Sent from my badass Samsung Galaxy SIII.
yea all the development is in the international forum. all roms on that forum will work on the tmo htc one and they work very well. i have flashed every sense based rom and most of the aosp roms. definitely not a ghost town over there:good:
Yeah, they should. But as always, continue at your own risk.
akarol said:
Oh wow. And all of those will work with the Tmo version?
Sent from my badass Samsung Galaxy SIII.
Click to expand...
Click to collapse
yes but the 4.2 sense roms havent implemented support for tmo yet they still work as im running trickdroid 7.0 now just no wifi calling yet but the 4.1 versions have wifi calling and most other tmo stuff
akarol said:
I remember the HTC Evo days. Boy, I spent hours-a-day browsing the development section on XDA to get my flash fix. That carried over with my Samsung Galaxy S2 and then the S3. Now that I'm considering coming back to HTC for a fresher experience, I found myself jaw-dropped at how ghostly the development forums are. I figured this could be a result of the phone being so young; so I went to the GS4 to see if that holds true. Wow... what a difference. Those forums seem busier than hell. And it's only been about a month since it was released as well.
Anyone have any idea why that is? I've been trying to convince myself to get the HTC One. I got over the fact that it lacks a replaceable battery, a MicroSD card, and recently, I got over the fact that the images are just not all that it's hyped up to be. I figured I'd be transitioning to the Moto X Phone when that comes out later in the year, so I might as well put-up with these shortcomings. But not having the development support that I experienced with the earlier HTC devices, and recently with the Samsung devices is just not something I think I can get over.
I am constantly thinking of the word "potential" when referring to this phone. What a shame. HTC had all the tools to flip the market on its feet, but it seems as if they came up short... again.
Click to expand...
Click to collapse
As you've noticed by now, there's plenty of developer support for the HTC One. It's all just confined to the general HTC One forums, which makes sense, as the various roms can be used on the AT&T, T-Mobile, and international HTC One's. Most developers don't want to have to maintain 3 or more separate threads for the same thing.
As was pointed out though, if you're looking for T-Mobile wifi calling compatibility, be careful about the ROMs you flash. Since the 4.2.2 OTA for T-Mobile isn't out yet, no 4.2.2 ROM is going to support it. I'd suggest Android Revolution 9.4, or a similar 4.1.2 ROM if WIFI calling is essential to you.
Also, since a Google edition of the phone is going to be coming out in the near future, developer support is likely going to expand even further.
So I think it's safe to say you can put your fears to rest and buy an HTC One. I don't think you'll regret it.
Yea I've been hanging out in the International One forums as almost all their ROMs work for us.
This forum really shouldn't even have a development section since there's not really any specific T-Mo stuff that needs to be done.
Every single ROM in the GSM section will work for T-Mo. There isn't a single one that won't work. The only thing you lose is T-Mo's branded stuff and T-Mo's wifi calling (as they are the only ones who do Wifi calling)/
LiquidSolstice said:
This forum really shouldn't even have a development section since there's not really any specific T-Mo stuff that needs to be done.
Every single ROM in the GSM section will work for T-Mo. There isn't a single one that won't work. The only thing you lose is T-Mo's branded stuff and T-Mo's wifi calling (as they are the only ones who do Wifi calling)/
Click to expand...
Click to collapse
Thanks you guys so much for your replies. I'm happy to see that the development forums for the One is indeed thriving. I'm more confident in snagging a one over the GS4 now.
Indeed, I don't see a reason as to why even bother with a Tmo specific section.
Sent from my badass Samsung Galaxy SIII.
akarol said:
Thanks you guys so much for your replies. I'm happy to see that the development forums for the One is indeed thriving. I'm more confident in snagging a one over the GS4 now.
Indeed, I don't see a reason as to why even bother with a Tmo specific section.
Sent from my badass Samsung Galaxy SIII.
Click to expand...
Click to collapse
Psssst... psssttt hey if u come we will welcome you!:screwy:
Sent from my SGH-M919 ddr3 13mp bad ass s4 using xda app-developers app
Firov said:
As you've noticed by now, there's plenty of developer support for the HTC One. It's all just confined to the general HTC One forums, which makes sense, as the various roms can be used on the AT&T, T-Mobile, and international HTC One's. Most developers don't want to have to maintain 3 or more separate threads for the same thing.
As was pointed out though, if you're looking for T-Mobile wifi calling compatibility, be careful about the ROMs you flash. Since the 4.2.2 OTA for T-Mobile isn't out yet, no 4.2.2 ROM is going to support it. I'd suggest Android Revolution 9.4, or a similar 4.1.2 ROM if WIFI calling is essential to you.
Also, since a Google edition of the phone is going to be coming out in the near future, developer support is likely going to expand even further.
So I think it's safe to say you can put your fears to rest and buy an HTC One. I don't think you'll regret it.
Click to expand...
Click to collapse
I was able to dig up an old link for Android Revolution 9.4 but can't find a description or list of features etc for it. Are you positive it has wi-fi calling in it?
I haven't owned an HTC since the OG Nexus One (had all Nexus devices since) so I'm reading up on S-OFF etc before I flash a new ROM. I really want to try out wifi calling though so that's why I'd like to make sure. Thanks in advance!
PS - link to ROM if anyone wants it: http://www.androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-One_9.4.zip
the7thson said:
I was able to dig up an old link for Android Revolution 9.4 but can't find a description or list of features etc for it. Are you positive it has wi-fi calling in it?
I haven't owned an HTC since the OG Nexus One (had all Nexus devices since) so I'm reading up on S-OFF etc before I flash a new ROM. I really want to try out wifi calling though so that's why I'd like to make sure. Thanks in advance!
PS - link to ROM if anyone wants it:
Click to expand...
Click to collapse
9.4 definitely has wifi-calling. I'm on 9.3 at the moment and wifi-calling works perfectly for me on T-Mobile. In the installer, just be sure to select T-Mobile as your carrier and it will install all the necessary files for wifi calling.
Also, note that S-Off isn't required to flash this ROM. All you need to do is unlock your device through HTC Dev, located at the HTC Dev site. I'd give you a direct link, but asinine restrictions in place on this forum are preventing that at the moment. Just Google HTC Dev and it will be the first result. You can't miss it.
Anyway, unlike with earlier HTC devices, this unlock method allows you to flash everything you need to update the ROM. Only some of the "black box" partitions like the radio and bootloader aren't flashable when it's unlocked with this method, but to my knowledge, no ROM requires that, and furthermore, the Nexus devices are very similar in that respect.
The only real advantage to S-Off is if you plan on flashing a different carrier's RUU, altering the radio, or changing your CID. Anyway, just something to be aware of.
Good luck.
Firov said:
9.4 definitely has wifi-calling. I'm on 9.3 at the moment and wifi-calling works perfectly for me on T-Mobile. In the installer, just be sure to select T-Mobile as your carrier and it will install all the necessary files for wifi calling.
Also, note that S-Off isn't required to flash this ROM. All you need to do is unlock your device through HTC Dev, located at the HTC Dev site. I'd give you a direct link, but asinine restrictions in place on this forum are preventing that at the moment. Just Google HTC Dev and it will be the first result. You can't miss it.
Anyway, unlike with earlier HTC devices, this unlock method allows you to flash everything you need to update the ROM. Only some of the "black box" partitions like the radio and bootloader aren't flashable when it's unlocked with this method, but to my knowledge, no ROM requires that, and furthermore, the Nexus devices are very similar in that respect.
The only real advantage to S-Off is if you plan on flashing a different carrier's RUU, altering the radio, or changing your CID. Anyway, just something to be aware of.
Good luck.
Click to expand...
Click to collapse
Sweet, thanks I'll definitely try 9.4 then! Reception in my office all day is terrible so I'm excited to try wi-fi calling.
I think I understand in theory why S-OFF would not be needed. but the nerd in me wants full control with S-OFF.. Also, if I use S-OFF, i can return my phone to bone-stock and keep warranty right? As amazing as the hardware on the HTC One is (I've gotten used to sub-standard hardware with the Nexus line), I'm not 100% sure yet I want to keep it.
Any chance you could educate me on what CID is for? Evidently it may restrict/allow flashing ROMS from certain regions?
Also, I believe I have a basic understanding of what an RUU is, but could you elaborate for me by any chance? I believe it's basically an all i one installer for a full stock ROM?
Sorry if this is a bit off-topic, but this T-Mo sub forum seems a bit more forgiving than some other areas
the7thson said:
Sweet, thanks I'll definitely try 9.4 then! Reception in my office all day is terrible so I'm excited to try wi-fi calling.
I think I understand in theory why S-OFF would not be needed. but the nerd in me wants full control with S-OFF.. Also, if I use S-OFF, i can return my phone to bone-stock and keep warranty right? As amazing as the hardware on the HTC One is (I've gotten used to sub-standard hardware with the Nexus line), I'm not 100% sure yet I want to keep it.
Any chance you could educate me on what CID is for? Evidently it may restrict/allow flashing ROMS from certain regions?
Also, I believe I have a basic understanding of what an RUU is, but could you elaborate for me by any chance? I believe it's basically an all i one installer for a full stock ROM?
Sorry if this is a bit off-topic, but this T-Mo sub forum seems a bit more forgiving than some other areas
Click to expand...
Click to collapse
It's worth doing to S-OFF. If you do, you'll have the ability to relock the phone and put it back to S-ON with zero indication that you ever messed with it. Also, CIDs are used to restrict ROMs from certain carriers to only be installed on certain devices. It's really only a stock or stock-leak ROM limitation, I don't think a single ROM in either the regular or original development section is CID-locked. Either way, if you are S-OFF, you can change your CID code to whatever you want it to be (the code "111111") is referred to as "SuperCID" because that allows you to in theory run an RUU/OTA from ANY Carrier regardless.
You are correct about what an RUU is. However, each RUU is specific to a build of Android made by the carrier, and so far, I think only the Sprint RUU is out. No one has a T-Mo RUU yet (but you really don't need one, all you have to do is flash the stock rooted ROM from our section here and then unroot from the SU app options).
Enjoy tinkering.
LiquidSolstice said:
It's worth doing to S-OFF. If you do, you'll have the ability to relock the phone and put it back to S-ON with zero indication that you ever messed with it. Also, CIDs are used to restrict ROMs from certain carriers to only be installed on certain devices. It's really only a stock or stock-leak ROM limitation, I don't think a single ROM in either the regular or original development section is CID-locked. Either way, if you are S-OFF, you can change your CID code to whatever you want it to be (the code "111111") is referred to as "SuperCID" because that allows you to in theory run an RUU/OTA from ANY Carrier regardless.
You are correct about what an RUU is. However, each RUU is specific to a build of Android made by the carrier, and so far, I think only the Sprint RUU is out. No one has a T-Mo RUU yet (but you really don't need one, all you have to do is flash the stock rooted ROM from our section here and then unroot from the SU app options).
Enjoy tinkering.
Click to expand...
Click to collapse
Perfect, thanks for confirming all that. I think I'm ready to get the HTC-noob stink off of me The phone feels so amazing in hand, it's making me look at all these Nexus devices (Nexi?) I have in a bit of a different light.. And once the Google Experience software drops, hopefully I won't miss having a Nexus as my daily driver!
You guys are so awesome. I'm counting down the days until July 1st now when I'll get my hands on my own HTC One. =)
Sent from my badass Samsung Galaxy SIII.
the7thson said:
Perfect, thanks for confirming all that. I think I'm ready to get the HTC-noob stink off of me The phone feels so amazing in hand, it's making me look at all these Nexus devices (Nexi?) I have in a bit of a different light.. And once the Google Experience software drops, hopefully I won't miss having a Nexus as my daily driver!
Click to expand...
Click to collapse
akarol said:
You guys are so awesome. I'm counting down the days until July 1st now when I'll get my hands on my own HTC One. =)
Sent from my badass Samsung Galaxy SIII.
Click to expand...
Click to collapse
You're going to enjoy the One. It's the first Android phone to have the build quality of an iPhone with specs that beat the pants off it
The only thing that sucks about the One is that because it has such a high pixel density, you will be extremely sensitive and aware of pixels in all your other displays (laptop/desktop/tablet etc).
I own an ASUS Zenbook, which is a 13" ultrabook with a full 1920x1080p display which is retina-levels of dense on such a small screen (I think it's almost 170 pixels per inch). The One? The one is a whopping ~470 pixels per inch. It is stupidly dense and I promise you won't find a single pixel no matter how hard you look.
the7thson said:
I was able to dig up an old link for Android Revolution 9.4 but can't find a description or list of features etc for it. Are you positive it has wi-fi calling in it?
I haven't owned an HTC since the OG Nexus One (had all Nexus devices since) so I'm reading up on S-OFF etc before I flash a new ROM. I really want to try out wifi calling though so that's why I'd like to make sure. Thanks in advance!
PS - link to ROM if anyone wants it: http://www.androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-One_9.4.zip
Click to expand...
Click to collapse
would anyone happen to have a working link for Android Revolution 9.4???
jjohn999 said:
would anyone happen to have a working link for Android Revolution 9.4???
Click to expand...
Click to collapse
Look like they took it down. I have it in my local computer here and I can upload it for you somewhere if you like. PM me if you have access to somewhere I can put it for you.
Tried talking to Samsung to find out why those of us never receive updates to our software. Besides their chat being a joke as usual this is what i got:
Melina: I understand that you want to know why developer edition Galaxy S4 does not get updates like normal S4 . Is that correct?
Visitor: yes
Melina: Thank you for confirming.
Melina: May I know the model number of the device? To know the model number of the device, please tap on Home>> Applications>> Settings>>More tab>> About Device/About phone. It generally starts with SCH or SGH or SPH or GT.
Visitor: sch-i545
Melina: Thank you for the model number.
Melina: May I know your device base band version? You can find it in Applications>>Settings>>About Device/ About Phone.
Visitor: i545oyuamdk
Melina: Thank you for the information.
Melina: May I place you on hold for 2 minutes, while I gather the information on your request?
Visitor: yes
Melina: Thank you.
Melina: Thank you for waiting. I appreciate your time and patience.
Melina: I should inform you that your device has an update to Android 4.3 Jelly Bean through OTA( Over The Air) . OTA updates are pushed by the carrier. You need to contact your carrier and request them to push the update on your device.
Melina: You can contact Verizon support at 1-888-466-4646.
Click here to reach them online.
Melina: http://www.samsung.com/us/support/faq/FAQ00053701/63350/SCH-I545ZKDVZW
Melina: Please click on the above link to view how to update your device to Android 4.3 and information about the update.
Melina: Are you able to open the above link?
Visitor: yes i realize that this has this update which is why i am asking why i do not recieve it. YOu also pushed out 2 other OTA updates prior to this that only the consumer edition galaxy s4 got, the developer edition does not ever get them. The link you sent is for the update all galaxy s4 should be receiving but as if stated, noone who owns a developer edition gets these.
Melina: I understand your concern.
Melina: I should inform you that OTA updates are released by the carrier and not by Samsung. They push the update in batches by selecting devices randomly. You can contact them and request to push the update.
Visitor: i have contacted verizon before in regards to the previous updates not being installed. THey have informed me that you, samsung, does not release any of these updates for the developer edition, the updates you give to verizon are only good for the consumer edition. SO yes my question still stands why are there no updates for this version of the phone. Im sorry if you do not have an answer for this question please direct me to someone who does
Melina: I'm sorry for the delay. I'll be right with you.
Melina: I am sorry for the delay.
Melina: I should inform you that Kies software updates are provided by Samsung and OTA updates are provided by carrier. However I should inform you that boot loader of developers edition devices are by default unlocked and these phones are meant to install third party software on their devices thus Samsusng does not specifically provide software update. I request you to contact our higher level of chat support to know more information about the same.
Melina: You can contact our voice support at 1-888-987-4357, Mon-Fri: 7 AM - 9 PM (CST), Sat: 9 AM - 6 PM (CST).
So yes essentially they are never going to update the dev edition galaxy s4 from the current build. And as we know installing the consumer edition software is no good for our phone. So glad i spent $650 on a phone that will never receive updates.
You have an unlocked bootloader, just install any custom rom. There will be a wave of 4.3 based roms soon/already.
MehStrongBadMeh said:
You have an unlocked bootloader, just install any custom rom. There will be a wave of 4.3 based roms soon/already.
Click to expand...
Click to collapse
Absolutely...and I wouldn't be surprised if one shows up today.
MehStrongBadMeh said:
You have an unlocked bootloader, just install any custom rom. There will be a wave of 4.3 based roms soon/already.
Click to expand...
Click to collapse
That is not a stock software from Samsung. Yes it's nice to flash a rom, but if they had no intentions of updating the phone they should outline that before purchase. Why do you replace your phone over time? Because it becomes old and no longer recieves updated android. So by them selling a phone with no updates from the start, they are basically stating the device is EOL.
While true in the strictest sense, there really is no compelling reason to purchase the dev edition for anything but the unlocked bootloader. If all you were looking for was updated stock firmware, the three standard s4 is all that is needed. The dev s4 can effectively receive all the updates the standard s4 receives by using custom roms based on said updates. Also, the unlocked bootloader means you will be able to use custom roms of Android updates that are made long after Samsung ceases to make official updates for the device.
Samsung seems to always direct you back to the carrier (VZW) in this case. Irony is the the GPe version is not supported by the carrier but by Samsung/Google. Although google does not post the binaries either of the device. Since our device is locked to VZW I would bug Big Red for all its worth.
My 2 cents
MehStrongBadMeh said:
While true in the strictest sense, there really is no compelling reason to purchase the dev edition for anything but the unlocked bootloader. If all you were looking for was updated stock firmware, the three standard s4 is all that is needed. The dev s4 can effectively receive all the updates the standard s4 receives by using custom roms based on said updates. Also, the unlocked bootloader means you will be able to use custom roms of Android updates that are made long after Samsung ceases to make official updates for the device.
Click to expand...
Click to collapse
This.
If you're going to buy the dev edition and you're not even a developer, then you bought it to run custom roms. You shouldn't care about if they update the stock firmware.
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
joshm.1219 said:
This.
If you're going to buy the dev edition and you're not even a developer, then you bought it to run custom roms. You shouldn't care about if they update the stock firmware.
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
You are correct, sir!
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
Personally, I agree with both sides. In one case, you have an unlocked bootloader for a reason.
I believe you dealt with an uninformed agent in that chat, as she was just reading from a script, you could tell with the whole "can I confirm you are" blah blah. Try getting on the phone and dealing with a live American rep.
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
This.
If you're going to buy the dev edition and you're not even a developer, then you bought it to run custom roms. You shouldn't care about if they update the stock firmware.
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I agree however i bought the dev edition solely for the fact i can customize it, and then run custom roms once i get bored of stock. Like any phone. However this leaves anyone with this phone no choice but to run custom roms for any updated software. It really doesn't matter what i wanted from the phone, or anyone else wanted, its solely the fact Samsung sold a phone with no intentions of supporting it beyond release. I can say that everyone who bought the standard gs4 should never have expected to run a custom rom and just be happy with stock as well, because thats exactly what the standard edition is made for. But we both know thats not true for the majority of people owning it. Samsungs selling point for the Dev edition is the choice to do what you want with it, by not supporting it they aren't giving you a choice to keep it stock (even though they give you no firmware image to get back to stock if you mess it up.) So yes i am right in saying they messed up big time with the Dev edition.
I have a conflicting view. I wouldnt personally want my developer edition phone to recieve updates, id rather want complete control over what is flashed to my device and I know I can just build a stock rom for the dev device from the consumer ed. updates. However not all people know how to build their own roms, know which partitions to ignore/modify/flash or know how to make it all come together and work. I think the issue is that there aren't many developers with dev s4's. Its possible to make odin images for all the corresponding consumer update builds. Dev edition devices are only limited by the ability and knowledge of their owners. Consumer devices dont get that luxary.
Sent from my XT912 using xda app-developers app
Surge1223 said:
I have a conflicting view. I wouldnt personally want my developer edition phone to recieve updates, id rather want complete control over what is flashed to my device and I know I can just build a stock rom for the dev device from the consumer ed. updates. However not all people know how to build their own roms, know which partitions to ignore/modify/flash or know how to make it all come together and work. I think the issue is that there aren't many developers with dev s4's. Its possible to make odin images for all the corresponding consumer update builds. Dev edition devices are only limited by the ability and knowledge of their owners. Consumer devices dont get that luxary.
Sent from my XT912 using xda app-developers app
Click to expand...
Click to collapse
I agree with that surge, the problem being like you said, those of us with limited development skillset cannot build the rom. guess I have something to learn
The other is brickability. Since the dev ed is more brickable without a true factory image to recover its a catch 22. Unlike the GPe there isn't any way to unlock the bootloader if it should become relocked.
my 2 cents
oakley470 said:
I agree however i bought the dev edition solely for the fact i can customize it, and then run custom roms once i get bored of stock. Like any phone. However this leaves anyone with this phone no choice but to run custom roms for any updated software. It really doesn't matter what i wanted from the phone, or anyone else wanted, its solely the fact Samsung sold a phone with no intentions of supporting it beyond release. I can say that everyone who bought the standard gs4 should never have expected to run a custom rom and just be happy with stock as well, because thats exactly what the standard edition is made for. But we both know thats not true for the majority of people owning it. Samsungs selling point for the Dev edition is the choice to do what you want with it, by not supporting it they aren't giving you a choice to keep it stock (even though they give you no firmware image to get back to stock if you mess it up.) So yes i am right in saying they messed up big time with the Dev edition.
Click to expand...
Click to collapse
Well, just playing devil's advocate, you would think that the purpose of a developer edition is to have custom software on it. I agree with what you said about the expectations of someone who buys a stock phone of course, but it's obviously not true the majority of people owning a stock phone want custom software. I don't know if you meant to type it like that but I can assure you most people who buy the s4 in the world run normal Touchwiz and have no idea about ROM's, bootloaders, android versions, etc. I can make assumptions too about Samsung's selling point for the Dev Edition, but the only differentiating factor is an unlocked bootloader. The purpose of that is to run custom software, thus the purpose of the Dev Edition. Also, they might just assume the developers these devices are really meant for know how tobuild updated stock rom's if they wanted to. I understand your frustration in that it wasn't upfront information before you purchased it.
Buy a Dev phone with no knowledge of building ROMs and then complain about updates not being released for a phone built for ROM development purposes? Not sure why this is even an issue.
Sent from my SCH-I545 using XDA Premium 4 mobile app
chriskader said:
Buy a Dev phone with no knowledge of building ROMs and then complain about updates not being released for a phone built for ROM development purposes? Not sure why this is even an issue.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure why you felt the need to post? The complaint is valid for many with a dev edition, everyone was wondering why they don't receive the updates, I have now answered that.
Even if we didn't get otas it would be nice if they released an Odin flashable factory image for when we screw our phones up.
Sent from my SCH-I545 using Tapatalk
Knowing how to make your own ROM's has nothing to do with owning a Dev edition phone. If you had to buy the phone at retail price anyways, the Dev edition is a better choice, so I'm sure a lot of people did that. Even if they never planned to put custom ROM's on it.
Also to add, firmware updates come with security fixes, and radio updates to better connect to the carriers network (AWS support..). If they can sell a phone that connects to Verizon, they should update it the same as Verizon does with consumer version.
Schoat333 said:
Knowing how to make your own ROM's has nothing to do with owning a Dev edition phone. If you had to buy the phone at retail price anyways, the Dev edition is a better choice, so I'm sure a lot of people did that. Even if they never planned to put custom ROM's on it.
Also to add, firmware updates come with security fixes, and radio updates to better connect to the carriers network (AWS support..). If they can sell a phone that connects to Verizon, they should update it the same as Verizon does with consumer version.
Click to expand...
Click to collapse
I agree although ROMing is the main activity with this phone other updates and software have nothing to do with the ROM. Since this is my first Dev Ed, I'm slightly disappointed.
I've tweeted with VZW to no avail but they seem to at least acknowledge the Dev Ed but don't have much info.
My 2 Cents
Schoat333 said:
Knowing how to make your own ROM's has nothing to do with owning a Dev edition phone. If you had to buy the phone at retail price anyways, the Dev edition is a better choice, so I'm sure a lot of people did that. Even if they never planned to put custom ROM's on it.
Also to add, firmware updates come with security fixes, and radio updates to better connect to the carriers network (AWS support..). If they can sell a phone that connects to Verizon, they should update it the same as Verizon does with consumer version.
Click to expand...
Click to collapse
I agree. Dev edition phones are not just for running Roms. There is a reason that Stock images are put out there, so the those with Dev editions that do play around, have a way of getting back to a fresh restart. So a Dev edition is permanently locked on old software? That makes no sense. It should be up to Samsung to release the VZW 4.3 update for the Dev edition through Kies, not pushed, but offered. Those with Dev editions should have the ability to upgrade and still tinker, and given a the stock image to restart when necessary. It's why they shelled out the extra $.
Hey, I am about to upgrade and I will likely hold out for the new Motorola phone, but if it is a disappointment then the G3 is a very interesting option.
Curious what to look for as far as custom ROMs are concerned. I am addicted to running custom ROMs however I have had a Nexus phone lately so the whole unlocking/rooting/hackability has never been an issue. I see the the G3 has root, but I presume something else must be done before a custom recovery can be installed...thus no custom ROMs.
I love the G3s hardware, but I will never love OEM software. I want stock Android and I am hoping that will be possible with the Moto X+1 and/or the G3.
Thanks guys and gals
I'm pretty sure once someone can find an exploit to unlock the boot loader, we'll see a custom recovery as well as a few roms shortly after. I don't think there will be stock android until CM adds G3 support
I have faith in the devs that they'll eventually unlock this phone. It's been said in a few places that the security isn't as tough as say in the S4 for example.
That said though... This phones stock experience really isn't bad IMO. Best stock I've ever had. Being rooted and with xposed it's quite tolerable.
I'm a crack flasher though so believe me the itch is there!
- Sent From My G3
Mistertac said:
I have faith in the devs that they'll eventually unlock this phone. It's been said in a few places that the security isn't as tough as say in the S4 for example.
That said though... This phones stock experience really isn't bad IMO. Best stock I've ever had. Being rooted and with xposed it's quite tolerable.
I'm a crack flasher though so believe me the itch is there!
- Sent From My G3
Click to expand...
Click to collapse
Agree totally
If you want a flagship phone that will definitely run custom roms, I believe the htc one m8 is it for now. I agree with the other posters that the G3 will likely get a bootloader unlock at some point, but there are no guarantees. That said, the stock rom has a similar look and feel to the cm 11 rom I was running on my galaxy s3. While not AOSP, it doesn't annoy me the way touchwiz did and I won't have buyer's remorse if the bootloader stays locked.
Robshr said:
Agree totally
Click to expand...
Click to collapse
+2
better be soon or mine is gone.
oneandroidnut said:
better be soon or mine is gone.
Click to expand...
Click to collapse
You know as soon as you get rid of yours like the following day or week they'll unlock it lol
... So get rid of it quick!
- Sent From My G3
Mistertac said:
You know as soon as you get rid of yours like the following day or week they'll unlock it lol
... So get rid of it quick!
- Sent From My G3
Click to expand...
Click to collapse
haha ok i will throw in my desk drawer then and hope it gets unlocked!!!
This thread is pointless! Asking will there ever be custom ROMs? Of course there will be. But what you and many others fail to remember is that these phones are harder and harder to crack each time. Only reason the M8 had root and S-Off so quickly is jcase had a 3yr old vuln that wasnt patched yet. They patched it and then he had to spend more time and money cracking it again and he made a new version, which he charged for since it was such a PITA. Look how long it took the S5 to get it. Just be happy we have root.
If you are so worried about not having an unlocked bootloader, you should get rid of Verizon and get AT&T or Tmo that supports devices that are unlocked right from the manufacture. They will always have Nexus devices and other cool ones Verizon will never see since they dont allow none Verizon devices on their network.
droidkevlar said:
This thread is pointless! Asking will there ever be custom ROMs? Of course there will be. But what you and many others fail to remember is that these phones are harder and harder to crack each time. Only reason the M8 had root and S-Off so quickly is jcase had a 3yr old vuln that wasnt patched yet. They patched it and then he had to spend more time and money cracking it again and he made a new version, which he charged for since it was such a PITA. Look how long it took the S5 to get it. Just be happy we have root.
If you are so worried about not having an unlocked bootloader, you should get rid of Verizon and get AT&T or Tmo that supports devices that are unlocked right from the manufacture. They will always have Nexus devices and other cool ones Verizon will never see since they dont allow none Verizon devices on their network.
Click to expand...
Click to collapse
I don't believe it is a "pointless" thread or question. GS5 doesn't have an unlocked bootloader and who knows if they ever will. They have an exploit to run essentially stripped down versions of the stock ROM but that is it. I have not intentions on switching carriers I was simply asking what the status of the G3 was as far as unlocking was concerned.
Thank you to everyone else that responded, I think the G3 is still a viable option for me. I am going to wait to see what Motorola puts out there, but if I don't like it I'll pull the trigger on the G3.
I think it is pointless because you're asking people to predict the future. Nobody can answer the question. Therefore, the question is pointless.
This thread has outlived it's usefulness.
The progress of this device's development can be followed by reading the threads in it's forum.
When progress is made it will be reported in either the general or development sections.
If there are any questions please PM me.
Thread closed