Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
1 . Download twrp-3.4.0-0-CTL_sprout.img & twrp-installer-3.4.0-0-CTL_sprout.zip copy in one folder
2. connect phone to pc boot your phone to download mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot boot twrp-3.4.0-0-CTL_sprout.img
6. now your phone will boot in to twrp
7. now copy twrp installer.zip in to your phone from pc using type c usb cable
8. now flash twrp installer zip ( this will make your twrp permanent )
10. now flash magisk or what ever your wish and press reboot system
11. now if you people want to boot in to twrp? power off your phone connect to pc or charger
& wait for battery logo and press volume up and power button for 8 seconds now you will boot in to twrp
Download Android 10 Twrp-3.4.0-0 From Here
For More Information About Status Official Click Here
XDA:DevDB Information
TWRP 3.4.0-0 , for the Nokia 7.1
Contributors
Raghu varma
Source Code: https://github.com/TeamWin/android_device_nokia_CTL_sprout
My build script https://github.com/RaghuVarma331/scripts
Version Information
Status: Stable
Current Stable Version: 3.x
Stable Release Date 2019-01-26
Created 2019-01-26
Last Updated 2020-06-25
Hi Raghu, I appreciate the work you are doing for the Nokia community!
I have a question... if I boot directly into TWRP instead of flashing TWRP over my stock recovery, is it truly necessary to reflash the stock recovery? Like for instance, I only want to load magisk on my device/create a nandroid backup and keep stock recovery and stock OS until the Android Q release. Though, from experience from other devices I have owned... booting directly into TWRP instead of flashing only is temporary and keeps the stock recovery intact. I am not sure from your tutorial if I truly need to flash my stock recovery after just booting TWRP temporarily?
usernamedoesnotexist said:
Hi Raghu, I appreciate the work you are doing for the Nokia community!
I have a question... if I boot directly into TWRP instead of flashing TWRP over my stock recovery, is it truly necessary to reflash the stock recovery? Like for instance, I only want to load magisk on my device/create a nandroid backup and keep stock recovery and stock OS until the Android Q release. Though, from experience from other devices I have owned... booting directly into TWRP instead of flashing only is temporary and keeps the stock recovery intact. I am not sure from your tutorial if I truly need to flash my stock recovery after just booting TWRP temporarily?
Click to expand...
Click to collapse
if you want to get back to your stock recovery just flash your stock boot.img of the respective security patch
for example you flashed twrp on may 2019 pie
and now you want to get back to stock recovery?
so just flash using fastboot flash boot boot.img ( may 2019 boot.img)
Raghu varma said:
if you want to get back to your stock recovery just flash your stock boot.img of the respective security patch
for example you flashed twrp on may 2019 pie
and now you want to get back to stock recovery?
so just flash using fastboot flash boot boot.img ( may 2019 boot.img)
Click to expand...
Click to collapse
Thanks for the info! Unfortunately, I couldn't pull my stock recovery from adb and had to use the terminal inside TWRP to pull my recovery. After successfully getting stock recovery, I patched the stock recovery (after copying) to my external SD with magisk and flashed that via adb. Magisk is now installed and I am satisfied.
Note: this is relatively the first time I am leaving stock recovery on my device vs custom recovery to keep the OTA updates. This is because there isn't much of a dev community here at the moment and not much to do on the device.
New Build Is Up
Based On R40
Android version - pie
twrp- based on June 2019
################ The final Main installation procedure #################
Note - this will work only On June 2019 Security Patch And From Now i will update Twrp Every Month
1 . Download twrp-3.3.1-0-CTL.img & twrp-installer-3.3.1-0-CTL.zip copy in one folder
2. connect phone to pc boot your phone to download mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot boot twrp-3.3.1-0-CTL.img
6. now your phone will boot in to twrp
7. now copy twrp installer.zip in to your phone from pc using type c usb cable
8. now flash twrp installer zip ( this will make your twrp permanent )
10. now flash magisk or what ever your wish and press reboot system
11. now if you people want to boot in to twrp? just power off your phone connect to pc or charger
& wait for battery logo and press volume up and power button for 8 seconds now you will boot in to twrp
congratulations now you are successfully booted in to twrp
@Raghu varma
Any telegram group for development? If that exist, please add me t.me/theHari08.
Note - Twrp Support is back for Nokia 7.1
Changelog
13-12-2019
* Initial android 10 twrp builds are up
* Twrp based on 3.3.1-0
* Supports on Android 10 stock roms and custom roms
* supports on Android 9 stock roms and custom roms
* Follow instructions as i mentioned above in the xda thread for installation
* Omni sources based on latest r47
* Decryption works
Hi,
I used to be into flashing phones back in the day but now I'm a bit rusty so my question is simple:
Do I have to unlock the bootloader first before I can flash twrp? It is a painpoint for me on this phone that there is no simple way to do that.
Thanks.
giant_karlik said:
Hi,
I used to be into flashing phones back in the day but now I'm a bit rusty so my question is simple:
Do I have to unlock the bootloader first before I can flash twrp? It is a painpoint for me on this phone that there is no simple way to do that.
Thanks.
Click to expand...
Click to collapse
Before you can modify anything on a phone you always have to unlock the bootloader. Since Nokia does not allow official bootloader unlocks, we have to go through a paid method (see other threads about unlocking the bootloader here).
this guy will do it for a small fee well worth it ...
Added official support
Android 10 TWRP doesn't work on 7.1 december update
Hey,
Thanks for all the hard work you're putting into this project, really helped me when I was using android 9.
But I can't seem to make the latest version you uploaded work now that I'm on android 10. When I try to boot the image file I'm stuck on the android one logo, no matter how much I wait.
So I was wondering if the latest update isn't supported yet or if I'm doing something wrong.
Really sorry to bother you if it's the former.
Have a nice day.
Reysen said:
Hey,
Thanks for all the hard work you're putting into this project, really helped me when I was using android 9.
But I can't seem to make the latest version you uploaded work now that I'm on android 10. When I try to boot the image file I'm stuck on the android one logo, no matter how much I wait.
So I was wondering if the latest update isn't supported yet or if I'm doing something wrong.
Really sorry to bother you if it's the former.
Have a nice day.
Click to expand...
Click to collapse
*make sure your phone bootloader is unlocked.
* make sure you downloaded twrp files from xda thread download links
* make sure you follow steps as i mentioned above
according to your info i tested again on my Nokia 6.1 Plus android 10 stock rom based on december security patch.
Nokia 7 Plus , Nokia 7.1 , Nokia 6.1 & Nokia 6.1 Plus all sources are same
so it should work on 7.1 too make sure you re flashed stock rom and test again because trying several times on same partition may corrupt and failed to boot.
Hey, thanks for your fast answer.
*make sure your phone bootloader is unlocked.
Click to expand...
Click to collapse
The bootloader is indeed unlocked
* make sure you downloaded twrp files from xda thread download links
Click to expand...
Click to collapse
I tried multiple versions from the sourceforge link.
* make sure you follow steps as i mentioned above
Click to expand...
Click to collapse
I'm stuck at "boot TWRP" step as there is only the android one boot screen and I can only reboot. Though for some reason I can still use some fastboot commands (such as fastboot reboot bootloader).
I never modified the system partition on my phone through fastboot, only flashed a magisk patched boot.img when I was still on android 9.
Before upgrading to android 10, I patched the stock boot.img and did a factory reset. Then I did all the available updates through the phone update system. Never used a custom rom, so everything should be stock.
Forgot to mention but the phone isn't bricked or anything, it work normally without any issue. I just can't run TWRP for some reason.
Here's the oem information if that can help you
Thanks and have a nice day
(Unfortunately I can't upload pictures or post links)
Reysen said:
Hey, thanks for your fast answer.
The bootloader is indeed unlocked
I tried multiple versions from the sourceforge link.
I'm stuck at "boot TWRP" step as there is only the android one boot screen and I can only reboot. Though for some reason I can still use some fastboot commands (such as fastboot reboot bootloader).
I never modified the system partition on my phone through fastboot, only flashed a magisk patched boot.img when I was still on android 9.
Before upgrading to android 10, I patched the stock boot.img and did a factory reset. Then I did all the available updates through the phone update system. Never used a custom rom, so everything should be stock.
Forgot to mention but the phone isn't bricked or anything, it work normally without any issue. I just can't run TWRP for some reason.
Here's the oem information if that can help you
Thanks and have a nice day
(Unfortunately I can't upload pictures or post links)
Click to expand...
Click to collapse
Well i don't want to waste my time infront of sitting xda and answering questions like customer care but still yes i will help you out in this
1. just don't use patched boot images
2. Flash stock rom again for fresh start
3. If you are confused about flashing stock rom process
Go ahead to this link
https://forum.xda-developers.com/nokia-7-1/development/tool-stock-rom-flash-tool-nokia-7-1-t4023959
4. After booting in to stock rom power of your phone & press volume down & power button for download mode
5. now open cmd in twrp download folder
6. type fastboot boot twrpname.img
7. Now your phone reboots to twrp
8. Decrypt your phone using your lock screen password,pin or pattern (if you keep security)
9. Now flash magisk of what ever you want but make sure you flash the stuff according to my loyal steps. Which i mentioned my xda threads in 7.1 xda forums
Peace !
Raghu varma said:
Well i don't want to waste my time infront of sitting xda and answering questions like customer care but still yes i will help you out in this
1. just don't use patched boot images
2. Flash stock rom again for fresh start
3. If you are confused about flashing stock rom process
Go ahead to this link
https://forum.xda-developers.com/nokia-7-1/development/tool-stock-rom-flash-tool-nokia-7-1-t4023959
4. After booting in to stock rom power of your phone & press volume down & power button for download mode
5. now open cmd in twrp download folder
6. type fastboot boot twrpname.img
7. Now your phone reboots to twrp
8. Decrypt your phone using your lock screen password,pin or pattern (if you keep security)
9. Now flash magisk of what ever you want but make sure you flash the stuff according to my loyal steps. Which i mentioned my xda threads in 7.1 xda forums
Peace !
Click to expand...
Click to collapse
Hi,
I flashed my nokia 7.1 like instructed and everything went well (though I noticed it wasn't the latest version, but that's a detail).
Went into the bootloader and tried running TWRP but still had the same issue as before (stuck on the android one boot, it was a totally stock ROM, the one provided on your other post).
So I used the boot.img from the stock ROM you uploaded and patched it, then flashed it in the bootloader and it worked.
So even though TWRP still doesn't work in the end I did what I wanted to do, so thanks for your help.
And again, thanks for all the work you're doing, sorry to bother you.
Have a nice day.
Same problem here - unlocked my sons' Nokia 7.1 today via techmestos service, rebooted into the downgraded Android, entered setup and started the mandatory Android upgrade, went through that successfully, activated ADB, got into Download mode and ran the following command:
Code:
fastboot boot twrp-3.3.1-0-CTL_sprout-10.0-20200109.img
downloading 'boot.img'...
OKAY [ 1.058s]
booting...
OKAY [ 5.058s]
finished. total time: 6.116s
Phone screen changed to the 'bootloader unlocked' screen and then the usual AndroidOne boot screen appeared. But neither TWRP nor Android came up ...
The downloaded files are OK, I checked the sha1sum on both of them
Any hints what to do here?`How can I help to track this down?
husky69 said:
Same problem here - unlocked my sons' Nokia 7.1 today via techmestos service, rebooted into the downgraded Android, entered setup and started the mandatory Android upgrade, went through that successfully, activated ADB, got into Download mode and ran the following command:
Code:
fastboot boot twrp-3.3.1-0-CTL_sprout-10.0-20200109.img
downloading 'boot.img'...
OKAY [ 1.058s]
booting...
OKAY [ 5.058s]
finished. total time: 6.116s
Phone screen changed to the 'bootloader unlocked' screen and then the usual AndroidOne boot screen appeared. But neither TWRP nor Android came up ...
The downloaded files are OK, I checked the sha1sum on both of them
Any hints what to do here?`How can I help to track this down?
Click to expand...
Click to collapse
TWRP went official so technically you can go to the TWRP site and download the current there
In addition to it going official, there is no need to download both the img and zip installer with it.
https://dl.twrp.me/CTL_sprout/
You can now just flash (fastboot flash recovery twrp-3.3.1-0-CTL_sprout.img).
https://twrp.me/nokia/nokia7.1.html
Things to keep in mind: If you have a PIN or Passcode you should disable it on the ROM before booting up to TWRP because of encryption.
If you flash another ROM such as Lineage OS shortly after flashing TWRP, it will replace the TWRP with the Lineage OS recovery. So you will probably have to flash TWRP again.
I hope that this works?!
i have android 9 is there a twrp image for 9?
Alas, this does not help, the same problem, the phone hangs on the logo)
P.S
executed the commands like this:
fastboot flash recovery (error issued)
fastboot boot
and successfully loaded into TWRP
Phone: OnePlus 7 Pro
Build number: Oxygen OS 10.0.3 GM21BA
Anndroid Version: 10
Model: GM1913
Hi all,
I received yesterday my Oneplus 7 Pro. My objective is to install nethunter fully rooted.
After looking the requirements in the offensive security website i noticed i need 3 things
TWRP
Magisk
DM-Verify
I started with TWRP watching different tutorials and comparing them but they are similar.
- Installed sdk platform tools and Minimal adb/fastboot ( tried both ways )
-unlocked the bootloader and enabled usb debug mode.
- Once i do " fastboot boot twrp.img " everything seems " okay " in the terminal, but the phone becomes stuck in fastboot mode logo image, it never actually boots into the twrp.
In a different tutorial, i replaced the "fastboot boot twrp.img" with " fastboot flash boot twrp.img ". This broke my phone i couldn't start the android or go the recovery mode, i couldn't leave fastboot mode unless to restart or to turn off the phone. I fixed this by " fastboot flash boot boot.img " that i had available in the platform tools folder.
I tried different twrp images:
TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Pie by mauronofrio
twrp-3.3.1-4-guacamole.img
Nothing seems to work, i don't know what else to try or what am i doing wrong.
I've been 8 hours around this so any help would be deeply appreciated.
Kind regards,
C666PO said:
Phone: OnePlus 7 Pro
Build number: Oxygen OS 10.0.3 GM21BA
Anndroid Version: 10
Model: GM1913
Hi all,
I received yesterday my Oneplus 7 Pro. My objective is to install nethunter fully rooted.
After looking the requirements in the offensive security website i noticed i need 3 things
TWRP
Magisk
DM-Verify
I started with TWRP watching different tutorials and comparing them but they are similar.
- Installed sdk platform tools and Minimal adb/fastboot ( tried both ways )
-unlocked the bootloader and enabled usb debug mode.
- Once i do " fastboot boot twrp.img " everything seems " okay " in the terminal, but the phone becomes stuck in fastboot mode logo image, it never actually boots into the twrp.
In a different tutorial, i replaced the "fastboot boot twrp.img" with " fastboot flash boot twrp.img ". This broke my phone i couldn't start the android or go the recovery mode, i couldn't leave fastboot mode unless to restart or to turn off the phone. I fixed this by " fastboot flash boot boot.img " that i had available in the platform tools folder.
I tried different twrp images:
TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Pie by mauronofrio
twrp-3.3.1-4-guacamole.img
Nothing seems to work, i don't know what else to try or what am i doing wrong.
I've been 8 hours around this so any help would be deeply appreciated.
Kind regards,
Click to expand...
Click to collapse
I have an almost identical problem to you.
except: my device is GM1910, I had a stock hydrogen OS, which has been converted to oxygen OS.
so far, I have tried twrp-3.3.1-0, 3.3.1-2, 3.3.1-3, 3.3.1-4, on oxygen OS version 10.0.2.GM21AA, 10.0.3.GM21AA, and 10.3.0.GM21AA, all would stuck at the fastboot mode logo screen
Rolling back to a lower version of oxygen OS, including version 9.5.1 and 9.5.7 causes my OP7P in bootloader mode no longer recognized by "fastboot devices", or even by "dmseg" as a usb device.
I received a suggestion of trying the latest TWRP 3.3.1-74 build, which I intend to try later tonight, but got not so optimistic about, seeing that you've experimented with TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
One observation I do like to make, is that android 9 is considered as Pie while android 10 was developed from android Q.
since your device is already android 10 at version 10.0.3, should you still use the Pie TWRP build?
OblixioN said:
One observation I do like to make, is that android 9 is considered as Pie while android 10 was developed from android Q.
since your device is already android 10 at version 10.0.3, should you still use the Pie TWRP build?
Click to expand...
Click to collapse
Hi OblixioN,
I tried the image with the Q at the end: TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio and it worked. I had no idea what the Q or Pie meant so your information just solved my problem. I assume it will work for you.
Huge thanks!
Thanks - worked for me as well!
Unfortunately I formated before getting to this solution, so rather unnecessary for me, but what I did was getting the unofficial twrp for guacamole here:
h-t-t-p-s://androidfilehost.com/?fid=4349826312261707787
(from this post: https://forum.xda-developers.com/oneplus-7-pro/development/recovery-unofficial-twrp-recovery-t3931322)
Then I booted to fastboot at ran
Code:
fastboot set_active a
fastboot boot .\twrp-3.3.1-75-guacamole-unified-Q-mauronofrio.img
fastboot set_active b
fastboot boot .\twrp-3.3.1-75-guacamole-unified-Q-mauronofrio.img
Now I could boot into twrp, it found all the internal data storage, and I could sideload
Code:
adb sideload .\twrp-installer-3.3.1-4-guacamole.zip
adb sideload .\Magisk-v20.3.zip
C666PO said:
I had no idea what the Q or Pie meant so your information just solved my problem.
Click to expand...
Click to collapse
It means if you are on Android Q, you need to use the TWRP version that supports Android Q.
Hey, I seem to have the same problem but how do u get it unstuck from the Fastboot Mode so I can try another version of TWRP?
OrionGiant said:
Hey, I seem to have the same problem but how do u get it unstuck from the Fastboot Mode so I can try another version of TWRP?
Click to expand...
Click to collapse
hey there.
So, first of, You restart it by pressing and holding volume up, down and power at the same time for 10+ seconds.
And second, try updating Oxygen OS to its latest version. It works for me now, just unpacked a new OnePlus 7 Pro, didn't work on Android 9, works on Android 10 latest update.
OrionGiant said:
Hey, I seem to have the same problem but how do u get it unstuck from the Fastboot Mode so I can try another version of TWRP?
Click to expand...
Click to collapse
While in fastboot , " fastboot boot twrp.img
Hi!
I'm on the latest official OxygenOS 11 and am having the exact same issue you hade above.
Tried everything mentioned above and the phone is still boot looping :'(
Any more tips?
SABMAN said:
Hi!
I'm on the latest official OxygenOS 11 and am having the exact same issue you hade above.
Tried everything mentioned above and the phone is still boot looping :'(
Any more tips?
Click to expand...
Click to collapse
I tried installing a new kernal and after that mine would go directly to bootloader, no matter what I did it went directly to bootload, thankfully fastboot was still active but using boot cmd into anything would fail,, ,I started my msm tool, and rebooted into edl and as soon as a com port became active on the MSM panel I hit start, and it took off running and did it's thing,
I think my issue had two reasons!
1. The boot.img file i used was from the earlier Oxygen update not the version i had just installed.
2. The phone encryption (but i doubt this!)
Anyway since nothing helped i erased the phone and restored it Now it's working again!
Motorola Moto G7 Play
Codename: CHANNEL
Boost Mobile Variant
Model No. XT1952-4
OBSOLETE THREAD
IMPORTANT NOTE:
At the time this thread was created, Motorola Mobility had not yet released the official stock Android 10 update for this variant of the CHANNEL. Because this variant has long since received the official Android 10 update, this thread is beneficial only for experimental or educational purposes. While you may certainly install RETAIL Android 10 firmware on the Sprint compatible xt1952-4, it is recommended always to install the latest official Android 10 firmware package released exclusively for this variant. Official Motorola stock firmware packages are available for the Boost Mobile/Sprint variant here https://mirrors.lolinet.com/firmware/motorola/channel/official/Sprint/
COMPATIBILITY:
Although this guide specifies the Boost Mobile (xt1952-4) variant of the CHANNEL, device owners have tested and confirmed that this Android 10 firmware is compatible with other variants/models. Namely, the MetroPCS xt1952-6 and the T-Mobile xt1952-T are confirmed. It is safe to assume that, because this is a RETAIL based official firmware build, compatibility should be universal for all region based retail models.
DISCLAIMER:
By proceeding further, you are assuming full responsibility for the operability and integrity of your device. Although this is an official firmware package, installation of firmware has an inherent risk of damaging your device or otherwise rendering it inoperable if the instructions are not followed carefully. Follow this detailed guide carefully and concisely and the installation should go smoothly. However, I am absolved of any liability in the event you break something. If you do mess something up, either myself or one of the many knowledgeable members herein will try to assist you.
OFFICIAL ANDROID 10:
For owners of the Moto G7 Play, it's no secret that the official Android 10 OTA update has already began rolling out to device owners in Brazil. As such, it probably will not be long before device owners in the US begin seeing a notification for the Android 10 update. In the meantime, for owners of the Boost Mobile variant (xt1952-4) who want to manually update to Android 10 by flashing the official Android 10 retail firmware package, I have put this simple guide together to assist you. In essence, to update manually, you will need to install the Android 10 firmware package via fastboot or RSD-Lite. This guide is premised upon the fastboot mode method. This Android 10 firmware is stable and may be used for your daily driver ROM. Look to the end of this guide for reported bugs.
BUILD INFO:
Android Version: Android 10
Build Region: RETAIL
Build No. QPY30.52-22
Kernel Version: 4.9.206-perf+
Radio Version: M632_41.178.01.156R
FSG Version: FSG-8953-25.163
Bootloader Version:2.1-channel_retail-315bc626c6-200423
System Version: 30.1.24.channel.retail.en.US
Build Date: April 13, 2020
Security Patch Level: April 1, 2020
ANDROID 10 UPDATE FEATURES:
• Optimized Fast Charging
• Bug Fixes for Battery Drain Issues
• Power Optimizations
• System-Wide Dark Theme
• Gesture-Based Navigation
• Privacy & Location Controls
• Sound Effects -- Stock Equalizer & Amplifier
• Smart Reply w/Messaging Apps
• Incognito Mode w/Google Maps
• Focus Mode
• Live Caption
• New Parental Controls
• New Moto Actions
INSTALLATION:
For those members who are not familiar with installing official firmware via fastboot mode, I will outline the exact steps below, including links to the files you'll need for the job. This guide requires a Windows PC or laptop, running Windows 7, 8.1 or 10 (32 or 64-bit). While fastboot can be used with other operating systems, this guide is outlined for Windows based systems only:
1. First, on your Windows PC or laptop, you will need to download and install the latest version of Motorola Device Manager, to ensure installation of up-to-date USB device drivers. Motorola Device Manager can be downloaded here: https://support.motorola.com/us/en/solution/MS88481
2. Next, download and install the latest fastboot and ADB utilities for flashing the firmware to your device. We will be using the Minimal ADB & Fastboot tools, version 1.4.3. On your PC or laptop, visit this link https://mega.nz/file/dVR3xCJL#GjcIXtNcCoB7R9DJtyqJ3dfOmeuGuPUvx6FKgp23yrc
3. Now download the official Android 10 retail firmware package from the Downloads section below;
4. Extract the contents of the firmware package zip you just downloaded to your Minimal ADB & Fastboot directory;
5. Boot your Moto G7 Play into AP Fastboot mode. With the device powered off, hold the power button along with the volume down button for around 8 seconds or until AP Fastboot mode appears on your device display;
6. Connect your device to your PC or laptop using the OEM supplied -- or quality equivalent -- USB to USB type C charging/syncing cable;
7. Open a command prompt in the path of your Minimal ADB & Fastboot directory. Execute the following command: fastboot devices
If your PC/laptop & device are properly synced, the command window will return an alphanumeric string synonymous with your device serial number. If you are not properly synced, try another USB syncing cable, change USB ports on your computer, or try reinstalling the USB device drivers.
**NOTES: by following these installation instructions, you will wipe your device of all userdata. Before proceeding further, make a backup of any important files and media.
Once you have confirmed proper syncing between your device and PC/laptop, execute the following fastboot commands, preferably in this order:
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 boot boot.img
fastboot flash logo logo.bin
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_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
fb oem config fsg-id boost
fb oem config carrier boost
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Upon reboot, your Boost Mobile Moto G7 Play will be running stock Android 10. During setup, select the "Use Mobile Data" option instead of using WiFi. This will allow your device to establish its initial 4G/LTE data connection on the Boost Mobile network. Once setup is complete, your cellular data, voice and messaging services should be functioning normally. Make a test phone call and send a test text message to confirm.
DOWNLOADS:
Android 10 Retail Firmware:
•Build No. QPY30.52-22 (April 1 SPL): https://mega.nz/file/YIZnwAAZ#17HH-vbEsbxQVPNLjvgNqdTHFI4Ow2ah6SNC4Nnw9ec
•Build No. QPYS30.52-22-2 (June 1 SPL): https://mega.nz/file/lB5gkaqK#BD-r7dSTw8dgZAfI90pJq7LB_XJvqcvSVshXbLo-yic
Android 9 Pie Stock Firmware:
• Official Firmware Builds: https://mirrors.lolinet.com/firmware/moto/channel/official/Sprint/
BUGS:
• PRL/Domestic Roaming:
When roaming outside of the home network, the device may give a mobile IP registration response error (MIP Error 67-- Mobile Node Failed Authentication), and the cellular signal may become unstable. This is most likely due to the lack of an integrated PRL (Preferred Roaming List) provisioning service within the retail firmware. I am looking for a workaround: possibly implementing the Boost Mobile radio firmware from Android 9, or including the SprintDM mobile provisioning service as an add-on;
• Gesture/Navigation Features:
As XDA Member @JohnSmith8786 has pointed out, some of the native Gesture Navigation features in the RETAIL Android 10 firmware are somewhat unstable and buggy at times. This bug has been reported to Motorola Mobility via official bug report. Since this issue does not appear to be specific to a particular variant/model, and has been reported on various different models, this issue is likely unique to the RETAIL Android 10 firmware builds, and will likely be resolved by stability improvements/bug fixes in a future OTA(s).
Please report any bugs or instabilities in comments below. Also, please provide confirmation regarding compatibility of this Android 10 firmware on specific Moto G7 Play models. In theory, this firmware should work on any model with an unlocked bootloader. As all Android enthusiasts, modders and devs know, confirmation is always better than theory.
Could it work on XT1952-6 from MetroPCS?
mickem said:
Could it work on XT1952-6 from MetroPCS?
Click to expand...
Click to collapse
Can confirm working on XT1952-6 & XT1952-T
I tested stock AndroidQ for XT1952-2 ATTMX QPYS30.52-22-2 from lollinet mirrors on MPCS XT1952-6 and flashed with RSDLite. Until now everything works fine. Still testing.
mickem said:
I tested stock AndroidQ for XT1952-2 ATTMX QPYS30.52-22-2 from lollinet mirrors on MPCS XT1952-6 and flashed with RSDLite. Until now everything works fine. Still testing.
Click to expand...
Click to collapse
I used RETAIL, only issue is the baked in gesture navigation gets squirrely sometimes
JohnSmith8786 said:
Can confirm working on XT1952-6 & XT1952-T
Click to expand...
Click to collapse
Thank you very much. I will add that to my OP heading. Yeah I've noticed some slight buggy behavior on the RETAIL Android 10 gesture navigation features too. Motorola Mobility has been notified of this issue, so perhaps a future OTA will fix this.
So this shouldn’t affect my modem or data connection on the Sprint Nationwide Network for Boost?
GRiZZ91 said:
So this shouldn’t affect my modem or data connection on the Sprint Nationwide Network for Boost?
Click to expand...
Click to collapse
Correct. Flashing this firmware to a device active on the Boost Mobile network will continue to function normally. I have noticed some buggy behavior when roaming outside of the home network. Other than that, your device should function just as if you were using the Sprint firmware build.
Sorry I was rusty
Does anyone know if in this Android version call recording goes back to our Motorola? On Android 9 I had to root phone for enable call recording. How is it now?
For those with the Sprint/Boost Mobile variant of the xt1952-4, the latest OTA is live, bringing the Build No. to QPYS30.85-18-6 and the security patch level to October 1. For anybody needing it, I will try to post a link for the entire firmware package this weekend. Here is a link to the latest full firmware package for the Sprint/Boost Mobile xt1952-4 https://mega.nz/file/SmAEwRZL#M4KP8hHHEtBw5fOtHGRuGfDV8F0SUkFENVGctzJagFw
Viva La Android said:
For those with the Sprint/Boost Mobile variant of the xt1952-4, the latest OTA is live, bringing the Build No. to QPYS30.85-18-6 and the security patch level to October 1.
Click to expand...
Click to collapse
Were you able to get Magisk running and the device rooted?
I had the Lenovo rescue tool unbrick my phone and it 30.85-18-11 and I can't get Magisk to stay on, let alone get it rooted.
veryspecialagent said:
Were you able to get Magisk running and the device rooted?
I had the Lenovo rescue tool unbrick my phone and it 30.85-18-11 and I can't get Magisk to stay on, let alone get it rooted.
Click to expand...
Click to collapse
I have a patched boot.image that will root your device.
Viva La Android said:
Ill have a patched boot.image that will root your device.
Click to expand...
Click to collapse
Correction I mean a patched recovery image
Viva La Android said:
You can I stall it via TWRP or fastboot
Click to expand...
Click to collapse
Let me make sure I am not misunderstanding. You want to run official stock Android 10 and root with Magisk, correct? If so, you can certainly do that, but since the Moto G7 Play does not have a boot-ramdisk, you ate forced to jump through some hoops to get Magisk installed. You are much better off flashing.offiicial Lineage OS 18.1 (Android 11) and installing Magisk using the typical boot image patching method -- the normal method. LineageOS 18.1 has a boot-ramdisk. If you do not like LineageOS, there are many official Android 11 based custom ROMs available for the CHANNEL. And a few Android 12 custom ROMs. They all include boot-ramdisk.
Viva La Android said:
Let me make sure I am not misunderstanding. You want to run official stock Android 10 and root with Magisk, correct? If so, you can certainly do that, but since the Moto G7 Play does not have a boot-ramdisk, you ate forced to jump through some hoops to get Magisk installed. You are much better off flashing.offiicial Lineage OS 18.1 (Android 11) and installing Magisk using the typical boot image patching method -- the normal method. LineageOS 18.1 has a boot-ramdisk. If you do not like LineageOS, there are many official Android 11 based custom ROMs available for the CHANNEL. And a few Android 12 custom ROMs. They all include boot-ramdisk
Click to expand...
Click to collapse
I've never bothered with custom ROMs. My interests with rooted phones are for practicing forensics and pentesting.
I'm downloading the latest Lineage and will try it that way. I'll report back when completed or I run into issues.
veryspecialagent said:
I've never bothered with custom ROMs. My interests with rooted phones are for practicing forensics and pentesting.
I'm downloading the latest Lineage and will try it that way. I'll report back when completed or I run into issues.
Click to expand...
Click to collapse
Cool. Yeah let me know. Follow the install instructions for LOS 18.1 directly from the Lineage WiKi. The install is not standard TWRP like most Lineage builds. This has to be done using.adb sideload in TWRP mode with a PC.
That should have posted 2 hours ago.
This is what I f'ing loathe about this process because it happens virtually EVERY time regardless of the device or OS or mod that I'm doing.
The first thing I did was make sure sdk tools were updated. There were updates for Android 6 and 10, as well as two new modules to install. It took about a half hour to go through them all, but everything is updated.
Downloaded LoS, latest version, and the recovery image.
Go to the first step on the LoS install, which is to sideload a specific zip file. kay...
-reboot into bootloader, then from there to recovery
-adb sideload <the file>
-on computer: error:closed
-on phone: Error 21, footer is wrong
This nearly ALWAYS happens, and I have yet to find a fix. I google for an answer, keeping results to just within the last year, and someone on Reddit had suggested a fix that worked for the poster. His problem was that he was in stock recovery. He needed to be in LoS recovery.
I think "well, they give you a recovery image separate with the OS download, maybe it's to boot with, like TWRP." So I boot into the bootloader and try to fastboot boot <lineage recovery.img>..........and it just starts up normal. I go to settings and check the build, and it's still the Android 10 version I started with. Tried it again, same results.
So then I get the bright idea to stay where I'm at in stock OS and adb reboot <lineage recovery.img>
Now, on my phone it's in a weird Android Recovery screen. "Can't load Android system. Your data may be corrupted. If you continue to get this message...." Then it gives me two options: Try again or factory reset.
Well, my mama didn't raise no quitter, so I hit Try Again. It goes to the black screen with "N/A" on it (which is what it would do back when I had this thing rooted and everything was peachy until I forgot the lock screen pattern), but then I get that error message again.
I'm going to factory reset and see what happens. Anyone with a solution, feel free to chime in anytime.
Factory reset complete. Now I'm.....still in Android 10, build QPYS30.85-18-11.
Lol, just to clarify where we're at: The process I'd "be much better doing" took three hours to implement just half of the first step, and it led to me having to factory reset because it wouldn't boot.
We have stock factory boot images, I'm only posting the latest builds.
The rooted android 10 images are rooted with latest Magisk 20.4
The rooted 11 images are rooted with latest Magisk Canary 4e0a3f5e
You will still need to install the Magisk Manager to use root. Root will not work without it.
You HAVE to be bootloader unlocked in order to flash a boot image, meaning these Verizon images are likely useless but google does say it covers extra carriers too. The 11 images seem to be unified in terms of Verizon and other carriers, but do NOT cover
Make sure to match the boot image build number to your own build number. (Settings/about/android version/build number)
-
Android 11 - RP1A - NOV - Stock Factory Boot
Stock Boot Image - Global - rp1a.201105.002 - All carriers except EMEA, SG, and IN
AFH
Old Stock Boot Versions
Android 11 - RP1A - Oct - Stock Factory Boot
Stock Boot Image - Global - rp1a.201005.006 - All carriers except EMEA, SG, and IN
AFH
Android 11 - RP1A - Sept - Stock Factory Boot
Stock Boot Image - Global - rp1a.200720.011 - All carriers except EMEA, SG, and IN
AFH
Android 11 Beta R3 - RPB3 - Stock Factory Boot
Stock Boot Image - Global - rpb3.200720.005
AFH
Android 10 - QD4A - Aug - Stock Factory Boot
Stock Boot Image - Global - QD4A.200805.003
AFH
Stock Boot Image - VZW/JP - QD4A.200805.001
AFH
--
Android 11 - RP1A - Nov - Rooted Factory Boot
Rooted Boot Image - Global - rp1a.201105.002 - All carriers except EMEA, SG, and IN
AFH
Old Rooted Boot Versions
Android 11 - RP1A - Oct - Rooted Factory Boot
Rooted Boot Image - Global - rp1a.201005.006 - All carriers except EMEA, SG, and IN
AFH
Android 11 - RP1A - Sept - Rooted Factory Boot
Rooted Boot Image - Global - rp1a.200720.011 - All carriers except EMEA, SG, and IN
AFH
Android 11 Beta R3 - RPB3 - Rooted Factory Boot - Thanks to @Xenanthropy !
Rooted Boot Image - Global - rpb3.200720.005
AFH
Android 10 - QD4A - Aug - Rooted Factory Boot
Rooted Boot Image - Global - QD4A.200805.003
AFH
Rooted Boot Image - VZW/JP - QD4A.200805.001
AFH
--
For root on Android 11, you need the latest Magisk Canary that can be found here
Steps to proceed:Unlock Bootloader
Ensure you are on latest android version
Ensure you have the latest versions of adb/fastboot tools
Download the desired boot image and place where adb tools have access
Connect phone to pc and open terminal/cmd prompt to where you put that desired boot image
On the phone:
Go to Settings/About and scroll to the bottom
tap 'Build Number' 7 times
type password/pincode if you have it otherwise don't worry
Go to Settings/System/Developer Options
Enable OEM Unlocking
Enable USB Debugging
Accept USB Debugging prompt on phone - If this doesn't pop-up by itself, unplug phone and plug back in to pc and then it should pop-up, HAVE to allow access..
On pc type:
adb reboot bootloader
fastboot flashing unlock
On phone:
Volume up/down to YES and press power button to proceed with bootloader unlock and wiping data partition
fastboot reboot
--
Flash Boot Image on Bootloader Unlocked Device
Ensure you are on an android version matching the boot image you want to download(Check Settings/About - Click on Android Version - Look at 'Build Number')
Download desired boot image on pc and place it where somewhere you have adb/fastboot access
Connect phone to pc and open terminal/cmd prompt to where you put that desired boot image
Reboot phone to bootloader
on pc type:
fastboot flash boot desired-bootimage-name.img
fastboot reboot
--
To Pass CTS w/root- Courtesy of @quangtran1
After flashing rooted kernel:
In Magisk Manager, install the MagiskHide Props Config module;
Execute command 'su -c props' using a terminal app on the phone;
Choose 'Force BASIC key attestation' option from menu;
Choose from fingerprints list, it should default to Pixel 4a, just Confirm
Reboot
?????
Profit
--
If you want or need to make your own rooted boot image
You need the latest Magisk Manager installed.
Stable Magisk for Android 10, maybe 11 | Canary Magisk for Android 11 for sure.
Download the desired Stock Boot Image from here or extract it yourself from Google's Factory Image zip.
Copy to sdcard of your device.
Open Magisk Manager, click the first 'Install' button next to 'Magisk is up to date'.
Click 'Install'.
Click 'Select and Patch a File'
Find and select the desired Stock Boot Image.
You will find the magisk patched, Rooted Boot Image in the sdcard/Download folder titled 'magisk_patched.img'
Copy that to your pc and flash your pixel 4a from fastboot or copy to the phone and flash with exkm/fkm/etc.
Reboot
Install Magisk Manager
Enjoy being rooted.
XDA:DevDB Information
[Stock/Rooted Boot Images] Pixel 4a [NOV 02], Tool/Utility for the Google Pixel 4a
Contributors
HolyAngel
Source Code: https://developers.google.com/android/images#sunfish
Version Information
Status: Snapshot
Created 2020-08-24
Last Updated 2020-11-02
thank you very much good man. if you can do that also for the beta version it would be great.
https://developer.android.com/preview/download#
@dark8899
Ah I had forgotten about the beta, thanks! And added!
Before I mess up my phone, Do I just run "adb reboot bootloader" then "fastboot flashing unlock" then "fastboot flash boot [Android11RootPatch].img" then "fastboot reboot", set up the phone, install magisk?
I haven't rooted in a while and I'm also just a user not a developer.
@DJesri13
Yep that would pretty much do it exactly.
Hmm, not seeming to work on mine... I tried both flashing my own acquired (and patched with magisk) boot.img as well as your patched boot, and neither seem to want to boot when I reboot, it just boots back into fastboot and says "reason: no valid slots to boot" (or something to that effect, i've already patched the original boot.img back) Tried flashing the patched img to both slot A and B, nothing seemed to work. Got the furthest with my own patched image, the google logo would turn to the G and act like it was loading but it continued to "load" for a good 10 minutes so I just gave up.
Xenanthropy said:
Hmm, not seeming to work on mine... I tried both flashing my own acquired (and patched with magisk) boot.img as well as your patched boot, and neither seem to want to boot when I reboot, it just boots back into fastboot and says "reason: no valid slots to boot" (or something to that effect, i've already patched the original boot.img back) Tried flashing the patched img to both slot A and B, nothing seemed to work. Got the furthest with my own patched image, the google logo would turn to the G and act like it was loading but it continued to "load" for a good 10 minutes so I just gave up.
Click to expand...
Click to collapse
It also isn't working for me. It won't let me flash the boot image. I also tried my own image patched with magisk.
Edit: I all my attempts to flash the boot partition failed so I can still boot the OS
@DJesri13
@Xenanthropy
Sounds like possibly not flashing correctly or you weren't already on the latest firmware. You need to be on the firmware matching the boot.img. This is pulled directly from the factory image. Try flashing that first and then this image and see what happens.
For flashing this after flashing same firmware on android 10 for instance:
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
make sure you're flashing to 'boot', the 3rd word in the command. if you don't put that it won't flash or if you put something other than 'boot' you could have other issues.. Should still be fixable by flashing the factory images.
HolyAngel said:
@DJesri13
@Xenanthropy
Sounds like possibly not flashing correctly or you weren't already on the latest firmware. You need to be on the firmware matching the boot.img. This is pulled directly from the factory image. Try flashing that first and then this image and see what happens.
For flashing this after flashing same firmware on android 10 for instance:
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
make sure you're flashing to 'boot', the 3rd word in the command. if you don't put that it won't flash or if you put something other than 'boot' you could have other issues.. Should still be fixable by flashing the factory images.
Click to expand...
Click to collapse
I just checked my build version (i'd upgraded to android 11 beta via the ota update by signing up for the beta) and it matches the boot img, RPB3.200720.005.
When I run "fastboot flash boot root.boot.sunfish-rpb3.200720.005.img" it flashes it properly, but upon rebooting it just reboots back into fastboot stating that there was an error. It wouldn't boot on my custom patched boot.img either so i'm not sure what the issue is here.
My current steps were:
1. get phone, immediately unlock bootloader
2. opt-in to android 11 beta, check for updates and upgrade to the beta (rpb3.200720.005)
3. extracted boot.img from the Android 11 beta OTA update, patch it with magisk and attempt to flash (doesn't work, google logo just loads indefinitely)
4. Try flashing your patched boot.img, which results in the phone immediately rebooting and stating an error with the boot slot
If i'm doing something wrong, i'm not sure what it is. I can provide more details if necessary
Xenanthropy said:
I just checked my build version (i'd upgraded to android 11 beta via the ota update by signing up for the beta) and it matches the boot img, RPB3.200720.005.
When I run "fastboot flash boot root.boot.sunfish-rpb3.200720.005.img" it flashes it properly, but upon rebooting it just reboots back into fastboot stating that there was an error. It wouldn't boot on my custom patched boot.img either so i'm not sure what the issue is here.
My current steps were:
1. get phone, immediately unlock bootloader
2. opt-in to android 11 beta, check for updates and upgrade to the beta (rpb3.200720.005)
3. extracted boot.img from the Android 11 beta OTA update, patch it with magisk and attempt to flash (doesn't work, google logo just loads indefinitely)
4. Try flashing your patched boot.img, which results in the phone immediately rebooting and stating an error with the boot slot
If i'm doing something wrong, i'm not sure what it is. I can provide more details if necessary
Click to expand...
Click to collapse
Ah ok gotcha. it sounds like you did everything right too. Might need a magisk update or something else for that then. May remove the beta root image then..
Are you currently running the Android 11 beta? It would be nice to know if someone was able to get the beta rooted properly so we could see what steps they took.
When I try to flash the boot img I get
FAILED (remote: Failed to write to partition Not Found)
Should I try to flash to the boot slot?
EDIT: I flashed and it went through but now it just boots to the bootloader, flashing the stock boot img doesn't fix it. Ill reflash the factory image and again later maybe
DJesri13 said:
When I try to flash the boot img I get
FAILED (remote: Failed to write to partition Not Found)
Should I try to flash to the boot slot?
EDIT: I flashed and it went through but now it just boots to the bootloader, flashing the stock boot img doesn't fix it. Ill reflash the factory image and again later maybe
Click to expand...
Click to collapse
i am also in the same boat here. unlocked and then fastboot flash boot root.boot.sunfish-qd4a.200805.003.img (to slot a)
it booted to Google logo then restarted into bootloader fastboot mode.
it says no valid slot to boot. see attached image
xxTECRAxx said:
i am also in the same boat here. unlocked and then fastboot flash boot root.boot.sunfish-qd4a.200805.003.img (to slot a)
it booted to Google logo then restarted into bootloader fastboot mode.
it says no valid slot to boot. see attached image
Click to expand...
Click to collapse
Yep, I was getting the same results using the beta firmware and boot img provided and my own as well as the Augusta firmware with the provided images and my own that I pulled from the factory image and ones I patched.
Anyone know if it is possible to sideload magisk as a zip?
i relfashed the factory image, then dropped magisk into phone with windows explorer. installed magisk then redid the fastboot flash boot root.boot.sunfish-qd4a.200805.003.img and she just booted up. unsure if i have root though
EDIT: i have root!
---------- Post added at 11:23 PM ---------- Previous post was at 11:03 PM ----------
DJesri13 said:
Yep, I was getting the same results using the beta firmware and boot img provided and my own as well as the Augusta firmware with the provided images and my own that I pulled from the factory image and ones I patched.
Anyone know if it is possible to sideload magisk as a zip?
Click to expand...
Click to collapse
if you're stuck inside fastboot, then reflash the factory image from this file sunfish-qd4a.200805.003-factory-fac7c08d.zip using the included "flash-all.bat". once that completes, boot phone back up and go to settings to enable developer options. then enable USB debugging and finally transfer the magisk.apk into the phone using windows explorer. once all this is done, start over at the top:
adb reboot bootloader
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
fastboot reboot
get paid
xxTECRAxx said:
i relfashed the factory image, then ....
.....
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
fastboot reboot
get paid
Click to expand...
Click to collapse
This is for android 10 or 11 beta?
Zlatty said:
This is for android 10 or 11 beta?
Click to expand...
Click to collapse
10
Can anyone confirm if Rooted 10 + Magisk passes SafetyNet on the 4a?
You need to patch boot-s by latest canary magisk, especially if it`s BETA 11.
https://github.com/topjohnwu/magisk_files/raw/canary/app-debug.apk
Can someone help me out, I don't understand why I can't boot up after flashing the stock or the batched boot image. My bootloader says slot a and that's the one I flashed to. I tried the beta but right now I'm back on Android 10 and neither will let me boot up.
Hi there,
I don't know how first installation of Lineage (and probably other Android tastes) went, though I had some issues I would like to share for people trying to install another OS then factory setup in the future.
I bought a new fresh G100 four days ago and set it up with only wifi, no sim, just to enlock and install LOS.
As I read on the forums, it normally is taking 2-3 days before the button in developer settings is active and not greyed out anymore, though for me nothing changed. After three days I did a full reset and set it up with only wifi, no sim, and the button in developer settings was active.
I used the following drivers and SDK:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Drivers | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
I used the following guides for unlocking:
Sign in to Motorola - Motorola Mobility LLC
Sign in to Motorola
motorola-global-portal.custhelp.com
Info about nio variants | LineageOS Wiki
wiki.lineageos.org
After unlocking in fastboot I did not reboot, though emmediately flashed the Lineage recovery.
The recovery from the LOS website was not booting so I installed TWRP:
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-2-for-moto-edge-s.4303199/
This recovery was booting and there I flashed the copy-partitions-xxxx.zip and emmediately after I installed LOS.
The procedure above was not working for me as I ended up with a phone only booting in fastboot.
So what I did afterwards was the following:
Phone was already unlocked, so installed the latest firmware following the procedure here:
https://www.getdroidtips.com/firmware-moto-g100-xt2125-4/
So, downloading latest firmware flash files, extracting to a folder with fastboot etc.. in it, and entering the commands to flash the firmware.
After that I head all my partitions back.
Then I installed latest LOSrecovery.img from:
index - powered by h5ai v0.29.2 (https://larsjung.de/h5ai/)
index - powered by h5ai v0.29.2 (https://larsjung.de/h5ai/)
build.lolinet.com
To be sure to have it in boot_a and boot_b I did:
fastboot flash boot_a <recovery.img>
fastboot flash boot_b <recovery.img>
This was working, so using adb sideload I now installed:
adb sideload copy-partitions-20220613-signed.zip
and the latest LOS:
adb sideload lineage-19.1-20220903-nightly-nio-signed.zip
(To use adb sideload you can go to "apply update" in LOS recovery and then "apply from ADB")
A working system, yes!
My questions at the moment;
- Is the official LOS recovery indeed not working, or am I doing something wrong?
When the above is true:
- I can not use the LOS update functionality as it is not possible to switch off updating recovery in settings?
- I have to disable LOS update and use adb sideload for updating?
In general:
- Is it possible to lock the bootloader again after the setup above, or do I have to keep it unlocked? Coming from Oneplus and there I could lock it again.
Hope it helps and am curious if the experiences from other people are the same.
For your last question, no, you can't relock the bootloader while on a custom rom for this device.
Today I tried again to install the LOS recovery from the official download page https://download.lineageos.org/nio
So in fastboot I did:
fastboot flash boot_a lineage-19.1-20220903-recovery-nio.img
fastboot flash boot_b lineage-19.1-20220903-recovery-nio.img
For your information; installation went without any issues. Recovery working fine, LOS booting fine, no issues.
So what went wrong the first time I do not exactly know, though I think the trouble came because of not rebooting after installation of LOS recovery and doing a full reset from within recovery to remove encryption.
Someone who can answer that?
That's it for now; a new happy G100 user!