Database Info

[Q] how to un-soft-brick MOTO 4G LTE Falcon 4.4.4

I think I permanently soft bricked my phone.
Possible reasons
I tried to to flash cm-12-20150115-NIGHTLY-falcon from recovery-clockwork-touch-6.0.4.7-falcon . I couldn't figure out how to go to recovery mode from fastboot, so I went there with command prompt via "fastboot boot openrecovery-twrp-2.7.1.0-xt1032.img" . From there, I went to flash CM 12 nightly, but I made one fatal error, I never backed up my stock rom The device restarted, but it took me to "Fastboot reason: Fall-through from normal boot mode". I tried to go to recovery and normal powerup, but I got the message "boot up failed".
Attempted fixes
I scoured the interned to find a possible solution, I tried to re-install a new recovery from fastboot, but I always got the message "Mismatched partition size". I tried to boot from a recovery like I did before with "fastboot boot openrecovery-twrp-2.7.1.0-xt1032.img", but I had no avail, as this message showed up:
downloading 'boot.img'...
OKAY [ 0.275s]
booting...
FAILED (remote failure)
finished. total time: 0.476s
I even followed this thread, http://forum.xda-developers.com/showthread.php?t=2542219 (for restoring the stock firmware), and did everything down to the very letter, and it still didn't work. I kept getting messages like "bab check failed for boot" or "bab check failed for recovery"
I am at my wits end. I don't know if there is anything else to do. If anyone can find a solution to my problem, I'll be forever grateful.
Here is some useful info:
I rememeber updating my phone from ICS to KITKAT (4.4.4) months before i tried to root/flash it.
I bought my phone in the US
"get var all" returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: peregrine
(bootloader) secure: yes
(bootloader) hwrev: 0x82D0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: TA95000LZM
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: 85054F0115000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 16 21:19:52 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/peregrine_retus/peregrine
(bootloader) ro.build.fingerprint[1]: :4.4.4/KXB21.14-L1.56/56:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.56.peregrine_r
(bootloader) ro.build.version.full[1]: etus.retus.en.US
(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 Wed Aug 6 01:2
(bootloader) kernel.version[3]: 3:55 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.13-0-g683cb0c
(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 1/1
(bootloader) ro.carrier: retus
all: listed above

croissanwish said:
I think I permanently soft bricked my phone.
Possible reasons
Click to expand...
Click to collapse
Why are you flashing falcon(xt1032) stuff to your peregrine(xt1045)?
They are not interchangeable.

meekrawb said:
Why are you flashing falcon(xt1032) stuff to your peregrine(xt1045)?
They are not interchangeable.
Click to expand...
Click to collapse
Oh I didn't know that. I'm kind of new to this. Which recovery should I flash?

@croissanwish Hi you have a MOTO G 4G (XT1042 in your case). You need to use this custom recovery https://www.androidfilehost.com/?fid=95864024717072097 TWRP 2.8.3.0 (Credits to Somcom3X). Then and only then flash the custom firmware you want from the http://forum.xda-developers.com/moto-g/4g-development area
If you still have issues after that then PM me.

hacktrix2006 said:
@croissanwish Hi you have a MOTO G 4G (XT1042 in your case). You need to use this custom recovery https://www.androidfilehost.com/?fid=95864024717072097 TWRP 2.8.3.0 (Credits to Somcom3X). Then and only then flash the custom firmware you want from the http://forum.xda-developers.com/moto-g/4g-development area
If you still have issues after that then PM me.
Click to expand...
Click to collapse
Thanks, I got it to work now, it turns out I was using the wrong recovery.

Moto G XT1032 8GB - Completely stock and bootloader locked stuck on Motorola logo

Hello everyone,
last week my Moto G (never unlocked, and completely stock) stopped working. I was on lastest official update, that is Lollipop 5.1, but the problem didn't come up with the update, this was later.
One morning (I have not been shutting down the phone for 1 month I guess) I wake up, it's off. I switch it on and it stays on Motorola logo forever.
If I try to go to fastboot (bootloader version 41.1A) it works, but if I select any option (except the barcode one, the only one working) the phone will go back to the Motorola logo, so I am unable to factory reset and even to go in recovery!
So I tried to erease everything using fastboot and PC: it can communicate with PC, and all commands work EXCEPT the commands that must act on partitions, they ALWAYS return "Remote failure" error.
At that point I tried to unlock the bootloader, maybe that was the problem, but no, same error, always.
Any idea guys? Save my phone please
This is the output for fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA9290CPXQ
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: BAAE0F020F000000000000000000
(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: "Sat Oct 3 15:18:41 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_reteu/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 5.1/LPB23.13-56/56:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.221.21.56.falcon_umt
(bootloader) ro.build.version.full[1]: s.EURetail.en.EU
(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.045
(bootloader) version-baseband: MSM8626BP_1032.3116.98.00R EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld73) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 18:36:22 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.068s

I have the same exact problem!
Nabbolo said:
Hello everyone,
last week my Moto G (never unlocked, and completely stock) stopped working. I was on lastest official update, that is Lollipop 5.1, but the problem didn't come up with the update, this was later.
One morning (I have not been shutting down the phone for 1 month I guess) I wake up, it's off. I switch it on and it stays on Motorola logo forever.
If I try to go to fastboot (bootloader version 41.1A) it works, but if I select any option (except the barcode one, the only one working) the phone will go back to the Motorola logo, so I am unable to factory reset and even to go in recovery!
So I tried to erease everything using fastboot and PC: it can communicate with PC, and all commands work EXCEPT the commands that must act on partitions, they ALWAYS return "Remote failure" error.
At that point I tried to unlock the bootloader, maybe that was the problem, but no, same error, always.
Any idea guys? Save my phone please
This is the output for fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA9290CPXQ
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: BAAE0F020F000000000000000000
(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: "Sat Oct 3 15:18:41 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_reteu/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 5.1/LPB23.13-56/56:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.221.21.56.falcon_umt
(bootloader) ro.build.version.full[1]: s.EURetail.en.EU
(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.045
(bootloader) version-baseband: MSM8626BP_1032.3116.98.00R EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld73) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 18:36:22 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.068s
Click to expand...
Click to collapse
My phone was stuck on blue logo in a bootloop, unable to access anything even after entering bootloader. I flashed the firmware through amd but the problem still exists! Please help

It sounds like emmc corruption for which there is no cure. Unfortunately, without an unlocked Bootloader - your options are limited. However we can try some things.
Flash the latest XT1032 (try both GPE and Retail) Factory Firmware Image using Fastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
It sounds like emmc corruption for which there is no cure. Unfortunately, without an unlocked Bootloader - your options are limited. However we can try some things.
Flash the latest XT1032 (try both GPE and Retail) Factory Firmware Image using Fastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
What are the chances with having an unlocked Bootloader?

Xephor_EX said:
What are the chances with having an unlocked Bootloader?
Click to expand...
Click to collapse
How do you mean? Is there a question mark over if the Bootloader is locked or Unlocked? Assuming the Bootloader is locked, the flashing the factory firmware image may resolve a partition issue - if one exists - and allow you to then unlock the Bootloader.
Make sure you are following the Bootloader unlocking tutorial: http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6

lost101 said:
How do you mean? Is there a question mark over if the Bootloader is locked or Unlocked? Assuming the Bootloader is locked, the flashing the factory firmware image may resolve a partition issue - if one exists - and allow you to then unlock the Bootloader.
Make sure you are following the Bootloader unlocking tutorial: http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6
Click to expand...
Click to collapse
No, I mean that my bootloader is unlocked, I tried flashing the stock firmwares but the problem still persists.

Xephor_EX said:
No, I mean that my bootloader is unlocked, I tried flashing the stock firmwares but the problem still persists.
Click to expand...
Click to collapse
fastboot boot twrp.img​
Factory reset (and format data if necessary) and flash a custom ROM.

lost101 said:
fastboot boot twrp.img​
Factory reset (and format data if necessary) and flash a custom ROM.
Click to expand...
Click to collapse
I can't enter recovery. The only option which works is the Barcodes one :/

Xephor_EX said:
I can't enter recovery. The only option which works is the Barcodes one :/
Click to expand...
Click to collapse
I didn't ask you to enter Recovery. Do that command via fastboot.

lost101 said:
I didn't ask you to enter Recovery. Do that command via fastboot.
Click to expand...
Click to collapse
I know, I did that. After the the fastboot flashes twrp, the phone screen goes black and shows the moto logo then re-enters bootloader.

Xephor_EX said:
I know, I did that. After the the fastboot flashes twrp, the phone screen goes black and shows the moto logo then re-enters bootloader.
Click to expand...
Click to collapse
I just need to be clear, you are doing:
fastboot boot twrp.img​
not:
fastboot flash recovery twrp.img​

lost101 said:
I just need to be clear, you are doing:
fastboot boot twrp.img​
not:
fastboot flash recovery twrp.img​
Click to expand...
Click to collapse
Mhm, yes.

It looks bad for you. The only remaining option (in my opinion) is to treat the phone as a hard-brick, and unbrick it. This may be a way to undo whatever corruption has occurred on the phone.
[HOW TO] Unbrick Moto G 2013! [Falcon, Peregrine] [Lollipop guide]​

lost101 said:
It looks bad for you. The only remaining option (in my opinion) is to treat the phone as a hard-brick, and unbrick it. This may be a way to undo whatever corruption has occurred on the phone.
[HOW TO] Unbrick Moto G 2013! [Falcon, Peregrine] [Lollipop guide]​
Click to expand...
Click to collapse
Will try it tomorrow. Thanks for the help man, appreciate it.
---------- Post added at 03:27 PM ---------- Previous post was at 03:25 PM ----------
Xephor_EX said:
Will try it tomorrow. Thanks for the help man, appreciate it.
Click to expand...
Click to collapse
The phone has actually died before in 2015 due to downgrade from 5.1 Brazil to 4.4.4 updating to 5.0.2 through OTA. A lot of people had been waiting for the mbm files for lollipop and I only got it unbricked through that method in June and now this happened :/

[Q] Moto G stuck on "Warning Bootloader unlocked" screen[but RECOVERY, FASTBOOT work]

[Q] Moto G stuck on "Warning Bootloader unlocked" screen[but RECOVERY, FASTBOOT work]
A friend sent the phone(MOTO G XT 1069) for assistance, and I believe they bricked the phone, but they told him the "board is defective" .
I have tried mfastboot + adb with ROM 4.4.4 STOCK(all commands) and others ROM's, but it restarts on the same white screen, it vibrates but does not leave this screen(warning bootloader...) ... and RSD LITE (a failure happens) ...
Ps: it can also receive charge through the charger.
ps¹: Should I really give up?
thanks

LOG fastboot:
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4887
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x7
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: 0434404824
(bootloader) cid: 0x000C
(bootloader) channelid: 0x19
(bootloader) uid: DFB473060F000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355***********2
(bootloader) meid:
(bootloader) date: 2014-12-11
(bootloader) sku: XT1069
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jul 8 21:38:38 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retbr_dstv/titan_ud
(bootloader) ro.build.fingerprint[1]: stv:6.0/MPB24.65-34-3/3:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.81.3.titan_retbr_
(bootloader) ro.build.version.full[1]: dstv.retbr.en.BR
(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.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g3a1ecea-00026-g0a0
(bootloader) kernel.version[1]: ded4 ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .8 (GCC) ) #1 SMP PREEMPT Mon Aug 22 14:
(bootloader) kernel.version[3]: 24:06 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V48.87-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.87-0-gbffe41a
(bootloader) rpm.git: git=MBM-NG-V48.87-0-gbe53f43
(bootloader) tz.git: git=MBM-NG-V48.87-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.87-0-g1b80345
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: 04*******4
(bootloader) sutinfo:
(bootloader) ro.carrier: retbr
all: listed above
finished. total time: 0.069s

Sorry can't help you much as I'm a bit of a novice but think people will need more info.
What recovery are you using ...twrp ?
And is it the latest version ,does it Boot into the bootloader menu OK ?
I'm not even sure which version of moto g that is but presuming its newer than my xt1039 so why try such a old ROM?
Sent from my XT1039 using Tapatalk

steve.loveday said:
Sorry can't help you much as I'm a bit of a novice but think people will need more info.
What recovery are you using ...twrp ?
And is it the latest version ,does it Boot into the bootloader menu OK ?
I'm not even sure which version of moto g that is but presuming its newer than my xt1039 so why try such a old ROM?
Sent from my XT1039 using Tapatalk
Click to expand...
Click to collapse
Recovery: Apparently it is stock, is written "Android Recovery"
Old ROM, was to try to see if he(moto g) would come back ...
thanks and forgive my english

Desmios said:
Recovery: Apparently it is stock, is written "Android Recovery"
Old ROM, was to try to see if he(moto g) would come back ...
thanks and forgive my english
Click to expand...
Click to collapse
Sounds like its just had its bootloader unlocked at that's it
Double check your model is definitely xt1069 and follow this guide to put new recovery and ROM
https://wiki.cyanogenmod.org/w/Install_CM_for_titan
Sent from my XT1039 using Tapatalk

I had exactly the same problem as you on an XT1032. It was a faulty internal storage (faulty hardware). It lets you flash the files and replace recovery and everything, but never boots, always stays at the bootlogo, not even bootanimation.
You can try the following:
a) Download the stock firmware from another source, then flash it again via mfastboot, read carefully the command output in the computer and in the fastboot screen. Both should say OK or report success in some way. Check if some command causes pink/red message lines in the fastboot screen.
b) Maybe you're forgetting some command in mfastboot?
c) Try flashing TWRP, then wiping all partitions from there and then flashing CyanogenMOD or another stable ROM. If there's an IO error, TWRP's verbosity will help you finding it.
Good luck.

moralesnery said:
I had exactly the same problem as you on an XT1032. It was a faulty internal storage (faulty hardware). It lets you flash the files and replace recovery and everything, but never boots, always stays at the bootlogo, not even bootanimation.
You can try the following:
a) Download the stock firmware from another source, then flash it again via mfastboot, read carefully the command output in the computer and in the fastboot screen. Both should say OK or report success in some way. Check if some command causes pink/red message lines in the fastboot screen.
b) Maybe you're forgetting some command in mfastboot?
c) Try flashing TWRP, then wiping all partitions from there and then flashing CyanogenMOD or another stable ROM. If there's an IO error, TWRP's verbosity will help you finding it.
Good luck.
Click to expand...
Click to collapse
Hello
My Moto G is also stuck on the unlocked bootloader screen, i cant even turn my mobile off (only via fastboot-> recover -> turn mobile off ).
I would flash a rom but i went totally wrom it seems.. im a noob with this things..
So, I have cyanogenmod recovery, but ive already tried to factory reset, wipe system partition and cache, but nothing has changed.
My PC dont recognize my MOTO G anymore because USB debugging is probably off.. Thats why i cant use command promt now ...
So.. is my mobile broken forever?
Or is there someone who can fix it?
(I was also wondering if someone is Dutch here, so i can bring the phone to repair it... if he can be repaired)
Im afraid he will never works again
Kind regards
Lauji
UPDATE: Solved by new recovery (twrp) and flashed another rom with GApps Package.

