Database Info

X1032 Falcon- Stock at Bootloop - & - Cannot flash recovery

Dear all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(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 Samsung S4 SDRAM DIE=4Gb
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jul 12 14:11: 9 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retde/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.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.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld34) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 19:06:25 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
this is my X1032 which is stuck at bootloop.
What i have tried:
numerous flashes, namely downgrading to RETAIL_XT1032_4.4.4_KXB21.14-L1.61_cid9_CFC.xml or GPE_5.1_XT1032_LMY47M.M001_CFC.xml.
formatting, flashing etc... i get numerous mismatch and hab failed errors.
The only flash which gets flashed without any warnings is
Code:
XT1032_FALCON_RETFR_5.1_LPB23.13-56_cid7_CFC.xml
but it also stocks at bootloop
also I cannot install any custom rom , every time i flash anyrom it boots up with the same stock "no command" recovery.
the closest i got was using
Code:
fastboot boot recovery twrp-2.8.7.0.-falcon_GPE.img
or
Code:
fastboot boot recovery twrp-2.8.7.0.-falcon_STOCK.img
which gives me a temporary Read-only access to my sdcard (until i reboot), even if i could upload anything to my sdcard in that mode it would have been great! then i can upload a custom image and Voila!
So any help on getting my MOTO G out of bootloop, or even any hints on how to get the custom recovery working on my phone would be greatly appreciated

Flash Lollipop stock firmware: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Enviado de meu SM-G900M usando Tapatalk

alexandrino said:
Flash Lollipop stock firmware: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Enviado de meu SM-G900M usando Tapatalk
Click to expand...
Click to collapse
isnt this XT1032_FALCON_RETFR_5.1_LPB23.13-56_cid7_CFC.xml the same thing?

Did you follow the instructions in this topic: http://forum.xda-developers.com/showthread.php?t=2542219 ?

alexandrino said:
Did you follow the instructions in this topic: http://forum.xda-developers.com/showthread.php?t=2542219 ?
Click to expand...
Click to collapse
yes every thing. only than i have not found any rom which has
Code:
flashall.bat /eu
so what i did was mostly with fastboot.

xarch15 said:
Dear all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(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 Samsung S4 SDRAM DIE=4Gb
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jul 12 14:11: 9 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retde/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.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.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld34) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 19:06:25 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
this is my X1032 which is stuck at bootloop.
What i have tried:
numerous flashes, namely downgrading to RETAIL_XT1032_4.4.4_KXB21.14-L1.61_cid9_CFC.xml or GPE_5.1_XT1032_LMY47M.M001_CFC.xml.
formatting, flashing etc... i get numerous mismatch and hab failed errors.
The only flash which gets flashed without any warnings is
Code:
XT1032_FALCON_RETFR_5.1_LPB23.13-56_cid7_CFC.xml
but it also stocks at bootloop
also I cannot install any custom rom , every time i flash anyrom it boots up with the same stock "no command" recovery.
the closest i got was using
Code:
fastboot boot recovery twrp-2.8.7.0.-falcon_GPE.img
or
Code:
fastboot boot recovery twrp-2.8.7.0.-falcon_STOCK.img
which gives me a temporary Read-only access to my sdcard (until i reboot), even if i could upload anything to my sdcard in that mode it would have been great! then i can upload a custom image and Voila!
So any help on getting my MOTO G out of bootloop, or even any hints on how to get the custom recovery working on my phone would be greatly appreciated
Click to expand...
Click to collapse
I've had this issue twice. Here is what to do, download this file XT1032_FALCON_RETUGLB_5.1_LPB23.13-58_cid9_CFC.xml.zip then download mfastboot-v2.zip followed by the .bat in the .zip file I uploaded.
Unzip all files, put the mfastboot files in the 5.1 firmware folder along with the .bat file. Connect your phone in fastboot mode, double click on the .bat file and let it do its job for you. If it doesn't work, try again? Worked for me. No issues.

lifetimes said:
I've had this issue twice. Here is what to do, download this file XT1032_FALCON_RETUGLB_5.1_LPB23.13-58_cid9_CFC.xml.zip then download mfastboot-v2.zip followed by the .bat in the .zip file I uploaded.
Unzip all files, put the mfastboot files in the 5.1 firmware folder along with the .bat file. Connect your phone in fastboot mode, double click on the .bat file and let it do its job for you. If it doesn't work, try again? Worked for me. No issues.
Click to expand...
Click to collapse
I downloaded the file (the attachment you provided was only an xml but i found the file easily so thanks) and booted it. i got hab check failed for boot and the rest went ok . but again in the end, same bootloop

xarch15 said:
I downloaded the file (the attachment you provided was only an xml but i found the file easily so thanks) and booted it. i got hab check failed for boot and the rest went ok . but again in the end, same bootloop
Click to expand...
Click to collapse
I have the same problem :/

