Related
I struggled long and hard with the decision to purchase the EVO. Its competitor for my patronage was the Nexus One on T-Mobile. At last, I made my decision based upon the following criteria: 1) better hardware, 2) better network, and 3) better price. Seems a no brainer, right?
Now that what's done is done, I'm left with a sense of remorse. Over what? Openness. Fortunately, I haven't bricked my Evo yet, but there is a very real possibility that I will at some point. With no open boot loader and a carrier hellbent on closing their system, I have to break into my own phone with a bunch of borrowed hacks, the mechanics of which are about 3 miles over my head.
What was Google really trying to do? By cutting out the carrier from distribution, the carriers don't have an opportunity to bake the system with their garbageware and close the door behind them. By failing to support Google's effort, each of us makes it less likely in some small amount that Google will do this again. We sold them out for a front-facing camera and a bit more screen (with light leak).
Then there we will be on the forums complaining about those evil, freedom-hating carriers. But then, perhaps we chose this and deserve our fates.
If you really were deciding between the nexus one and the evo how come you didn't know the evo was locked .... I mean about just everyone knew this, every single phone but the nexus one its locked from the beginning give it a few days for people to release root, I had a nexus one and couldn't be more happy to have bought the evo I hope you enjoy your phone man
-------------------------------------
Sent from my HTC Evo via the XDA Tapatalk App
Rooting isn't THAT hard. Stop being such a drama queen.
-------------
Sent from my EVO 4G using Tapatalk Pro.
TheBiles said:
Rooting isn't THAT hard. Stop being such a drama queen.
Click to expand...
Click to collapse
You do realize that we do not have full root--and might not ever have full root, right?
You also realize as time goes on that this will inevitably become more difficult?
As charged as the OP's post is, he does have a point.
aLdaRiS said:
If you really were deciding between the nexus one and the evo how come you didn't know the evo was locked .... I mean about just everyone knew this, every single phone but the nexus one its locked from the beginning give it a few days for people to release root, I had a nexus one and couldn't be more happy to have bought the evo I hope you enjoy your phone man
-------------------------------------
Sent from my HTC Evo via the XDA Tapatalk App
Click to expand...
Click to collapse
I knew the evo was locked. I was just too caught up in the specs and the excitement. I got greedy. She was hot, so I cheated. Now I'm sober and feel a sense of remorse.
nihilion_Zero said:
I knew the evo was locked. I was just too caught up in the specs and the excitement. I got greedy. She was hot, so I cheated. Now I'm sober and feel a sense of remorse.
Click to expand...
Click to collapse
Why don't you just return the phone if this bugs you so much?
Shidell said:
You do realize that we do not have full root--and might not ever have full root, right?
You also realize as time goes on that this will inevitably become more difficult?
As charged as the OP's post is, he does have a point.
Click to expand...
Click to collapse
I'm fairly confident that we will get NAND access fairly soon. There is no such thing as an "unhackable" device. Even now, though, it is NOT that difficult to access recovery and easily flash custom ROMs.
Just my two cents, I have only had one android phone and that was the mytouch from t-mobile. I now have the HTC - HD2 and really like it. When it comes to flashing roms, especially for someone new to winmo like me, it can be a bit scary. The developers have a HSPL flash that takes away almost all the risks as long as you use common sense and read things carefully. With that said I did see where a Chef of the HD2 bricked his phone just a few days ago (I have no idea what he was attempting to do when he bricked it but it did make me realize the danger)
Thanks
Derbyman32
Yes, if the remorse is really that bad, take it back. Sprint will refund ALL of your money. Then get the Nexus One for T-Mobile for $179. No-brainer...and the N1 is still an awesome Android phone!
I've seen enough issues on this forum to know that some people have no business flashing a camera, let alone a $500 phone. These are the same people that will install a GSM radio on their CDMA phone, come here and beg for a fix only to be told "sorry, read the instructions next time." They then head to Sprint, shrug, and say "I don't know, it worked fine yesterday" in the hopes of getting the phone replaced under warranty.
I agree with the premise that they are our phones and we should be able to flash whatever we want on them; however, if *I* break my phone, I do not expect Sprint to fix it. Unfortunately, common ethical behavior such as this escapes enough that Sprint made a business decision to make it hard enough so only those competent enough to follow complex procedures succeed in taking ownership of their phones. I get that. I also knew this before buying the phone.
If it's the principle of the matter for you, you can always go back to the N1, but I'd wonder why you're here in the first place.
Me? I have enough faith in this community to undo the locks, and I'll patiently enjoy the marvel of technology the EVO is while shackled until the benefits of rooting outweigh my perceived risks in performing the procedure.
Until then, I have what I consider to be the best handheld computer on the planet. Sorry for being long winded.
jmxp69 said:
Until then, I have what I consider to be the best handheld computer on the planet. Sorry for being long winded.
Click to expand...
Click to collapse
I second that emotion! And it can even make the occasional phone call, too!
nihilion_Zero said:
carrier hellbent on closing their system, I have to break into my own phone with a bunch of borrowed hacks, the mechanics of which are about 3 miles over my head.
Click to expand...
Click to collapse
I don't think a LESS true statement could be said.
Sprint doesn't give two flying flips what you do with your device. They have never made a move to precent root access, and MANY of the same reps who sell these devices root when it becomes available. The phone comes locked because of security and licensing agreements.
An example for the Evo is QIK. QIK is not made by Sprint, HTC, or Google. It is its own entity who paid HTC and Sprint a great deal of money to bake this app into the firmware. It would be a violation of that agreement to allow you to remove this app by default, therefore Root access is removed.
Android, when rooted, has so many holes in the security that information on the phone (like your contact list!) would in no way be considered safe. Sprint has to make some guarantee for that information, so those holes are filled and Root accessis denied.
However, should you be one of those FEW people competent enough to handle this kind of power, and you understand that Sprint, HTC, and Google will honor to warranty for the device should you break it then go for it. None of these companies will make even a token effort to stop you.
You are, for all intents and purposes, ignored. Software updates will be made as though Root did not exist. Known issues and fixes will be sent to employees and techs as though you did not exist. Features will be advertised as stock that you might no longer have, because you no longer exist.
It's not that the "carrier is bent on closing the system" it's that they are bound be several contracts to not help you.
I think they are making a big mistake taking this stance on root & custom roms.
http://androinica.com/2010/07/14/mo...source=feedburner&utm_medium=twitter&utm_camp aign=Feed%3A+androinica+%28Androinica+-++A+Google+Android+Blog%29
Maybe they should stop with Android then. The platform is all about being open. I lost all interest in this phone when this was confirmed.
Sent from my SPH-M900 using XDA App
They just lost half of there customers now
Sent from my HTC Dream
You guys are desensitized from being members here
the rooting/modding/flashing community is maybe at most 10-15% of users, and that's being super generous
most people will not even read that announcement, and if they do, most will have no idea what it means
Zardos66 said:
Maybe they should stop with Android then. The platform is all about being open. I lost all interest in this phone when this was confirmed.
Sent from my SPH-M900 using XDA App
Click to expand...
Click to collapse
i can only completely agree with that! i wanted it but now i ordered a galaxy S...screw you motorola!
Modders may only be a very small portion of their user base. But I'll tell everyone who ask to avoid the whole Moto line of phones. And being a Computer Guy I get asked a lot.
I too have posted my feelings on a couple of other boards. Even on my facebook. Android is open source and it is my understanding that Gingerbread is actually aiming at getting rid of overlays like Sense and Blur. Good for Google.
This wasn't even a fully open admission from Motorola. From what I understand the eFuse thing was found BY modders...and not explained by Motorola. That is down right devious.
I was seriously on the fence about this phone...been driving my friends nuts with comparisons between Evo and Droid X. Was going to have both of them in 30 day period to compare side by side for a week...
...now...I love my Evolina more and she is the phone for me. Canceling my spot on the waiting list.
Its really just a stop gap phone until we see a 4.3" HTC device or other super phone with more features. I can live without custom roms and root access on this phone for 6 months.
grdm said:
You guys are desensitized from being members here
the rooting/modding/flashing community is maybe at most 10-15% of users, and that's being super generous
most people will not even read that announcement, and if they do, most will have no idea what it means
Click to expand...
Click to collapse
I'd say it much smaller than that. There also seems to be a lot of die hard ROM flashing types buying the phone anyways
I dislike the encrypted boot loader, but not enough to not buy the phone. I am assuming we will manage to get root access. And with that we can do a lot.
Only time will tell how big an issue the bootloader ends up being.
Who of you are going to be pissed when / if you find out that, as the hardware is encrypted, you'll won't be able to put any roms on it? Under UK law at least, you won't have any justification to take it back for a refund.
i wont be pissed i just want a good new phone if its unlocked all the better...
MarkusPO said:
Who of you are going to be pissed when / if you find out that, as the hardware is encrypted, you'll won't be able to put any roms on it? Under UK law at least, you won't have any justification to take it back for a refund.
Click to expand...
Click to collapse
When I purchase a phone it is done purely on the following:-
1. What hardware and software is currently available.
2. How it works in it's native form.
3. Whether or not the manufacturer supports the device.
Okay, two out of three's not bad and good enough for me but having an ability to alter/tamper outside of it's base/core never comes into it's purchase.
I'm sure this is what most people will purchase the phone for.
It's a great phone, simple as that.
What? Is the HW encrypted? What did I miss?
I'm with Beards on this one. It's a great phone and that's why I've pre-ordered one.
How is it possible to not care about locked bootloader? But i guess it won't be locked?
Arrghh nearly pre-ordered mine,
What's this about HW encryption??
Is he joking or being serious, I can't find anything
Sent from my MB525 using XDA Premium App
I'm pretty sure he's saying if you find this out, will you be mad? He's not saying it is true.
Who cares...this baby will be cracked open like a nut...and theres always a way to get back to stock if needed...chill out...we are gods here at xda hahaha..
Sent from my GT-I9000 using XDA Premium App
from the horses mouth itself: http://galaxys2.samsungmobile.com/html/feature.html
MarkusPO said:
from the horses mouth itself: http://galaxys2.samsungmobile.com/html/feature.html
Click to expand...
Click to collapse
Is it locked down?
On Device Encryption
The Samsung GALAXY S II is the first Android smartphone to adopt powerful encrypted hardware, minimizing the use of security software and applying encryption technology to the hardware itself, greatly accelerating security protection and achieving superior performance.
I can not see why Samsung would care, they are selling hardware not software, so a open sgs2 will sell more.
DKMIK said:
I can not see why Samsung would care, they are selling hardware not software, so a open sgs2 will sell more.
Click to expand...
Click to collapse
I think wrong. i'm sure 75% of people buying it won't care. however if samsung can make a device that's locked down and secure and it catches on for this reason, it could tempt many large businesses to buy the s2 in hundreds if not thousands per company. that's going to add up to a lot of sales.
I don't know very much about ROM development etc. but couldn't it be that the encryption is totally transparent for accessing the ROM via "normal" software and only exists to protect the ROM against being built out and accessed manually?
this would be bs and i will be pissed.. it would probably mean no tweeking like deleting crap you dont need in system/app or replacing apps with tweeked version.. i may cancel my preorder
Sebring5 said:
Is it locked down?
On Device Encryption
The Samsung GALAXY S II is the first Android smartphone to adopt powerful encrypted hardware, minimizing the use of security software and applying encryption technology to the hardware itself, greatly accelerating security protection and achieving superior performance.
Click to expand...
Click to collapse
Encryption is something else than locking it down. Just wait ya'll...
Hardware encryption does not mean locked bootloader. Samsung has not yet commented about the bootloader locking status. I want to believe that it won't be locked because it is fighting against the whole idea of Android. If I want to do exactly what big brother says I will buy an iPhone.
If the bootloader is properly locked, we won't be able to open it even here in XDA. Motorola Atrix has a locked bootloader and you can go to the Atrix forum here and see yourself how many custom kernels there are. (None)
We all know the direction of Android is completely based on Google's whim, and it has become increasingly apparent that in order to stabilize and defragment their evergrowing and unwieldy ecosystem, they must set some standards and lock some things down. Google has already told phone manufacturers that future Android changes that the companies make must be approved by Google or they won't release early source code to devs who don't comply. They have realized they won't be able to compete with closed and stable systems like iOS, RIM, and WP7 with this "open" approach. What makes you think custom ROM from hacker A will get any blessings when the likes of Samsung or HTC will have to go through Google's scrutiny? I look forward to seeing more locked bootloaders.
It might be like that but as a customer I don't care about the "Being able to compete with iOS"-angle. If I can't modify my phone I am leaving it to shop. Maybe in the future the Google phones are the only ones without locked bootloaders.
Now that I think of it, the locked bootloader has nothing to do with the Android fragmentation. It only prevents developers to modify their phones. Phone manufacturers can still do their Touchwiz and Motoblur things. Maybe this locked bootloader thing has something to do with operators (especially in USA)?
In the UK, if you've preordered it online, there is an EU law on distance selling which covers internet purchases. This enables you to get a refund within 7 days. Whether you think it will be cracked after these 7 days will be up to you, but xda should provide an insight into how hard it will be to do upon release.
http://www.oft.gov.uk/about-the-oft/legal-powers/legal/distance-selling-regulations/
Hi
I am interested in buying this device but still having a nightmare the boot loop because I had really bad experience with G2 G3 G4. What do you think did they truly solve it?
Thank you for sharing your opinion.
I have no issues so far. Keep in mind, no 2 devices are alike.
Sent from my LG-H918 using XDA-Developers Legacy app
Had mine 2 weeks and no problems at all. I'd say go for it, the V20 is an incredible device.
But, if you're into rooting be aware that root is only possible on a few variants. Look for the options here for the particular variant you plan on buying.
Ooh, awesome that good to hear. Looking forward to see more feedback. Thank you both
As a V10 bootloop victim I am confident that the v20 won't have the same issues. It uses a different chipset and doesn't get nearly as hot as the 808 snapdragon (which is the chipset used in the g4/Nexus 5x/V10).
The main boot loop issue on the g4/V10/Nexus 5x was a combination of heat and poor soldering causing a disconnect in the hardware.
I am fairly certain LG has learned it's lesson since it's been a PR nightmare for them further they have a class action lawsuit against them for it.
In one of the G6 videos they made it a point in showing the technology they use to draw heat away from the processor.
Sent from my LG-H918 using XDA-Developers Legacy app
Ok in this case I am going to buy it. Do you or someone else to buy it ? Thank you all
Greetings fellow nerds. How's it hangin'
Note to admin, I don't have permissions to create a dev thread. Your move broooh.
Uhhhh so this whole "Wah VZN and I couldn't buy a google pixel in full because I'm poor" has been getting on my nerves. I too can't afford an $900 phone and due to college, my credit history is a burden.
I want to start a discussion on the feasibility of literally opening up a phone, jamming some probes in and directly overwriting the chip to a generic bootloader/kernel.
Maybe you'd have to replace the chip and start with a blank slate, I dunno, but it's a frikkin' rock encased in refined dinosaur crap. How could the awesome might of electricity (in the form of merciless shock therapy) fail against a turd-encrusted sand-dollar? I don't think so.
I just made this account. Hope to see some naysayers in the morning at least telling me the idea is pointless and I'm an idiot so I don't waste my time.
Btw I don't mean zapping a chip, I just meant using one of those in-system programmers. This method could probably never be patched which is worth looking at as an exploit. AMiR?
Anyone notice that Verizon's latest commercial stars the protagonist of Silicon Valley? As if.
I kind of agree but the knife cuts both ways here. Us making posts about devs needing to try harder to unlock the bootloader may just be getting annoying. They know who they are and they may or may not be working on it. I would love to know somebody that knew how to do this or have an understanding of this. Even at the basic level I wish I knew where they even started.
The way I look at it, the bounty for unlocking the bootloader being ~2k isnt enough. This probably takes weeks to do. I would assume whoever figures out the exploits has an engineering degree from somewhere and understands how programming and exploitation works. They can probably make more money in a weeks time than what the bounty will ever be from this site.
It's not the bounty or the money. There is no reason to unlock the bootloader since the Google version is unlockable. And then a new update comes out and it's locked again. It's just pointless.
Sent from my Pixel using XDA-Developers Legacy app
I've said it before, and I'll say it again. The best bet for unlocking this, or any other phone, is to keep an eye on Linux kernel vulnerabilities. It's not a magic box, it's a small computer running modified Linux. The tricky bit is if a vuln is found, it will be patched. Is it work? Yes. Is it more effort than it's worth? Probably. Is it fun? If it's interesting to you, then yes!
I think in the end, if you look at it as a mystery or puzzle when trying to unlock your device, it can be fun. If you are wanting or needing extra functionality that requires root, then you should likely buy it direct from Google. In principle I don't like that it's locked, but in practice it doesn't matter too much. I totally understand people not being able to afford to drop the money up front, hell I'm one of em! At the same time though, there's nothing magic about "the devs." They're just people who found this stuff fascinating and decided to learn how to do it. Which means YOU can do it too! Only thing standing between you and an unlocked device is investment, either in money (a google phone), or in time (learn how these things work and try it yourself).
Ok this ended in me rambling a bit. Hopefully it made sense.
Has anyone tried manually flashing an ota update through the stock recovery ? It Should pass signature verification from the locked bootloader right ? If so , couldn't there be a way to fake the signature , so a modified .zip could be flashed on a locked bootloader ?
IDK just asking since I got a Verizon version a week ago . Been on Nexus devices since the Galaxy Nexus . I am pretty upset at my ignorance on not knowing Verizon locked the bootloader on their version before buying.
I'm not an expert but I have some experience modding kernels and recoveries on the Galaxy Nexus and Nexus 6
Sent from my Pixel XL using Tapatalk
Jessooca said:
I understand what you're asking and I too bought a Pixel XL (verizon version) forgetting entirely about the locked bootloader... in all the other nexus devices I've had you could simply download the latest official image from google for the device and simply flash it and youd have a nexus/pixel you could use on whichever carrier you want and not have to worry about bloatware, etc... so I am assuming your asking if you can do just that, simply download the latest full factory image https://dl.google.com/dl/android/aosp/marlin-opr3.170623.007-factory-fc68b6a3.zip and flash it to your phone and will it work or cause issues...... well it simply will fail from the get go IF it won't work.
Click to expand...
Click to collapse
Basically what I was getting at is there might be a way to trick the locked bootloader into thinking a .zip file I flash is an ota update when it's really something else . It's the only way I see a route into gaining superuser privilege.
Also I am going to call Verizon and see why they decided to do this. I can't see an answer that they could give that would be reasonable . Hopefully they have the ability to unlock them or push an update to unlock after the pixel 2 is out IDK .
Sent from my Pixel XL using Tapatalk
bsmitty83 said:
Basically what I was getting at is there might be a way to trick the locked bootloader into thinking a .zip file I flash is an ota update when it's really something else . It's the only way I see a route into gaining superuser privilege.
Also I am going to call Verizon and see why they decided to do this. I can't see an answer that they could give that would be reasonable . Hopefully they have the ability to unlock them or push an update to unlock after the pixel 2 is out IDK .
Click to expand...
Click to collapse
You do that. Let us know what they say. It's prolly just a mistake on their part. They prolly didn't mean to lock them.
LMAO.
mattwheat said:
You do that. Let us know what they say. It's prolly just a mistake on their part. They prolly didn't mean to lock them.
LMAO.
Click to expand...
Click to collapse
Id say save your time calling them. They will more than likely give you some ,in their eyes common sense, reasons in the direction of "Its network security" or "we don't want our customers unknowingly flashing a file not meant for the device and bricking their device" ect. Look online as to why they chose to lock the boot loader, because they can get away with it hiding behind network security and watching out for customers.
bsmitty83 said:
Also I am going to call Verizon and see why they decided to do this. I can't see an answer that they could give that would be reasonable . Hopefully they have the ability to unlock them or push an update to unlock after the pixel 2 is out IDK .
Click to expand...
Click to collapse
I highly doubt it. They do it for security as well as a control measure when it comes to warranty, returns, and insurance.
You have dishonest people that would do things to their devices and brick them and try to say it's a defect. Back in the day you could load iPhone firmware onto an iPod, brick it so bad their in-store software tools couldn't find the root cause and walk out with a shiny new device because it looks like a defect.
The fact that a nexus / pixel is almost impossible to brick is irrelevant because they arent in the business of quantifying how brickable or not a device is and applying bootloaders accordingly.
The majority of their customers don't even know what a bootloader is.
Further more I don't think anyone in their 3 tier service model will give you a useful answer based off of the point above. Even if you got an answer how will that change what the current situation is.
Frankly I'd figure out a way to buy from Google and screw the run around because I bet you there are people holding out hope for an early exploit like we had on the Pixel which is highly unlikely.
Unless you can find how bootloaders are in violation of the block C rules, this is a losing battle.
pcriz said:
I highly doubt it. They do it for security as well as a control measure when it comes to warranty, returns, and insurance.
You have dishonest people that would do things to their devices and brick them and try to say it's a defect. Back in the day you could load iPhone firmware onto an iPod, brick it so bad their in-store software tools couldn't find the root cause and walk out with a shiny new device because it looks like a defect.
The fact that a nexus / pixel is almost impossible to brick is irrelevant because they arent in the business of quantifying how brickable or not a device is and applying bootloaders accordingly.
The majority of their customers don't even know what a bootloader is.
Further more I don't think anyone in their 3 tier service model will give you a useful answer based off of the point above. Even if you got an answer how will that change what the current situation is.
Frankly I'd figure out a way to buy from Google and screw the run around because I bet you there are people holding out hope for an early exploit like we had on the Pixel which is highly unlikely.
Unless you can find how bootloaders are in violation of the block C rules, this is a losing battle.
Click to expand...
Click to collapse
It's definitely not a security issue , if they were worried about it on their end , the network end , I would never have been running unlocked bootloader devices on their network for better part of a decade. There's no reason they can give other than " we don't want people messing with their phone "
I honestly don't care if they hang up on me when I call , but they greyed out a switch and left a message to contact them so that's what I'll do since I guess no one else ever has . I'll laugh if they do unlock it for me ......
Again I was merely trying to suggest ways to attack the problem , I'm surprised there isn't more of a will to over come the problem simply because it's a challenge , not go buy a google version . I did buy a google version , screw Verizon . I'll find a way to unlock it or someone who can , or they will .
Xda has changed a lot..... [emoji53]
Sent from my Pixel XL using Tapatalk
bsmitty83 said:
It's definitely not a security issue , if they were worried about it on their end , the network end , I would never have been running unlocked bootloader devices on their network for better part of a decade. There's no reason they can give other than " we don't want people messing with their phone "
I honestly don't care if they hang up on me when I call , but they greyed out a switch and left a message to contact them so that's what I'll do since I guess no one else ever has . I'll laugh if they do unlock it for me ......
Again I was merely trying to suggest ways to attack the problem , I'm surprised there isn't more of a will to over come the problem simply because it's a challenge , not go buy a google version . I did buy a google version , screw Verizon . I'll find a way to unlock it or someone who can , or they will .
Xda has changed a lot..... [emoji53]
Click to expand...
Click to collapse
Them allowing you to run an unlocked device has nothing to do with what they sell. They can't prevent you from using a compatible device if their network supports it and it isn't black listed. That's an FCC rule, plain and simple. Has nothing to do with the bootloader on your device.
XDA hasn't changed, the fact that you think this battle is brand new and we are blazing a trail just shows a short sightedness of the community.
There have been hundreds of petitions created, there have been pushes in various device threads to flood the FCC with requests to elevate the issue. Verizon as well as other carriers have literally had lawsuits levied against them. This has literally been going on for YEARS.
Please tell me after reading all that what calling and wasting the time of tech support is gonna do.
The real funny thing is someone that thinks they can call tech support and simply get your bootloader unlocked. That is hilarious.
Tell me who do you think designed and very likely has the means to unlock the boot loader on your GOOGLE Pixel? Hint, it isn't Verizon.
Verizon didn't develop the patch that blocked the exploit either. So what do you really think Verizon is gonna do to help you by calling tech support.
You want your bootloader unlocked? Get super friendly with a Google Android engineer, get super smart with Android period, or get a lawyer.
Xda hasn't changed, the mobile market has changed and it is making it harder to feel bad for people that buy subsidized carrier phones and then cry about locked bootloaders
Especially when affordable unlocked devices exist. But hey, screw logic. Let's go harass CSRs like their jobs don't suck enough.
pcriz said:
Them allowing you to run an unlocked device has nothing to do with what they sell. They can't prevent you from using a compatible device if their network supports it and it isn't black listed. That's an FCC rule, plain and simple. Has nothing to do with the bootloader on your device.
XDA hasn't changed, the fact that you think this battle is brand new and we are blazing a trail just shows a short sightedness of the community.
There have been hundreds of petitions created, there have been pushes in various device threads to flood the FCC with requests to elevate the issue. Verizon as well as other carriers have literally had lawsuits levied against them. This has literally been going on for YEARS.
Please tell me after reading all that what calling and wasting the time of tech support is gonna do.
The real funny thing is someone that thinks they can call tech support and simply get your bootloader unlocked. That is hilarious.
Tell me who do you think designed and very likely has the means to unlock the boot loader on your GOOGLE Pixel? Hint, it isn't Verizon.
Verizon didn't develop the patch that blocked the exploit either. So what do you really think Verizon is gonna do to help you by calling tech support.
You want your bootloader unlocked? Get super friendly with a Google Android engineer, get super smart with Android period, or get a lawyer.
Xda hasn't changed, the mobile market has changed and it is making it harder to feel bad for people that buy subsidized carrier phones and then cry about locked bootloaders
Especially when affordable unlocked devices exist. But hey, screw logic. Let's go harass CSRs like their jobs don't suck enough.
Click to expand...
Click to collapse
I guess I wasn't being clear enough . All I was trying to understand is why its locked in the first place . My Nexus 6 was never locked by Verizon . What if I paid full price outright for it from Verizon ? Why would they care what I do with the phone once its paid for ? What would be the difference if I bought it from google and put a Verizon sim card in it ? You sound so keen on defending the company and their poor hapless CSR's lol .
I don't care about the petitions or any of what your telling me .
I have no interest in lawsuits , simply finding a means to unlock my bootloader .
I could care less if it was htc that designed the patch , or google or apple.
I'm looking to find a way to make it work because it's something to do .
It's about unlocking it , that's it . People on this site used to be about finding solutions to problems , that's all .
Tell me what's wrong with that logic.
Sent from my Pixel XL using Tapatalk
bsmitty83 said:
I guess I wasn't being clear enough . All I was trying to understand is why its locked in the first place . My Nexus 6 was never locked by Verizon . What if I paid full price outright for it from Verizon ? Why would they care what I do with the phone once its paid for ? What would be the difference if I bought it from google and put a Verizon sim card in it ? You sound so keen on defending the company and their poor hapless CSR's lol .
I don't care about the petitions or any of what your telling me .
I have no interest in lawsuits , simply finding a means to unlock my bootloader .
I could care less if it was htc that designed the patch , or google or apple.
I'm looking to find a way to make it work because it's something to do .
It's about unlocking it , that's it . People on this site used to be about finding solutions to problems , that's all .
Tell me what's wrong with that logic.
Click to expand...
Click to collapse
So you don't care about fighting the market status quo of carriers locking devices which would be a preventative measure to help all mobile device users. Got it...
You want to know why it's locked and how to unlock it, but can't trouble yourself with asking questions to the right people. Got it..
Part of solution finding is narrowing down all the efforts that have failed or won't work for obvious reason, like calling them and saying why is my phone bootloader locked, calling them and asking if they can unlock it. Yet the fact that I don't agree with that means there is inherently something wrong with XDA.
I mention legal means as it relates to their block c spectrum purchase, you don't want to hear that. Again let me say again you have to make comment that XDA has changed. But yet another path ignored.
I get it now so I will agree to disagree, some people want thumbs up and yes men around them instead of well rounded opinions.
I tell you what. If you call and they tell you how to unlock your device I will Google wallet you 50 bucks.
pcriz said:
So you don't care about fighting the market status quo of carriers locking devices which would be a preventative measure to help all mobile device users. Got it...
You want to know why it's locked and how to unlock it, but can't trouble yourself with asking questions to the right people. Got it..
Part of solution finding is narrowing down all the efforts that have failed or won't work for obvious reason, like calling them and saying why is my phone bootloader locked, calling them and asking if they can unlock it. Yet the fact that I don't agree with that means there is inherently something wrong with XDA.
I mention legal means as it relates to their block c spectrum purchase, you don't want to hear that. Again let me say again you have to make comment that XDA has changed. But yet another path ignored.
I get it now so I will agree to disagree, some people want thumbs up and yes men around them instead of well rounded opinions.
I tell you what. If you call and they tell you how to unlock your device I will Google wallet you 50 bucks.
Click to expand...
Click to collapse
I'm not interested in fighting the status quo , no .
I'm into actual software development . Hands on stuff . I'm not a politician .
Your trying to give me solutions to a problem that isn't relevant to my immediate problem. I was looking for software related fixes .
Your too hung up on me calling Verizon lol . It was more tongue in cheek than anything , and it was an edit to my post about finding a workaround to the greyed out settings switch . That was all .
So again if you have any advice on how to unlock the bootloader , which is what I'm trying to do , not fight the man , please advise .
That's the spirit of xda , software development , not "fighting market status quo"
Sent from my Pixel XL using Tapatalk
So what did Verizon say?
Sent from my Nexus 6 using Tapatalk
stinger4321 said:
So what did Verizon say?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
My understanding is that Verizon suggested multi-pronged approach, including,
1. Call VZW customer service
2. Hire a lawyer
3. Complain to the FCC independent of your attorney
4. Start a thread on xda
4.1. Generically denigrate the quality and state of development on xda
4.2. Misspell "you're" as often as you please
4.3. Kvetch at xda users, including @pcriz
5. "Thank you for calling Verizon"
I believe that buying directly from Google was never mentioned.
Lol®
micmars said:
My understanding is that Verizon suggested multi-pronged approach, including,
1. Call VZW customer service
2. Hire a lawyer
3. Complain to the FCC independent of your attorney
4. Start a thread on xda
4.1. Generically denigrate the quality and state of development on xda
4.2. Misspell "you're" as often as you please
4.3. Kvetch at xda users, including @pcriz
5. "Thank you for calling Verizon"
I believe that buying directly from Google was never mentioned.
Lol®
Click to expand...
Click to collapse
Lol
micmars said:
My understanding is that Verizon suggested multi-pronged approach, including,
1. Call VZW customer service
2. Hire a lawyer
3. Complain to the FCC independent of your attorney
4. Start a thread on xda
4.1. Generically denigrate the quality and state of development on xda
4.2. Misspell "you're" as often as you please
4.3. Kvetch at xda users, including @pcriz
5. "Thank you for calling Verizon"
I believe that buying directly from Google was never mentioned.
Lol®
Click to expand...
Click to collapse
Lol.. i figured he hadn't called yet.. just liked blowing smoke in here...But I did unlock my bootloader.... Sold it on swappa... Now waiting on pixel prices to drop or waiting for pixel 2.. meantime rocking my nexus 6 which has more support then the pixel...
Sent from my Nexus 6 using Tapatalk
I've called Verizon on the locked bootloader issue when I was stuck on O beta and trying to downgrade. I first called Google because I unenrolled the beta and never got the OTA to go back to 7.1.2. They told me to flash the image but I told them I couldn't since the bl is locked. The rep told me to call VZW to have them unlock it so I called them and the VZW rep was all "wut, we don't fool around with OS, call Google and tell them to unlock it." I called Google and was told they couldn't unlock it. I seriously miss root.