[Q] Any AT&T disadvantage to rooting? - AT&T HTC One (M8)

I'm not a newbie, so this isn't about the safety of rooting. My other units recently have included Verizon and a non-cellular Samsung tablet, both of which are blocked from getting updates if rooted. And in the distant past, AT&T did the same thing (with the Motorola Backflip.) Since some of the updates were radio improvements, that was rather unfortunate.
Are there still such problems with rooting? Do the ROMs make it out quickly anyhow (as they did with the Backflip)? I'm good with the technical risk of rooting, but would like to assess the bureaucratic risk before diving in.

Root itself will not block OTA, from my understanding. However, any system files that were altered, uninstalled, frozen, etc. by root need to be returned to the "stock" condition, as this will block OTA from installing (all system files are checked before OTA install).
Also, stock recovery needs to be installed.
But my opinion, is that especially on the AT&T variant, OTAs have no place on a rooted/modded phone, anyway. One of the great things about being bootloader unlocked, rooted, etc. is that you can install ROMs based on other carrier's software, especially the international version, which gets updates before we do.
For instance, I've already been running Android 4.4.3 version of Sense (international base) for a few weeks now, with the AT&T release nowhere in sight (supposed to be "soon", but who know exactly when?).
Some folks do like the AT&T base features, such as Visual Voicemail support and ISIS. But I don't personally care for them. And there are ROMs built with that functionality as well. Wonders_Never_Cease for instance has a 4.4.3 ROM based on the Dev Edition OTA, with VVM and ISIS added.
Moral of the story, IMO root and don't worry about OTAs. The community here will take care of you. Or worst case you can restore the system files and stock recovery if you really want OTA.