xarch15 said:
I downloaded the file (the attachment you provided was only an xml but i found the file easily so thanks) and booted it. i got hab check failed for boot and the rest went ok . but again in the end, same bootloop
Click to expand...
Click to collapse
you have tried to install some kernel?

xarch15 said:
I downloaded the file (the attachment you provided was only an xml but i found the file easily so thanks) and booted it. i got hab check failed for boot and the rest went ok . but again in the end, same bootloop
Click to expand...
Click to collapse
Interesting. I'm wondering if that's a bootloader problem.

lifetimes said:
Interesting. I'm wondering if that's a bootloader problem.
Click to expand...
Click to collapse
I have tried with a flash another rom with a custom kernel and a stock kernel and in the installation give me error that was "hub check failed for boot"
So i keep trying to resolv the same problem that you have.
Sorry for my bad english.

Wichodroide said:
you have tried to install some kernel?
Click to expand...
Click to collapse
not as far as i remember, i went crazy and install multiple stuff at some point but none of them was a kernel to my knowledge

xarch15 said:
not as far as i remember, i went crazy and install multiple stuff at some point but none of them was a kernel to my knowledge
Click to expand...
Click to collapse
I know the archive of kernel is a boot.img, so i put the archive with the files of stock rom and tried to flash.

same problem here right now the last thing i tried its to install a custom recovery but i still get the stock recovery im going to try with more versions of twrp or should i use philz?

gabriel32mty said:
same problem here right now the last thing i tried its to install a custom recovery but i still get the stock recovery im going to try with more versions of twrp or should i use philz?
Click to expand...
Click to collapse
I tried with so many custom recoverys, but no one works ?

Provide full and complete fastboot logs. Copy and paste Command Prompt screen - or take screenshots.

Same here with XT1033
same thing is happening to me. phone is not booting stock rom.
i was on cynogenmod nightly and wanted a clean install of snapshot build. i connected my device to pc and booted phone into bootloader mode. i flashed stock rom using a .bat file. the rom zip and bat file are the same as i used earlier many times successfully. now i am stuck at unlocked bootloader warning screen.
update: Flashed Kitkat rom and it booted successfully.

lost101 said:
Provide full and complete fastboot logs. Copy and paste Command Prompt screen - or take screenshots.
Click to expand...
Click to collapse
Here are a some screenshots taken with another cell
{
"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"
}
gR6vMa[/IMG]
and not how to get the information from the bootloader with system commands, but i have the errors ''hub check failed for boot'' ''hub check failed for recovery'',
and when i want to install stock rom non-gpe y have the errors ''image is too large'' in the files ''systemspacechuncks
my moto g is xt1032

Wichodroide said:
Here are a some screenshots taken with another cell
gR6vMa[/IMG]
and not how to get the information from the bootloader with system commands, but i have the errors ''hub check failed for boot'' ''hub check failed for recovery'',
and when i want to install stock rom non-gpe y have the errors ''image is too large'' in the files ''systemspacechuncks
my moto g is xt1032
Click to expand...
Click to collapse
Use mfastboot. Use GPE_5.1_XT1032_LMY47M.M005. List all the fastboot commands you are using.

lost101 said:
Use mfastboot. Use GPE_5.1_XT1032_LMY47M.M005. List all the fastboot commands you are using.
Click to expand...
Click to collapse
Well, the same thing happened again , with the same mistakes
the errors are 'hub check failed for boot and recovery'' and now not pass from bootloop animation
Here are the screenshots of cellphone
Here are the files
And here are the commands that I use
What should I do now? i have wait the boot for 30 minutes and nothing

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.

Brick Moto X4

