Database Develop

[Q] Im brick my AHD AT&T on JB flashing MB886_niimx-user-4.1.2-9.8.2Q-50_MB886

I made the mistake of flash this file MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-AHD MX.xml.zip in my AHD AT&T on JB 4.1.1, now when I try to flash, I get this error:
RSDLite: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL.
ATRIX HD: security downgraded version
gpt_main version update failed
preflash validation failed for GPT.
any ideas to fix this?
PD. Excuse my english

How is there a Mexican firmware for this phone??? I haven't seen this phone available in Mexico...

3z3-8917 said:
I made the mistake of flash this file MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-AHD MX.xml.zip in my AHD AT&T on JB 4.1.1, now when I try to flash, I get this error:
RSDLite: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL.
ATRIX HD: security downgraded version
gpt_main version update failed
preflash validation failed for GPT.
any ideas to fix this?
PD. Excuse my english
Click to expand...
Click to collapse
+1

joel_sinbad said:
How is there a Mexican firmware for this phone??? I haven't seen this phone available in Mexico...
Click to expand...
Click to collapse
Yes the mexican firmware is avaliable for dowload in sbf.droid-developers, but it's but it's no compatible with AHD AT&T.
I lost the signal constantly in my AHD AT&T 4.1.1 stock JB, for that reason I flashing mexican firmware for fix this, but I brick my phone, not is posible reflashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip, I get this error en RDS: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL

