Related
Do you want the fastboot files for ics (official AT&T US)?
well its all (or almost all) here!!!
Note: This is the minimal standard that is just missing the system.img and the junk apps in the preinstall partition, we should get it with the %100 OEM official .
Also: I'm not responsible if this brick's your Atrix 2!!!
And finally, the download link:
Minimal
Minimal Standard
Cheers,
TCF38012
PS: Don't flash your own system.img this WILL SOFT BRICK YOUR DEVICE.
List of Images Needed(by priority):
1. System (DON'T USE THE SOUTH AFRICIAN ONE AND SOFT BRICK)
Reserved.
Good job man!
It's important to have an ICS FXZ.
Sent from my MB865 using xda app-developers app
sad_but_cool1 said:
Good job man!
It's important to have an ICS FXZ.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but it is incomplete so don't totally rely on it.
So what happens if you bork your system image? Have you tested that yet?
I do see you are looking for a system image, but I am curious how this can save you from a boot loop without that.
Nice start though.
jimbridgman said:
So what happens if you bork your system image? Have you tested that yet?
I do see you are looking for a system image, but I am curious how this can save you from a boot loop without that.
Nice start though.
Click to expand...
Click to collapse
Thanks.
I have every image now except for radio.
I'll upload the final one for the second leak when I make the most hardest part(radio.img)
tcf38012 said:
Thanks.
I have every image now except for radio.
I'll upload the final one for the second leak when I make the most hardest part(radio.img)
Click to expand...
Click to collapse
You can grab it off the phone and use the ext4utils to package it up, there are few guides on how to do it for the og atrix, and you can figure the rest out from there.... that is similar to how I have done it.
Don't we have to worry about the certs on those missing img files? From my understanding, you can't just dd/cat those images and flash on anyone's phone.. and from some of our previous tests with mtnlion.. we've tried that.
Or, would everyone have to make their own images? Found this in a post by whirleyes (not sure how much weight it holds, but similar idea):
whirleyes said:
Next time you got it back from service, do
Code:
cat /dev/block/system > /mnt/sdcard/system.img
& put it somewhere safe.
It seems that you can restore own system partition backup from fastboot.
Condition :
bootloader won't check security certificate when restored from own backup
you must used moto-fastboot.exe & not fasboot.exe
Click to expand...
Click to collapse
I would really like to see this fxz come to life though... keep it up.
alteredlikeness said:
Don't we have to worry about the certs on those missing img files? From my understanding, you can't just dd/cat those images and flash on anyone's phone.. and from some of our previous tests with mtnlion.. we've tried that.
Or, would everyone have to make their own images? Found this in a post by whirleyes (not sure how much weight it holds, but similar idea):
I would really like to see this fxz come to life though... keep it up.
Click to expand...
Click to collapse
Yes that works with moto-fastboot since it does not check during flashing. Now booting those is another issue. The boot image is the one to really worry about. System image and others not so much, even the recovery image is not signed.
jimbridgman said:
Yes that works with moto-fastboot since it does not check during flashing. Now booting those is another issue. The boot image is the one to really worry about. System image and others not so much, even the recovery image is not signed.
Click to expand...
Click to collapse
Right, but whirleye's was saying the certs aren't checked only if you flash your own system.img on your own phone.. or that's what i took away from it. Plus, we flashed the ICS system and boot from your phone on mtnlion's, and he came out with new CG errors.. still stuck in fastboot.
I guess this is a good place to elaborate on all of this.. if it's not considered hijacking.
@tcf38012 - has this been tested?
alteredlikeness said:
Right, but whirleye's was saying the certs aren't checked only if you flash your own system.img on your own phone.. or that's what i took away from it. Plus, we flashed the ICS system and boot from your phone on mtnlion's, and he came out with new CG errors.. still stuck in fastboot.
I guess this is a good place to elaborate on all of this.. if it's not considered hijacking.
@tcf38012 - has this been tested?
Click to expand...
Click to collapse
Right, that is why I was saying that flashing is easy, but booting is much harder with the locked bootloader checking the signature before booting, hence the cg errors from MY image on someone else's phone.
Updated 10/14/2012!!!
Cheers!!!
tcf38012 said:
Updated 10/14/2012!!!
Cheers!!!
Click to expand...
Click to collapse
So what exactly is this and how do we use it?
Sent from my MB865 using xda premium
tmease1 said:
So what exactly is this and how do we use it?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
It is the partial fastboot files for ATT US 4.0.4. Nothing like a bootloader unlock or jellybean. When you are softbricked, just use these in AP fastboot and you are back to normal
Cheers!!!
I do not understand exactly how this works, please be more explicit.
Well let me know if this would work for me, my problem was that upgrading from GB to ICS 2.3.6 Official OTA, everything worked well and use the computer all day, until it froze and reboot and get stuck in the Motorola logo and back and restarted.
Andr3s said:
I do not understand exactly how this works, please be more explicit.
Well let me know if this would work for me, my problem was that upgrading from GB to ICS 2.3.6 Official OTA, everything worked well and use the computer all day, until it froze and reboot and get stuck in the Motorola logo and back and restarted.
Click to expand...
Click to collapse
This may help you since it sounds like you are softbricked. At this point you have nothing to lose and the boot.img is already there on your phone. Give it a shot and if it doesn't work you may be able to take it to AT&T since it was the official OTA that bricked ya. Good luck!!!
Ok friend, another question, as I use the files that I download, Minimal, Minimal Standard? also you do with South Africa FXZ file?
regards
Andr3s said:
Ok friend, another question, as I use the files that I download, Minimal, Minimal Standard? also you do with South Africa FXZ file?
regards
Click to expand...
Click to collapse
Minimal Standard. All you need from the South Africa FXZ is the system.img and flash with "moto-fastboot flash system system.img". Don't flash anything else from the South Africa FXZ.
Cheers!!!
Ok to get this straight, first put the phone in Fastboot bike, then unzip the file 4.0.4_67.21.125_edison_fxz_minimal_standard, run the file and then run flash.bat "moto-fastboot flash system system.img" with the system.img? That is so true?
if this is so I could include the system.img file in the same folder and add the file. bat line "moto-fastboot flash system system.img"?
Hello, after doing all this, I have this problem
Invalid CG OTV (CG: systema): Invalid SP Data
Invalid CG HAB (CG: system, status: 0X0056)
Invalid CG OTV (CG: system)
sending 'mbm' (256 KB)... OKAY [ 0.024s]
writing 'mbm'... OKAY [ 0.466s]
rebooting into bootloader... OKAY [ 0.285s]
sending 'mbmloader' (41 KB)... FAILED (command write failed (No such file or
directory))
sending 'mbm' (256 KB)... FAILED (command write failed (No such file or
directory))
sending 'cdt.bin' (16 KB)... FAILED (command write failed (No such file or
directory))
sending 'lbl' (16 KB)... FAILED (command write failed (No such file or
directory))
sending 'logo.bin' (854 KB)... FAILED (command write failed (No such file or
directory))
< waiting for device >
sending 'ebr' (16 KB)... OKAY [ 0.007s]
writing 'ebr'... OKAY [ 0.502s]
sending 'mbr' (16 KB)... OKAY [ 0.249s]
writing 'mbr'... OKAY [ 0.471s]
sending 'devtree' (512 KB)... OKAY [ 0.286s]
writing 'devtree'... OKAY [ 0.519s]
sending 'boot' (8192 KB)... OKAY [ 1.401s]
writing 'boot'... OKAY [ 0.877s]
sending 'recovery' (9216 KB)... OKAY [ 1.609s]
writing 'recovery'... OKAY [ 1.433s]
sending 'radio' (12080 KB)... OKAY [ 1.109s]
writing 'radio'... OKAY [ 1.906s]
sending 'cdrom' (12032 KB)... OKAY [ 1.049s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
sending 'preinstall' (262144 KB)... OKAY [ 17.227s]
writing 'preinstall'... OKAY [ 28.739s]
sending 'preinstall' (20480 KB)... OKAY [ 1.433s]
writing 'preinstall'... OKAY [ 1.901s]
sending 'system' (262144 KB)... OKAY [ 19.473s]
writing 'system'... OKAY [ 29.494s]
sending 'system' (229120 KB)... OKAY [ 15.423s]
writing 'system'... OKAY [ 25.304s]
erasing 'userdata'... OKAY [ 0.045s]
erasing 'cache'... OKAY [ 0.666s]
rebooting...
Press any key to continue . . .
Click to expand...
Click to collapse
I was running just the stock ICS on an AT&T Atrix 2. I went into Root explorer, and in System/bin i deleted both logwrapper files and the safestrap file as directed by bootmanager, then i rebooted. Well, now I get past the dual core technology screen, to the AT&T "rethink possible" logo, then nothing, no reboots, nothing. I tried wiping cache and data from stock recovery but still nothing... someone please help as this is my only phone.
My computer DOES recognize the device also. can anyone point me in the right direction to restoring my device to complete stock??
Enzopreme said:
I was running just the stock ICS on an AT&T Atrix 2. I went into Root explorer, and in System/bin i deleted both logwrapper files and the safestrap file as directed by bootmanager, then i rebooted. Well, now I get past the dual core technology screen, to the AT&T "rethink possible" logo, then nothing, no reboots, nothing. I tried wiping cache and data from stock recovery but still nothing... someone please help as this is my only phone.
My computer DOES recognize the device also. can anyone point me in the right direction to restoring my device to complete stock??
Click to expand...
Click to collapse
Can you access adb? What leak are you on?
tcf38012 said:
Can you access adb? What leak are you on?
Click to expand...
Click to collapse
yes i can get into AP fastboot, i think im on the first leak, Blur_Version.55.1.3.25.MB865.ATT.en.US is the verion i flashed to get onto ICS. I tried the "get back to 2.3.5 from ICS utility but now i cant even get to the AT&T logo i only get to the initial non animated dual core technology screen.
Enzopreme said:
yes i can get into AP fastboot, i think im on the first leak, Blur_Version.55.1.3.25.MB865.ATT.en.US is the verion i flashed to get onto ICS. I tried the "get back to 2.3.5 from ICS utility but now i cant even get to the AT&T logo i only get to the initial non animated dual core technology screen.
Click to expand...
Click to collapse
OK then downgrade to gb and update again (This will erase all your installed apps).
Fastboot Files.
You MUST use these fastboot files. If you use the original ones your are hard-bricked.
yeah thats the utility i keep trying, but its not working, i keep getting stuck at the dual core logo.... this is what happens when i run the script:
Press any key to continue . . .
Erasing Boot...
sending 'mbm' (256 KB)... OKAY [ 0.047s]
writing 'mbm'... OKAY [ 0.499s]
ECHO is off.
rebooting into bootloader... OKAY [ 0.281s]
ECHO is off.
sending 'mbmloader' (39 KB)... FAILED (command write failed (No such file or
directory))
ECHO is off.
sending 'mbm' (256 KB)... FAILED (command write failed (No such file or
directory))
ECHO is off.
rebooting into bootloader... FAILED (command write failed (No such file or
directory))
ECHO is off.
sending 'cdt.bin' (16 KB)... FAILED (command write failed (No such file or
directory))
ECHO is off.
erasing 'userdata'... FAILED (command write failed (No such file or
directory))
ECHO is off.
erasing 'cache'... FAILED (command write failed (No such file or
directory))
ECHO is off.
sending 'lbl' (16 KB)... FAILED (command write failed (No such file or
directory))
ECHO is off.
sending 'logo.bin' (854 KB)... FAILED (command write failed (No such file or
directory))
ECHO is off.
sending 'ebr' (16 KB)... FAILED (command write failed (No such file or
directory))
ECHO is off.
< waiting for device >
sending 'mbr' (16 KB)... OKAY [ 0.010s]
writing 'mbr'... OKAY [ 0.462s]
ECHO is off.
sending 'devtree' (512 KB)... OKAY [ 0.343s]
writing 'devtree'... OKAY [ 0.593s]
ECHO is off.
sending 'system' (262144 KB)... OKAY [ 26.816s]
writing 'system'... OKAY [ 23.884s]
sending 'system' (229120 KB)... OKAY [ 22.885s]
writing 'system'... OKAY [ 21.263s]
ECHO is off.
sending 'radio' (12080 KB)... OKAY [ 1.170s]
writing 'radio'... OKAY [ 1.498s]
ECHO is off.
sending 'cdrom' (12032 KB)... OKAY [ 1.716s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
ECHO is off.
sending 'preinstall' (262144 KB)... OKAY [ 26.629s]
writing 'preinstall'... OKAY [ 23.971s]
sending 'preinstall' (20480 KB)... OKAY [ 2.031s]
writing 'preinstall'... OKAY [ 2.093s]
Flashing Boot...
sending 'boot' (8192 KB)... OKAY [ 0.983s]
writing 'boot'... OKAY [ 1.217s]
Your phone is now back on stock firmware!
Press any key to reboot your phone!
If the script doesn't work, try placing the xml from the file in rsd.
Sent from my MB865 using xda premium
Axis_Drummer said:
If the script doesn't work, try placing the xml from the file in rsd.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
since he deleted the logwrapper file by mistake will pushing the logwrapper through adb work??
devilhunter47 said:
since he deleted the logwrapper file by mistake will pushing the logwrapper through adb work??
Click to expand...
Click to collapse
I would think as long as he was on ICS leak #1 for AT&T, then using this should fix it. Whether it be by the script or RSD.
That is if he can still get into AP fastboot with sufficient enough battery to go through the process.
HOWEVER, I'm not 100% sure on whether or not the logwrapper file will be replaced. But its worth trying.
Sent from my MB865 using xda premium
I got a feeling since he's failing on cdt.bin that he's on the second leak....
Sent from my SAMSUNG-SGH-I727 using xda premium
Fall of Enosis said:
I got a feeling since he's failing on cdt.bin that he's on the second leak....
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
According to his post in Jim's return to GB thread, its fixed. :thumbup:
Sent from my MB865 using xda premium
Axis_Drummer said:
According to his post in Jim's return to GB thread, its fixed. :thumbup:
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
yeah Im fixed guys, thanks for everything!! It took me all night but u got it, at the end of it all i had to RSD the 2.3.5 XML 3 times, but it worked, so im satisfied!!!!
NOTE: Says when on rsd mode failed to boot 0x00001
on fastboot same + is says failed to format pds and does't connect to the pc after that
i have over 50 hours in 5 days looking for way to fix no luck .
i try my luck with Fastboot. I first tried flashing the recovery with no luck. I then tried flashing over the official moto files (boot/sytstem/....)
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.694s]
writing 'boot'... FAILED (remote: (19000008))
....
If i follow that order boot/system and recovery fail then userdata says it works and it lets me flash the other options (but clearly just says they work it looks like it's lying)
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.694s]
writing 'boot'... FAILED (remote: (19000008))
.......
C:\SDK_tools>fastboot flash userdata userdata.img
sending 'userdata' (139233 KB)... OKAY [ 11.598s]
writing 'userdata'... OKAY [ 0.164s]
finished. total time: 11.764s
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.688s]
writing 'boot'... OKAY [ 3.462s]
finished. total time: 4.151s
.....
If I try fastboot oem unlock I'm prompted with the unlock message and after hitting accept. I see the following error on the screen
ERROR: Failed to format UDA.
Error while unlocking device.
My next try was with RSD light. I tried flashing all of the images for my xoom off this site . all of them give me the following error:
Failed flashing process. Failed Flashing process. Interface AP-OS: Error flashing subscriber unit. Device API error: 0xE0020085 Address: 0x1F870 Command: ADDR (0xE0222085); phone connected
I ran out of ideas on what to do next. One post i saw said try using a nand backup but I can't find one that will work.
Any help would be great. I really love my XOOM and I'm sad i can't fix it.
Hi,
I got a notification today that the 5.0 OTA update is available for my Nexus 5. I tried doing the update and Clockwork Mod complained and the update didn't work. I decided to try doing a manual install. I downloaded the 5.0 stock image, adb executable and fastboot executable. I ran flash-all.sh script included with the stock image. It seemed the ROM installed fine but I was stuck on the boot animation for over an hour. I decided this was too long and tried flashing 4.4.4 with the same problem (downloaded the 4.4.4 stock image and ran it's flash-all.sh script), boot animation kept going.
I tried installing a TeamWin as a recovery because some googling told me that the Dalvik Cache may not have been wiped correctly. I tried wiping Dalvik (and everything else) but they all errored out. I completely formatted everything (had the type "yes" for TeamWin to let me). Once again I tried installing 5.0 and had the same problem.
I did some more googling and some people suggested using ClockworkMod. I flashed ClockworkMod, wiped everything (user data, cache and dalvik) and am now stuck on the boot animation of 4.4.2. I'm running out of ideas and I hope someone else knows what's going on.
Every time that I tried running the flash-all.sh script of any of the stock images I get output very similar to the following:
ERROR: could not get pipe properties
sending 'bootloader' (2508 KB)...
OKAY [ 0.191s]
writing 'bootloader'...
OKAY [ 0.478s]
finished. total time: 0.669s
ERROR: could not get pipe properties
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
ERROR: could not get pipe properties
sending 'radio' (42049 KB)...
OKAY [ 1.427s]
writing 'radio'...
OKAY [ 2.891s]
finished. total time: 4.317s
ERROR: could not get pipe properties
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
ERROR: could not get pipe properties
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-1.0.25.0.23
Serial Number........: 0489450843835f19
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8628 KB)...
OKAY [ 0.490s]
writing 'boot'...
OKAY [ 0.745s]
sending 'recovery' (9210 KB)...
OKAY [ 0.535s]
writing 'recovery'...
OKAY [ 0.773s]
sending 'system' (702500 KB)...
OKAY [ 22.241s]
writing 'system'...
OKAY [ 48.088s]
erasing 'userdata'...
OKAY [ 14.391s]
erasing 'cache'...
OKAY [ 0.550s]
rebooting...
Also, for what it's worth, when trying to figure out my problem with TeamWin I noticed that a message to the effect of "full SELinux support is present".
Does anyone happen to know what's going on?
EDIT: I'm doing this on OS X 10.9
Did you try turning it on and off again?
Quit using custom recoverys and root, in fact, dont even try to root after you install Lollipop. If you are in Fastboot mode/bootloader and it isnt working then you should verify the integrity of the file and try a better USB cable that is dedicated for file transfer, not the cheap stock one. I flashed mine in 2 mintues no problem 5 mintues to load
EDIT: You also have to update your fastboot drivers and adb, there is a new one
Well...I fixed it. I can't say for sure but I think I may have had a bad fastboot executable. I followed this guide and installing 4.4.2 worked perfectly.
Try extracting the .img files and use fastboot to flash them manually. It installed fine for me without errors.
I m using Droid Ultra (xt1080) SU6-7.7 and i was trying to flash the same firmware because the previous one was corrupted and wifi and bluetooth stoped working and settings began to crash , etc.
I downloaded RSD Lite latest version and adb drivers and stuff and i charged the phone to 100% and finally started flash and it went good in the start but when it began to flash system.img it took a long time and FAILED. with a message on the screen "invalid entry hash for system index=0"
I also tried House Of Moto , Adb and Fastboot but it also gives the error: "invalid sparse file format at header magi". PLEASE HELP ME OUT OF THIS MY DEVICE IS BRICKED
the firmware i m trying to flash " VZW-4.4.4-SU6-7.7-release-keys.xml.zip "
DeXtern00b said:
I m using Droid Ultra (xt1080) SU6-7.7 and i was trying to flash the same firmware because the previous one was corrupted and wifi and bluetooth stoped working and settings began to crash , etc.
I downloaded RSD Lite latest version and adb drivers and stuff and i charged the phone to 100% and finally started flash and it went good in the start but when it began to flash system.img it took a long time and FAILED. with a message on the screen "invalid entry hash for system index=0"
I also tried House Of Moto , Adb and Fastboot but it also gives the error: "invalid sparse file format at header magi". PLEASE HELP ME OUT OF THIS MY DEVICE IS BRICKED
the firmware i m trying to flash " VZW-4.4.4-SU6-7.7-release-keys.xml.zip "
Click to expand...
Click to collapse
did you verify md5 checksum?
sd_shadow said:
did you verify md5 checksum?
Click to expand...
Click to collapse
How to do that.... i m a noob in android....
Thanks in Advance
sd_shadow said:
did you verify md5 checksum?
Click to expand...
Click to collapse
i dont think its something wrong in the file because i have tried download the file twice and from other websites either
Nothing wrong in md5
sd_shadow said:
did you verify md5 checksum?
Click to expand...
Click to collapse
@sd_shadow i just confirmed the md5 and its the same in the xml.... and when i flash it manualy in fastboot i get the error : Cannot load system.img: Not enough space..
please tell me what to do.... my device is nearly bricked and i have lost all hope
DeXtern00b said:
@sd_shadow i just confirmed the md5 and its the same in the xml.... and when i flash it manualy in fastboot i get the error : Cannot load system.img: Not enough space..
please tell me what to do.... my device is nearly bricked and i have lost all hope
Click to expand...
Click to collapse
try mfastboot
Code:
mfastboot flash system system.img -P
Still no luck
sd_shadow said:
try mfastboot
Code:
mfastboot flash system system.img -P
Click to expand...
Click to collapse
Thats what i got after your command : @sd_shadow
C:\android-sdk-windows\platform-tools>mfastboot flash system system.img -P
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [ 68.798s]
writing 'system'...
OKAY [ 25.042s]
sending 'system' (262144 KB)...
OKAY [ 60.104s]
writing 'system'...
OKAY [ 25.229s]
sending 'system' (262144 KB)...
OKAY [ 35.584s]
writing 'system'...
OKAY [ 24.540s]
sending 'system' (262144 KB)...
OKAY [ 29.200s]
writing 'system'...
OKAY [ 23.672s]
sending 'system' (262144 KB)...
OKAY [ 16.759s]
writing 'system'...
OKAY [ 23.892s]
sending 'system' (7783 KB)...
OKAY [ 0.813s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 334.857s
@sd_shadow is there a way o flash another Os in fastboot like ubuntu or something to unbrick the dev if not then how do i flash android back on it? :/
DeXtern00b said:
@sd_shadow is there a way o flash another Os in fastboot like ubuntu or something to unbrick the dev if not then how do i flash android back on it? :/
Click to expand...
Click to collapse
no
Sent from my KFFOWI using XDA Labs
@sd_shadow then how can i unbrick it
DeXtern00b said:
@sd_shadow then how can i unbrick it
Click to expand...
Click to collapse
try flashing just the boot.img then reboot
Sent from my DROID Turbo using XDA Labs
Still no luck
sd_shadow said:
try flashing just the boot.img then reboot
Sent from my DROID Turbo using XDA Labs
Click to expand...
Click to collapse
No Valid PIV block in SP for system
piv validation failed (system)
Boot up failed @sd_shadow