Google apps ..."infecting" a fresh LOS install? Feedback on workaround? - Motorola One Guides, News, & Discussion

Hi. I've noticed that after this last time I did a stock factory reflash using fastboot, every time I try to install LOS to the phone, Three google apps are left behind on the home screen. So did a factory recovery again, with the motorola recovery assistant. The apps were still there.
each time, booted TWRP, formatted data, then reboot into TWRP, then clear dalvik, system, data before trying to install LOS. The gapps fragments still showed up. What is known is that the play store and play services are not left behind, only the apps themselves remain., so they don't actually work, they just complain that play services is not present and exit.
Searched around on the internet but didn't really see a solution. so I came up with my own. I'm posting it here to get some feedback, and to maybe see if someone has a better way, because just flashing the stock rom was not solving this problem.
All steps in this walk through were done with adb fastboot and TWRP recovery.
##Make sure both of the above tools AND the USB drivers definitely work on your PC and device before doing this, you will be intentionally bricking your phone! I am not responsible for your device if you try this!##
Stuff you need:
a) The blankflash .zip from this guide: https://forum.xda-developers.com/motorola-one/development/blankflash-motorola-one-t4097391
b) The factory rom .zip for the baseband version currently running on your deen from lolinet.
c) The 8.1.0 rom .zip for your deen from lolinet.
d) LineageOS or other non-gapps rom of your choice. I used the one from this guide: https://forum.xda-developers.com/motorola-one/development/rom-lineage-17-1-motorola-one-t4131339
All Motorola One firmwares are here: https://mirrors.lolinet.com/firmware/moto/deen/official/
DO NOT UNPLUG THE PHONE WHILE DOING THIS. I don't know what will happen if you do.
Steps I did:
0) Unzip both of the roms and the blankflash into their own folders on the PC. Put LOS on your sdcard.
1) Reflash phone to factory stock. Do the initial set up and activate usb debugging in developer tools.
2) Reboot the phone into bootloader mode.
3) Flash the 8.1.0 rom. The phone will brick. It should brick to the blinking LED, but if it just bricks with no LED the PC should still pick it up and initialize the blankflash driver, as long as the usb drivers were installed correctly.
4) Flash the blankflash to get it back into bootloader.
5) Use these commands to flash only the BL, baseband, modem and stub partition from the factory stock flash .zip you downloaded from step b) above to your phone:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash dsp_b adspso.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system_other.img
fastboot flash system_b system_other.img
fastboot oem fb_mode_clear
fastboot set_active b
fastboot reboot bootloader
6) boot into TWRP, wipe/format data. Type yes to confirm.
7) Reboot to bootloader
8) Boot to TWRP again
8) Wipe/advance wipe/system-data-dalvik ONLY
9) Install LOS from your sd card.
10) After LOS install, boot to bootloader
11) Getvar all, if active slot is not a, set it to a
12) Boot LOS.
Thoughts? Is there a better way to do this??
(edited to clarify the steps)

Related

Bootloop on any Surnia ROM

