Modified XT1095 OTA - X 2014 General

I took the OTA update zip from my phone and modified the updater-script to look for:
motorola/victara_tmo/victara:5.0/LXE22.46-11/11:user/release-keys
Click to expand...
Click to collapse
This should allow the OTA to be sideloaded if you used the Motorola 5.0 Lollipop factory image that they recently published.
DISCLAIMER:
This is untested by me. I have no idea if it will work. Be sure you can return to stock if you need to. DO NOT flash this if your bootloader is locked!
Still here? Then if you want to be a guinea pig, you must be on the factory image from lollipop and the fingerprint must be motorola/victara_tmo/victara:5.0/LXE22.46-11/11:user/release-keys.
Url removed. Motorola has fixed the 5.0 images. Download them again.

Honestly I'd rather not do this. The check is there for a reason.

alvareo said:
Honestly I'd rather not do this. The check is there for a reason.
Click to expand...
Click to collapse
True. But Motorola hasn't been too good with their checks already. The only part that concerns me would be the sbl update at the end of the script.

I think the official 5.0 image Motorola posted was put together in a rush or something. After I flashed it, the software status in the bootloader always showed: modified. When I didn't see the OTA popping up after checking for updates yesterday, I tried a logcat and it was spitting out errors about build fingerprint mismatch (that made sense), but also errors about root being present? I had not rooted after flashing the 5.0 image... The OTA was clearly available from Motorola's servers (I could see the download link and manually download it if I wanted). It was just determined to be incompatible, so the phone just kept saying software is up to date...
After flashing the previous 5.0 I had laying around, the software status showed as official in the bootloader as well.

Very good info. Sounds like they botched the build and now it's causing issues for everyone. I bet when they compiled the image they had something extra in the /system and that caused it to increment the build fingerprint and the status to show modified

Anyone get this to work? Comes up invalid file for me.

I don't think it will work. If I remember correctly otas need a signature, which only motorola has. Since it's a modified ota, the signature won't match.
Sent from my XT1095 using Tapatalk

Actually it will work. Chinese people had successfully modified ota of 5.0.2,he reduced BL's version and gpt's level. So if u flash that ,it would not update your BL version and also gpt level. because of this modified ota u can easily downgrade ~

colourfuldays said:
Actually it will work. Chinese people had successfully modified ota of 5.0.2,he reduced BL's version and gpt's level. So if u flash that ,it would not update your BL version and also gpt level. because of this modified ota u can easily downgrade ~
Click to expand...
Click to collapse
I just read up on it some more. We are both correct. Yes you can modify an ota file but if it is not signed by motorola it can only be used on an unlocked bootloader. Anyoneone that has a locked bootloader will not work.
Sent from my XT1095 using Tapatalk

colourfuldays said:
Actually it will work. Chinese people had successfully modified ota of 5.0.2,he reduced BL's version and gpt's level. So if u flash that ,it would not update your BL version and also gpt level. because of this modified ota u can easily downgrade ~
Click to expand...
Click to collapse
In the other 5.1 thread they posted IMG files for everything but bl and gpt. I fastbooted just the system and boot files and now am on 5.1 may try the modem files at some point but didnt see a need so far. One disclaimer in the same thread i gave explicit directions to another user who said it didnt work at all but he was not on a pure edition and had a different bl version.
So why post all this here.... to agree with the above that with the script correctly modified it should work perfectly.

Related

Android M 6.0.1 Official Stock Firmware and OTA for Z00A ZE551ML