Hello all.
I have a big problem, the phone doesn't have rom, TWRP and stay in fastboot flash mode (secure).
The big problem is in ADB. the program don't recognize the device.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached.
But in fastboot is ok
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY22****** fastboot
if I try to charge the TWRP to install any rom is not possible and sends this error message.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP-3.3.3-0.img
(bootloader) slot-suffi: not found
(bootloader) partition-typ: not found
target reported max download size of 536870912 bytes
sending 'recovery' (30488 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot/path/to/TWRP-3.3.3-0.img
fastboot: usage: unknown command boot/path/to/TWRP-3.3.3-0.img.
please help me.

Put your TWRP.img (replace with the full filename) into the folder where adb and fastboot are in.
fastboot boot TWRP.img
or
fastboot flash boot TWRP.img
OR
Look here: https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348

This also helped me, because I was able to get the stock rom back up, but I stupidly re-locked the oem and thus had no internet connection.
https://github.com/Genymobile/gnirehtet

I've bricked mine too!
I might have messed up during the installation of TWRP, it didn't work out, and i wiped all data.
trying to fix and trying to install the stock rom back, i locked my bootloader.
How do i fix this?
Code:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190305
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: 0041129846
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 284F9D2D
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 359552083482056
(bootloader) meid:
(bootloader) date: 11-24-2017
(bootloader) sku: XT1900-6
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4266
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -26-6/0531:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.231.18.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gf95b07e (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]: Tue Mar 5 06:07:06 CST 2019
(bootloader) git:abl: MBM-3.0-payton_retail-0e6e7ce-190305
(bootloader) git:xbl: MBM-3.0-payton_retail-6b0c3d7-190305
(bootloader) git:pmic: MBM-3.0-payton_retail-6b0c3d7-190305
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190305
(bootloader) git:tz: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) git:hyp: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) git:devcfg: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) git:cmnlib: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) git:keymaster: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) git:prov: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) git:storsec: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(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: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.260s
{
"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"
}
Any help is really welcome.

hello if you flash your original firmware I think everything would be ok, your device is xt-1900-6 retail, although the bootloader is blocked via adb it flashes without problems, look for that firmware, regards

Thanks!
grosobart said:
hello if you flash your original firmware I think everything would be ok, your device is xt-1900-6 retail, although the bootloader is blocked via adb it flashes without problems, look for that firmware, regards
Click to expand...
Click to collapse
I did wht you said, got the adb sideload working.
but my phone just says:
Code:
E: Footer is wrong
Update package verifications took 0.3s (result 1).
E: Signature Verification Failed
E: error: 21
Installation aborted.
I'm searching for this now, not sure why this is happening...

1: some bad line apparently
2: error 21 is rare because "error 21" is related to the format in which the phone numbers are stored. ... Regarding the messaging service settings, the Internet Access Point Name (APN) is the address that the phone uses to connect to the Internet.
and why install via sideload? this method always gave me problems

grosobart said:
1: some bad line apparently
2: error 21 is rare because "error 21" is related to the format in which the phone numbers are stored. ... Regarding the messaging service settings, the Internet Access Point Name (APN) is the address that the phone uses to connect to the Internet.
and why install via sideload? this method always gave me problems
Click to expand...
Click to collapse
Well, i tried Lenovo Rescue System, didn't work. I tried RSD Lite, I got an error saying "can't change to fastboot mode" while my phone was already on fastboot. Now via ADB, I got a different error, i really don't know what else to do or any other way to try.

Unlock the bootolader!

Did anybody got the bootloader unlock yet

Is it me or the website is not allowing people to unlock their bootloader, did anybody experience this issue yet if you did please comment below let me know your thoughts.
I got Verizon I try to unlock it yesterday the bootloader it still says code fail so their isn't no Verizon unlocking on this phone.
Sent from my moto g stylus using Tapatalk

I've tried repeatedly phone was released but as of this post I'm still unable to unlock bootloader.

I got mine unlocked yesterday with no problem

i get remote unlock error please help full getvar
Microsoft Windows [Version 10.0.19041.264]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofiap_t-20deb5d-200222
(bootloader) product: sofiap
(bootloader) board: sofiap
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 128GB SAMSUNG DV6DMB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 06 10 12
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZF6523J4FN
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid:
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805263360
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-06-2020
(bootloader) sku: XT2043-4
(bootloader) carrier_sku: XT2043-4
(bootloader) battid: SB18C71380
(bootloader) battery-voltage: 3793
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/sofiap_t/sofiap:10/QPR30.
(bootloader) ro.build.fingerprint[1]: 80-64/777253:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_10.11.03.22R SOFIAP_NA_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 Sat Feb 22 04:
(bootloader) kernel.version[3]: 41:00 CST 2020
(bootloader) git:xbl: MBM-3.0-sofiap_t-37f1d83-200222
(bootloader) git:xbl_config: MBM-3.0-sofiap_t-37f1d83-200222
(bootloader) git:rpm: MBM-3.0-sofiap_t-ffcccb0-200222
(bootloader) git:tz: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:hyp: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:devcfg: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:cmnlib: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:cmnlib64: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:keymaster: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) gitrov: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:abl: MBM-3.0-sofiap_t-20deb5d-200222
(bootloader) git:qupfw: MBM-3.0-sofiap_t-f848623-200222
(bootloader) git:uefisecapp: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C69985
all: listed above
finished. total time: 0.312s

jcastro889 said:
I got mine unlocked yesterday with no problem
Click to expand...
Click to collapse
Show and prove photos
Sent from my moto g stylus using Tapatalk

Been knew that go ahead to the Motorola website
Sent from my moto g stylus using Tapatalk

Yep, unlocked mine on 5/6/2020.

Tried to unlock one a few days ago but it wouldn't work. I will try again today

Mine unlocked fine. Did it a few days ago

The new update came out and they gave me a dumb code that isn't working good enough
Sent from my moto g stylus using Tapatalk

