Related
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
Hey guys, i'm going to copy/paste my post from Tom's Hardware (I felt this may be a better place for the question):
Alright, so, i've been all over google the last two days and I just can't seem to find the right person/post having the exact same problem I am so I figured I'd ask myself.
So, as part as my effort to complete one of the various project I have going on around the house, I rooted and flashed custom recovery on my HTC One m9. Then, I flashed skydragon 10 onto it. This part seems to be fine and dandy.
But I just realized that I have ZERO Sprint software or options on my phone. As in, I can't update my profile and prl (the option is gone), I have no operator or mobile data, and my sim card appears to not be recognized as a Sprint SIM. How do I return those options and my phone's "identity"?
I tried various MMI codes to try and update PRL or somehow get my sprint profile back, but it just says "phone connection error or invalid MMI code". Of course, I assume I'm using MMI codes since that's what my phone's calling them (##72786# or something or other). But, right now, I don't really trust my phone.
As far as first experiences go with ROM flashing, this part has been a nightmare. It's like my phone is having an identity crisis and doesn't know that it's Sprint. I feel like shaking it and screaming "Damn it, Carl, you're not a tablet! You're a Sprint Phone!".
I literally feel 2 steps away from a solution, but I feel like I forgot to do something after flashing the ROM.
Here's what I know so far:
All my settings appear correct (APN, Phone Identity, Software Information)
If I search for Network Operators, Sprint comes up (there are 3 more with X's on them, assuming because it's not carrier-unlocked), but when I try to register, it just says the SIM is not a Sprint SIM i.e. my phone has lost it's identity.
As I'm certain you realize, I don't know much at this point. I saw a lot of answers and jargon and I know what it all means, I just don't know what to apply to my problem specifically. I haven't tried much beyond messing with settings since I'm trying to be cautious., but gosh darn (substitute the appropriate swear).
As far as backups go, I have none. I didn't realize that you could back up the stock ROM (not a single one of many guides mentioned nandroid, which I thought was the android folder misspelled, nor an EFS backup, which I thankfully, don't need... hopefully)
UPDATE: So, my phone keeps the annoying as 2am alarm I'm too lazy to get rid of, but ditches it's wireless carrier. Some priorities...
ACTUAL UPDATE: I'm going to call Sprint and see if I can have my SIM reactivated. First solution I've found that makes a little sense. Will post update later.
the_lost_dev said:
Hey guys, i'm going to copy/paste my post from Tom's Hardware (I felt this may be a better place for the question):
Alright, so, i've been all over google the last two days and I just can't seem to find the right person/post having the exact same problem I am so I figured I'd ask myself.
So, as part as my effort to complete one of the various project I have going on around the house, I rooted and flashed custom recovery on my HTC One m9. Then, I flashed skydragon 10 onto it. This part seems to be fine and dandy.
But I just realized that I have ZERO Sprint software or options on my phone. As in, I can't update my profile and prl (the option is gone), I have no operator or mobile data, and my sim card appears to not be recognized as a Sprint SIM. How do I return those options and my phone's "identity"?
I tried various MMI codes to try and update PRL or somehow get my sprint profile back, but it just says "phone connection error or invalid MMI code". Of course, I assume I'm using MMI codes since that's what my phone's calling them (##72786# or something or other). But, right now, I don't really trust my phone.
As far as first experiences go with ROM flashing, this part has been a nightmare. It's like my phone is having an identity crisis and doesn't know that it's Sprint. I feel like shaking it and screaming "Damn it, Carl, you're not a tablet! You're a Sprint Phone!".
I literally feel 2 steps away from a solution, but I feel like I forgot to do something after flashing the ROM.
Here's what I know so far:
All my settings appear correct (APN, Phone Identity, Software Information)
If I search for Network Operators, Sprint comes up (there are 3 more with X's on them, assuming because it's not carrier-unlocked), but when I try to register, it just says the SIM is not a Sprint SIM i.e. my phone has lost it's identity.
As I'm certain you realize, I don't know much at this point. I saw a lot of answers and jargon and I know what it all means, I just don't know what to apply to my problem specifically. I haven't tried much beyond messing with settings since I'm trying to be cautious., but gosh darn (substitute the appropriate swear).
As far as backups go, I have none. I didn't realize that you could back up the stock ROM (not a single one of many guides mentioned nandroid, which I thought was the android folder misspelled, nor an EFS backup, which I thankfully, don't need... hopefully)
UPDATE: So, my phone keeps the annoying as 2am alarm I'm too lazy to get rid of, but ditches it's wireless carrier. Some priorities...
ACTUAL UPDATE: I'm going to call Sprint and see if I can have my SIM reactivated. First solution I've found that makes a little sense. Will post update later.
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
Do you own the Sprint One M9 or the International one?
___
v7
XDA Assist
The Sprint version.
the_lost_dev said:
The Sprint version.
Click to expand...
Click to collapse
Moving your thread to Sprint HTC M9 Q&A,Help and Troubleshooting
Skydragon is for the international HTC M9.You can find the development for your device in Sprint HTC M9 Android Development.Reflashing stock or any compatible ROMs should solve the issue.
___
v7
XDA Assist
Are you serious? That's it? But... I just got to like skydragon... Ah well. Here I was thinking it had to do with flashing the radio's firmware. So glad I didn't do anything like that. Thanks for you help!
I bought my phone on Amazon, refurbished. It was in great condition physically, and using it for a month or few it's working fine... But I'm starting to want to do the XDA thing and have forgotten the fact I'm not sure what phone I bought. Online when I bought it, I believe it was sold to me as a GM1910... This was confusingly perplexed further when I looked in the about section and found it to claim 2 other versions in different places... It said GM1915 in one area, and GM1917 in another... But did claim GM1910 at least somewhere... Until...
After the OS had it's update OTA, this got more fishy; now no longer claims GM1910, but claims both of the other versions. So I'm under the impression that perhaps other software was loaded onto it, other than what was on the hardware initially... But I seem to not know truly what version of hardware I'm in possession of...
Is there any way to tell for sure what hardware and radio I'm in possession of, and whether or not it's normal to have conflicting or even changing model numbers on the about screen. I've tried going into recovery, but that's bare of any model; unless I'm missing the snake biting me... Anyone have tips?
Best option is to obtain the IMEI and check it online. Hopefully that can give you the answer you are looking for
MemoryThief said:
I bought my phone on Amazon, refurbished. It was in great condition physically, and using it for a month or few it's working fine... But I'm starting to want to do the XDA thing and have forgotten the fact I'm not sure what phone I bought. Online when I bought it, I believe it was sold to me as a GM1910... This was confusingly perplexed further when I looked in the about section and found it to claim 2 other versions in different places... It said GM1915 in one area, and GM1917 in another... But did claim GM1910 at least somewhere... Until...
After the OS had it's update OTA, this got more fishy; now no longer claims GM1910, but claims both of the other versions. So I'm under the impression that perhaps other software was loaded onto it, other than what was on the hardware initially... But I seem to not know truly what version of hardware I'm in possession of...
Is there any way to tell for sure what hardware and radio I'm in possession of, and whether or not it's normal to have conflicting or even changing model numbers on the about screen. I've tried going into recovery, but that's bare of any model; unless I'm missing the snake biting me... Anyone have tips?
Click to expand...
Click to collapse
My device reads 1917 in About Phone, and both 1915 and 1917 in Regulatory Labels. Got it straight from OnePlus.
Cbro0345 said:
Best option is to obtain the IMEI and check it online. Hopefully that can give you the answer you are looking for
Click to expand...
Click to collapse
phr0zen said:
My device reads 1917 in About Phone, and both 1915 and 1917 in Regulatory Labels. Got it straight from OnePlus.
Click to expand...
Click to collapse
Thanks for the effort thus far; I had done the IMEI on the official site, however it doesn't claim is any particular model, only that it's a pro7. Unless I'm being blind, which as frantic and I may have looked could be it... If you know otherwise, of love to be wrong here...
And I actually do feel somewhat better knowing my phone isn't the only one telling me conflicting information... But you never mentioned what model you figured you had though.... I'm hoping to assume you're certain that you bought a 1917 from the source? Perhaps the radio is the same?
That's really what I'm after, I want to know the bands that I am able to use, and whether I have band 71 [I think that what I'm after, the lowest freq tmo band]. Perhaps to add fuel to the fire, is anyone aware if we can flash the firmware of other models radios? I'm also curious to whether I'm able to get CDMA on my phone...
Right, so something I forgot to mention was before that update, I did have 2 iemi numbers, now I've only one... Furthermore, in bootloader there happens to be nothing in the fields that read: bootloader ver, baseband ver. This highly troubles me.
Sent from my OnePlus 7 Pro using XDA Labs
MemoryThief said:
Thanks for the effort thus far; I had done the IMEI on the official site, however it doesn't claim is any particular model, only that it's a pro7. Unless I'm being blind, which as frantic and I may have looked could be it... If you know otherwise, of love to be wrong here...
And I actually do feel somewhat better knowing my phone isn't the only one telling me conflicting information... But you never mentioned what model you figured you had though.... I'm hoping to assume you're certain that you bought a 1917 from the source? Perhaps the radio is the same?
That's really what I'm after, I want to know the bands that I am able to use, and whether I have band 71 [I think that what I'm after, the lowest freq tmo band]. Perhaps to add fuel to the fire, is anyone aware if we can flash the firmware of other models radios? I'm also curious to whether I'm able to get CDMA on my phone...
Right, so something I forgot to mention was before that update, I did have 2 iemi numbers, now I've only one... Furthermore, in bootloader there happens to be nothing in the fields that read: bootloader ver, baseband ver. This highly troubles me.
Click to expand...
Click to collapse
Ignore that, thought the OnePlus account would have told you further info but it doesn't. I'm not sure how you would go about finding the official number
Cbro0345 said:
Have you created a OnePlus account? I think you can attach th IMEI to a OnePlus account and view further info
Click to expand...
Click to collapse
Yes, I've done this so far as I can tell looking in every nook'n'crany I could, nothing about anything model number, just the model. I know it's a7pro, I am certain based on design and the pop-up camera... But if you can find a model number on that site easily, I will admit social defeat.
Cbro0345 said:
Ignore that, thought the OnePlus account would have told you further info but it doesn't. I'm not sure how you would go about finding the official number
Click to expand...
Click to collapse
Lol, no worries; I'll be the first to admit that the fact I don't know this, and the fact it's not easily discernable is pretty unbelievable... I would question the amount of lost marbles someone lost until I went proving otherwise as well; but perhaps you can quell another suspicion.
Would you check your bootloader to see about whether you have values at the aforementioned versions?
Sent from my OnePlus 7 Pro using XDA Labs
Last thing I can think of is to download AIDA64 and check what model shows there
Hello anyone. I normally lurk until I can lurk no more, but I'm struggling. I've tried to install every rom I could find, and can't seem to get any to boot. Everything either fails on crashdump during flash (repeatedly), or reboots right back into the fastboot/bootloader menu. I've had to MSM repeatedly, and even that kept failing until I realized I had the wrong version because there is one for Visible specifically (even though Visible and Global are both IN2015).
Main point: Is anybody else using the Visible variant of the Oneplus 8 and able to change roms? I despise stock roms with a passion and don't even want to start the setup process if I can get onto a custom rom instead. So if anybody has advice, I'd certainly take it, but I'm really just asking for the sake of seeing if there's anybody else that has succeeded. If so, I can go off and figure out where I keep screwing it up.
Thanks in advance!
Edit: I'm throwing in the towel. I feel like I've tried everything. Even when it looks like the ROM does finally successfully install, I just get stuck in an infinite "fastboot loop". If there's another Visible OP8 user that has managed to get a custom rom installed, please let me know!
Are you sure the Visible Oneplus is the IN2015? I'm fairly certain they are just using the Verizon 5G UW, which should be an IN2017. I doubt that Verizon or its mvnos are selling true dual sim phones (with dual imeis) even if its firmware locked.
Yeah, I'm fairly certain. It's definitely NOT dual SIM though, but the back is branded "ONEPLUS" (as opposed to "5G") and the volume buttons are higher than the ones that are moved down physically to accommodate for the mm antenna in the Verizon branded device.
The sticker on the back says IN2015, it shows up on Windows and Linux as IN2015. All of these bread crumbs lead me to believe it is a IN2015, except that no guides or outlines that I've followed for the IN2015 have worked, with the sole exception of using the MSM tool explicitly including the Visible firmware. That's what makes me think they have some slightly modified version of the IN2015 global, but haven't been able to track down specifics.
Thanks for the reply though! If there's any other information I can provide that may be helpful, I'll gladly oblige!
Edit: Attached image of the back sticker
Thought I would chime in. Visible's network is very different than you typically would expect. Even if you could flash ROMs, the likelihood of it working with Visible's network is nearly impossible. I was using a Pixel 3a XL when I had Visible. If I tried anything other than stock, it refused to connect. Heavy testing from various devs, and we never could figure out why. Ultimately gave up on it. The lack of ROM support on Visible is why I have T-Mobile now.
We (me and the wife) actually tried out T-mobile via their "Hotspot test drive" program and it just couldn't keep up with some of the "boonies" areas we frequent, so we opted for "big red" but with a cheaper access.
That's actually very helpful, because I was just thinking today that maybe I should have gotten a Pixel like the wife did. I'd be pretty disappointed to find the ROM installed but couldn't get connected (which would inevitably launch me down a wild goose chase of TWRPing modems and the like).
Both replies have been very helpful. Thank you for chiming in!
Edit: On a side note though, if there are any developers looking for a challenge and want to take on the mysterious world of Visible-compatible ROMs, you'd have at least one willing beta participant.
@stompysan How long ago were you trying custom roms with Visible? Apparently it was an issue at one point but has since been corrected? At least, that's what I gather from the discussion here.
Not that I'm trying to "gotcha," of course, but was just curious if you were on T-mobile for the past 12ish months and the problem has been corrected since you were playing with it before.
Edit: I've also dug up that it's becoming increasingly known/confirmed that Visible is rolling around with their own version of the Oneplus 8. Sort of like a hybrid between the global model IN2015, and their own build of it, as denoted by the IN68CE in the "build" section of About info.
I tried to flash stock global rom on visible and even that doesn't work. Got hardbricked to qualcomm crashdump. If anyone can flash global rom into Visible op8 please let me know. Thanks
Hoping for some good news too. I didn't realize dual sim doesn't work when I bought it on visible.
I gave up and got the 8 Pro instead. Still have my 8, but only for a little while longer. I'm going to sell it to offset the cost of the 8 Pro.
Hi I am trying to buy Oneplus 8 from Visible but doesn't intend to use it on Visible network infact i intened to use it on Tmobile network. So i was thinking of buying it from visible and flash Global Oxygen OS A11 on it and root. Use this on Tmobile network. Will this work?I mean can i flash Global Oxygen OS on it or does this had any different version similar to Tmobile branded phone.
deepu458 said:
Hi I am trying to buy Oneplus 8 from Visible but doesn't intend to use it on Visible network infact i intened to use it on Tmobile network. So i was thinking of buying it from visible and flash Global Oxygen OS A11 on it and root. Use this on Tmobile network. Will this work?I mean can i flash Global Oxygen OS on it or does this had any different version similar to Tmobile branded phone.
Click to expand...
Click to collapse
As far as I know, nope. You can root and it should connect to tmobile, but the Visible model seems to be stuck running their modified version which is on a dated version of Android 10.
RileyOsno said:
As far as I know, nope. You can root and it should connect to tmobile, but the Visible model seems to be stuck running their modified version which is on a dated version of Android 10.
Click to expand...
Click to collapse
Thanks that a deal breaker. I wish that wasn't the case. I thought it can be modified to global variant
I downloaded the original software and Troys rom in the SDcard. I made sure they are the right ones for my model, SM-N986U1.
I downloaded Odin to my desktop. I have also rooted twice before. But rooting seems a lot more complicated. I've read several rooting threads and it's confusing. It was hard before, but straight forward.
Please could someone walk me through the process? Or point me to a reliable paid service.
Lord Sekhmet said:
I downloaded the original software and Troys rom in the SDcard. I made sure they are the right ones for my model, SM-N986U1.
I downloaded Odin to my desktop. I have also rooted twice before. But rooting seems a lot more complicated. I've read several rooting threads and it's confusing. It was hard before, but straight forward.
Please could someone walk me through the process? Or point me to a reliable paid service.
Click to expand...
Click to collapse
There is none, anything above bootloader 1 can not be rooted, even with paid services
adj998 said:
There is none, anything above bootloader 1 can not be rooted, even with paid services
Click to expand...
Click to collapse
People have rooted the Note 20 and there are ROMs available. Please explain. Did I buy the wrong version of the Note 20?
There is a Snapdragon version and an Exynos version. This dichotomy has been around for a long time for Samsung phones. However, despite being unable to root consider yourself lucky as the Snapdragon has significantly better performance/battery efficiency than the Exynos variant.
Lord Sekhmet said:
People have rooted the Note 20 and there are ROMs available. Please explain. Did I buy the wrong version of the Note 20?
Click to expand...
Click to collapse
There's no easy answer to your question. As others have mentioned if your device came with a recent version of Android then reverting back to the previous bootloader (Ver 1) from the current updated one is next to impossible. I don't believe the paid services folks have been able to get around that either.
Now the Exynos version is a bit more flexible in this regard if you're able to get the right model but here's the conundrum- Since you a have a U1 device which is the U.S unlocked version I'm assuming you're located Stateside. This makes it really difficult to find an Exynos version which supports U.S bands and if you do you'll have to deal with lack of carrier aggregation and various other headaches. You could potentially look for a Honk Kong or another Asian Snapdragon variant but you'll circle right back to where you started from with the same bootloader issues you're currently facing. Dig through the various threads and ask questions there if you still want to pursue it further.
Sorry bud. Not the answers you were hoping for but I hope this helps!