3z3-8917 said:
Yes the mexican firmware is avaliable for dowload in sbf.droid-developers, but it's but it's no compatible with AHD AT&T.
I lost the signal constantly in my AHD AT&T 4.1.1 stock JB, for that reason I flashing mexican firmware for fix this, but I brick my phone, not is posible reflashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip, I get this error en RDS: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL
Click to expand...
Click to collapse
I learned YEARS ago never to flash an sfb\fastboot\odin\whatever if its not made specifically for your device+OS+carrier until the super smarts have determined if the signatures\values are compatible (or wait until a post like this shows up ). Motorola's notorious for setting up sbf's in a way that will brick you, prevent you from ever going back to stock, and\or downgrading. Knowing that, I made a rom from MR instead of flashing the fastboot.
ATRIX HD: security downgraded version -- that line worries me the most, especially if that's what it says if you're trying to flash AT&T now -- It could mean that MR has a higher CG value than AT&T. You'll never be able to install the AT&T fastboot again if that ends up being the case -- you've blown an efuse.
I'm gonna need some more details: Did the MR flash fully finish the first time used? If it fully finished and didn't boot or loops, do a factory reset in the stock reocovery. You could also try to unlock the bootloader (worth a shot at any rate) -- seems like you still have fastboot access so its at least worth trying -- it would be great if MR is the secret fastboot that unlocks us (I mean, the rom itself has no entitlement checking whatsoever, maybe its bootloader doesn't either...)
.
Can you still access SS or does it boot directly into fastboot\stock recovery? . If fastboot only, try flashing just the boot.img from the fastboot (probably won't work if an efuse has been blown). If you still have SS then we can put the boot.img in a zip and flash that -- its how we safely tested Defy sbf's without blowing an efuse.
After trying all of the above and if none of them work you should attempt flashing the Bell JB fasboot as a last ditch effort.

loading into fastboot only with error "flash failure"

marshok said:
loading into fastboot only with error "flash failure"
Click to expand...
Click to collapse
I'm not really sure what to tell you. You could try flashing just AT&T boot.img and devtree....Maybe make a hybrid fastboot, replace what fails during the AT&T flash with files from the MR fastboot (and modify the xml accordingly). Since it seems you're using the MR fastboot menu it, trying the unlock command is worth a shot.
All my other suggestions involve trying to connect directly to the nand and manually dd in the mbr and such -- I've never even tried connecting to my phone like that, so you'll have to search for those methods on your own, sorry. You'll also be diving in to full on brick territory too. You're just semi bricked, so you can still get lucky if you don't change that.
There is still hope (maybe) -- Apparently 4.2 is in testing and a fastboot should pop up for it before or after it's released. If its like every other major sbf\fastboot release I've seen it should have higher signatures\cg values and could possibly be a fix for you. That's all an assumption, but its based on credible rumor (a Mattlgroff post) and Motorola's past actions. The point is -- You still have access to fastboot, don't do anything to screw that up because your needed fix might not be available yet.
Or you could send in your phone for warranty; check Motorola's website to see if your still covered under factory warranty -- I am and my phone is a 99 cent refurbished model -- I still have 11 months left You get 12-24 months coverage when you register (length depends on New or Refurb). I was truthful on my Purchase Date, but I suppose you could lie and say you just recently bought it and it quit working when you started to upgrade it.

Did the MR flash fully finish the first time used?
Click to expand...
Click to collapse
no the flashing not completed, I got the error just flash boot.img
You could also try to unlock the bootloader (worth a shot at any rate) -- seems like you still have fastboot access so its at least worth trying -- it would be great if MR is the secret fastboot that unlocks us (I mean, the rom itself has no entitlement checking whatsoever, maybe its bootloader doesn't either...)
Click to expand...
Click to collapse
how I can do this? when my AHD is briked
Can you still access SS or does it boot directly into fastboot\stock recovery? . If fastboot only, try flashing just the boot.img from the fastboot (probably won't work if an efuse has been blown). If you still have SS then we can put the boot.img in a zip and flash that -- its how we safely tested Defy sbf's without blowing an efuse.
Click to expand...
Click to collapse
if boot directly into fastboot and I have acces stock recovery
After trying all of the above and if none of them work you should attempt flashing the Bell JB fasboot as a last ditch effort.
Click to expand...
Click to collapse
I try flash Bell JB fasboot and I get the same error
thanks for your help skeevy420
PD. Excuse my english

del

3z3-8917
How do you help skeevy420?
you have restored your phone after flashing on MB886_niimx-user-4.1.2-9.8.2Q-50_MB886?

In the same boat
Hey guys I'm in the same boat. I rooted my Atrix HD and was happy until I installed busy box 9.2, which managed to overwrite /system/bin and I don't know what else I could no longer mount/remount, change w/r in root, use the ls or many other commands and wifi, mobile data, bluetooth, or OS factory reset all gone.
I should have made a copy of my system before doing anything else but I went ahead and used the boot menu recovery, which didn't do anything to help the problem.
I then flashed the MR rom with RSD Light in an attempt to recovery my phone, it was 4.1.2 and seemed like a good (hindsight horrible) idea at the time.
Now I can fastboot flash recovery images from att JB but it does no good because the boot partition fails. The RSD Light MR boot flash failed but somehow the security version stuck, and the Bell 4.1.2, Att 4.1.1, and 7.7.1Q-144, roms boot.img all return Partition (boot) Security Version Downgraded. If anyone knows a way around this please let me know.
It seems kind of tragic that Dan's bootloader unlocking came out, pretty much the day after I got stuck in this locked bootloader loop

You have to use a special xml, unzip your stock-rom replace the old xml with this one: for ICS and this one for JB.
Then try to flash it again with https://www.box.com/s/cmoz84iachug77tghdlo version of rsd lite. Make sure you have these latest drivers.

3z3-8917 said:
Yes the mexican firmware is avaliable for dowload in sbf.droid-developers, but it's but it's no compatible with AHD AT&T.
I lost the signal constantly in my AHD AT&T 4.1.1 stock JB, for that reason I flashing mexican firmware for fix this, but I brick my phone, not is posible reflashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip, I get this error en RDS: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL
Click to expand...
Click to collapse
it can fix?????? i did the same flash at my atrix hd

rorrito said:
it can fix?????? i did the same flash at my atrix hd
Click to expand...
Click to collapse
for the moment it's not possible, wait bootloader unlock tool for AHD briked....

Codex01 said:
You have to use a special xml, unzip your stock-rom replace the old xml with this one: for ICS and this one for
JB
Then try to flash it again with this version of rsd lite. Make sure you have these latest drivers.
Click to expand...
Click to collapse
Ok downloaded the JB you linked and upgraded from RSD Light 6.1.4 to 6.1.5, I edited the XML to remove getvar, and ran RSD Light but it still fails on step 1.
"Failed Flashing Process 1/23 "gpt_main0.bin -> Phone returned FAIL."
On the Phone "preflash validation failed for gpt_main0.bin"
The only stock rom that made it past step 1 has been the MR that bricked my phone, so I replaced the system.img, boot.img, and recovery.img of the MR with the JB 4.1.1 you linked but it still fails at step 15, flashing boot.img. Preflash validation falure

BRICK AHD
Exactly same situation here, Flashing Mexican Firmware.
Now i got Partition (Boot) Security Version Downgraded
Hope it can be fixed:crying:

fix fail on part 1 rsd
use the stickyboot fix from general got it from skeevydude it works, try using mythtools after!
ickysjazz said:
Exactly same situation here, Flashing Mexican Firmware.
Now i got Partition (Boot) Security Version Downgraded
Hope it can be fixed:crying:
Click to expand...
Click to collapse

Shame on me :S
Well, I just bricked an ATT AHD in the same manner, trying to flash the Mexican JB version (I bought 3 of this phones to sell here in Mexico and wanted them to look as the phones they sell here by replacing the broken digitizers with ones with no ATT logo and flashing local firmware) ...But yeah, I made a big mistake, I wasn't aware I had to unlock BL before flashing other carrier SBF's... :S At least I've learned from this and didn't made the same mistake with the other 2 AHD's I have (And I'm planning to go back to stock and deodex em' because Mex fw isnt working pretty well on this AHD's...)
Trying to repair this thing by reflashing ATT JB stock fw... RSD & Myth seem not to work;
-In RSD I can't even get past step 1/23 (flash partition "gtp_main0.bin" failed"); when trying to flash Mexican rom I got to step 15/23 till I got the error.
-In Myth It looks like some files get flashed (It even gets me to the "Load Recovery" option, I obviously choose Stock as I don't want to f'up the phone even more ) and then "finishes" but when rebooting, shows "Dual Core tech" bootscreen and sends me back to Fastboot (Reason: Sticky bit factory_fastboot), tried stickyboot solution on cmd and then reflash on myth, same result.
Also I get the messages "downgraded security version" and "Invalid PIV Image: System" in AHD Fastboot. I don't know what else to do now, I still haven't tried Bell rom as I think I'll mess things up even more so I've stayed away from it At this point I guess I'm pretty much f***ed...

@ickysjazz
@vananucho
You're using the wrong fastboot...I can tell that by the error code...use snapdragon fastboots...those are the only ones for us to use. Any other fastboot will result in errors.
So Download those
DL Mex Retail
Extract it
Open terminal to that extracted directory
Do the sticky_bit fix.
Do these commands in this order
Code:
fastboot flash partition gpt_main0.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot flash cdrom cdrom
fastboot erase cache
fastboot erase userdata
And that's how you manually flash a fastboot. I've never used MythTools or RSD. That is how I do it, always have done it, always will do it -- with the same fastboot linked above with same commands posted. Those are for Mex Retail, but should work on any JB fastboot...ICS fastboots need a few minor tweaks.
Do the fastboot commands as root on Linux or as a Windows Admin (set the admin privileges for the app in the right click properties menu)

Replaced the fastboot with the one provided by Skeevydude and still get the same error but I guess it's due to the fact that I'm running out of battery (Started showing low bat advice after 3rd failed attempt, using regular cable), I'll try this again as soon as I make a flashing cable, I'll keep updated!

[Q] Need help to bring back my phone (XT1052) Up and Running

Hi All.
I was trying to install 5.1 OTA update on my phone (Moto X - XT1052), but i got below error while install :
mount point :/system location: /dev/block/platform/msm_sdcc.1/by-name/system , file system type :ext4script aborted: Package expects build fingerprint of motorola/ghost_retasia/ghost:4.4.4/KXA21.12-L1.26/18:user/release-keys or motorola/ghost_retasia/ghost:5.1/LPA23.12-15/19:user/release-keys; this device has .
Package expects build fingerprint of motorola/ghost_retasia/ghost:4.4.4/KXA21.12-L1.26/18:user/release-keys or motorola/ghost_retasia/ghost:5.1/LPA23.12-15/19:user/release-keys; this device has .
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/cache/Blur_Version.212.44.26.ghost_row.AsiaRetail.en.03.zip'
E:Error installing zip file
Later i tried to install stock kitkat 4.4 (XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip) on my phone through adb using below commands:
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
But while reboot my phone got stuck at bootloader unlocked screen.
I tried to navigate to recovery, but there was nothing in there.
Also, when I tried installing same ROM through sideload, it was throwing below error:
Finding update package...
Opening update package...
Verifying update package...
Installation aborted...
Can some please tell, what mistake I did here and how to bring back my phone Up and Running ?

rvneo said:
Hi All.
I was trying to install 5.1 OTA update on my phone (Moto X - XT1052), but i got below error while install :
mount point :/system location: /dev/block/platform/msm_sdcc.1/by-name/system , file system type :ext4script aborted: Package expects build fingerprint of motorola/ghost_retasia/ghost:4.4.4/KXA21.12-L1.26/18:user/release-keys or motorola/ghost_retasia/ghost:5.1/LPA23.12-15/19:user/release-keys; this device has .
Package expects build fingerprint of motorola/ghost_retasia/ghost:4.4.4/KXA21.12-L1.26/18:user/release-keys or motorola/ghost_retasia/ghost:5.1/LPA23.12-15/19:user/release-keys; this device has .
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/cache/Blur_Version.212.44.26.ghost_row.AsiaRetail.en.03.zip'
E:Error installing zip file
Later i tried to install stock kitkat 4.4 (XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip) on my phone through adb using below commands:
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
But while reboot my phone got stuck at bootloader unlocked screen.
I tried to navigate to recovery, but there was nothing in there.
Also, when I tried installing same ROM through sideload, it was throwing below error:
Finding update package...
Opening update package...
Verifying update package...
Installation aborted...
Can some please tell, what mistake I did here and how to bring back my phone Up and Running ?
Click to expand...
Click to collapse
Please confirm your Bootloader Version ,
Do you have 5.1 OTA for Asia Retail

siddsufiyan said:
Please confirm you Bootloader Version ,
Do you have 5.1 OTA for Asia Retail
Click to expand...
Click to collapse
yeah, OTA update version 212.44.26. avialble for software update (Attached Screenshots) for Asia Retail.
Some how i did manage to reset my phone now. but still getting error while installing lollipop update.
have attached the full logs. please refer the log and suggest me a way to update to lollipop.
I am using bootloader version 2.8.4.0.

rvneo said:
yeah, OTA update version 212.44.26. avialble for software update (Attached Screenshots) for Asia Retail.
Some how i did manage to reset my phone now. but still getting error while installing lollipop update.
have attached the full logs. please refer the log and suggest me a way to update to lollipop.
I am using bootloader version 2.8.4.0.
Click to expand...
Click to collapse
Are you using TWRP. if yes you should revert to stock try this http://forum.xda-developers.com/moto-x/general/guide-newbies-how-to-revert-to-stock-t3104208
How to check boot loader version
(check by Booting the X into Bootloader/Fastboot mode, and make note of the second line on the screen)

Could you post 5.1 retail Asia link
Sent from my XT1052 using XDA Free mobile app

Did you captured the ota? If yes then, Please Please Please provide ota link for the side load.
Sent from my XT1052

rvneo said:
yeah, OTA update version 212.44.26. avialble for software update (Attached Screenshots) for Asia Retail.
Some how i did manage to reset my phone now. but still getting error while installing lollipop update.
have attached the full logs. please refer the log and suggest me a way to update to lollipop.
I am using bootloader version 2.8.4.0.
Click to expand...
Click to collapse
can you please explain how you managed to reset phone and get back to kitkat???
I tried same as what you tried and i got stuck at same place.....
Right now am on Brasil retail version of lollipop and need to get back to asia retail kitkat, so need help in getting back....

amit.inchal said:
can you please explain how you managed to reset phone and get back to kitkat???
I tried same as what you tried and i got stuck at same place.....
Right now am on Brasil retail version of lollipop and need to get back to asia retail kitkat, so need help in getting back....
Click to expand...
Click to collapse
Please refer .. http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 .. i used the fastboot method, it worked

sroy001 said:
Could you post 5.1 retail Asia link
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
hey, i had tried copying zip file from cache, but didn.t get copied. i dont have the OTA update file with me now

rvneo said:
hey, i had tried copying zip file from cache, but didn.t get copied. i dont have the OTA update file with me now
Click to expand...
Click to collapse
Are you a soak tester?
If not can you create a twrp backup for clean 5.1?
Sent from my XT1052

[Q] Help! Moto G Dead and massive headache

Right.
So, I was opening youtube on the last version of CM 12.1. No xposed, stock kernel, XT1068 model, when all of a sudden the phone stopped working.
Youtube wasn't opening. The phone was stuck on the home screen, all I could do was just press the home/back/recent buttons. Even long pressing power button to reboot would just take me to the power menu but Wouldn't allow me to do anything.
So in the end I long pressed the power menu to force reboot the phone aaaand... stuck on the boot logo. Not on the bootanimation, on the Motorola Bootlogo.
Managed to get to fastboot mode, tried to go to recovery, but after the twrp splash screen It would reboot to the splash screen again.
So i decided to mfastboot the original firmware. Who knows? maybe something got corrupted on cm.
Now, mfastboot is giving me weird errors.
flash partition gpt.bin gives (bootloader) Preflash validation failed
flash motoboot motoboot.bin gives FAILED (data transfer failure (Unknown error))
flash boot boot.img freezes everything and i need to reboot it to try and get to fastboot again.
Anybody knows what I should do? I'm kinda desperate here...
Thanks in advance. Peace.
(by the way, latest motorola drivers, just so you know...)
EDIT. Also, on the phone, it says
"hab check failed for primary_gpt
Failed to verify hab image primary_gpt"

Hope I can help
Are you flashing a gpt.bin from a previous android version? You cannot downgrade gpt.bin or motoboot.bin so the error is normal. From what firmware version is the boot.img you are flashing from? Try downloading this twrp recovery img from here https://dl.twrp.me/titan and
Code:
fastboot flash recovery recovery.img
or
Code:
mfastboot flash recovery recovery.img
Then you can try flashing any rom like this AOSP one http://forum.xda-developers.com/moto-g-2014/development/rom-android-source-project-t3123109
Hope this helps. I understand how hard it is to have a phone that won't boot.

Maybe you should try to place the stock rom 4.4.4 and then upgrade to 5.0, with 4.4.4 rom the GPT will have a downgrade and then you update the GPT putting 5.0

LudwigFerdinand18 said:
Maybe you should try to place the stock rom 4.4.4 and then upgrade to 5.0, with 4.4.4 rom the GPT will have a downgrade and then you update the GPT putting 5.0
Click to expand...
Click to collapse
You cannot downgrade gpt

Well I somehow managed to reboot into recovery, but the great problem here is that it won't mount \data.
Now, maybe all I need is to reformat \data cause it got corrupted, but since TWRP won't mount it, I can't do much about it.
I found on another thread this command
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Which apparently formats the data partition of a phone. I suppose I'd have to change "ext4fs" into "f2fs", but I'm too scared to actually try it out.
Also because I don't know whether mmcblk0p8 is the right block for our data partition.
Jeez, I hate this.
Thanks for your help guys, but I don't think flashing recovery again would help. Nor downgrading, but I'll think about it.
EDIT.
Magic, just magic. After hours of tinkering I did EXACTLY THE SAME THINGS and now it's working. Restored the stock Rom and I'm off to install CM again.
Sorry guys and thanks so much!!!

Bricked Moto X 2014? Fastboot flashing, ADB Sideloading, Nothing Seems To Work

Bricked Moto X 2014? Fastboot flashing, ADB sideloading, nothing seems to work
Hello,
I have this Moto X 2nd gen (XT1092), and I wanted to install an Android Marshmallow OS last weekend.
I did it according to this article on XDA: http://forum.xda-developers.com/moto-x-2014/general/install-image-marshmallow-6-0-xt-1097-t3266858 , where an install image plus small install description is posted.
This is the first ‘non-standard’ thing I tried with this phone. It is not rooted, nor did I make any changes in the settings for developers, apart from enabling USB debugging. The device was running an stock version of Android 5.1, which I received the normal way(just an automatic system update).
Using some 'fastboot flash....' commands via the PC, the image should be installed. However, upon trying the first command: 'fastboot flash partition gpt.bin', the terminal responded with:
-------------------------
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.102s
-------------------------
Afterwards, my phone didnt boot to android anymore. The only thing it does is put me in "AP Fastboot Flash Mode (S)"
I have tried installing different stock Motorola images/zips for my phone, in order to try to get it back to how it was, but for every fastboot flash I want to do (except for the boot logo), I get the preflash validation error.
I also tried sideloading images via ADB via the recovery mode, bit this doesn’t work either:
When I try "adb sideload <IMAGE>.zip", it starts to send the file to the phone, and the phone receives it. Very quickly after completing the transfer, though, the phone can say two things (depending on what .zip file I try):
1.
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Package expects build fingerprint of motorola/victara_reteu/victara:5.0/LXE22.46-19.1/1:user/release-keys or motorola/victara_reteu/victara:5.1/LPE23.32-25.1/1:user/release-keys; this device has motorola/victara_reteu/victara:4.4.4/KXE21.187-42/41:user/re
Installation aborted.
2.
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
One thing to note is that when I try 'adb devices', it gives me:
-------------------------
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
TA99300SXJ sideload
-------------------------
It says that the device is in ADB sideload mode, which blocks me from using other ADB functions, like shell. Is there a way to get 'full' ADB acces?
I also tried using the official Motorola “RDS Lite” software, as some people say this can be used to correctly flash an image to the phone, but this program just does not see my phone.
I did install all drivers, and Windows recognizes the device correctly, in both fastboot and ADB (recovery) mode.
Another thing I wanted to do to solve this, is to unlock the bootloader, as some people on forums said that this would help. However, when I try “fastboot oem unlock UNIQUEKEY” with the key I got from the Motorola website, the bootloader responds with the message stating that I have to enable unlocking the bootloader via developer settings. And obviously, I cannot go to settings to enable this.
-------------------------
I’m very stuck here, and I would be the intensely happy if there would be someone around who can help me get my phone back to life!
I do have experience with flashing Android ROMs/Images/Zips, but not on Motorola devices.
I reckon that this:
“Package expects build fingerprint of motorola/victara_reteu/victara:5.0/LXE22.46-19.1/1:user/release-keys or motorola/victara_reteu/victara:5.1/LPE23.32-25.1/1:user/release-keys; this device has motorola/victara_reteu/victara:4.4.4/KXE21.187-42/41:user/re”
could possibly be caused by an incorrect zip file. If that is the case, is there any way to obtain the proper file?
I did read about some special micro USB cables connecting the normally unused pin 4. Could this be helpful?
Any help would be IMMENSELY appreciated. I'm not ready to give up the fight!
Kind regards,
Ostheer

This same thing happened to me today. Ive had my fair share of rooted phone issues but this one is a mystery to me. Ive rooted every other Moto device [G, G '14, X, X Pure] And now a new issue arises.
I used a .bat file from CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162 . It finished and booted into bootloader but wont go anywhere from there. I have a feeling Ive reset to a locked state with no boot file.
Device is LOCKED. Status Code:0
Software status: Modified
$ Normal Powerup
failed to validate boot img
boot up failed
fastboot oem get_unlock_data
(bootloader) could not get unlock data
boot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.040s
Just like you I tried several fixes and no luck.
1. ADB Lite: Same issue
2. mfastboot Same issue
3. RSD Lite: Does not recognize my devices (win 10 / sdk / all drivers / redownloaded 3 times)
4. any bat file I try / manual code / or adb all fail
There must be a solution to this. I want Marshmallow 6.0 just as much as the next guy to work on my phone. Thanks for the help

WhiteRaven96 said:
This same thing happened to me today. Ive had my fair share of rooted phone issues but this one is a mystery to me. Ive rooted every other Moto device [G, G '14, X, X Pure] And now a new issue arises.
I used a .bat file from CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162 . It finished and booted into bootloader but wont go anywhere from there. I have a feeling Ive reset to a locked state with no boot file.
Device is LOCKED. Status Code:0
Software status: Modified
$ Normal Powerup
failed to validate boot img
boot up failed
fastboot oem get_unlock_data
(bootloader) could not get unlock data
..... ..... .....
There must be a solution to this. I want Marshmallow 6.0 just as much as the next guy to work on my phone. Thanks for the help
Click to expand...
Click to collapse
At this point I would be happy to get anything to work on it, 6.0 is not a requirement for me anymore.
For me it says: "Software status: Official", and getting the unlock data works. Still can't unlock though, as this should've been enabled in settings apparently.

ostheer said:
At this point I would be happy to get anything to work on it, 6.0 is not a requirement for me anymore.
For me it says: "Software status: Official", and getting the unlock data works. Still can't unlock though, as this should've been enabled in settings apparently.
Click to expand...
Click to collapse
Well there is your problem, your bootloader is locked. You can't flash firmware that is not for your model/carrier with a locked bootloader. It absolutely will fail.
Try flashing this with mfastboot:
http://www.filefactory.com/file/i8htlx8fqpv/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml.zip
Most likely gpt.bin and motoboot will fail to flash, just keep flashing all the files even if those 2 fail.
If this works, do NOT use the OTA update to get to 6.0 there is a high probability that you will hard brick your phone if you use OTA, and there is no way to fix that currently.
Because of what you did, you will have to wait for a full 6.0 firmware for the xt1092EU. Do not flash anything else until that is released.
Sent from my XT1095 using Tapatalk

AGISCI said:
Well there is your problem, your bootloader is locked. You can't flash firmware that is not for your model/carrier with a locked bootloader. It absolutely will fail.
Try flashing this with mfastboot:
http://www.filefactory.com/file/i8htlx8fqpv/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml.zip
Most likely gpt.bin and motoboot will fail to flash, just keep flashing all the files even if those 2 fail.
If this works, do NOT use the OTA update to get to 6.0 there is a high probability that you will hard brick your phone if you use OTA, and there is no way to fix that currently.
Because of what you did, you will have to wait for a full 6.0 firmware for the xt1092EU. Do not flash anything else until that is released.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
@AGISCI,
Thank you for your reply. I am currently downloading the file you linked, and will try to flash it using mfastboot as soon as it finishes downloading.
I did indeed hear that using the OTA afterwards is not something you will want to do.

ostheer said:
At this point I would be happy to get anything to work on it, 6.0 is not a requirement for me anymore.
For me it says: "Software status: Official", and getting the unlock data works. Still can't unlock though, as this should've been enabled in settings apparently.
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...-0-xt-1097-t3266858/post64274827#post64274827 POST #33
This I think is your delay. I just woke up today and noticed my phone now says UNLOCKED I didnt do anything else but attempt all my failed steps on another computer and a reboot [which had not been done since system failure. So it boot up like it was unlocked and didnt go further. Back to bootloader mode, let see if it works
YES! Got it to load up and boot using this 6.0 zip http://forum.xda-developers.com/moto-x-2014/development/rom-installation-rsd-t3263800
However now my SIM card isnt being recognized. Which ssems to happen all the time when using a file from another country. Isnt there a simple solution for this fix?

WhiteRaven96 said:
http://forum.xda-developers.com/mot...-0-xt-1097-t3266858/post64274827#post64274827 POST #33
This I think is your delay. I just woke up today and noticed my phone now says UNLOCKED I didnt do anything else but attempt all my failed steps on another computer and a reboot [which had not been done since system failure. So it boot up like it was unlocked and didnt go further. Back to bootloader mode, let see if it works
YES! Got it to load up and boot using this 6.0 zip http://forum.xda-developers.com/moto-x-2014/development/rom-installation-rsd-t3263800
However now my SIM card isnt being recognized. Which ssems to happen all the time when using a file from another country. Isnt there a simple solution for this fix?
Click to expand...
Click to collapse
That is great news! I am still downloading the zip AGISCI linked.
So if I'm correct, in the fastboot screen it now says "device is unlocked" for you?
What steps did you make to try to unlock the bootloader?
Also, am I correct to assume that you used fastboot/mfastboot to flash your zip in the end?

How is it possible? Your bootloader just got unlocked without root!
I will be more than happy if you explain again what you did and what happend exactly.
Thanks.

Whenever you flash a firmware meant for another region/carrier, you are also flashing the modem/radio that supports that region/carrier, so you have to find the firmware that supports your device/region/carrier and flash the modem/radio from it, in bootloader mode:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
These are the files you need to flash "NON-HLOS.bin" and "fsg.mbn"

AGISCI said:
Well there is your problem, your bootloader is locked. You can't flash firmware that is not for your model/carrier with a locked bootloader. It absolutely will fail.
Try flashing this with mfastboot:
http://www.filefactory.com/file/i8htlx8fqpv/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml.zip
Most likely gpt.bin and motoboot will fail to flash, just keep flashing all the files even if those 2 fail.
If this works, do NOT use the OTA update to get to 6.0 there is a high probability that you will hard brick your phone if you use OTA, and there is no way to fix that currently.
Because of what you did, you will have to wait for a full 6.0 firmware for the xt1092EU. Do not flash anything else until that is released.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
The download completed, and I have tried flashing it using mfastboot:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
what I get is the following:
the gpt.bin and motoboot.img indeed failed, logo.bin, boot.img, recovery.img, NON-HLOS.bin and fsg.mbn succeeded.
the system.img_sparsechunk.X files give this:
-------------------------
C:\Program Files (x86)\Minimal ADB and Fastboot\VICTARA_RETEU_XT1092_5.1_LPE23.3
2-25.3_cid7_CFC.xml>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (256681 KB)...
OKAY [ 8.068s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.181s
-------------------------
while the phone responds with:
-------------------------
cmd: getvar:max-sparse-size
cmd: download:0faaa7a0
cmd: flash:system
version downgraded for system
Invalid PIV signed system image
-------------------------
Any ideas? This zip seemed to have done 'better' than other, but the phone still doesn't accept it.

ostheer said:
The download completed, and I have tried flashing it using mfastboot:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
what I get is the following:
the gpt.bin and motoboot.img indeed failed, logo.bin, boot.img, recovery.img, NON-HLOS.bin and fsg.mbn succeeded.
the system.img_sparsechunk.X files give this:
-------------------------
C:\Program Files (x86)\Minimal ADB and Fastboot\VICTARA_RETEU_XT1092_5.1_LPE23.3
2-25.3_cid7_CFC.xml>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (256681 KB)...
OKAY [ 8.068s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.181s
-------------------------
while the phone responds with:
-------------------------
cmd: getvar:max-sparse-size
cmd: download:0faaa7a0
cmd: flash:system
version downgraded for system
Invalid PIV signed system image
-------------------------
Any ideas? This zip seemed to have done 'better' than other, but the phone still doesn't accept it.
Click to expand...
Click to collapse
It sounds like the download of the .zip is corrupt. You will need to download the zip again. There is a list of md5 values in an xml file inside the zip. If the md5 is different it won't flash as a safety precaution.
Sent from my XT1095 using Tapatalk

ostheer said:
That is great news! I am still downloading the zip AGISCI linked.
So if I'm correct, in the fastboot screen it now says "device is unlocked" for you?
What steps did you make to try to unlock the bootloader?
Also, am I correct to assume that you used fastboot/mfastboot to flash your zip in the end?
Click to expand...
Click to collapse
You are indeed correct. I dont think using another computer helped, although I managed to get FLASH Partition gpt.bin to work first try. What I think happened was my friend [not knowing it was in bootloader] did the bootloader button sequence and failed so instead it just tried to boot up [Stopped @ unlocked bootloader screen]
SO after I got 6.0 to work the radio network wasnt the same so now my SIM isnt being recognized.
So I looked for a simple solution and found directions
The Radio uses these lines of the flash process:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
I searched for Moto X radio files but no luck, however I did find this link for Moto G which is everything I need to find the solution myself with instructions
http://forum.xda-developers.com/showthread.php?t=2649763
:highfive:
---------- Post added at 08:46 PM ---------- Previous post was at 08:27 PM ----------
OrenGazala said:
How is it possible? Your bootloader just got unlocked without root!
I will be more than happy if you explain again what you did and what happend exactly.
Thanks.
Click to expand...
Click to collapse
I believe that Root is a step that comes after bootloader
[YOUR PHONE]
1. unlock-Bootloader --> mfastboot oem get_unlock_data
This is the first step Motorola tells you to do. Go Here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2. Install TWRP --> mfastboot flash recovery 'your twrp.img'
At this point your phone should turn on, if not your not finished
3. Install Root --> push SuperSU-v2.--
This zip I have CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip started this whole mess but it was made to where you can relock your phone after returning it to stock. Problem was that when I ran the .bat file it never took the files so it dumped every partition THEN locked me out, or just pretended to, Im still unsure because I think all I did was try to push a flash line by line [eg. gpt.bin,motoboot,logo...] only got to motoboot and then did a reset. :highfive:

bootloader unlock question
AGISCI said:
It sounds like the download of the .zip is corrupt. You will need to download the zip again. There is a list of md5 values in an xml file inside the zip. If the md5 is different it won't flash as a safety precaution.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I checked all MD5's and compared them to the ones I generated with a MD5 checksum tool, they all match. I am downloading the zip again, but theoretically that shouldn't help as de MD5's are good.
"Invalid signed image" stays the problem here, unfortunately...
Is there no way to unlock the bootloader if you didn't enable this via settings in Android?

ostheer said:
Thanks for the reply. I checked all MD5's and compared them to the ones I generated with a MD5 checksum tool, they all match. I am downloading the zip again, but theoretically that shouldn't help as de MD5's are good.
"Invalid signed image" stays the problem here, unfortunately...
Is there no way to unlock the bootloader if you didn't enable this via settings in Android?
Click to expand...
Click to collapse
No there is no way to unlock it if you didn't.
Question what version of android were you on before you did this? 5.1? With stagefright patch?
Sent from my XT1095 using Tapatalk

AGISCI said:
No there is no way to unlock it if you didn't.
Question what version of android were you on before you did this? 5.1? With stagefright patch?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Thought so,
I was on an official 5.1 build, presumably with the patch indeed, as my phone was fully updated and the patch came out in September. For the patch I can't be 100% sure though.
I downloaded the zip for the second time, but as expected after the MD5 check, the results were the same...

ostheer said:
Thought so,
I was on an official 5.1 build, presumably with the patch indeed, as my phone was fully updated and the patch came out in September. For the patch I can't be 100% sure though.
I downloaded the zip for the second time, but as expected after the MD5 check, the results were the same...
Click to expand...
Click to collapse
I don't know if this is the reason, but maybe if you did not have the stagefright patch you need the firmware without it. Here is the 5.1 without stagefright to try:
http://www.filefactory.com/file/w34zg9w3v4h/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.1_cid7_CFC.xml.zip
Sent from my XT1095 using Tapatalk

AGISCI said:
I don't know if this is the reason, but maybe if you did not have the stagefright patch you need the firmware without it. Here is the 5.1 without stagefright to try:
http://www.filefactory.com/file/w34zg9w3v4h/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.1_cid7_CFC.xml.zip
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I am currently downloading this zip, and also some others.
Curiosity:
How is the phone actually checking the file signatures? What is it comparing them to?
I'm wondering how did I manage to make the phone unable to boot, while the bootloader doesn't allow anything to be flashed?

ostheer said:
I am currently downloading this zip, and also some others.
Curiosity:
How is the phone actually checking the file signatures? What is it comparing them to?
I'm wondering how did I manage to make the phone unable to boot, while the bootloader doesn't allow anything to be flashed?
Click to expand...
Click to collapse
The images are also signed by motorola with a special key that only they have and know. If the key does not match with your installed firmware flashing will fail.
Sent from my XT1095 using Tapatalk

AGISCI said:
I don't know if this is the reason, but maybe if you did not have the stagefright patch you need the firmware without it. Here is the 5.1 without stagefright to try:
http://www.filefactory.com/file/w34zg9w3v4h/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.1_cid7_CFC.xml.zip
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I downloaded the zip without stagefright, and flashing it using the described procedure again gave the error 'Preflash validation failed' - 'Invalid PIV signed system image'.
Strangely though, flashing motoboot.img actually did work for the first time. (!)
Also flashing the recovery.img works for most zips I tried. That's rather strange as apparently they are being checked too: flashing a twrp recovery (unsurprisingly) didn't work: "mismatched partition size (recovery)".

AGISCI said:
The images are also signed by motorola with a special key that only they have and know. If the key does not match with your installed firmware flashing will fail.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I requested a compatible stock zip from Motorola for my device, using a ticket on their site. Probably they won't be very eager to supply it though.

Soft bricked XT1052

Soft bricked when trying to flash stock 5.1 back from CM13. Somehow managed to wipe the entire phone and now all I have access to are fastboot and TWRP recovery. I have no ROM ZIPs to access in TWRP since internal storage was wiped. I tried ADB sideload but says it can't mount /data/. My computer recognises the phone as a fastboot device but not as an ADB device.
Is there any coming back from this?

I've downloaded the retail GB stock image file for XT1052 but I can't flash the partition as I just get error 'update gpt_main version failed' 'preflash validation failed for GPT'

Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed

varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I've downloaded the RetGB for 5.1 for XT1052 from here: https://firmware.center/firmware/Motorola/Moto X (1st gen-2013)/Stock/XT1052/
But it seems to be missing a number of key files that are described in option 5 of the link you posted. Am I missing something? I'm also still getting errors each time I try to flash the partition except now CMD is just showing:
"target max-download-size: 768MB error: cannot load 'gpt.bin': no error. Any ideas? Thanks.
My only other thought at this point is to try and flash a ROM in recovery using USB-OTG. Could that work? For example, if I download stock ROM or even the CM 14 I had on previously before everything got wiped and put that on an external drive and flashed in TWRP?

varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I just moved cmd.exe into my platform tools folder where everything else is and tried again to flash the partition. Instead this time I get:
C:\Android-SDK\platform-tools>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.335s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.328s
And then on the phone itself in the fastboot screen it shows:
"downgraded security version. update gpt_main version failed. preflash verification failed for GPT'. I thought this would mean the bootloader I'm trying to flash would represent a downgrade but I checked against the info.txt file in the recovery image zip and it says 30.BE which matches the 30.BE in my fastboot screen...

OK I've now got an OS. Managed to reinstall CM14 using usb-otg. Figured that was the safest bet given it was the last OS installed.
Problem I now have is that I can't get any service (I could previously on CM14 before all this happened). Is it possible that when I managed to completely wipe the phone that I would the relevant modem/radio files?
Thanks

Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Sent from my XT1060 Dev Ed

varunpilankar said:
Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Click to expand...
Click to collapse
That doesn't have my version - xt1052.
Would this be to return my mobile service? I've got back on CM14 but all my IMEI and sim data has wiped so I can't get service. Not sure if I need to use the 5.1 factory image I have and just flash modem files. Seen elsewhere that I could try
Fastboot flash modem NON-hlos.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Would that do the trick do you reckon?

Take a nandroid backup & try doing it!
There is also a 5.1 stock zip Rom & try that too, might be helpful.
Sent from my XT1060 Dev Ed

Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,

hachamacha said:
Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,
Click to expand...
Click to collapse
Thanks. Will give that a look as I would like to know how to easily go back to stock in the event of catastrophe - I've been trying to flash back using both fastboot and TWRP but it fails every time due to 'downgrade security' etc. even though I know I'm using the same bootloader as in the stock ROM.
I managed to get my IMEI and service back by flashing
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
I've now got Resurrection Remix on as I thought I'd see if that would fix my service issues (it didn't - so still had to do the steps above). But have managed to learn a lot over the past few days to bring my phone back from death! I'm mainly used to Sony phones so this has been an experience.