Related
I am ever impatient. So when I saw new factory images up on the Google page, I just had to try them out. I upgraded to LMY47E, then naturally the next day I saw the news about LMY47M. Being that I'm a T-Mobile customer, I want the M version (reported the T-Mobile version) of the new 5.1. Unfortunately, as part of the LMY47E upgrade, the bootloader was moved from 71.05 to 71.08.
Now, trying to flash factory images from LRX22C results in a bootloader mismatch error. I got around this by manually flashing radio, system, boot, etc. images on the phone, and I do in fact now have the 5.01 build showing. However, when I try to sideload the LMY47M build, I'm receiving an error from this line in the updater script:
Code:
#getprop("ro.build.fingerprint") == "google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys" ||
abort("Package expects build fingerprint of google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
It's stating that I have 5.0.2 LRX22G signed with test keys. I don't know how I would have got an engineering build installed from flashing factory firmware from the Google page, but apparently something is confused somewhere along the way. The best I can guess is that perhaps that's some leftover remnants from when I had installed a CM12 nightly build (which I believe is based on 5.0.2).
I don't know what I need to flash with what to get that cleared so I can sideload the LMY47M OTA, and I'm concerned that I may be unable to properly upgrade to additional OTA upgrades if there's a missmatch along the way. There was a confirmed update coming to move from LMY47E to LMY47M per T-Mo support , also confirmed by @askdes) but again, if I have some funky mismatched stuff, unsure if I can upgrade to LMY47E again and still expect to receive the OTA.
I'd love to have someone with more knowledge of these wonderful things weigh in on this. Educated opinions are always welcome, but someone with actual first-hand knowledge would be incredibly helpful to my sanity as well.
Thanks!
Theres nothing you can do to receive the OTA now.
Maybe the M factory image will become available. If so, you'll be able to flash that. Well at least the system and boot image. If the bootloader is newer, that too.
I suppose the other options are that if someone could install TWRP with an unmodified, unrooted M on, they could take a backup of system and boot and give you them to do a Nandroid restore via TWRP... Or maybe someone can take a system dump for you. But you cannot downgrade the bootloader.
mikecole79 said:
I am ever impatient. So when I saw new factory images up on the Google page, I just had to try them out. I upgraded to LMY47E, then naturally the next day I saw the news about LMY47M. Being that I'm a T-Mobile customer, I want the M version (reported the T-Mobile version) of the new 5.1. Unfortunately, as part of the LMY47E upgrade, the bootloader was moved from 71.05 to 71.08.
Now, trying to flash factory images from LRX22C results in a bootloader mismatch error. I got around this by manually flashing radio, system, boot, etc. images on the phone, and I do in fact now have the 5.01 build showing. However, when I try to sideload the LMY47M build, I'm receiving an error from this line in the updater script:
Code:
#getprop("ro.build.fingerprint") == "google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys" ||
abort("Package expects build fingerprint of google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
It's stating that I have 5.0.2 LRX22G signed with test keys. I don't know how I would have got an engineering build installed from flashing factory firmware from the Google page, but apparently something is confused somewhere along the way. The best I can guess is that perhaps that's some leftover remnants from when I had installed a CM12 nightly build (which I believe is based on 5.0.2).
I don't know what I need to flash with what to get that cleared so I can sideload the LMY47M OTA, and I'm concerned that I may be unable to properly upgrade to additional OTA upgrades if there's a missmatch along the way. There was a confirmed update coming to move from LMY47E to LMY47M per T-Mo support , also confirmed by @askdes) but again, if I have some funky mismatched stuff, unsure if I can upgrade to LMY47E again and still expect to receive the OTA.
I'd love to have someone with more knowledge of these wonderful things weigh in on this. Educated opinions are always welcome, but someone with actual first-hand knowledge would be incredibly helpful to my sanity as well.
Thanks!
Click to expand...
Click to collapse
What about relashing the factory image? Of course, this would wipe all data, config, apps, etc.
clairez said:
What about relashing the factory image? Of course, this would wipe all data, config, apps, etc.
Click to expand...
Click to collapse
Thank you both for the replies. My course at this point seems to be "wait until M is up on the factory images page", which is what I suspected.
I have done a full factory flash of the LRX22C image, manually (since the script fails because of the newer bootloader) and it has still left me with the engineering build stamp showing. Any idea where that information is coming from? The image I used to flash back was the LRX22C for Shamu from developers <dot> google <dot> com/android/nexus/images. I would think that would have wiped the world (exception of the bootloader that doesn't know how to travel back in time; should really introduce that thing to Doc....). I'm not sure if it's because of the bootloader itself, or because of some other thing that just didn't get wiped properly. I flashed the radio, boot, cache, recovery, userdata, and system images initially, then re-flashed recovery to TWRP 2.8 after. Where does ro.build.fingerprint get it's information from? Is that all from the bootloader?
clairez said:
What about relashing the factory image? Of course, this would wipe all data, config, apps, etc.
Click to expand...
Click to collapse
But you can not flash an older bootloader So far for the developer phone At least HTC has S-Off.
gee2012 said:
But you can not flash an older bootloader So far for the developer phone At least HTC has S-Off.
Click to expand...
Click to collapse
I could be wrong (often am), but I thought several folks tried and succeeded with a factory image flash, by using the following methodology:
1. If your phone is showing OEM Unlock in the developer options and you can boot into recovery, then
2. Boot into android and remove all security
3. Set OEM Unlock and USB debugging
4. Perform several reboots to ensure OEM Unlock is persistent (if not, do not proceed)
5. Perform a factory reset/data wipe in recovery
6. Reflash the 5.01 factory image (or wait for 5.1 M version) using the manual method located here:
[TUTORIAL][GUIDE][HOW TO] Flash Factory Images || Unroot || Relock bootloader
http://forum.xda-developers.com/nexu...shamu-t2954008
* Use Method 2 from this tutorial, Method 1 does not work
7. You can relock the bootloader as outlined in the tutorial.
8. At this point if all went as expected, the N6 is factory fresh and eligible for the OTA.
But before you proceed check out some of the other posts to ensure that others have succeeded. So many reports of bricked phones it is hard to tell what caused the problem.
I have used the above method several times, but only reflashing to a newer version.
Hope this helps ....
PS: I missed the mention of CM12! There are so many variables in your situation, I am unsure now that there is a way back. So many of the hard bricked cases involved CM12. Good luck, I hope you come out of this right side up!
mikecole79 said:
Thank you both for the replies. My course at this point seems to be "wait until M is up on the factory images page", which is what I suspected.
I have done a full factory flash of the LRX22C image, manually (since the script fails because of the newer bootloader) and it has still left me with the engineering build stamp showing. Any idea where that information is coming from? The image I used to flash back was the LRX22C for Shamu from developers <dot> google <dot> com/android/nexus/images. I would think that would have wiped the world (exception of the bootloader that doesn't know how to travel back in time; should really introduce that thing to Doc....). I'm not sure if it's because of the bootloader itself, or because of some other thing that just didn't get wiped properly. I flashed the radio, boot, cache, recovery, userdata, and system images initially, then re-flashed recovery to TWRP 2.8 after. Where does ro.build.fingerprint get it's information from? Is that all from the bootloader?
Click to expand...
Click to collapse
I am in the same situation as you are, mine shows my build fingerprint as "google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy020120939:eng/test-keys" I have gone through the same steps as you have and tried to reflash LRX22C. I guess we wait until the factory image!
wadsface said:
I am in the same situation as you are, mine shows my build fingerprint as "google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy020120939:eng/test-keys" I have gone through the same steps as you have and tried to reflash LRX22C. I guess we wait until the factory image!
Click to expand...
Click to collapse
Have you flashed a custom kernel? Sounds like a non-google boot.IMG or something is on the device.
clairez said:
4. Perform several reboots to ensure OEM Unlock is persistent (if not, do not proceed)
Click to expand...
Click to collapse
That is absurd.
Unlocked is unlocked is unlocked.
The only thing that may not be persistent is the flag in the dev settings menu, ENABLE oem unlock.
Once you enable the unlock, you may *immediately* try to unlock it. If the enable setting isn't persistent, then it just won't unlock.
ONCE IT IS UNLOCKED, IT IS UNLOCKED. DON'T EVER LOCK IT AGAIN.
I also received that error when trying to sideload the OTA. The only modification I made was using a custom kernel, but I flashed the stock boot.img before attempting to sideload. So I'm not sure what could have caused the error?
I just read somewhere that we can get the sideload to work if a line in the updater script is deleted or modified. Has anyone else read this?
To sideload an OTA you need a stock recovery. I have been unable to sideload an OTA with a custom recovery installed since 5.0. The Dees Troy (guessing TWRP recovery) in the path is a dead giveaway that it is from the recovery. I don't think it is checking bootloader version when sideloading OTA.
android_mp99 said:
TI don't think it is checking bootloader version when sideloading OTA.
Click to expand...
Click to collapse
It is. OTA doesn't replace the bootloader. It patches the existing BL with the deltas - I.e. the code that have changed. Obviously the bootloader must be the exact expected version for a patch to work, so it is definitely being checked when you install an OTA, no matter what method you use..
If you patched the BL with an incorrect patch, you could very easily be facing a brick.
Then I'm guessing the people that were able to sideload the OTA with the new bootloader got lucky or are talking a bunch of BS (totally possible). I haven't tried it myself but I know for sure that the stock recovery is needed to sideload the OTA since 5.0 and the error reported earlier by some could be because of the recovery installed.
You definitely need stock recovery, yes
Since I have never updated my bootloader, I'm inclined to think it must be recovery. I was trying to sideload via TWRP.
doitright said:
[snip]
ONCE IT IS UNLOCKED, IT IS UNLOCKED. DON'T EVER LOCK IT AGAIN.
Click to expand...
Click to collapse
There are many reasons that people want to have a locked bootloader, such as, among many other reasons, your employer requires it, for example.
rootSU said:
It is. OTA doesn't replace the bootloader. It patches the existing BL with the deltas - I.e. the code that have changed. Obviously the bootloader must be the exact expected version for a patch to work, so it is definitely being checked when you install an OTA, no matter what method you use..
If you patched the BL with an incorrect patch, you could very easily be facing a brick.
Click to expand...
Click to collapse
No, OTA updates do not verify which bootloader your device is running, and they do NOT patch the bootloader -- they fully replace it.
android_mp99 said:
Then I'm guessing the people that were able to sideload the OTA with the new bootloader got lucky or are talking a bunch of BS (totally possible). I haven't tried it myself but I know for sure that the stock recovery is needed to sideload the OTA since 5.0 and the error reported earlier by some could be because of the recovery installed.
Click to expand...
Click to collapse
rootSU said:
You definitely need stock recovery, yes
Click to expand...
Click to collapse
You can use TWRP as well. It just requires an edit to one line in the updater-script file.
efrant said:
There are many reasons that people want to have a locked bootloader, such as, among many other reasons, your employer requires it, for example.
No, OTA updates do not verify which bootloader your device is running, and they do NOT patch the bootloader -- they fully replace it.
Click to expand...
Click to collapse
Yes you're right, my mistake.
efrant said:
You can use TWRP as well. It just requires an edit to one line in the updater-script file.
Click to expand...
Click to collapse
You need to have stock recovery to apply a stock ota. You could edit the updater-script for any amount of purposes, but that isn't really the point. The people who simply want to "check for updates" and use the standard mechanism to apply it, it will not work with twrp.
rootSU said:
You need to have stock recovery to apply a stock ota. You could edit the updater-script for any amount of purposes, but that isn't really the point. The people who simply want to "check for updates" and use the standard mechanism to apply it, it will not work with twrp.
Click to expand...
Click to collapse
Yeah, ok, but we were talking about sideloading the OTA, no? You can sideload an OTA update file (or even flash it directly from your device) using TWRP just by editing one line. But yes, as far as clicking on "check for updates" and having it install that way requires the stock recovery.
efrant said:
Yeah, ok, but we were talking about sideloading the OTA, no? You can sideload an OTA update file (or even flash it directly from your device) using TWRP just by editing one line. But yes, as far as clicking on "check for updates" and having it install that way requires the stock recovery.
Click to expand...
Click to collapse
You technically can. But then you edit the line, side load the ota via twrp, and immediately flash SuperSU to stop the updated system image from replacing the recovery.. It all seems a little pointless to me. If you're going to modify an ota (or download a modified ota) to side load from custom recovery rather than use a pre-rooted ROM.zip, it seems to add unnecessary steps.
I did do a search for "November Security Update" but didn't find anything.
Specifically I just received the November Security Update from Google but cannot apply it.
I am running a modified boot image to allow me to root the phone.
Is it possible all I have to do is return to unrooted status (disable SuperSU) and apply this patch?
UPDATE: LOL, that would be a resounding NO. It does say "Error in Recovery" but now the Update is gone.... and the Security Patch level still says 10/1
You have to fastboot flash system.img from factory image. Any OTA is not possible unless you are full stock, unmodified.
Not sure if the security updates end up packaged into system.img or not. If not, you will have to flash stock recovery, system and boot, then accept the OTA then re-flash custom recovery and re-root.
danarama said:
You have to fastboot flash system.img from factory image. Any OTA is not possible unless you are full stock, unmodified.
Not sure if the security updates end up packaged into system.img or not. If not, you will have to flash stock recovery, system and boot, then accept the OTA then re-flash custom recovery and re-root.
Click to expand...
Click to collapse
That's probably what will be needed as the security update is pretty fresh and proabably not in the stock system I would think. And then, to get back to rooted status, I would have to revert to the modified image, thus undoing the application of the security update? Ehhh, not going unrooted, oh well.
And thanks btw
Can't you adb sideload? Isn't that possible when the boot image is modified?
Sent from my Nexus 6 using Tapatalk
swa100 said:
Can't you adb sideload? Isn't that possible when the boot image is modified?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
No.. OTA checks for stock recovery, boot and system. Any amendment it will fail. It's in the zip file regardless of how you apply that zip, it will always fail.
Sent from my Nexus 6 using Tapatalk
I'm lost...please help
So I bought my unlocked Nexus 6 from Amazon. I was probably stupid, and was to impatient to wait for the OTA to Android 6. So I followed the Andriod Central instructions on how to do the basic download adb tools, unlock phone, flashed. the stock Andriod 6 image (MRA58K). And everything went great. I failed to relock, but it didn't seem to be a big deal.
Then I noticed I didn't get the November Security update.
Then I thought I needed to relock the phone. So I booted into the recovery and ran fastboot oem lock.
So now I am back to a fresh phone and I am downloading my apps in Google Play.
But the November Updates didn't come through.
What did I do wrong?
http://forum.xda-developers.com/nexus-6/help/nexus-6-mra58k-n-r-forced-encryption-t3242664/page2
jgriesshaber said:
So I bought my unlocked Nexus 6 from Amazon. I was probably stupid, and was to impatient to wait for the OTA to Android 6. So I followed the Andriod Central instructions on how to do the basic download adb tools, unlock phone, flashed. the stock Andriod 6 image (MRA58K). And everything went great. I failed to relock, but it didn't seem to be a big deal.
Then I noticed I didn't get the November Security update.
Then I thought I needed to relock the phone. So I booted into the recovery and ran fastboot oem lock.
So now I am back to a fresh phone and I am downloading my apps in Google Play.
But the November Updates didn't come through.
What did I do wrong?
Click to expand...
Click to collapse
Locked bootloader has nothing to do with it.
Title says all. This is for the American Retail variant. Does not include Oreo.
Glad to see that Moto is being consistent with Security patches though!
Edit:. I meant April 1st 2018!
This is for all varients
reteu,retbr,Retin also got updates
Sent from my Moto G5S Plus using XDA Labs
Yet to be seen in retapac though
Adi5 said:
This is for all varients
reteu,retbr,Retin also got updates
Click to expand...
Click to collapse
The day before I saw the update notification, but didn't update as I wanted to backup some of my files. Later when I checked for update the notification was gone. Says phone is upto date with March patch.
JaggedPill said:
The day before I saw the update notification, but didn't update as I wanted to backup some of my files. Later when I checked for update the notification was gone. Says phone is upto date with March patch.
Click to expand...
Click to collapse
I didn't had notification,now flashed custom rom
Flash full firmware for ur software channel
Retid here, still no updates
Got it..retin software channel.
In retla was not released
April Patch also released for retapac ?
I only just got 116-48-12 yesterday on retus, so I'm not gonna hold my breath.
you can edit the thread title by editing your post and pressing "go advanced"
Meanwhile retgb is still on October 2017. This is the last time I buy Motorola.
Hi all,
I've just applied the 01 April Security Patch and my phone has rebooted into TWRP. If I select to reboot, it starts to reboot and goes back into TWRP. Any ideas as to how I can get it to reboot back to normal ?
So I'm basically stuck in a TWRP Bootloop
Thanks in advance
championc said:
Hi all,
I've just applied the 01 April Security Patch and my phone has rebooted into TWRP. If I select to reboot, it starts to reboot and goes back into TWRP. Any ideas as to how I can get it to reboot back to normal ?
So I'm basically stuck in a TWRP Bootloop
Thanks in advance
Click to expand...
Click to collapse
Hi, you should know that you can't get updates via OTA once you have modified system, and unlocking bootloader and flashing TWRP is certainly a system modification, so I really hope that you made a TWRP backup before trying to update. In case you didn't, try flashing official firmware using fastboot, also there is one post in XDA with a TWRP backup in case you messed up, if you can't use fastboot or don't have a backup, try using that one. Remember to NEVER update via OTA unless your phone is fully unmodified.
Juancasa14 said:
Hi, you should know that you can't get updates via OTA once you have modified system, and unlocking bootloader and flashing TWRP is certainly a system modification, so I really hope that you made a TWRP backup before trying to update. In case you didn't, try flashing official firmware using fastboot, also there is one post in XDA with a TWRP backup in case you messed up, if you can't use fastboot or don't have a backup, try using that one. Remember to NEVER update via OTA unless your phone is fully unmodified.
Click to expand...
Click to collapse
U can update with unlocked bootloader. Only without mods like root or twrp
Adi5 said:
U can update with unlocked bootloader. Only without mods like root or twrp
Click to expand...
Click to collapse
Yeah I know, sorry if I didn't make myself clear, thanks for explaining
Championc were you able to recover your phone?
It's security updates up to May 1st. I can't install it though it fails and I am stock with unlocked bootloader.
Comet1966 said:
It's security updates up to May 1st. I can't install it though it fails and I am stuck with an unlocked bootloader.
Click to expand...
Click to collapse
I'm in the same boat. I just followed this thread and did everything right when restoring my stock ROM for Sprint. The only thing I didn't do was lock the bootloader. I cannot do OTA updates, fails every time. Someone mentioned a few pages in that thread, that right now it's a 50/50 chance due to an unknown variable. Give the forum time we will get it
Link to thread: https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
I'll try tonight after the Gym and see if I can get it to update for me
JordanFromIT said:
I'm in the same boat. I just followed this thread and did everything right when restoring my stock ROM for Sprint. The only thing I didn't do was lock the bootloader. I cannot do OTA updates, fails every time. Someone mentioned a few pages in that thread, that right now it's a 50/50 chance due to an unknown variable. Give the forum time we will get it
Link to thread: https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Click to expand...
Click to collapse
For me, that variable is twrp. If I flashall to stock I can take the ota, then resinstall twrp and root after. Worked today too.
I was going to install LineageOS and just gave up on it lol. So I flash-all'd back to stock and the OTA worked this time.
So is there a method for clean flashing or i just flash over a rom using fastboot? I tried flashing a retail rom on my tmobile variant, it work but some things were broken.
Comet1966 said:
I was going to install LineageOS and just gave up on it lol. So I flash-all'd back to stock and the OTA worked this time.
Click to expand...
Click to collapse
which flashall did you use? I'm trying to do this too and it fails no matter what. did you also re-lock the boot loader for the ota to work?
I've tried unlocked and locked and it still doesn't take the OTA for me.
byt3b0mb said:
which flashall did you use? I'm trying to do this too and it fails no matter what. did you also re-lock the boot loader for the ota to work?
I've tried unlocked and locked and it still doesn't take the OTA for me.
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
I used the sprint oreo flash-all from that link, 2nd post. I just ran it and then updated without issue.
Comet1966 said:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
I used the sprint oreo flash-all from that link, 2nd post. I just ran it and then updated without issue.
Click to expand...
Click to collapse
oh. I am on T-Mobile. seems that im on december security patch although im on 27.1. something is wrong with my phone...
You'd think Motorola would have released an updated flash-all. Maybe they have?
Josh McGrath said:
You'd think Motorola would have released an updated flash-all. Maybe they have?
Click to expand...
Click to collapse
I doubt it. The Feb release of the Dec update got released two months later. (Apr 7th)
This phone is really weird. I got the update to work the very first time I flashall but twrp bootlooped and it won't install after the second flashall, tried multiple times.
This phone is really software wonky
the zip files from Tmobiie are NASH_TMO_C_OCX27.109-51.... Does anyone know the difference between this and the OCX27.109-48-6?
kendallgreen said:
the zip files from Tmobiie are NASH_TMO_C_OCX27.109-51.... Does anyone know the difference between this and the OCX27.109-48-6?
Click to expand...
Click to collapse
When the update first came out, the December path I think, it was simply generic Android security updates, nothing specific to our phone or fixes, at least for the TMobile version
My phone was rooted, so I thought it could be the problem. So I made a factory reset and uninstalled magisk.
Anyway, it keeps failing to install a new security patch. It keeps trying to install and always says there was a problem in the installation. What could be causing it?
I'm running the stock OTA with december security patch, since january and february had annoying bugs.
matheusgoes said:
My phone was rooted, so I thought it could be the problem. So I made a factory reset and uninstalled magisk.
Anyway, it keeps failing to install a new security patch. It keeps trying to install and always says there was a problem in the installation. What could be causing it?
I'm running the stock OTA with december security patch, since january and february had annoying bugs.
Click to expand...
Click to collapse
Try flashing stock ROM, it worked for me
Firexxe69 said:
Try flashing stock ROM, it worked for me
Click to expand...
Click to collapse
I've never flash any ROM. Do you have any tutorial I can follow?
matheusgoes said:
I've never flash any ROM. Do you have any tutorial I can follow?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445/page68 download the fastboot version, then flash it using fastboot commands
Firexxe69 said:
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445/page68 download the fastboot version, then flash it using fastboot commands
Click to expand...
Click to collapse
you directly flashed update?
i cant update since december security patch and now if i flash march s.p. with fastboot that will work?
Maharram said:
you directly flashed update?
i cant update since december security patch and now if i flash march s.p. with fastboot that will work?
Click to expand...
Click to collapse
I never tried it, but when i'm on december patch, i flashed the december patch, then update it from system update. Make sure to backup your data because it may erase your data.
I tried to flash december s.p.
Got the message "Flashing error bluetooth_a" mi flash tool. Do someone know how to solve it?