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 :/
Related
Hi guys,
I've some trouble to unlock my brand new Moto G's bootloader.
I've tried howto from wiki.cyanogenmod. org/w/Install_CM_for_falcon.
Step 6.
Code:
# fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [ 0.160s]
finished. total time: 0.160s
There is no sim card inserted.
I've never connected the phone to my Google account or a Motorla account.
Android 4.3
Baseband MSM 8626BP_1032.3051.51.02P
System 14.91.11.falcon_umts.Retail.en.DE
Build 14.10.oQ3.X-76-LGG-11
Any ideas?
Regards,
Timm
I've updated Android to 4.4.4
System version 210.12.40.falcom_umts.Retail.en.DE
Baseband MSM8626BP_1032.390.81.01P
Build KXB21.14-L1.40
Behavior of "fastboot oem get_unlock_data" didn't change.
cid is 0x0000 so unlocking should be possible.
Any ideas?
Regards,
Timm
timm2k said:
I've updated Android to 4.4.4
System version 210.12.40.falcom_umts.Retail.en.DE
Baseband MSM8626BP_1032.390.81.01P
Build KXB21.14-L1.40
Behavior of "fastboot oem get_unlock_data" didn't change.
cid is 0x0000 so unlocking should be possible.
Any ideas?
Regards,
Timm
Click to expand...
Click to collapse
I've had this problem too. In the latest update 4.4.4 there is a bug for unlocking bootloader but there is a fix for it. i did it and it worked. i found it in the motorola forums. click the link and afterwards on the page, search moto g 4.4.4 bootloader fix in the search bar, its a zip with instructions for you how to unlock, hope it helps
https://forums.motorola.com/hives/3ba9b2429c/summary
Thanks for your reply.
Did you really get this message?:
Code:
# fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [ 0.160s]
finished. total time: 0.160s
I found a zip archive which will unlock the phone when you get your unlock key.
My phone doesn't display the unlock request key. I only get "Could not get unlock data!".
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA8<blanked>
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 168DFB010F000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Oct 13 15:30:13 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retde/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.40/36:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.falcon_umt
(bootloader) ro.build.version.full[1]: s.Retail.en.DE
(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-gb89c9dd ([email protected]
(bootloader) kernel.version[1]: ilclbld27) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 04:49:32 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 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.062s
I've had this same problem. My brother has a Moto G first gen that's softbricked, and since I've worked on androids before I thought I'd fix it. I could get it to boot into fastboot, so I'm trying to install TWRP and fix his phone (stock recovery won't work). But when I enter fastboot oem get_unlock_data I have the same result....
---------- Post added at 05:03 PM ---------- Previous post was at 05:01 PM ----------
Update: turning off the phone and rebooting into fastboot fixed the problem for me. Sorry, that probably doesn't help you :/
Hey Guys,
I got a bricked Moto G from a friend of mine. The device boots untill it gets to the m logo and then reboots. Device doesn't boot into recovery or doesn't do a factory reset. But i can get into fastboot.
I'm familiar with nexus and samsung devices so I already tried a lot of things but nothing seems to work.
I unlocked the bootloader but no change, tried to reflash stock firmware (RETAIL-BR-SS_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF_SVC) via mfastboot but no change.
I tried the hard bricked tutorial found on this forum but my device shows up as fastboot falcon s in my device manager and is not detected when i use the driver for "Qualcomm HS-USB QLoader 9008" it keeps giving me waiting for device when trying to execute the clean flash bat.
I tried to brick the bootloader with the Bootloader bricker but it still shows up as fastboot falcon s.
Any ideas?
The device info for this device is (i deleted serial, there was no imei):
Quote:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(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 Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno:
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 5EE000020F000000000000000000
(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: "Wed Sep 10 18:59:52 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_reteu/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.40/36:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.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.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gb89c9dd ([email protected]
(bootloader) kernel.version[1]: ilclbld54) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 05:33:52 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 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.057s
Press any key to continue . . .
Like I've said in the other topic, try this:
BobDiaz said:
Can you give us more details?
Like if this is really a bootloop (in wich you would see that white image with an exclamation mark for a loooong time) or if you just can't switch your phone on?
I've read about it and, in a situation like yours, the phone usually bricks...
______________________________________
Edit:
When it happened to me, I did the following:
Download and execute the .bat of this topic after installing the phone drivers.
forum. xda-developers. com/ moto-g/general/ guide-xt1033-downgrade-lollipop-5-0-to-t2969729
After this, my phone went to the GPE but it could not flash an stock rom. Than, I did this:
forum. xda-developers. com/ moto-g/general/guide-moto-g-xt1033-android-5-0-lollipop-t2979623
Follow this steps exactly the way its written and it should work.
Click to expand...
Click to collapse
Hey bobdiaz,
I didn't see a reply on the other thread from you but this didn't happen when downgrading. It has always been a 4.4.4 but i wil try the things you suggest!
Oké the explanation you gave me does not resolve my problem.
But i'm pretty sure the brick doesn't come from a downgrade from version 5.
Any other suggestions?
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.
Hi guys!
So I was flashing my mums moto g (xt1032) for the first time in ages. I was upgrading from 4.1 (i think) to 6.0 (http://forum.xda-developers.com/moto-g/development/caf-aosp-aosparadox-project-1-0-t3135626). After all this happened I have realised the xt1032 is not the falcon and I wonder if this is what caused all my problems...?
Anyway, to the problem at hand. After trying to flash, it told me my bootloader was incompatible so I upgraded it to 41.18, flashed the rom again and it went fine. Then I restarted to boot into the rom but it put me into the bootloader. It comes up with "Fastboot Reason: Fall-through from normal boot mode". Now something else that is weird...I can move down the bootloader options with the down key but when I press "up" to select it just flashes the motorola boot screen for a split second (was the "your bootloader is unlocked" screen but I have flashed another boot logo since). This happens when I try to select any option [EDIT 1] I should note that I have a feeling this may have been the case for a while and not related to me flashing the rom or bootloader before - but I can't say for certain. I have tried using mfastboot to flash stock, specifically - ASIA-DS_4.4.4_KXB21.14-L1.40_34_cid7_CFC_1FF which ran mostly successfully but failed to flash the motoboot.img (guessing it can't downgrade the bootloader). This didn't make any difference to the operation of the phone. Now I'm currently downloading the BRASIL_XT1032_5.0.2 stock rom but it is taking forever, really bad host.
Also, I can flash a recovery image but when I try to boot it with "fastboot boot recovery.img" it starts doing it but then shows me an error - something about "remote failed".
[EDIT 1] I have noticed that it does allow me to select the option "barcodes" to show imei information. But for any other option it just says "Boot up failed".
Anyone got any ideas? Been out of the phone flashing biz for too long, it's my mums phone and I'm supposed to be doing my dissertation so any help would be greatly appreciated!
[EDIT 2]
C:\android-sdk\platform-tools>mfastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 4118
(bootloader) product: peregrine
(bootloader) secure: yes
(bootloader) hwrev: 0x82D0
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: TA47XXXXXXXX
(bootloader) cid: 0x0007
(bootloader) channelid: 0x41
(bootloader) uid: 9D00EB0315000000000000000000
(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 22 16:54:20 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/peregrine_reteu/peregrine
(bootloader) ro.build.fingerprint[1]: :4.4.4/KXB21.14-L1.46/42:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.1.46.peregrine_re
(bootloader) ro.build.version.full[1]: teu.reteuall.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.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g26ca2df ([email protected]
(bootloader) kernel.version[1]: ilclbld26) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue May 27 02:43:50 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.18-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.18-0-g5742832
(bootloader) rpm.git: git=MBM-NG-V41.18-0-gcecd6e9
(bootloader) tz.git: git=MBM-NG-V41.18-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.18-0-g99084d5
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: retgb
all: listed above
finished. total time: 0.093s
DoNiMaToR said:
So I was flashing my mums moto g (xt1032) for the first time in ages. [...] After all this happened I have realised the xt1032 is not the falcon and I wonder if this is what caused all my problems...?
...
(bootloader) product: peregrine
Click to expand...
Click to collapse
XT1032 is a falcon, XT1039/40/45 is peregrine. You are trying to install stuff for the wrong device, which is generally a bad idea.
Yep was a silly mistake by me! I'd assumed it was an XT1032 for some reason that I cannot remember, it's actually the XT1039 - flashed it with the correct ROM now. Thanks for your help
All working as normal now. For anyone with similar issues, get the IMEI number from the bootloader and check exactly what model you have using this - IMEI info checker.
[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.