This is for a Motorola XT1955-5 Retail US. I wanted chrome and play store to where the user cant get to them, but other apps can still interact with them. This is a quick and dirty guide in case anyone is in same boat
Install drivers for Motorola g7 power.
Install adb and fastboot tools minimal. Do the portable version
Get the stock firmware from lolinet this person is great!
Flash your phone with the latest firmware. Commands are below. Notice we don't erase user data cuz we don't need to. If it doesn't, work, you can rerun and erase data.
Download the magisk manager app and install on phone
Unpack the stock firmware, and copy the boot.img to the phone
In magisk manager, install magisk (not manager). Select download and install, and select the boot.img
Once it creates the magisk_patched.img, copy that to your computer
Boot the phone to bootloader, and from your computer, run fastboot flash boot magisk_patched.img
Boot the phone normally, and go to magisk manager and see magisk is installed.
Now download the twrp temporary recovery image to your machine.
Boot to the bootloader
Now run: fastboot boot twrp-3.3.1-2-ocean.img
Go to mount. Check the box for system
Now to Advanced -> terminal, and run the commands to remove the system apps from the phone
rm -rf /system/system/app/Chrome
rm -rf /system/system/priv-app/Phonesky
Now boot the phone normally. You will see the play store and chrome are gone!
The trick now is to get a version of the app that we can load, but the user cant touch.
Download chrome and play store from apkmirror.com
Install them on the phone
Now download link2sd and install on phone
Use link2sd with root (it should prompt you for magisk root access), and "freeze" the chrome and play store apps
(Pro tip, make sure the latest version of android web view is installed to pair with latest version of chrome. You don't need to freeze web view)
Now get rid of link2sd.
Now you have a phone where people cant use chrome or play store, but other apps that require it will work.
This is mainly useful if you want a person to use the phone but not install apps on it. The only way around this for them would be to reflash the stock boot.img to the boot partition, or manually copy the app from a usb drive. But if you give someone the phone and say "don't install apps on it" and they don't have other devices, this is the way to do it.
Fastboot commands:
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 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_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 oem oem.img
fastboot flash oem_b oem_other.img
##fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Related
Dear All,
After upgrading to Nougat 7.0 April patch with the following commands:
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 erase modemst1
fastboot erase modemst2
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.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash system system.img_sparsechunk.4
fastboot.exe flash system system.img_sparsechunk.5
fastboot.exe flash system system.img_sparsechunk.6
fastboot.exe flash system system.img_sparsechunk.7
fastboot.exe flash system system.img_sparsechunk.8
fastboot.exe flash system system.img_sparsechunk.9
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
My phone works normally but if i shut down and power on ,the phone boots on fastboot and I have to press on start to boot on OS . Additionally the id status has changed to bad key (previous on n/a status).
I get the update notification to 7.1.1 but because it cannot boot to recovery mode (which is part of the update procedure ) directly and it boots on fastboot mode, the update fails.
Any suggestion?
Looks like you set fastboot mode when you flashed, and just forgot to clear it.
Try rebooting to bootloader
Connect your device to your computer
In the ADB terminal, type 'fastboot oem fb_mode_clear' without the quotes and execute the command.
Reboot and see if that clears the block.
echo92 said:
Looks like you set fastboot mode when you flashed, and just forgot to clear it.
Try rebooting to bootloader
Connect your device to your computer
In the ADB terminal, type 'fastboot oem fb_mode_clear' without the quotes and execute the command.
Reboot and see if that clears the block.
Click to expand...
Click to collapse
you re MY MAN . thx a lot!
A friend unlocked its bootloader and tried to root it with no success.
The phone works but only boots through fastboot, because when I press the power button it enters fastboot mode instead of booting.
I don't know what happened, as I was not the one who tried to root, so I just wanted to know how to revert back to stock and relock the bootloader, since the phone works normally.
freeZbies said:
A friend unlocked its bootloader and tried to root it with no success.
The phone works but only boots through fastboot, because when I press the power button it enters fastboot mode instead of booting.
I don't know what happened, as I was not the one who tried to root, so I just wanted to know how to revert back to stock and relock the bootloader, since the phone works normally.
Click to expand...
Click to collapse
If they flashed twrp and your phone can only be started normally through the bootloader see
https://forum.xda-developers.com/g5/how-to/fix-phone-reboots-recovery-mode-started-t3705325
If you want to root the phone stock can only be rooted with a system root
Most roots now use a systemless root which is not compatible with the stock kernel
You either need a custom rom to use the latest magisk root or if you want to stick with stock use an old version of magisk (can't remember which really old version works) or use supersu but flash the config zip first and set to system as default will be systemless
With regards to flashing stock download firmware and run these fastboot commands assuming you have fastboot set up on your pc
fastboot oem fb_mode_set
fastboot flash partition gpt.bin (do not flash unless you want to repartition the phone)
fastboot flash bootloader bootloader.img (do not flash unless you really need to replace the bootloader)
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (ignore any error)
fastboot erase clogo (ignore any error)
fastboot oem fb_mode_clear
fastboot reboot
To lock the bootloader do the above and then go back to the bootloader mode & enter these fastboot commands
fastboot oem lock
fastboot oem lock (yes type it again)
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 boot boot.img
fastboot oem lock
Then once restarted refresh all the firmware again with the commands from earlier
I have seen though that some boot.img are not officially signed so it may not lock
TheFixItMan said:
If they flashed twrp and your phone can only be started normally through the bootloader see
https://forum.xda-developers.com/g5/how-to/fix-phone-reboots-recovery-mode-started-t3705325
If you want to root the phone stock can only be rooted with a system root
Most roots now use a systemless root which is not compatible with the stock kernel
You either need a custom rom to use the latest magisk root or if you want to stick with stock use an old version of magisk (can't remember which really old version works) or use supersu but flash the config zip first and set to system as default will be systemless
With regards to flashing stock download firmware and run these fastboot commands assuming you have fastboot set up on your pc
fastboot oem fb_mode_set
fastboot flash partition gpt.bin (do not flash unless you want to repartition the phone)
fastboot flash bootloader bootloader.img (do not flash unless you really need to replace the bootloader)
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (ignore any error)
fastboot erase clogo (ignore any error)
fastboot oem fb_mode_clear
fastboot reboot
To lock the bootloader do the above and then go back to the bootloader mode & enter these fastboot commands
fastboot oem lock
fastboot oem lock (yes type it again)
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 boot boot.img
fastboot oem lock
Then once restarted refresh all the firmware again with the commands from the first post
I have seen though that some boot.img are not officially signed so it may not lock
Click to expand...
Click to collapse
Yes, thank you.
I was checking the relocking guides here in xda and seems signed boot images are the problem. Anyways, I'll check to see if it works.
freeZbies said:
Yes, thank you.
I was checking the relocking guides here in xda and seems signed boot images are the problem. Anyways, I'll check to see if it works.
Click to expand...
Click to collapse
Also just noticed you are talking about the Moto G5s - this is the Moto G5 Cedric forum
The Moto G5s forum is located
https://forum.xda-developers.com/moto-g5s
TheFixItMan said:
Also just noticed you are talking about the Moto G5s - this is the Moto G5 Cedric forum
The Moto G5s forum is located
https://forum.xda-developers.com/moto-g5s
Click to expand...
Click to collapse
Oh thanks, I'm gonna check it there, because it's indeed a Moto G5S.
Only thing I'd like to say is that on the XDA Labs app the only forum shown when I search for Moto G5S is the Moto G5 forum, no variants are presented, whom should I report this to, so that it can be fixed?
freeZbies said:
Oh thanks, I'm gonna check it there, because it's indeed a Moto G5S.
Only thing I'd like to say is that on the XDA Labs app the only forum shown when I search for Moto G5S is the Moto G5 forum, no variants are presented, whom should I report this to, so that it can be fixed?
Click to expand...
Click to collapse
No idea - don't use the app
The email on the Google play listing says
[email protected]
The thread for the app is
https://forum.xda-developers.com/android/apps-games/labs-t3241866
hELLO..
I have had a moto g5 with oreo and magisk installed I tried to unistall magisk from magisk app after reboot it told me that startup failed then flashed an nougat rom and it worked perfectly but without imei numbers so i deleted cache from twrp recovery and tried to install the same software again but it gave me the error at the end ..what should I know now to fix the mobile knowing that when i try to select recoverymode it tells me ersing and then takes m back to fastboot
note the first time i just opened a bat file with the software that installed the software automatically..
the bat file told me that
<bootloader> slot-count not found
<bootloader> slot suffixes not found
<bootloader>has-slot:fsg not found
hELLO..
I have had a moto g5 with oreo and magisk installed I tried to unistall magisk from magisk app after reboot it told me that startup failed then flashed an nougat rom and it worked perfectly but without imei numbers so i deleted cache from twrp recovery and tried to install the same software again but it gave me the error at the end ..what should I know now to fix the mobile knowing that when i try to select recoverymode it tells me ersing and then takes m back to fastboot
note the first time i just opened a bat file with the software that installed the software automatically..
the bat file told me that
<bootloader> slot-count not found
<bootloader> slot suffixes not found
<bootloader>has-slot:fsg not found
Click to expand...
Click to collapse
Code:
<bootloader> slot-count not found
<bootloader> slot suffixes not found
<bootloader>has-slot:fsg not found
This is a totally normal output
You either have an error elsewhere or you are trying to flash wrong firmware
If you have a working bootloader there's no need to flash gpt or bootloader parts of the firmware if you are flashing the same android version - if you are upgrading android versions you will need to flash these
The commands are
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 oem fb_mode_clear
fastboot reboot
Firmware can be download from https://mirrors.lolinet.com/firmware/moto/cedric/official/
Hello friends, came out OTA update for my moto z2 Brazilian version, but I have twrp and magisk installed. Do I need to remove both and reinstall the original oreo firmware or can I upgrade normally?
ps: sorry i'm kinda noobie
EDIT: resolved: method posts below :victory:
You should leave it as without any modification. And install the update. Source: Own experience
dark-basic said:
You should leave it as without any modification. And install the update. Source: Own experience
Click to expand...
Click to collapse
so if i install stock recovery and remove magisk completely can i upgrade without problems?
viniisiilvaa said:
so if i install stock recovery and remove magisk completely can i upgrade without problems?
Click to expand...
Click to collapse
after some internet research, i did the update as follows.
MOTO Z2 PLAY MODEL XT1710-07 (I don't know if it works on other models)
1 - be in the version "RETBR OPSS27.76-12-25-23"
2 - completely removed magisk
3 - original re-flash recovery from last rom OREO from fastboot (XT1710-07_ALBUS_RETBR_8.0.0_OPSS27.76-12-25-23_cid50 ...) to remove TWRP
4 - Download Pie rom (XT1710-07_ALBUS_RETBR_9.0_PPS29.133-30_cid50 ...)
5 - Flash from fastboot with the following commands (I did not wipe not to lose the files)
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 erase modemst1
fastboot erase modemst2
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 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 oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
took about 15-25 minutes and went back to normal operation. :victory::victory::victory:
PS: I am not responsible if your phone has a problem after this process. :good:
Hi there guys,
I need help with my phone. I've flashed TWRP on it so i would be able to flash a custom ROM. Everything went fine and i was able to install the custom ROM without errors. Now, everytime i start my phone it only shows the "No Command" screen with an open belly Droid. The only way i'm able to boot it is going to fastboot mode and booting into Factory Mode.
I tried flashing the stock rom with several different methods, and all ends in the same, the "no command" screen on boot.
It's now flashed with the stock rom but i can't get it to boot normally. I've tried Formatting /data, /cache, everything in my hands. What should i do?
how, exactly, did you flash twrp?
using the instructions provided on twrp website
and what procedure did you use to re-flash stock?
i tried using fastboot and also the "Rescue and Smart Assistant" app, both ended up with the same results
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 erase modemst1
fastboot erase modemst2
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 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 oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
try doing this
hi there,
that's what i did when i mentioned that i flashed using fastboot...
sergiobaiao said:
hi there,
that's what i did when i mentioned that i flashed using fastboot...
Click to expand...
Click to collapse
these exact commands in this exact order?
yes, exactly
then unfortunately im out of ideas