IHere it is folks from Asus's support page. V2.20.40.168. 1.16 gig download. Instal how you'd like but beware there may or may not be a way to root yet. So take that into consideration when you sideload, update, or flash. I would imagine if your boot loader is unlocked it should be possible to fastboot the latest supersu.zip file to gain root. That's what I plan on doing.
I've taken a look at the OTA 's META-INF updater-script and it looks as if you'll need to be completely back to stock to be able to use the standard OTA method to update. It has the standard " abort if system has unexpected content" lines all the way through it.
Neither one of these has been altered, rooted, or modified in any way. These are straight stock 6.0.1 from ASUS.
http://www.asus.com/us/supportonly/ASUS ZenFone 2 (ZE551ML)/HelpDesk_Download/
Here's the META-INF updater-script
Sorry. I apologize to all. O think this is for the wrong device. It came from XDA's home page story and I downloaded via the link provided. Stay tuned ill figure it out.
Can anybody who flashes Marshmallow on its Zenfone 2 try out the game Ingress for a bit, just to see if it works/runs? Because CM13 has that problem that something broke the game and maybe Asus has finally released the particular framework in the official MM firmware which could be used to patch the bug in CM13.
Gesendet von meinem SGP611 mit Tapatalk
mattwheat said:
Here it is folks from Asus's support page. V2.20.40.168. 1.16 gig download. Instal how you'd like but beware there may or may not be a way to root yet. So take that into consideration when you sideload, update, or flash. I would imagine if your boot loader is unlocked it should be possible to fastboot the latest supersu.zip file to gain root. That's what I plan on doing.
I've taken a look at the OTA 's META-INF updater-script and it looks as if you'll need to be completely back to stock to be able to use the standard OTA method to update. It has the standard " abort if system has unexpected content" lines all the way through it.
Neither one of these has been altered, rooted, or modified in any way. These are straight stock 6.0.1 from ASUS.
http://www.asus.com/us/supportonly/ASUS ZenFone 2 (ZE551ML)/HelpDesk_Download/
If you want just the OTA (which is only 183 MB ) then here's a link to it. Again I don't know if you can keep root or if we have a way to root yet.
https://drive.google.com/file/d/0B2OabWtEBQcpYzhscXRqQUlfMjA/view?usp=docslist_api
Here's a screen shot of the META-INF updater-script showing the Android version and you can see all the "abort if system has unexpected content" lines through out.
Click to expand...
Click to collapse
V2.20.40.168 has been public for weeks, its 5.0 still. Thai was the last OTA they released.
Sent from my N5206 using Tapatalk
Nothing new here..
anyone installed this yet?
I apologize to all. This is not the M update. I jumped the gun due to a post I saw on XDA's home page.
After looking closely at the OTA file. I don't think that its even for our device. The model numbers in the updated-script file are wrong.
Again I apologize I got bad info on what should have been a trustable source on XDA and from their link this is the OTA that automatically downloaded.
Update for zenwatch
This isn't 6.0.1 at all
mattwheat said:
IHere it is folks from Asus's support page. V2.20.40.168. 1.16 gig download. Instal how you'd like but beware there may or may not be a way to root yet. So take that into consideration when you sideload, update, or flash. I would imagine if your boot loader is unlocked it should be possible to fastboot the latest supersu.zip file to gain root. That's what I plan on doing.
I've taken a look at the OTA 's META-INF updater-script and it looks as if you'll need to be completely back to stock to be able to use the standard OTA method to update. It has the standard " abort if system has unexpected content" lines all the way through it.
Neither one of these has been altered, rooted, or modified in any way. These are straight stock 6.0.1 from ASUS.
http://www.asus.com/us/supportonly/ASUS ZenFone 2 (ZE551ML)/HelpDesk_Download/
Click to expand...
Click to collapse
Please so some homework before posting and you should of reported your other thread, that I moved out of the Development sections: http://forum.xda-developers.com/zenfone2/general/z00a-ze551ml-6-0-1-marshmallow-stock-t3328626
Nevertheless, this Thread is Closed also...

XT-1644 Official Nougat Update?

My Phone Info:
Single sim 2gb ram + 16gb rom
Hello folks I've been searching for a nougat update for XT-1644, but unable to find over the xda if anyone of you havs upgraded your xt-1644 then kindly tell the procedure here, Thanks.
Here is my About Phone Info.
http://cloud.tapatalk.com/s/589c8f61b2eab/Screenshot_20170209-203359.png
http://cloud.tapatalk.com/s/589c8f48b01b2/Screenshot_20170209-203401.png
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
echo92 said:
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
Click to expand...
Click to collapse
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
waseemmayaa said:
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
Click to expand...
Click to collapse
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
echo92 said:
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
waseemmayaa said:
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
Click to expand...
Click to collapse
I see you've received a response in the other thread regarding if XT1644 will accept the update; given you've flashed TWRP, if you wish to be very safe, I would suggest re-installing your Marshmallow ROM so you have a stock install before proceeding to Nougat. There's nothing stopping you from directly flashing Nougat, and the fastboot method for either Nougat build may correctly overwrite the relevant files, the only way is to try the procedure. Don't use the TWRP backup images of Nougat - they don't contain updates to your baseband modem and other core parts of your device - they are only meant to be used once your entire phone is updated to Nougat.
If you wish to restore back to stock MM before flashing Nougat, here's links to stock firmware for XT1644: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980
But either way, read all the instructions first, ensure you've got all the firmware and tools you need installed/downloaded, your phone has at least 50 % battery and plenty of time, and you should be okay.

