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.
So I've tried to do my due diligence researching but as a noob a lot of this is very confusing. My main goal is to have verizon unlimited tethering (currently ota 5.0) I installed and ran Kingroot thinking I could just edit the system/build.prop file and be on my way, that doesn't appear to work. So anyways I was wondering if I buy sunshine unlock my bootloader would I need to buy mofo to enable use of TWRP or would the KingRoot temp root work for that? Don't have much money at the moment and am trying to see if I can just pay for the Sunshine. Any thoughts or help would be greatly appreciated?
Root with Kingroot and unlock with Sunshine. Mofo not needed. Install a recovery to your liking.
Sorry if this is really basic but I'm just really nervous about missing something. So I ran sunshine unlocked my bootloader and have root, installed busybox and TWRP. I'm currently on 5.0 verizon OTA and want to flash this stock rom http://forum.xda-developers.com/showpost.php?p=62785699&postcount=781 with G-apps. Don't I need to update my bootloader to 5.1? I'm assuming I do but most of the directions I've found are for doing that through mofo. Do you know where there is a bootloader img for 5.1 that I can flash through TWRP? Again sorry if this is really basic and thanks for any help. Also is there anything else I'm missing/forgetting that I would need to flash?
bengeo31 said:
Sorry if this is really basic but I'm just really nervous about missing something. So I ran sunshine unlocked my bootloader and have root, installed busybox and TWRP. I'm currently on 5.0 verizon OTA and want to flash this stock rom http://forum.xda-developers.com/showpost.php?p=62785699&postcount=781 with G-apps. Don't I need to update my bootloader to 5.1? I'm assuming I do but most of the directions I've found are for doing that through mofo. Do you know where there is a bootloader img for 5.1 that I can flash through TWRP? Again sorry if this is really basic and thanks for any help. Also is there anything else I'm missing/forgetting that I would need to flash?
Click to expand...
Click to collapse
You absolutely do not want to upload your partition table (the gpt.bin file). Your Sunshine unlock is based in part on the original partition table in your phone and you may/will lose root if you update to the 5.1 gpt.bin. The post you are referencing is to upgrade the first release of 5.1 to 5.1 with the stagefright patch. You need to follow the upgrade instructions in the first post of that thread to be on 5.1 v23.32-25-3 before using the info in post 781 to patch that version to 23.32-25-5.
The short version of the process is to download this file: 5.1bins.7z Extract the files from the archive and then use these commands:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
You will not flash the recovery.img file because you already have TWRP as your recovery.
After you do the above steps then select the option to go into recovery, when TWRP launches flash this file: xt1096-5.1-stock-20150820.zip After it flashes use the clear cache/dalvik button and then reboot the phone into 5.1 v23.32-25-3
Then you can use the instructions in post 781 to upgrade to 23.32-25-5, the current version. You have to do the first one, because the files in post 781 are patch files that only work with the -3 version. Clear as mud?
mikeoswego said:
You absolutely do not want to upload your bootloader (the gpt.bin file). Your Sunshine unlock is based in part on the original bootloader file in your phone and you will lose root if you update to the 5.1 bootloader. All the bootloader does is start up the phone, tell it to load the kernel and then it exits. It also handles fastboot flashing but there is no functional difference in the newer bootloader except to stop you from having root.
Click to expand...
Click to collapse
Are you absolutely certain about this? I'm under the impression that once your bootloader is unlocked root is a simple matter of installing TWRP and SUPERSU.
mbkintner said:
Are you absolutely certain about this? I'm under the impression that once your bootloader is unlocked root is a simple matter of installing TWRP and SUPERSU.
Click to expand...
Click to collapse
You're correct that your bootloader must be unlocked to install TWRP and SuperSU which is all that is needed for root.
Unless you've gotten an unlock code from Motorola, you paid money to get your bootloader unlocked. If you flash a new bootloader, the verification bypass that allows you to run TWRP will no longer work. If you fastboot flash the new bootloader before upgrading the rom you would lose root because you would no longer be able to use TWRP to flash SuperSU for the new ROM. If you waited to flash the bootloader after flashing the new ROM, you could keep root but still not have TWRP to flash future updates. IF there becomes a way to unlock the new bootloader, then you can pay again to unlock that one to regain the ability to run TWRP. I've never tried to go backward on bootloader versions, there seem to be a lot of warnings about bricking phones by doing that.
If you have an unlock code from Motorola, lucky you, don't worry about any of this.
bengeo31 said:
Don't I need to update my bootloader to 5.1?
Click to expand...
Click to collapse
You can run 5.1 ROMs and kernels while staying on the 5.0 bootloader and partition table.
mikeoswego said:
You're correct that your bootloader must be unlocked to install TWRP and SuperSU which is all that is needed for root.
Unless you've gotten an unlock code from Motorola, you paid money to get your bootloader unlocked. If you flash a new bootloader, the verification bypass that allows you to run TWRP will no longer work. If you fastboot flash the new bootloader before upgrading the rom you would lose root because you would no longer be able to use TWRP to flash SuperSU for the new ROM. If you waited to flash the bootloader after flashing the new ROM, you could keep root but still not have TWRP to flash future updates. IF there becomes a way to unlock the new bootloader, then you can pay again to unlock that one to regain the ability to run TWRP. I've never tried to go backward on bootloader versions, there seem to be a lot of warnings about bricking phones by doing that.
If you have an unlock code from Motorola, lucky you, don't worry about any of this.
Click to expand...
Click to collapse
I double checked with jcase and others in the official Sunshine thread and can confirm that upgrading to the latest release, to include your bootloader, will not cause your bootloader to relock. Sunshine is not a bootloader bypass, it is a permanent unlock. You will lose root but as stated, simply install TWRP and SuperSu to regain it.
Start reading here to see the discussion. http://forum.xda-developers.com/showthread.php?p=62893130
mbkintner said:
I double checked with jcase and others in the official Sunshine thread and can confirm that upgrading to the latest release, to include your bootloader, will not cause your bootloader to relock. Sunshine is not a bootloader bypass, it is a permanent unlock. You will lose root but as stated, simply install TWRP and SuperSu to regain it.
Start reading here to see the discussion. http://forum.xda-developers.com/showthread.php?p=62893130
Click to expand...
Click to collapse
Another bit of internet lore shot down. Thanks for the info!
I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. I would also like the bootloader to be locked again as well, I'm not sure whether or not flashing stock firmware would do this. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.
Ladyslayer said:
I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.
Click to expand...
Click to collapse
this is not quite a normal request.
any and all changes done to your phone are done at your own risk, no guarantee that the process will be "safe". and no guarantee the end result will be as expected.
I can upload stock system, boot, and recovery images.
download them, unzip the file. put the 3 .img files to the phone.
reboot phone to twrp.
select install, browse to the folder you loaded files to, you should not see the file yet. Select flash image in lower part of screen. Now select system.img, on next screen select system and swipe to confirm.
when done do same for boot.img to boot
then recovery to recovery
when all three are done do a wipe(factory reset)
this should bring you back to prime v6.1
be advised that re-locking the boot loader has potential of bricking the pone so it is not advised to do it.
also on all the early versions there are reports that after ota update with unlocked bootloader it caused a bootloop most times it was recoverable by performing "oem unlock" again.
once booted to v6.1 I suspect there will be proper update notice. but if not here is a list of the official update download links.
6.1 to 6.4
http://hwfotadown.mayitek.com/ota/r....4_GENERIC_6.0_20160710-00151468612925207.zip
6.4 to 6.5
http://hwfotadown.mayitek.com/ota/r....5_GENERIC_6.0_20160729-21551470255454500.zip
6.5 to 6.6
http://hwfotadown.mayitek.com/ota/r....6_GENERIC_6.0_20160823-20201472826184648.zip
7.4.2 to 8.4
http://hwfotadown.mayitek.com/ota/r..._V8.4_GENERIC_6.0_20170505-18551493981392.zip
17 to 21
http://hwfotadown.mayitek.com/ota/r...RIC_6.0_20170505-17451495815395129/update.zip
==>>V6.1 images.zip
.
.
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
well you can go back to locked but it is tricky. Think of it like this.
unlocking , allows anything you put on phone to try and load.
when you re-lock it only properly signed images are allowed to load.
so you can potentially lock yourself out of allowing phone to boot up, so the warning is more relevant when trying to go back to a locked state.
kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
Sorry guys I have yet to try it out, I don't have a lot of time and am a little nervous to bite the bullet. @kfn, did you follow the guidelines in the above post to restore to original condition or a different set of instructions from somewhere else? Btw any suggestions on how to back up pretty much everything? Sorry Noob here obviously.
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Which version update was it?
I can't be certain about the 8.4 or 21 updates, but older ones when that happened you needed to boot into fastboot mode and do oem unlock again.
kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Did you re-lock the bootloader or was this because of an unlocked bootloader?
It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.
kfn said:
It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.
Click to expand...
Click to collapse
Do you still have the phone? Have you done the OTA updates since then with an unlocked bootloader?
did not try another OTA, put back modified ROM and disabled OTA.
Here post #312 with similar unanswered question about relocking bootloader, it is unclear for me if another OTA would properly relock it without bricking.
https://forum.xda-developers.com/r1...tock-rom-6-5-flashed-via-twrp-t3455532/page32
@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.
Ladyslayer said:
@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.
Click to expand...
Click to collapse
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.
mrmazak said:
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.
Click to expand...
Click to collapse
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?
Ladyslayer said:
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?
Click to expand...
Click to collapse
I do not know for sure. And there fore cannot recommend to do it. In the event something goes wrong and bootloader is locked, you cannot use fastboot to flash a repair, there fore MY opinion is the same "DO NOT relock bootloader". If something goes wrong it will be a brick.
Run stock version un modified all you want but if you unlocked I do not think you should relock. My opinion, do as you want.
Hello there.
My G5s+ is suggesting a security update. But since I did unlock the bootloader and rooted it with magisk I did not install it.
My question is: What is the best way to update the phone?
Just flash the new stock rom? And where do I get those?
Thanks in advance.
Nobody here that can tell me how to upgrade?
Should I just flash the new version if I get it somewhere?
Mr.Chainsaw said:
Nobody here that can tell me how to upgrade?
Should I just flash the new version if I get it somewhere?
Click to expand...
Click to collapse
Unlocked bootloader will not affect the OTA installation..!
The reason the OTA-Update fails is that one of the boot, system, logo or recovery partitions are changed.
Magisk modifies the boot image.
On rooted device..OTA may brick the device..so avoid OTA installation..!
Reply your current build Number from about phone..
Do a clean flash.
crazytech2 said:
On rooted device..OTA may brick the device..so avoid OTA installation..!
Click to expand...
Click to collapse
Thats why I did not do it yet. But I still want to do the update somehow.
crazytech2 said:
Reply your current build Number from about phone..
Click to expand...
Click to collapse
The Build No is
NPSS26.116-26-8
Mr.Chainsaw said:
Thats why I did not do it yet. But I still want to do the update somehow.
The Build No is
NPSS26.116-26-8
Click to expand...
Click to collapse
Flash 26-11 full firmware
Where can I find full firmware versions of the stock rom to flash?
My build version is: NPSS26.116-26-4
As I understand it, there are two new security patches since that version? If I'm flashing one of the newer versions, is it just a case of dirty flashing it normally through twrp? No need to factory reset?
Chemacky said:
Where can I find full firmware versions of the stock rom to flash?
My build version is: NPSS26.116-26-4
As I understand it, there are two new security patches since that version? If I'm flashing one of the newer versions, is it just a case of dirty flashing it normally through twrp? No need to factory reset?
Click to expand...
Click to collapse
If that is the firmware build you need, you could try the firmware here: https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/ but ensure you download the correct firmware. (credit to: https://forum.xda-developers.com/moto-g5s-plus/how-to/xt1804-able-to-lock-bootloader-npss26-t3722572) Also, verify it is the firmware you require and was the latest firmware build on your device - please don't downgrade with stock firmware (else you may hard brick with OTA updates corrupting your bootloader)...
Stock OTA updates, as mentioned above, require fully stock firmware - they will not flash with root, modifications or TWRP (and attempting to flash via TWRP may soft bootloop your device). Thus, you must re-flash the stock firmware - you may be able to save your data by omitting the 'fastboot erase userdata' command and you do not have to re-lock your bootloader. However, I'm not familiar with the G5S Plus and I hope another user can provide you with flashing commands.
I would still recommend you make a backup of your device in TWRP and keep that safe, in case you have to wipe your data for stability.
Anyone plz give me the proper steps to install the ota..
Im on stock rom non rooted bootloader locked...
N also plz tell me the possible problems related to it...
https://drive.google.com/uc?id=14nWazUMHTyk-od6SF3KJOXVTOWZoC_Do&export=download
You may be able to ADB sideload this (credit to: https://forum.xda-developers.com/mo.../official-soak-8-0-0-download-how-to-t3743021 ). Though the steps are for the Z Play, they should be similar for the G5S Plus, my edits are in italics. I however have not tried this procedure, but seems to work for users in that thread.
You could try:
Install ADB on your PC | Copy OTA ZIP to Installation directory (I imagine this is your ADB folder).
Boot your G5S Plus to Fastboot > Recovery > again to Stock Recovery
Select Apply update through ADB
Open ADB on your PC
Connect your device via USB
adb sideload Blur_Version.26.336.15.sanders.retail.en.US.zip
Press enter and it will start. This will take around 30 mins, perhaps even up to an hour. This is a major software update.
EDIT - you could also try the first method (again, I've not tried it) https://forum.xda-developers.com/moto-z-play/help/sideload-addison-oreo-8-0-update-noob-t3779630
METHOD 1
A simplified way of updating using your device only. Untested by me but confirmed to be working.
Download
Move this zip file to the root directory of your internal storage
Go to Settings>Apps and Notifications>App permissions>Storage. In the top corner select the dots and activate 'Show system'. Find 'Motorola Update Services' and activate it
Reboot your device
The update should be detected by Update services automatically
Click to expand...
Click to collapse
Be warned that as you have a locked bootloader, you cannot downgrade your device. That means any bugs you encounter in the soak test by flashing this OTA you'll have to cope with. If you are not part of the soak test, you won't receive support from Motorola (as you're not supposed to have this file). You also need to get all the soak test patches or get the official Oreo stock firmware to return back to official OTA, else you will be stuck on the soak test. Once you flash this, it becomes your responsibility to keep your device updated and find all the relevant soak test patches or hope the Oreo stock firmware is leaked.
A few more things from the OTA itself:
1)This OTA update requires Sanders G5S Plus and you need to be on NPSS26.116-61-8, will update your device to the Oreo soak test OPS28.49-2
Code:
Package expects build thumbprint of 8.1.0/OPS28.49-2/202c:user/release-keys or 7.1.1/NPSS26.116-61-8/15:user/release-keys
. If you are not on NPSS26.116-61-8 or OPS28.49-2, this OTA will not flash. Also, your device must be fully stock for the OTA - no TWRP, no root, no debloating etc. Unlocked bootloader status should not matter, but any modifications will mean you have to re-flash the stock ROM fully.
2)Updates your modem (and Widevine DRM), OEM, system, kernel, GPT and bootloader. As it updates your GPT/bootloader, it's not safe to downgrade to Nougat (but in your case, you've got a locked bootloader so you cannot downgrade).
3)For those with IMEI issues, this OTA wipes your modemst1 and modemst2.
Thnx a lot!!!
echo92 said:
You may be able to ADB sideload this (credit to: https://forum.xda-developers.com/mo.../official-soak-8-0-0-download-how-to-t3743021 ). Though the steps are for the Z Play, they should be similar for the G5S Plus, my edits are in italics. I however have not tried this procedure, but seems to work for users in that thread.
You could try:
Install ADB on your PC | Copy OTA ZIP to Installation directory (I imagine this is your ADB folder).
Boot your G5S Plus to Fastboot > Recovery > again to Stock Recovery
Select Apply update through ADB
Open ADB on your PC
Connect your device via USB
adb sideload Blur_Version.26.336.15.sanders.retail.en.US.zip
Press enter and it will start. This will take around 30 mins, perhaps even up to an hour. This is a major software update.
EDIT - you could also try the first method (again, I've not tried it) https://forum.xda-developers.com/moto-z-play/help/sideload-addison-oreo-8-0-update-noob-t3779630
Be warned that as you have a locked bootloader, you cannot downgrade your device. That means any bugs you encounter in the soak test by flashing this OTA you'll have to cope with. If you are not part of the soak test, you won't receive support from Motorola (as you're not supposed to have this file). You also need to get all the soak test patches or get the official Oreo stock firmware to return back to official OTA, else you will be stuck on the soak test. Once you flash this, it becomes your responsibility to keep your device updated and find all the relevant soak test patches or hope the Oreo stock firmware is leaked.
A few more things from the OTA itself:
1)This OTA update requires Sanders G5S Plus and you need to be on NPSS26.116-61-8, will update your device to the Oreo soak test OPS28.49-2
Code:
Package expects build thumbprint of 8.1.0/OPS28.49-2/202c:user/release-keys or 7.1.1/NPSS26.116-61-8/15:user/release-keys
. If you are not on NPSS26.116-61-8 or OPS28.49-2, this OTA will not flash. Also, your device must be fully stock for the OTA - no TWRP, no root, no debloating etc. Unlocked bootloader status should not matter, but any modifications will mean you have to re-flash the stock ROM fully.
2)Updates your modem (and Widevine DRM), OEM, system, kernel, GPT and bootloader. As it updates your GPT/bootloader, it's not safe to downgrade to Nougat (but in your case, you've got a locked bootloader so you cannot downgrade).
3)For those with IMEI issues, this OTA wipes your modemst1 and modemst2.
Click to expand...
Click to collapse
What about my data? Will that be wiped?
Saadatrm said:
What about my data? Will that be wiped?
Click to expand...
Click to collapse
OTA updates should not wipe your data usually. However, with any system update, there exists the possibility that you may have to factory reset your device if you experience instability. Back up any key files on your device. Also, if you have to factory reset, ensure you have backed up your SD card - if you have one as adopted internal storage; wiping your data may also wipe the encryption key used for the adopted SD card and so means your SD card may be unusable until you wipe that as well.
With such a major update, you may experience heating up of the device and battery drain as your device is setting up, but that should settle down within a day or two.
I want to but at the same time i dont want to try this. Moto!?! Took too much time still they need soak test
echo92 said:
OTA updates should not wipe your data usually. However, with any system update, there exists the possibility that you may have to factory reset your device if you experience instability. Back up any key files on your device. Also, if you have to factory reset, ensure you have backed up your SD card - if you have one as adopted internal storage; wiping your data may also wipe the encryption key used for the adopted SD card and so means your SD card may be unusable until you wipe that as well.
With such a major update, you may experience heating up of the device and battery drain as your device is setting up, but that should settle down within a day or two.
Click to expand...
Click to collapse
Last thing..
Im on Indian software channel.. N the ota seems to be US variant.. Will it mess with my ota?
Again Thnx a lot!!!
Saadatrm said:
Last thing..
Im on Indian software channel.. N the ota seems to be US variant.. Will it mess with my ota?
Again Thnx a lot!!!
Click to expand...
Click to collapse
Most of the OTA retail updates end in retail.en.US from what I've seen, so it seems to be a general Motorola naming system. It shouldn't mess with your future OTA, but again, once you flash this, you will not get official OTA updates until you get all the soak tests or flash the official Oreo firmware. Your device would be on the soak test OTA path if you flash this. You cannot flash the Nougat firmware or any Nougat OTA updates after using this as you have a locked bootloader.
echo92 said:
Most of the OTA retail updates end in retail.en.US from what I've seen, so it seems to be a general Motorola naming system. It shouldn't mess with your future OTA, but again, once you flash this, you will not get official OTA updates until you get all the soak tests or flash the official Oreo firmware. Your device would be on the soak test OTA path if you flash this. You cannot flash the Nougat firmware or any Nougat OTA updates after using this as you have a locked bootloader.
Click to expand...
Click to collapse
Can I flash all the requirements to get back the normal OTAs
Through Method 1.. If method 1 worked for me this time?
Saadatrm said:
Can I flash all the requirements to get back the normal OTAs
Through Method 1.. If method 1 worked for me this time?
Click to expand...
Click to collapse
I'm not sure what your question is asking - are you asking if you can flash the soak test OTA updates to get back to the official OTA?
If so, then yes - but you must find and flash all the soak test OTA updates - if you're not on the Motorola Feedback Network, you will not get the soak test OTA updates from Motorola. Thus, you have to manually apply them (can be through Method 1), again, it depends on if you can find the soak test OTA updates, whether it be from XDA or other channels. You have to apply the updates in sequence as well, you cannot miss one OTA update.
The other way is to flash the Oreo stock fastboot ROM, though that usually is leaked when the soak test is over.
echo92 said:
I'm not sure what your question is asking - are you asking if you can flash the soak test OTA updates to get back to the official OTA?
If so, then yes - but you must find and flash all the soak test OTA updates - if you're not on the Motorola Feedback Network, you will not get the soak test OTA updates from Motorola. Thus, you have to manually apply them (can be through Method 1), again, it depends on if you can find the soak test OTA updates, whether it be from XDA or other channels. You have to apply the updates in sequence as well, you cannot miss one OTA update.
The other way is to flash the Oreo stock fastboot ROM, though that usually is leaked when the soak test is over.
Click to expand...
Click to collapse
If im able to flash all the soak tests sequentially, will I get the official Oreo through OTA.. Or I have to flash that manually again?
N can that OREO STOCK FASTBOOT ROM be installed through Method 1?
Saadatrm said:
If im able to flash all the soak tests sequentially, will I get the official Oreo through OTA.. Or I have to flash that manually again?
N can that OREO STOCK FASTBOOT ROM be installed through Method 1?
Click to expand...
Click to collapse
1)If you flash the soak test OTA updates, you should be back on the official OTA update path. It seems that the final soak test build is often the same build released to retail, unifying both update paths again. Up until then, you have to manually flash all soak test OTA updates (unless you are an active soak tester on the MFN).
2)No, you must flash the fastboot ROM via fastboot (the bootloader mode), using the fastboot flashing commands. I'm not familiar with the G5S Plus flashing commands, but looking through this thread, here are the flashing commands through ADB (as usual, you need minimal ADB/fastboot and the Motorola drivers. If you have Windows 10 or 8.1, you may have to disable driver signature enforcement. Also, double-check how many system.img_sparsechunk images you have in the fastboot image):
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot oem reboot
Credit to: https://forum.xda-developers.com/moto-g5s-plus/how-to/xt1804-link-nps26-116-61-t3737476
If you wish to try to save your data, you can omit the fastboot erase userdata command. As your bootloader is already locked, you do not need the OEM lock commands.
Where did you found the link of that captured OTA?..
As per the Senior member information If you are able to get all the captured files of Future OTAs then you can install this now..through any of the method stated by the Senior member..
Me installed with adb sideload after install wiped data wipecache room very smooth
Nani dhfm said:
As per the Senior member information If you are able to get all the captured files of Future OTAs then you can install this now..through any of the method stated by the Senior member..
Click to expand...
Click to collapse
I found it in a whatsapp group
Can you give the link of that WhatsApp group...thanks
Saadatrm said:
I found it in a whatsapp group
Click to expand...
Click to collapse
Give me the link of that group..so that I can join that gropu.pls
---------- Post added at 04:47 AM ---------- Previous post was at 04:43 AM ----------
eoror24 said:
Me installed with adb sideload after install wiped data wipecache room very smooth
Click to expand...
Click to collapse
Can you add screenshots..pls
Saadatrm said:
I found it in a whatsapp group
Click to expand...
Click to collapse
This time you got it fine, but there's no guarantee you'll get all the soak test zips. So there's some hiccups might be there. Be cautious, official rollout is not far.
geekychandu said:
This time you got it fine, but there's no guarantee you'll get all the soak test zips. So there's some hiccups might be there. Be cautious, official rollout is not far.
Click to expand...
Click to collapse
Well, the official OTA may be in 1-2 months time, perhaps even longer depending on what bugs are encountered in the various soak tests. As you correctly pointed out though and I've mentioned it as well, all the soak test OTA updates must be flashed and in sequence if you're not on the MFN to get back to official OTA status. Alternatively you could flash the Oreo stock ROM (with the official build) if that gets leaked.
Okay, so in theory you could try the soak test and, if you don't like it or find too many bugs (you should expect bugs, this is a soak test!), you could downgrade by flashing stock Nougat (if you have an unlocked bootloader). Be warned that this downgrade will not usually downgrade your bootloader (flashing stock firmware does not usually downgrade your bootloader). You will likely still have the Oreo bootloader on a Nougat system, which may boot and work okay. If the next OTA update you apply is the Oreo update, then you may be okay and not hard brick. However, if you're still on the Oreo bootloader and you apply a Nougat OTA (e.g. if the June 2018 Nougat security patch arrives onto your device) you may hard brick your device. We've unfortunately seen many instances of this with the Z Play (when they downgraded from Oreo soak tests to their Dec 2017 stock Nougat ROM and attempted to flash the Feb 2018 Nougat security patch...). In other words, try to commit to the soak test OTA path or stay with the official OTA path, try to not mix between the 2, or avoid using OTA updates if you downgrade your stock firmware.
Have fun but please be responsible.
echo92 said:
Well, the official OTA may be in 1-2 months time, perhaps even longer depending on what bugs are encountered in the various soak tests. As you correctly pointed out though and I've mentioned it as well, all the soak test OTA updates must be flashed and in sequence if you're not on the MFN to get back to official OTA status. Alternatively you could flash the Oreo stock ROM (with the official build) if that gets leaked.
Okay, so in theory you could try the soak test and, if you don't like it or find too many bugs (you should expect bugs, this is a soak test!), you could downgrade by flashing stock Nougat (if you have an unlocked bootloader). Be warned that this downgrade will not usually downgrade your bootloader (flashing stock firmware does not usually downgrade your bootloader). You will likely still have the Oreo bootloader on a Nougat system, which may boot and work okay. If the next OTA update you apply is the Oreo update, then you may be okay and not hard brick. However, if you're still on the Oreo bootloader and you apply a Nougat OTA (e.g. if the June 2018 Nougat security patch arrives onto your device) you may hard brick your device. We've unfortunately seen many instances of this with the Z Play (when they downgraded from Oreo soak tests to their Dec 2017 stock Nougat ROM and attempted to flash the Feb 2018 Nougat security patch...). In other words, try to commit to the soak test OTA path or stay with the official OTA path, try to not mix between the 2, or avoid using OTA updates if you downgrade your stock firmware.
Have fun but please be responsible.
Click to expand...
Click to collapse
For eg: there are 3 soak test OTAs..nd next official Oreo OTA released..Iflashed the first soak test OTA..
Can I directly flash the official oreo OTA without flashing the remaining 2 soak test OTAs..
If it's possible..will I get official OTAs then onwards?(I mean security patches and all)
---------- Post added at 02:19 AM ---------- Previous post was at 02:13 AM ----------
Nani dhfm said:
For eg: there are 3 soak test OTAs..nd next official Oreo OTA released..Iflashed the first soak test OTA..
Can I directly flash the official oreo OTA without flashing the remaining 2 soak test OTAs..
If it's possible..will I get official OTAs then onwards?(I mean security patches and all)
Click to expand...
Click to collapse
And one last qstn..
If I flash all the 3 soak test OTAs as per the example..will I get official Oreo OTA update?..or I should flash it?..
Method 1 works...
Method 1 hinted by the Senior member in this thread works...
Downloaded the Ota file..
Move it to the main internal storage
Give storage permission to the MOTOROLA UPDATE SERVICES
Check for update in system
N it will show up..
Try it Guys..