so I was using cm12.1 and decided to update to latest nightly build but after that, I've experienced bootloop, after restoring to my previous ROM and download the whole Nightly ROM and flashed it, my phone bootloops. used other ROM's but bootloop persist, anyone can help me?
PaulDnoOb said:
so I was using cm12.1 and decided to update to latest nightly build but after that, I've experienced bootloop, after restoring to my previous ROM and download the whole Nightly ROM and flashed it, my phone bootloops. used other ROM's but bootloop persist, anyone can help me?
Click to expand...
Click to collapse
If your phone runs fine after restoring your previous ROM, whatever your flashing must be bad or wrong for your phone.
If you cannot get your phone running with a restore, hopefully you can get into the bootloader.
If you can get into the bootloader (volume down and power buttons, which brings you to AP Fastboot Flash Mode), you can flash a factory image, assuming there is a good one out there for your phone. I flashed a factory image a couple of days ago on a Moto E 2015 for a friend, and it is working fine. There are a number of threads / links to flashing factory images for the Moto E 2015.
tedr108 said:
If your phone runs fine after restoring your previous ROM, whatever your flashing must be bad or wrong for your phone.
If you cannot get your phone running with a restore, hopefully you can get into the bootloader.
If you can get into the bootloader (volume down and power buttons, which brings you to AP Fastboot Flash Mode), you can flash a factory image, assuming there is a good one out there for your phone. I flashed a factory image a couple of days ago on a Moto E 2015 for a friend, and it is working fine. There are a number of threads / links to flashing factory images for the Moto E 2015.
Click to expand...
Click to collapse
I've finally fixed my phone by flashing the factory images thanks for your help :good:
PaulDnoOb said:
I've finally fixed my phone by flashing the factory images thanks for your help :good:
Click to expand...
Click to collapse
I have to same problem. What 'factory rom' did you use to fix it?
edit 1:
I did install cm-12.1-20151226-NIGHTLY-surnia using this TWRP version and everything was fine.
I could start and restart my phone without any problems. After adding some google apps and installing some CW-themes I decided to reboot.
After that: boot loop!
So far I have Tried the following things without success:
- TWRP factory reset
- reinstall cm
- install older version CM (nightly build 20151224)
- reinstall cm using cm-recovery instead of TWRP
- removing external SD-card
- advanced flash wipe
- some more re-installation of CM
- installed a factory ROM (I guess?? ) AOSP-5.1.1-20150921-surnia-jenkins-dual-28 )
Nothing helped so far. The "Fix permissions" and "Fix SELinux" options in TWRP are getting tempting. but I suppose this might be dangerous to use.
Anyone some tips?
edit 2:
It seems to be fixed now. I'm not sure how I did it though.
I've tried multiple things in different sequence and ended with installing some of the following stuff
[ROM] Boost Moto E 2015 LTE Stock 5.1 (LPI23.29-18-S.11) Unmodified & Deodexed
Before that I flashed multiple files from the following zip-file to my phone (I suppose this is relevant as well):
"XT1524_SURNIA_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml.zip"
Using the following commands:
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 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 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 oem config carrier vzw
fastboot oem fb_mode_clear
Greetings,
Exhale
exhalenl said:
I have to same problem. What 'factory rom' did you use to fix it?
edit 1:
I did install cm-12.1-20151226-NIGHTLY-surnia using this TWRP version and everything was fine.
I could start and restart my phone without any problems. After adding some google apps and installing some CW-themes I decided to reboot.
After that: boot loop!
So far I have Tried the following things without success:
- TWRP factory reset
- reinstall cm
- install older version CM (nightly build 20151224)
- reinstall cm using cm-recovery instead of TWRP
- removing external SD-card
- advanced flash wipe
- some more re-installation of CM
- installed a factory ROM (I guess?? ) AOSP-5.1.1-20150921-surnia-jenkins-dual-28 )
Nothing helped so far. The "Fix permissions" and "Fix SELinux" options in TWRP are getting tempting. but I suppose this might be dangerous to use.
Anyone some tips?
edit 2:
It seems to be fixed now. I'm not sure how I did it though.
I've tried multiple things in different sequence and ended with installing some of the following stuff
[ROM] Boost Moto E 2015 LTE Stock 5.1 (LPI23.29-18-S.11) Unmodified & Deodexed
Before that I flashed multiple files from the following zip-file to my phone (I suppose this is relevant as well):
"XT1524_SURNIA_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml.zip"
Using the following commands:
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 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 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 oem config carrier vzw
fastboot oem fb_mode_clear
Greetings,
Exhale
Click to expand...
Click to collapse
that's what I did, flashing the whole stock ROM revived my ex moto e 2015 phone! cheers! :highfive:

Phone messed up.

