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?
Related
Hallo, guys, help needed.
i have a DE Moto G, after unlocking bootloader Moto stuck on a bootloop. I've tried to flash custom recovery(all of them), but works only PhilZ(every others just loaded,and after a second started to load again and again, i can access anywhere, recovery loop). I have tried to return to stock rom - doesn't work, lock bootloader - failure, flash via fastboot any other rom - nope. Via recovery (adb sideload, adb push) - tried to flash cm or restore any other backup - nope, after installing phone reboots to recovery. I need your help! All drivers and etc are fine.
(bootloader) version: 0.5
(bootloader) version-bootloader: 4105
(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: TA92904DWO
(bootloader) cid: 0x0007
(bootloader) uid: EBB062020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359276056394136
(bootloader) meid:
(bootloader) date: 01-24-2014
(bootloader) sku: XT1032
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 7:49 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_gpe/falcon_umts:4.
(bootloader) ro.build.fingerprint[1]: 4.2/KOT49H.M004/5:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.176.44.1.falcon_umts
(bootloader) ro.build.version.full[1]: .Retail.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-g0c11b77 ([email protected]
(bootloader) kernel.version[1]: 101lnxdroid70) (gcc version 4.7 (GCC) )
(bootloader) kernel.version[2]: #1 SMP PREEMPT Sat Dec 28 10:26:49 PST 2
(bootloader) kernel.version[3]: 013
(bootloader) sdi.git: git=MBM-NG-V41.05-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.05-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.05-0-g4018bbe
(bootloader) tz.git: git=MBM-NG-V41.05-0-g11658be
(bootloader) aboot.git: git=MBM-NG-V41.05-0-gf4ab363
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.062s
Same problem! pls somebody help us!!!!!!!!!!!
lewqou said:
Hallo, guys, help needed.
i have a DE Moto G, after unlocking bootloader Moto stuck on a bootloop. I've tried to flash custom recovery(all of them), but works only PhilZ(every others just loaded,and after a second started to load again and again, i can access anywhere, recovery loop). I have tried to return to stock rom - doesn't work, lock bootloader - failure, flash via fastboot any other rom - nope. Via recovery (adb sideload, adb push) - tried to flash cm or restore any other backup - nope, after installing phone reboots to recovery. I need your help! All drivers and etc are fine.
(bootloader) version: 0.5
(bootloader) version-bootloader: 4105
(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: TA92904DWO
(bootloader) cid: 0x0007
(bootloader) uid: EBB062020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359276056394136
(bootloader) meid:
(bootloader) date: 01-24-2014
(bootloader) sku: XT1032
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 7:49 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_gpe/falcon_umts:4.
(bootloader) ro.build.fingerprint[1]: 4.2/KOT49H.M004/5:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.176.44.1.falcon_umts
(bootloader) ro.build.version.full[1]: .Retail.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-g0c11b77 ([email protected]
(bootloader) kernel.version[1]: 101lnxdroid70) (gcc version 4.7 (GCC) )
(bootloader) kernel.version[2]: #1 SMP PREEMPT Sat Dec 28 10:26:49 PST 2
(bootloader) kernel.version[3]: 013
(bootloader) sdi.git: git=MBM-NG-V41.05-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.05-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.05-0-g4018bbe
(bootloader) tz.git: git=MBM-NG-V41.05-0-g11658be
(bootloader) aboot.git: git=MBM-NG-V41.05-0-gf4ab363
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.062s
Click to expand...
Click to collapse
Connect the device in Fastboot and type in "fastboot -w" and it will delete all user data than just go into recovery (It will boot now) and format everything and than sideload a rom via ADB
The easiest method would be to reflash the stock firmware again and then flash the custom recovery...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
Philz Recovery to rescue!
I was facing the same problem. In twrp it said , updating partition details, and got stuck there, neither i could flash any rom, nor boot the system. The only solution i could find was to change the recovery to philz recovery.
MF I had the same problem for long time in 2 devices (moto g), and finaly, after 1 month I solved the problem with the new firmware 4.4.4 (stock), pls download it for your devices, xt1032 or xt1033.
xt1032
filefactory.com/file/5k8pfdikwltp/XT1032_RETAIL-BR-SS_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF.xml.zip
xt1033
filefactory.com/file/7koj5z8zk1mf/XT1033_RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml.zip
Sorry for my english, im not english speaker
Hello! I've been working on flashing my Boost Moto G to PagePlus. After Flashing the verizon firmware, i ended up changing my mind about the process and reverting back to the Boost stock rom. My fastboot connection works flawlessly, but i no longer can access bp tools. Nor, when i boot up, does the phone get recognized as anything. Ive reinstalled the rom, used a couple different ones, changed cables, changed usb ports, tried different computers, updated my drivers. It seems to be a device issue, not an issue with the connection. Like i said, when entering the bootloader fastboot works fine, If i leave the usb plugged in, then go to bp tools or power up regularly, the phone will get stuck on the Unlocked Bootloader Screen, until i remove the usb cable, and then will vibrate and proceed to power up. Its a very weird issue, and im in need of my bp tools to relash the prl and change my settings back to Boost. any help would be appreciated. Thanks
tsaun817 said:
Hello! I've been working on flashing my Boost Moto G to PagePlus. After Flashing the verizon firmware, i ended up changing my mind about the process and reverting back to the Boost stock rom. My fastboot connection works flawlessly, but i no longer can access bp tools. Nor, when i boot up, does the phone get recognized as anything. Ive reinstalled the rom, used a couple different ones, changed cables, changed usb ports, tried different computers, updated my drivers. It seems to be a device issue, not an issue with the connection. Like i said, when entering the bootloader fastboot works fine, If i leave the usb plugged in, then go to bp tools or power up regularly, the phone will get stuck on the Unlocked Bootloader Screen, until i remove the usb cable, and then will vibrate and proceed to power up. Its a very weird issue, and im in need of my bp tools to relash the prl and change my settings back to Boost. any help would be appreciated. Thanks
Click to expand...
Click to collapse
Please reboot the device in fastboot mode and run the command "getvar all" using fasboot or mfastboot. Post the log here (you can delete your IMEI and serial no).
getvar all
oversleeper said:
Please reboot the device in fastboot mode and run the command "getvar all" using fasboot or mfastboot. Post the log here (you can delete your IMEI and serial no).
Click to expand...
Click to collapse
Actually, one thing that is weird is the imei and meid were missing initially. the only thing i removed was the serial number. Not sure if that could be a contributing factor. Thanks for the response.
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8626 CS
(bootloader) serialno:
(bootloader) cid: 0x0009
(bootloader) channelid: 0x00
(bootloader) uid: 91E933020F000000000000000000
(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: "Thu Aug 28 20:21:56 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_boost/falcon_cdma:
(bootloader) ro.build.fingerprint[1]: 4.4.2/KXB20.9-1.10-1.18/18:user/re
(bootloader) ro.build.fingerprint[2]: lease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.173.44.18.falcon_cdm
(bootloader) ro.build.version.full[1]: a.Boost.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-gc6fc9e1-00001-gf3bf
(bootloader) kernel.version[1]: 628 ([email protected]) (gcc version 4.
(bootloader) kernel.version[2]: 7 (GCC) ) #1 SMP PREEMPT Thu Jan 9 20:46
(bootloader) kernel.version[3]: :19 CST 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: vzw
tsaun817 said:
Actually, one thing that is weird is the imei and meid were missing initially. the only thing i removed was the serial number. Not sure if that could be a contributing factor. Thanks for the response.
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8626 CS
(bootloader) serialno:
(bootloader) cid: 0x0009
(bootloader) channelid: 0x00
(bootloader) uid: 91E933020F000000000000000000
(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: "Thu Aug 28 20:21:56 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_boost/falcon_cdma:
(bootloader) ro.build.fingerprint[1]: 4.4.2/KXB20.9-1.10-1.18/18:user/re
(bootloader) ro.build.fingerprint[2]: lease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.173.44.18.falcon_cdm
(bootloader) ro.build.version.full[1]: a.Boost.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-gc6fc9e1-00001-gf3bf
(bootloader) kernel.version[1]: 628 ([email protected]) (gcc version 4.
(bootloader) kernel.version[2]: 7 (GCC) ) #1 SMP PREEMPT Thu Jan 9 20:46
(bootloader) kernel.version[3]: :19 CST 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: vzw
Click to expand...
Click to collapse
It's pretty normal about IMEI and MEID missing, it's normal with the 41.13 bootloader. I don't understand your cable and boot problem, never heard about this. Also never heard about missing BP Tools... Seems you got a corrupted bootloader If you want to try to get a fresh bootloader using the script to brick then the flash blank tool you can try my guide here.
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.
So here's what all I did with my XT1033. (Asia_Retail)
Flashed an AOSP Slim 6 ROM. - Worked fine for over a month.
Wanted to return to STOCK.
Followed steps:
- Used XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml.zip
- Extracted and flashed using the fastboot commands.
- Every partition flashes with NO ERROR.
But rebooting the phone leads me to the AOSP Slim bootanimation.
Also system boots somewhat frozen, i.e no touch response.
**Even the stock recovery doesn't work, it still loads up TWRP (Also frozen, stuck at TWRP bootsplash)
Though I have flashed several times using mfastboot-v2.
So end result.
Fastboot seems to working fine but has no effect.
*** I can only boot in the fastboot mode.
Any help or information which would guide me in the right direction would be appreciated.:fingers-crossed:
Thanks for help guys.
Fastboot getvar all info
dracovoldy said:
So here's what all I did with my XT1033. (Asia_Retail)
Flashed an AOSP Slim 6 ROM. - Worked fine for over a month.
Wanted to return to STOCK.
Followed steps:
- Used XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml.zip
- Extracted and flashed using the fastboot commands.
- Every partition flashes with NO ERROR.
But rebooting the phone leads me to the AOSP Slim bootanimation.
Also system boots somewhat frozen, i.e no touch response.
**Even the stock recovery doesn't work, it still loads up TWRP (Also frozen, stuck at TWRP bootsplash)
Though I have flashed several times using mfastboot-v2.
So end result.
Fastboot seems to working fine but has no effect.
*** I can only boot in the fastboot mode.
Any help or information which would guide me in the right direction would be appreciated.:fingers-crossed:
Thanks for help guys.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x5
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA91601GLT
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 61BBC1020F000000000000000000
(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: "Tue Jun 23 1:17:28 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_asia_ds/falcon_umt
(bootloader) ro.build.fingerprint[1]: sds:5.1/LPB23.13-56/55:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) ro.build.version.full[0]: Blur_Version.221.21.56.falcon_umt
(bootloader) ro.build.version.full[1]: sds.AsiaRetail.en.03
(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_DSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld32) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 10:37:16 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 1/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.084s
BUMP!
ADB seems to work fine too. I can pull/push files from my SD Card
Hello guys,
I own a XT1032 formerly rooted and open bootloader, custom rom based on german retail 5.02.
After not able to enter recovery mode I tried to install TWRP for installing Cyanogen later on.
Cause this all didn't word i tried to install it by fastboot and now it's bricked.
I can still force the phone to Bootloader but...
During normal boot the phone stucks in the "warning your bootloader is open"-dootscreen and even after a forced shutdown by pressing power button for a few settings it gets back in the start loop for it's own.
During boot to recovery mode the phone stucks on the regular bootscreen white background + blue m.
Already tried to, go back on stock, downgrade to 4.4.4, multiple bootloaders and roms, wipe userdata etc.pp . Found no solution by search or in an other thread.
(bootloader) version: 0.5
(bootloader) version-bootloader: 4118
(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 Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA9290NMSP
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 88208E030F000000000000000000
(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: "Fri Jan 23 16:49:45 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_reteu/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 5.0.2/LXB22.46-28.1/1:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) ro.build.version.full[0]: Blur_Version.220.27.1.falcon_umts
(bootloader) ro.build.version.full[1]: .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.3105.93.00R EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-gdd242b0 ([email protected]
(bootloader) kernel.version[1]: ilclbld35) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jan 23 08:13:13 CST 2015
(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: unknown
Click to expand...
Click to collapse
This quote isn't blanked, so there is no entry for IMEI/MEID.
Whoever is able to give me a hint solving this problem would do me a great favour to do so.
Thanks in advance & best regards
deiscodt
To whom it may concern: Running debian on my pc. Means win-executives are not working.
Hi, did you find a solution? I believe I am in the same situation.