[SOLVED] [HELP] "Failed to load kernel" after flashing LineageOS 17.1 on Moto G6

Hi everyone.
I purchased a new Motorola Moto G6 with the intention to try out using LineageOS instead of the stock rom.
Here's everything that used to appear in the About section of the Settings. Keep in mind I selected Portuguese so I'll be translating some labels:
Software channel: retin
Android version: 8.0.0
Android security patch level: 2018-04-01
Base band version: M450_03.08.10.51R ALI_INDIADSDS_CUST
Kernel version: 3.18.71-perf-ga4749e5
[email protected] #1
Fri Mar 30 11:53:22 CDT 2018
Version number: OPS27.82-45
This is my first time messing with phones like this. I am a Computer Engineer, though.
I started following the instructions here. I enabled developer options in the settings, enabled USB debugging and allowed OEM unlocking.
Then I unlocked the bootloader. I'm using ADB and Fastboot that came with Android Studio.
I ran fastboot oem get_unlock_data, got the code, inserted in on the Motorola website, got the email with the unlock key and unlocked it with fastboot oem unlock UNIQUE_KEY.
Then I installed TWRP 3.3.1-0. No problems there.
Then I had to search for the link to download LineageOS and GApps because it looked like the steps I was following were incomplete.
I downloaded LineageOS from here and GApps from here. For the latter, I chose ARM64, Android 10.0 and full. I transfered them to the internal storage using Android Studio Device File Explorer.
Then I followed the YouTube video from the first link. I had trouble wiping because of encryption, so it seems. I followed this to proceed. Using a pass or a pin didn't work. The next solution, Repair File System, was unavailable. I could only see Change File System. Then I formatted /data to EXT2 then back to EXT4 and it worked.
Then I tried to flash LineageOS. I got error 255. I looked here. Apparently, I should have used a 64 bit TWRP. I found one here and flashed it. Then I was able to flash both LineageOS and GApps. No error messages here.
Then I rebooted without installing the TWRP app. I got the following:
Code:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer
to repair your device.
Connect you device to your computer to get
the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Error: failed to load kernel!
Fastboot Reason: Fall-through from normal boot mode
USB connected
I searched and didn't find much. I looked for the Software Repair Assistant but it seems it's only good to reinstall the stock ROM. I still want to install LineageOS, though.
I found some results about flashing boot.img and some other stuff, but I'm too afraid to hard brick my phone to follow any instructions that haven't been written specifically for my situation.
I still can access TWRP. I wiped and installed again to double check that there wasn't any error messages during flashing and then again to try installing the TWRP app, but the prompt for that didn't show up.
Please advise on what to do to complete installing LineageOS on my Moto G6.
Update 2020-12-15: It seems that the tutorial I followed has been updated. Now there are no steps missing. I'll try again using the files provided there.
Thanks in advance.

