Moto G bricked unable to boot/enter recovery stuck on bootlogo - Moto G Q&A, Help & Troubleshooting

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.

Related

[HELP]Urgent, Bootloop, Can't flash any rom, restore or TWPR recovery.

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

[Q] Stuck in Bootloop, Forever

I have been stuck in a bootloop for a while now, and it has been affecting my life making me unable to use my phone when needed. The screen will show "Bootloader has been unlocked" and then will briefly go black and then start up the screen again. I can only access bootloader and fastboot, and I am trying to flash a recovery to get a rom on it. I have tried flashing stock image, but it never worked, no matter what tutorial I used. I feel as though I downloaded the wrong files, and if anyone could point me in the right direction (to set my phone back up, even if just to stock) that would be great.
Here is what I get when I do ./fastboot getvar all, if this tells you anything about my phone.
(bootloader) version: 0.5
(bootloader) version-bootloader: 4110(*)
(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: TA950014UD
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: D8D8470115000000000000000000
(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: "Mon Jan 5 3:12:47 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retuglb/falcon_umt
(bootloader) ro.build.fingerprint[1]: s:4.4.2/KXB20.9-1.8-1.4/4:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.172.44.4.falcon_umts
(bootloader) ro.build.version.full[1]: .Retail.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 ([email protected]
(bootloader) kernel.version[1]: lclbld34) (gcc version 4.7 (GCC) ) #1 SM
(bootloader) kernel.version[2]: P PREEMPT Wed Dec 18 02:39:10 CST 2013
(bootloader) sdi.git: git=MBM-NG-V41.10-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.10-0-gcff5797
(bootloader) rpm.git: git=MBM-NG-V41.10-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.10-1-gb427cd9
(bootloader) aboot.git: git=MBM-NG-V41.10-0-g918f16f
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: retus
all: listed above
all right, I will try. Just seems "iffy" because last time I tried reflashing stock it had some errors.

Semi Bricked XT1032 HELP!

I have a Semi-Bricked Moto G XT1032. Its Only Semi-Bricked because it will not boot, tried several Firmwares zips, even trying to update to 4.4.4 Firmware which made it worse. The problem was caused when trying to update it to a Newer Firmware because it shows that there were no new System Updates via Software Update. Ive tried many different firmware zips, all duds didnt work. Any help is appreciated!
Problem:
"version downgraded for boot. failed to validate boot image. Fastboot Reason: Fall-through from normal boot mode"
Phone: Motorola Moto G XT1032 (Persumably the Telus ca Model)
New Carrier: Cricket Wireless
Bootloader: 41.13.
Firmware/OS: Android 4.4.2. | 173.44.9.falcon_umts.aio.en.us
Last Info grabed before Semi-Brick.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4105
(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: TA929169W4
(bootloader) cid: 0x0010
(bootloader) uid: 33D985040F000008000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 353307062096864
(bootloader) meid:
(bootloader) date: 07-11-2014
(bootloader) sku: XT1032
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jun 27 20:56:52 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_aio/falcon_umts:4.
(bootloader) ro.build.fingerprint[1]: 4.2/KXB20.9-1.10-1.9/12:user/bldac
(bootloader) ro.build.fingerprint[2]: fg,release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.173.44.9.falcon_umts
(bootloader) ro.build.version.full[1]: .AIO.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 ([email protected]
(bootloader) kernel.version[1]: lclbld31) (gcc version 4.7 (GCC) ) #1 SM
(bootloader) kernel.version[2]: P PREEMPT Thu Dec 19 02:03:58 CST 2013
(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 2/1
all: listed above
Continued to try to fix it. Made it worse due to no reply's. Now only getting Boat-loader Permission Denied Error.
New Attempts: Used Hard Bricker Program, and used qboot Blankflash or whatever it is. Now not able to do anything at all. Tried GPT, Boot, Recovery, etc etc etc. All permission Denied Errors. OEM unlock is now disabled. Not sure what else tood at this point.

My Moto G 1st gen stop working after trying update it to 5.1

Hello friends,
My Moto G 1st gen with [5.0.2], i got OTA update notification, but update fail because my device is rooted and boot-loader is unlocked!
I already downloaded a lot of ROMs as zip files.
Code:
Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip
XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml.zip
XT1033_Retail_Asia_51_Untouched.zip
cm-12.1-20151023-NIGHTLY-falcon.zip
And I'm wrongly flashed ROM for XT1032 and my device is XT1033, I cannot boot to normal mode! but I can access the fastboot flash boot using power button and volume down key.
The question here, which ROM is suitable with my device, and how can I flash ZIP ROMs to my device?
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4119
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x5
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA91600LX5
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: A64C36020F000000000000000000
(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 Mar 17 18:38:57 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_gpe/falcon_umts:5.
(bootloader) ro.build.fingerprint[1]: 1/LMY47M.M001/6:user/release-keys
(bootloader) ro.build.version.full:
(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-ga838857 ([email protected]
(bootloader) kernel.version[1]: pe) (gcc version 4.8 (GCC) ) #1 SMP PREE
(bootloader) kernel.version[2]: MPT Tue Mar 17 11:09:24 PDT 2015
(bootloader) sdi.git: git=MBM-NG-V41.19-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.19-0-g5742832
(bootloader) rpm.git: git=MBM-NG-V41.19-0-gcecd6e9
(bootloader) tz.git: git=MBM-NG-V41.19-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.19-0-g291b089
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: unknown
all: listed above

MOTO G XT1032 Unable to Flash Any ROM >> Bricked

MOTO G XT1032 hab check errorrs
Hi,
Iam facing a difficulty flashing any ROM on my Moto G
Soft Bricked
XT1032
Unable to get into Recovery(Gets stuck at Motorola Boot Logo if recovery is selected, same happens when any rom is flashed) however able to access fastboot
RSD Lite does not work
Tried a few roms
i get habcheck errors for boot and recovery while entering the commands
eventually phone gets to the motorola logo and goes into a blank blue screen >>BRICKED
Can anybody help me
Commands where i encounter habcheck errors are>>
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
GETVAR ALL RESULTS >>
F:\G\mfastboot-v2\mfastboot-v2>mfastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA89003TA0
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 129CEC010F000000000000000000
(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 14 2:56:12 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_vffrsl/falcon_umts
(bootloader) ro.build.fingerprint[1]: :4.4.4/KXB21.14-L1.40/36:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.falcon_umt
(bootloader) ro.build.version.full[1]: s.SFRSL.en.FR
(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]: ilclbld32) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 02:19:14 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.061s
As you can see my issue is very similar, but if you look around in recent topics, you see several phones having the same symptoms.
I'm 90% sure that it's hardware failure in my case and maybe the memory chips are reaching the end of their (short) lifetime these months...

Categories

Resources