Trouble flashing STOCK recovery

I am able to flash stock firmware with fastboot, however recovery.img and boot.img always fail with "(bootloader) image signed with key bad key"... doesnt matter if its 139.48-49-64 or the nougat soak test. I have xt1625 US retail, i made sure im using the correct non-amazon US firmware...
It boots up and runs properly, and i can install twrp... however, im unable to install the OTA updates without stock recovery, so im stuck on NPJ25.93-11 instead of 14
anybody have any similar issue?
That error with the boot.img and recovery.img, if I recall, usually shows up - provided after the warning the log says they were flashed okay, then you shouldn't have any problems, as you've experienced.
Yup, you cannot install any OTA updates from Motorola once you've modified your system - you need to be on stock recovery and system. Unlocking your bootloader is okay, but modifying your recovery, kernel, or any other part of your system may stop the OTA from installing. Your possible options are to re-flash the 93-11 update and download the 93-14 OTA if it's available in your region, or fastboot one of the 93-14 ROMs in the Guides section (e.g. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369)
ourangashane said:
I am able to flash stock firmware with fastboot, however recovery.img and boot.img always fail with "(bootloader) image signed with key bad key"... doesnt matter if its 139.48-49-64 or the nougat soak test. I have xt1625 US retail, i made sure im using the correct non-amazon US firmware...
It boots up and runs properly, and i can install twrp... however, im unable to install the OTA updates without stock recovery, so im stuck on NPJ25.93-11 instead of 14
anybody have any similar issue?
Click to expand...
Click to collapse
When and how did you get the Nougat update for the XT1625? I am on stock and have not received it, nor have I seen any update from Motorola available for it.
pastorbob62 said:
When and how did you get the Nougat update for the XT1625? I am on stock and have not received it, nor have I seen any update from Motorola available for it.
Click to expand...
Click to collapse
Likely fastboot'ed one of the Nougat images in the Guides section; I've not seen any mentions of OTA updates in the US either - Canada and Brazil appear to have received it thus far, hopefully the US isn't far behind!
echo92 said:
Likely fastboot'ed one of the Nougat images in the Guides section; I've not seen any mentions of OTA updates in the US either - Canada and Brazil appear to have received it thus far, hopefully the US isn't far behind!
Click to expand...
Click to collapse
That would be my guess as well. I don't get why some are so impatient to get Nougat that they risk flashing firmware not intended for their devices. Then they wonder why they are having issues. Oh well!
pastorbob62 said:
When and how did you get the Nougat update for the XT1625? I am on stock and have not received it, nor have I seen any update from Motorola available for it.
Click to expand...
Click to collapse
No, no update yet.... i just flashed the indian version from the forum..
echo92 said:
That error with the boot.img and recovery.img, if I recall, usually shows up - provided after the warning the log says they were flashed okay, then you shouldn't have any problems, as you've experienced.
Yup, you cannot install any OTA updates from Motorola once you've modified your system - you need to be on stock recovery and system. Unlocking your bootloader is okay, but modifying your recovery, kernel, or any other part of your system may stop the OTA from installing. Your possible options are to re-flash the 93-11 update and download the 93-14 OTA if it's available in your region, or fastboot one of the 93-14 ROMs in the Guides section (e.g. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369)
Click to expand...
Click to collapse
Had i just used my eyes lol... Id been looking for a fastboot 93-14, i must have been way too tired lol.. thank you

Which stock firmware should I use for an XT1687?

