Related
When I bought the 64GB DE, it was with the expectation it would receive OTA updates directly from HTC. Now it appears, at least one HTC respondent is claiming that because the bootloader is unlocked, it will not be receiving OTA updates. I hope this info is wrong.
http://forums.androidcentral.com/htc-one/272529-htc-one-aint-getting-no-ota-updates.html
Of course it will. HTC needs this phone to succeed. They wouldn't shoot themselves In the foot like that.
Sent from my HTC One using xda premium
It will probably just get RUUs instead. It makes no sense to try and support a device with an unlocked bootloader when unlocking the bootloader breaks the system signature.
It should get updates faster than the branded carrier versions. Whether its via OTA or RUU remains to be seen.
MG
Ok, I just got a reply from HTC a few minutes ago:
Thank you for contacting us. Robert, we understand how important this information is for you.
As the developer’s edition of the HTC One has its bootloader unlocked, it will not get the updates OTA (Over the Air). You can manually install it when available with the instructions found at http://www.htcdev.com/.
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader or installing different ROMS (A file which contains a copy of the data from a read-only memory chip) may be covered under warranty. We strongly suggest that you do not perform this process unless you are confident that you understand the risks involved. This is a technical procedure and the side effects could possibly necessitate repairs to your device not covered under warranty.
If further assistance is required, please let me know. As always, it was my pleasure to assist you.
Feel free to visit www.htc.com/ for important information about HTC, or contact us by phone at 1-866-449-8358 between 8am to 1am ET, 7 days a week for your convenience.
Have a nice day!
Let me know if I have successfully answered your question, please click here to complete this.
To send a reply to this message, please click here.
Sincerely,
David
HTC
rmc69 said:
Ok, I just got a reply from HTC a few minutes ago:
Thank you for contacting us. Robert, we understand how important this information is for you.
As the developer’s edition of the HTC One has its bootloader unlocked, it will not get the updates OTA (Over the Air). You can manually install it when available with the instructions found at http://www.htcdev.com/.
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader or installing different ROMS (A file which contains a copy of the data from a read-only memory chip) may be covered under warranty. We strongly suggest that you do not perform this process unless you are confident that you understand the risks involved. This is a technical procedure and the side effects could possibly necessitate repairs to your device not covered under warranty.
If further assistance is required, please let me know. As always, it was my pleasure to assist you.
Feel free to visit www.htc.com/ for important information about HTC, or contact us by phone at 1-866-449-8358 between 8am to 1am ET, 7 days a week for your convenience.
Have a nice day!
Let me know if I have successfully answered your question, please click here to complete this.
To send a reply to this message, please click here.
Sincerely,
David
HTC
Click to expand...
Click to collapse
That makes no sense at all. They push the responsibility the bootloader being unlocked to the customer. No, it was purchased that way. I'm thinking David doesn't know what the hell he's talking about...
No, he's saying that if you want to get updates, you need to run RUUs. This is far from surprising, people need to get over it.
1. Using a ruu is far from a technical process
2. If you buy a developer edition phone it's implying you will be using it for development purposes.
3. Who still accepts ota downloads
Ok .. how l can download this update ? I can believe there ,, no update for htc one developer edition ! Why ?
That does suck. We too would like our updates.
I have a 64GB DE and I could not care less about OTA on stock rom. By getting the DE and hanging out here, isn't it implied that you would install custom roms? What HTC said that by getting the Dev Edition you'll have to install via RUU - it make perfect sense since if they were to push it out via OTA on multiple carrier's 3G network it would probably require agreement and fees. Just download it when it's ready, or better yet, use a good custom rom. I don't see this as a big deal.
I have no problem with downloading and installing updates from the HTCDev website. My only concern now is the timeliness of the updates. I hope we won't find that major carriers have released updates and we're still waiting for ours. Most of us that bought the DE do indeed plan to install custom roms. I personally wanted to wait a few weeks before doing so, but I guess it really makes no difference.
This is actually idiotic.
Shouldn't HTC give the choice to OTA update or not to the purchasers of the developer edition? You can always turn it off if you don't want it, but not providing it at all is dumb.
I am waiting for my developer edition to arrive. I bought this phone primarily for the good industrial design and in part for the low light camera.
I hope I don't regret it, if updates are few and far between (even the 4.2 update has been delayed and it will be out after 4.3 is already available). HTC better get on the ball, because the ONE is the last chance many consumers will give it.
Hello All,
I realize this issue has been addressed, and there are a few short threads on the topic. Frankly, I am surprised that there is not more chatter regarding the lack of Android 6.0 - Marshmallow for Nexus 6 devices purchased through T-Mobile!!!!!!!!!!!!!!
I am no expert, but would not consider myself in the "noob" category. I am fully aware of the wider LTE spectrum required for T-Mobile Nexus devices, i.e. Band 12, as well as carrier enabled Wi-Fi calling over T-Mobile's network.
I just can't seem to understand how almost 2 months later, my d*mn Nexus 6 is still on 5.1.1. ?!?!?!?
Does anyone have anymore insight regarding this? Can we discuss and find out WHY they are still in their "Testing" phase? Honestly, I'm glad that they are doing the properly required due diligence and QA testing, but 2 months?!?!?!?!? COME ON T-Mobile/Google!
At this point, I would NOT be surprised to get 6.0 on my Note 5 before my Nexus 6. Wait, on second thought, I doubt it. Will probably get it after the Note 7 comes out.
And please don't tell me I can flash the factory image from https://developers.google.com/android/nexus/images?hl=en I am fully aware and we have all gone this route plenty of times. I simply want to start a meaningful discussion that may shed some light on WHAT in the WORLD is taking T-Mobile so long to finish validating their Marshmallow build, or if it's not truly that, then what is the hold up??????
Do you really think your going to get a meaningful discussion here? Especially when your ranting your head off throwing caps around and cursing in the thread title?
Regardless of if its what you want to hear or not... Google made the update available for you the instant it came out. If you have chosen not to take it, then that was your choice.
Wait patiently, or make the choice to go take the update... Those are your options.
Cursing in the title? I took the courtesy of censoring it, if you haven't noticed and Hell isn't exactly a "bad word". Relax man, it isn't directed at you or anyone else for that matter. If you have nothing "meaningful" to say, then why waste time even replying. Didn't realize there were so many sensitive females on this website.
It's quite obvious you don't like to read things in it's entirety prior to replying to a stranger. I would recommend Neurontin, or maybe Zoloft. Might help with the impulse control.
Punctuation exists for a reason. If I want to complain about a Nexus branded device not receiving a major update two months after release within the context of a website that exists to discuss just these types of issues, I will.
Again, Neurontin... ENN, EE, YOU, ARR, OH, ENN, TEE, EYE, ENN. Talk with your shrink about it. Might help get your head out of your rectum. Unless of course your father prefers it that way.
Then by all means, carry on.
Anyhow, spoke to a T-Mobile tech support representative, not that they have ever been much help historically, but apparently they are testing T-Mobile specific applications to ensure that they play well with Android 6.0 (He Mentioned Visual Voicemail, T-Mobile My Account, etc.). Does that mean that the Nexus 6 devices purchased via T-Mobile will have a disparate build? Based on what this guy said, it looks like it.
Another reason why I didn't just blindly flash the Universal builds. Not to mention, many T-Mobile customers who have already done so, are experiencing bugs with their devices and/or broken functionality.
Android1126 said:
Cursing in the title? I took the courtesy of censoring it, if you haven't noticed and Hell isn't exactly a "bad word". Relax man, it isn't directed at you or anyone else for that matter. If you have nothing "meaningful" to say, then why waste time even replying. Didn't realize there were so many sensitive females on this website.
It's quite obvious you don't like to read things in it's entirety prior to replying to a stranger. I would recommend Neurontin, or maybe Zoloft. Might help with the impulse control.
Punctuation exists for a reason. If I want to complain about a Nexus branded device not receiving a major update two months after release within the context of a website that exists to discuss just these types of issues, I will.
Again, Neurontin... ENN, EE, YOU, ARR, OH, ENN, TEE, EYE, ENN. Talk with your shrink about it. Might help get your head out of your rectum. Unless of course your father prefers it that way.
Then by all means, carry on.
Click to expand...
Click to collapse
That was a great delivery, lmao.
I don't give a **** if you say hell. Just saying if you want the reasonable conversation your claim to, your doing a pretty ****ing bad job of starting it.
Your Nexus branded devices DOES have an update. You're just waiting for it to be sent to you, by all means continue to do so.
scryan said:
I don't give a **** if you say hell. Just saying if you want the reasonable conversation your claim to, your doing a pretty ****ing bad job of starting it.
Your Nexus branded devices DOES have an update. You're just waiting for it to be sent to you, by all means continue to do so.
Click to expand...
Click to collapse
Son, you really DO NOT know what you are talking about. Go look at the Factory Image page at https://developers.google.com/android/nexus/images?hl=en , now go to Shamu, and read the images (might take a bit of scrolling, so resist the urge to give up and rant and rave, in an attempt to teach me etiquette). Do you see where it says "5.1.0 (For T-Mobile ONLY) (LMY47M)" or "5.1.1 (For T-Mobile ONLY) (LYZ28E)" or "5.1.1 (For T-Mobile ONLY) (LYZ28J)" or 5.1.1 "(For T-Mobile ONLY) (LYZ28K)" or "5.1.1 (For T-Mobile ONLY) (LYZ28M)" or "5.1.1 (For T-Mobile ONLY) (LYZ28N)"??
Again, impulse control. Do a little research before replying. Not to mention VoLTE and Cat 14 LTE that only T-Mobile uses (in this country, and at this time). Not saying that the universal build absolutely WON'T work, but there are more than a few stories out there stating that exact opposite. I for one, would like to wait for a build that is catered to the frequencies of my Mobile network for the simple fact that it will address all of those incompatibility issues.
Anger issues? Abused as a child? Watch your dirty little mouth. Also, learn some basic grammar "I don't give a **** if you say hell. Just saying if you want the reasonable conversation "your" claim to, "your"doing a pretty ****ing bad job of starting it"?
I think you meant "you" and you're"
How do we go from hell to F***? You're one sick little boy.
Moderator, please close this thread, as you deem fit.
Also, many people who have downloaded the universal image, wiped their devices, and installed the update, have had to root, downgrade their Radio for 5.1.1. just to get an LTE signal and WiFi calling as well as a number of other features to work properly.
Again, read before you reply.
Android1126 said:
Son, you really DO NOT know what you are talking about. Go look at the Factory Image page at https://developers.google.com/android/nexus/images?hl=en , now go to Shamu, and read the images (might take a bit of scrolling, so resist the urge to give up and rant and rave, in an attempt to teach me etiquette). Do you see where it says "5.1.0 (For T-Mobile ONLY) (LMY47M)" or "5.1.1 (For T-Mobile ONLY) (LYZ28E)" or "5.1.1 (For T-Mobile ONLY) (LYZ28J)" or 5.1.1 "(For T-Mobile ONLY) (LYZ28K)" or "5.1.1 (For T-Mobile ONLY) (LYZ28M)" or "5.1.1 (For T-Mobile ONLY) (LYZ28N)"??
Again, impulse control. Do a little research before replying. Not to mention VoLTE and Cat 14 LTE that only T-Mobile uses (in this country, and at this time). Not saying that the universal build absolutely WON'T work, but there are more than a few stories out there stating that exact opposite. I for one, would like to wait for a build that is catered to the frequencies of my Mobile network for the simple fact that it will address all of those incompatibility issues.
Anger issues? Abused as a child? Watch your dirty little mouth. Also, learn some basic grammar "I don't give a **** if you say hell. Just saying if you want the reasonable conversation "your" claim to, "your"doing a pretty ****ing bad job of starting it"?
I think you meant "you" and you're"
How do we go from hell to F***? You're one sick little boy.
Moderator, please close this thread, as you deem fit.
Click to expand...
Click to collapse
theres only one build for marshmallow. no matter which carrier you use, you use the same build. yes, wifi calling works on it. lte, volte, and everything else too. im on tmobile as well.
Android1126 said:
Anger issues?
Click to expand...
Click to collapse
Yes. You have them.
https://support.t-mobile.com/thread/116433
Please note, as documented by tmobile support, no tmobile specific build is presented because beginning with 6.0 its a unified build.
Android 6.0 (Marshmallow) is a unified build and is the same version across all carriers. WiFi Calling is baked into the OS.
Click to expand...
Click to collapse
simms22 said:
theres only one build for marshmallow. no matter which carrier you use, you use the same build. yes, wifi calling works on it. lte, volte, and everything else too. im on tmobile as well.
Click to expand...
Click to collapse
simms22, thanks for the advice. I do realize that, and I have read as much for the most part. My main point was really an attempt at trying to gain an understanding as to why Nexus 6 devices from T-Mobile have not yet been updated to Marshmallow.
I appreciate your comment. I have also read about a number of incompatibility issues when flashing the universal build, so I like to err on the side of caution, especially considering that I use my Note 5 as a daily driver. Also, not trying to do a full wipe just yet (I realize I can do so without, but from what I have read, that is what is causing the bugs/incompatibility).
Like I stated earlier, the T-Mobile tech. rep. stated that there will be a T-Mobile specific build out soon. Now what that contains, I cannot say. Just trying to gain some insight. It could just be T-Mobile bloatware, though I am fairly certain they are addressing some of the known issues that are affecting a portion of Nexus 6 devices running Marshmallow on T-Mobile.
Thanks again.
scryan said:
Yes. You have them.
https://support.t-mobile.com/thread/116433
Please note, as documented by tmobile support, no tmobile specific build is presented because beginning with 6.0 its a unified build.
Click to expand...
Click to collapse
You just linked me to a site where a bunch of amateurs are discussing flashing a non standard build. Where, by the way, a person poses the question "a) Is that a T-Mobile Build? I am not seeing Wi-Fi calling related section anywhere"
Really, do you read anything before posting replying?
I would look at this page that T-Mobile has published.
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Do you see what it says? If you need help reading (and then pausing to process), let me know.
Here is a recap for people with learning disabilities (no offense if you really have one, seriously).
UPDATE PROCESS 3 stages. Current: Stage 2 T-Mobile testing.
Please man, just stop replying. Because I can keep making you look like your mother dropped you on your head all night.
scryan said:
Yes. You have them.
https://support.t-mobile.com/thread/116433
Please note, as documented by tmobile support, no tmobile specific build is presented because beginning with 6.0 its a unified build.
Click to expand...
Click to collapse
Also, do you see where the correct answer states "Flashing with a T-Mobile rom is going to require you to unlock your bootloader...." Key words "T-Mobile ROM"
Where does it say that all builds are unified starting at Android 6.0? That may be the case for all other carriers, but it is PRETTY obvious, that this does not apply to the T-Mobile build for 6.0.
Android1126 said:
You just linked me to a site where a bunch of amateurs are discussing flashing a non standard build. Where, by the way, a person poses the question "a) Is that a T-Mobile Build? I am not seeing Wi-Fi calling related section anywhere"
Really, do you read anything before posting replying?
I would look at this page that T-Mobile has published.
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Do you see what it says? If you need help reading (and then pausing to process), let me know.
Here is a recap for people with learning disabilities (no offense if you really have one, seriously).
UPDATE PROCESS 3 stages. Current: Stage 2 T-Mobile testing.
Please man, just stop replying. Because I can keep making you look like your mother dropped you on your head all night.
Click to expand...
Click to collapse
Your not really making me look like I have been dropped on my head, your making yourself look like a raving lunatic.
I gave you the same answer as simms, other than the fact that I linked to the official support site where the answer marked as correct supports what I said.
Android1126 said:
Also, do you see where the correct answer states "Flashing with a T-Mobile rom is going to require you to unlock your bootloader...." Key words "T-Mobile ROM"
Where does it say that all builds are unified starting at Android 6.0? That may be the case for all other carriers, but it is PRETTY obvious, that this does not apply to the T-Mobile build for 6.0.
Click to expand...
Click to collapse
Flashing ANY rom is going to require a bootloader unlock, so yes flashing a tmobile rom would require a bootloader unlock.
Other carriers then T-Mobile have a unified build? lol, check your definitions there man
u·ni·fy
ˈyo͞onəˌfī/
verb
past tense: unified; past participle: unified
make or become united, uniform, or whole.
It's not united or uniform if its different for tmobile... the entire basis of a unified build is it's the same for everyone.
This thread is too good. Nothing but multiparagraph rants and personal insults from you about how others have anger issues. :laugh:
Android1126 said:
Also, do you see where the correct answer states "Flashing with a T-Mobile rom is going to require you to unlock your bootloader...." Key words "T-Mobile ROM"
Where does it say that all builds are unified starting at Android 6.0? That may be the case for all other carriers, but it is PRETTY obvious, that this does not apply to the T-Mobile build for 6.0.
Click to expand...
Click to collapse
6.0 is one build...I'm pretty sure everyone else that has upgraded by now have already said that...if I take my "sprint" nexus 6 and put a t-mobile sim in...and I have 6.0 after it realizes, hey, I'm on t-mobile...wifi calling will pop up and t-mobile service will work...and before you try to say I'm wrong or t-mobile knows better...why did this work when I tried just that to help someone with the same issue
scryan said:
Your not really making me look like I have been dropped on my head, your making yourself look like a raving lunatic.
I gave you the same answer as simms, other than the fact that I linked to the official support site where the answer marked as correct supports what I said.
Flashing ANY rom is going to require a bootloader unlock, so yes flashing a tmobile rom would require a bootloader unlock.
Other carriers then T-Mobile have a unified build? lol, check your definitions there man
u·ni·fy
ˈyo͞onəˌfī/
verb
past tense: unified; past participle: unified
make or become united, uniform, or whole.
It's not united or uniform if its different for tmobile... the entire basis of a unified build is it's the same for everyone.
This thread is too good. Nothing but multiparagraph rants and personal insults from you about how others have anger issues. :laugh:
Click to expand...
Click to collapse
Yes, I know how to flash an image and/or a ROM, unlocking the bootloader has nothing to do what this conversation, other than I do not want to wipe my device Einstein. Do you know how to SSH into a RHEL Server across a minimally perforated firewall to change jre environments for global profile enabled Linux applications on let's say, an Apache Web Server LBP?
I know how Linux works. Android is child's play.
You are completely ignoring the fact that there is a reason that T-Mobile Nexus 6 devices have NOT been given the green light for Android 6.0.
Really, why do you think that is? If it were such a simple solution, then it wouldn't have been 2 months and no update. Clearly, there are some technical details, that are probably WAY above your intrinsic level of comprehension, that are delaying the release of this image.
If you are too dense to comprehend that, then continuing this conversation is futile.
If anyone has any insight or information as to the delay, feel free to let me know.
Thanks.
A2CKilla said:
6.0 is one build...I'm pretty sure everyone else that has upgraded by now have already said that...if I take my "sprint" nexus 6 and put a t-mobile sim in...and I have 6.0 after it realizes, hey, I'm on t-mobile...wifi calling will pop up and t-mobile service will work...and before you try to say I'm wrong or t-mobile knows better...why did this work when I tried just that to help someone with the same issue
Click to expand...
Click to collapse
Brother, no offense, I'm not following you. The reason Wi-Fi calling pops up when you throw a T-Mobile SIM card into a Sprint phone, is because Wi-Fi calling is baked into Android 5.1.1.
Sorry, not sure what point you are trying to make. You do know that on the Google Developers Factory Images page, there are T-Mobile specific builds for the Nexus 6 right?
Even Verizon users, just started receiving 6.0 in this past week. The only other time this happened was with the Samsung Galaxy Nexus, and we all know what happened there. Exact same thing I am talking about. As a matter of fact, (will link to it later), we have already had an in-depth discussion about this on a different forum on this site. There are in fact different builds for different carriers.
The Universal build WILL work, no one is saying that it won't, but keep doing some research and you will see that many (and I mean many) users have reported incompatibility and/or broken functionality when flashing the Factory Images on their T-Mobile and also Verizon devices.
As far as what you are saying about a T-Mobile SIm card working in a Sprint Nexus 6. I don't think anyone is arguing that. We all know that to be the case, although I can guarantee you that if you put a Verizon SIM card into your Sprint/AT&T/T-Mobile Nexus 6, it will NOT work.
I know because I have Verizon service (for work), and I have tried. That is less about the phone being locked, and more about non Verizon IMEI's being blacklisted. My point is, that we know that the Nexus 6 is unlocked. That is not the question I am asking here.
Android1126 said:
Brother, no offense, I'm not following you. The reason Wi-Fi calling pops up when you throw a T-Mobile SIM card into a Sprint phone, is because Wi-Fi calling is baked into Android 5.1.1.
Sorry, not sure what point you are trying to make. You do know that on the Google Developers Factory Images page, there are T-Mobile specific builds for the Nexus 6 right?
Click to expand...
Click to collapse
For LP yes.
Android1126 said:
Even Verizon users, just started receiving 6.0 in this past week.
Click to expand...
Click to collapse
Yup, VZW took their sweet ass time testing and distributing it too.
Yet check that developer image page... and where is the VZW MM image?
Just because the carrier has not pushed it as an OTA does not mean it's a different build, because M is unified. So even though it took until last week for VZW to push it to their phones.... It's the same unified build that has been out this whole time.
Android1126 said:
As far as what you are saying about a T-Mobile SIm card working in a Sprint Nexus 6. I don't think anyone is arguing that. We all know that to be the case, although I can guarantee you that if you put a Verizon SIM card into your Sprint/AT&T/T-Mobile Nexus 6, it will NOT work.
I know because I have Verizon service, and I have tried. That is less about the phone being locked, and more about non Verizon IMEI's being blacklisted. My point is, that we know that the Nexus 6 is unlocked. That is not the question I am asking here.
Click to expand...
Click to collapse
I have a non VZW phone btw, and on VZW with a VZW sim. It works fine. You need to do your reading on this one, lots of us don't have Verizon issued phones, its only ATT that is carrier locked.
Many people had issues getting VZW to activate their nexus 6, this was not technical as much as it was people bringing their phones to VZW and VZW declining. People also had issues not getting their discount for buying a phone outright, but from early launch you could stick a VZW sim into a nexus 6 and use it
See this droid life article from launch
http://www.droid-life.com/2014/10/31/nexus-6-working-on-verizon-out-of-the-box/
Enough ranting now...
Thread closed
Hey there people
I know this is the Z3 section, couldn't find a Z1... so, in 2 words, i got this xperia Z1 which is password locked and i need to unlock it.
First let me tell you what i do for living, i work in a non profit organization in belgium called "les petit riens" (the little nothings), we do lots of stuff for charity, we have
a guest house for homeless people and also for youngsters in difficulties, we also have a small store where people can buy first need products for a really low price, we receive countless articles from people everyday to later be sold for an affordable price, of course these articles need to be tested or repair beforehand, me personally, i am responsible for the computer & gadgets department, from time to time we receive lots of phones and/or computers that were lost and never claimed by the owner... you may be thinking "but you're a tech guy"... well yes, in short i am, but that doesn't mean i know everything, and that's the reason i am here.
One of the obstacles i face almost everyday, are icloud locked devices and xperia phones, not knowing how android really works, i don't dare to mess around with software i don't really understand.. better ask people with experience on the field.
Fair to say i am only beginning to understand terms like "bootloader" or "rooting", so what i am asking for is for step by step instructions on how to properly unlock these xperia devices.
Needless to say these phones were legally acquired, you may contact sncb in belgium and ask, and if you'd need my credential, i'll be happy to show them in private.
the locked phone is a sony xperia z1 C6903
thank you very much for your time and help, if you got more questions regarding the phone or anything else, please don't hesitate.
cheers
cesarin321 said:
Hey there people
I know this is the Z3 section, couldn't find a Z1... so, in 2 words, i got this xperia Z1 which is password locked and i need to unlock it.
First let me tell you what i do for living, i work in a non profit organization in belgium called "les petit riens" (the little nothings), we do lots of stuff for charity, we have
a guest house for homeless people and also for youngsters in difficulties, we also have a small store where people can buy first need products for a really low price, we receive countless articles from people everyday to later be sold for an affordable price, of course these articles need to be tested or repair beforehand, me personally, i am responsible for the computer & gadgets department, from time to time we receive lots of phones and/or computers that were lost and never claimed by the owner... you may be thinking "but you're a tech guy"... well yes, in short i am, but that doesn't mean i know everything, and that's the reason i am here.
One of the obstacles i face almost everyday, are icloud locked devices and xperia phones, not knowing how android really works, i don't dare to mess around with software i don't really understand.. better ask people with experience on the field.
Fair to say i am only beginning to understand terms like "bootloader" or "rooting", so what i am asking for is for step by step instructions on how to properly unlock these xperia devices.
Needless to say these phones were legally acquired, you may contact sncb in belgium and ask, and if you'd need my credential, i'll be happy to show them in private.
the locked phone is a sony xperia z1 C6903
thank you very much for your time and help, if you got more questions regarding the phone or anything else, please don't hesitate.
cheers
Click to expand...
Click to collapse
Download flashtool, download firmware, flash it wipe data, system, ect. And now like a factory new phone
pikeylfc said:
Download flashtool, download firmware, flash it wipe data, system, ect. And now like a factory new phone
Click to expand...
Click to collapse
hey there, thanks for your response, if you don't mind and have the time, would you care to explain which software exactly i should use ? and also which firmware?
does it depend on something specifically ? or it could be firmware ? and where do i download all that?
thanks so much
there is already a nice guide: http://forum.xda-developers.com/showthread.php?t=2439328
I believe that you are actually only interested in bypassing the user-password lock and then resetting the phone to its default state. If so, there's no need to actually root the phone or to unlock its bootloader.
If so, you can use the Repair function of the Sony PC Companion programme. See instructions here. Using this function will wipe all user data (including the user-password lock) and also flash the phone to the latest stock firmware.
And the Xperia Z1 section is here: http://forum.xda-developers.com/xperia-z1
Hello everyone
just wanted to say a big thank you for all the help !!!!
what i needed was what "hush66" suggested, and so i followed his instructios to a full success i must say, so far i have been able to unluck about 10 devices
i had in stock.
thanks again and happy new year
Do not ask for an ETA
Once the mods start getting onto people for asking, I'll take my dev work off site. I don't want to upset mods and admin over people being impatient.
I've been looking and root isn't available yet for the Snapdragon version. I've created root access for a few devices so far, be it years ago. I want root, so I've decided to start dev work on my own. Can't say how long it will take, or if I will be able to, but anyone that is willing to test or help, feel free to comment and say so, since help would be greatly appreciated. Testers are needed.
First off though, what advancements have been made so far? Several posts I've seen have dead links to data, so to start, I'll need to know what's been done already. No need to reproduce failed outcomes.
Reserved for future links.
drakaina said:
Do not ask for an ETA
Once the mods start getting onto people for asking, I'll take my dev work off site. I don't want to upset mods and admin over people being impatient.
I've been looking and root isn't available yet for the Snapdragon version. I've created root access for a few devices so far, be it years ago. I want root, so I've decided to start dev work on my own. Can't say how long it will take, or if I will be able to, but anyone that is willing to test or help, feel free to comment and say so, since help would be greatly appreciated. Testers are needed.
First off though, what advancements have been made so far? Several posts I've seen have dead links to data, so to start, I'll need to know what's been done already. No need to reproduce failed outcomes.
Click to expand...
Click to collapse
One guy flashed a combination version of the firmware and got the OEM unlock toggle to show on a SM-G960U. It switched on and off but I am not sure if it actually unlocked the bootloader or not. There is a TWRP already ported to the Snapdragon version as well, although only for the Chinese and Hong Kong version, it should work on our device if you can get the bootloader unlocked first. I have been scouring online and in the forums since the phone came out and that's all I nave found thus far. Im sure you already know these things, but I figured I would say it just in case you weren't aware. Hope you get it figured out! Good luck! ?
The only development I've heard of is one user claiming he got a diagnostic boot with SElinux permissive. (In the S9 root dev forum/thread) I also have a source who is NOT trying to be identified publicly because he works for google, but he informed me that "the android O build for SAMSUNG DEVICES, was developed with special instructions in it to automatically kick a KERNEL PANIC , if ANY app NOT on some internal White List attempts to access, modify, or send SU commands through any NOT LISTED app with those permissions granted already." ... now I'm not an Android level programmer, but I'm an old Linux dev/ penetration systems tester (lol) and from what I am gathering is that the patches or whatever that Samsung added to the O.S. also included an encrypted or hidden white list, which he says is VERY small, (as in number of items actually in the list) , but even he said they do not have any access nor knowledge of where they stored this. He did tell me that they delivered an incomplete or infant code for Samsung Snapdragon Model Note 8,9 and s8,9, and it was so crude that not only would it not compile because of missing crap Samsung deliberately did not supply them with... but he said that it was NOT lockable in that state, so Samsung either inserted their own locked kernel and whatever to create this B.S. broke down version of Android that is Root crippled. BUT the only clue he could give me was that "On no level can an E-fuse provide an unbreakable chain of trust, and that if an extreme modded were to actually break down the system board of an S9, they could in theory remove or add some sort of device that would bypass the Qualcomm Secure boot completely!" ... now this ain't a best friend or nothing so truthfully I'm surprised I got this much from him... but I've known who he was and that hes worked for Google nearly 12 years as a developer and software engineer. So I dont know if any of that info helps... but my contribution is that I can get my device (s9+ from Sprint USA Sm-g965U) replaced with little to no hassle, so I'm 100% willing to do any tests u need, providing that you give me at least a basic level of instruction, as to each set of commands or package u want me to flash. I'm pretty android savvy considering it's just a linux derivative... and I know Samsung 100% .. I've had every S - galaxy since day 1 . BUT throwing blind commands at my device that I have 0 understanding of their impact, makes me feel like a squirrel running across the freeway during rush hour! Plz Do me a favor and shoot me a private message and I'll give you my cell number and email so u can reach me quicker when you have something u need tested! Now please people don't berate me if something he said to me was not correct or you have different data to disprove what he said. I literally took notes by hand and had him confirm them, so I'm just the messenger/informant and u gotta realize that as a google employee, he #1 is partially not knowledgeable of ways to exploit the O.S. which is what the hackers come into play for. And make the developers work **** tons harder to FIX the hole the ****ed up in the 1st place! ? Lol... and #2. I did ask about the possibility of a $$$$ number he would take in order to provide an actual Eng-boot like that of the S8, and he said that "Those are developed by each individual corporation after they are provided the build source code", and that "google has no interest in possessing or archiving any such file because the O.S. does not need it to provide a developers version of the O.S., which is as far as Google goes in providing a new system to the companies.... so for something like that, reach out to one of the underpaid factories full of workers and I'm sure they would happily give you what you want for much cheaper than you imagine!" Ok that was very long winded but I wanted to cover all I could because I prob wont check this thread anymore.... plz PM me bro so I can get you my info ... and let's put this Flashing Guinea Pig (me) to work in getting this ***** at least hack rooted or maybe full!!!
Hello, i've just finished reading all above and from what I've read I can tell that not all hopes are lost as well I'm offering my help to be a (TESTER) for any attempts you wanna try, however, please note that I'm NO DEV just a user who would like to his phone rooted ASAP that's all, so please explain the commands that you would give me and the steps. plz PM me so I can get you my contact info
It ain't happening with the known exploits.
Ok, so far I have a few routes I plan to take that have worked on other devices. Working on the first, but not at the moment. The rude comment compelled me to post my own. Devs don't follow old ways of doing things so get that out of your head if you want to think forward, not backwards. I have found what could be an exploit in the rom itself that "might" be the starting point to get root access. This is NOT an ETA but hopefully we can start testing in the next few weeks.
I'll say it now, don't get overly excited a possible exploit has been found. I make no guarantee on it being THE exploit needed. Just be patient, and if you have insight on a way to attack this or another possible exploit, do say so.
If anyone knows of the bootloader partition already having been copied, post a link. I share mine at the moment so I don't always have it around, so any of the bootloader data would help greatly.
drakaina said:
Ok, so far I have a few routes I plan to take that have worked on other devices. Working on the first, but not at the moment. The rude comment compelled me to post my own.
Click to expand...
Click to collapse
I saw no rude comment, just a dose of reality for you, a little thin skinned are we?
You're continuing to be rude and attempting to derail the point of the thread. Meh, I'm getting back to work since it not good to feed trolls.
Pretty sure placeholder threads are not allowed on XDA...
I am making presence known now. I will be watching this closely
Technicly this thread don't even need to exist right now.
drakaina said:
Do not ask for an ETA
First off though, what advancements have been made so far? Several posts I've seen have dead links to data, so to start, I'll need to know what's been done already. No need to reproduce failed outcomes.
Click to expand...
Click to collapse
Myself and a handful of other people involved in us snapdragon s8/s8+/n8+ took a brief crack at it a little while ago to no avail. I don't want to go into too many details on here as 1) Samsung is watching surely and 2) the contents from the peanut gallery get old quick but here are the cliff notes. Feel free to pm me here or on telegram for more details. (Backstory on me, I created samfail which was the first/only n8 root method and the second for the s8/s8+ and the only published one beyond bootloader v1.
- samfail is 100% patched. No known way to modify system
- you can't mix combo boot with stock images anymore. Samsung got wise to that. Figured out how to track it if we can force write a system image
- there is a ton of new system level security because they had to move out of the boot image due to treble. Probably the first big nail in the coffin I'm.
- don't waste your time on the oem unlock toggle in the combo/factory rom. No it doesn't unlock the bootloader. The us snapdragons don't respect it's value outside of turning off frp, but that was with the s8 idk if it is still true on the s9.
- the other poster is right about the anti root thing. It's in the open source kernel code. If anything being exexuted under uid 0 matches a list of common/known root mods/not stuff that is supposed to be there, instant kernel panic. Things like "binary is called BusyBox" are on that list.
This was the point I gave up. Partially because I don't have the device so testing is extremely difficult (I wised up this year and purchased a intl. Snapdragon sm-g9650 which has full oem unlock just like the exy).
In sure there's things in forgetting right now and again, being too transparent here results in root method bring patched faster, hit me up if you want more brain dump
drakaina said:
You're continuing to be rude and attempting to derail the point of the thread. Meh, I'm getting back to work since it not good to feed trolls.
Click to expand...
Click to collapse
Although I have seen a lot worse on these threads, his comment was pretty negative, which is what we do not need in this thread. I wish people would just keep their thoughts to themselves if they have nothing to add to the discussion. I also will test so let me know if there is anything I can do to help.
i also have a g965u and have been trying various mwthods to no avail at this point.. we need new exploits to be found.. all the obvious stuff will not work
It is because of this is why I will never buy another Galaxy phone. I need root.
zzEvilGeniuszz said:
It is because of this is why I will never buy another Galaxy phone. I need root.
Click to expand...
Click to collapse
Just don't buy snapdragon, the Exynos S9s are unlocked
*Detection* said:
Just don't buy snapdragon, the Exynos S9s are unlocked
Click to expand...
Click to collapse
You cannot buy Exynos from a carrier. You have to buy directly from Samsung for that. I know because I requested a Exynos variant. Sprint said they couldn't (or wouldn't) give me one.
edit: nvm not worth it.
zzEvilGeniuszz said:
You cannot buy Exynos from a carrier. You have to buy directly from Samsung for that. I know because I requested a Exynos variant. Sprint said they couldn't (or wouldn't) give me one.
Click to expand...
Click to collapse
i talked to samsung a couple months ago before i got my s9 and they told me they wont sell you one directly with the Exynos. I was going to get the s8 with the exynos if they would of sold me one. They wouldn'ty so i bought a tmobile s9 with my carrier.
has anyone been able to reboot phone into edl mode?
Hello, guys!
Today something came up to my mind and I was wondering if you know anything about this...
A couple of months ago I changed to my actual mobile company (Entel), i was using WOM, but the thing is that I saw in SamMobile that there is an update available days ago for S10 and I can't receive it being in Entel, I'm always checking for new updates but there's nothing, I think that when WOM releases it I will be able to have it, but the question is...
Does anybody know how could I change this? Does it happen in your countries? If I'm registered in their servers as a client I would receive the update, wouldn't I?
Moderator Edit:
Please read the FORUM RULES, particularly Rule #4
vermillion66 said:
Hello, guys!
Today something came up to my mind and I was wondering if you know anything about this...
A couple of months ago I changed to my actual mobile company (Entel), i was using WOM, but the thing is that I saw in SamMobile that there is an update available days ago for S10 and I can't receive it being in Entel, I'm always checking for new updates but there's nothing, I think that when WOM releases it I will be able to have it, but the question is...
Does anybody know how could I change this? Does it happen in your countries? If I'm registered in their servers as a client I would receive the update, wouldn't I?
Click to expand...
Click to collapse
firmware releases are put out incrementally by IMEI, but in the interim, if you want to update manually, you can. And yes, this also happens in the USA. I would not recommend downloading the firmware directly from sammobile.com/fimwares tho only because they take such a long time. Samfirm and Frija are both tools that download firmware literallt 5 times faster. it takes about 2 hours when diwnloading directly from sammobile vs about 20 min on samfirm or frija (ive used both many times and theyre literally the same)