Related
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!
Hi all
I bought a XT862 droid 3 from ebay. The seller stated it has a bad esn with verizon.
I have unlocked it with the code I bought from http://www.cellunlocker.net/motorola-unlock.php
I can use it as a GSM/UTMS phone. I have also flashed Eclipse/Steel Droid roms with safetrap.
When I attempted to install the XT883 chinese rom,
(1) it gave me errors at the 1st step of the RSDlite method
(2) it gave me black screen after rebooting. The strange part is, although the screen is black and backlit, I can actually feel the vibration when i randomly touch and hold different part of the screen as if I am actually pressing onto the different app shortcuts on the home screen. The hardware keys vibrated when i touch them too.
Before attempting to install the XT883 rom, I did a SBF using the 1-Click method from Overlayer to revert back to .890 version.
I also have the needed files ready for flashing: XT883 SBF 57.1.60, XT883 OTA to 60.3.250, GMS_XT883_update_r7. Beside this, I also have VRZ_XT862_5.5.1_84_D3G-55_1FF_01 and the 1-Click on standby. Used RSDLite 5.6, motofail-root and moto-fastboot.
I have referred to numerous threads and forums but in vain.
http://forum.xda-developers.com/showthread.php?t=1249720
http://www.rimweb.in/forums/topic/33272-cdma-omh-motorola-droid-3/page-4#entry262490
http://mobility.forumsee.com/a/m/s/p12-9442-0134208--droid-screen-stays-black.html
http://forum.xda-developers.com/showthread.php?t=1492869
http://forum.xda-developers.com/showthread.php?t=1780737
http://forum.xda-developers.com/showthread.php?p=29781907#post29781907
http://forum.xda-developers.com/showthread.php?p=29384940#post29384940
http://forum.xda-developers.com/showthread.php?p=29354697#post29354697
http://forum.xda-developers.com/showthread.php?p=29340113#post29340113
http://forum.xda-developers.com/showthread.php?p=29133918#post29133918
http://forum.xda-developers.com/showthread.php?p=21718696#post21718696
http://forum.xda-developers.com/showthread.php?p=21710468#post21710468
http://forum.xda-developers.com/showthread.php?p=20964799#post20964799
http://forum.xda-developers.com/showthread.php?t=1780737
I have been tracking mvp3 and The Solutor replies closely on this rom, but still in vain.
Can someone please help me to resolve this problem because I need the call recording in XT883 rom.
(By the way, I have done flashing on Motorola Dext, LG and Samsung phones)
did you verify xml was complete?
did ap fastboot version change?
Sent from my XT862 using xda premium
sd_shadow said:
did you verify xml was complete?
did ap fastboot version change?
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
Hi,
How do I verify xml was complete? The download was completed successfully. No errors during unzip too.
My current boot mode selection menu & AP Fastboot is 0A.64.
Whenever I try to flash XT883, I will encounter flash fail error for cdt.bin, boot.img and recovery.img.
But I can flash from .890 to .906 back and forth without any problem with the cdt, boot or recovery.img.
[How to] Verify that your download is complete with MD5/SHA-1 Hash Checksums
AP Fastboot 0A.64 is the 906 version
yes, but it's not completely .890, you still can't flash the complete.890.xml, because the bootloader stuff can not be downgraded
I suspect that the XT883 xml, can not be flashed with the AP Fastboot 0A.64
sd_shadow said:
[How to] Verify that your download is complete with MD5/SHA-1 Hash Checksums
AP Fastboot 0A.64 is the 906 version
yes, but it's not completely .890, you still can't flash the complete.890.xml, because the bootloader stuff can not be downgraded
I suspect that the XT883 xml, can not be flashed with the AP Fastboot 0A.64
Click to expand...
Click to collapse
Do you know the link to the full .890 model ? Or the link to download the Fastboot version ? I have been hunting for weeks.
lovesg said:
Do you know the link to the full .890 model ? Or the link to download the Fastboot version ? I have been hunting for weeks.
Click to expand...
Click to collapse
you can't use the 890 .xml if AP Fastboot is 0A.64
but it's posted http://sbf.droid-developers.org/cdma_solana/list.php
and in the .906 1-click-sbf.exe + tools right at the top where it says 'D3.SBF.890.ZIP'
sd_shadow said:
you can't use the 890 .xml if AP Fastboot is 0A.64
but it's posted http://sbf.droid-developers.org/cdma_solana/list.php
and in the .906 1-click-sbf.exe + tools right at the top where it says 'D3.SBF.890.ZIP'
Click to expand...
Click to collapse
Yes I have used the D3.SBF.890.ZIP and it ran successfully but the fastboot stayed at 0A.64.
So what is the fastboot version to run the XT883?
Today, I re-run the .906 1-click restore and then I ran the .890 SBF and I realised that my Fastboot version became 0A.53.
So in this case, can I flash the XT883 with this fastboot? Does it work?
don't think anyone has reported, getting back to ap fastboot 0A.53, so I don't know
try it
sd_shadow said:
don't think anyone has reported, getting back to ap fastboot 0A.53, so I don't know
try it
Click to expand...
Click to collapse
OK I tried. It keep flashing failure at steps 6. I saw many similar post on Step 1 or 6 or 18 flash failures. Read through the thread but still cannot resolve.
How else can I flash it to XT883?
you could unzip the XT883 .xml and copy and replace files in the
.906 1-click-sbf.exe + tools, you need to figure out which ones can be replaced
or
unzip the XT883 .xml and flash with motofastboot.exe
may just want to try flashing system.img
sd_shadow said:
you could unzip the XT883 .xml and copy and replace files in the
.906 1-click-sbf.exe + tools, you need to figure out which ones can be replaced
or
unzip the XT883 .xml and flash with motofastboot.exe
may just want to try flashing system.img
Click to expand...
Click to collapse
Ok i tried that. Can boot up but the screen is black. I can feel the icon behind the "black" screen (just like my first post) but i cannot do away with the black screen.
How else can I tweak?
After following this guide, I successfully flashed the XT883
http://bbs.hiapk.com/thread-4318916-1-1.html
But there is a problem, it cannot detect my GSM sim card. It keep stating UIM card not detected. CDMA should work.
Any idea how to solve this issue?
so you flashed all these from the XT883 xml, or were some of them from 906 xml or 906.exe
{
"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"
}
I was checking the files in the 906.exe
base on that, I would flash
906.exe allow-mbmloader-flashing-mbm.bin
906.exe boot.img
XT883 cdrom
906.exe cdt.bin
906.exe device_tree.bin
XT883 ebr
XT883 lbl
XT883 logo.bin
906.exe mbn.bin
906.exe mbmloader_hs.bin
XT883 mbr
XT883 radio.img (may want to try the 906)
906.exe recovery.img
XT883 system.img
XT883 ....XT883...............xml (about 3KB)
not sure which one controls the sim, would think the radio.img
sd_shadow said:
so you flashed all these from the XT883 xml, or were some of them from 906 xml or 906.exe
I was checking the files in the 906.exe
base on that, I would flash
906.exe allow-mbmloader-flashing-mbm.bin
906.exe boot.img
XT883 cdrom
906.exe cdt.bin
906.exe device_tree.bin
XT883 ebr
XT883 lbl
XT883 logo.bin
906.exe mbn.bin
906.exe mbmloader_hs.bin
XT883 mbr
XT883 radio.img (may want to try the 906)
906.exe recovery.img
XT883 system.img
XT883 ....XT883...............xml (about 3KB)
not sure which one controls the sim, would think the radio.img
Click to expand...
Click to collapse
Ok i just tried. It goes into a bootloop.
Yes i supposed it would be the radio.img. I have flashed both the 890 or the 906 on separate occasion, same problem.
help me
lovesg said:
Hi all
I bought a XT862 droid 3 from ebay. The seller stated it has a bad esn with verizon.
I have unlocked it with the code I bought from http://www.cellunlocker.net/motorola-unlock.php
I can use it as a GSM/UTMS phone. I have also flashed Eclipse/Steel Droid roms with safetrap.
When I attempted to install the XT883 chinese rom,
(1) it gave me errors at the 1st step of the RSDlite method
(2) it gave me black screen after rebooting. The strange part is, although the screen is black and backlit, I can actually feel the vibration when i randomly touch and hold different part of the screen as if I am actually pressing onto the different app shortcuts on the home screen. The hardware keys vibrated when i touch them too.
Before attempting to install the XT883 rom, I did a SBF using the 1-Click method from Overlayer to revert back to .890 version.
I also have the needed files ready for flashing: XT883 SBF 57.1.60, XT883 OTA to 60.3.250, GMS_XT883_update_r7. Beside this, I also have VRZ_XT862_5.5.1_84_D3G-55_1FF_01 and the 1-Click on standby. Used RSDLite 5.6, motofail-root and moto-fastboot.
I have referred to numerous threads and forums but in vain.
http://forum.xda-developers.com/showthread.php?t=1249720
http://www.rimweb.in/forums/topic/33272-cdma-omh-motorola-droid-3/page-4#entry262490
http://mobility.forumsee.com/a/m/s/p12-9442-0134208--droid-screen-stays-black.html
http://forum.xda-developers.com/showthread.php?t=1492869
http://forum.xda-developers.com/showthread.php?t=1780737
http://forum.xda-developers.com/showthread.php?p=29781907#post29781907
http://forum.xda-developers.com/showthread.php?p=29384940#post29384940
http://forum.xda-developers.com/showthread.php?p=29354697#post29354697
http://forum.xda-developers.com/showthread.php?p=29340113#post29340113
http://forum.xda-developers.com/showthread.php?p=29133918#post29133918
http://forum.xda-developers.com/showthread.php?p=21718696#post21718696
http://forum.xda-developers.com/showthread.php?p=21710468#post21710468
http://forum.xda-developers.com/showthread.php?p=20964799#post20964799
http://forum.xda-developers.com/showthread.php?t=1780737
I have been tracking mvp3 and The Solutor replies closely on this rom, but still in vain.
Can someone please help me to resolve this problem because I need the call recording in XT883 rom.
(By the way, I have done flashing on Motorola Dext, LG and Samsung phones)
Click to expand...
Click to collapse
fixed the problem? I have the save problem
i was recently rooted and successfully flashed the recovery through fastboot but when trying to run install the 4.4 update i get an error message during the install. i tried to completely wipe the device but im having a problem flashing the system.img. when trying to manually flash the system.img in fastboot on windows 8.1, i keep getting an error message where fastboot stops working. anyone know what to do?
try to use fastboot in win7 compatibility mode (right click -> properties -> compatiility)
waiflih said:
try to use fastboot in win7 compatibility mode (right click -> properties -> compatiility)
Click to expand...
Click to collapse
That stopped it from crashing but the flash fails. The phone says the package is too small
did you try with mfastboot? i really don't know what's the difference, but in other threads they suggest that. A link was posted in one of those threads:
https://docs.google.com/file/d/0B9qC3vvamytkSVp0NXhlSEhZVFU/edit?usp=sharing
waiflih said:
did you try with mfastboot? i really don't know what's the difference, but in other threads they suggest that. A link was posted in one of those threads:
https://docs.google.com/file/d/0B9qC3vvamytkSVp0NXhlSEhZVFU/edit?usp=sharing
Click to expand...
Click to collapse
Yea just got it from another thread and it worked. What is the difference with mfastboot? Edit: nm you stated you don't know.
Running the install for the update now hopefully it doesn't error
Edit: it worked thanks for your help
yw, i'm charging the phone to flash the vzw
I used mfastboot to flash system and boot, but when I tried flashing recovery I got the error preflash validation failed. Any help with that?
Jelps said:
I used mfastboot to flash system and boot, but when I tried flashing recovery I got the error preflash validation failed. Any help with that?
Click to expand...
Click to collapse
same. trying to flash it with mfastboot ended up with a failed flash for me and wouldn't boot. got it going again, but still without a recovery. hopefully somebody who has experienced this also comes along.
Tanknspank said:
same. trying to flash it with mfastboot ended up with a failed flash for me and wouldn't boot. got it going again, but still without a recovery. hopefully somebody who has experienced this also comes along.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2534438
so that's the problem you're having?
alex94kumar said:
http://forum.xda-developers.com/showthread.php?t=2534438
so that's the problem you're having?
Click to expand...
Click to collapse
not to that extent, no. My device works fine, I just can't reflash recovery to have the update pass through.
Tanknspank said:
not to that extent, no. My device works fine, I just can't reflash recovery to have the update pass through.
Click to expand...
Click to collapse
Worse comes to worse you could try RSD. That should restore recovery. Just make sure you RSD with the correct fastboot files (i.e. the ones that match the version you are running)
piccit said:
Worse comes to worse you could try RSD. That should restore recovery. Just make sure you RSD with the correct fastboot files (i.e. the ones that match the version you are running)
Click to expand...
Click to collapse
Tried, but couldn't get RSD to recognize my Moto X on Windows 8.1. I can access my X through fastboot, adb and storage but it will not show in RSD to save my life. Tried compatibility modes, older versions... just about everything short of another computer which I wont be able to try until my roommate gets back.
EDIT: I can honestly say that this worked, and with a combination of mfastboot and the recovery.img from the latest sbf, I'm updating along just fine. http://forum.xda-developers.com/showpost.php?p=47635914&postcount=10
Tanknspank said:
Tried, but couldn't get RSD to recognize my Moto X on Windows 8.1. I can access my X through fastboot, adb and storage but it will not show in RSD to save my life. Tried compatibility modes, older versions... just about everything short of another computer which I wont be able to try until my roommate gets back.
EDIT: I can honestly say that this worked, and with a combination of mfastboot and the recovery.img from the latest sbf, I'm updating along just fine. http://forum.xda-developers.com/showpost.php?p=47635914&postcount=10
Click to expand...
Click to collapse
If for some reason that doesn't work out this is what I did and was able to at least flash recovery. flash partition gpt.bin flash motoboot motoboot.IMG flash boot boot.img flash recovery recovery.IMG flash system system.IMG *not sure if motoboot is necessary. Still got an error trying to install though. First 410 and then 252. Ugh.
Now that I have an unlocked bootloader I was trying to update to the newest stock version. I had modded by /system so I was unable to do an easy OTA update. I was trying to flash a system.img from here for 4.4 since that is what I was running but then fastboot threw me an error. I think it was an issue with the file since I got this error
Anyone know where I can the sbf file for our phone? I need +4.4 since that is what I was running last.
Side Question: When using TWRP to back up what format does the usb drive need to be so I can put back ups on it? FAT32?
Thanks in advance for all help
Are you using motos custom fastboot to flash the system image? The image is too large for regular fastboot, moto fastboot breaks it up into chunks to flash properly
Sent from my XT1060
rocketsaucev2 said:
Are you using motos custom fastboot to flash the system image? The image is too large for regular fastboot, moto fastboot breaks it up into chunks to flash properly
Sent from my XT1060
Click to expand...
Click to collapse
So I was using the fastboot that comes with the sdk. Where can I download motos custom fastboot? Are there any important differences from regular fastboot?
Nitro made a zip that has everything you need including the mfasboot.exe
You will need to flash the system.img with the mfastboot command instead of fastboot.
https://www.elementalxdesigns.com/e...-Edition-install-TWRP-and-how-to-flash-images
Icon000 said:
So I was using the fastboot that comes with the sdk. Where can I download motos custom fastboot? Are there any important differences from regular fastboot?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B28ubovBBGskTnBlUl9reGFzQ1E/view?usp=sharing
heres a copy of mine. Make sure you put it in the same folder as your adb or regular fastboot and use the command 'mfastboot' when flashing
rocketsaucev2 said:
https://drive.google.com/file/d/0B28ubovBBGskTnBlUl9reGFzQ1E/view?usp=sharing
heres a copy of mine. Make sure you put it in the same folder as your adb or regular fastboot and use the command 'mfastboot' when flashing
Click to expand...
Click to collapse
I tried using that it seems to have worked but now I have an issue with my system.img. It will not turn wifi on and it will not update to 4.4.4. Where can I find a good copy of 4.4.2 sbf
Icon000 said:
I tried using that it seems to have worked but now I have an issue with my system.img. It will not turn wifi on and it will not update to 4.4.4. Where can I find a good copy of 4.4.2 sbf
Click to expand...
Click to collapse
Did you flash back the original boot.img so it matches your system.img?
adm1jtg said:
Did you flash back the original boot.img so it matches your system.img?
Click to expand...
Click to collapse
I tired a whole bunch of things ended up finding 4.4.4 and using rsdlite to put it on my phone.
Thanks anyway.
Here is the fully stock Boot.img, Recovery.img and System.img. There are no modifications to any of these. This is all we have until Motorola releases full factory images for Lollipop 5.0.
For the XT1095 Pure Edition ONLY
BUILD: LXE22.46-11 (22.21.11)
http://apollyon-dev.com/motox/XT1095_Lollipop5_22.21.11_BOOT_RECOVERY_SYS.zip
md5: 43888F4EAB74600E6D6DF41FF202C9BA
here's a mirror
https://mega.co.nz/#!a9hymLCD!ek2VVQNPGmUpNHFl6WIQe8znsFtUBjbsvTu0-TyORnM
Previous builds
BUILD: LXE22.39-6 (22.11.6)
http://apollyon-dev.com/motox/XT1095_Lollipop5_22.11.6_BOOT_RECOVERY_SYS.zip
md5: 6A527AFB1DEED2248AE2D3B4ACCF04ED
here's a mirror
https://mega.co.nz/#!H0wn2LoT!hHqhasTUnLjxMxACvODWcRIrtm3jTGjg1MEqxZfP5lo
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, catches on fire or it starts WWIII. Use at your own risk.
how do you flash these, I tried both fastboot and mfastboot but both fail, they crash even
also build prop says this is 4.4.4 not 5
godutch said:
how do you flash these, I tried both fastboot and mfastboot but both fail, they crash even
also build prop says this is 4.4.4 not 5
Click to expand...
Click to collapse
you are doing it wrong...
mrvirginia said:
you are doing it wrong...
Click to expand...
Click to collapse
ok, how can we do it?
thx
overon37 said:
ok, how can we do it?
thx
Click to expand...
Click to collapse
by using mfastboot. this is for advanced users...
yes, i got it, but, can i flash it over XT1092 with Kitkat?
^^I have a conversion guide, that'd help you for sure
mrvirginia said:
you are doing it wrong...
Click to expand...
Click to collapse
so how i am supposed to flash this then?
After some experimentation I cleaned up these instructions a little bit and confirmed this method works for me for rooted (.6):
Here's what I did, real easy:
- Download mfastboot v2 from graffixnyc's thread.
- unzip boot, recovery, system imgs that you downloaded from the OP into the mfastboot folder where the mfastboot.exe is located. Open a cmd prompt on that folder.
- Put phone in fastboot, plug it in:
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
For the new radio, download it from graffixnyc's site, put in mfastboot folder and flash :
Code:
mfastboot flash modem radio.img
After you get a successful boot, put the phone back in fastboot and download CF-Auto-root from graffixnyc's post in "General". Put the CF-Auto-Root.... img (inside the zip in the /image folder) in the mfastboot folder with everything else and flash according to his instrucions :
Code:
mfastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
That's it. Nothing hard about it. Any questions let me know.
Big thanks to both mrvirginia and graffixnyc for their work on this. And of course Chainfire.
*Note- you have to be upgrading from KK for this to work. If you run into issues already on a version of 5.0 and attempt this method to "fresh install", you will get stuck at boot ani. Downgrade and then try this method again. :good:
Can someone provide the bootanimation file in system/bin?
Links dead?
Devans32 said:
Links dead?
Click to expand...
Click to collapse
Nope. they both seem to work here.
updated
for the official 22.21.11 Build.
mirror up shortly
Ok now I am getting a parse invalid file error when I try to flash the system image.
Edit; fixed. Found right files and up and running.
Sent from my Nexus 6 using XDA Free mobile app
Chronzy said:
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
Click to expand...
Click to collapse
I get the error:
Code:
Invalid sparse file format at header magi
when trying to flash system.img
I've verified MD5 of file, but I'm redownloading it. Do I need to manually split it into chunks or something?
Kallb123 said:
I get the error:
Code:
Invalid sparse file format at header magi
when trying to flash system.img
I've verified MD5 of file, but I'm redownloading it. Do I need to manually split it into chunks or something?
Click to expand...
Click to collapse
Are you using mfastboot v2?
The files in this OP worked great for me on .6, but .11's so widespread I'm not sure why one wouldn't downgrade to KK and accept the OTA? Then use chainfire's root?
Chronzy said:
Are you using mfastboot v2?
The files in this OP worked great for me on .6, but .11's so widespread I'm not sure why one wouldn't downgrade to KK and accept the OTA? Then use chainfire's root?
Click to expand...
Click to collapse
Yes, got the new mfastboot, but I've tried with old as well as mfastboot v1. I was trying to flash .11 but I got this error, so I came here to use these files but also got this error :/
EDIT: Flashed KK and upgraded .11 from there. Can't get a signal though, even after flashing my modem back..
EDIT2: erase modemst1 and modemst2 and then flashing my fsg and modem worked
Chronzy said:
After some experimentation I cleaned up these instructions a little bit and confirmed this method works for me for rooted (.6):
Here's what I did, real easy:
- Download mfastboot v2 from graffixnyc's thread.
- unzip boot, recovery, system imgs that you downloaded from the OP into the mfastboot folder where the mfastboot.exe is located. Open a cmd prompt on that folder.
- Put phone in fastboot, plug it in:
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
For the new radio, download it from graffixnyc's site, put in mfastboot folder and flash :
Code:
mfastboot flash modem radio.img
After you get a successful boot, put the phone back in fastboot and download CF-Auto-root from graffixnyc's post in "General". Put the CF-Auto-Root.... img (inside the zip in the /image folder) in the mfastboot folder with everything else and flash according to his instrucions :
Code:
mfastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
That's it. Nothing hard about it. Any questions let me know.
Big thanks to both mrvirginia and graffixnyc for their work on this. And of course Chainfire.
*Note- you have to be upgrading from KK for this to work. If you run into issues already on a version of 5.0 and attempt this method to "fresh install", you will get stuck at boot ani. Downgrade and then try this method again. :good:
Click to expand...
Click to collapse
You did this from -6 rooted? With stock recovery or TWRP?
zgroten said:
You did this from -6 rooted? With stock recovery or TWRP?
Click to expand...
Click to collapse
That was the method I used to upgrade from KK to .6. I don't understand your recovery question. All this is done in bootloader.
I think you guys would benefit from SolarTrans' guide in the "general" section... http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074
Anyone else have issues
I'm on 22.39-6 and I am having issues when the phone. Anyone else have the issue where the home and menu buttons randomly disappear? Or text messages don't appear? The only fix was to reboot the phone. I also have unresponsive issues randomly when the phone is plugged to AC power and charging. Just wondering if I'm the only one with these issues. I'm going to flash the new build, but just wondering.