Related
Hi all,
I have a HTC that when I bought it, they SAID it should have been unlocked but I don't know if that means my bootloader is unlocked or something else. how can I tell if my model is unlocked model (model is just HTC 10 and I don't have any provider software installed on it either) ... I mainly ask as Android 7 was released to unlocked HTC 10 last year but I got no OTA notifications that it is ready for me.
Also if this doesn't mean that the bootloader unlocked and I need to go through it at HTCDev, then I believe this will wipe the phone... so I need to backup my stuff before I can unlock the bootloader, so I can root my phone, so I can install my backup stuff (Titanium Backup) any help on this one? i'm used to Samsung so the changes in how things work I'm still getting my head around.
Nobody knows? Is this the correct part of the forums to ask this sort of question? I didn't want to post in the wrong section and this seemed to be the closest fit.
aerospyke said:
Hi all,
I have a HTC that when I bought it, they SAID it should have been unlocked but I don't know if that means my bootloader is unlocked or something else. how can I tell if my model is unlocked model (model is just HTC 10 and I don't have any provider software installed on it either) ... I mainly ask as Android 7 was released to unlocked HTC 10 last year but I got no OTA notifications that it is ready for me.
Also if this doesn't mean that the bootloader unlocked and I need to go through it at HTCDev, then I believe this will wipe the phone... so I need to backup my stuff before I can unlock the bootloader, so I can root my phone, so I can install my backup stuff (Titanium Backup) any help on this one? i'm used to Samsung so the changes in how things work I'm still getting my head around.
Click to expand...
Click to collapse
When you buy a phone and if seller says that phone is unlocked it usually means "carrier/sim unlocked". Your phone might be carrier unlocked, but bootloader unlock is different. When you unlock bootloader than phone gets wiped. Google servers usually backup your apps and some data, but videos/music/photos I backup on my PC by connecting phone to a computer and copying files to a folder.
If you bought directly from HTC w/o purchasing through a carrier (such as Sprint, AT&T, Verizon), then you have an "Unlocked Model". That's completely different from having an unlocked bootloader, which is not necessary to get the Nougat update. If you have an unlocked (carrier-free) HTC 10, then you should be able to get the update. I restored mine to stock, and was able to update to 7.0. It's possible that it's not available in your country yet, or that there's some funny software glitches occurring.
Hope that helps!
Thanks all for the confirmation. So from that I do know from when I got my phone, which was only 4 weeks ago, and no modifications to it whatsoever
a) my phone is carrier unlocked
b) I need to unlock my bootloader but to do that I need to backup my app data, Google didn't backupt he app data when I migrated phones, so all my apps were empty and brand new when it all restored to my new phone... oh well.
c) whilst i SHOULD be eligible for nougat as I have a carrier unlocked HTC 10, perhaps it isn't available in Australia for HTC yet. My colleague who has a pixel XL is still rubbing it in my face that he has 7.1.1 already
Thanks
aerospyke said:
Thanks all for the confirmation. So from that I do know from when I got my phone, which was only 4 weeks ago, and no modifications to it whatsoever
a) my phone is carrier unlocked
b) I need to unlock my bootloader but to do that I need to backup my app data, Google didn't backupt he app data when I migrated phones, so all my apps were empty and brand new when it all restored to my new phone... oh well.
c) whilst i SHOULD be eligible for nougat as I have a carrier unlocked HTC 10, perhaps it isn't available in Australia for HTC yet. My colleague who has a pixel XL is still rubbing it in my face that he has 7.1.1 already
Thanks
Click to expand...
Click to collapse
c) Yeah Nougat is only available for U.S Unlocked (and tmobile as of today) thus far.
Tarima said:
c) Yeah Nougat is only available for U.S Unlocked (and tmobile as of today) thus far.
Click to expand...
Click to collapse
Rats..... i'll just keep waiting, or wipe my device unlocking the bootloader so I can flash a custom ROM like Viper or the like. Decisions. Wonder when the rest of the world will get the update
aerospyke said:
Rats..... i'll just keep waiting, or wipe my device unlocking the bootloader so I can flash a custom ROM like Viper or the like. Decisions. Wonder when the rest of the world will get the update
Click to expand...
Click to collapse
Australia is usually last to get the update.
Earlier today I installed Magisk, but then found that some apps I frequently use (Samsung Pay being one of them) were no longer working so I decided to revert back to Android O, remove Magisk etc. and basically go back to stock. I flashed the factory images using fastboot, then sent the command to lock the bootloader. Strangely when I tried "fastboot flashing lock_critical" it told me the bootloader was locked, but when I entered "fastboot flashing lock" it went through and restarted.
This is where I get stuck, when the phone boots it shows a message about the device being corrupt. If I press the power button, it just then goes to the white screen with Google in the middle and does nothing else.
What should I do to get my phone back to factory specs?
naiku said:
Earlier today I installed Magisk, but then found that some apps I frequently use (Samsung Pay being one of them) were no longer working so I decided to revert back to Android O, remove Magisk etc. and basically go back to stock. I flashed the factory images using fastboot, then sent the command to lock the bootloader. Strangely when I tried "fastboot flashing lock_critical" it told me the bootloader was locked, but when I entered "fastboot flashing lock" it went through and restarted.
This is where I get stuck, when the phone boots it shows a message about the device being corrupt. If I press the power button, it just then goes to the white screen with Google in the middle and does nothing else.
What should I do to get my phone back to factory specs?
Click to expand...
Click to collapse
Why on earth did you lock the bootloader? But oh well. Try unlocking it again, then fastboot 8.1 again. No need to worry about data anymore since you've been wiped! ?
I locked it again as Samsung Pay kept crashing saying I had a modified system, since I had already flashed back to factory 8.1 I assumed that was the reason why, hence locking the bootloader. I was actually in the middle of flashing 8.1 again when you replied, did exactly that, unlocked bootloader, flash-all in fastboot and I am back to setting it up again.
Going to leave the bootloader unlocked for now, but I do want to be able to use Samsung Pay so if that means locking it will likely go through the whole ordeal again at some point!!
naiku said:
I locked it again as Samsung Pay kept crashing saying I had a modified system, since I had already flashed back to factory 8.1 I assumed that was the reason why, hence locking the bootloader. I was actually in the middle of flashing 8.1 again when you replied, did exactly that, unlocked bootloader, flash-all in fastboot and I am back to setting it up again.
Going to leave the bootloader unlocked for now, but I do want to be able to use Samsung Pay so if that means locking it will likely go through the whole ordeal again at some point!!
Click to expand...
Click to collapse
Well glad your up and running. Outa curiosity, did you run the fastboot flashing unlock_critical when you first unlocked the bootloader? ?
Yep, in fact I think I only ran the unlock critical. Did both this time, oddly though unlock critical did nothing initially, so did just unlock, then tried unlock critical again and it reported being unlocked.
In the middle of setting everything up now, Samsung Pay working with the unlocked bootloader. Must have been something with root, even after removing it, that screwed it up previously.
naiku said:
Yep, in fact I think I only ran the unlock critical. Did both this time, oddly though unlock critical did nothing initially, so did just unlock, then tried unlock critical again and it reported being unlocked.
In the middle of setting everything up now, Samsung Pay working with the unlocked bootloader. Must have been something with root, even after removing it, that screwed it up previously.
Click to expand...
Click to collapse
Yep, root is usually always the culprit with pay type apps if magisk hide isn't working properly. But hey, at least your happy now ?
Yup, I had tried magisk hide and it did not work, so (wrongly) assumed the bootloader unlocked was the problem.
Thankfully all good now, was definitely a little worried earlier this evening!
naiku said:
Yep, in fact I think I only ran the unlock critical. Did both this time, oddly though unlock critical did nothing initially, so did just unlock, then tried unlock critical again and it reported being unlocked.
In the middle of setting everything up now, Samsung Pay working with the unlocked bootloader. Must have been something with root, even after removing it, that screwed it up previously.
Click to expand...
Click to collapse
How did you get SP to work on a non Samsung phone? Does MST work or does that take special hardware?
Sent from my SM-T820 using Tapatalk
dew.man said:
How did you get SP to work on a non Samsung phone? Does MST work or does that take special hardware?
Sent from my SM-T820 using Tapatalk
Click to expand...
Click to collapse
Pay works fine with no issues, I did nothing other than install the app while on O, then it still works on P DP3.
Not sure what MST is, so can't help there.
Are you sure you're talking about SAMSUNG pay, and not Android Pay? As far as I know (and just checked again), it' s not available from google, only from the galaxy store.
MST is the (supposedly) proprietary Samsung technology that allows you to pay with your phone at older terminals that do not have NFC. From what I understand, they have a way to communicate with magnetic card readers enabling their solution to work pretty much everywhere.
dew.man said:
Are you sure you're talking about SAMSUNG pay, and not Android Pay? As far as I know (and just checked again), it' s not available from google, only from the galaxy store.
MST is the (supposedly) proprietary Samsung technology that allows you to pay with your phone at older terminals that do not have NFC. From what I understand, they have a way to communicate with magnetic card readers enabling their solution to work pretty much everywhere.
Click to expand...
Click to collapse
100% sure it's Samsung Pay. I will say though that I use it on my watch, not the phone itself. Had to double check though, looks like we are both right. I don't have Samsung Pay on my phone as its own app, but it is used as part of the Gear app in order to set it up on my watch. During set up with the phone rooted, the watch Samsung Pay setup, on the phone, was crashing. Sorry for any confusion.
Gotta say I am glad the watch works with it. I would not have been happy if I had lost that functionality switching from the S7 Edge to the Pixel.
Soooo, after enabling dev options and enabling oem unlock. download mode wont allow me to unlock the bootloader itself, theres no option for volume up to unlock. Any ideas / work arounds
If you recently got your phone there may be the 7 day block on it. Which basically disables you from unlocking the phone for 7 days. There is a workaround though where you set the time 8 days behind, check for update, restart the phone, change the time back to the correct time, and then oem unlock should be available under Developer Options!
my phone samsung a50 is stuck on boot logo (SAMSUNG), flashing, wipe data reset, but it cant. Same problems stuck on samsung logo. How did i fix?
Another thing to note is that phones in America likely have locked bootloaders, especially ones on Verizon. If you have a device from a US carrier other than that it should be fine...
AjBeld said:
If you recently got your phone there may be the 7 day block on it. Which basically disables you from unlocking the phone for 7 days. There is a workaround though where you set the time 8 days behind, check for update, restart the phone, change the time back to the correct time, and then oem unlock should be available under Developer Options!
Click to expand...
Click to collapse
If your phone is a US Variant (your phone model number: SM-A505U) then it can't be unlocked. I'm guessing your's is the SM-A505U?
Hello everyone. I installed the developer preview for Android R and i'm over it. I wanna go back to stock and I tried sideloading the OTA image and I get this message
update package is older than the current build. Downgrade not allowed.
My bootloader is locked so I can't flash the image through fastboot. I need help.
May update released might want to try that one.
hedgehogmd said:
May update released might want to try that one.
Click to expand...
Click to collapse
I tried but it didn't work.
I was on the phone with t-mobile to see if they could unlock my phone but we're having issues with the unlock app.
I miss the days of typing in a code and getting your phone unlocked.
As you have just learned, the developer previews are not the same as beta releases. With the beta releases, you can "quit" the beta program and have the old OS version reinstalled via an OTA update The preview releases have no such OTA reset ability. Therefore, you should not participate in the preview releases unless your phone is unlocked.
If the May release doesn't let you revert back, then I think the only option you will have is to wait until the beta is released. Join the beta and have it installed on your phone and then quit the beat and hope that the OTA update takes you back to stock Android 10. In theory I think it will.
you should use the flashall.bat script if you're installing the factory image. Though this will earase data. Just make sure you have USB debugging on
EDIT: I think you should still be able to unlock your bootloader
EDIT2: After reading a bit more I see that on carrier specific devices, OEM unlocking is greyed out until the phone is sim unlocked. But after you get the app working everything should work fine. Did you use another sim thats not from T Mobile?
RicardoSal24 said:
you should use the flashall.bat script if you're installing the factory image. Though this will earase data. Just make sure you have USB debugging on
EDIT: I think you should still be able to unlock your bootloader
EDIT2: After reading a bit more I see that on carrier specific devices, OEM unlocking is greyed out until the phone is sim unlocked. But after you get the app working everything should work fine. Did you use another sim thats not from T Mobile?
Click to expand...
Click to collapse
I put a different sim on the phone and it worked but it's b/c I did the temporary unlock. After 30 days the phone will be locked again. The phone won't let me unlock the bootloader unless it's a permanent unlock. The problem is I'll have to wait 30 days for the phone to re-lock. I wish t-mobile could just give me a code...
Lucky for me this phone isn't my daily driver but I wanted to revert to stock android b/c I got an invite to test out the Ratio launcher by Blloc. It's incompatible with Android R.
chivamex10 said:
I put a different sim on the phone and it worked but it's b/c I did the temporary unlock. After 30 days the phone will be locked again. The phone won't let me unlock the bootloader unless it's a permanent unlock. The problem is I'll have to wait 30 days for the phone to re-lock. I wish t-mobile could just give me a code...
Lucky for me this phone isn't my daily driver but I wanted to revert to stock android b/c I got an invite to test out the Ratio launcher by Blloc. It's incompatible with Android R.
Click to expand...
Click to collapse
Your best bet would be to just wait until you can permanently unlock it. I got mine from best buy and only recently did I bother with flashing roms on it.
I have a TMO device and had a temp unlock, and obviously it doesn't allow oem unlocking to be enabled. I DM'd TMOhelp on twitter and was able to get a permanent unlock there. They told me that I'd have to wait for my temp unlock to expire before I could perm unlock, but I didn't. If you have trouble with the app, just clear the storage and cache data for it. Once it is actually perm unlocked you'll immediately get a notification and be prompted to restart the phone. After that you should see oem unlocking enabled in dev options and be able to hit bootloader and unlock it.
Hi all, I just recently purchased a Google pixel 6 pro new for cheap coming from a Galaxy S9. I was wondering if there are any downsides to unlocking the bootloader? Like losing some kind of functionality or DRM or Widevine certification, etc. forever? Switching from a brand that has everything locked down I'm used to losing functionality lol
Teet1 said:
Hi all, I just recently purchased a Google pixel 6 pro new for cheap coming from a Galaxy S9. I was wondering if there are any downsides to unlocking the bootloader? Like losing some kind of functionality or DRM or Widevine certification, etc. forever? Switching from a brand that has everything locked down I'm used to losing functionality lol
Click to expand...
Click to collapse
As far as I know, only rooting will have disadvantages, <ie> Banking and Google Pay. My Bank won't allow rooted phones to use its app.
Disadvantages to unlocking the bootloader (unlocking the bootloader can be done without rooting after):
It may be possible that some rare banking or other sensitive apps will notice that your bootloader is unlocked and refuse to fully function.
If you're not very careful, you could accidentally either temporarily or permanently brick your device by flashing the wrong thing.
Truthfully, most of the time, having the bootloader unlocked (or at least OEM unlocking enabled) gives you MORE recovery options if something bad happens (such as you flash Android 20 Beta 1 and it bricks your phone).
Having the bootloader unlocked is by its nature less secure, so if your device gets stolen, there may be a greater possibility a hacker can break into your phone and/or get valuable data out of your account or cause greater havoc. I've never had a phone stolen, although I did find someone's stolen Sprint HTC 4G (if I remember the model correctly) one time, which I arranged to return to the owner by calling Sprint. I assume the person who stole the phone gave up on being able to easily use the stolen phone, since Sprint erased and locked down the phone remotely.
Disadvantages to being rooted:
Have to manually update anytime you want the new month's update.
Have to jump through a few hoops to make sure almost all banking/sensitive apps don't realize that you're rooted. The method may change from time to time due to changes in Android, so there's always the possibility any time you flash an update to Android on your device that you'll have to wait for and flash an update to root-hiding methods.
Advantages of being rooted: Well, you know, there are tons.
Good luck!
roirraW edor ehT said:
Disadvantages to unlocking the bootloader (unlocking the bootloader can be done without rooting after):
It may be possible that some rare banking or other sensitive apps will notice that your bootloader is unlocked and refuse to fully function.
If you're not very careful, you could accidentally either temporarily or permanently brick your device by flashing the wrong thing.
Truthfully, most of the time, having the bootloader unlocked (or at least OEM unlocking enabled) gives you MORE recovery options if something bad happens (such as you flash Android 20 Beta 1 and it bricks your phone).
Having the bootloader unlocked is by its nature less secure, so if your device gets stolen, there may be a greater possibility a hacker can break into your phone and/or get valuable data out of your account or cause greater havoc. I've never had a phone stolen, although I did find someone's stolen Sprint HTC 4G (if I remember the model correctly) one time, which I arranged to return to the owner by calling Sprint. I assume the person who stole the phone gave up on being able to easily use the stolen phone, since Sprint erased and locked down the phone remotely.
Disadvantages to being rooted:
Have to manually update anytime you want the new month's update.
Have to jump through a few hoops to make sure almost all banking/sensitive apps don't realize that you're rooted. The method may change from time to time due to changes in Android, so there's always the possibility any time you flash an update to Android on your device that you'll have to wait for and flash an update to root-hiding methods.
Advantages of being rooted: Well, you know, there are tons.
Good luck!
Click to expand...
Click to collapse
Thank you! i've been in the game for a while so I know the pros/cons of rooting and unlocking. I just didnt know if there were any device specific downsides on the pixel 6 pro, but it seems its just the usual stuff. Coming from a locked down brand, this is very liberating!
Teet1 said:
Thank you! i've been in the game for a while so I know the pros/cons of rooting and unlocking. I just didnt know if there were any device specific downsides on the pixel 6 pro, but it seems its just the usual stuff. Coming from a locked down brand, this is very liberating!
Click to expand...
Click to collapse
Cool, you're welcome. Yep, I fooled with a Sony phone once. Was extremely disappointing that it gimped the camera on purpose if you unlocked the bootloader using their official means to do so. And for a while with the bootloader unlocked but not rooted, I still received OTA updates just fine, but then suddenly they stopped allowing OTAs to download and install actually over the air - had to use XperiFirm to download and then flash them manually.
It's getting harder to pass various integrity checks for Play, banking apps, and GPay. And now device integrity. You have to consciously maintain all of these.