I got mine unlocked it's the XT2043-5 sku

god_of_wisdom said:
The new update came out and they gave me a dumb code that isn't working good enough
Sent from my moto g stylus using Tapatalk
Click to expand...
Click to collapse
You said you got one from Verizon? More than likely it is not unlockable....
Don't get discouraged yet. You gotta think outside of the box. I had a Verizon variant Google Pixel and updated it before learning about depixel8.
Shortly there was a bounty out for the Google Pixel. Soon there was someone who found out how to break it greyed out unlocked bootloader on the Google Pixel.
What I'm trying to say is that it's not impossible to get it done if you have the right mindset, but I'd caution you from buying from Verizon. It's a respectable company, however they make their bootloaders hard to crack.

ShadowWeasel said:
You said you got one from Verizon? More than likely it is not unlockable....
Don't get discouraged yet. You gotta think outside of the box. I had a Verizon variant Google Pixel and updated it before learning about depixel8.
Shortly there was a bounty out for the Google Pixel. Soon there was someone who found out how to break it greyed out unlocked bootloader on the Google Pixel.
What I'm trying to say is that it's not impossible to get it done if you have the right mindset, but I'd caution you from buying from Verizon. It's a respectable company, however they make their bootloaders hard to crack.
Click to expand...
Click to collapse
My oem isn't grey out that's the strange part when I got the code it was a dumb code AAAAAAAAAAAAAAAAAAAA i was like wtf I thought be a code that be easy but this code hell no
Sent from my moto g stylus using Tapatalk

god_of_wisdom said:
My oem isn't grey out that's the strange part when I got the code it was a dumb code AAAAAAAAAAAAAAAAAAAA i was like wtf I thought be a code that be easy but this code hell no
Sent from my moto g stylus using Tapatalk
Click to expand...
Click to collapse
Yeah, that is a dummy code. It makes me wonder, though. Is all bootloader keys the same or unique? Many if not all says unique....
you could try mine which is 4JXK6WCCVJTD5VXEKFGV
If it works, then good. If not, I feel for you.
I had mine unlocked for 1 day and still looking how to root the thing. Many say patch the boot.img for magisk, but I cant find it...

U download the stock rom and u find the boot.img from there I will post the root method
Sent from my moto g stylus using Tapatalk

god_of_wisdom said:
U download the stock rom and u find the boot.img from there I will post the root method
Click to expand...
Click to collapse
it's been a while since I rooted a phone but what does everyone use these days to check if bootloader is unlocked

god_of_wisdom said:
U download the stock rom and u find the boot.img from there I will post the root method
Sent from my moto g stylus using Tapatalk
Click to expand...
Click to collapse
yeah, i was fatigued when i sent that last message. anyways i digress....
attempted root. failed miserably....
what happened is the same as a few others on another thread. touchscreen unresponsive. also shows no service and 0% battery.
good thing i backed up everything and downloaded the stock rom.
anyways has anyone had a successful root?

ShadowWeasel said:
yeah, i was fatigued when i sent that last message. anyways i digress....
attempted root. failed miserably....
what happened is the same as a few others on another thread. touchscreen unresponsive. also shows no service and 0% battery.
good thing i backed up everything and downloaded the stock rom.
anyways has anyone had a successful root?
Click to expand...
Click to collapse
I didn't have any problems rooting. Downloaded the stock rom with the Lenovo Rescue & Smart Assist software on my PC. Copied the boot.img to the phone & patched it with Magisk 20.4 / Magisk Manager 7.5.1. Copied the patched boot image back to my PC & flashed it via fastboot.

dafunk60 said:
I didn't have any problems rooting. Downloaded the stock rom with the Lenovo Rescue & Smart Assist software on my PC. Copied the boot.img to the phone & patched it with Magisk 20.4 / Magisk Manager 7.5.1. Copied the patched boot image back to my PC & flashed it via fastboot.
Click to expand...
Click to collapse
How did you do it? I did my 2nd attempt and still failed.
Also, comparing the boot.img is way different. The original boot.img is 60mb while the patched boot.img is about 10mb. Is that supposed to be right?

ShadowWeasel said:
How did you do it? I did my 2nd attempt and still failed.
Also, comparing the boot.img is way different. The original boot.img is 60mb while the patched boot.img is about 10mb. Is that supposed to be right?
Click to expand...
Click to collapse
All I did to root is listed in the steps above. My patched boot images are also much smaller, I think the original boot image is just padded as it's a perfect 64MB. My patched boot image is 11.8MB. All I can think of is that the boot image your patching & flashing may not be the exact version that phone is running. My phone shipped with SOFIAP_RETAIL_QPR30.80_58 & the update from last week was SOFIAP_RETAIL_QPRS30.80_58_3. Where are you getting your original boot.img file from?