Android 5.1 Possibly Coming February 2015

Google released Android 5.0 just over a month ago, and since then Lollipop has been trying to … more

Double Tap to Wake on the Nexus 6 Without Root

A few weeks ago, we featured an app which allowed the Nexus 6 to regain the double tap to wake … more

Make Your Own Heat Sink for the LG Optimus 4X HD

Its not a rare occurrence that performing a resource heavy task on your Android device (e.g. … more

Learn How to Create an Old School Dialer

XDA is not only a great source for custom ROMs, kernels, and various modifications for numerous … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Will my unlock code work after update?

OP kicker22004

1st April 2014, 12:27 AM   |  #1  
OP Senior Member
Thanks Meter: 107
 
332 posts
Join Date:Joined: Mar 2008
Donate to Me
I have the RW version and unlocked with the China man... My question is once I take the OTA will it relock my bootloader?? And if I relock it can I use the same code to unlock it again? And last can I still use the sbf file on this phone or must I manually flash the partitions? Thanks guys

Sent from my XT1049 using xda app-developers app
1st April 2014, 01:07 AM   |  #2  
southern87's Avatar
Senior Member
Flag The Command Center
Thanks Meter: 98
 
476 posts
Join Date:Joined: May 2008
More
No it will not relock it it. Once the flags are triped there is no going back to locked. Just relocked

Sent from my XT1058 using xda app-developers app
1st April 2014, 08:03 PM   |  #3  
The Tallest's Avatar
Senior Member
Thanks Meter: 20
 
155 posts
Join Date:Joined: Jul 2013
More
I've been wondering this too. The last phone I had (Google Galaxy Nexus) was unlocked and rooted running CM 10.1 and then CM 11 so it never received the OTA's. But mine and my wife's Moto X Developer Editions are both unlocked and rooted but running stock 4.4.2.

As I understand it we'll still receive OTA's correct? Once we do there is a chance they will lock back up and we'll lose root correct? The reason I say chance is because both phones are setup through Titanium to "attempt" to keep root and I know it doesn't always work.

I'm assuming the bootloader gets relocked? If it does how do we go about unlocking and rooting them again? Will the codes we got from Motorola work or do we need to go through the entire process of unlocking then rooting?

Sorry for the newb questions. Like I said, every phone I ever unlocked and rooted I put custom ROMs on them so I never got the OTA's.
1st April 2014, 09:00 PM   |  #4  
OP Senior Member
Thanks Meter: 107
 
332 posts
Join Date:Joined: Mar 2008
Donate to Me
Yeah I've read about it going to relock if I do it.. But can a ota update relock it.. And if it did.. Will my code still work.

Sent from my XT1049 using xda app-developers app
1st April 2014, 09:25 PM   |  #5  
KidJoe's Avatar
Recognized Contributor
Flag Thorndale/Romansville, PA
Thanks Meter: 955
 
2,271 posts
Join Date:Joined: Aug 2008
More
Yes, you can flash using either RSDLite or fastboot/mFastboot

If you do relock your bootloader, yes the same code will work to unlock it later.

And... already said here -> http://forum.xda-developers.com/show...&postcount=394
Quote:

[*]Taking future OTA's will not re-lock your bootloader, however you will need to have stock recovery on your phone, and revert any modified system files, i.e. get back to "stock" or nearly stock, in order to install OTA's, just like those with Developer Edition phones have to do. (this is due to the OTA updates containing a manifest file that lists files and their "check sums" it looks for on your phone before it starts. If they are not on your phone, or the ones on your phone don't match the expected check sum, the OTA install will fail.)
[*]Flashing with RSDLite will not re-lock your bootloader
[*]Only manually re-locking via the relock process (moto has on the Dev Edition web site, it is fastboot oem lock ) will re-lock your bootloader.

Last edited by KidJoe; 1st April 2014 at 09:28 PM.
The Following 2 Users Say Thank You to KidJoe For This Useful Post: [ View ]
1st April 2014, 11:11 PM   |  #6  
The Tallest's Avatar
Senior Member
Thanks Meter: 20
 
155 posts
Join Date:Joined: Jul 2013
More
So, I'd need to reinstall all the bloatware that came on the phone originally? That's pretty much all I took off the phone was all of Verizon's crap that I'll never use nor have any interest in. The only other thing I did was edit the navigation keys out using the build.prop, but that's easy enough to turn back on. My phone as well as my wife's are stock aside from the removal of the bloatware and taking the nav keys out of my phone.
2nd April 2014, 11:19 AM   |  #7  
OP Senior Member
Thanks Meter: 107
 
332 posts
Join Date:Joined: Mar 2008
Donate to Me
Thanks kid. I've just read mixed messages about bricking my device from ota updates and sbfs. Thanks again.

Sent from my XT1049 using xda app-developers app
2nd April 2014, 12:04 PM   |  #8  
KidJoe's Avatar
Recognized Contributor
Flag Thorndale/Romansville, PA
Thanks Meter: 955
 
2,271 posts
Join Date:Joined: Aug 2008
More
Quote:
Originally Posted by The Tallest

So, I'd need to reinstall all the bloatware that came on the phone originally? That's pretty much all I took off the phone was all of Verizon's crap that I'll never use nor have any interest in. The only other thing I did was edit the navigation keys out using the build.prop, but that's easy enough to turn back on. My phone as well as my wife's are stock aside from the removal of the bloatware and taking the nav keys out of my phone.

When it comes to taking OTA's, yes.

Inside the OTA is a manifest file. It contains a list of files and their check sums it expects to be on your phone. If the files are missing, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall. Because of this, you must be "stock" (or as close to stock as possible). Any bloat you deleted, needs to be put back. Any files you altered (like build.prop) need to be reverted. Any apps you froze with Titanium Backup or the like, may need to be unfrozen.

Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update.

---------- Post added at 06:04 AM ---------- Previous post was at 05:58 AM ----------

Quote:
Originally Posted by kicker22004

Thanks kid. I've just read mixed messages about bricking my device from ota updates and sbfs. Thanks again.

Sent from my XT1049 using xda app-developers app

Yes, there are some cautions and warnings about bricking... They usually relate to if you've taken 4.4.2 and try to downgrade your rom to 4.4 or lower. Or if you flash only parts of a rom using mFastboot and get into a state when you have "mixed" versions on your phone...

Due to changes in the bootloader included with the 4.4.2 Update, under certain circumstances when trying to downgrade from 4.4.2 to 4.4 or lower, you could either brick your phone, or set it up to brick in the future when you take an upgrade. So it is suggested you just stick with what is on your phone once you get on 4.4.2.
2nd April 2014, 01:37 PM   |  #9  
The Tallest's Avatar
Senior Member
Thanks Meter: 20
 
155 posts
Join Date:Joined: Jul 2013
More
Quote:
Originally Posted by KidJoe

When it comes to taking OTA's, yes.

Inside the OTA is a manifest file. It contains a list of files and their check sums it expects to be on your phone. If the files are missing, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall. Because of this, you must be "stock" (or as close to stock as possible). Any bloat you deleted, needs to be put back. Any files you altered (like build.prop) need to be reverted. Any apps you froze with Titanium Backup or the like, may need to be unfrozen.

Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update.[COLOR="Silver"]

---------- Post added at 06:04 AM ---------- Previous post was at 05:58 AM ----------

Well damn, I'm kind of screwed then as I deleted all those dumbass Verizon apps that I have no use for and didn't bother making backups of any of them. I'll have to check the "Apps" folder and see if the .apk files are still there so that Google Play can redownload them at some point.

I don't even think the backup I made via TWRP has them. Although I think Motorola's website does have the system image so I can probably just reflash that when the next OTA comes out.
2nd April 2014, 03:26 PM   |  #10  
KidJoe's Avatar
Recognized Contributor
Flag Thorndale/Romansville, PA
Thanks Meter: 955
 
2,271 posts
Join Date:Joined: Aug 2008
More
Quote:
Originally Posted by The Tallest

Well damn, I'm kind of screwed then as I deleted all those dumbass Verizon apps that I have no use for and didn't bother making backups of any of them. I'll have to check the "Apps" folder and see if the .apk files are still there so that Google Play can redownload them at some point.

I don't even think the backup I made via TWRP has them. Although I think Motorola's website does have the system image so I can probably just reflash that when the next OTA comes out.

TWRP.. then you have an unlocked bootloader? If so, you do have the option to flash the SBF to revert to stock, or unzip it and just mfastboot flash system.img onto your phone, because you can always re-root later.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes