Related
I've run into a couple roms (I'd rather not mention in an open forum) that have indicated that the marshmallow bootloader is needed.
I've downloaded and extracted the mm factory images. I've used fastboot plenty of times, but by no means am I an expert. I need to confirm that:
fastboot flash bootloader bootloader.img is going to work. I noticed that the instructions for flashing the system images has a step (fastboot flash partition gpt.bin) before this. Is that needed as well?
I realize I can go through the entire going back to stock to achieve what I need, but it seems overkill if I just need to flash the mm bootloader in fastboot.
Thanks
mxpe 6.0
Edit:
Just bit the bullet and flashed gpt.bin and bootloader.img. Extremely easy.
Steps to flash mm bootloader (assuming you have adb/fastboot/drivers properly setup):
Move mm gpt.bin and bootloader.img into adb directory
reboot into bootloader mode (note bootloader version number A0.1C is lp and A0.48 is mm)
fastboot devices
(should return device number)
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
bootloader is now mm (A0.48)
Files directly from motorola mm firmware:
gpt.bin
https://drive.google.com/file/d/0Bwj2Hf45t6uMbjFfSTRmVDh6eDg/view?usp=sharing
mm bootloader.img
https://drive.google.com/file/d/0Bwj2Hf45t6uMLXBBbGQ0a2pZQjg/view?usp=sharing
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.
Hi i have found the method for go back to naugat from official oreo. Many people got navabr bug in oreo and also battery drain faster in oreo.
I have tried lots of method to go back to naugat but what happen always i got imei null...
so using this method you can go back to naugat without loosing your IMEI...
So what you have to do is first download naugat firmware from below link:
Naugat Firmware With December Patch
and the steps for fastboot:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0 (repeat up to 12)
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot reboot
enjoy hit thanks
Can you verify the link please? The MEGA link sends me to a 'file no longer available' page.
Also, I'm hoping you're linking to the Feb 2018 Nougat 7.1.1 firmware, not the Dec 2017 firmware - if you really want to downgrade. Be aware that your bootloader is still likely the Oreo bootloader (not the Nougat bootloader - there's no commands to flash the bootloader, but then again, your Oreo bootloader may block a downgrade anyway), so attempting to take Nougat OTA updates may hard brick your device. A hard brick may occur if you use OTA updates after downgrading to Nougat from an Oreo firmware newer than the April 2018 security patch. Be careful.
My moto g4 plus, model XT1643 was hardbricked, i installed blank flash on it, it has rebooted into bootloader mode of blankflash with no android logo, and has locked oem of my phone. I cannot install a stock rom now as the oem is locked and when unlocking oem from cmd prompt its asking me to enable oem from from developer options, which i cannot do as my mobile is not booting. Please help as to how can i install stock rom into it as my bootloader and oem is locked now. Any help would be appreciated, thanks.
tried to pass the last stock if I am not mistaken version that is or updated passes without being with bootloader unlocked.
Pranav_dp said:
My moto g4 plus, model XT1643 was hardbricked, i installed blank flash on it, it has rebooted into bootloader mode of blankflash with no android logo, and has locked oem of my phone. I cannot install a stock rom now as the oem is locked and when unlocking oem from cmd prompt its asking me to enable oem from from developer options, which i cannot do as my mobile is not booting. Please help as to how can i install stock rom into it as my bootloader and oem is locked now. Any help would be appreciated, thanks.
Click to expand...
Click to collapse
Following a blankflash, you can only boot into the bootloader, which is normal. It seems that using a blankflash sets your bootloader to be locked, regardless of if it was previously unlocked in the first place. Provided you can flash a stock ROM, your bootloader should become unlocked again.
Have you tried flashing the April 2018 fastboot stock ROM from https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ? The guide there should be useful in how to reflash stock firmware to your device, and as it's the newest firmware that has been leaked, should rescue your device.
If you want to keep your bootloader unlocked and try to save your data, then try the following flashing commands instead of the ones in the guide. Be aware that you may have to factory reset your device should it boot but be unstable.
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
These commands should flash the April 2018 GPT, bootloader, system and modem to your device. Please try to avoid hardbricks in the future by only flashing stock firmware as new or newer than your bootloader, and please do not use old OTA updates.
echo92 said:
Following a blankflash, you can only boot into the bootloader, which is normal. It seems that using a blankflash sets your bootloader to be locked, regardless of if it was previously unlocked in the first place. Provided you can flash a stock ROM, your bootloader should become unlocked again.
Have you tried flashing the April 2018 fastboot stock ROM from https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ? The guide there should be useful in how to reflash stock firmware to your device, and as it's the newest firmware that has been leaked, should rescue your device.
If you want to keep your bootloader unlocked and try to save your data, then try the following flashing commands instead of the ones in the guide. Be aware that you may have to factory reset your device should it boot but be unstable.
These commands should flash the April 2018 GPT, bootloader, system and modem to your device. Please try to avoid hardbricks in the future by only flashing stock firmware as new or newer than your bootloader, and please do not use old OTA updates.
Click to expand...
Click to collapse
Thank you so much, I've restored the stock rom following your guidelines, my phone is working fine but im not able to install any OTA updates after that. Should i just skip any OTA updates from now on, please advice. Thank you.
Pranav_dp said:
Thank you so much, I've restored the stock rom following your guidelines, my phone is working fine but im not able to install any OTA updates after that. Should i just skip any OTA updates from now on, please advice. Thank you.
Click to expand...
Click to collapse
If you flashed the April 2018 security patch stock firmware, there are currently no OTA updates, the April 2018 security patch is the latest available.
If you fully flashed the latest firmware as I mentioned, you should be okay to use OTA updates. Just in future please remember to not use OTA updates if you downgraded your device by flashing old stock firmware.
i have here one xt1640 dead for ota OPJ28.111-22 upgrade.. is possible put in Fastboot for Blank Flash Repair?
Daroas said:
i have here one xt1640 dead for ota OPJ28.111-22 upgrade.. is possible put in Fastboot for Blank Flash Repair?
Click to expand...
Click to collapse
Without a blankflash new enough to flash to the device, I don't think so. You'd have to consider a JTAG repair, a motherboard replacement or buy a new device.
Hi all,
I have a Moto G5 Plus (dual sim, European version) that was on stock Android 8. I wanted to revive this old phone and use it for experimenting.
I unlocked the bootloader, installed TWRP recovery and then installed the unofficial Lineage OS 17.1 (here from xda: [ROM][UNOFFICIAL][10.0][POTTER] LineageOS 17.1).
I then proceeded to get root installed using no-verity and magisk.
I now have a boot loop that loads Lineage but then restarts into TWRP recovery.
It's been a really long time since I fooled around with bootloaders, recoveries and alternative roms (been using a Samsung S8 for several years now on stock rom).
So I am unsure how to proceed. What do you recommend that I do?
I would like to have a rooted Android 10 on the Moto G5 Plus, preferably without a bootloop
Update 1:
Using this thread I have been able to revert to stock Android 8.1 ROM: https://forum.xda-developers.com/showthread.php?t=2542219
But I would be interested to know which Android 10 ROM would be recommended for the Moto G5 Plus?
PartisanEntity said:
Hi all,
I have a Moto G5 Plus (dual sim, European version) that was on stock Android 8. I wanted to revive this old phone and use it for experimenting.
I unlocked the bootloader, installed TWRP recovery and then installed the unofficial Lineage OS 17.1 (here from xda: [ROM][UNOFFICIAL][10.0][POTTER] LineageOS 17.1).
I then proceeded to get root installed using no-verity and magisk.
I now have a boot loop that loads Lineage but then restarts into TWRP recovery.
It's been a really long time since I fooled around with bootloaders, recoveries and alternative roms (been using a Samsung S8 for several years now on stock rom).
So I am unsure how to proceed. What do you recommend that I do?
I would like to have a rooted Android 10 on the Moto G5 Plus, preferably without a bootloop
Update 1:
Using this thread I have been able to revert to stock Android 8.1 ROM: https://forum.xda-developers.com/showthread.php?t=2542219
But I would be interested to know which Android 10 ROM would be recommended for the Moto G5 Plus?
Click to expand...
Click to collapse
Problem; the procedure you followed is for a Moto G, and not a G5 Plus. If you used Moto G firmware on your Moto G5+, you may have induced more problems.
Moto g5+ firmwares are located at https://mirrors.lolinet.com/firmware/moto/potter/official/ Proper firmware for the Moto G5+ depends on your model and what country you are operating in.
potter - Moto G5 Plus = firmware
XT1680(LATAM/Argentina/Chile,2GB) {LATAM; Latin America}
XT1681(LATAM/Colombia/Mexico,2GB)
XT1683(Brazil,DS,DTV,2GB)
XT1684(Europe,3GB)
XT1685(Australia/NewZealand/Europe,3GB)
XT1686(India,3/4GB)
XT1687(USA,2GB/4GB)
{AMX, America Movil Mexico}{owns Claro}
{ATTMX; AT&T Mexico}
{AMZ; Amazon)
{RETAPAC; Retail Pacific; Australia, New Zealand}
{RETAR; Retail Argentina}
{RETBR; Retail Brazil}
{RETEU; Retail European Union)
{RETGB; Retail Great Britian}
{RETIN; Retail India}
{RETLA; Retail Latin America}
{RETMX; Retail Mexico}
{RETUS; Retail Unitied States}
{TEF, Telefonica S A.}
{TEFBR; Telefonica Brazil}
{TEFCO; Telefonica Columbia}
{TEFES; Telefonica European Sector}
{TEFMX; Telefonica Mexico}
Since your in Europe, your firmware group is probally RETEU, RETGB, or TEFES. You need to locate your model number of the phone, maybe a XT1684 or XT1685 and find the model number under the proper directory of firmware. I would download the latest, usually has 8.1.0_OPS28.85-17-6-2 in the firmware name and the lastest date. Extract the software and fastboot it.
For the 8.10_OPS28.85-17-6-2 firmwares the fastboot commands are:
Fastboot flash partition gpt.bin
Fastboot flash bootloader bootloader.img
Fastboot flash modem NON-HLOS.bin
Fastboot flash fsg fsg.mbn
Fastboot flash dsp adspso.bin
Fastboot flash logo logo.bin
Fastboot flash boot boot.img
Fastboot flash recovery recovery.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 oem oem.img
Fastboot erase cache
Fastboot erase userdata
Fastboot erase DDR
Fastboot reboot
Again, this may not work because if the Moto G firmware you flashed on to the Moto G5+.....
Also, did LineageOS work on the phone before flashing Magisk and/or no-verity ?
Hi, thank you for your help.
Yes Lineage OS did work. Was it Magisk or no-verity that caused the bootloop?
So, I went to the proper stock ROM, and then I installed the Pixel Experience: https://download.pixelexperience.org/potter - so far nice and stable.
What is the commended/cleanest/safest way to get root?
PartisanEntity said:
Hi, thank you for your help.
Yes Lineage OS did work. Was it Magisk or no-verity that caused the bootloop?
So, I went to the proper stock ROM, and then I installed the Pixel Experience: https://download.pixelexperience.org/potter - so far nice and stable.
What is the commended/cleanest/safest way to get root?
Click to expand...
Click to collapse
Sorry to not reply earlier - was tied up with election recounts -----
Do not know what caused the boot loop. The proper way to install is to install LineagrOS first, boot LineageOS and make sure it comes up, Then go back to recovery/TWRP and install Magisk and the reboot to system and check LineageOS to make sure it came up. Then look in your apps and see if you have the Magisk icon. On the no-verity, I had a couple that did not work, I was turned on to Disable_Dm-Verity_ForcedEncrypt_02.04.2019.zip at
https://androidfilehost.com/?fid=11410963190603877244 (by WolfCity - thanks)
which worked for me. Use the procedure at paragraph 13 (my procedure that I listed
a PDF, its at http://s000.tinyupload.com/?file_id=...86655137330218 ) to install the program to decrypt the file system. Then reboot the phone and verify the phone is un-encrypted (it will say "Encrypt Phone" instead of Phone Encrypted). Then you will have to reboot back to recovery and reinstall Magisk again (its because when the file system was decrypted the memory was formatted/overwrited). Then boot back to system and verify Magisk is in your icons again. If you have Magisk, you should have root. You can verify root by either programs that check it root or open a terminal window and type in SU and Magisk will pop up a window asking if you want to give the program root access.
Hope that helped.