Related
Follow at your own risk. Unlocked bootloader required.
This is how I was able to fix my softbrick after updating to -64 on my US XT1625 Amazon G4. Credit goes to Android Doctor (his YouTube tutorial), I changed his fastboot commands a little though to better match how a real Moto upgade would act (based off of the flashfile.xml file in the firmware zip).
From here download "XT1625_ATHENE_AMAZON_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" (Here's a direct link if it works for you).
Extract that zip to a folder and copy ADB/fastboot files to that folder. Navigate or open a command prompt window to that directory. Boot your phone into fastboot (power it off and power it back on holding the volume down key or just run "adb reboot bootloader" if you're in recovery). Run the following commands from the command prompt window when your phone is in the bootloader and your command prompt window is navigated to the folder you extracted XT1625_ATHENE_AMAZON...zip to (you can also copy and paste them all into command prompt):
Running the below commands unmodified will wipe your data. You can try to run them without the "fastboot erase userdata" command at the bottom to possibly save your data (I can't guarantee anything).
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_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
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 system system.img_sparsechunk.7
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 erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Again, I give no guarantees on this and probably won't be checking back on this thread for replying or updating. Also note, Amazon ads will return to your lock screen.
beano311 said:
Follow at your own risk.
This is how I was able to fix my softbrick after updating to -64 on my US XT1625 Amazon G4. Credit goes to Android Doctor (his YouTube tutorial), I changed his fastboot commands a little though to better match how a real Moto upgade would act (based off of the flashfile.xml file in the firmware zip.
From here download "XT1625_ATHENE_AMAZON_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" (Here's a direct link if it works for you).
Extract that zip to a folder and copy ADB/fastboot files to that folder. Navigate or open a command prompt window to that directory. Boot your phone into fastboot (power it off and power it back on holding the volume down key or just run "adb reboot bootloader" if you're in recovery). Run the following commands from the command prompt window when your phone is in the bootloader and your command prompt window is navigated to the folder you extracted XT1625_ATHENE_AMAZON...zip to (you can also copy and paste them all into command prompt):
Running the below commands unmodified will wipe your data. You can try to run them without the "fastboot erase userdata" command at the bottom to possibly save your data (I can't guarantee anything).
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_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
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 system system.img_sparsechunk.7
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 erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Again, I give no guarantees on this and probably won't be checking back on this thread for replying or updating. Also note, Amazon ads will return to your lock screen.
Click to expand...
Click to collapse
Will this work on a locked bootloader?
Mathracer1 said:
Will this work on a locked bootloader?
Click to expand...
Click to collapse
I think not. Check out the youtube link I posted. The first thing you see in the video description is "UNLOCKED BOOTLOADER REQUIRED BEFORE DOING THIS THIS,UNLOCKED BOOTLOADER RQUIRED BEFORE DOING THIS, UNLCOKED BOOTLOADER REQUIRED BEFORE DOING THIS". I'll update the main post to reflect this.
I tried this with a unlocked bootloader and it worked.
I then locked the bootloader at the last step. However, the software status still shows "modified". How do I make it official?
SemiConductor said:
I tried this with a unlocked bootloader and it worked.
I then locked the bootloader at the last step. However, the software status still shows "modified". How do I make it official?
Click to expand...
Click to collapse
I don't think there is a way of relock. Well, whatever you do and whatever you see on the screen or your PC says it has been locked again, the hardware counter tells the bootloader has been unlocked once. I read this from somewhere else on the internet. Correct me if it is wrong.
beano311 said:
I think not. Check out the youtube link I posted. The first thing you see in the video description is "UNLOCKED BOOTLOADER REQUIRED BEFORE DOING THIS THIS,UNLOCKED BOOTLOADER RQUIRED BEFORE DOING THIS, UNLCOKED BOOTLOADER REQUIRED BEFORE DOING THIS". I'll update the main post to reflect this.
Click to expand...
Click to collapse
Yes! its able to flash whith Locked Bootloader, but only flash oem, system, recovery, non-hlos, cache, userdata, flash boot, bootloader,gpt, always because a locked bootloader
Lussardi said:
Yes! its able to flash whith Locked Bootloader, but only flash oem, system, recovery, non-hlos, cache, userdata, flash boot, bootloader,gpt, always because a locked bootloader
Click to expand...
Click to collapse
Please could you specify better that I should install, I am desperate :llorando:
stephydth said:
Please could you specify better that I should install, I am desperate :llorando:
Click to expand...
Click to collapse
Code:
only flash oem, system, recovery, non-hlos, cache, userdata, boot, bootloader
download firmware zip extract and flash above mentioned
I have a Moto G4 (XT1625) Unlocked with 32GB of storage. Bootloader Unlocked and TWRP Bootloader or Recovery, IDK how to word it, but I attempt to update from Android 6.0.1 to Android 7 and the update fails. When the device reboots it reboots into the TWRP Recovery Menu. How do I proceed. Please help.
Haven't used adb, drivers, or anything and cannot seem to remember the process. Any pointers in the right direction are appreciated. Thank you.
Update 1: I am able to boot into TWRP 3.0.2-0 and see files on my MicroSD. However I downloaded a .ZIP file that was suppose to be the Nougat factory image and when I went to flash it, it says "Installing zip file.... could not find 'META-INF/COM/GOOGLE/ANDROID/UPDATE-BINARY' in the zip file. Error installing zip file."
Update 2: Can someone confirm that I would need to first somehow remove TWRP in order to update? How do I remove TWRP and get phone back to FULL STOCK.
Okay, accepting OTA updates requires a stock recovery (as you've discovered), stock kernel and unmodified system. Furthermore, the stock Nougat zip that you've downloaded needs to be extracted on your computer and flashed via fastboot, it's not flashable in TWRP.
If you're wanting to update and update to the latest Nougat build (which for US devices - XT1625 and XT1644 - appears to be NPJ25.93-14.5, June 2017), the easiest way is to download the stock Nougat ROM from here: https://www.androidfilehost.com/?fid=673368273298984458 . Download to your computer and extract the files. This build is for retail US (non-Amazon devices), with a retus software channel as listed in Settings>About Phone.
Then follow the instructions here, but using the above NPJ25.93-14.5 stock ROM instead. https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Beware that this process may erase your data in the process, so back up as necessary. If you do not wish to erase your data, then you can use the following fastboot commands instead of the commands in the guide. Back up anyway and you may have to factory reset (thus losing your data) if your device is not stable. Also, either process will remove TWRP, root and any other modifications. Xposed is still not officially released for Nougat. It is up to you if you choose to re-lock your bootloader or not (of course, re-locking the bootloader will prevent you from flashing TWRP/root/any other modifications).
Code:
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 system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
pause
One word of warning, once you have formally updated to June 2017 (B1:06 bootloader), do not attempt to downgrade and accept OTA updates. You may wish to downgrade, but I don't recommend it - if you forget to not accept OTA updates, you may hard brick your device. If you think you'll forget, do not downgrade.
Hello.
I had serial rom with all updates (non-touched nougat 7.1.1 europe). The phone became slow and laggy. Had a dream to restore lollipop to go back to geatest time of the moto x play.
Unlocked bootloader with motoroloa website and code sent on email. Installed recovery twrp 3.2.1-r1.
Roms tried:
Lollipop zips
LPH_v1.1_DS_by_Eska
LPH_v1.0_DS_by_Eska
Marshmallow zips
24.107-70-1_Debloated-lux_2.0.0 (Stock Debloated VoLTE)
SpetrumMM_VoLTE-lux_5.6.0
Nougat zips
DOT-N-v1.2-20180219-lux-OFFICIAL ( [OFFICIAL][LUX][7.1.2][V-1.2]DOT-OS [Smoothest OS] by Sharan
and finally one, that worked: PIXEL+DARK+OS+V11
and second: [ROM][7.1.2][lux][OMS] ViperOS v3.1.1
What is the reason I can't install any rom beside 2 last of them?
Process with not working roms looks similar. After wiping, installing and reboot, only boot logo image changed and sometimes showed second animated logo with no further results (even if waited many minutes )
Are you using the "stock" gapps? They take a long time to boot. Try using pico, and if not, you can revert to an earlier version by flashing each file through fastboot.
Also, the stock-based roms already have gapps. There is no need to install gapps and it may cause issues.
First, extract your stock rom zip.
(This should work for any stock rom, and will not brick your phone unless you make a mistake. However, as always, I take no reliability for your broken phone)
1. Extract stock rom
2. Reboot phone into download mode/bootloader/fastboot mode.
3. Type these commands:
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 system system.img_sparsechunk.((((number)))) <-- FOR EVERY FILE LIKE THIS WITH THE NUMBER AFTER IT!!!!!
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
Then reboot.
Someone managed to get the RSD Secure link for the FASTBOOT files of the final Oreo 8.1 release for RETAIL Moto G5/cedric.
With these files you'll be able to update to official oreo, relock your bootloader or simply go back to stock.
Using the guide I'll write below you'll be able to flash it from Linux, Windows and MacOS.
The new firmware is named OPP28.85-16 and Blur Version listed within the firmware package is:
Code:
Blur_Version.28.41.15.cedric.retail.en.US
whereas the OTA file for the corresponding Firmware lists it as:
Code:
Blur_Version.25.361.10.cedric.retail.en.US
I dont know which is "correct", but anyways, this should not alter your results when flashing this with fastboot.
DOWNLOAD
Gdrive: https://drive.google.com/file/d/1gNB7vNM8xH5ueTPKh5Qwev87gJpSpyyK/view?usp=sharing
RSD Secure: https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
FLASHING IT
If your seeing this post long after Setember 2018 it may be the case you have updated your firmware past this one and got a different bootloader version, in that case, make sure to check you bootloader version is BELOW B8.31. Flashing bootloader of equal or minor version will hardbrick your device
UPDATING FROM PREVIOUS ANDROID VERSION
1. If you're on Windows/Mac, download motorola USB drivers here. (You shouldn't need these on Linux)
2. Download Android Platform Tools (ADB & Fastboot ) for Windows/Mac/ Linux here (if you're on Linux, get these from your distro's repo instead).
3. Extract the platform tools somewhere
4. Extract the firmware's ZIP too (I recommend extracting it to the same directory as platform tools, this will make your life easier).
5.Open a command prompt/terminal where you extracted platform tools (To do that on windows, Hold SHIFT + right Click some blank area within platform-tools directory, then click "Open Command Prompt Here".
6. Reboot into fastboot (power off and connect USB while holding Vol Down) and Execute the following commands
Code:
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 system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
7. Reboot your phone by typing fastboot reboot or by selecting the "START" option in phone's screen and then pressing the power button
PS: Do not execute commands related to erasing the modemst1 and modemst2 partitions. This has been related to people losing their IMEI's.
RELOCKING YOUR BOOTLOADER
edit
Seems like my instructions on how to relock didn't work, but I want to thank Andrej_SK, who managed to do it and posted instructions on how to do it. Just remember that you should Not flash bootloader if you're already on B8.31 or past it. Flashing gpt.bin can also hardbrick your phone and there have been reports of it happening here on XDA and on telegram. I personally didn't flash it when moving from NPPS25.137-93-2-5 and had no problem at all, and I think you shouldn't too, unless you know you absolutely need it (which I think is unlikely, since the partition scheme looks the same on both nougat and Oreo)
Andrej_SK said:
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
Try this (on your own risk only): input "fastboot oem lock" twice (first time for starting the whole process of locking, second time for confirmation). Then, execute commands below, one by one
Code:
fastboot flash oem oem.img
fastboot flash boot boot.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 system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
Then, input "fastboot oem lock" for the last time. Your phone should immediately reboot, as mine did. If there will be problem with booting into OS, just reflash the whole system with commands below:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img (do not flash this if you're on B8.31 or further, so as not to hardbrick the device)
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 system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
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 reboot
Click to expand...
Click to collapse
DOWNGRADING FROM A FIRMWARE NEWER THAN OPP28.85-16
1. Follow steps one 1 up to five described in the first section UPDATING FROM PREVIOUS ANDROID VERSION
2. Omit these lines from step 6:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Notice that omitting these two lines is VERY IMPORTANT if you're downgrading, otherwise you'll hardbrick your device.
3.7. Reboot your phone by typing fastboot reboot or by selecting the "START" option in phone's screen and then pressing the power button
That's it. If you liked, press thanks
Ps: some of my friends have reported phone is rebooting right after flashing sparsechunk.5.
phone will apparently boot normally and show the setup wizard screen, but in actuality there will be missing files on the system partition.
in that case, reboot into fastboot and finish flashing the system normally, then boot your phone
Thank you very much! Excuse me if I'm wrong but with this file it's safe to install Oreo from stock Nuggat right? I just need to unlock the bootloader and flash normally?
Thank, you to provide the firmware.
On another thread (https://forum.xda-developers.com/g5...eo-8-1-0-release-opp28-t3849273/post77771786) you wrote it's necessary to be on firmware NPPS25.137-93-2-5. Maybe you forgot to mention that!?
I believe the two threads are separate updates. One being OTA and this thread being fastboot firmware. I was wondering if this would work on my Moto g5 xt1670 (137-93-8)?
Woooow
Thanks
Ahasverus said:
Thank you very much! Excuse me if I'm wrong but with this file it's safe to install Oreo from stock Nuggat right? I just need to unlock the bootloader and flash normally?
Click to expand...
Click to collapse
no need to unlock BL to flash this. If you're on stock Nougat just make sure you're on NPPS25.137-93-2-5 (July security patch), then grab the ota here and sideload or flash it using the stock recovery
if you're not on NPPS25.137-93-2-5 then you'll need to flash it before flashing the ota.
AndroidenKalle said:
Thank, you to provide the firmware.
On another thread (https://forum.xda-developers.com/g5...eo-8-1-0-release-opp28-t3849273/post77771786) you wrote it's necessary to be on firmware NPPS25.137-93-2-5. Maybe you forgot to mention that!?
Click to expand...
Click to collapse
if you're going to install it from fastboot there's no need to be on NPPS25.137-93-2-5
TWRP v3.2.3.0 for Cedric: works
Magisk v17.1: works (don't use safetynet)
Thank you very much for this! I've been using the soak Oreo and could not be happier until this thread, time for the final Oreo for my beloved G5.
Blur_Version.28.41.15 for OPP28.85-16 is correct!
I'm on the 2nd soak test update OPP28.85-13 and tried the OTA update from your other post. This failed due to wrong version (E3002) since it expects the last NPPS25.137-93-2-5 version.
How can I update from OPP28.85-13 to the latest OPP28.85-16 via fastboot flash without losing my current data and settings?
Can I flash without "erase userdata"?
The thing I don't like in your instructions is lack of DDR errase command.
Please explain your point. Also please compare with flashfile.xml from Oreo firmware.
PsyClip-R said:
The thing I don't like in your instructions is lack of DDR errase command.
Please explain your point. Also please compare with flashfile.xml from Oreo firmware.
Click to expand...
Click to collapse
So "fastboot erase ddr" command should be included while flashing stock Oreo through fastboot? What does that command do?
I am on amzin software channel and my build number is NPPS25.137-93-14 (July Security Patch). Will this fastboot method work for me?
Hello,
the bootloader locking seems not to be working. At the last "fastboot oem lock" it says that it needs a signed boot.img. Has anyone else experienced this issue ?
achintyakv said:
I am on amzin software channel and my build number is NPPS25.137-93-14 (July Security Patch). Will this fastboot method work for me?
Click to expand...
Click to collapse
I don't think so since this is definitely a retail version.
BUILD REQUEST INFO:
SW Version: cedric-user 8.1.0 OPP28.85-16 0400 release-keysM8937_22.29.02.70R
MBM Version: B8.31
Modem Version: M8937_22.29.02.70R
FSG Version: FSG-8937-02.65.33
Build Fingerprint: motorola/cedric/cedric:8.1.0/OPP28.85-16/0400:user/release-keys
CQATest App Version: 6.0.6
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 28.41.15.cedric.retail.en.US
Model Number: Moto G (5)
Android Version: 8.1.0
Baseband Version: M8937_22.29.02.70R
Build Id: OPP28.85-16
SW Display Build ID: OPP28.85-16
Build Date: Wed Sep 5 09:46:09 CDT 2018
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.28.41.15.cedric.retail.en.US
Version when read from CPV: cedric-user 8.1.0 OPP28.85-16 0400 release-keys
slsmaster said:
Hello,
the bootloader locking seems not to be working. At the last "fastboot oem lock" it says that it needs a signed boot.img. Has anyone else experienced this issue ?
Click to expand...
Click to collapse
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
Try this (on your own risk only): input "fastboot oem lock" twice (first time for starting the whole process of locking, second time for confirmation). Then, execute commands below, one by one
Code:
fastboot flash oem oem.img
fastboot flash boot boot.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 system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
Then, input "fastboot oem lock" for the last time. Your phone should immediately reboot, as mine did. If there will be problem with booting into OS, just reflash the whole system with commands below:
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 system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
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 reboot
Edit: as you can see at the screenshots in the attachment, I'm able to lock bootloader with this firmware. First, I reflashed the whole Oreo firmware, then rebooted into bootloader using "fastboot reboot-bootloader" command and at last I tried to relock bootloader which was (once again) successful.
Phone specs: XT1676 (3/16), DualSIM, reteu soft. channel
Andrej_SK said:
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
......
......
Click to expand...
Click to collapse
Thank you very much, worked like a charm.
need cedric amzin oreo update before was on soak oreo ,after upate this phone stay in fastboot mode
PsyClip-R said:
The thing I don't like in your instructions is lack of DDR errase command.
Please explain your point. Also please compare with flashfile.xml from Oreo firmware.
Click to expand...
Click to collapse
never heard about this command before, I have never used it ever and I flashed this firmware without any problem so far
Andrej_SK said:
So "fastboot erase ddr" command should be included while flashing stock Oreo through fastboot? What does that command do?
Click to expand...
Click to collapse
As I said above, I and other people I know who flashed this didn't have any problem by flashing without typing "fastboot erase DDR" and in fact I'm curious to know what does this command do.
JoeDoe0 said:
Blur_Version.28.41.15 for OPP28.85-16 is correct!
I'm on the 2nd soak test update OPP28.85-13 and tried the OTA update from your other post. This failed due to wrong version (E3002) since it expects the last NPPS25.137-93-2-5 version.
How can I update from OPP28.85-13 to the latest OPP28.85-16 via fastboot flash without losing my current data and settings?
Can I flash without "erase userdata"?
Click to expand...
Click to collapse
I think it's very unlikely anyone has this OPP25.85-16, otherwise it would've already surfaced somewhere.
(edit)
seems like I was wrong, I just reflashed the firmware and managed to keep my data by not using fastboot erase user data.
(/edit)
regarding the "fastboot erase user data" it doesn't matter if you use it or not, since once you flash all sparse chunks you'll lose your data partition anyways.
what I'd suggest you to do is
1.backup your data partition using twrp and your internal storage to a pc/sdcard/whatever (twrp doesn't backup your internal storage)
2. flash the firmware just as described on the main thread
3 fastboot boot twrp.img PRIOR to the first boot
4. restore your data
5. connect your phone to USB cable with twrp still open and copy back your internal storage through TWRP's MTP(or use twrp's file manager/aroma FM in case you backed internal storage to sd card)
5. boot your phone.
I never tried backing up internal storage but I already did this when fastbooting and managed to keep my data (settings, apps, etc) .
I just advice you to remove any screen lock prior to backing up your data since your previous pattern/pin/password generally won't work after restoring a twrp backup, but in case you forget it use twrp and go to /data/system and delete locksettings.db and your
lock screen protection will be gone
achintyakv said:
I am on amzin software channel and my build number is NPPS25.137-93-14 (July Security Patch). Will this fastboot method work for me?
Click to expand...
Click to collapse
I don't know, this could brick your phone, but I'm not sure
tapan8914 said:
need cedric amzin oreo update before was on soak oreo ,after upate this phone stay in fastboot mode
Click to expand...
Click to collapse
as I said idk what'd happen if someone did this. the best you can do now is to find some old amzin firmware and fastboot it (do not flash gpt.bin or bootloader.bin, so as not to hard brick your device)
Andrej_SK said:
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
Try this (on your own risk only): input "fastboot oem lock" twice (first time for starting the whole process of locking, second time for confirmation). Then, execute commands below, one by one
Code:
fastboot flash oem oem.img
fastboot flash boot boot.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 system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
Then, input "fastboot oem lock" for the last time. Your phone should immediately reboot, as mine did. If there will be problem with booting into OS, just reflash the whole system with commands below:
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 system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
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 reboot
Edit: as you can see at the screenshots in the attachment, I'm able to lock bootloader with this firmware. First, I reflashed the whole Oreo firmware, then rebooted into bootloader using "fastboot reboot-bootloader" command and at last I tried to relock bootloader which was (once again) successful.
Phone specs: XT1676 (3/16), DualSIM, reteu soft. channel
Click to expand...
Click to collapse
many a thanks, I'll put this on the main thread
Currently on OPP28.85-3
Currect me if I'm wrong, but by what I have been reading,
I cant go from OPP28.85-3 to OPP28.85-16
What I've read, I can't be on bootloader B8.31 (which I am) and since this isn't a "full system" image, just a "patch" for official Nougat to upgrade to offical Oreo, I need to be on Nougat.
If this is the case, could I go back to nougat through a TWRP Zip, or would this need to be done through fastboot commands. I know I need a downgraded Bootloader and I don't think ROM flashing affects anything else but /system
PLEASE correct me if I'm wrong. Just a curious guy who loves learning.
Maybe it isn't a right place to ask for it, however, I saw that erfanoabdi made an Ubuntu Touch GSI and also a halium-boot port for river. Maybe it's a silly question, but it is possible to just simply install this GSI (or maybe semi-GSI, because it requires halium port) on river and boot it? There's a simple guide for installing this GSI or any device which has a halium port, here it is:
0) Install treble compatible android 9 rom
1) FORMAT data in twrp
2) Flash halium-boot.img of your device
3) Flash GSI zip (I think I can't give a link here, it is allowed?)
So can it theoretically work? I tried it, but unfortunately I saw just blank screen after booting.
don't format data before LOS16
HueyT said:
don't format data before LOS16
Click to expand...
Click to collapse
So, I should:
1. Flash LOS 16 without formatting data (I'm on Android 10)
2. Format data
3. Flash halium boot
4. Flash UBports GSI
I'll try that but I don't think it's a data problem, because I've already tried it and the zip was successfully installed - files it should copy were copied on data partition, I've checked this. But I'll try once more, without formatting data. Should I boot lineage after flashing?
Yeah, so I followed this and it worked. Thanks!
If anyone had the same problem, I'll write down all what I did:
0. Temporarily booted TWRP and installed it via zip (twrp-3.3.1-14-river)
1. Installed LOS 16 (lineage-16.0-20200127-UNOFFICIAL-river) without formatting data.
2. Booted LOS but it rebooted as the data wasn't formatted and i kept it booting until it booted into LOS Recovery to format data, so I just rebooted phone without formatting data and installed TWRP as in step 0.
3. Flashed halium-boot as boot image in TWRP and installed UBports installed v5 zip, also in TWRP of course.
4. Rebooted phone.
5. Now Ubuntu Touch booted succesfully. Unfortunately, it reboots after about 1 minute. So it's not stable enough at this time. Or maybe I'm doing something wrong, I'll try also another vendor image.
EDIT: I've just tried another vendor.img from newer LOS16 build. Worked fine, but sim doesn't work
Nick_Nicker said:
Maybe it isn't a right place to ask for it, however, I saw that erfanoabdi made an Ubuntu Touch GSI and also a halium-boot port for river. Maybe it's a silly question, but it is possible to just simply install this GSI (or maybe semi-GSI, because it requires halium port) on river and boot it? There's a simple guide for installing this GSI or any device which has a halium port, here it is:
0) Install treble compatible android 9 rom
1) FORMAT data in twrp
2) Flash halium-boot.img of your device
3) Flash GSI zip (I think I can't give a link here, it is allowed?)
So can it theoretically work? I tried it, but unfortunately I saw just blank screen after booting.
Click to expand...
Click to collapse
Did it occur to you to maybe link to what you're talking about? Where is this halium-boot port for River you're talking about? I see nothing in the main GSI thread about anything but the G7 Power. No results on google for halium-boot river or halium river point to anything but this thread, so I have no idea what you could possibly mean.
Check on https://build.lolinet.com/file/halium/
Here you can find GSI and halium-boot images from Erfan. He also posted it on XDA, here you can find all information about it: https://forum.xda-developers.com/pr...development/gsi-ubuntu-touch-ubports-t4110581
So, halium-boot.img is found on build.lolinet.com
But you can also build Halium 9 image if your device's kernel source is available, here's some info https://github.com/ubports/porting-notes/wiki/Generic-system-image-(GSI)#how-to-install-gsi
Also it's very important to have Android 9 ROM installed before. However, stock Android 9 didn't work for me, I prefer LineageOS. So, just install Lineage and then the GSI and halium boot image. For Moto G7 also flash 'river-firmwares.zip' found on lolinet. It'll fix that weird vibration noise bug. For now, there are some visual glitches visible (also only on river), but it'll be fixed. Anbox is working if you have /data partition formatted in ext4 (not f2fs), so if you follow instructions, you can also run some Android apps. Unfortunately, for me internet connection inside Anbox doesn't work.
Thanks sorry I was just starting to feel a bit insane, that stuff is not indexed on google at all by the looks of it. Thank you.
So here is the process that worked for me.
I started with the stock rom.
1. Followed the full Lineage OS install instructions, including the partitions zip etc.
2. Installed Lineage OS on Slot B per the above instructions
3. Wiped data
4. Flash halium-boot.img
5. Flash GSI zip
Everything works perfectly including cellular functionality.
Followed the steps above. Is it possible to revert?
I followed the steps above, but I am have serious issues with the screen jitter. I have been looking all over the place to see if there is a way to revert back to android so that I can use my phone without the screen jitter. Does any one have any instructions on how to do this? I did turn on ADB mode on Ubuntu Touch but my computer does not see an adb device. Thank for any help.
Took me a long time to figure out too.
Main thing is, if you hold down Power and Volume Down, eventually it will reboot to the boot menu. Don't select anything, just plug it in, and you'll have fastboot.
To go back to stock:
1. Hold down Power and Volume till the boot menu shows up.
2. Plug the phone into your PC
3. Get the newest firmware for your phone model. I bought mine at Best Buy, so it was RETUS aka retail US. https://mirrors.lolinet.com/firmware/moto/river/official/
4. Extract the archive, and enter that folder in your terminal
5. Run the following commands from that folder. I saved these commands in a shell script and ran it but I think you can just paste it
THIS WILL WIPE ANY DATA ON YOUR PHONE AND PUT IT BACK TO FULL FACTORY FIRMWARE WITH LOCKED BOOT LOADER. At least when I ran it, it got my phone 100% no more complaints when it boots about untrusted code. After this you should have a fresh phone you can unlock and try flashing again. THis also restored my OTA ability and I was able to get the Android 10 update without any issues.
fastboot oem lock begin
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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 system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.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 system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot oem lock
Click to expand...
Click to collapse