Database Users

[Q] XT907 bricked! Help :(

Howdy
I have a Razr M which was the old BDH debloated stock rom.
I flashed over to PACMan this morning, rebooted, stuck in fastboot!
I have tried the Razr M Utility and RSD Lite to try to flash back to stock, but I am met with incessant errors:
#1 When I try RSD Lite, it fails at writing the system.img
#2 When I try Matt's utility, I get a 'remove fail' when writing system.img
FastBoot reasons vary between "No PIV in system block" or "stick bit in factory_reset"
I am unable to get to any kind of recovery, or any kind of logo screen. M will flash, but then immediately to fastboot.
Phone was previously unlocked and rooted

shlazzer said:
Howdy
I have a Razr M which was the old BDH debloated stock rom.
I flashed over to PACMan this morning, rebooted, stuck in fastboot!
I have tried the Razr M Utility and RSD Lite to try to flash back to stock, but I am met with incessant errors:
#1 When I try RSD Lite, it fails at writing the system.img
#2 When I try Matt's utility, I get a 'remove fail' when writing system.img
FastBoot reasons vary between "No PIV in system block" or "stick bit in factory_reset"
I am unable to get to any kind of recovery, or any kind of logo screen. M will flash, but then immediately to fastboot.
Phone was previously unlocked and rooted
Click to expand...
Click to collapse
not sure if your problem has been resolved, but are you able to get into recovery? also, make sure you charge the phone up to 100% first (if you can't tell, then just charge it for about 2 hours)

Fortunately, my issues have been resolved.
Not sure what the specific fix was, but all I really did was just retry flashing over and over and over, with RSD Lite and matt's utility. One time it finally worked.
from there, the factory_fastboot sticky bit was fixed by clearing oem fastboot userdata and cache in ADB
phone was good as new!

Enter fastboot oem fb_mode_clear and problem gone.

I find the solution
:laugh::laugh::laugh: I find the solutions reply me if u want
shlazzer said:
Howdy
I have a Razr M which was the old BDH debloated stock rom.
I flashed over to PACMan this morning, rebooted, stuck in fastboot!
I have tried the Razr M Utility and RSD Lite to try to flash back to stock, but I am met with incessant errors:
#1 When I try RSD Lite, it fails at writing the system.img
#2 When I try Matt's utility, I get a 'remove fail' when writing system.img
FastBoot reasons vary between "No PIV in system block" or "stick bit in factory_reset"
I am unable to get to any kind of recovery, or any kind of logo screen. M will flash, but then immediately to fastboot.
Phone was previously unlocked and rooted
Click to expand...
Click to collapse

i got one stuck at no valid piv block in SP for system. tried to flash to kitkat but always got stuck at system partition with rsd. tried to downgrade without sbls but does not work.

el_venga said:
i got one stuck at no valid piv block in SP for system. tried to flash to kitkat but always got stuck at system partition with rsd. tried to downgrade without sbls but does not work.
Click to expand...
Click to collapse
If you want to downgrade, remove commands to flash gpt.main and tz from the xml of the ROM

Klen2 said:
If you want to downgrade, remove commands to flash gpt.main and tz from the xml of the ROM
Click to expand...
Click to collapse
left it for like 2 hours with rsd. finally system was flashed. thanks for response.

[Q] OTA Relocked Bootloader, Bricked Device

Some strange experience to report.
Flashed my unlocked (had been running CM11 beforehand) RAZR M to stock using Matt's utility (all modems, kernel, system and recovery) and everything worked fine.
After booting, I decided to accept OTA update (had done this before without any problems)
Device booted into recovery, flashed the OTA, and booted straight into fastboot, telling me my device's bootloader is now locked (status code 0) and that I can no longer use Matt's utility to flash anything (my guess is something messed up the partitions)
AP Fastboot:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e94557, 2013-05-24 14:49:34)
eMC Info: Size 8GB
Device is LOCKED, Status Code 0
Battery OK
Transfer Mode:
USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
Click to expand...
Click to collapse
Anyone got any ideas what might have caused this, and what can be done to fix it?

Leraeniesh said:
Some strange experience to report.
Flashed my unlocked (had been running CM11 beforehand) RAZR M to stock using Matt's utility (all modems, kernel, system and recovery) and everything worked fine.
After booting, I decided to accept OTA update (had done this before without any problems)
Device booted into recovery, flashed the OTA, and booted straight into fastboot, telling me my device's bootloader is now locked (status code 0) and that I can no longer use Matt's utility to flash anything (my guess is something messed up the partitions)
AP Fastboot:
Anyone got any ideas what might have caused this, and what can be done to fix it?
Click to expand...
Click to collapse
Try flashing each file through Mfastboot.
Code:
mfastboot flash partition gpt_main0.bin
mfastboot flash logo logo.bin
mfastboot flash system system.img
mfastboot flash boot boot.img
mfastboot flash fsg fsg.mbn

ATTACK said:
Try flashing each file through Mfastboot.
Code:
mfastboot flash partition gpt_main0.bin
mfastboot flash logo logo.bin
mfastboot flash system system.img.ext4
mfastboot flash boot boot.img
mfastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
When flashing anything via fastboot (or mfastboot)
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'partition' (32KB)...
OKAY [ 0.074s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.383s
Click to expand...
Click to collapse

Leraeniesh said:
When flashing anything via fastboot (or mfastboot)
Click to expand...
Click to collapse
Have you tried RSDLite? What version of firmware are you flashing? It looks like you flashed a downgraded GPT partition.

ATTACK said:
Have you tried RSDLite? What version of firmware are you flashing? It looks like you flashed a downgraded GPT partition.
Click to expand...
Click to collapse
Have also tried RSD Lite (5.6 and 6.1.5) with similar results
I just flashed the OTA that VZW sent my way.
EDIT: Was able to get it to flash using HouseofMoto's RSD XML.
All good

Leraeniesh said:
Have also tried RSD Lite (5.6 and 6.1.5) with similar results
I just flashed the OTA that VZW sent my way.
Click to expand...
Click to collapse
And you tried to restore 98.30.1? I know with the leak, it is a two part flashing process. It will reboot after part 1, then you need to reboot into recovery to start part 2. You may need to wait until there's a FXZ to fix it.

This is scary. Ive just RSD'd back to stock and am about to update my phone with all the OTA's. Perhaps ill stop for now.
EDIT: And the OTA process just failed from Stock update. FML.

Maybe try this? This is sourced from Moto's website
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/91999/p/1449,8620

If anyone else experiences something similar, you can follow jimyv's post regarding setting up RSD to flash (despite something going wonk with the partition table)

I am having this same issue, I tried the house of moto tutorial and my result is everything failed. Any other suggestion will be greatly appreciated

techfellow said:
I am having this same issue, I tried the house of moto tutorial and my result is everything failed. Any other suggestion will be greatly appreciated
Click to expand...
Click to collapse
How did "everything fail?" Just need more details.

xKroniK13x said:
How did "everything fail?" Just need more details.
Click to expand...
Click to collapse
I've been trying this for the past 2 days. I just tried it again so I can give you details, and it worked without any issues, so I'm good.
Thanks to all the previous posters, and the house of moto maker.

Rsdlite Fastboot Flash Fail with System.img

Hey all,
Recently had various issues with my phone. My phone is now permenantley stuck into fastboot mode. I try to flash a firmware with RSD lite and I get an error after trying to flash the 15th of the 17th element of the file: Failed flashing process. 15/17 flash system "system.img" -> Phone returned FAIL. Any help to get my phone in nromal mood.
Thanks!

We need more details like the system version you are trying to install, unlocked bootloader?

More importantly: what's your device status? (0 or 3?)

zaibysk said:
Hey all,
Recently had various issues with my phone. My phone is now permenantley stuck into fastboot mode. I try to flash a firmware with RSD lite and I get an error after trying to flash the 15th of the 17th element of the file: Failed flashing process. 15/17 flash system "system.img" -> Phone returned FAIL. Any help to get my phone in nromal mood.
Thanks!
Click to expand...
Click to collapse
You're probably using too old version of RSD lite (which can't flash bigger system images).
Please use RSD lite 6.1.5 or newer.

This. A few peoples have been bricking their phones that way for some reasons. I try to use the latest I can find.

Dr. Mario said:
This. A few peoples have been bricking their phones that way for some reasons. I try to use the latest I can find.
Click to expand...
Click to collapse
i have done.. with new version of RSD lite... thanks

Can't get December 2016 security OTA.

Hey guys, a while ago I tried going back to stock with the official Motorola Factory image. I wasn't getting any security OTAs, so I tried again with this image: CLARK_RETUS_6.0_MPHS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip by Motorola-Firmware-Team It was an update behind despite being uploaded on 1/26/17. I totally reset my phone and now I'm getting the latest update notification, but it won't update because of this error: [IMG="Sorry for the BLUR (see what I did there?)"]
I get that this error happens a lot and yes, I know I went back to stock correctly and I'm pretty sure I flashed my modem correctly. Anyone know what I'm doing wrong?

pswiifanwmi said:
Hey guys, a while ago I tried going back to stock with the official Motorola Factory image. I wasn't getting any security OTAs, so I tried again with this image: CLARK_RETUS_6.0_MPHS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip by Motorola-Firmware-Team It was an update behind despite being uploaded on 1/26/17. I totally reset my phone and now I'm getting the latest update notification, but it won't update because of this error: [IMG="Sorry for the BLUR (see what I did there?)"]
I get that this error happens a lot and yes, I know I went back to stock correctly and I'm pretty sure I flashed my modem correctly. Anyone know what I'm doing wrong?
Click to expand...
Click to collapse
We can't see your image of your error. Can you link a screen shot on imgur or something?

acejavelin said:
We can't see your image of your error. Can you link a screen shot on imgur or something?
Click to expand...
Click to collapse
Whoops! Sorry 'bout that! Okay, XDA won't let me post pictures since I haven't posted enough so let me try this. imgur . com / a / wYX1F
Does that work?

pswiifanwmi said:
Whoops! Sorry 'bout that! Okay, XDA won't let me post pictures since I haven't posted enough so let me try this. imgur . com / a / wYX1F
Does that work?
Click to expand...
Click to collapse
Yeah, I got it... You have a incomplete flash on 18-8 or you used a ROM not for your device. You need to reflash the modem stack from 18-8 image and try the update again.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify an OKAY after each step, if you don't get one, do it again.
Then if it still fails to update, can you post output of `fastboot getvar all` and mask out your IMEI number?

acejavelin said:
Yeah, I got it... You have a incomplete flash on 18-8 or you used a ROM not for your device. You need to reflash the modem stack from 18-8 image and try the update again.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify an OKAY after each step, if you don't get one, do it again.
Then if it still fails to update, can you post output of `fastboot getvar all` and mask out your IMEI number?
Click to expand...
Click to collapse
How did you know that would work?! The script I've been running had those steps in them and they said okay each time, so what made this attempt any different? Was it the cache clearing that happened right afterward that messed everything up or the lack of a reboot after flashing system, recovery, logo and boot?
I used the same files I'd been using, but I copied them again for good measure. Guess they got corrupted the first time huh?
Thanks so much for your help!

pswiifanwmi said:
How did you know that would work?! The script I've been running had those steps in them and they said okay each time, so what made this attempt any different? Was it the cache clearing that happened right afterward that messed everything up or the lack of a reboot after flashing system, recovery, logo and boot?
I used the same files I'd been using, but I copied them again for good measure. Guess they got corrupted the first time huh?
Thanks so much for your help!
Click to expand...
Click to collapse
Lucky guess, and I figured it was a radio issue from the error message. And I know the modem stack messes up a lot, especially when flashed too fast... There is a reason we recommend doing it manually and not with a script. ?

Installing updates after flashing back to stock

So I just flashed back to stock using this method, https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 and I was wondering if I can install updates that are pushed to me? After rebooting following the back to stock method I got a notification but it failed when I tried to install the update, I read that it doesn't matter if your bootloader is unlocked as long as your running stock updates should install, and I read that here https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 but it still failed.

MrKite4 said:
So I just flashed back to stock using this method, https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 and I was wondering if I can install updates that are pushed to me? After rebooting following the back to stock method I got a notification but it failed when I tried to install the update, I read that it doesn't matter if your bootloader is unlocked as long as your running stock updates should install, and I read that here https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 but it still failed.
Click to expand...
Click to collapse
What was the exact error? The recovery logs will tell you before you before it reboots...
Because OTA's do work after returning to stock, it has been tried and tested hundreds, probably thousands, of times.

acejavelin said:
What was the exact error? The recovery logs will tell you before you before it reboots...
Because OTA's do work after returning to stock, it has been tried and tested hundreds, probably thousands, of times.
Click to expand...
Click to collapse
I only get the little android guy on his back with the exclamation point and under it it says Error, then I'm forced to hold down the power button to reboot at which point I get the message popping up on my phone after the reboot saying "Software Update Unsuccessful. Sorry there was a problem updating your Moto X Pure Edition. No changes were made"

MrKite4 said:
I only get the little android guy on his back with the exclamation point and under it it says Error, then I'm forced to hold down the power button to reboot at which point I get the message popping up on my phone after the reboot saying "Software Update Unsuccessful. Sorry there was a problem updating your Moto X Pure Edition. No changes were made"
Click to expand...
Click to collapse
At that point, press Power and tap Vol Up and select Recovery Logs from the menu to see the full error message.

acejavelin said:
At that point, press Power and tap Vol Up and select Recovery Logs from the menu to see the full error message.
Click to expand...
Click to collapse
Alright, let me try that and see what happens.

acejavelin said:
At that point, press Power and tap Vol Up and select Recovery Logs from the menu to see the full error message.
Click to expand...
Click to collapse
This is what I'm getting,
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: motorola/clark_retus/clark:6.0M
PHS24.49-18-4/5:user/release-keys
Target: motorola/clark_retus/clark:6.0M
PHS24.49-18-8/4:user/release-keys
Verifying current system...
"/modem/image/adsp.b01" has unexpected contents.
E:Error in /cache/Blur_Version.24.221.4.clark_retus.retus.en.US.zip
(Status 7)
Installation aborted.

As I expected... it's a modem issue. You need to reflash the modem stack from MPHS24.49-18-4 firmware image with fastboot, then it should apply properly.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify an OKAY response after each step... you might have to do a step more than once., then do the update and it will work.

acejavelin said:
As I expected... it's a modem issue. You need to reflash the modem stack from MPHS24.49-18-4 firmware image with fastboot, then it should apply properly.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify an OKAY response after each step... you might have to do a step more than once., then do the update and it will work.
Click to expand...
Click to collapse
Worked perfectly, you're the sh*t, thank you.

MrKite4 said:
Worked perfectly, you're the sh*t, thank you.
Click to expand...
Click to collapse
Since you found the solution, it would be good if you edit the OP and add a solution section below it. That will help people who might face this error in future.

AsquareX said:
Since you found the solution, it would be good if you edit the OP and add a solution section below it. That will help people who might face this error in future.
Click to expand...
Click to collapse
I was actually trying to add "SOLVED" to my main title but I cannot edit it, only the body of my OP.