Related
Hey there remaining Verizon S3 users!
Coming from my favorite device the T959V this has been quite a trip. This device's bootloader is seemingly impossible to unlock on the 4.4.2 NE1 firmware.
I've got a slightly modified Superlite rom rolling with SafeStrap already strapped. And it is great to say the least. Added some initd and utilities. Evie launcher is pretty nice btw- recommend a try :good:
However. I still really want this thing to be unlocked. The T959V has multiple working Fro, GB, ICS, JB, KK, L, M, AND Nougat ROMS. Totally different devices yes but-- even the newer S4-S6 have cracked loaders now.
There has to be a special way to change this things firmware.
Right now I have 2 ideas to throw out to the wind-
1- Would be that there could be a way to trick the device into thinking it is receiving a new update. Maybe somehow with CSC or something. Also I saw a file named authorized.xml and was reading through to find traces of knox. Would unauthorizing knox strings somehow render it useless?
2- I was reading a suggested post about AVB boots and how they can be resigned on devices such as the Google Pixel and allows the newer patches to still install. Including what was described as a forced re-sign method.
--- Could we somehow resign the bootloader on our device so as to gain control of it? Has anybody tried anything like this since around 2015?
I'll gladly talk about all of this more whenever I feel like popping on- and atm I have no web besides this service. :silly: so no DOS updates and no shiny linux for now.
Gladly tell me that it is "impossible" but I'm not asking that. I'm trying to add some ideas to possibly do the impossible.
Edit: This seems to be an interesting lead on emmc cracking this device. It's probably why people in other threads were in search of a "dev" edition.
http://forum.gsmhosting.com/vbb/f777/unlock-samsung-devices-bootloader-emmc-backdoor-2142981/
graycow9 said:
Hey there remaining Verizon S3 users!
Coming from my favorite device the T959V this has been quite a trip. This device's bootloader is seemingly impossible to unlock on the 4.4.2 NE1 firmware.
I've got a slightly modified Superlite rom rolling with SafeStrap already strapped. And it is great to say the least. Added some initd and utilities. Evie launcher is pretty nice btw- recommend a try :good:
However. I still really want this thing to be unlocked. The T959V has multiple working Fro, GB, ICS, JB, KK, L, M, AND Nougat ROMS. Totally different devices yes but-- even the newer S4-S6 have cracked loaders now.
There has to be a special way to change this things firmware.
Right now I have 2 ideas to throw out to the wind-
1- Would be that there could be a way to trick the device into thinking it is receiving a new update. Maybe somehow with CSC or something. Also I saw a file named authorized.xml and was reading through to find traces of knox. Would unauthorizing knox strings somehow render it useless?
2- I was reading a suggested post about AVB boots and how they can be resigned on devices such as the Google Pixel and allows the newer patches to still install. Including what was described as a forced re-sign method.
--- Could we somehow resign the bootloader on our device so as to gain control of it? Has anybody tried anything like this since around 2015?
I'll gladly talk about all of this more whenever I feel like popping on- and atm I have no web besides this service. :silly: so no DOS updates and no shiny linux for now.
Gladly tell me that it is "impossible" but I'm not asking that. I'm trying to add some ideas to possibly do the impossible.
Edit: This seems to be an interesting lead on emmc cracking this device. It's probably why people in other threads were in search of a "dev" edition.
http://forum.gsmhosting.com/vbb/f777/unlock-samsung-devices-bootloader-emmc-backdoor-2142981/
Click to expand...
Click to collapse
I've been around this and many many other forums for years now. If there was an unlock method it would of been found years ago. Devs have long moved on from the old S3. I still have my S3 lying around, bootloader unlocked but I really haven't messed around with it for quite a long time now
And yes the dev edition would of been nice had someone actually had one, it would of of course made it easier to crack the bootloader option maybe. I don't know much about the ins and outs of the device but I know many are permanently locked and will probably never be unlocked.
As far as certain other Samsung devices being unlocked those are far and few between. VZW got smart and started just locking them from the start. This is a huge reason why I left Verizon. The S3 was my last device on big red. I since have had a Nexus 5 and 6 and now a oneplus 3t. I really don't like locked devices and the ability to unlock them and customize them just intrigues me to no end. Good luck however in finding something that may work, but I highly doubt it will ever be cracked
Sent from my OnePlus 3T
Ya I expected your negatude Shapes. Already seen that you have been searching but it isn't just some application you run. It's an unknown exploit that I'm sure exists. There are exploits right now that can be considered viral potentially exploiting my device as we speak. Maybe not granted my semi-precautious take on things.
Quadrooter and dirty cow could be used to exploit the S3 and gain access to a quoted "all" physical memory. So I find it hard to believe that things can't work in our favor.
Being open minded here. After all, this is technically hacking your own device. Which--
Got me thinking the other day, becausr I was setting up my laptop proper- could we run a nix distro and poke through the bootloader's parameters via exploitation tools? Referencing Kali or it's elder BTrack. But I think it is possible and I just haven't gotten around this loop mounting issue.
To be clear, running a distro ON the device. My flat is already running square.
Sent from my SCH-I535 using XDA-Developers Legacy app
Also a purposely separate post- I'm building a ROM for this locked firmware and the goal is to have some specific updated apps and yet trim it nicely so as to save space and RAM it's mostly stock style-wise but it'd be cool to re-theme it. I haven't gotten things deodexed yet- being I haven't gotten my apktools working proper yet.
Is there anybody left to be interested in this? I haven't posted anything I've made before- usually just keep them lying around for emergency flashes.
Sent from my SCH-I535 using XDA-Developers Legacy app
graycow9 said:
Ya I expected your negatude Shapes. Already seen that you have been searching but it isn't just some application you run. It's an unknown exploit that I'm sure exists. There are exploits right now that can be considered viral potentially exploiting my device as we speak. Maybe not granted my semi-precautious take on things.
Quadrooter and dirty cow could be used to exploit the S3 and gain access to a quoted "all" physical memory. So I find it hard to believe that things can't work in our favor.
Being open minded here. After all, this is technically hacking your own device. Which--
Got me thinking the other day, becausr I was setting up my laptop proper- could we run a nix distro and poke through the bootloader's parameters via exploitation tools? Referencing Kali or it's elder BTrack. But I think it is possible and I just haven't gotten around this loop mounting issue.
To be clear, running a distro ON the device. My flat is already running square.
Click to expand...
Click to collapse
I don't think shapes was trying to act negative at all, just stating the obvious. Nobody is going to try to unlock the Verizon S3, it's pretty much a dead end.
The unlock method used on the S5 will most likely work on this phone, but we need a developer CID to rewrite to the emmc as the series chip used on the S3 likely has the same vulnerability. This is what happened on the S5.
If you read some of the other posts (sounds like you have), we looked for an S3 developer edition but had no luck in tracking one down. For one, it's an incredibly old device. Secondly, you'd have to be semi retarded to purchase one as the original unlock method was around before the developer edition was released.
So yes, if you can find a developer S3 this will likely be an unlock method. It tricks the S3 into thinking it's a developer phone and unlocks the bootloader if the method to write it works the same as in the S5.
As for your questions,
1. I think you're underestimating the amount of security that goes into the bootloader itself. If you want to learn a lot about Android security in general, in the Android security discussion section located under general forums, there's tons of info regarding how complex this all is. But basically, in order to send an update patch, it needs to be signed (you can't just fake the signature) and it must agree with the current bootloader. The way the bootloader is written, it simply won't allow a reversion back to earlier versions or it'll abort the boot.
An easier way to think of this is understanding that the changes made are preinstalled before the actual boot. There's no way for us to change this through normal methods as the emmc has to be written to directly. There is no way to do this from download or recovery mode. Wouldn't matter if you flashed it or used and update package, they are essentially the same thing.
So the only way to actually change the bootloader is to write to the emmc directly through use of the JTAG port. This changes the code of the entire bootloader before the boot and the phone will boot up with any version of the S3 bootloader you write.
2. I think I kind of answered that?
Hope it's clear.
BadUsername said:
I don't think shapes was trying to act negative at all, just stating the obvious. Nobody is going to try to unlock the Verizon S3, it's pretty much a dead end.
The unlock method used on the S5 will most likely work on this phone, but we need a developer CID to rewrite to the emmc as the series chip used on the S3 likely has the same vulnerability. This is what happened on the S5.
If you read some of the other posts (sounds like you have), we looked for an S3 developer edition but had no luck in tracking one down. For one, it's an incredibly old device. Secondly, you'd have to be semi retarded to purchase one as the original unlock method was around before the developer edition was released.
So yes, if you can find a developer S3 this will likely be an unlock method. It tricks the S3 into thinking it's a developer phone and unlocks the bootloader if the method to write it works the same as in the S5.
As for your questions,
1. I think you're underestimating the amount of security that goes into the bootloader itself. If you want to learn a lot about Android security in general, in the Android security discussion section located under general forums, there's tons of info regarding how complex this all is. But basically, in order to send an update patch, it needs to be signed (you can't just fake the signature) and it must agree with the current bootloader. The way the bootloader is written, it simply won't allow a reversion back to earlier versions or it'll abort the boot.
An easier way to think of this is understanding that the changes made are preinstalled before the actual boot. There's no way for us to change this through normal methods as the emmc has to be written to directly. There is no way to do this from download or recovery mode. Wouldn't matter if you flashed it or used and update package, they are essentially the same thing.
So the only way to actually change the bootloader is to write to the emmc directly through use of the JTAG port. This changes the code of the entire bootloader before the boot and the phone will boot up with any version of the S3 bootloader you write.
2. I think I kind of answered that?
Hope it's clear.
Click to expand...
Click to collapse
Truthfully after being around the forums for as long as I have I'm really surprised there is any interest in unlocking this device at this point in time. There are just so many other options and unlocked vzw s3s are not that hard to come by.
And I wasn't being negative it's about being realistic. Thanks for sticking up for me brother
Sent from my OnePlus 3T
Are there any updates to this by any chance, I am interested :C
any hope?
I talked to Samsung for about an hour about why the bootloader is locked for the US versions of the S7.( I have a SM-G930R4) Most of the time they gave me the run around but I was able to find out that with the Oreo update ,it may be possible to lock/unlock the bootloader. They didn't come right out and say it but that's what it sounded like to me. They were saying something about a "security issue" that is supposed to be fixed in Oreo,and that it's within the realm of possibilities. Let's hope they weren't trying to make me feel better,lol. I haven't had a nice phone since 2013,and I was pretty nonplussed to find out we got shafted. I have been using Samsung phones since the original Google Nexus,and have flashed/rooted/customized every single one of them. Customization is important to a lot of people,and Samsung understands this. Why'd they have to give in this time? ><
Highly unlikely
Samsung talk out of their rears when you contact them, usually just to get you to go away I find
Well that's corporations in general right? Lol. I don't want to get another phone if I don't have to. I rather like this one. I guess we'll find out in the coming weeks ,eh?
I have a screenshot of part of the conversation,but it seems like I can't post the link or embed it. Basically it was them feeding me a line of garbage about none of their USA model phones having unlockable bootloaders,and I corrected them. They also said that it was Qualcomm's fault but I can't see how. Don't they use their own bootloaders?
I guess I could always try to trade my S7 for a S6 lol.
I don't know the details of why they are locked or who's fault it is, but they're right that none of the USA S7s have unlocked bootloaders (Snapdragon Models)
It's the Exynos International S7s that are unlocked (G930F, G930W8)
Samsung will have the bootloader encryption key, so they could have added a feature to unlock it like they did with the Exynos versions, no idea why they haven't
If you want an unlocked S7 I'd sell that one and get the G930F
They didn't say it would never be unlocked. What I got from the exchange was that it may happen during the next OTA,which I assume is Oreo,or a patch of sorts thereafter. The particular lady I was speaking to implied it was Qualcomm's fault,but I find that hard to believe. I brought up the fact that we're being singled out (for whatever reason) and that customization is quite important to a lot of us.She said "Yes I agree,if you buy a phone it should be yours" So hopefully they do the right thing. I can't very well just sell this phone ,however. It holds sentimental value and was a gift from someone very dear to me.So my only option is ,A) Pray Sammie does right by us,or B) wait until someone hacks it(if it's even possible)
Also from what I've been told and what I've read on multiple forums(XDADev included) our phone carriers pressured Samsung to do it,to cut down on people bricking their phones. From my experience it's pretty hard to completely brick a Samsung. As long as you can get into download mode and flash something via Odin or backup from recovery,it's all good.
I'm running oreo. But soon all carriers will now lock bootloaders latest sprint and Verizon starting , to make it it so no one can change carriers
Not to stir up an old thread, but oreo just rolled out for the sm-g930p yesterday and I noticed that there is the option for OEM unlock. Good news for finally unlocking the bootloader?
whbisondtr said:
Not to stir up an old thread, but oreo just rolled out for the sm-g930p yesterday and I noticed that there is the option for OEM unlock. Good news for finally unlocking the bootloader?
Click to expand...
Click to collapse
No.. That's not what that feature is for. It's in Nougat as well under development options
InsanePostman said:
No.. That's not what that feature is for. It's in Nougat as well under development options
Click to expand...
Click to collapse
Gotcha. I didn't have it on here with nougat though, it didn't show up until I got the oreo update. From what I've read around, that's what it was for.
whbisondtr said:
From what I've read around, that's what it was for.
Click to expand...
Click to collapse
Random thought...Maybe when the Oreo U firmware comes out flashing the BL will work?
SprintBama said:
Random thought...Maybe when the Oreo U firmware comes out flashing the BL will work?
Click to expand...
Click to collapse
When I talked to Samsung about it they hinted that would be the case. They didn't confirm or deny it directly,but the way they put it sure alluded to something of the sort.
lets pray ))
Yea so anyway still locked and I honestly don't even need root. I'll just use the unlocked firmware and disable bloat. Rooting the s7 seems arbitrary at this point. If I wanted to I would just trade my s7 USA varient for an international varient if I was really that adamant. S7's are pretty cheap now with the s8 and s9 out on the market.
I have an unlocked phone and the only thing unlocked is the carrier or sim, nothing to do with the bootloader unless you all are suggesting that after the full release of Oreo on all the s7 devices that they may rethink locked bootloader. By then I'll probably just get a new phone. I've lost interest in rooting the s7 but that's probably because there's only three ways around it. Rooting Android 6, rooting earlier versions of Android 7 or getting the xynos s7. I love Oreo more than root on this phone.
I mean this thing is a piece of junk, keys all over the place, I typo all the time from mismatched touches on the screen, it bug reports daily, it is slower than older phones, no bootloader, no root, I HATE LG and this piece of S###! I have contacted Sprint, LG, anyone I can, and LG doesnt care, they are the absolute worst company ever in existence of mobile phones. I CANNOT WAIT until they go bankrupt. This is the WORST DEVICE EVER IN HISTORY! I am SO upset with LG and Sprint and SO disappointed with LG mobile in general. I havent met one customer who is 100% satisfied with LG YET to date! They will soon become the next Blackberry, a distant bad memory but they dont have to be if they would just listen to us and unlock the damn bootloaders. THEN we can fix the issues ourselves and accept LG, not love LG, but at least not hate them. I would have AOSP on my device day 1, instead, I am stuck with this overbloated Sprint BS (yes I have Octoplus LG and can move to US-Open / non-branded) but then I run into CDMA issues with Sprint so I am stuck with a terrible device I wish I could toss. And Sprint actually ASKED me if I would be interested in purchasing the lease out and owning it (to get a new phone on a new lease), YEAH RIGHT, I am DONE with this piece of crap phone and Sprint! They can both bite me, Sprint overcharges now with hidden fees and terrible customer support, and LG just doesnt care, they dont give a hoot about the customer, once they get the money, you are a distant past memory (like they will soon be)!
I have had this phone since late September, and have never had the issues that you have. Yes, it does have its quirks, but nothing like you've described. Have you tried a factory reset to see if that fixes the issues?
Sent from my LM-G710VM using Tapatalk
Since I got mine, I have debloated what I can on the phone via application menu and adb.. It's ok, but would prefer having a unlocked bootloader, and root.
I am 100% satisfied, so I must be your first
Can you flash custom partitions with octopus box?
No!
Just use this beast with some nice headphones.
Go to compare with s10 or iPhone xs max screen. Max brightness on all, G7 wins!
Best screen, best Dac, best Amp, best camera software. Best USB-C 3.1 with 5Gbps, hdmi output. What else do you want? Updates? What for? Since Qualcomm introduced Trust Zone it's almost impossible to get hacked or root the phone. Software updates are just a gimmick.
Enjoy your phone. It's WONDERFUL! Trust me on this.
I wouldn't say I'm miserable with the phone but the lack of timely security updates and lack of update to Android Pie makes it unlikely I would consider getting another LG phone. The solution is simple, sell just 1 global version of the phone so you don't have to provide updates for multiple models but they aren't listening to me.
mr3p said:
I wouldn't say I'm miserable with the phone but the lack of timely security updates and lack of update to Android Pie makes it unlikely I would consider getting another LG phone. The solution is simple, sell just 1 global version of the phone so you don't have to provide updates for multiple models but they aren't listening to me.
Click to expand...
Click to collapse
Actually its only two versions.
The rest is carrier software that your carrier is responsible for.
maydayind said:
Actually its only two versions.
The rest is carrier software that your carrier is responsible for.
Click to expand...
Click to collapse
Interesting. So you are saying that G710TM, G710VMX, G710ULM, G710PM, G710VM, G710EM and G710EMW are all the exact same phone with interachangable firmware? For the record, try calling Google Fi and telling them they are responsible for providing updates, LOL. They will tell you its LG's responsibility but either way my comments still stands. I wouldn't recommend anyone who wants a phone which receives regular updates to ever purchase an LG device.
I loved my quirky V10, but that decided that it would not turn on or chrage one day so I got the flagship at the time - the G7. I think the V30 was still a month or more to release. G7 is or was ok - optimize phone seemed to screw it up, clearing cache in recovery was just an error message, it was not particularly fast, but I could live with that. Then there was a few weeks of the fingerprint scanner being wonky. Well fingerprint stopped working yesterday. Hard reset didnt fix it. So yeah after 4+ years with LG never again will I get one.
Update: fingerprint started working again for some unknown reason. Software conflict maybe?
mjl574 said:
I have had this phone since late September, and have never had the issues that you have. Yes, it does have its quirks, but nothing like you've described. Have you tried a factory reset to see if that fixes the issues?
Sent from my LM-G710VM using Tapatalk
Click to expand...
Click to collapse
done 5 times (through settings and through recovery as well, I tried both methods), still piece of junk
I am glad everyone else is happy, but not me. All I can say it, wait until you DO have issues and try to reach out through LG. LG wont respond, they dont care, trust me, we are on our own. I will NEVER again EVER purchase another LG product, not a phone, washer, TV, monitor, nada. I am far from the only one complaining, its everywhere on the internet but I am surprised to find so many happy LG users here on XDA (but thats actually a good thing). I was expecting to find more users like me who cannot stand bloat, corporate BS, locked bootloaders, ETC. Maybe its just me, but I cannot stand by any company that does not allow bootloaders to be unlocked, no one has the right to tell us what we can and cannot do with phones WE OWN!
LameMonster82 said:
Can you flash custom partitions with octopus box?
Click to expand...
Click to collapse
Yes but with the locked bootloaders, it is limited to "EMERGENCY FLASH" not the full bore flash. I can however cross-flash but I think that would only help if I had a .KDZ or .OCT that contains a rooted image for the EM model (or custom variant). I tried to load the EM model and unlock through the LG.DEV and it knew my IMEI was for a different model so it wouldnt give me the .bin file.
Octoplus LG:
G710AWMH - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EM - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EMW - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
GROOVYJOSHCLARK said:
Yes but with the locked bootloaders, it is limited to "EMERGENCY FLASH" not the full bore flash. I can however cross-flash but I think that would only help if I had a .KDZ or .OCT that contains a rooted image for the EM model (or custom variant). I tried to load the EM model and unlock through the LG.DEV and it knew my IMEI was for a different model so it wouldnt give me the .bin file.
Octoplus LG:
G710AWMH - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EM - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EMW - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
Click to expand...
Click to collapse
Maybe emergency flash could be enough. I know how to get root through flashing abl_a and ftm (I think) partitions from an EM module and using the unlock bin from the em model. Can you check if you can flash abl_a and ftm?
LameMonster82 said:
Maybe emergency flash could be enough. I know how to get root through flashing abl_a and ftm (I think) partitions from an EM module and using the unlock bin from the em model. Can you check if you can flash abl_a and ftm?
Click to expand...
Click to collapse
I actually deleted the .bin file a while back when it didnt work, if you have a new copy, I will try it. I am willing to try anything at this point to get off the stock OS, it is such junk! I am glad other users are happy, but I am surely not! I went from my own AOSP on my PME (HTC 10) to this over-bloated piece of junk that barely functions.
GROOVYJOSHCLARK said:
I actually deleted the .bin file a while back when it didnt work, if you have a new copy, I will try it. I am willing to try anything at this point to get off the stock OS, it is such junk! I am glad other users are happy, but I am surely not! I went from my own AOSP on my PME (HTC 10) to this over-bloated piece of junk that barely functions.
Click to expand...
Click to collapse
Yeah I have. Don't worry.
@GROOVYJOSHCLARK i need your help getting some info about the phone through your octopus box. Can you help me?
LameMonster82 said:
@GROOVYJOSHCLARK i need your help getting some info about the phone through your octopus box. Can you help me?
Click to expand...
Click to collapse
Not right this second but yes, just tell me what you need and I'll get it and reply. My box is home and I'm at the office in the city so it won't be until tonight or tomorrow morning but I will get it.
GROOVYJOSHCLARK said:
Not right this second but yes, just tell me what you need and I'll get it and reply. My box is home and I'm at the office in the city so it won't be until tonight or tomorrow morning but I will get it.
Click to expand...
Click to collapse
Just the box. The idea is to record how the box communicates with the phone and get a firehose file out of it. No need to flash anything. Just USB sniffing the recognition
Edit: tell me whenever you're ready and I will guide you if you don't know how
LameMonster82 said:
Just the box. The idea is to record how the box communicates with the phone and get a firehose file out of it. No need to flash anything. Just USB sniffing the recognition
Edit: tell me whenever you're ready and I will guide you if you don't know how
Click to expand...
Click to collapse
Just PM me whatever you need or here publicly if you think it's worth while for others.
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 have a Fold 2 from China, which makes it a game breaker in that it locks the Samsung apps store to China's, including related Samsung gear (like the gear S3 watch or buds), which means I have NO access to any actual useful English apps.
This would solve a world of problems for me.
Crossing fingers...
Spixe1 said:
I have a Fold 2 from China, which makes it a game breaker in that it locks the Samsung apps store to China's, including related Samsung gear (like the gear S3 watch or buds), which means I have NO access to any actual useful English apps.
This would solve a world of problems for me.
Crossing fingers...
Click to expand...
Click to collapse
You should be able to BUT make sure the model numbers are the same and that the bootloader is unlocked before flashing a ROM (SoC version MUST match or its bricksville). This will also require a CSC change.
This may also require rooting your phone which will nullify any warranties...
I'd make sure you have read up how to do this and REALLY understand the dangers as this can brick your device.
Also have a a stock ROM on hand to flash back if/when things go sideways.
I tend to find the Chinese region locked variants of phones, though a little cheaper to buy, are NOT worth the effort and risk due to the reason you want to reflash. Warranties are also non-existent due to postage and time constraints.
Again, this could be a major drain of time and effort, not to mention hair pulling, to find yourself back at square one or worse.
ultramag69 said:
You should be able to BUT make sure the model numbers are the same and that the bootloader is unlocked before flashing a ROM (SoC version MUST match or its bricksville). This will also require a CSC change.
This may also require rooting your phone which will nullify any warranties...
I'd make sure you have read up how to do this and REALLY understand the dangers as this can brick your device.
Also have a a stock ROM on hand to flash back if/when things go sideways.
I tend to find the Chinese region locked variants of phones, though a little cheaper to buy, are NOT worth the effort and risk due to the reason you want to reflash. Warranties are also non-existent due to postage and time constraints.
Again, this could be a major drain of time and effort, not to mention hair pulling, to find yourself back at square one or worse.
Click to expand...
Click to collapse
Appreciate the honest reply - hell I just appreciate the reply at all, pretty much thought it'd be ignored. What you said makes sense, from all the reading I've done, just TRYING to find an answer to this question, considering info on flashing to other ROMS is pretty much non-existent, it seemed a risk. You all but confirmed this, and I will most definitely take your advice and just give up the venture. Better having a working phone locked to Chinese apps (arg!) than a bricked phone... barely, ha.
Thanks again for the answers mate, truly appreciated.