I see over a dozen different versions here but I'm not sure which one to download:
https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
I've already tried two different ones but I receive no cell signal when it boots.
Any ideas?
Thanks!
I actually found the answer on my own: none of them. Wrestling with the G5 this morning made me lose my mind. I ended up with the Pixel ROM.
Does anyone have a copy of the XT1687 stock rom (carrier unlocked ... I bought mine at Costco)? I could really use it.
My phone is totally messed up. My /system is empty except for 'bin'....
Thank you for any help!
I have used this one: POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I was on this version for a while, rooted, and I had to use this firmware to reflash back to stock in order to take the OTA successfully (the OTA is NPNS25.137-93-4, which is the latest as of this writing).
I basically flashed everything from the flashfile.xml
dunderball said:
I have used this one: POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I was on this version for a while, rooted, and I had to use this firmware to reflash back to stock in order to take the OTA successfully (the OTA is NPNS25.137-93-4, which is the latest as of this writing).
I basically flashed everything from the flashfile.xml
Click to expand...
Click to collapse
did going back to stock and accepting the OTA work for you??!
roydhritiman said:
did going back to stock and accepting the OTA work for you??!
Click to expand...
Click to collapse
I ended up with some kind of error with the OEM partition, but in the end all of the details on my settings screen show that I'm on the latest security patch, kernel, etc.
dunderball said:
I have used this one: POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
What does this version of the firmware say for (in the About settings) Software Channel? Android Version? Or rather, I guess what does it say now that you think it took the OTA successfully?
dunderball said:
I was on this version for a while, rooted, and I had to use this firmware to reflash back to stock in order to take the OTA successfully (the OTA is NPNS25.137-93-4, which is the latest as of this writing).
I basically flashed everything from the flashfile.xml
Click to expand...
Click to collapse
The OTA that are downloaded into /cache are named something like Blur_* right? Do you know if those OTA contains the full image or is it just patches to various parts of the system?
dlong said:
The OTA that are downloaded into /cache are named something like Blur_* right? Do you know if those OTA contains the full image or is it just patches to various parts of the system?
Click to expand...
Click to collapse
Patches, a full ROM is rarely sent as an OTA. You'll know it's a full ROM if the size of the OTA is greater than 1GB. Anything less than say 300-400MB is patches to the system
dlong said:
What does this version of the firmware say for (in the About settings) Software Channel? Android Version? Or rather, I guess what does it say now that you think it took the OTA successfully?
The OTA that are downloaded into /cache are named something like Blur_* right? Do you know if those OTA contains the full image or is it just patches to various parts of the system?
Click to expand...
Click to collapse
I went from version 83 to successful OTA 92 (November patch), then to 93 January patch (but ended up with a failure message after booting up for whatever reason). I'm on retus, baseband M8953_37.46.07.47R POTTER_NA_CUST, build number NPNS25.137-93-4.
As far as I see, I don't see any full stock firmware out for NPNS25.137-93-4 which is unfortunate. I have a feeling my update to Oreo will fail if it ever comes out. I'm not even sure why my OTA fails, as I do my best to avoid modifying any partitions and mostly use systemless modules through Magisk. Whatever though.
No joy. So apparently, since I'm on NPN25.137-92 (POTTER_RETAIL_7.0_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), I wasn't able to downgrade to (POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip).
I did re-flash everything and the results seems to be the same (unable to 'see' new updates). I am on November 2017 patch but when I check for upgrades, it states the system is up to date.
I hope that because my phone is 'unlocked from store (Costco - USA)' that RETAIL is the correct firmware. Anyone know for sure?
Also... I guess I wiped recovery when I installed TWRP. Is there an OEM recovery.img available for Moto 5G Plus?
Edit: So the whole reason, I originally rooted my phone was so that I can enable Hot Spot by adding net.tethering.noprovisioning=true to /system/build.prop (now I wonder if root is even required to do that?)

Final Official Oreo 8.1.0 Release - OPP28.85-16 OTA

