Related
Since I heard motorola isn't going to unlock bootloaders I'm thinking of getting a different device. However if it is possible for a dev to get the job done I will gladly wait. So is it possible for a dev to crack this phone? Or rather must we wait for Motorola?
Sent from my MB865 using Tapatalk
Unfortunately we will have to wait for an unlocked version of the bootloader to be leaked, and or found through cheesecake. This is how the OG Atrix was unlocked. I have found a way to DOS the bootloader, but it will brick the device at the same time, so it is possible to overload the bootloader temporarily, but once the phone is booted, it corrupts the initrd boot image, so you can only run the changed kernel once. Until we can figure a more stable way to use that information, we will have to wait for the leaked version or cheesecake.
Heck why not get another phone and still hang on to this one to play with? That is what I am doing. I am also in the process of locating an LTE version of the galaxy nexus, to play with on ATT's network, so I will have both phones to play with.
jimbridgman said:
Unfortunately we will have to wait for an unlocked version of the bootloader to be leaked, and or found through cheesecake. This is how the OG Atrix was unlocked. I have found a way to DOS the bootloader, but it will brick the device at the same time, so it is possible to overload the bootloader temporarily, but once the phone is booted, it corrupts the initrd boot image, so you can only run the changed kernel once. Until we can figure a more stable way to use that information, we will have to wait for the leaked version or cheesecake.
Heck why not get another phone and still hang on to this one to play with? That is what I am doing. I am also in the process of locating an LTE version of the galaxy nexus, to play with on ATT's network, so I will have both phones to play with.
Click to expand...
Click to collapse
funds prevent me from buying another device. i think im still within my 30 days but the only phone better was the gs2 and they wouldnt let me get that one as my a2 was an exchange for my nexus s. they gave me 600 bucks credit and gs2 was 650 bucks. i suppose im stuck. i have 4 lines so ill have to wait for my upgrade. shoot by then att might have the galaxy nexus. well ill just sit back and have some fun with it and check for updates on cheesecake. this is such a great phone with SO much potential. i just dont like having to sit on stock for so long. i really enjoy flashing any rom i can and trying every devs work. i wonder if by moto saying they wouldnt unlock bootloaders that meant what we would find on cheesecake or official releases OTA.
What's going on, has Big Red forced a change in our devices? Coming from a DroidX, I'm getting scared.
I'm pretty sure the Verizon one didn't come out yet
Sent from my SPH-D710 using xda premium
Only a few of the verizon phones have actually gotten into people's hands. Once next week hits and everybody starts to get there preorders delivered then we'll see some major improvement
I got mine today and I'm too much of a rookie to try any methods out there... sort of disappointing. I really want Google Wallet.
Rooted mine with no problems.
http://forum.xda-developers.com/showthread.php?t=1762204
bootloader locked
evidently verizon is selling their s3 with a locked bootloader.
not impossible to root, just more of a pain in the a$$.
and they kepp pushing the date back
mas4489 said:
evidently verizon is selling their s3 with a locked bootloader.
not impossible to root, just more of a pain in the a$$.
and they kepp pushing the date back
Click to expand...
Click to collapse
You can root... Click the link in my sig for details!!
I spoke to a rep the other day regarding Jelly Bean. Long Story short he said it is rolling out to their systems now (computer support info) so we should have it very very VERY soon.
Sent from my SCH-I535 using Tapatalk 2
Your title gives the impression that it'll be JB
Edit : you edited your post.
Sent from my SCH-I535 using xda premium
blestsol said:
Your title gives the impression that it'll be JB
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
actually, it implies the opposite. his post in sort of confusing though.
hopefully a small update is making the phone ready for the update. anyone whos waited before trying jb will be happy!
First mistake is assuming the reps have a clue about what they are talking about. They are lucky to dress themselves for work every morning. If I had a nickel for every time a rep told me an update is coming, I'd be a thousandaire.
ddurandSGS3 said:
actually, it implies the opposite. his post in sort of confusing though.
hopefully a small update is making the phone ready for the update. anyone whos waited before trying jb will be happy!
Click to expand...
Click to collapse
I think when he says a small update he is describing his post as a small update to here. No the actually Verizon update.
Of course the next Verizon update will be JB. They do not need to make our phone ready for JB, it is ready and the leak we have also says it is pretty ready to go.....
Yes to Jellybean. Sorry for the confusion.
Sent from my SCH-I535 using Tapatalk 2
ddurandSGS3 said:
actually, it implies the opposite. his post in sort of confusing though.
hopefully a small update is making the phone ready for the update. anyone whos waited before trying jb will be happy!
Click to expand...
Click to collapse
I'm familiar with your posts in other threads. Carry on.
Sent from my SCH-I535 using xda premium
Never trust verizon reps....
I know a bunch of people who work for Verizon corporate.
I tell THEM when builds/phones are coming. I just updates their store model M to JB on Friday. They had no idea
Sent from my SCH-I535 using Tapatalk 2
Delete.
Sent from my Galaxy Nexus using xda app-developers app
The leak seems more stable than the ICS official to me...
I think these delays are more of a marketing strategy of sort rather than a real technical time to get it ready.... I might be wrong but...
Well VZW is going to have to do something either right before or same day the Note 2 comes out.
Sent from my SCH-I535 using Tapatalk 2
It seems more of a marketing strategy because t mobile released theirs after the note 2 was released.
Sent from my SCH-I535 using xda app-developers app
Verizon lies to there customers. When I bought the galaxy nexus I had 2 weeks to return the device. Signal was terrible but, loved the phone otherwise. I contaced them and they said and update when be comming out that would fix the problem but it would be after the 2 weeks of me being able to return the phone....no update acctually for several months then I was stuck with the useless phone.
Sent from my SCH-I535 using xda premium
Well that depends, what's their definition of "soon".
Terry_blair said:
Verizon lies to there customers. When I bought the galaxy nexus I had 2 weeks to return the device. Signal was terrible but, loved the phone otherwise. I contaced them and they said and update when be comming out that would fix the problem but it would be after the 2 weeks of me being able to return the phone....no update acctually for several months then I was stuck with the useless phone.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Same kind of thing happened to me. I wasn't getting an OTA even though one had come out. I went back to the store to exchange and he was like "it takes a while to get to everybody" so I went home and called Verizon and he advised me to go back and demand replacement.
I went back and demanded a new phone and he was like "fine I'll give you a new phone but the new one is going to do the same thing."
Well, he gives me a new phone, same sim card, and what do you know... first thing to pop up on the screen???
UPDATE AVAILABLE!
I laughed to his face and told him I would never be doing business with his store again.
Sent from my SCH-I535 using xda app-developers app
josh995 said:
Same kind of thing happened to me. I wasn't getting an OTA even though one had come out. I went back to the store to exchange and he was like "it takes a while to get to everybody" so I went home and called Verizon and he advised me to go back and demand replacement.
I went back and demanded a new phone and he was like "fine I'll give you a new phone but the new one is going to do the same thing."
Well, he gives me a new phone, same sim card, and what do you know... first thing to pop up on the screen???
UPDATE AVAILABLE!
Click to expand...
Click to collapse
Did you manually check for an update not long before you got the new phone?
From recent discussion, it seems there is a counter being kept for each account that notes when the last query for an OTA was made and it does not allow for a new check after a certain timeframe (seems anywhere from 2-4 weeks) after the most recent manual pull attempt. If your phone is not yet in the active queue for an active OTA push, the prior attempt will naturally return no new updates . . . but subsequent checks won't actually determine if you are in the OTA queue or not until the timeout period, even if your account was placed into the OTA queue by that time. My understanding is that this helps them balance load of the OTA downloads to some extent. Eventually, the OTA will be pushed to your phone, regardless of manual check attempts. It takes patience to wait.
However, this is bound to your account info, so changing a SIM card in the phone can make it seem as if the phone and/or SIM was the problem, because your prior, manual attempt was made when you were not yet in the active OTA queue, subsequent manual checks will not actually perform a check for the OTA for a period of time since the prior manual check - even if you were recently added into the active queue, and then a new SIM essentially resets the counter in your account and performs a true check for the OTA: if you were placed into the queue while unable to actually perform a check just before the new SIM, the OTA will now download and look like a miracle.
So, it does take patience. I experience the above symptoms exactly as described for the prior OTA and merely waited for the OTA to be pushed onto my phone - they gave me a timeframe for that and they were correct.
- ooofest
ooofest said:
Did you manually check for an update not long before you got the new phone?
From recent discussion, it seems there is a counter being kept for each account that notes when the last query for an OTA was made and it does not allow for a new check after a certain timeframe (seems anywhere from 2-4 weeks) after the most recent manual pull attempt. If your phone is not yet in the active queue for an active OTA push, the prior attempt will naturally return no new updates . . . but subsequent checks won't actually determine if you are in the OTA queue or not until the timeout period, even if your account was placed into the OTA queue by that time. My understanding is that this helps them balance load of the OTA downloads to some extent. Eventually, the OTA will be pushed to your phone, regardless of manual check attempts. It takes patience to wait.
However, this is bound to your account info, so changing a SIM card in the phone can make it seem as if the phone and/or SIM was the problem, because your prior, manual attempt was made when you were not yet in the active OTA queue, subsequent manual checks will not actually perform a check for the OTA for a period of time since the prior manual check - even if you were recently added into the active queue, and then a new SIM essentially resets the counter in your account and performs a true check for the OTA: if you were placed into the queue while unable to actually perform a check just before the new SIM, the OTA will now download and look like a miracle.
So, it does take patience. I experience the above symptoms exactly as described for the prior OTA and merely waited for the OTA to be pushed onto my phone - they gave me a timeframe for that and they were correct.
- ooofest
Click to expand...
Click to collapse
Well I had been manually checking for like a week, however, I wasn't receiving an update that had been out for months. The phone was 2 updates behind!
The new phone with my same SIM updated instantly after it was set up. I didn't even have to manually check. And then it updated again. So I honestly believe there was something wrong with the phone. Very strange to not get an update that had been out for months, you know?
Sent from my SCH-I535 using xda app-developers app
It does not change ver. from 4.1.2
what does this updatedo?
What does this update do? Does it affect my root? Thanks!
It is notifying me too. Since I have twrp and root on stock jelly bean, how can I update if helpful, or turn off update notification?
Chad
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
AFwarbird said:
It is notifying me too. Since I have twrp and root on stock jelly bean, how can I update if helpful, or turn off update notification?
Chad
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Started getting the notification yesterday, but I'm also on stock Jelly Bean 4.1.2 and TWRP. I was able to stop the notifications by freezing "AT&T Sofware Update" with Titanium Backup, but I'd also like to know if there's anything here worth the trouble of trying to get it installed.
I just had a chat session with a Samsung official, and she said it's news to them. I told her that I am on I727UCMC1, and she said that my device is up to date. The small update AT&T is pushing must be something to do with AT&T.
Unless it updates my camera features, I'm not even bothering with it, and will keep AT&T Update frozen.
I'm pretty sure I'd have to backup everything, revert to stock UCMC1, cross my fingers and toes that it still doesn't brick my phone, and hope it still can be rooted the way I did before.
It sure would be nice if there was some sort of explanation as to what is being updated. I have looked all over and not found anything anywhere else that mentions this update to I727UCNJ1. I got the number from this an at&t website I would post the link but can't. It is only 12mb so probably not worth a bunch of trouble but I wish I knew what it is trying to update.
Paranoid?
Me too. Mine is original stock, but I upgraded the Android OS last year to 4.1.2 via Samsung Kies. However, mine is unlocked, and I can't help but be suspicious that AT&T is "updating" to do something that is to their benefit and not ours (i.e. relocking the phone?, spyware, etc.?), so it would be nice to have some details of what/why this unexpected update, before blindly agreeing to it. So, if anyone know what this update is all about, please share with us. Thanks very much!
My money's on an update that locks the phone down. What else would AT&T possibly do with a three-year-old platform that isn't making them any new money at this point?
I chatted with an AT&T representative yesterday, and all I could get out of her was that the update had to do with new features to the O/S. That's all the information that she could find, and couldn't tell me any specifics about what features were being updated.
I am about to go to an S5 or S5 Active soon, and I might just revert to stock to check it out.
It's pretty fishy though that neither Samsung, or AT&T has, or wants to divulge in any, information on exactly what it's going to do.
---------- Post added at 07:29 PM ---------- Previous post was at 07:26 PM ----------
As far as it locking your device back down, I have yet to flash, or install anything that has re-locked my phone. I guess it's possible. The only thing I'm worried about is losing root, and not being able to get it back with the last way that's available.
I see it's now listed on the AT&T eSupport website No details, just "Android OS Enhancements".
I don't have enough posts on this forum to be permitted to publish a link, but you can find it by Googling "AT&T Update to Skyrocket", and the eSupport link should be near the top of the results.
AT&T is taking the same tack as Verizon, and locking everything down. Even the mid to low end phones. So, I wouldn't be surprised if this is a way to lock older phones.
On the other hand, it really may be final bug fixes - a sort of final service pack. I wish I trusted them to give it a try.
I reverted back to stock I727UCMC1 using Odin v1.85, updated OTA to I727UCNJ1, flashed TWRP custom recovery, got root back, but I am not sure if I am still unlocked or not. I tried *#7465625# on the dialer, but the code does nothing.
Anyone know of another code to check the unlock status?
Thanks very much for your feedback. I've always just put a SIM card from another carrier into my phone. Even if it is not an active SIM, your phone should still tell you whether or not it is locked.
24fan4life said:
I reverted back to stock I727UCMC1 using Odin v1.85, updated OTA to I727UCNJ1, flashed TWRP custom recovery, got root back, but I am not sure if I am still unlocked or not. I tried *#7465625# on the dialer, but the code does nothing.
Anyone know of another code to check the unlock status?
Click to expand...
Click to collapse
unless u restored a previous efs partition that was locked to a carrier then u will remain unlocked, afaik no one lost their unlocked sim by restoring or flashing any firmwares, to read more about the sim lock or to unlock the sim read this http://forum.xda-developers.com/showthread.php?t=2638037
as for firmwares locking down the phone its referring to the way root is acheived not to the sim carrier lock
T.J. Bender said:
My money's on an update that locks the phone down. What else would AT&T possibly do with a three-year-old platform that isn't making them any new money at this point?
Click to expand...
Click to collapse
i hope you are joking, because if not then then you're insane. no offense intended.
Not so insane, I'm afraid. AT&T has started a war on unlocked bootloaders lately. The CEO has officially come out as saying they don't want unlocked devices on their network, and have followed up by sending out OTA updates that lock down devices. Several devices started out unlocked, like the S2, and became locked by OTA updates. The S3, Note 2, etc.
IOW, I wouldn't put it past them, especially if Samsung wasn't aware of the update. On the flip side, the S2 is no longer even for sale, and I have to wonder how many are left in active service.
Clarification?
lingowistico said:
i hope you are joking, because if not then then you're insane. no offense intended.
Click to expand...
Click to collapse
Thanks, that was very helpful! Seriously though, as a senior member of this forum, perhaps you might have some constructive comments on this subject? After all, we're sitting here with phones (the I-727 SII Skyrocket is an oldie, but goodie!) that are trying to push an unanticipated OTA update on us, in a very suspicious manner. We hope it's just a bug fix, but don't trust the carrier (AT&T) to be doing this, unless they have some ulterior motive. The benefit of your substantial experience would be appreciated. Thanks in advance for any insight you can offer us.
Regards,
Ron M.
jshamlet said:
Not so insane, I'm afraid. AT&T has started a war on unlocked bootloaders lately. The CEO has officially come out as saying they don't want unlocked devices on their network, and have followed up by sending out OTA updates that lock down devices. Several devices started out unlocked, like the S2, and became locked by OTA updates. The S3, Note 2, etc.
IOW, I wouldn't put it past them, especially if Samsung wasn't aware of the update. On the flip side, the S2 is no longer even for sale, and I have to wonder how many are left in active service.
Click to expand...
Click to collapse
Thank you for your insight, it was TRULY helpful! As a relative newbie, I just want to clarify our terms. When you use the term "unlocked", I deduce you are referring to a phone that has been rooted and is running a different platform - is that correct? In my case, I am NOT rooted and simply running the original crappy stock platform, but my phone is "unlocked" in the traditional sense, in that I can use it with different sims from different carriers throughout the world, rather than being "locked" to AT&T. So, for those of us who are not as technically advanced, could you please clarify? For me, if this OTA update doesn't prevent me from continuing to use other sims from other carriers, then I don't know what the downside would be, unless they're just adding more spyware and bloatware to their already intrusive system? I look forward to your comments.
Regards,
Ron M.
jshamlet said:
Not so insane, I'm afraid. AT&T has started a war on unlocked bootloaders lately. The CEO has officially come out as saying they don't want unlocked devices on their network, and have followed up by sending out OTA updates that lock down devices.
Click to expand...
Click to collapse
I thought T.J. Bender was talking about simlock since he didn't mention the bootloader. :silly:
At&t sure isn't making life easy for you.. I'd still be proudly rocking a skyrocket too if I didn't lose it :angel:
I only messed with my Skyrocket for an hour or so after accepting the OTA update, before starting up my new S 5 Active.
The only thing that I really noticed, was they took the AT&T phone setup app off of it, since it is no longer in use by AT&T. There may have been more that I didn't notice, but only running it a couple hours, I couldn't tell. I even checked the camera thinking they might have finally snuck some new features into it, but no dice.
lingowistico said:
i hope you are joking, because if not then then you're insane. no offense intended.
Click to expand...
Click to collapse
How does suggesting that AT&T would lock a bootloader make me insane?
Sent from my totally badass HTC One m8 using Tapatalk
I (very) recently got a Verizon Galaxy S6 and (stupidly) allowed the updates to run :silly:. I should have known better, as I went through the unlocking/rooting process with Verizon's S3. I could live with it for a bit if people think it will be unlocked in the near future (I'm on VRU4BOG9), but if there's a reason that it's unlikely that it will ever be unlocked, I can still return it and cancel my plan. I could just change carriers, but it's a little tricky because it involves my wife's phone/line, as well.
Does anyone have any information or opinions regarding this?
Thanks!
I'm with you in the same boat.
It was past the baseband even before i let the updates run.
I doubt there will be anything. This forum is pretty dead. No developers etc. I am going to look into getting a tmobile s6 and see if I can unlock, root and get it working on verizon. I think it can be done I've just not looked into it yet so not for sure.
Sent from my SM-G920V using Tapatalk
Stagefright might allow root. I'm waiting to see.
redrol said:
Stagefright might allow root. I'm waiting to see.
Click to expand...
Click to collapse
Stagefright doesn't run at root level.
dobbs3x said:
I doubt there will be anything. This forum is pretty dead. No developers etc. I am going to look into getting a tmobile s6 and see if I can unlock, root and get it working on verizon. I think it can be done I've just not looked into it yet so not for sure.
Sent from my SM-G920V using Tapatalk
Click to expand...
Click to collapse
t-mo has CDMA radio?
or you plan to run LTE only?
i would be interested to find out as well
It's unlikely.. as some of the recent dev posts have made clear samsung is the ultimate anti-developer company... as such most of the dev's that would normally work on this have moved on to other brands. It's also gotten to the point that it's almost impossible to actually unlock.. they almost always work around it rather than unlock it, and there are only so many of these workarounds out there.
It may get rooted again, but it will be very unlikely that the bootloader gets unlocked.. basically our only hope would be a leaked test bootloader thats already unlocked.. But I've only ever heard of this happening once.
Take it back while you can. Had my s6 rooted on 5.0.2 but there was no xposed support or xposed for it. If you enjoy rooting your phone the outlook is not good. Not much going on with this scene. After owning mine for just 2 months I sold mine on eBay and am headed towards a nexus. Not a bad phone but not good for flashing...I will do my research next time before getting a Samsung !
sulpher said:
It's unlikely.. as some of the recent dev posts have made clear samsung is the ultimate anti-developer company....
Click to expand...
Click to collapse
It's not Samsung, IT'S Verizon that's locking Us out.
rbeavers said:
It's not Samsung, IT'S Verizon that's locking Us out.
Click to expand...
Click to collapse
It's Samsung that lets Verizon lock us out. They let companies throw their logo on it still so...
How about Chainfire
EXPERIMENT: Root without modifying /system (you can search for it here on XDA)
I hope it could actually work soon!
webwarr said:
How about Chainfire
EXPERIMENT: Root without modifying /system (you can search for it here on XDA)
I hope it could actually work soon!
Click to expand...
Click to collapse
Tried it, no go
Got it...
That's sad
Sent from my SM-G920V using XDA Free mobile app
Becoming less and less happy that I bought this phone. Especially on the payment plan. I may have to bite the bullet, pay it off and just sell it for whatever I can get. Sucks. I loved my fascinate, my S3, and my S4. Been using my Moto Maxx 2 more and more lately. THAT'S SAD.
Sent from my XT1565 using Tapatalk
Besides the Nexus what model phones are now dev friendly? I was looking at a G4 but apparently LG is just like Samsung with the nearly uncrackable locked bootloaders now.
s5 just got full bootloader unlock..
Is it Verizon or the Exynos chip that's holding back development on this device? ELI5
Sent from my XT1565 using Tapatalk
It's the customized software that samsung builds for Verizon that limits access to root and bootloader. Without having root privileges, you can not make any system changes let alone access it. The chip has nothing to do with this.
s5 just got bootloader unlock BUT the dev has not said he will release anything. It may never happen on this device. having said that the debloater is the key to a smooth device with good battery. If debloating is all you need, that can be done without root.
After debloating about 150 apps on my s6, I can get days and days on battery with minimal use.
This who ordeal with Samsung screwing us on the S6 is making me want to switch to a Nexus...