According to this, I can bump. So, bump 1/7.

GuiRitter said:
Then I had to search for the link to download LineageOS and GApps because it looked like the steps I was following were incomplete.
Click to expand...
Click to collapse
It seems the steps have now been fixed. I downloaded the GApps from there, as the LineageOS ROM was apparently the same as the one I already had. Tried to flash again. No change.
It was suggested elsewhere that I might have to disable dm-verity. I was asked to install no-verity-opt-encrypt-6.1.zip. I tried and it failed with the following message in the log: /tmp/updater[63]: .: config.sh: No such file or directory.
It was also suggested to patch boot.img. However, it was also said that LineageOS should come with a patched one, so I didn't look further due to lack of time.

I was asked to flash the stock ROM in order to run Magisk Manager and get a screenshot. I used the Lenovo Rescue and Smart Assistant in order to do that. Phone is working again, but I still want to install LineageOS. Here's the screenshots.
In the process, I learned about the fastboot getvar all command. Here's the output
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-sdm450-C3.09
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 5
(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: SDM450
(bootloader) serialno: ZF62236MJW
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 63B4457200000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) imei: [REDACTED]
(bootloader) meid:
(bootloader) date: 08-11-2018
(bootloader) sku: XT1925-13
(bootloader) carrier_sku: XT1925-13
(bootloader) battid: SB18C18509
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue May 9 7: 0:46 UTC 1972"
(bootloader) ro.build.fingerprint[0]: motorola/ali/ali:8.0.0/OPS27.82-45
(bootloader) ro.build.fingerprint[1]: /56:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.81.56.ali.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_03.08.10.51R ALI_INDIADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-ga4749e5 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 30 11:53:22 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC3.09-0-g4650d8f
(bootloader) rpm.git: git=MBM-NG-VC3.04-0-g02798db
(bootloader) tz.git: git=827710b-dirty
(bootloader) devcfg.git: git=827710b-dirty
(bootloader) keymaster.git: git=827710b
(bootloader) cmnlib.git: git=827710b
(bootloader) cmnlib64.git: git=827710b
(bootloader) prov.git: git=827710b-dirty
(bootloader) aboot.git: git=MBM-NG-VC3.09-0-g225f207
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.082s