Ok, i have unlocked bootloader, installed this rom https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342, added twrp via fastboot, rooted and so on.
Everything worked like a charm.
Than yesterday I got this update notification (from nplp 25.86-15 to nplp 25.86 -17-3; something about fixing notification sound - about 500mb). I thought what the hell lets try it - ended up in boot loop to recovery(twrp).
After that I installed this rom (odexed version) https://forum.xda-developers.com/moto-z/development/twrp-ported-to-moto-z-eu-version-t3470920.
Again I tried the update since it restored stock recovery - it went into the process and than reported some error.
Now, no matter what rom I install(those 2 and I tried cm14) phone acts messed up, it freezes and reboots when using it randomly and always reboots when screen goes to sleep 4 about 10 seconds.
I have also tried to install mm rom via twrp but ended up in recovery loop.
Any help is highly appreciated..
You need to flash back full stock ROM for your device. Had same issue. But that's if you are downgradable to MM roms
tafarelli said:
Ok, i have unlocked bootloader, installed this rom https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342, added twrp via fastboot, rooted and so on.
Everything worked like a charm.
Than yesterday I got this update notification (from nplp 25.86-15 to nplp 25.86 -17-3; something about fixing notification sound - about 500mb). I thought what the hell lets try it - ended up in boot loop to recovery(twrp).
After that I installed this rom (odexed version) https://forum.xda-developers.com/moto-z/development/twrp-ported-to-moto-z-eu-version-t3470920.
Again I tried the update since it restored stock recovery - it went into the process and than reported some error.
Now, no matter what rom I install(those 2 and I tried cm14) phone acts messed up, it freezes and reboots when using it randomly and always reboots when screen goes to sleep 4 about 10 seconds.
I have also tried to install mm rom via twrp but ended up in recovery loop.
Any help is highly appreciated..
Click to expand...
Click to collapse
i have the exactly same situation with my phone please help... i flashed MM rom but it didn't help it keeps rebooting every 5-10 minutes for no reason... will cyanogenmod 14.1 from this forum help?
Ok I have tried.
I flashed http://www.filefactory.com/file/6ht...ubsidy-DEFAULT_regulatory-03_CFC_EMEA.xml.zip using following commands:
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 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 system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
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 oem config carrier T-2
fastboot oem fb_mode_clear
Phone booted to mm stock (build number MPL 24.246-17) but I already had one reboot few minutes after.
Any suggestions?
kaxuna1 said:
i have the exactly same situation with my phone please help... i flashed MM rom but it didn't help it keeps rebooting every 5-10 minutes for no reason... will cyanogenmod 14.1 from this forum help?
Click to expand...
Click to collapse
I tried with cm but it's not helping.
Phone is stable so far after that initial self-reboot; I'll wait 4 couple hours and if it stays stable returning to n version because mm is too big of a downgrade.
If it continues rebooting, well I guess I'll just bang my head on the wall few times) cause I am out of ideas..
tafarelli said:
Phone is stable so far after that initial self-reboot; I'll wait 4 couple hours and if it stays stable returning to n version because mm is too big of a downgrade.
If it continues rebooting, well I guess I'll just bang my head on the wall few times) cause I am out of ideas..
Click to expand...
Click to collapse
i dont know what to do anymore i tried CM and it keeps rebooting...
do you have any more suggestions?
kaxuna1 said:
i dont know what to do anymore i tried CM and it keeps rebooting...
do you have any more suggestions?
Click to expand...
Click to collapse
Did you try what I posted above?
I have flashed nougat again after that and had one random reboot since. Don't like the fact that reboot happened but otherwise it feels stable and smooth.
Incomparable from what it was before-phone was unusable..
Ok now I have fully functional and stable Moto Z with rooted nougat (EU version).
Here is the receipt:
Download:
-(1) https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342 (mm rom)
-(2) https://mega.nz/#!ktxzwQrZ!UVHWD2B_ngkk7SiD9bWfVUhIfXkkdjpb2mgQhTrZIR8 (twrp img)
-(3) https://drive.google.com/file/d/0B7t82wiSkgOSdE5pbkVoZmNnLWM/view?usp=sharing (nougat modem)
-(4) https://mega.nz/#!5k5nCJAT!PUYLbJDGGyq3eZJMe38cl4tXG2vaXLIIID-wCdDjcYg (nougat rom)
-(5) superuser-r259.zip from https://superuser.phh.me/ (root zip)
Than from(1) fastboot as follows:
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 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 system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
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 oem fb_mode_clear
Boot up and put (4) and (5) to internal storage (idealy to sd card or usb via otg cable).
Than fastboot twrp from (2): fastboot flash recovery TWRP-Moto-Z.img
Than fastboot modem from (3): fastboot flash modem NON-HLOS.bin
Enter twrp recovery, advanced wipe dalvik, data, cache, format data; install n rom from (4); install root zip from (5)
Reboot
I have also freezed Motorola Update Services via Root Freezer Pro so that I don't get bothered with that type of potential problems in future.
Also, if you want to get rid of that annoying warning message (unlocked bootloader) upon booting download:
https://forum.xda-developers.com/attachment.php?attachmentid=3927285&d=1478365739
https://forum.xda-developers.com/attachment.php?attachmentid=3484630&d=1443097711
Unzip both on your pc, drag logo.bin onto MotoLogo_Injectorv1.1.bat, connect your phone in fastboot mode and follow onscreen instructions.
Hello @tafarelli what versiĆ³n bootloader have your ?? Very thanks
Downgrade the Nougat at Mm ?
Regards
I never upgraded to nougat through OTA but from fastbooting this:
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
so I believe I still have mm bootloader.
If you have n bootloader than I guess(don't know) you will have to wait 4 stock nougat zip equivalent to (1) mm posted above..
tafarelli said:
Did you try what I posted above?
I have flashed nougat again after that and had one random reboot since. Don't like the fact that reboot happened but otherwise it feels stable and smooth.
Incomparable from what it was before-phone was unusable..
Click to expand...
Click to collapse
Yes I tried and it's been a 12 hours without reboot so thanks friend you saved me... I will try that nougat method you posted bello ???
---------- Post added at 11:45 PM ---------- Previous post was at 11:40 PM ----------
tafarelli said:
Ok now I have fully functional and stable Moto Z with rooted nougat (EU version).
Here is the receipt:
Download:
-(1) https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342 (mm rom)
-(2) https://mega.nz/#!ktxzwQrZ!UVHWD2B_ngkk7SiD9bWfVUhIfXkkdjpb2mgQhTrZIR8 (twrp img)
-(3) https://drive.google.com/file/d/0B7t82wiSkgOSdE5pbkVoZmNnLWM/view?usp=sharing (nougat modem)
-(4) https://mega.nz/#!5k5nCJAT!PUYLbJDGGyq3eZJMe38cl4tXG2vaXLIIID-wCdDjcYg (nougat rom)
-(5) superuser-r259.zip from https://superuser.phh.me/ (root zip)
Than from(1) fastboot as follows:
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 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 system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
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 oem fb_mode_clear
Boot up and put (4) and (5) to internal storage (idealy to sd card or usb via otg cable).
Than fastboot twrp from (2): fastboot flash recovery TWRP-Moto-Z.img
Than fastboot modem from (3): fastboot flash modem NON-HLOS.bin
Enter twrp recovery, advanced wipe dalvik, data, cache, format data; install n rom from (4); install root zip from (5)
Reboot
I have also freezed Motorola Update Services via Root Freezer Pro so that I don't get bothered with that type of potential problems in future.
Also, if you want to get rid of that annoying warning message (unlocked bootloader) upon booting download:
https://forum.xda-developers.com/attachment.php?attachmentid=3927285&d=1478365739
https://forum.xda-developers.com/attachment.php?attachmentid=3484630&d=1443097711
Unzip both on your pc, drag logo.bin onto MotoLogo_Injectorv1.1.bat, connect your phone in fastboot mode and follow onscreen instructions.
Click to expand...
Click to collapse
??????
tafarelli said:
I never upgraded to nougat through OTA but from fastbooting this:
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
so I believe I still have mm bootloader.
If you have n bootloader than I guess(don't know) you will have to wait 4 stock nougat zip equivalent to (1) mm posted above..
Click to expand...
Click to collapse
Hello correct I have bootloader Nougat I do not understand what it means to expect 4 stcok nougat zip equivalent to 1 MM postado but back many thanks
regards
iron maiden said:
Hello correct I have bootloader Nougat I do not understand what it means to expect 4 stcok nougat zip equivalent to 1 MM postado but back many thanks
regards
Click to expand...
Click to collapse
It means when they put link for n factory image here
http://www.androidsage.com/2016/12/...ce-android-7-0-nougat-ota-and-factory-images/
(or elshewhere)
than you download it and fastboot stock n rom to repair your (I presume) damaged device.
tafarelli said:
It means when they put link for n factory image here
http://www.androidsage.com/2016/12/...ce-android-7-0-nougat-ota-and-factory-images/
(or elshewhere)
than you download it and fastboot stock n rom to repair your (I presume) damaged device.
Click to expand...
Click to collapse
Hello my Moto z is in nougat but I was wondering if you had bootloader Nougat and could return to forgive MM if I made you believe that it was in brick my phone sorry for my English there is no image factory of the last version? NPL25.86-17-3 " I installed this by adb sideload but I like to install the whole image thanks
regards

MetroPCS Moto E5 Plus Root And Recovery Solution

So with the help of @CodyF86 with his lovely twrp recovery I have had trouble flashing to the metro variant of this device so I found a firmware where I can flash it without messing up my modem and my LTE Metro Connection so this is for those who cannot boot up.
So first you will need to use Cody's guide on booting up twrp to along with fstab and all the other stuff on his guide before doing this.
After you did his guide now it's time for mine if you can't boot up properly and mind you the LTE works and wifi but I can't seem to find out why it feels a bit slow but anyway.
Step 1. Download this update and put it(unzip file) into your adb/fastboot folder on your computer. https://drive.google.com/file/d/1kW-FAfXccQMBMX3DuGJ_p2r0moDiCYtR/view?usp=drivesdk
Step 2. Put your phone into fastboot mode
Step 3. Flash these in order
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 oem oem.img
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
After that's done follow Cody's guide again and make sure you do it step by step and flash ONLY MAGISK 16.7
TheAmbition267 said:
So with the help of @CodyF86 with his lovely twrp recovery I have had trouble flashing to the metro variant of this device so I found a firmware where I can flash it without messing up my modem and my LTE Metro Connection so this is for those who cannot boot up.
So first you will need to use Cody's guide on booting up twrp to along with fstab and all the other stuff on his guide before doing this.
After you did his guide now it's time for mine if you can't boot up properly and mind you the LTE works and wifi but I can't seem to find out why it feels a bit slow but anyway.
Step 1. Download this update and put it(unzip file) into your adb/fastboot folder on your computer. https://drive.google.com/file/d/1kW-FAfXccQMBMX3DuGJ_p2r0moDiCYtR/view?usp=drivesdk
Step 2. Put your phone into fastboot mode
Step 3. Flash these in order
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 oem oem.img
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
After that's done follow Cody's guide again and make sure you do it step by step and flash ONLY MAGISK 16.7
Click to expand...
Click to collapse
I keep getting cannot open error. any help would be greatly apprecciated

Moto G5S PLUS INDIAN VARIANT LOCKING THE BOOTLOADER WITH JUNE PATCH INCLUDED

DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
1. Make sure your device is charged above 80%.
2. We recommend creating a backup of all your important files before beginning with this process.
HOW TO INSTALL STOCK ROM IN MOTO G5 PLUS And LOCK THE BOOT LOADER
1. Download Moto G5s Plus Stock Firmware and other necessary files from the download link.
2. Extract and install ABD Fastboot Drivers drivers
3. Install ADB Fastboot Driver on your PC.
4. Install the Latest Motorola Drivers
5. Now extract stock firmware in ADB Fastboot folder
6. Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
7. Now, connect your device to your PC via a USB Cable.
8. Open a command prompt or PowerShell window and type the following commands:
Code:
fastboot getvar max-sparse-size
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 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Now Setup the phone properly till you reach the main screen, don't skip any steps
Now use this second command
Code:
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock
Flash the phone again with the first command and set it up again then boot to the fastboot again and flash the phone twice with the second command and your Motorola G5S PLUS should have a locked bootloader, keep in mind older Firmware would not work for this process to work, if you see any errors regarding bootloader.img not signed, don't worry and proceed with it.
Downloads:
HTML:
https://drive.google.com/drive/folders/1lWCQAjZBXM_iYHNwBO-5xKU4RY1FK9QV?usp=sharing
Kindly copy the full link to your browser and download the files, all the required files are present on the link
WIsh you guys all the best, I locked my bootloader the same and hope it will solve your problems too if you follow the instructions properly, I am no developer, I learned the hardway
Please Rate and comment if you liked my post helped you.
Shampak said:
DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
1. Make sure your device is charged above 80%.
2. We recommend creating a backup of all your important files before beginning with this process.
HOW TO INSTALL STOCK ROM IN MOTO G5 PLUS And LOCK THE BOOT LOADER
1. Download Moto G5s Plus Stock Firmware and other necessary files from the download link.
2. Extract and install ABD Fastboot Drivers drivers
3. Install ADB Fastboot Driver on your PC.
4. Install the Latest Motorola Drivers
5. Now extract stock firmware in ADB Fastboot folder
6. Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
7. Now, connect your device to your PC via a USB Cable.
8. Open a command prompt or PowerShell window and type the following commands:
Code:
fastboot getvar max-sparse-size
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 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Now Setup the phone properly till you reach the main screen, don't skip any steps
Now use this second command
Code:
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock
Flash the phone again with the first command and set it up again then boot to the fastboot again and flash the phone twice with the second command and your Motorola G5S PLUS should have a locked bootloader, keep in mind older Firmware would not work for this process to work, if you see any errors regarding bootloader.img not signed, don't worry and proceed with it.
Downloads:
HTML:
https://drive.google.com/drive/folders/1lWCQAjZBXM_iYHNwBO-5xKU4RY1FK9QV?usp=sharing
Kindly copy the full link to your browser and download the files, all the required files are present on the link
WIsh you guys all the best, I locked my bootloader the same and hope it will solve your problems too if you follow the instructions properly, I am no developer, I learned the hardway
Please Rate and comment if you liked my post helped you.
Click to expand...
Click to collapse
hi, i have tried the same as you gave command. but unfortunately it doesn't work for me. i had installed soak test OREO then moved to Android P custom ROM, finally rolled back to android N to relock the bootloader. now i couldn't relock it.
i am getting error "still require valid signed image"
i am using sanders.
kindly assist me
Thanks
---------- Post added at 06:39 PM ---------- Previous post was at 06:35 PM ----------
hi, i have tried the same as you gave command. but unfortunately it doesn't work for me. i had installed soak test OREO then moved to Android P custom ROM, finally rolled back to android N to relock the bootloader. now i couldn't relock it.
i am getting error "still require valid signed image"
i am using sanders.
kindly assist me
Thanks
arunkumar.rp said:
hi, i have tried the same as you gave command. but unfortunately it doesn't work for me. i had installed soak test OREO then moved to Android P custom ROM, finally rolled back to android N to relock the bootloader. now i couldn't relock it.
i am getting error "still require valid signed image"
i am using sanders.
kindly assist me
Thanks
---------- Post added at 06:39 PM ---------- the Previous post was at 06:35 PM ----------
hi, I have tried the same as you gave the command. but unfortunately, it doesn't work for me. i had installed soak test OREO then moved to Android P custom ROM, finally rolled back to android N to relock the bootloader. now I couldn't relock it.
i am getting the error "still require valid signed image"
i am using sanders.
kindly assist me
Thanks
Click to expand...
Click to collapse
Don't worry about the signed image. Try the locking command twice back to back. Hope this helps

Question how to remove a custom operating system from a Motorola g power (2021) phone?

how to remove a custom operating system from a Motorola g power (2021) phone?
jazzybird2009 said:
how to remove a custom operating system from a Motorola g power (2021) phone?
Click to expand...
Click to collapse
If you did a nandroid backup (e.g., TWRP etc.), do a full 'clean restore (i.e., wipe cache, Dalvik cache, system AND format data > Yes (important).
If not, do the same full wipe, reboot to fastboot and flash the stock rom. You could also try the Motorola "Rescue and Smart Assistant" but I'm not sure it will work in your particular case.
If you want to go back to stock ROM or "OS" consider this method unofficial works on RETCA not sure about other devices, Verizon for sure needs its own software, The requirements of this method are Windows 10/11, Motorola's USB Drivers and a working Fastboot. Download the stock ROM from here https://mirrors.lolinet.com/firmware/motorola/borneo/ match the model of the device, Extract the firmware guessing it's in Downloads folder open that folder in the Terminal here's an example "cd C:\Users\smoke\Downloads" then here are commands to flash converted from the xml files
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
This has worked for me never had a problem don't expect the same outcome, I would read the terms and services you agreed to when unlocking the bootloader.
Mind if I ask what custom ROM you were using? I haven't seen any for this phone yet

Categories

Resources