Okay so i have read a few thread posts but all this seems a bit too confusing. Here is the situation. I bought a used S6-G920T which is unlocked as of now, i don't know what method was used to unlock it since i bought it pre unlocked. My sim(Non T-Mobile) is working fine. I am on 5.1.1- BASEBAND: G920TUVU3DOJ7, what i want to do is update to marshmallow, the official OTA isn't really available as it says the system was tampered with. I want to know if it is safe to update to 6.0.1 via odin without losing my unlock. Thanks in advance to anyone who bothered to read through.
BTW as of now i don't have root access.
What do you mean when you say you're unlocked?
You can use Odin to update the phone to newer baseband and bootloader; you can then use Odin to flash TWRP, and install the ROM of your choice.
socal87 said:
What do you mean when you say you're unlocked?
You can use Odin to update the phone to newer baseband and bootloader; you can then use Odin to flash TWRP, and install the ROM of your choice.
Click to expand...
Click to collapse
I am talking about carrier unlock. I currently don't have any carrier restrictions. Will update cause my phone to become relocked?
bolt890 said:
I am talking about carrier unlock. I currently don't have any carrier restrictions. Will update cause my phone to become relocked?
Click to expand...
Click to collapse
It shouldn't, no. You should be able to update and still use your phone on the carrier of your choice.
socal87 said:
It shouldn't, no. You should be able to update and still use your phone on the carrier of your choice.
Click to expand...
Click to collapse
It doesn't matter regardless of what method may have been used to unlock it?
Going to update soon via odin.
bolt890 said:
It doesn't matter regardless of what method may have been used to unlock it?
Click to expand...
Click to collapse
What method did you use? I don't imagine it would...of course, if you flash a stock TMobile ROM, some TMobile features may not work on another carrier...
socal87 said:
What method did you use? I don't imagine it would...of course, if you flash a stock TMobile ROM, some TMobile features may not work on another carrier...
Click to expand...
Click to collapse
That is the issue I bought it unlocked(used) so no idea what method may have been used. I might just go ahead and update. Thanks for the help.
bolt890 said:
That is the issue I bought it unlocked(used) so no idea what method may have been used. I might just go ahead and update. Thanks for the help.
Click to expand...
Click to collapse
I'm pretty sure the phone unlock has something to do with the IMEI of the phone being tied to the carrier. If it is unlocked, you should be able to use it on any carrier. It sounds like the process takes place in a special partition that is at the lower levels, like the bootloader, and does not change regardless of what software is used on the phone. I'd say just go for it and update, I can't see any reason why it wouldn't work, even after an Odin flash.
Related
i buy the phone HTC DREAM from the internet (i'm from malaysia) so i don't have T MOBILE SIM, but it's already unlocked.
what happen if i rooted or flash the phone with custom rom such as JACHeroski and etc.
will the phone become locked again ??
if the phone is locked, can i still able to like root and flash the phone ??
a rooted phone with custom rom, can eliminate the unlocking process ???
thx in advance
sorry for my poor english
keatliang2005 said:
i buy the phone HTC DREAM from the internet (i'm from malaysia) so i don't have T MOBILE SIM, but it's already unlocked.
what happen if i rooted or flash the phone with custom rom such as JACHeroski and etc.
will the phone become locked again ??
if the phone is locked, can i still able to like root and flash the phone ??
a rooted phone with custom rom, can eliminate the unlocking process ???
thx in advance
sorry for my poor english
Click to expand...
Click to collapse
No. A custom ROM wouldn't lock or unlock the phone. It can be unlocked for any SIM and still be stock firmware, it can also be unlocked for any SIM and have a custom rom.
The two things are completely different.
Hope this helps.
You can do whatever you want to any rom, and that won't affect anything that makes it unlocked
thx for replying,
so meaning, currently the phone is unlocked, and i downgrade to RC29
so it wont be locked again ?
because need to downgrade to root-ed the firmware....
is this mean, downgrade my unlocked phone firmware to RC29
in the process, it will not reset my phone from unlock back to lock status ??
if it will not make my phone locked back again during the process
and i success downgrade to RC29 i can gain root access, then i can update to custom firmware
so another question, in the upgrading process (flasing to custom firmware or cupcake 1.5) will it set back from unlock to locked ??
sorry for my bad english
appreciate for replying, i need to know before i done anything
in the process,
Hi. I also have an unlocked phone. It was unlocked prior I downgraded it, and flashed new custom roms, and it is still unlocked. As the others said no need to worry, if i'm right the locking thing is in deeper level. Of course everything you do with your phone is your responsibility.
eami said:
Hi. I also have an unlocked phone. It was unlocked prior I downgraded it, and flashed new custom roms, and it is still unlocked. As the others said no need to worry, if i'm right the locking thing is in deeper level. Of course everything you do with your phone is your responsibility.
Click to expand...
Click to collapse
thx for the reply, now i can do the firmware flashing
unlock after root?
NPerry said:
No. A custom ROM wouldn't lock or unlock the phone. It can be unlocked for any SIM and still be stock firmware, it can also be unlocked for any SIM and have a custom rom.
The two things are completely different.
Hope this helps.
Click to expand...
Click to collapse
Can T-mobile still unlock the phone after I rooted it or would they know that I put a custom rom on it??
c_licious said:
Can T-mobile still unlock the phone after I rooted it or would they know that I put a custom rom on it??
Click to expand...
Click to collapse
Yes, you can still unlock it through T-Mo. No one at T-Mo needs to have physical access to your phone, they can give you an unlock code over the phone.
c_licious said:
Can T-mobile still unlock the phone after I rooted it or would they know that I put a custom rom on it??
Click to expand...
Click to collapse
One has nothing to do with the other. ROMs have nothing to do with the SIM cards and SIM cards have nothing to do with ROMs. T-Mobile isn't going to come to your house and spank you for having a custom ROM because they "know"
DirectMatrix said:
One has nothing to do with the other. ROMs have nothing to do with the SIM cards and SIM cards have nothing to do with ROMs. T-Mobile isn't going to come to your house and spank you for having a custom ROM because they "know"
Click to expand...
Click to collapse
Hmm highly unfortunate. Wouldn't have minded a little love tap from Cindy with Customer Service LOL
Thanks buddy!
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
You should check out the 'Chinese Middleman' thread. If you get the bootloader unlocked you should be able to fix anything.
I can't unlock the bootloader since this is not a Dev edition. Unless something has changed, I'll check it.
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Even though it's not a Dev edition?
Yes you should be able too.
Sent from my XT1053 using Tapatalk
danman421 said:
Even though it's not a Dev edition?
Click to expand...
Click to collapse
All XT1053s can be unlocked, yes. Additionally, if you follow my advice, you don't NEED to unlock. If one of the commands fails, simply skip to the next as I previously advised, and TRY flashing with RSD Lite after you have run the commands I listed.
If you want to check and make sure fastboot is working, type:
fastboot devices
if you see your phone and it's serial number listed, you fastboot IS properly communicating with your phone.
You do not need to unlock your BL to do any of this...but if you are interested in ROOTING, you will need to.
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
danman421 said:
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
Click to expand...
Click to collapse
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
danman421 said:
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
Click to expand...
Click to collapse
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
samwathegreat said:
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
Click to expand...
Click to collapse
So if I am reading this correctly, there is no way to keep all of my data and take the update?
danman421 said:
So if I am reading this correctly, there is no way to keep all of my data and take the update?
Click to expand...
Click to collapse
You can attempt to, by either editing the XML in the SBF and removing the line that says "erase userdata", or by skipping the erase userdata if you use the manual method, but either way CAN mess everything up.
You used an EXPLOIT previously. Any time you use an exploit, you should -expect- to have to wipe everything and re-install from scratch if you want to get back to stock in order to be able to take updates. Keep this in mind if you use any exploits in the future.
Hi! This hasn't seemed to spelled out yet..... But many Moto x's can be unlocked, not just dev editions. However, you stated in the opening post that you have a Verizon Non dev, which can not be unlocked. Only way is to pay the "China middleman" (See thread in general with that name).
And personally.... I would stay on 4.2.2 and do the Slapmymoto method to get root and write protection disabled. That is the best root scenario, aside from unlocking the bootloader.
If you update to 4.4.2 or higher, you will have write protection enabled always, and no root, or sorta root with towelroot and pie. But that will limit what you can do.
See the How do I root my phone sticky thread in general for your options.
I should have posted earlier. I ran RSDLite and put the newest version on. I am unrooted. My Moto X is a Sept '13 version the the middleman probably wont work anyways. Its not worth it with this phone, im tired of the rooting, I guess im at that point in my life... Thanks for all your help though guys!
danman421 said:
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
Click to expand...
Click to collapse
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
KidJoe said:
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
Click to expand...
Click to collapse
Good catch! ?
OP... Perhaps full disclosure of what you have done on the phone would help.
Or is that how it was?
If it's been downgraded to 4.2.2 after being on 4.4.2... As said above.... You could brick now... Especially if you OTA.
I'd tread lightly at this point.
danman421 said:
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
Click to expand...
Click to collapse
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Yes, that was a good catch. What I did was RSD Lite to 4.4.4 now which reset all my data.
KidJoe said:
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Click to expand...
Click to collapse
Correct, I do not need help anymore but thank you.
Hi, I have a T-mobile GS6 and want to unlock it I know I need to flash METRO PCS firmware unlock it then flash back to stock but what unlocker is $20 or less and works with the S6 tmobile that is on METRO PCS firmware also while I am doing this and it asks me what carrier I am currently using do I select METRO PCS or T-MOBILE?
Thanks
ethanscooter said:
Hi, I have a T-mobile GS6 and want to unlock it I know I need to flash METRO PCS firmware unlock it then flash back to stock but what unlocker is $20 or less and works with the S6 tmobile that is on METRO PCS firmware also while I am doing this and it asks me what carrier I am currently using do I select METRO PCS or T-MOBILE?
Click to expand...
Click to collapse
Once you unlock with the MetroPCS firmware, do not ever flash back to T-Mobile firmware, or you'll end up relocking it! You can flash any compatible ROM, just not the T-Mobile radio firmware. ROM'S never include the radio firmware, so you should be fine.
guyd said:
Once you unlock with the MetroPCS firmware, do not ever flash back to T-Mobile firmware, or you'll end up relocking it! You can flash any compatible ROM, just not the T-Mobile radio firmware. ROM'S never include the radio firmware, so you should be fine.
Click to expand...
Click to collapse
Ok and really quick, lets say I used the unlock app to get a temp unlock and froze it to kind of make it perm could I flash another ROM and still be unlocked?
ethanscooter said:
Ok and really quick, lets say I used the unlock app to get a temp unlock and froze it to kind of make it perm could I flash another ROM and still be unlocked?
Click to expand...
Click to collapse
No, it's not that easy! You need a real unlock to make it permanent.
You just need to decide which route to take to unlock it.
I did the MetroPCS firmware and then traditional sim unlock, and then custom rom.
guyd said:
No, it's not that easy! You need a real unlock to make it permanent.
You just need to decide which route to take to unlock it.
I did the MetroPCS firmware and then traditional sim unlock, and then custom rom.
Click to expand...
Click to collapse
But what if I went back to tmobile stock and then I would lose the unlock BUT after going to the tmobile rom which would make me lose my unlock could I go back to a metroPCS ROM and unlock with the same code?
ethanscooter said:
But what if I went back to tmobile stock and then I would lose the unlock BUT after going to the tmobile rom which would make me lose my unlock could I go back to a metroPCS ROM and unlock with the same code?
Click to expand...
Click to collapse
No, It's the low level firmware that's the key to the unlock.
MetroPCS firmware = traditional code unlock
T-Mobile firmware = proprietary device unlock
After you're unlocked, you can change the ROM all you want. It's the low level firmware that you must be careful with (mainly the radio).
guyd said:
No, it's not that easy! You need a real unlock to make it permanent.
You just need to decide which route to take to unlock it.
I did the MetroPCS firmware and then traditional sim unlock, and then custom rom.
Click to expand...
Click to collapse
Do you mind pointing me to the guide you used to root and install recovery on your S6.
I just unlocked mines using the metro firmware and I don't want to accidentally install the T-Mobile firmware
Thanks
GeeRoooock said:
Do you mind pointing me to the guide you used to root and install recovery on your S6.
I just unlocked mines using the metro firmware and I don't want to accidentally install the T-Mobile firmware
Thanks
Click to expand...
Click to collapse
Don't download and Odin flash the T-Mobile firmware or radio, and you'll have nothing to worry about!
Rooting is simple on an unlocked bootloader if you don't mind tripping knox.
1. Odin flash TWRP.
2. Boot straight into TWRP after Odin flashing (vol-up + home + power)
3. Flash SuperSU from TWRP
Done, profit!
guyd said:
Don't download and Odin flash the T-Mobile firmware or radio, and you'll have nothing to worry about!
Rooting is simple on an unlocked bootloader if you don't mind tripping knox.
1. Odin flash TWRP.
2. Boot straight into TWRP after Odin flashing (vol-up + home + power)
3. Flash SuperSU from TWRP
Done, profit!
Click to expand...
Click to collapse
Hey! I do have the same question as the person that created this thread. When I flash the MetroPCS firmware should I select MetroPCS or T-Mobile on a 3rd party unlocking company to buy the unlocking code? Thank you all!
marcio_moura said:
Hey! I do have the same question as the person that created this thread. When I flash the MetroPCS firmware should I select MetroPCS or T-Mobile on a 3rd party unlocking company to buy the unlocking code? Thank you all!
Click to expand...
Click to collapse
MetroPCS, that's what I did and it worked fine if you flash the MetroPCS firmware.
I need to get my S6 to show the Tmobile Logo on bootup so I can Jump to the S7. I had flashed it to MetroPCs for the unlock. I thought if I went the Odin route and installed the Tmobile software it would change the bootup Logo but so far after running Odin it still boots up with MetroPCs.
guyd said:
No, it's not that easy! You need a real unlock to make it permanent.
You just need to decide which route to take to unlock it.
I did the MetroPCS firmware and then traditional sim unlock, and then custom rom.
Click to expand...
Click to collapse
Which MetroPCS firmware did you use and where did you get it from?
I have a SM_G920T on TMobile 5.1.1 Baseband G920TUVS3DOJC and I tried flashing the G920T1UVU2COF9 MetroPCS firmware from sammobile and I get a FAIL message on Odin.
mudcat242000 said:
Which MetroPCS firmware did you use and where did you get it from?
I have a SM_G920T on TMobile 5.1.1 Baseband G920TUVS3DOJC and I tried flashing the G920T1UVU2COF9 MetroPCS firmware from sammobile and I get a FAIL message on Odin.
Click to expand...
Click to collapse
I Odin'd the MetroPCS firmware (G920T1) a long time ago, and it was newer than the TMo firmware the device had on it at the time. I think you're failing to flash because the MetroPCS firmware you used 2COF9 is older than the Tmobile firmware 3DOJC you already have on it. That's my guess.
Hey guys,
So I just bought bought a G920T1 and I am aware that it is the same hardware as the G920T with a few software differences (missing download booster). Knowing this, is it safe for me to use the root methods/custom recoveries/custom firmwares of the G920T on my phone?
Thanks
Yes. And by custom firmwares I assume you mean custom roms
Sent from my SM-G920T using Tapatalk
Yup, they are exactly the same phone. So use Unikernel to root, TWRP for recovery, and firmware of choosing.
One thing tho is if you wanna use the unlocking method with Metro which use codes. Then don't flash any TMO modem and bootloader as you will lose the unlock. Just update them to lastest 5.1.1 from sammobile or OTA if you need to. Other then that you should be good to go.
serio22 said:
Yes. And by custom firmwares I assume you mean custom roms
Sent from my SM-G920T using Tapatalk
Click to expand...
Click to collapse
Yeah, it's been awhile since i've been back on xda
stylin350 said:
Yup, they are exactly the same phone. So use Unikernel to root, TWRP for recovery, and firmware of choosing.
One thing tho is if you wanna use the unlocking method with Metro which use codes. Then don't flash any TMO modem and bootloader as you will lose the unlock. Just update them to lastest 5.1.1 from sammobile or OTA if you need to. Other then that you should be good to go.
Click to expand...
Click to collapse
I bought the phone off swappa and it was listed under the T-mobile S6 section, but I noticed that the model number in the pictures was G920T1. I'll probably ask the seller how he unlocked his phone. So flashing a custom ROM should be fine, right? Based on my previous experience flashing my older S3, flashing modems were usually a different .zip than the ROMs and I don't really remember all too much about bootloaders.
crazililazn said:
Yeah, it's been awhile since i've been back on xda
I bought the phone off swappa and it was listed under the T-mobile S6 section, but I noticed that the model number in the pictures was G920T1. I'll probably ask the seller how he unlocked his phone. So flashing a custom ROM should be fine, right? Based on my previous experience flashing my older S3, flashing modems were usually a different .zip than the ROMs and I don't really remember all too much about bootloaders.
Click to expand...
Click to collapse
Yeah flashing custom rom is fine as they don't include the modem nor bootloader. It's just that most newer roms require you to have the lastest bootloader and modem for best experience. Sorry didn't mean to confuse you more, but G920T and G20T1 are the same phone. Some people just swap firmwares between TMO and Metro as the G920T1 is easier to unlock. I have the same version G920T1 and bought code off of ebay to unlock easily.
stylin350 said:
Yeah flashing custom rom is fine as they don't include the modem nor bootloader. It's just that most newer roms require you to have the lastest bootloader and modem for best experience. Sorry didn't mean to confuse you more, but G920T and G20T1 are the same phone. Some people just swap firmwares between TMO and Metro as the G920T1 is easier to unlock. I have the same version G920T1 and bought code off of ebay to unlock easily.
Click to expand...
Click to collapse
Alright, then can I upgrade to the newest Metro bootloader to keep my unlock and then install the newer ROMs? Or would I lose my unlock that way.?
crazililazn said:
Alright, then can I upgrade to the newest Metro bootloader to keep my unlock and then install the newer ROMs? Or would I lose my unlock that way.?
Click to expand...
Click to collapse
Correct and you'll keep the unlock.
stylin350 said:
Yeah flashing custom rom is fine as they don't include the modem nor bootloader. It's just that most newer roms require you to have the lastest bootloader and modem for best experience. Sorry didn't mean to confuse you more, but G920T and G20T1 are the same phone. Some people just swap firmwares between TMO and Metro as the G920T1 is easier to unlock. I have the same version G920T1 and bought code off of ebay to unlock easily.
Click to expand...
Click to collapse
stylin350 said:
Correct and you'll keep the unlock.
Click to expand...
Click to collapse
Hello again, about to get my S6 soon and was wondering if you could point me to some root methods that would work without breaking fingerprint scanner or tripping KNOX. It's been awhile since I've been back in the rooting scene and was hoping you could point me in the right direction. Also, if I want to keep my unlock and upgrade to Tmo 5.1.1 stock, I would flash the Tmo ROM with a Metro bootloader?
I looked on Cyanogenmod's website below:
https://download.cyanogenmod.org/?device=shamu
and it just has 1 ROM for Nexus 6. I have Nexus 6 for Sprint. Is there only 1 version of the ROM that works for all carriers ?
My old Galaxy S4 has many different builds for Sprint, ATT, Verizon, etc.... wasn't sure if Nexus has the same set up.
Yes, applies to all N6 variants.
thats because every sgs4 has a different setup for different carriers. we only have one nexus 6, and its the same for every carrier.
simms22 said:
thats because every sgs4 has a different setup for different carriers. we only have one nexus 6, and its the same for every carrier.
Click to expand...
Click to collapse
I didn't have a locked bootloader with Sprint Galaxy S4. If I were to restore the Nexus 6 back to stock to do an OTA update to update everything, then re-root and put a new custom ROM does the bootloader need to be re-locked, or can the factory .img be suffice to do an OTA ?
I'm still trying to learn how to do this as it is much different than the Samsung GS4. I saw there is a Nexus Toolkit by wug fresh. Is there any benefit to doing these processes by adb vs just using this progra which seems easier ?
mikeprius said:
I didn't have a locked bootloader with Sprint Galaxy S4. If I were to restore the Nexus 6 back to stock to do an OTA update to update everything, then re-root and put a new custom ROM does the bootloader need to be re-locked, or can the factory .img be suffice to do an OTA ?
I'm still trying to learn how to do this as it is much different than the Samsung GS4. I saw there is a Nexus Toolkit by wug fresh. Is there any benefit to doing these processes by adb vs just using this progra which seems easier ?
Click to expand...
Click to collapse
you dont use adb for it, you use fastboot. and doung it right vs a toolkit.. toolkits dont teach you anything, and can mess things up.
simms22 said:
you dont use adb for it, you use fastboot. and doung it right vs a toolkit.. toolkits dont teach you anything, and can mess things up.
Click to expand...
Click to collapse
Does the bootloader need to be locked to do OTAs or does the stock ROM with leaving the bootloader unlock suffice for an OTA ?
mikeprius said:
Does the bootloader need to be locked to do OTAs or does the stock ROM with leaving the bootloader unlock suffice for an OTA ?
Click to expand...
Click to collapse
bootloader can be locked or unlocked, it doesnt matter. but i recommend that you keep it unlocked forever, as it can save your phone in certain situations. and having it locked can be the end of your device, in the same situations.
simms22 said:
bootloader can be locked or unlocked, it doesnt matter. but i recommend that you keep it unlocked forever, as it can save your phone in certain situations. and having it locked can be the end of your device, in the same situations.
Click to expand...
Click to collapse
Ok. That's what I was planning on doing once it becomes unlocked. I was going to have it set like my previous GS4 and just toggle custom ROMs from there. When you mention having it locked, are you referring to when people have re-locked the bootloader then had an error flashing the stock custom ROM thus bricking the phone ? That's what worries me. Looks like the security is more stringent on the new Nexus vs. older versions.
mikeprius said:
Ok. That's what I was planning on doing once it becomes unlocked. I was going to have it set like my previous GS4 and just toggle custom ROMs from there. When you mention having it locked, are you referring to when people have re-locked the bootloader then had an error flashing the stock custom ROM thus bricking the phone ? That's what worries me. Looks like the security is more stringent on the new Nexus vs. older versions.
Click to expand...
Click to collapse
i was actually refering to it because of the unlock setting that has to be ticked to unlock. some stock users got caught in a bootloop, then cant boot up to tick the setting, to fix their bootloop. since it cant get unlocked, their phones are a "brick".
simms22 said:
i was actually refering to it because of the unlock setting that has to be ticked to unlock. some stock users got caught in a bootloop, then cant boot up to tick the setting, to fix their bootloop. since it cant get unlocked, their phones are a "brick".
Click to expand...
Click to collapse
Is this what happened to this person below ?:
http://forum.xda-developers.com/nexus-6/help/help-nexus-6-brick-t3227126
Since the stock rom did not have developer options "checked" then the bootloader can't be unlocked ? How can you tick the OEM unlock if it is in a bootloop ?
mikeprius said:
Is this what happened to this person below ?:
http://forum.xda-developers.com/nexus-6/help/help-nexus-6-brick-t3227126
Since the stock rom did not have developer options "checked" then the bootloader can't be unlocked ? How can you tick the OEM unlock if it is in a bootloop ?
Click to expand...
Click to collapse
you cant, thats why i said that you should keep it unlocked.
simms22 said:
you cant, thats why i said that you should keep it unlocked.
Click to expand...
Click to collapse
Ok that makes sense. What is the purpose of having the bootloader come locked in a stock phone then ? What does it actually do ? Prevents root ? I probably took it for granted mine was always unlocked before so all I had to do was worry about flashing the proper carrier ROM
mikeprius said:
Ok that makes sense. What is the purpose of having the bootloader come locked in a stock phone then ? What does it actually do ? Prevents root ? I probably took it for granted mine was always unlocked before so all I had to do was worry about flashing the proper carrier ROM
Click to expand...
Click to collapse
Security.
Security in that if stolen your phone cannot be made to work for someone else...
Someone can (and likely will [emoji14]) correct me if I am wrong... But does little to secure your data...ESPECIALLY if you stay encrypted.
scryan said:
Security in that if stolen your phone cannot be made to work for someone else...
Someone can (and likely will [emoji14]) correct me if I am wrong... But does little to secure your data...ESPECIALLY if you stay encrypted.
Click to expand...
Click to collapse
It does nothing to secure data from remote access, but it will protect data (if set with a password) from physical access, providing they do not know the password. The bootloader being unlocked, with no password on encryption would allow them to flash a custom recovery and pull the data off. This will be decrypted on the fly. So it works in conjunction with Encryption. To secure data from physical access, you need both.
IF your bootloader is unlocked and you have no password, you may aswell not be encrypted