Database Info

[Q&A] [Recovery] Unofficial CWM - 6.0.5.0 - peregrine

Q&A for [Recovery] Unofficial CWM - 6.0.5.0 - peregrine
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Recovery] Unofficial CWM - 6.0.5.0 - peregrine. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

black screen cwm
EDIT: SOLVED (with somcom's recovery toolkit http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710 /please feel free to delete this post which now only serves as proof of my incompetence)
........................................................................
hello, i've just bought a moto lte (uk) xt1039
have successfully unlocked bootloader
trying to flash recovery via fastboot but having issues
seems to flash ok but then when rebooting into recovery device show (nearly) black screen with some white flickers.
i can boot into bootloader and access via fastboot on windows 7
i downloaded recovery and rom on the moto (before erasing partitions and being unable to boot) and have copies on laptop too.
what have i done? how can i get recovery working to install a rom?
thanks so much for your help, sorry I couldn't find answer here (I tried!
C:\Users\prosody\moto g\RECOVERY>fastboot devices
TA003002KC fastboot
C:\Users\prosody\moto g\RECOVERY>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113(*)
(bootloader) product: peregrine
(bootloader) secure: yes
(bootloader) hwrev: 0x82D0
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: TA003002KC
(bootloader) cid: 0x0007
(bootloader) channelid: 0x49
(bootloader) uid: B6C1B20515000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Nov 9 17:24:15 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/peregrine_o2gb/peregrine:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.56/52:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.56.peregrine_o
(bootloader) ro.build.version.full[1]: 2gb.o2gball.en.GB
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gc20375a-00001-g804
(bootloader) kernel.version[1]: 2017 ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .7 (GCC) ) #1 SMP PREEMPT Tue Aug 5 22:4
(bootloader) kernel.version[3]: 2:49 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.11-0-gcff5797
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: o2gb
all: listed above
finished. total time: 0.100s
C:\Users\prosody\moto g\RECOVERY>fastboot erase system -w
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.078s]
erasing 'userdata'...
OKAY [ 0.243s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.018s]
erasing 'cache'...
OKAY [ 0.070s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.021s]
finished. total time: 0.449s
C:\Users\prosody\moto g\RECOVERY>fastboot erase boot
erasing 'boot'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.113s]
finished. total time: 0.117s
C:\Users\prosody\moto g\RECOVERY>fastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.118s]
finished. total time: 0.122s
C:\Users\prosody\moto g\RECOVERY>fastboot flash CWM-6.0.5.0-peregrine.img
unknown partition 'CWM-6.0.5.0-peregrine.img'
error: cannot determine image filename for 'CWM-6.0.5.0-peregrine.img'
C:\Users\prosody\moto g\RECOVERY>fastboot flash recovery CWM-6.0.5.0-peregrine.i
mg
target reported max download size of 536870912 bytes
sending 'recovery' (7752 KB)...
OKAY [ 0.311s]
writing 'recovery'...
OKAY [ 0.426s]
finished. total time: 0.746s
C:\Users\prosody\moto g\RECOVERY>fastboot reboot
rebooting...
finished. total time: 0.006s
C:\Users\prosody\moto g\RECOVERY>

Blinking stripes when trying recovery
I just wanted to add that I too have trouble booting into CWM recovery. The screen goes black and some flashing stripes appear accross the screen before it goes completely black. Basically it's unusable...
I can hold the power button and the phone reboots as normal.
The bootloader is unlocked and the phone is rooted.
I hope this information is useful in some way and some fix can be found.
(I have the same problem with TWRP by the way.)
I'm so sorry, you can all ignore what I wrote above.
I fixed it the same way as noted in the post above...
Cheers,

I flashed the CWM recovery as described but when I try to enter it I only get a black screen. I also tried the non-touch version of the recovery but that didn't make any difference. Ideas!?
*edit*
Followed the instructions above and got stuck in the bootloader. Then somehow managed to flash CWM using the Toolkit mentioned above.
C:\Users\prosody\moto g\RECOVERY>fastboot erase boot
Click to expand...
Click to collapse
What's with the flashboot commands posted by prosodyspeaks, I guess that erasing the boot was somehow responsible for being unable to boot the system!?

Every time I create a recovery to my external SD card, it hangs at "Generating md5 sum" but works fine when its in the internal storage. I always have to restart my phone manually. Is there a fix to this, or can I just make a recovery to my internal storage and move the entire recovery folder to my external SD card?