Solved with help from here.

what was the problem/ solution finally? Did you try again with other stock ROM 8.1.0 / 9.0 or was it GApps issue?

aIecxs said:
what was the problem/ solution finally? Did you try again with other stock ROM 8.1.0 / 9.0 or was it GApps issue?
Click to expand...
Click to collapse
I can't say, because I did 2 things differently: 1) I used the GApps from the tutorial I was following, for which there was no download link previously; 2) I followed your step by step instead of those from the tutorial I was following.

so you did not flash Android 8.1.0 / 9.0 because it worked with Android 8.0 this time, and your device is not system-as-root therefore you did not do the workaround bind mounting /system_root/system from adb shell
strange because the steps are exactly the same. it should have worked like the first time because you did nothing wrong

aIecxs said:
so you did not flash Android 8.1.0 / 9.0 because it worked with Android 8.0 this time, and your device is not system-as-root therefore you did not do the workaround bind mounting /system_root/system from adb shell
strange because the steps are exactly the same. it should have worked like the first time because you did nothing wrong
Click to expand...
Click to collapse
Just to be clear: Android 8.0 was the stock ROM. The LineageOS 17.1 that I used is supposed to be Android 10.0 (I forgot to double check yesterday but I think it's correct).
EDIT: actually, the Lenovo tool installed an Android 9. The original was 8.

so you did flash Android 9.0 (stock ROM) - probably the reason why it worked this time... LineagesOS installer is targeting Android 8.1.0 (probably min requirement) - seems it doesn't install well on Android 8.0 or below because of incompatibility with firmware/radio

Moto G8 Plus latam stuck on flashing product

HI there, first time here and need some help, I was following this guide "https://forum.xda-developers.com/t/rom-unofficial-lineageos-18-1-for-moto-g8-g-fast-rav.4223617/", the first issue I got was with `fastboot flash recovery recovery.img` which gave me `(bootloader) Invalid partition name recovery` the I followed to rest of the steps, but again got a (bootloader) Invalid partition name product while flashing the product, the tried restarting the phone, and got to this screen
{
"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"
}
then tried again the steps, but this time im getting a
`(bootloader) reboot to fastbootd is not supported by device!`
when running
`fastboot flash product product.img`
and have no clue where to go, any ideas?

what's your exact phone model? Is it a g8 plus or fast?
You should follow this guide to install a GSI on a g8 plus. Not sure about other models; might be similar. https://forum.xda-developers.com/t/tutorial-how-to-install-any-gsi-on-doha-g8-plus.4290237/
Before you do this, you should recover the stock rom. Download LMSA if you can and try to recover. If you want to try to flash through a custom recovery, you first need to root and then install the unofficial TWRP for the g8 plus.

gfrank227 said:
what's your exact phone model? Is it a g8 plus or fast?
You should follow this guide to install a GSI on a g8 plus. Not sure about other models; might be similar. https://forum.xda-developers.com/t/tutorial-how-to-install-any-gsi-on-doha-g8-plus.4290237/
Before you do this, you should recover the stock rom. Download LMSA if you can and try to recover. If you want to try to flash through a custom recovery, you first need to root and then install the unofficial TWRP for the g8 plus.
Click to expand...
Click to collapse
Hi there, thanks for your response, its a g8 plus, just to be safe, do you think this guide should take me on the right path? https://www.getdroidtips.com/stock-rom-motorola-xt2019-2-firmware/

camicase82 said:
Hi there, thanks for your response, its a g8 plus, just to be safe, do you think this guide should take me on the right path? https://www.getdroidtips.com/stock-rom-motorola-xt2019-1-firmware/
Click to expand...
Click to collapse
Yes. this should work but it's not necessary. This takes you through the process to do it manually; however, it might be easier to simply allow LMSA tool to flash the stock firmware automatically. Then, set up the phone and follow the guide I mentioned regarding the GSI. If for some reason LMSA gives an issue with the restore, then we'd try it this way and see.

gfrank227 said:
Yes. this should work but it's not necessary. This takes you through the process to do it manually; however, it might be easier to simply allow LMSA tool to flash the stock firmware automatically. Then, set up the phone and follow the guide I mentioned regarding the GSI. If for some reason LMSA gives an issue with the restore, then we'd try it this way and see.
Click to expand...
Click to collapse
Hi, there just tried the process with LMSA and got an error while flashing the bootloader, I used the zip version that it gave me to download after asking for mi IMEI as it didn't let me pick a specific zip file, any ideas, also LMS forced me to update, should I use a specific version?
Also in case is of use, this is the output of getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-doha_retail-f9b10e522bd-210802
(bootloader) product: doha
(bootloader) board: doha
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZY2277HKNF
(bootloader) cid: 0x0032
(bootloader) channelid: 0x27
(bootloader) uid: C9AB0681
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805263360
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 357207103109211
(bootloader) imei2: 357207103109229
(bootloader) meid:
(bootloader) date: 01-06-2020
(bootloader) sku: XT2019-2
(bootloader) carrier_sku: XT2019-2
(bootloader) battid: SB18C52857
(bootloader) battery-voltage: 4314
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: openla
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:10/QPIS30.28-Q3
(bootloader) ro.build.fingerprint[1]: -28-26-4-1-6/9976a:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_43.45.03.45R DOHA_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Mon Aug 2 07:2
(bootloader) kernel.version[3]: 4:56 CDT 2021
(bootloader) git:abl: MBM-3.0-doha_retail-f9b10e522bd-210802
(bootloader) frp-state: no protection (0)
(bootloader) current-slot:
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C72095
all: listed above
Finished. Total time: 0.195s

camicase82 said:
Hi, there just tried the process with LMSA and got an error while flashing the bootloader, I used the zip version that it gave me to download after asking for mi IMEI as it didn't let me pick a specific zip file, any ideas, also LMS forced me to update, should I use a specific version?
View attachment 5527231
Click to expand...
Click to collapse
is your bootloader unlocked?

gfrank227 said:
is your bootloader unlocked?
Click to expand...
Click to collapse
Yes, I did all the process getting to moto page, submitting the code and getting back my unlock code and applying to the phone, just in case I rechecked and got this:
D:\Movile\platform-tools>fastboot oem unlock U25CRSIQS3V3D3HHTSJ6
(bootloader) Already unlocked
Update: Followed some flash steps from here https://forum.xda-developers.com/t/...-cant-start-only-fastboot-mode.4208715/page-2 and managed to get recovery running again using the files contained on the zip that LMSA downloaded, and after running the hard reset from fastboot, the phone is back to life, and android 10 is running again.
To be sure, I tried again to use LMSA, and this time the process finished successfully, but I'm still getting the "device software can't be checked for corruption" message on boot, is this safe place to try again with LineageOS or do I'm missing something?

camicase82 said:
Yes, I did all the process getting to moto page, submitting the code and getting back my unlock code and applying to the phone, just in case I rechecked and got this:
D:\Movile\platform-tools>fastboot oem unlock U25CRSIQS3V3D3HHTSJ6
(bootloader) Already unlocked
Update: Followed some flash steps from here https://forum.xda-developers.com/t/...-cant-start-only-fastboot-mode.4208715/page-2 and managed to get recovery running again using the files contained on the zip that LMSA downloaded, and after running the hard reset from fastboot, the phone is back to life, and android 10 is running again.
To be sure, I tried again to use LMSA, and this time the process finished successfully, but I'm still getting the "device software can't be checked for corruption" message on boot, is this safe place to try again with LineageOS or do I'm missing something?
Click to expand...
Click to collapse
The warning about the unlocked bootloader is normal. Should be fine to try again. Just follow the link I put above.

gfrank227 said:
The warning about the unlocked bootloader is normal. Should be fine to try again. Just follow the link I put above.
Click to expand...
Click to collapse
Lol, I did and now it really seems to be bricked, the process from the link finished "normally"
But after this step, and rebooting, the phone shows the moto logo for less than a sec, and the screen goes back to black, can't even get to fastboot, time to get it to service?
Update: After spending a couple of hours reading and looking at forums, I realized that the phone was still detected by the pc but just in the wrong mode, then managed to bring it back to life using this:
I'll give it a try again next week with a g6+ to see if I have better luck