So I'm unboxing my xl in Germany. I know the bootloader can be unlocked. I want to flash the oem os from the Google.developer site. Don't want to have to wait for t-mobile to approve updates from Google first. Here are my question 's
Idiot guide to ulocking the bootloader. I know I need to do something with adb. Dow loaded fastboot and adb to my PC
Which Rom should I flash. There are 3 different marlin Roms available. All with a different letter at the end.
Sorry for the noob questions.
Thanks
As this is a developer forum I guess we can expect you to use at least the search engine for bootloader unlocking and flashing the firmware,ain't we?
For now everything looks like Deutsche Telekom didn't change anything at the running firmware and you're good to go by doing nothing at all but unlocking the bootloader.
Yes I searched and think I figured out the bootloader part. I was just wanting to make sure I wasn't overthinking it.
With that being said, I've also researched that they haven't changed anything firmware wise. Yet the community still says I wouldn't get the updates released from Google until tmobile released them....
So to complete the noob mayhem
If I'm not flashing a new firmware why am I unlocking the bootloader .....
I'm lost. Lol
I also got my device from the Deutsche Telekom and I'll just wait until the first Majorupdate (probably Android O) from Google. If the Telekom wants to do their "special quality assurance whatever thing" and need x months to released the update, I can still flash a factory image.
silencertk said:
Yes I searched and think I figured out the bootloader part. I was just wanting to make sure I wasn't overthinking it.
With that being said, I've also researched that they haven't changed anything firmware wise. Yet the community still says I wouldn't get the updates released from Google until tmobile released them....
So to complete the noob mayhem
If I'm not flashing a new firmware why am I unlocking the bootloader .....
I'm lost. Lol
Click to expand...
Click to collapse
Some people believe if you unlock the bootloader, then your phone ever fails to boot, say after a bad flash, then you are not locked out from being able to reflash your phone to recover it. If your phone ever fails to boot, and the bootloader is still locked, you will not be able to unlock it to flash it.
I choose to leave my bootloader locked until I know I'm going to reflash a factory image (I typically do for a major release). I can still flash OTA updates through adb. Plus I'm reading that Android Pay is disabled when the bootloader is unlocked (that's a future for me here in Canada).
Read around and make your own decision.
Ahhhhh makes sense now. I'm expecting the tap to wake ota update to be out pretty son. So......... no idea
But thanks for clatyring things a bit more. So maybe I just won't mess with it for right now.
Still does anyone know what the difference between the three different marlin versions are ?
Afaik there are two hardwareversions: One is the US version which supports CDMA Bands and the other is the international version without CDMA.
Related
@4m8 since you are the only guy here who knows best about HTC Desire 300.
Well my friend gave his Desire 300 to me for repair. i thought its going to be easy as like 1,2,3. but guess i was wrong.
I tried several options already.
USB DEBUGGING might be off as well since my friend doesnt know about flashing or unlocking bootloaders. i cant unlock the bootloader i think.
Its S-ON. (Dont know what it actually means).
I tried going to recovery but it shows me a PHONE with A RED ''DOWNLOAD MODE ARROW'' i think recovery is corrupted?
i tried already flashing boot.img and recovery.img over FASTBOOT. but it says ''failed remote signature verify fail''. its just isnt like my sony device which says OKAY all the time lol. those two files were found on a Google drive website.
i have no other options left to revive this phone.
Help will be a very good option :good: thanks in advance.
Well i read a lot of sites which says stuck at boot. and i cant find a Official Stock firmware for this device. is it that HTC didnt released one?
That sounds really bad. So let's recap to see if I understand your situation correctly:
Phone doesn't boot, can't enter recovery and will only load the bootloader. (b-loader status is S-ON Locked)
Now unless you are able to unlock the bootloader (which you aren't as you have stated) there is no way to flash a custom recovery.
The locked bootloader will prevent it because it requires anything you want to flash to be signed by HTC.
The only way out is to flash an actual official update by HTC which afaik is not available for this device.
To make matters worse, if the phone is branded you couldn't even revive it this way because some providers, like mine, actually force HTC
to prevent those phones from flashing an official HTC update that is not branded.
But there is a bright side to your situation. Since you weren't able to unlock the bootloader your friends warenty should still be intact.
And even if this was a branded phone try to claim a replacement from the manufacturer, that way you might have the chance to get
an unbranded device in return for the trouble you and your friend had to endure. :fingers-crossed:
Sorry if I had to shatter the last piece of hope that you were clinging on to but without an unlocked bootloader the only option that
remains is getting a replacement or begging HTC to release an update or the version that is installed by default as a RUU exe
PS:
Just to be certain, you did try the factory reset option in the bootloader before giving up, right?
4m8 said:
That sounds really bad. So let's recap to see if I understand your situation correctly:
Phone doesn't boot, can't enter recovery and will only load the bootloader. (b-loader status is S-ON Locked)
Now unless you are able to unlock the bootloader (which you aren't as you have stated) there is no way to flash a custom recovery.
The locked bootloader will prevent it because it requires anything you want to flash to be signed by HTC.
The only way out is to flash an actual official update by HTC which afaik is not available for this device.
To make matters worse, if the phone is branded you couldn't even revive it this way because some providers, like mine, actually force HTC
to prevent those phones from flashing an official HTC update that is not branded.
But there is a bright side to your situation. Since you weren't able to unlock the bootloader your friends warenty should still be intact.
And even if this was a branded phone try to claim a replacement from the manufacturer, that way you might have the chance to get
an unbranded device in return for the trouble you and your friend had to endure. :fingers-crossed:
Sorry if I had to shatter the last piece of hope that you were clinging on to but without an unlocked bootloader the only option that
remains is getting a replacement or begging HTC to release an update or the version that is installed by default as a RUU exe
PS:
Just to be certain, you did try the factory reset option in the bootloader before giving up, right?
Click to expand...
Click to collapse
Yes i did. Factory reset. But still no luck.
Yes, i cant enter recovery as well.
Well it actually started ones it told me "Process System Not Responding". And on that point i knew the system files are corrupted.
My friend told me, he left the phone in deep sleep after that it didnt turned on again.
Thanks for your help @4m8 :laugh: :good: (IT ISNT MINE SO I DONT HAVE A PROBLEM) I will give this phone back to my friend.
*FACEPALM TO HTC FOR NOT RELEASING A OFFICIAL FIRMWARE*
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.
So Moto One Action keeps on surprising every now and then. The latest addition to it is the System Integrity is Compromised message. This is how I end up doing so:
https://photos.app.goo.gl/8Q5xZXTzGWGVMZX48
Unlocked the device's bootloader.
Rooted the device successfully using Magisk patched boot image and Moto One Vision's vbmeta file.
Then I had to unroot my device (for some reason), so flashed the stock firmware using Moto Smart Assistant Tool. But kept the device's bootloader in an unlocked state.
Now I have a stock ROM on my device, unrooted without any modification to the /system partition. The only modification is the unlocked bootloader.
Then I went to System > Advanced > System Updates and then got greeted with the message that I am no longer eligible for software updates. Although not an issue as I could still flash the stock firmware by one way or the other, I am just curious to know whether it is indeed a result of an unlocked bootloader or not. All the users who have unlocked their bootloader kindly let me know in the comments whether they have the same message or not. Thanks in advance
binary**# said:
So Moto One Action keeps on surprising every now and then. The latest addition to it is the System Integrity is Compromised message. This is how I end up doing so:
https://photos.app.goo.gl/8Q5xZXTzGWGVMZX48
Unlocked the device's bootloader.
Rooted the device successfully using Magisk patched boot image and Moto One Vision's vbmeta file.
Then I had to unroot my device (for some reason), so flashed the stock firmware using Moto Smart Assistant Tool. But kept the device's bootloader in an unlocked state.
Now I have a stock ROM on my device, unrooted without any modification to the /system partition. The only modification is the unlocked bootloader.
Then I went to System > Advanced > System Updates and then got greeted with the message that I am no longer eligible for software updates. Although not an issue as I could still flash the stock firmware by one way or the other, I am just curious to know whether it is indeed a result of an unlocked bootloader or not. All the users who have unlocked their bootloader kindly let me know in the comments whether they have the same message or not. Thanks in advance
Click to expand...
Click to collapse
Yeah you need locked bootloader for OTA. Same on One Vision.
Magisk will hide the unlocked status while you're rooted so that you can check for OTA, but I believe it will fail to install during update. Never tyried but that's how it is on Motorola One and One Power.
fastboot flash if you're unlocked and want to update.
Hey, sorry if I am wrong but I highly doubt this claim of yours: "you need a locked bootloader for OTA". True to my knowledge, I don't think any OEM really blocks OTA on an unlocked bootloader device. Until we modify system files, we are safe to get OTA updates. That's what I always knew and every time it stood correct. Isn't it?
binary**# said:
Hey, sorry if I am wrong but I highly doubt this claim of yours: "you need a locked bootloader for OTA". True to my knowledge, I don't think any OEM really blocks OTA on an unlocked bootloader device. Until we modify system files, we are safe to get OTA updates. That's what I always knew and every time it stood correct. Isn't it?
Click to expand...
Click to collapse
I don't know about all oem's but I believe samsung blocks ota if bootloader is unlocked.
I read somewhere in G7 forum that Moto support had told that OTA is disabled on that device if you're on unlocked bootloader, so I guess Moto changed their policy about that too.
tys0n said:
Yeah you need locked bootloader for OTA. Same on One Vision.
Magisk will hide the unlocked status while you're rooted so that you can check for OTA, but I believe it will fail to install during update. Never tyried but that's how it is on Motorola One and One Power.
fastboot flash if you're unlocked and want to update.
Click to expand...
Click to collapse
tys0n said:
I don't know about all oem's but I believe samsung blocks ota if bootloader is unlocked.
I read somewhere in G7 forum that Moto support had told that OTA is disabled on that device if you're on unlocked bootloader, so I guess Moto changed their policy about that too.
Click to expand...
Click to collapse
Not sure about Samsung, but was going through Motorola's official blog, and this is what they have to say:
"Unlocking your bootloader does not affect your eligibility to receive over-the-air (OTA) upgrades from Motorola."
Anyways, thanks for your inputs.....
binary**# said:
Not sure about Samsung, but was going through Motorola's official blog, and this is what they have to say:
"Unlocking your bootloader does not affect your eligibility to receive over-the-air (OTA) upgrades from Motorola."
Anyways, thanks for your inputs.....
Click to expand...
Click to collapse
Oh I see. I don't know then.
You could ask here:
https://forums.lenovo.com/t5/motorola-one-action/bd-p/motorola_one_action_en
They should be able to give a proper answer.
I got a XT2013-4 US - Unlocked boot loader, but the root method doesn't work for the US Firmware (Hear the EU Firmware works for someone in Canada) but I am unable to check for updates being fully stock, unrooted, and only an unlocked bootloader so yes if the OS can read that the bootloader is unlocked then it won't let you check for updates (At least on the US Firmware) but then we aren't Android One though on the XT2013-4
If you are on Stock Firmware, unrooted but your Bootloader is Unlocked, you'll not get any OTA despite the Motorola Support page you've posted (It might be old information, just look the phone they used on the top).
Is it possible to relock it?
ReConfirmed: Official OTA Updates is possible after Unlocked Bootloader.
Just to reiterate the facts (in response to #2 and #8), I guess my assumption was well and truly correct. This is because I did end up receiving an OFFICIAL OTA update from Motorola, a few days back. And at this point, my BOOTLOADER IS STILL UNLOCKED! The first image attached below shows the OTA update notification as well as the proof that my Bootloader is unlocked. The second one provides details about that OTA.
binary**# said:
Just to reiterate the facts (in response to #2 and #8), I guess my assumption was well and truly correct. This is because I did end up receiving an OFFICIAL OTA update from Motorola, a few days back. And at this point, my BOOTLOADER IS STILL UNLOCKED! The first image attached below shows the OTA update notification as well as the proof that my Bootloader is unlocked. The second one provides details about that OTA.
Click to expand...
Click to collapse
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
tys0n said:
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
Click to expand...
Click to collapse
No, my device isn't rooted. The only modification is the unlocked bootloader. I did this when I saw enrolled users getting beta Android 10 updates for Moto One Power. Since One Action has released almost a year after Power, I thought the soak test would just be around the corner for our device as well. But here we are with One Power receiving Stable Android 10 update, and there is no news of the same for our device. I have got myself enrolled in the MFN and just keeping my fingers crossed.
binary**# said:
No, my device isn't rooted. The only modification is the unlocked bootloader.
Click to expand...
Click to collapse
Ok, thanks. That's intresting.
tys0n said:
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
Click to expand...
Click to collapse
One more doubt. I tried the root hide via Magisk for some apps like Google Pay or Pokemon Go and it worked pretty well. But could it trick OEMs as well into thinking the device is unrooted, so that the device may receive OTA updates? I guess probably not, but need some more weight on this opinion.
It's possible to relock the bootloader and get ota functionality back.. just use 'fastboot oem lock' command and then reflash the original firmware..
aditya7286 said:
It's possible to relock the bootloader and get ota functionality back.. just use 'fastboot oem lock' command and then reflash the original firmware..
Click to expand...
Click to collapse
Bootloader Locking/Unlocking has nothing to do while receiving OTAs. As I have mentioned in my other post, I have already received Android 10 OTA on an unlocked bootloader. And as far as the response to my own question goes, it was regarding whether one could hide root from the system as we do for Google Pay and get OTAs. The answer is nopes. I tried hiding root from all the necessary files related to Motorola's system OTA via Magisk but didn't get the update. As soon as I unrooted, BOOM the Android 10 update was right there!
Anyways thanks for your response
Unlocking bootloader on its own does not lead to that message. So I'm guessing it's probably something specific to that ROM, or....something else entirely.
arsradu said:
Unlocking bootloader on its own does not lead to that message. So I'm guessing it's probably something specific to that ROM, or....something else entirely.
Click to expand...
Click to collapse
binary**# said:
Bootloader Locking/Unlocking has nothing to do while receiving OTAs. As I have mentioned in my other post, I have already received Android 10 OTA on an unlocked bootloader. And as far as the response to my own question goes, it was regarding whether one could hide root from the system as we do for Google Pay and get OTAs. The answer is nopes. I tried hiding root from all the necessary files related to Motorola's system OTA via Magisk but didn't get the update. As soon as I unrooted, BOOM the Android 10 update was right there!
Anyways thanks for your response
Click to expand...
Click to collapse
I am getting same thing on my moto g8 plus. just flashed omni and now when i returned the device shows this message.
methuselah said:
I am getting same thing on my moto g8 plus. just flashed omni and now when i returned the device shows this message.
Click to expand...
Click to collapse
You mean "System Integrity Compromised" or something else?
Omni, if we're talking about OmniROM, is a custom, pre-rooted ROM, right? So...maybe that's why.
Interesting though that people with stock ROM, who only unlocked the bootloader (no root) are getting the same message.
Personally, I never rooted this phone and I'm not planning to. Also never seen that message on my phone. However, it was bootloader unlocked and now it's back to locked again.
So... For custom ROMs I can understand why it would show you this. For stock ROM with no root, that doesn't make much sense to me. But maybe I'm missing something.
Sent from my motorola one action using Tapatalk
arsradu said:
You mean "System Integrity Compromised" or something else?
Omni, if we're talking about OmniROM, is a custom, pre-rooted ROM, right? So...maybe that's why.
Interesting though that people with stock ROM, who only unlocked the bootloader (no root) are getting the same message.
Personally, I never rooted this phone and I'm not planning to. Also never seen that message on my phone. However, it was bootloader unlocked and now it's back to locked again.
So... For custom ROMs I can understand why it would show you this. For stock ROM with no root, that doesn't make much sense to me. But maybe I'm missing something.
Sent from my motorola one action using Tapatalk
Click to expand...
Click to collapse
The issue in brief.
Well the thing is i have again flashed back stock that with blankflash file. Before april update i had locked bootloader. But now nothing is happening. As soon as i flash stock ROM(clean stock) and relock the bootloader, the phone just says it is corrupted. But at the same time when i unlock the boot loader it boots.
Last I read, the U and the U1 were still locked and unable to be unlocked because the major cell carriers make the cell phone makers their little b****** and won't let the manufacturers make US versions of phones that can be unlocked. Are we still screwed at being able to unlock the BL on the US versions of these phones, or has any progress been made on this?
BriMan83 said:
Last I read, the U and the U1 were still locked and unable to be unlocked because the major cell carriers make the cell phone makers their little b****** and won't let the manufacturers make US versions of phones that can be unlocked. Are we still screwed at being able to unlock the BL on the US versions of these phones, or has any progress been made on this?
Click to expand...
Click to collapse
You can check this thread:
[CLOSED] Rick's Rom DUB7 SM-G986U1 Safe Update To One UI 3.1
First, I am not responsible to what happens after you flash this. If your phone dose not work afterwords it is your own doing. I didn't force you to flash it... Here is a pretty much stock ROM for the SM-G986U1 or U that I use as my daily...
forum.xda-developers.com
There are links to unlock method available, but one is only possible on older firmware and the other leads to a paid unlock service.
If you have further questions, best to ask in the corresponding thread directly.
I've had my eye on this phone for a bit now, and if all is good, I'm going to get one next weekend.
Some disturbing news though, it appears that unlocking the bootloader will completely kill the cameras. And the only way to get them functional again, is to lock the bootloader again.
SO, I guess this means that recovery, root, or anything else that requires modifiying the system in any way, will kill the use of the cameras?
Is it possible to unlock, root and do whatever, then relock the bootloader and get cameras back while still having root?
The 90% people on this community first what learn ro do is to unlock bootloader. You think that they all dont need camera or..
How is that even possible?
Once when you unblock bootloader you can do what you want, flash custom rom, custom recovery, custom Kernel. Magisk. Magisk modules..
But when you lock it ,and something got wrong ,you get hard brick phone. Bootloader must ne unlock until you use root and etc..
Camera have nothing to do with unlocking and working perfectly. I dont know who say to you ...or make a joke
Btw what phone you want to unlock?
Sometimes it is better to keep quite, specially when you are not aware about current affairs.
@ OP yes, still same.
dr.ketan said:
Sometimes it is better to keep quite, specially when you are not aware about current affairs.
@ OP yes, still same.
Click to expand...
Click to collapse
Well, dang. That kind of kills the idea of fully functional phone with root. I mostly use root for ad blocking anymore. I don't really do the custom ROM thing all that much. Custom Android development these days isn't what it used to be.
I'm looking at either the carrier unlocked version, or the Verizon version (as I have Verizon as my carrier)
I believe rooting for ad blocking means you are paying more (now a days). In my opinion, Private DNS could be a good choice for ad block on unrooted.
I use AdAway. Works perfectly. But for best use, requires root. But yeah, other than that, I don't really use root. Would be nice to have a functional TWRP, but that may or may not happen. But that camera kill is a problem. I guess if I can get DNS to work, I won't have to worry about the bootloader at all. There would be no point.
I use AdGuard on my non-rooted phone and I don't see ads. None.
I see no reason why you need to root to just block ads. There are some great ad blocking apps out there. I love AdGuard because it works not only on my phone, but my PC as well.
There is a reason you cannot get this on the PlayStore. Google kicked it off because it works so well.
NextDNS
tze_vitamin said:
The 90% people on this community first what learn ro do is to unlock bootloader. You think that they all dont need camera or..
How is that even possible?
Once when you unblock bootloader you can do what you want, flash custom rom, custom recovery, custom Kernel. Magisk. Magisk modules..
But when you lock it ,and something got wrong ,you get hard brick phone. Bootloader must ne unlock until you use root and etc..
Camera have nothing to do with unlocking and working perfectly. I dont know who say to you ...or make a joke
Click to expand...
Click to collapse
Actually that is where you are wrong. Another user on this forum unlocked their bootloader on fold3 and then their cameras where disabled. There is even a warning message on unlocking bootloader screen that states clearly that cameras will be disabled after unlocking the bootloader. Even Sony smartphones had this but then Sony removed it so cameras won't be disabled after bootloader unlock.
You can read more about it here: https://forum.xda-developers.com/t/unlocking-bootloader-will-disable-the-camera.4321957/
So if bootloader locked/unlocked doesn't much matter (at least at this point), since I have Verizon, is there any reason to spring for the Unlocked version over the Verizon version? Does the Verizon version have any more apps preinstalled on it that the Unlocked version doesn't? Does either perform any differently?
Unlocked carrier is not the same as unlocked bootloader.
chevycam94 said:
So if bootloader locked/unlocked doesn't much matter (at least at this point), since I have Verizon, is there any reason to spring for the Unlocked version over the Verizon version? Does the Verizon version have any more apps preinstalled on it that the Unlocked version doesn't? Does either perform any differently?
Click to expand...
Click to collapse
ronaldheld said:
Unlocked carrier is not the same as unlocked bootloader.
Click to expand...
Click to collapse
What he said.
Carrier Unlock is the same as SIM Unlock which lets you use other carrier SIM Cards, has NOTHING to do with the Bootloader.
The Bootloader just unlocks the ability to flash custom Recoveries and ROM's. This does NOT SIM Unlock your phone.
Guys, I'm well aware of the difference between the two. I've been at this for 14+ years. I'm just wondering if there is a performance difference, or bloatware content difference between the Carrier Unlocked version and the Verizon Locked version.
chevycam94 said:
Guys, I'm well aware of the difference between the two. I've been at this for 14+ years. I'm just wondering if there is a performance difference, or bloatware content difference between the Carrier Unlocked version and the Verizon Locked version.
Click to expand...
Click to collapse
Today, the hardware in the US variant "Unlocked" and "Verizon" versions are exactly the same. The difference is only in the software set. And you have choices there. With Odin 3B you can cross-flash between the models to get the software set you want. Hell, you can even put the TMO software on the VZW "locked" device (I use quotes there because it is only locked for 90 days, at which point it becomes fully SIM unlocked automatically). You can load the U1-XAA, the U1-VZW, the U-VZW, whatever you can get your hands on. I am currently using a Verizon device with U1-XAA software, happily on One UI 4.0 beta. The Note 10 was the last device to have different hardware profiles between carriers that prevented full cross-flash support, and that was just because of the differing 5G networks as 5G was still in its infancy.
Notice how my phone setting in the photo show my phone as being a U1 (because it reads the phones software), and my phone info page within Samsung Members shows it to be a VZW device (because it uses the serial number to look up info from its database).
If you have any specific questions about it, feel free to message me. I have been doing this stuff since the WinMo days before Android existed. I don't post a lot because very few people read AND understand.
Oh, and for clarification to all the trolls out there, my device is still bootloader locked, Knox is fully intact, and my device is still covered under warranty (This was tested with my Note20 when i had to have the NFC chip replaced, and it too was a U-VZW running U1-XAA software.).
tze_vitamin said:
The 90% people on this community first what learn ro do is to unlock bootloader. You think that they all dont need camera or..
How is that even possible?
Once when you unblock bootloader you can do what you want, flash custom rom, custom recovery, custom Kernel. Magisk. Magisk modules..
But when you lock it ,and something got wrong ,you get hard brick phone. Bootloader must ne unlock until you use root and etc..
Camera have nothing to do with unlocking and working perfectly. I dont know who say to you ...or make a joke
Click to expand...
Click to collapse
Hoping for some progress on camera issue and all we get is this dips### lol
I didnt know that unlocking bootloader can kill camera. I unlocking phones , Samsung mostly. After then Xiaomi comes with lower prices and I now unlocking Xiaomi.
Can understand why vendors doing it..
But ... Some Hacker will always find some way
I have a U1 phone on Verizon. Everything works. 5g, wifi calling etc. Not sure if Verizon video calling works but who uses that? Duo is in the dialer I think. I've used opera browser for years which has ad blocking as well. YT vanced also and fblc
tze_vitamin said:
I didnt know that unlocking bootloader can kill camera. I unlocking phones , Samsung mostly. After then Xiaomi comes with lower prices and I now unlocking Xiaomi.
Can understand why vendors doing it..
But ... Some Hacker will always find some way
Click to expand...
Click to collapse
It's with this batch of Sammy phones. Doesn't always kill the camera.
BUT they have tried and haven't found a work around. Maybe 12 will let us, but for now we cannot unlock withou the camera "breaking".
Please see my thread - i believe with a12 this is thankfully now moot!!!!