Will this work this the Lollipop 5.1 bootloader?

SJHacker said:
Will this work this the Lollipop 5.1 bootloader?
Click to expand...
Click to collapse
I have 6.0.5.1 installed on my XT1039 Peregrine and it works, i downloaded it from here h t t p ://builder.unstableapps.com/#/latest/clockworkmodrecovery/peregrine .
Anyway you can always test before flash using
Code:
fastboot boot [B]HERE_YOUR_RECOVERY_IMG[/B]
.
If it boots and works then you flash.
PS: I use the CWM linked above, there is only one issue: when you flash it and boot the recovery screen flickers and shows an horizontal line that goes from up to bottom....but everything seems working.
If i simply boot the recovery image without flashing there are no graphical issues.

Try this
The easiest method to install CWM without pc:
1. Download the file on your phone (I moved it to the internal storage)
2. Download Flashify from Play Store
3.Go to "flash" section and select "flash recovery image"
4. Click on "choose a file"
5. Choose the downloaded file
6. Click on this file and select "yup"
7. CWM should be now installed
I have tried this method with my device (Motorola Moto G 4G) and everyrhing went well.

_Immanuel_ said:
I have 6.0.5.1 installed on my XT1039 Peregrine and it works, i downloaded it from here h t t p ://builder.unstableapps.com/#/latest/clockworkmodrecovery/peregrine .
Anyway you can always test before flash using
Code:
fastboot boot [B]HERE_YOUR_RECOVERY_IMG[/B]
.
If it boots and works then you flash.
PS: I use the CWM linked above, there is only one issue: when you flash it and boot the recovery screen flickers and shows an horizontal line that goes from up to bottom....but everything seems working.
If i simply boot the recovery image without flashing there are no graphical issues.
Click to expand...
Click to collapse
Thanks!

Does latest version supports the ext. sdcard used as internal in a marshmallow rom? Thx

[Q] D820E hammerhead dead emmc?