redpoint73 said:
Root itself will not block OTA, from my understanding. ...But my opinion, is that especially on the AT&T variant, OTAs have no place on a rooted/modded phone, anyway.
Click to expand...
Click to collapse
"No place" is a bit harsh, but I will forgive you the hyperbole for the sake of creative, if vapid, license. Largely I agree.
But "the community" doesn't tend to support custom hardware as well as the carrier. I go back a distance; you couldn't trust the then. In fairness, Verizon was the worst. AT&T was more like benignly evil - they'd have been more evil, but it would have taken too much effort and anyhow they already had the DeathStar logo so it would have been redundant.
Still, we're talking semi-custom phones. Does the T-Mobile version of the M8 have LTE 700? Not sure, but I'd guess just as little as the AT&T version has WiFi calling. (This stuff matters to me; I'd really rather have a Sony Z1 Compact - more form-factor friendly to my size - but no LTE 700 and no Wi-Fi calling.)
Good to know that rooting probably won't block OTA. Thanks

Wotta said:
"No place" is a bit harsh, but I will forgive you the hyperbole for the sake of creative, if vapid, license. Largely I agree.
Click to expand...
Click to collapse
I did explicitly say in my opinion OTA has no place on modded phones. I strongly believe this, although it doesn't mean that others are completely entitled to have a different opinion
I don't see my phrasing as "harsh" but I meant it to be interchangeable with "In my opinion OTAs do not belong on modded phones" if that makes you feel better. After 4 HTC devices, the number of times I've installed OTA, or even felt the desire to . . . ZERO.

Related

what does "locked bootloader" mean?

What's up guys
I'm considering getting an Atrix when it eventually hits Europe, but people always talk about Motorola's locked bootloader. What does that actually mean? Does it mean custom ROMs are impossible? I love the look of this phone but I'd like to be able to modify it if I can't live with the supposedly-awful Motoblur.
Thanks for reading,
jennan
jennan88 said:
What's up guys
I'm considering getting an Atrix when it eventually hits Europe, but people always talk about Motorola's locked bootloader. What does that actually mean? Does it mean custom ROMs are impossible? I love the look of this phone but I'd like to be able to modify it if I can't live with the supposedly-awful Motoblur.
Thanks for reading,
jennan
Click to expand...
Click to collapse
please search forums before starting new topics
this question and discussion is in almost every topic under atrix in all categories and is cluttering up badly
http://forum.xda-developers.com/showthread.php?t=957461
But this thread is straight forward and good for noobs.
Sent from my MSM using XDA App
IN SHORT.
It pretty much means you can't change the KERNEL .. which means you're limited to customization to the phone. (e.g. No cyanogenmod, No MIUI, no community upgrades to gingerbread or honeycomb etc., no custom ditbits that only a kernel can provide).
/end.
darkamikaze said:
IN SHORT.
It pretty much means you can't change the KERNEL .. which means you're limited to customization to the phone. (e.g. No cyanogenmod, No MIUI, no community upgrades to gingerbread or honeycomb etc., no custom ditbits that only a kernel can provide).
/end.
Click to expand...
Click to collapse
Locked you can, encrypted you can't. All phones come locked bootloader. So we are praying that its locked and not encryped although it will likely be encrypted
Sent from my MSM using XDA App
Why would they do this?
Surely they know most users will want this feature... Once they save sold it, what it is to them..?
Maybe I'm missing something here?
EDIT: Posted this on the wrong thread. Please delete.
BoogWeed said:
Why would they do this?
Surely they know most users will want this feature... Once they save sold it, what it is to them..?
Maybe I'm missing something here?
Click to expand...
Click to collapse
Wrong. Few users even know about locked/encrypted bootloaders. We are a very small minority who cares about this issue.
One thing you'll note if you look around the forums are people still using older model phones like the 8525 which have lost support from the manufacturer a long time ago. Keeping legacy hardware current is costly to manufacturers due to development costs and from competitors releasing newer model phones. Look at what happened to Motorola when they clung to the Razr. They have to keep up with the others. Every sale lost is a potential profit gain for the competition. So they always have a "newer/better model" right around the corner. Keeping their boot loaders encrypted is an attempt at forcing the user to upgrade by limiting the amount of development required to keep the phone current. Even though we are a minority, we are still viewed as lost profit if we are still staying attached to our old phones when newer models are released.

Is it just me, or is the development section for this phone a ghost town?

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.

FYI anyone with a Dev Edition GS4

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 $.

[Q] Go back to complete stock

Hello,
I've seen some threads on rollbacks but want to be sure I'm doing it right since I'm on an old version.
I have a Apollo 8.9. I can't even remember all the steps I took to get Google apps, but I know I'm on 3.2.5 and have the HDXposed module installed to block updates etc. I'm on Safestrap v 3.75. All I want to do is get back to factory stock latest version so I can sell this. I don't care about getting root again or custom ROMs.
Any help is appreciated. Thanks!
Tim
Imo, it would be easier to sell as is. Many people want the flexibility that your device has. The ability to have a wonderful screen and be able to put one of many roms on it.
lekofraggle said:
Imo, it would be easier to sell as is. Many people want the flexibility that your device has. The ability to have a wonderful screen and be able to put one of many roms on it.
Click to expand...
Click to collapse
Agreed. Clearly state the firmware version and indicate the bootloader can be unlocked. Knowledgeable buyers will recognize what this means and may be willing to pay for this capability. Where to sell it and a fair asking price are unknowns (at least to me).
Ironically, market value may be reduced somewhat by a flurry of recent tool/rom releases that work on rooted HDX devices regardless of firmware level as it opens the door for many users who were previously shut out - unless they had a device like yours.
Attempting to restore you device to 'factory defaults' introduces risks that could yield a brick. Best not mess with it unless you are willing to assume those risks.

What a kick in the teeth! No marshmallow for Z3v.

http://blogs.sonymobile.com/2015/10/06/sony-xperia-and-android-6-0-marshmallow/ don't see the Z3v in the short list.
Why not the Z3v too?
1linuxfreak said:
http://blogs.sonymobile.com/2015/10/06/sony-xperia-and-android-6-0-marshmallow/ don't see the Z3v in the short list.
Why not the Z3v too?
Click to expand...
Click to collapse
If we can't even get lollipop, why on earth would you expect marshmallow? Not trying to be rude, I'm just trying to be realistic.
mrrodgersss said:
If we can't even get lollipop, why on earth would you expect marshmallow? Not trying to be rude, I'm just trying to be realistic.
Click to expand...
Click to collapse
Agreed this 509 firmware is stagefright patched and was built like 5 weeks ago and its 5.0.2 I think this is all were getting and since the Z4v is no longer coming out I belive 5.0.2 is the end of the road for the Z3v. This 509 firmware is good though.
I can understand your frustration, but I wouldn't take it for 100% that Sony is intentionally excluding the Z3V... They will probably send the marshmallow firmware to Verizon, and because of that, we'll probably never receive it unless we get a lucky leak, but I doubt that because I don't think it'll even be a candidate for Internal Testing as I'm sure Verizon plans to push Lollipop, fulfill their year old promises, and be done with their EOL device.. so even if Sony does send them the firmware, Verizon is most likely going to sit on it until it's buried... But you have to think with articles like these, even if they are press statements from Sony, it's still likely that they could leave out the Z3V unintentionally because even though its a variant of the Z3, by saying the Z3 is getting the update, they could be collectively including the Z3V along with that... but either way, I agree that we'll most likely never get this update, and that sucks.... But I do think Verizon is going to give us the latest Lollipop for sure.... There's no reason not to jump it to 5.1.1 if Sony gave them the firmware, it's not a major update... I think they just wanted a solid Lollipop build in "testing" (an intentional leak out there to collect usage stats from people bold enough to flash it) with stagefright patches, etc to make sure they had a solid build before putting the finishing touches on the firmware. There is a different Kernel in the .509 version than the .485, as well as some other interesting differences that make me think they're gearing it for the latest Lolllipop... and really as long as we get that with working VOLTE.... I can be happy enough with that.
zachariahpope said:
I can understand your frustration, but I wouldn't take it for 100% that Sony is intentionally excluding the Z3V... They will probably send the marshmallow firmware to Verizon, and because of that, we'll probably never receive it unless we get a lucky leak, but I doubt that because I don't think it'll even be a candidate for Internal Testing as I'm sure Verizon plans to push Lollipop, fulfill their year old promises, and be done with their EOL device.. so even if Sony does send them the firmware, Verizon is most likely going to sit on it until it's buried... But you have to think with articles like these, even if they are press statements from Sony, it's still likely that they could leave out the Z3V unintentionally because even though its a variant of the Z3, by saying the Z3 is getting the update, they could be collectively including the Z3V along with that... but either way, I agree that we'll most likely never get this update, and that sucks.... But I do think Verizon is going to give us the latest Lollipop for sure.... There's no reason not to jump it to 5.1.1 if Sony gave them the firmware, it's not a major update... I think they just wanted a solid Lollipop build in "testing" (an intentional leak out there to collect usage stats from people bold enough to flash it) with stagefright patches, etc to make sure they had a solid build before putting the finishing touches on the firmware. There is a different Kernel in the .509 version than the .485, as well as some other interesting differences that make me think they're gearing it for the latest Lolllipop... and really as long as we get that with working VOLTE.... I can be happy enough with that.
Click to expand...
Click to collapse
the thought did cross my mind that they would update 509 the rest of the way to 5.1.1 now that stagefright patch is out for z3 5.1.1 because it may be bad for business to have us on firmware we shouldn't have. I don't even care really Verizon made me sick with this shiit I guess I have to get a nexus phone next but I'm not doing that till they firgure out how to but an SD card in a phone. And thank you for your work and getting the ball rolling on Lollipop.
Tigerhoods said:
the thought did cross my mind that they would update 509 the rest of the way to 5.1.1 now that stagefright patch is out for z3 5.1.1 because it may be bad for business to have us on firmware we shouldn't have. I don't even care really Verizon made me sick with this shiit I guess I have to get a nexus phone next but I'm not doing that till they firgure out how to but an SD card in a phone. And thank you for your work and getting the ball rolling on Lollipop.
Click to expand...
Click to collapse
Thanks so much for the recognition. Somehow my leaked FTF of Lollipop was taken down, so I wasn't even sure if people still knew that I was the one that brought us that first Lollipop leak. I'm going to build us an amazing rom too.. I'm just waiting on Verizon to push their official build so that I won't be wasting my time building an outdated rom lol... U know like last time :/
zachariahpope said:
Thanks so much for the recognition. Somehow my leaked FTF of Lollipop was taken down, so I wasn't even sure if people still knew that I was the one that brought us that first Lollipop leak. I'm going to build us an amazing rom too.. I'm just waiting on Verizon to push their official build so that I won't be wasting my time building an outdated rom lol... U know like last time :/
Click to expand...
Click to collapse
you know are phones should be pretty close to being able to be unlocked by Verizon I was looking on eBay and there are unlocked Z3V's I dont know if they kept the drm keys but anyway once they release the final version..and we get our bootloader unlocked then we can go crazy. (edit)Unless that's a carrier unlock Im not sure if that unlocks the bootloader or if their the same.
zachariahpope said:
I can understand your frustration, but I wouldn't take it for 100% that Sony is intentionally excluding the Z3V... They will probably send the marshmallow firmware to Verizon, and because of that, we'll probably never receive it unless we get a lucky leak, but I doubt that because I don't think it'll even be a candidate for Internal Testing as I'm sure Verizon plans to push Lollipop, fulfill their year old promises, and be done with their EOL device.. so even if Sony does send them the firmware, Verizon is most likely going to sit on it until it's buried... But you have to think with articles like these, even if they are press statements from Sony, it's still likely that they could leave out the Z3V unintentionally because even though its a variant of the Z3, by saying the Z3 is getting the update, they could be collectively including the Z3V along with that... but either way, I agree that we'll most likely never get this update, and that sucks.... But I do think Verizon is going to give us the latest Lollipop for sure.... There's no reason not to jump it to 5.1.1 if Sony gave them the firmware, it's not a major update... I think they just wanted a solid Lollipop build in "testing" (an intentional leak out there to collect usage stats from people bold enough to flash it) with stagefright patches, etc to make sure they had a solid build before putting the finishing touches on the firmware. There is a different Kernel in the .509 version than the .485, as well as some other interesting differences that make me think they're gearing it for the latest Lolllipop... and really as long as we get that with working VOLTE.... I can be happy enough with that.
Click to expand...
Click to collapse
FWIW VoLTE is working, for me at least, on .509 so I think we're getting really close to the official release.
BladeRunner said:
FWIW VoLTE is working, for me at least, on .509 so I think we're getting really close to the official release.
Click to expand...
Click to collapse
while your here are you rooted and have you deleted any system apps I'm curious...I know you had advanced calling before on your plan so that part makes sense.
Tigerhoods said:
while your here are you rooted and have you deleted any system apps I'm curious...I know you had advanced calling before on your plan so that part makes sense.
Click to expand...
Click to collapse
rooted yes, froze a few apps, mostly vzw with tibu but nothing deleted.
---------- Post added at 07:38 PM ---------- Previous post was at 07:36 PM ----------
Tigerhoods said:
you know are phones should be pretty close to being able to be unlocked by Verizon I was looking on eBay and there are unlocked Z3V's I dont know if they kept the drm keys but anyway once they release the final version..and we get our bootloader unlocked then we can go crazy. (edit)Unless that's a carrier unlock Im not sure if that unlocks the bootloader or if their the same.
Click to expand...
Click to collapse
I think they mean carrier unlocked, which all vzw phones are now, since like the Galaxy S4. Boot loader and carrier unlock are two completely different things.
mrrodgersss said:
If we can't even get lollipop, why on earth would you expect marshmallow? Not trying to be rude, I'm just trying to be realistic.
Click to expand...
Click to collapse
my girlfriends droid turbo just received android 5.1 -
It was written on September 1st one day after ours was (509)-5.0.2 so maybe........ Soon or not it's Verizon.
http://phandroid.com/2015/10/07/sony-xperia-marshmallow-beta/ So the Z3 and Z3 compact are getting beta testing already.
Maybe leaked Marshmallow FTF for the Z3v soon.
mrrodgersss said:
If we can't even get lollipop, why on earth would you expect marshmallow? Not trying to be rude, I'm just trying to be realistic.
Click to expand...
Click to collapse
Just though all the kids on here would like to know that there is a 6.0 release over the 5.1.1, after all numbers mean so much on this forum.
:good:
Didn't mean to kill the thunder of the leaked beta Lollipop.
1linuxfreak said:
Just though all the kids on here would like to know that there is a 6.0 release over the 5.1.1, after all numbers mean so much on this forum.
:good:
Didn't mean to kill the thunder of the leaked beta Lollipop.
Click to expand...
Click to collapse
I wasn't trying to be rude either I have had this phone for almost a year since it first came out and have received no support for this phone at all I have spent literally hundreds of hours trying to fix this phone myself because verzions incompetence I'm not sure for the reason for the leak or how it happened but I doubt very much we will receive 6.0 and I don't really give a **** I would just like them to realease a Lollipop version so I can have a feature I was promised a year ago -advanced calling. Also quick charge 2.0 is a listed feature- it's not. Verizon = Liars. Look at the Z4v that's a disaster to.
Tigerhoods said:
I wasn't trying to be rude either I have had this phone for almost a year since it first came out and have received no support for this phone at all I have spent literally hundreds of hours trying to fix this phone myself because verzions incompetence I'm not sure for the reason for the leak or how it happened but I doubt very much we will receive 6.0 and I don't really give a **** I would just like them to realease a Lollipop version so I can have a feature I was promised a year ago -advanced calling. Also quick charge 2.0 is a listed feature- it's not. Verizon = Liars. Look at the Z4v that's a disaster to.
Click to expand...
Click to collapse
I am pretty tough skinned, it takes more than what you said to be considered "rude" to me.
I agree B.S. what VZW has done with the Advanced Calling 1.0, I am tired of getting the stepchild phones and VZW keeping us from getting the next OS release due to heavy-handed control. I mean Z3 getting a beta test for Marshmallow, seriously? Maybe the guy who got the leak can get Marshmallow leak, but I would like to have the latest OS if possible and I am sure others will agree.
An AOSP with a unlocked bootloader, I miss those days.
Is this bogus?
Hi I'm new to xda developers forum. Is this site BS that claims to offer a 6.0 rom for Z3v?
Since I'm new, I'm not allowed to share the link but it's from
android-xda.net
Marea01 said:
Hi I'm new to xda developers forum. Is this site BS that claims to offer a 6.0 rom for Z3v?
Since I'm new, I'm not allowed to share the link but it's from
android-xda.net
Click to expand...
Click to collapse
If it was real we would have heard about it. If it is still wait until it shows up here on XDA.
Marea01 said:
Hi I'm new to xda developers forum. Is this site BS that claims to offer a 6.0 rom for Z3v?
Since I'm new, I'm not allowed to share the link but it's from
android-xda.net
Click to expand...
Click to collapse
It is fake
Man it was so great to have the Droid when it first came out. ROM competition was tremendous and you could lead anything you wanted; if you could dream it, someone was already working on it.
I have 4 of those beauts!
AddictedToGlass said:
Man it was so great to have the Droid when it first came out. ROM competition was tremendous and you could lead anything you wanted; if you could dream it, someone was already working on it.
I have 4 of those beauts!
Click to expand...
Click to collapse
I have a similar experience. My last phone was a Galaxy Nexus, it was an embarrassment of riches as far as being able to modify it. Different ROMs everywhere you looked, modified kernels, etc... Thanks to baldwinguy77 I was running KitKat 3 days after Google introduced it, even before any manufacturers had released phones with it.
The Xperia's lack of popularity with the general public is probably the cause of it's noticeable lack of developer interest. Few devs have one so few work on it.
I really like the phone, it's battery life is second to none. I may have to be satisfied running Lollipop but at least it is rooted so there's that.

Categories

Resources