Related
All nexus one users got OTA update???????
im a at&t device user, using in other country (HongKong) and i tried to get OTA update on ERD79 and also Stock EPE54b.. installed stock recovery too..
stil didnt get any OTA notifications.. even typed *#*#checkin#*#*
is it only me having a problem?? i just want to know if i unlock bootloader,
cannot be getting OTA notifiction?
is there any reason why you cant use one of the many manual updates posted on this site? none of them should require unlocking the boot loader
Yes probably can update thru manual update.
i just wanna know why OTA doesnt show up on ma phone since 2weeks ago.
The OTA is gradual over about a week or so. They release to a certain group of IMEI numbers each night so they don't get server overload. I wasn't able to check in and get the OTA but I was able to download the zip file and install manually without issue.
Sent from my Nexus One using XDA App
as far as I'm aware, the only way to root the HTC one is via unlocking the bootloader, which then prevents the phone from receiving OTA updates, is it possible to root the HTC one without opting out of these updates?
Thanks, LordTumnas
(if there is a similar thread to this, i apologize, i was unable to find it)
I'm not sure about all versions, but I have the Developer Edition that came unlocked and I get OTA updates. I think it is more about CID, MID, and stock OS & recovery.
artiemon said:
I'm not sure about all versions, but I have the Developer Edition that came unlocked and I get OTA updates. I think it is more about CID, MID, and stock OS & recovery.
Click to expand...
Click to collapse
im not sure what version i have... its through Telstra in australia (32GB silver)...
A good place to start is here: http://forum.xda-developers.com/showthread.php?t=2228274
The key is to make sure you are confident you can get back to stock recovery and perhaps locked bootloader (depending on model) before you take the plunge. That way you can get back to a fully stock device.
LordTumnas said:
as far as I'm aware, the only way to root the HTC one is via unlocking the bootloader, which then prevents the phone from receiving OTA updates, is it possible to root the HTC one without opting out of these updates?
Thanks, LordTumnas
(if there is a similar thread to this, i apologize, i was unable to find it)
Click to expand...
Click to collapse
Use revone to s-off and unlock then install cwm recovery, install supersu from recovery, install stock recovery. With supersu you can temp unroot for otas.
LordTumnas said:
as far as I'm aware, the only way to root the HTC one is via unlocking the bootloader, which then prevents the phone from receiving OTA updates, is it possible to root the HTC one without opting out of these updates?
Thanks, LordTumnas
(if there is a similar thread to this, i apologize, i was unable to find it)
Click to expand...
Click to collapse
This doesn't answer your question, but usually somebody posts a zip for a stock, rooted ROM within a couple days of OTA.
Just root, unlock, and install a custom rom already.
Sent from my HTC One using xda premium
I am on a Verizon moto x developer edition with an unlocked boot loader, custom recovery installed and I am rooted. I got the notification for the ota update. What if anything will this break?
Sent from my XT1060 using XDA Premium 4 mobile app
First, you need to be on stock recovery for the OTA to attempt to install. Next you need to make sure all your system files and such are present and back to "stock" (i.e. if you did the tethering hacks, renamed or replaced system files, etc, you need to undo that), and you need to un-install Xposed or the OTA will fail when it tries to install.
Since you are Dev with unlocked bootloader, it wont "break" anything, but the new bootloader installed via the OTA prevents downgrading your rom. So if you find an issue with 4.4.2, you're stuck with it, you can't flash back to 4.4. If you loose root, you can still flash custom recovery and install SuperSU to root.
Those with locked bootloader might keep root, but Write Protection gets Enabled again. With an unlocked boot loader, you don't have to worry about this.
Also, if you really want 4.4.2, there is a zip in the android development section with an unofficial sbf. Be very careful with what files you flash, i flashed the zip in RSD lite blindly (my mistake) and spend four hours trying to figure out why i didn't have data or any mobile connection.
-edit-
Also, don't take my word for it but i think you'll still be alright if you don't flash gpt.bin and the bootloader and you should still be able to downgrade.
Ok. Thanks for the info guys. I might just wait until someone puts out the deoxidized 4.4.2 rom. I would flash slim or cm11 but I really like the active display and the touch less controls.
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
Ok. Thanks for the info guys. I might just wait until someone puts out the deoxidized 4.4.2 rom. I would flash slim or cm11 but I really like the active display and the touch less controls.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For what its worth, I've been running this 4.4.2 rom (the odexed version, deodexed also available) created from a XT1052 image on my VZW/DE XT1060:
http://forum.xda-developers.com/moto-x/development/rom-moto-x-xt1052-t2639724
I did swap out the original build.prop with the Verizon-ized build.prop someone was kind enough to post on page 2 or 3 of that thread. It has been working great for me for the last week! Tethering even works on VZW w/o any extra steps.
robwege said:
I am on a Verizon moto x developer edition with an unlocked boot loader, custom recovery installed and I am rooted. I got the notification for the ota update. What if anything will this break?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If that's all you've done (haven't modified/deleted/renamed any system files/apps or installed Xposed, etc..) then it's really easy.
Flash the stock recovery back to your phone
install the update
Flash TWRP back to your phone (or not....)
Done.
You won't lose root taking the OTA and flashing recovery back doesn't affect your user data or app installs/configurations.
Hi, tried searching my answer, but still not clear as to the answer for my situation, im about to purchase the unlock code for my non DE verizon moto x , code is from someone from china. If i upgrade to 4.4.2 while unlocked bootloader, any way back to 4.2.2 post camera update. Thanks
ericizzy1 said:
Hi, tried searching my answer, but still not clear as to the answer for my situation, im about to purchase the unlock code for my non DE verizon moto x , code is from someone from china. If i upgrade to 4.4.2 while unlocked bootloader, any way back to 4.2.2 post camera update. Thanks
Click to expand...
Click to collapse
Yes and No
No you can not flash the complete 4.2.2 PCU package it will fail because you can't downgrade the bootloader
Yes because you can flash everything but the bootloader and it will take but if you accidentally take a OTA. you will brick your device.
but if you are able to unlock your bootloader then why would you want to downgrade. with a unlocked bootloader you will be able to root 4.4.2 with no issues
because when I was on 4.4, I had some battery consumption and heating issues also bluetooth was not perfect, I just wanted to make sure I have a way back To 4.2.2
also, not being able to downgrade the bootloader, in which way does this affect me going back to four point 4.2.2?
Your phone will work fine but like i said if you ever take a ota it will brick your phone
Sent from my XT1056 using XDA Premium 4 mobile app
dray_jr said:
Your phone will work fine but like i said if you ever take a ota it will brick your phone
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ota will brick, will be able to rsd to 4.4 or 4.4.2 if wanted?
Yup that is correct
Sent from my XT1056 using XDA Premium 4 mobile app
ericizzy1 said:
ota will brick, will be able to rsd to 4.4 or 4.4.2 if wanted?
Click to expand...
Click to collapse
No. Once you start mixing bootloader versions with system file versions (i.e. 4.4.2 bootloader with 4.2.2 system files), RSD Lite won't work. You will have to use a command line and mfastboot.exe to manually flash each partition.
And I actually tried to run 4.2.2 (post camera update) system files with a 4.4.2 bootloader and it would not boot; however, 4.4 system files do work with a 4.4.2 bootloader.
This has actually been discussed at great length and detail in this forum and A LOT of people were bricking their phones playing around with bootloader versions, just like you are talking about doing. At one point there was a sticky dedicated to it, but its since disappeared from the board for some reason.
To put it simply, please don't start mixing bootloader versions with system files. If you like 4.2.2, don't upgrade to 4.4.2. If you are on 4.4, then you can still downgrade to 4.2.2 (post camera update version). Do that and stay there. But if you upgrade to 4.4.2, don't fool around with it and start trying to downgrade. There is no point, and you will likely end up bricking your phone.
It's your phone, so do what you want, but you have been warned (by someone with personal experience by the way). If you do brick it, please don't start another "OMG! HELP ME!! I BRICKED MY PHONE!!" thread. There's plenty of those already floating around here. :good:
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
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
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.
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
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/showpost.php?p=51363645&postcount=394
[*]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.
Click to expand...
Click to collapse
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.
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
The Tallest said:
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.
Click to expand...
Click to collapse
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 ----------
kicker22004 said:
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
Click to expand...
Click to collapse
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.
KidJoe said:
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 ----------
Click to expand...
Click to collapse
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.
The Tallest said:
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.
Click to expand...
Click to collapse
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.
KidJoe said:
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.
Click to expand...
Click to collapse
Yes, my boot loader is unlocked. That's good to know that I can do that, thanks.
Wait... Did I miss read that... You can flash sbf in TWRP?? sorry but I've been on Gnex and haven't had a moto since the droid x... Things have changed a bit.
Sent from my XT1049 using xda app-developers app
kicker22004 said:
Wait... Did I miss read that... You can flash sbf in TWRP?? sorry but I've been on Gnex and haven't had a moto since the droid x... Things have changed a bit.
Sent from my XT1049 using xda app-developers app
Click to expand...
Click to collapse
Yes, you miss read.. I was saying that he could just flash the SBF (implying RSDLite) or unzip it and mfastboot flash "part"
because being unlocked he could still root afterwards
OK that's what I thought. Thanks again for the info..looks like I'll sit tight with my unlocked bootloader until RW gets 4.4 update.
Sent from my XT1049 using xda app-developers app