friend brought me a d820e to look at, says it happens after OTA (sounds weird...)
my analysis as follows:
1. bootloader stays locked after reboot, tried "fastboot oem unlock" several times
2. flashing factory image, custom recoveries, cache, etc... are failed
Code:
sending 'recovery' (9434 KB)...
OKAY [ 0.515s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.696s
.
3. factory reset/date wipe/cache wipe results in:
Code:
Can't mount /cache/etc...
i could try to flash with LG flashtool but i'm not sure which TOT i should use, don't want to brick the device even more.
any other suggestions?
device info:
Code:
tools>fastboot.exe getvar all
(bootloader) max-download-size: 0x40000000
(bootloader) version-hardware: rev_11
(bootloader) version-baseband: M8974A-2.0.50.2.22
(bootloader) version-bootloader: HHZ12d
(bootloader) version-cdma: N/A
(bootloader) variant: hammerhead D820(E) 16GB
android system recovery LRX22C

sh33z0r said:
1. bootloader stays locked after reboot, tried "fastboot oem unlock" several times
Click to expand...
Click to collapse
eMMC is dead.

anything to do or just rma?

sh33z0r said:
anything to do or just rma?
Click to expand...
Click to collapse
If it's still in warranty, RMA. If it isn't, send it to LG and pay for repair (motherboard swap).

Moto G 1st Gen Bootloop

Hi all Phone is stuck on a bootloop with a white motorola logo.
I've since had a mess and i think ive made it worse!!
I've unlocked the Bootloader & since tried to reflash a stock image but nothings working.
Where am i going wrong????????
My phones a 1st gen XT1039 (It was on Tesco) i can access recovery where it says the device is UNLOCKED Status code 3,Battery OK
but once i try and flash using mflashbootv2 using firmware
(Moto_G_LTE_XT1039)_TESCO-GB_4.4.4_KXB21.14-L1.46_cid7_CFC_1FF.xml
& I've tried
XT1039_PEREGRINE_TESCOGB_5.1_LPBS23.13-17.6-1_cid7_CFC.xml
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
I'm just getting failed to erase partitions etc

C:\Users\Dave\Desktop\mfastboot-v2>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 5.024s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.301s
C:\Users\Dave\Desktop\mfastboot-v2>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 5.097s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 10.952s
C:\Users\Dave\Desktop\mfastboot-v2>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 5.057s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.082s
C:\Users\Dave\Desktop\mfastboot-v2>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 5.374s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.784s
C:\Users\Dave\Desktop\mfastboot-v2>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 5.374s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.786s

if you're bootloader is unlocked then just flash TWRP Recovery and flash custom ROMs.

jbanti said:
if you're bootloader is unlocked then just flash TWRP Recovery and flash custom ROMs.
Click to expand...
Click to collapse
I've tried flashing via TWRP.
I've followed this guide
Downloaded ABD FASTBOOT and extracted into a folder on my desktop i've also downloaded twrp-3.2.3-0-peregrine.img and put that in the same folder but renamed it recovery.img
I then shift right click > open command window here
I then type
fastboot devices
TA00303RVM fastboot
Then
fastboot flash recovery recovery.img but all i'm getting is errors??
adb-fastboot-latest_win_linux>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (8332 KB)...
OKAY [ 5.319s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.411s
I've never flashed anything before am i missing something? also the phone continues to try to boot up when i dont put it into recovery mode and is only listed under device manager as Qualcomm HS-USB QDLoader 9008

Bettz said:
I've tried flashing via TWRP.
I've followed this guide
Downloaded ABD FASTBOOT and extracted into a folder on my desktop i've also downloaded twrp-3.2.3-0-peregrine.img and put that in the same folder but renamed it recovery.img
I then shift right click > open command window here
I then type
fastboot devices
TA00303RVM fastboot
Then
fastboot flash recovery recovery.img but all i'm getting is errors??
adb-fastboot-latest_win_linux>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (8332 KB)...
OKAY [ 5.319s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.411s
I've never flashed anything before am i missing something? also the phone continues to try to boot up when i dont put it into recovery mode and is only listed under device manager as Qualcomm HS-USB QDLoader 9008
Click to expand...
Click to collapse
you need to unlock the bootloader for flashing recovery and roms.

jbanti said:
you need to unlock the bootloader for flashing recovery and roms.
Click to expand...
Click to collapse
It's saying the bootloaders unlocked

Typed fastboot oem get_unlock_data
Desktop\adb-fastboot-latest_win_linux>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 3A95920045195889#54413030333033
(bootloader) 52564D00585431303339000000#749B
(bootloader) 3CCD3CF018E29770D1AC24AF8A1DADA
(bootloader) D62E1#8E6F800615000000000000000
(bootloader) 0000000
type the following in on the Motorola website
3A95920045195889#5441303033303352564D00585431303339000000#749B3CCD3CF018E29770D1AC24AF8A1DADAD62E1#8E6F8006150000000000000000000000
to generate the unique key
reboot phone back into recovery mode then type the following in adb fastboot
Desktop\adb-fastboot-latest_win_linux>fastboot devices
TA00303RVM fastboot
C:\Users\Desktop\adb-fastboot-latest_win_linux>fastboot oem unlock BZ5CL4FNM4KHWNGZPWCG
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Device already unlocked!
FAILED (remote failure)
finished. total time: 0.019s
What do i try now?????

Bettz said:
Typed fastboot oem get_unlock_data
Desktop\adb-fastboot-latest_win_linux>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 3A95920045195889#54413030333033
(bootloader) 52564D00585431303339000000#749B
(bootloader) 3CCD3CF018E29770D1AC24AF8A1DADA
(bootloader) D62E1#8E6F800615000000000000000
(bootloader) 0000000
type the following in on the Motorola website
3A95920045195889#5441303033303352564D00585431303339000000#749B3CCD3CF018E29770D1AC24AF8A1DADAD62E1#8E6F8006150000000000000000000000
to generate the unique key
reboot phone back into recovery mode then type the following in adb fastboot
Desktop\adb-fastboot-latest_win_linux>fastboot devices
TA00303RVM fastboot
C:\Users\Desktop\adb-fastboot-latest_win_linux>fastboot oem unlock BZ5CL4FNM4KHWNGZPWCG
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Device already unlocked!
FAILED (remote failure)
finished. total time: 0.019s
What do i try now?????
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g/general/guide-unlock-bootloader-root-recovery-t3418432
follow this tutorial.

jbanti said:
you need to unlock the bootloader for flashing recovery and roms.
Click to expand...
Click to collapse
jbanti said:
https://forum.xda-developers.com/moto-g/general/guide-unlock-bootloader-root-recovery-t3418432
follow this tutorial.
Click to expand...
Click to collapse
I get stuck at the following
Download the latest SuperSU flashable zip from
Copy it to your phone.
I can't get access to my phone it doesnt show up on my pc devices etc

Bettz said:
I get stuck at the following
Download the latest SuperSU flashable zip from
Copy it to your phone.
I can't get access to my phone it doesnt show up on my pc devices etc
Click to expand...
Click to collapse
can u access ur twrp recovery?

jbanti said:
can u access ur twrp recovery?
Click to expand...
Click to collapse
Nope

I have similar issue on Moto G Falcon.
The fastboot factory images fail to write partitions. Also can't flash custom Roms. And this was sudden in the middle while I was using custom rom and the phone rebooted on its own one day and never booted up again.

Hard bricked tf300t with locked bootloader

Hello everyone ! XDA is my last hope !
I've hard bricked my asus tab tf300t and i've done every tutorials on XDA and i spent many days to fix it. Every erases commands works except "misc", the RCK freezes and the command stay at erasing 'misc'.... I can't do anything because it freezes at write step. When i want to install from SD CARD, there is no chance to work, nothing happens. Every choices on bootloader menu RCK - ANDROID - WIPE DATA, turns wrong with "unrecoverable bootloader error 0x00000000" message.
You guys, are the last hope i have. Is there something to do to backup my tablet please ? Any command i missed, or tutorial to suggest to me please ? I know it's old but i want to use it and no money to buy a new one.
My bootloader is locked. Only fastboot works.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system blob
target didn't report max-download-size
erasing 'system'...
OKAY [ 0.137s]
sending 'system' (800931 KB)...
OKAY [102.980s]
writing 'system'...
_
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d46d9285bf81a
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x000000032a680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.107s
Thanks if someone can helps me.

rabahdu91 said:
I've hard bricked my asus tab tf300t and i've done every tutorials on XDA and i spent many days to fix it.
Click to expand...
Click to collapse
First of all Thanks to @Buster99 and his Solution for fixing this problem,
This guide is for helping you to fix Unrecoverable bootloader error, Hope it will help you out of this problem.
Download “Minimal ADB and Fastboot”. Make a folder C:/Fastboot and extract it there and install it. Download firmware WW_V10.6.1.27.5 from the ASUS official website and unzip it twice. Copy the .blob file from WW_V10.6.1.27.5 into the folder C:/Fastboot. Connect the tablet to PC via USB cable.
Open “Minimal ADB and Fastboot” and put in "fastboot devices"or “adb devices”. The device should appear as "real serial number".
Now type following command-lines in cmd-window step by step (wait after every step!):
fastboot erase system
fastboot erase recovery
fastboot erase user data
fastboot erase boot
fastboot erase misc
fastboot erase cache
After that open C:\put in cmd "fastboot -i 0x0B05 flash system blob" without " " .
Now it takes a while "sending..." appears then "write..." and the load status will be shown.
If loading is finished put in "fastboot -i 0x0B05 reboot". It takes a while to start into a clean JB 4.2.2!
Good luck!

Hello and thanks for your reply. I've already did it without a success. It seems don't work with locked bootloader. Like I said the erase misc command freezing and don't work.
I think this tablet is good to the trash.
Thanks for your time.

rabahdu91 said:
Hello and thanks for your reply. I've already did it without a success. It seems don't work with locked bootloader. Like I said the erase misc command freezing and don't work.
I think this tablet is good to the trash.
Thanks for your time.
Click to expand...
Click to collapse
You are welcome! Using the thanks button is greatly appreciated.
Please note, as long as you can access the device via fastboot or ADB is always hope to rescue it. Before you really give up have a look at this thread https://forum.xda-developers.com/showthread.php?t=2179759. You will also find an answer for your misc issue.

Need advice on fresh (re)install of LOS

Hi,
I’ve been an owner of a Moto G7 Power device for a few months now. As we all know, life is not perfect and I still experience several problems (such as unavailable VoLTE/VoWiFi and no SMS notifications on a locked screen), that were present in LOS17.1 and are still there in 18.1. Since I am not an expert and therefore might had made some mistakes during flashing my phone, I’d like to give it a (last) shot and to try to do a fresh install of LOS – maybe it will help? What would be the best possible way to do that (in order to eliminate any doubts that anything was done wrong during flashing, etc)?
So what I have:
- Moto G7 Power (ocean, X1955-5), now "almost new".
- The device is manufacturer unlocked, all hardware seem to be completely OK.
- LOS18.1 installed (and is pretty much OK except for the problems I mentioned above).
That said, here is what I’d like to ask:
1. Does it make any sense to go back to the stock ROM, thren get all official Android/Motorola updates first and only after that to flash LOS?
2. Which LOS to flash: older 17.1 or the most recent 18.1?
3. Which custom recovery to use: TWRP or the one provided by LOS? Both have the versions specific for my device and seem to be maintained and updated.
4. Is it better to flash the custom recovery or just to load it via fastboot boot recovery.img? I used the latter option before and it seemed to work.
5. Does it matter which version of platform-tools to use? My Linux distro definitely does not have the latest one, though it works.
Thanks for any advice!

Stilbium said:
Hi,
I’ve been an owner of a Moto G7 Power device for a few months now. As we all know, life is not perfect and I still experience several problems (such as unavailable VoLTE/VoWiFi and no SMS notifications on a locked screen), that were present in LOS17.1 and are still there in 18.1. Since I am not an expert and therefore might had made some mistakes during flashing my phone, I’d like to give it a (last) shot and to try to do a fresh install of LOS – maybe it will help? What would be the best possible way to do that (in order to eliminate any doubts that anything was done wrong during flashing, etc)?
So what I have:
- Moto G7 Power (ocean, X1955-5), now "almost new".
- The device is manufacturer unlocked, all hardware seem to be completely OK.
- LOS18.1 installed (and is pretty much OK except for the problems I mentioned above).
That said, here is what I’d like to ask:
1. Does it make any sense to go back to the stock ROM, thren get all official Android/Motorola updates first and only after that to flash LOS?
2. Which LOS to flash: older 17.1 or the most recent 18.1?
3. Which custom recovery to use: TWRP or the one provided by LOS? Both have the versions specific for my device and seem to be maintained and updated.
4. Is it better to flash the custom recovery or just to load it via fastboot boot recovery.img? I used the latter option before and it seemed to work.
5. Does it matter which version of platform-tools to use? My Linux distro definitely does not have the latest one, though it works.
Thanks for any advice!
Click to expand...
Click to collapse
Your problems are more like related to the carrier the device is on, the software channel, radio firmware, and maybe apns included with LOS

sd_shadow said:
Your problems are more like related to the carrier the device is on, the software channel, radio firmware, and maybe apns included with LOS
Click to expand...
Click to collapse
So, in other words, you do not think that anything like this could be screwed up during installation/flashing?
I also have a feeling that it (VoLTE part) is somehow related to the carrier... but what can I do? I tried to make a new apn (based on the carrier's instructions) and it worked exactly the same as that included into LOS (i.e. no VoLTE, IMS is always reported "not registered"). On the other hand, I (as well as a couple of others) did not have these problems on the stock.
The reason why I'd like to try a fresh install is that someone (Moto G7: river, which is very similar; also the same carrier) reported that a) he got VoLTE working by going back to stock and then flashing a new version of LOS17.1 and b) his VoWiFi stopped working (on the same device) after an upgrade to 18.1:
https://gitlab.com/LineageOS/issues/android/-/issues/3269

Stilbium said:
So, in other words, you do not think that anything like this could be screwed up during installation/flashing?
I also have a feeling that it (VoLTE part) is somehow related to the carrier... but what can I do? I tried to make a new apn (based on the carrier's instructions) and it worked exactly the same as that included into LOS (i.e. no VoLTE, IMS is always reported "not registered"). On the other hand, I (as well as a couple of others) did not have these problems on the stock.
The reason why I'd like to try a fresh install is that someone (Moto G7: river, which is very similar; also the same carrier) reported that a) he got VoLTE working by going back to stock and then flashing a new version of LOS17.1 and b) his VoWiFi stopped working (on the same device) after an upgrade to 18.1:
https://gitlab.com/LineageOS/issues/android/-/issues/3269
Click to expand...
Click to collapse
Flashing stock is a possible fix, even likely, if others have reported just that.
Doesn't mean you installed it incorrect.
Custom Roms don't include radio firmware, and sometimes it needs to be reflashed.
If you want you can just flash the stock radio firmware.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

sd_shadow said:
Flashing stock is a possible fix, even likely, if others have reported just that.
Doesn't mean you installed it incorrect.
Custom Roms don't include radio firmware, and sometimes it needs to be reflashed.
If you want you can just flash the stock radio firmware.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
Thanks for a hint! Honestly, I bought this phone with a sole purpose of using a custom ROM without google apps... so I am not going back to stock.
Do I understand it correctly that the code you provided implies that I follow only the part of the instructions on "how to flash a stock ROM back" from here:
https://forum.xda-developers.com/t/...ersions-flash-back-to-stock-firmware.3927138/ ? The sequence of commands is different there - erasing comes after the both flashing commands (I am not an expert, sorry).
One more thing - which stock ROM should I use? I mean, which version - the latest, the closest to the current version of LOS or it does not matter? As far as I can see, the latest stock is for Android 10, and I have LOS18.1 installed.

Stilbium said:
Thanks for a hint! Honestly, I bought this phone with a sole purpose of using a custom ROM without google apps... so I am not going back to stock.
Do I understand it correctly that the code you provided implies that I follow only the part of the instructions on "how to flash a stock ROM back" from here:
https://forum.xda-developers.com/t/...ersions-flash-back-to-stock-firmware.3927138/ ? The sequence of commands is different there - erasing comes after the both flashing commands (I am not an expert, sorry).
One more thing - which stock ROM should I use? I mean, which version - the latest, the closest to the current version of LOS or it does not matter? As far as I can see, the latest stock is for Android 10, and I have LOS18.1 installed.
Click to expand...
Click to collapse
The commands I posted are just the radio parts.
That order sometimes fixes radio issues, that the normal order does not.
There may be a benefit to flashing the newer firmware, rarely is the older firmware better, unless you are flashing an older custom ROM.

sd_shadow said:
The commands I posted are just the radio parts.
That order sometimes fixes radio issues, that the normal order does not.
There may be a benefit to flashing the newer firmware, rarely is the older firmware better, unless you are flashing an older custom ROM.
Click to expand...
Click to collapse
Thanks a lot! Though it did not help... maybe I did something wrong.
So first I looked at getvar:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-16222030b3b-201001
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ....................
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: A37CC9D800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: ....................
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 07-08-2020
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C28956
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Apr 29 15:45:40 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:10/QPOS30.85-
(bootloader) ro.build.fingerprint[1]: 23-3/dc622c:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_41.00.01.162R OCEAN_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Thu Oct 1 00:21
(bootloader) kernel.version[3]: :27 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_retail-a30e356d6d-201001
(bootloader) rpm.git: MBM-2.1-ocean_retail-20f2cf34-201001
(bootloader) tz.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) devcfg.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) keymaster.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) prov.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) aboot.git: MBM-2.1-ocean_retail-16222030b3b-201001
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
(bootloader) pcb-part-no: SP69A6P7PU
all: listed above
finished. total time: 0.014s
and noticed that the current-slot/running-slot is b.
Grabbed the latest retus Moto firmware from lolinet (the same 10/QPOS30.85) and then, as probably expected:
Code:
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modemb' (65428 KB)...
OKAY [ 2.616s]
writing 'modemb'...
(bootloader) Invalid partition name modemb
FAILED (remote failure)
finished. total time: 2.617s
Then:
Code:
$ fastboot flash modem_b NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_b' (65428 KB)...
OKAY [ 2.612s]
writing 'modem_b'...
OKAY [ 1.110s]
finished. total time: 3.722s
$ fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.017s]
finished. total time: 0.017s
$ fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.017s]
finished. total time: 0.018s
$ fastboot flash fsg_b fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_b' (9204 KB)...
OKAY [ 0.368s]
writing 'fsg_b'...
OKAY [ 0.121s]
finished. total time: 0.490s
After reboot everything is exactly the same as before - i.e. the same problems remained, no new ones showed up.
UPD: actually, no - the phone is reachable, it rings, but neither I can hear the other party, nor I am heard by anyone.
Maybe I had to flash both a and b slots?
Since my carrier is T-Mobile (though the phone is retail), would it make any sense to try to flash the radio from the T-mobile ROM? There are two ROMs available - RETUS (which I used) and TMO.
Looks like I'll have to temporarily go back to the stock... my fault anyway, needed to check more carefully what the LOS "official support" actually means
Thank you.

Well, back to stock (RETUS) for a while. IMS status is registered, so I guess VoLTE should work. Will try it and VoWiFi a bit later.
However, the settings in APN are a bit different from what is supplied with LOS - could this be the problem?
I'll try to flash LOS ROM once again, so going back to my initial questions - which recovery would you recommend and should I really flash it or fastboot boot?
Thank you.