I've just captured the Official OPP28.85-16 OTA for retail cedric and I'm posting it here. I'm on retbr channel but this will work on any retail device. If you're on another updated channel, I don't know what would happen if you installed this.
Notice that to install this YOU MUST be on NPPS25.137-93-2-5 to install these, since OTA's are not full firmwares like fastboot files, but instead they're patchings tailored to be applied upon a specific firmare - NPPS25.137-93-2-5 in this case.
Another particular detail is that the OTA file (gotten directly from my credric) lists the Blur Version as Blur_Version.25.361.10.cedric.retail.en.US, but curiously, the fastboot version for the same firmware ( which you can download here) lists it as Blur_Version.28.41.15.cedric.retail.en.US
Someone also reported in another thread that they just sideloaded this upon the Second Soak test. I wouldn't doubt it since this is what should happen to regular soak testers, but if you do it, DO IT AT YOUR OWN RISK
I also won't post instructions on how to install this since they're already available here
Download
Gdrive: https://drive.google.com/file/d/149hrGFpuWUgAvJr02McYNwJVaqSvllYO/view?usp=sharing
That's it.
changelog?
Has anyone already tried it?
Since this is a (Delta) OTA Update that expects NPPS25.137-93-2-5 (Blur_Version.25.361.10) it should be correctly named "block_delta-ota-Blur_Version.25.361.10-28.41.15.cedric.retail.en.US" in my view.
Someone also reported in another thread that they just sideloaded this upon the Second Soak test.
Click to expand...
Click to collapse
I'm on the 2nd soak test update OPP28.85-13.
Just tried to flash the update from SD card and ADB sideload.
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
JoeDoe0 said:
Since this is a (Delta) OTA Update that expects NPPS25.137-93-2-5 (Blur_Version.25.361.10) it should be correctly named "block_delta-ota-Blur_Version.25.361.10-28.41.15.cedric.retail.en.US" in my view.
I'm on the 2nd soak test update OPP28.85-13.
Just tried to flash the update from SD card and ADB sideload.
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
Click to expand...
Click to collapse
seems like it can be updated. from. soak test then, but I never heard nor did I find anything about OPP25. 85-16 build. maybe there was a third soak test and we don't know about it
Works perfect
Hi,
i used the above Image in Germany and i am now on Oreo 8.1
Everything works perfect. First i had a little bit trouble due to an old Version of ADB Tools, but after Update ADB to current Version the Update to Oreo took something around 30min.
Build 28.85-16
Oreo 8.1
Software Channel reteu
Patch Level 01.08.2018
bori321 said:
Hi,
i used the above Image in Germany and i am now on Oreo 8.1
Everything works perfect. First i had a little bit trouble due to an old Version of ADB Tools, but after Update ADB to current Version the Update to Oreo took something around 30min.
Build 28.85-16
Oreo 8.1
Software Channel reteu
Patch Level 01.08.2018
Click to expand...
Click to collapse
On which version you were before update?
Firmware
Hi,
before update to Oreo i flashed NPPS25.137-93-2-5 Firmware and after that the Image from this thread.
Worked perfect.
Alex
I tried to post a Screenshot but it was not possible because i am a new member...
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
Click to expand...
Click to collapse
freeZbies said:
seems like it can be updated. from. soak test then, but I never heard nor did I find anything about OPP25. 85-16 build. maybe there was a third soak test and we don't know about it
Click to expand...
Click to collapse
Update fails from OPP28.85-13 since it expects either OPP28.85-16 which is the latest Oreo build (that I want to update to) or the latest Nougat NPPS25.137-93-2-5.
There is no OPP25. 85-16 build! I think you misread the error message.
BTW I updated from OPP28.85-13 to -16 using the full fastboot version and it worked out perfectly.
JoeDoe0 said:
Update fails from OPP28.85-13 since it expects either OPP28.85-16 which is the latest Oreo build (that I want to update to) or the latest Nougat NPPS25.137-93-2-5.
There is no OPP25. 85-16 build! I think you misread the error message.
BTW I updated from OPP28.85-13 to -16 using the full fastboot version and it worked out perfectly.
Click to expand...
Click to collapse
yeah, I actually misread it, now I see it.
Anyways, flashing it from fastboot doesn't prove anything. but seems like Cedric can be upgraded from the soak test to final version using this ota. Idk because I used fastboot myself too, since I had already modified my system partition.
AsusZenFone3Deluxe said:
changelog?
Click to expand...
Click to collapse
seriously?
stop joking, Motorola doesn't release changelogs.
but I'll try:
updated from nougat to oreo?
duhhh
how is speaker quality in this build ?
because there is some issues in previous oreo builds
Speaker
Hi,
i would say that for my ears the speaker sounds better than it was with Nougat.
After a few days of testing everything works really good and i have not found anything not working or any problems.
Alex
bori321 said:
Hi,
before update to Oreo i flashed NPPS25.137-93-2-5 Firmware and after that the Image from this thread.
Worked perfect.
Alex
I tried to post a Screenshot but it was not possible because i am a new member...
Click to expand...
Click to collapse
how do you get back to NPPS25.137-93-2-5
I followed the steps from this Thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
- Unlocked bootloader (don't know of this is necessary)
- back to NPPS25.137-93-2-5 via the commands from the thread i linked (without the lines:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
)
- via ADB sideload with the Oreo download from this thread to Oreo.
Alex
ahmedAZ said:
how is speaker quality in this build ?
because there is some issues in previous oreo builds
Click to expand...
Click to collapse
In my experience the quality is better than on previous oreo builds.
ahmedAZ said:
how do you get back to NPPS25.137-93-2-5
Click to expand...
Click to collapse
if you have an unlocked bootloader download NPPS25.137-93-2-5 Flashable Zip here and flash it with twrp
bori321 said:
I followed the steps from this Thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
- Unlocked bootloader (don't know of this is necessary)
Alex
Click to expand...
Click to collapse
to flash official Motorola files there's no need to unlock the bootloader.
you've just unnecessarily voided your warranty
@freeZbies
Hey is that twrp stock rom (137-93-2-5) the only thing we need to flash before going for the ota ? Cause I've been told that we needed to be on a completely unmodified system partition in order to receive the ota. In that case just flashing twrp stock wouldn't be sufficient right?
https://forum.xda-developers.com/g5...o-official-stock-oreo-8-t3823598/post77713117
Chekm8Qc said:
@freeZbies
Hey is that twrp stock rom (137-93-2-5) the only thing we need to flash before going for the ota ? Cause I've been told that we needed to be on a completely unmodified system partition in order to receive the ota. In that case just flashing twrp stock wouldn't be sufficient right?
https://forum.xda-developers.com/g5...o-official-stock-oreo-8-t3823598/post77713117
Click to expand...
Click to collapse
I dont know if the twrp version would be valid. To apply an OTA, your system must matchbit by bit, so the most guaranteed way is to flash that firmware via fastboot, but you could try flashing the twrp version, and in case it works, you could post the results here.
just dont forget that if the ota fails youll soft brick ur phonr and will only be able to recover it via fastboot
freeZbies said:
I dont know if the twrp version would be valid. To apply an OTA, your system must match stick bit by bit, so the most guaranteed way is to flash that firmware via fastboot, but. you could try flashing the twrp version, and in case it. woeks you could post the results here.
just dont forget that if the ota fails youll soft brick ur phonr and will only be able to recover it via fastboot
Click to expand...
Click to collapse
Thanks I'll keep that in mind
Being soft bricked,, wouldn't I be able to use twrp still? Like to flash a valid rom or one of my backups?
Anyways I can't really try it that way since the update hasn't come to me yet I'm on software channel Retca.
Edit : right I forgot that I could just use the official ota available here if I would like to test it.
Chekm8Qc said:
Thanks I'll keep that in mind
Being soft bricked,, wouldn't I be able to use twrp still? Like to flash a valid rom or one of my backups?
Anyways I can't really try it that way since the update hasn't come to me yet I'm on software channel Retca.
Edit : right I forgot that I could just use the official ota available here if I would like to test it.
Click to expand...
Click to collapse
being soft bricked doesnt necessarily mean you can recover it through twrp. OTA's are different of twrp flashables in that it modifies things beyond system partition. I've seen reports from people with other motorola devices who applied an OTA while having a modified system partition, and even though they were able to boot to twrp, flashing a custom Rom or restore a backup wouldn't make the phone boot. Their phones weren't hard bricked, but still they had to fastboot to recover their phones. Anyways, why don't you flash the Twrp flashable if, it's already available (considering you have an unlocked bootloader).
I'm case you have a locked bootloader you may fastboot without executing "fastboot erase userdata" in case you want to try. I did it without losing my data (although I was already in Opp 28.85-16)
but after all I really advice you to flash the twrp zip if u can

Categories

Resources