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
Related
I want to go back to GB because I was having issues with ICS. I used the correct script to go back. BUT... This is what I got, and now I cannot get past the "M" Logo. I can get into fastboot but nothing more..
Checking for phone...
0A3BD3050D01D00B fastboot
If your phone serial did not show up then exit this,
reconnect your phone, and try again!
If you did see the serial then this will continue
Waiting; if you want to cancel press c (Ctrl+C)
Press any key to continue
Press any key to continue . . .
Allowing bootloader flashing
sending 'mbm' (256 KB)... OKAY [ 0.031s]
writing 'mbm'... OKAY [ 0.556s]
Flashing bootloader mbm.bin
sending 'mbm' (256 KB)... OKAY [ 0.289s]
writing 'mbm'... OKAY [ 0.559s]
Rebooting into bootloader
rebooting into bootloader... OKAY [ 0.274s]
Flashing cdt.bin
sending 'cdt.bin' (16 KB)... FAILED (command write failed (No such file or
directory))
Erasing userdata
erasing 'userdata'... FAILED (command write failed (No such file or
directory))
Erasing cache
erasing 'cache'... FAILED (command write failed (No such file or
directory))
Flashing lbl
sending 'lbl' (16 KB)... FAILED (command write failed (No such file or
directory))
Flashing logo.bin
sending 'logo.bin' (854 KB)... FAILED (command write failed (No such file or
directory))
Flashing ebr
< waiting for device >
sending 'ebr' (16 KB)... OKAY [ 0.010s]
writing 'ebr'... OKAY [ 0.514s]
Flashing mbr
sending 'mbr' (16 KB)... OKAY [ 0.274s]
writing 'mbr'... OKAY [ 0.473s]
flashing device_tree.bin
sending 'devtree' (512 KB)... OKAY [ 0.327s]
writing 'devtree'... OKAY [ 0.795s]
Flashing System
sending 'system' (262144 KB)... OKAY [ 25.115s]
writing 'system'... OKAY [ 22.656s]
sending 'system' (229120 KB)... OKAY [ 21.956s]
writing 'system'... OKAY [ 21.215s]
Flashing Boot image
sending 'boot' (8192 KB)... OKAY [ 0.819s]
writing 'boot'... OKAY [ 1.449s]
flashing recovery
sending 'recovery' (9216 KB)... OKAY [ 0.956s]
writing 'recovery'... OKAY [ 1.852s]
Flashing Radio
sending 'radio' (12080 KB)... OKAY [ 1.256s]
writing 'radio'... OKAY [ 1.248s]
Flashing cdrom
sending 'cdrom' (12032 KB)... OKAY [ 1.231s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
Flashing preinstall
sending 'preinstall' (262144 KB)... OKAY [ 25.070s]
writing 'preinstall'... OKAY [ 23.457s]
sending 'preinstall' (20480 KB)... OKAY [ 1.997s]
writing 'preinstall'... OKAY [ 1.760s]
Flashing webtop, This will take a LONG time, be patient
sending 'webtop' (262144 KB)...
PLEASE try and search your problem first before making a new thread about it. This problem has been discussed in the thread for the return to GB utility, as well as in other threads.
Try running the script again. If it still doesn't work after maybe 4 or 5 tries then go ahead and use RSD Lite to flash the .xml file located in the script's folder. You can find more information if you search.
cogeary said:
PLEASE try and search your problem first before making a new thread about it. This problem has been discussed in the thread for the return to GB utility, as well as in other threads.
Try running the script again. If it still doesn't work after maybe 4 or 5 tries then go ahead and use RSD Lite to flash the .xml file located in the script's folder. You can find more information if you search.
Click to expand...
Click to collapse
I did search, I was probably looking at my answers and just didnt know it. Im still on a learning curve. Ive rooted and ROM'd multiple times but this is my 1st issue like this so I am really clueless....... I dont know what the RSD Lite is (never even heard of it) or how it works. But thanks I guess.:good:
And I have tried more than 10 times with the script...
jburke90 said:
I did search, I was probably looking at my answers and just didnt know it. Im still on a learning curve. Ive rooted and ROM'd multiple times but this is my 1st issue like this so I am really clueless....... I dont know what the RSD Lite is (never even heard of it) or how it works. But thanks I guess.:good:
And I have tried more than 10 times with the script...
Click to expand...
Click to collapse
RSDLite is a must have with this phone. It's a program that will help you flash stock images (FXZs) when all else doesn't seem to want to cooperate. Download it, and use it when scripts give you trouble. I used to FXZ back to stock via a script, then one day it said "nope, not doing it agsin". RSDLite worked like a charm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Apex_Strider said:
RSDLite is a must have with this phone. It's a program that will help you flash stock images (FXZs) when all else doesn't seem to want to cooperate. Download it, and use it when scripts give you trouble. I used to FXZ back to stock via a script, then one day it said "nope, not doing it agsin". RSDLite worked like a charm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I just got RSDlite. Which file am I looking for now? An image? I dont know.. lol
You are looking for the xml located inside the zip file. Please just search mate, I've seen the answer to this question in three different threads. Read the thread for the utility script.
Sent from my MB865 using xda premium
You'll need to locate the FXZ to get back to 2.3.6 but there's a patch file that you'll need to also download and extract and place in the 2.3.6 FXZ folder (it'll ask if you want to make these changes when doing this on your PC, and you will have to) then open RDSLite, connect your phone with your USB cable, and go! I'll try to find the links to the files.
Sent from my SAMSUNG-SGH-I747 using xda premium
---------- Post added at 08:42 PM ---------- Previous post was at 08:16 PM ----------
Look at this thread
as well as this thread
and you should be able to read through these and get yourself back in business!
Off topic, and my bad for that. But I have to say, much as I get annoyed too by the constant posting of questions already answered, many times those of us who are new to something won't even know WHAT to search for. Many times I've searched with terms I thought ought to get me my answer, with no result. If I had never heard of things like fxz and RSDlite, I'd have no idea to use such terms in a search.
That said, I feel like the thread about the IRC Chat ought to be stickied. This sort of question is much more appropriate and welcomed there than on a post on the main page. And many thanks to Apex Strider for doing the legwork .
Silas0220 said:
Off topic, and my bad for that. But I have to say, much as I get annoyed too by the constant posting of questions already answered, many times those of us who are new to something won't even know WHAT to search for. Many times I've searched with terms I thought ought to get me my answer, with no result. If I had never heard of things like fxz and RSDlite, I'd have no idea to use such terms in a search.
That said, I feel like the thread about the IRC Chat ought to be stickied. This sort of question is much more appropriate and welcomed there than on a post on the main page. And many thanks to Apex Strider for doing the legwork .
Click to expand...
Click to collapse
I agree, and I will PM Moscow to see about getting the IRC thread stickied. Good call.
to use rsd you will need the xml file from the script from this thread
http://forum.xda-developers.com/showthread.php?t=1805975
here is a screen shot
I just did this today and it worked great
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!!!!
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
Hi all. it's been a while since I've posted on xda
I'm having a problem with my newly acquired Pixel,
Today, I received an OTA notification for Android 8.1, tried to have it install but the when the phone restarts to install, it just flash to google logo like 3 times and them boot back to 8.0.
I looked it up on google, people say I should factory reset before restarting and install 8.1. Tried that but same thing happens.
Then I decided to download the factory image and flash it myself. With OEM unlocking and Android debugging enabled, the 8.1 image flashed successfully. However, the phone doesn't boot, it shows a dead Android and a "No command" error. Same thing happen when I try to sideload the OTA file...
I had to flash the 8.0 factory image for the phone to boot successfully again...
Now I have no idea how to get 8.1... Do you guys have any idea of what can be done or what's happening?
Thanks in advance!
Did you update your fastboot tools? That is needed for 8.1
TonikJDK said:
Did you update your fastboot tools? That is needed for 8.1
Click to expand...
Click to collapse
I used the latest version of minimal adb and fastboot:
https://forum.xda-developers.com/showthread.php?t=2317790
It flashed successfully without any error, so I assume my fastboot is fine...
If 8/28/15 is the latest minimalist platform tools, it's too old. I don't have the link handy but Google provides a direct link to the latest at all times now, so you don't have to install the developer tools or download someone else's repackaged to get the latest.
They updated it yet again the day they released 8.1.
Edit: here it is
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
The link stays the same and is always the latest version. Just extract it to where the firmware is extracted to.
Thanks, I'll try and report back
roirraW "edor" ehT said:
If 8/28/15 is the latest minimalist platform tools, it's too old. I don't have the link handy but Google provides a direct link to the latest at all times now, so you don't have to install the developer tools or download someone else's repackaged to get the latest.
They updated it yet again the day they released 8.1.
Edit: here it is
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
The link stays the same and is always the latest version. Just extract it to where the firmware is extracted to.
Click to expand...
Click to collapse
Just tried the latest platform tools, and the same issue persists... any idea?
Edit: Tried sideloading 8.1 OTA from 8.0, however, it boots back to 8.0 eventually.
cnkhanh said:
Just tried the latest platform tools, and the same issue persists... any idea?
Edit: Tried sideloading 8.1 OTA from 8.0, however, it boots back to 8.0 eventually.
Click to expand...
Click to collapse
how about not doing an ota update but using the full firmware image instead?
you would have two options;
1. edit the flash-all script, removing the -w flag, so it doesn't wipe your data partition
2. or do a full system wipe backup anything important first...
nine7nine said:
how about not doing an ota update but using the full firmware image instead?
you would have two options;
1. edit the flash-all script, removing the -w flag, so it doesn't wipe your data partition
2. or do a full system wipe backup anything important first...
Click to expand...
Click to collapse
I already tried flashing the 8.1 factory image, wiping data, still have the same issue though...
cnkhanh said:
I already tried flashing the 8.1 factory image, wiping data, still have the same issue though...
Click to expand...
Click to collapse
I don't see how that would be possible, if u had run the flash-all script it would've replaced the bootloader, all of your devices partitions with the new firmware...
there would be no 8.0 to boot back into, at all.
please write your steps down and some of thevrelevant output you see on your phone, when the script runs...
nine7nine said:
I don't see how that would be possible, if u had run the flash-all script it would've replaced the bootloader, all of your devices partitions with the new firmware...
there would be no 8.0 to boot back into, at all.
please write your steps down and some of thevrelevant output you see on your phone, when the script runs...
Click to expand...
Click to collapse
Sorry, I meant the issue was that in my original post, the phone doesn't boot and stuck on the "No command" screen...
When the flash all script runs, my phones was on fastboot mode, rebooting to bootloader several times during the process (this is expected i guess). When the script finishes successfully, the phone tries to boot into the OS, but it shows a google logo and turns off, several times (like a bootloop), then eventually shows the "No command" screen.
Currently, I'm on 8.0, build number OPR3.170623.013
cnkhanh said:
Currently, I'm on 8.0, build number OPR3.170623.013
Click to expand...
Click to collapse
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs
Sgace said:
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Last ditch effort is a different PC and/or cable.
I'm out of ideas otherwise. Is it under warranty?
roirraW "edor" ehT said:
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Click to expand...
Click to collapse
Sgace said:
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Thanks for pointing out, but the version I was trying to flash was correct, sailfish 8.1.0 (OPM1.171019.011, Dec 2017)
I'll try another PC and cable later, I'm running on Windows 10 Fall Creator Update.
I don't think warranty is a viable option for me
Here is the cmd lines when installing 8.1, seems fine with me.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.059s]
finished. total time: 2.951s
rebooting into bootloader...
OKAY [ 0.051s]
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.499s]
writing 'radio_a'...
OKAY [ 0.486s]
finished. total time: 1.989s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (28 MB) to disk... took 0.410s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1751 MB) to disk... took 18.393s
archive does not contain 'system.sig'
extracting system_other.img (551 MB) to disk... took 6.660s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (250 MB) to disk... took 2.662s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6509568 4k blocks and 1630208 inodes
Filesystem UUID: 657305e6-e288-11e7-8b52-538b74cf9ac7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1710040120
Baseband Version.....: 8996-130091-1710201747
Serial Number........: FA6960306426
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.048s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
erasing 'system_a'...
OKAY [ 0.320s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 13.651s]
writing 'system_a' 1/4...
OKAY [ 3.451s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 13.604s]
writing 'system_a' 2/4...
OKAY [ 3.488s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 14.015s]
writing 'system_a' 3/4...
OKAY [ 3.446s]
sending sparse 'system_a' 4/4 (220660 KB)...
OKAY [ 5.700s]
writing 'system_a' 4/4...
OKAY [ 1.494s]
erasing 'system_b'...
OKAY [ 0.261s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 13.702s]
writing 'system_b' 1/2...
OKAY [ 3.451s]
sending sparse 'system_b' 2/2 (40660 KB)...
OKAY [ 1.083s]
writing 'system_b' 2/2...
OKAY [ 0.355s]
erasing 'vendor_a'...
OKAY [ 0.142s]
sending 'vendor_a' (257004 KB)...
OKAY [ 6.358s]
writing 'vendor_a'...
OKAY [ 1.758s]
Setting current slot to 'a'...
OKAY [ 0.088s]
erasing 'userdata'...
OKAY [ 1.705s]
sending 'userdata' (4412 KB)...
OKAY [ 0.196s]
writing 'userdata'...
OKAY [ 0.100s]
rebooting...
finished. total time: 89.845s
Press any key to exit...
roirraW "edor" ehT said:
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Last ditch effort is a different PC and/or cable.
I'm out of ideas otherwise. Is it under warranty?
Click to expand...
Click to collapse
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Sent from my Google Pixel using XDA Labs
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
cnkhanh said:
Here is the cmd lines when installing 8.1, seems fine with me.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.059s]
finished. total time: 2.951s
rebooting into bootloader...
OKAY [ 0.051s]
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.499s]
writing 'radio_a'...
OKAY [ 0.486s]
finished. total time: 1.989s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (28 MB) to disk... took 0.410s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1751 MB) to disk... took 18.393s
archive does not contain 'system.sig'
extracting system_other.img (551 MB) to disk... took 6.660s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (250 MB) to disk... took 2.662s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6509568 4k blocks and 1630208 inodes
Filesystem UUID: 657305e6-e288-11e7-8b52-538b74cf9ac7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1710040120
Baseband Version.....: 8996-130091-1710201747
Serial Number........: FA6960306426
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.048s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
erasing 'system_a'...
OKAY [ 0.320s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 13.651s]
writing 'system_a' 1/4...
OKAY [ 3.451s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 13.604s]
writing 'system_a' 2/4...
OKAY [ 3.488s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 14.015s]
writing 'system_a' 3/4...
OKAY [ 3.446s]
sending sparse 'system_a' 4/4 (220660 KB)...
OKAY [ 5.700s]
writing 'system_a' 4/4...
OKAY [ 1.494s]
erasing 'system_b'...
OKAY [ 0.261s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 13.702s]
writing 'system_b' 1/2...
OKAY [ 3.451s]
sending sparse 'system_b' 2/2 (40660 KB)...
OKAY [ 1.083s]
writing 'system_b' 2/2...
OKAY [ 0.355s]
erasing 'vendor_a'...
OKAY [ 0.142s]
sending 'vendor_a' (257004 KB)...
OKAY [ 6.358s]
writing 'vendor_a'...
OKAY [ 1.758s]
Setting current slot to 'a'...
OKAY [ 0.088s]
erasing 'userdata'...
OKAY [ 1.705s]
sending 'userdata' (4412 KB)...
OKAY [ 0.196s]
writing 'userdata'...
OKAY [ 0.100s]
rebooting...
finished. total time: 89.845s
Press any key to exit...
Click to expand...
Click to collapse
Looks ok to me too. Are u able to manually boot to stock recovery after the flash and from there do a factory reset?
Cheers
Sent from my Google Pixel using XDA Labs
cnkhanh said:
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
Click to expand...
Click to collapse
I would have to re-flash the firmware to check (which I'm not doing), but shouldn't the boot.img be flashed to both the slot_a and slot_b partitions?
your issue of it ending boot with the recovery "no command" makes me think that something isn't right with the flashed boot images....
one thing you could try is unzipping the fimeware update zip and manually using fast boot to flash the boot images, after flashing the firmware....
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
you could also try using twrp to manually flash the boot.img and system image (you would need to copy them to your device though).... I've bumped into the error you speak of; but not when doing a full flash of system firmware.... that _shouldn't_ happen.....
Sgace said:
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Click to expand...
Click to collapse
You're welcome, hey, you can up with the good suggestion!
Another idea is at least on 8.0 with SuperSU, I was able to flash the entire 8.1 firmware with @Chainfire 's FlashFire app, every partition.
Sgace said:
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Sent from my Google Pixel using XDA Labs
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
Looks ok to me too. Are u able to manually boot to stock recovery after the flash and from there do a factory reset?
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Yes, I still can boot in to stock recovery, I tried factory reset many times though...
nine7nine said:
I would have to re-flash the firmware to check (which I'm not doing), but shouldn't the boot.img be flashed to both the slot_a and slot_b partitions?
your issue of it ending boot with the recovery "no command" makes me think that something isn't right with the flashed boot images....
one thing you could try is unzipping the fimeware update zip and manually using fast boot to flash the boot images, after flashing the firmware....
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
you could also try using twrp to manually flash the boot.img and system image (you would need to copy them to your device though).... I've bumped into the error you speak of; but not when doing a full flash of system firmware.... that _shouldn't_ happen.....
Click to expand...
Click to collapse
Hmm, I think it only flashes the active slot. Mine is "a", shown in bootloader mode.
Btw, my device shows the OTA update is about 566 MB while the OTA zip for sideloading is 900+MB, is that normal?
Edit: Just tried flashing both boot slot "a" and "b", changing active boot slot to "b" still have the same issues
cnkhanh said:
Yes, I still can boot in to stock recovery, I tried factory reset many times though...
Hmm, I think it only flashes the active slot. Mine is "a", shown in bootloader mode.
Btw, my device shows the OTA update is about 566 MB while the OTA zip for sideloading is 900+MB, is that normal?
Edit: Just tried flashing both boot slot "a" and "b", changing active boot slot to "b" still have the same issues
Click to expand...
Click to collapse
My theory is that it is updating the secondary system partition but failing to switch partitions. I could be wrong.
X:\MM>fastboot flash boot boot.img
target reported max download size of 524288000 bytes
sending 'boot' (22672 KB)...
OKAY [ 0.516s]
writing 'boot'...
OKAY [ 1.274s]
finished. total time: 1.791s
X:\MM>fastboot flash cust cust.img
target reported max download size of 524288000 bytes
sending 'cust' (204572 KB)...
OKAY [ 4.595s]
writing 'cust'...
OKAY [ 4.547s]
finished. total time: 9.143s
X:\MM>fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (36118 KB)...
OKAY [ 0.827s]
writing 'recovery'...
OKAY [ 1.795s]
finished. total time: 2.622s
X:\MM>fastboot flash recovery2 recovery2.img
target reported max download size of 524288000 bytes
sending 'recovery2' (36118 KB)...
OKAY [ 0.811s]
writing 'recovery2'...
OKAY [ 1.812s]
finished. total time: 2.623s
X:\MM>fastboot flash system system.img
target reported max download size of 524288000 bytes
sending sparse 'system' (511933 KB)...
OKAY [ 12.387s]
writing 'system'...
OKAY [ 11.362s]
sending sparse 'system' (511977 KB)...
OKAY [ 12.509s]
writing 'system'...
OKAY [ 11.365s]
sending sparse 'system' (510760 KB)...
OKAY [ 12.582s]
writing 'system'...
OKAY [ 11.323s]
sending sparse 'system' (482362 KB)...
OKAY [ 11.807s]
writing 'system'...
OKAY [ 10.682s]
sending sparse 'system' (282051 KB)...
OKAY [ 6.866s]
writing 'system'...
OKAY [ 6.281s]
finished. total time: 107.184s
Click to expand...
Click to collapse
i did all of this but still my phone is at Huawei Logo.
CHC-U01
the dload is not working every time i try it phone is showing black screen. but i was able to reach cwm but black screen but i can feel the vibrations
thanks sir.
SpectreZ said:
i did all of this but still my phone is at Huawei Logo.
CHC-U01
the dload is not working every time i try it phone is showing black screen. but i was able to reach cwm but black screen but i can feel the vibrations
thanks sir.
Click to expand...
Click to collapse
Try to flash in the specified order and that too with your stock KK firmware.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
flash system system.img
miststudent2011 said:
Try to flash in the specified order and that too with your stock KK firmware.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
flash system system.img
Click to expand...
Click to collapse
i did that with stock KK now its rebooting on Huawei Logo.
SpectreZ said:
i did that with stock KK now its rebooting on Huawei Logo.
Click to expand...
Click to collapse
Is Twrp or CWM working on your device?
miststudent2011 said:
Is Twrp or CWM working on your device?
Click to expand...
Click to collapse
CWM works But i get Black Screen. Sir
Phone vibrate on volume up and downs.
miststudent2011 said:
Is Twrp or CWM working on your device?
Click to expand...
Click to collapse
UPDATE: Sir i the phone booted up on Andorid L Build B330 How do i RollBack to Kitkat without any problem?
I did your Method with Lolipop and The Phone Boots.
Thank you soo much sir but if you could help me to Get Back in Kitkat ( Storage Problems in Latest Version )
SpectreZ said:
UPDATE: Sir i the phone booted up on Andorid L Build B330 How do i RollBack to Kitkat without any problem?
I did your Method with Lolipop and The Phone Boots.
Thank you soo much sir but if you could help me to Get Back in Kitkat ( Storage Problems in Latest Version )
Click to expand...
Click to collapse
In order to roll back to KitKat you need to flash downgrade package and then flash KitKat firmware by using dload method.
But it may or maynot work as your phone is modified.
Is your phone is certified if you look into play store settings?
miststudent2011 said:
In order to roll back to KitKat you need to flash downgrade package and then flash KitKat firmware by using dload method.
But it may or maynot work as your phone is modified.
Is your phone is certified if you look into play store settings?
Click to expand...
Click to collapse
By Useing dLoad Method looks like i got the device in the same position now trying to do what you said again. sir
SpectreZ said:
By Useing dLoad Method looks like i got the device in the same position now trying to do what you said again. sir
Click to expand...
Click to collapse
Is your phone is certified if you look into play store settings?
miststudent2011 said:
Is your phone is certified if you look into play store settings?
Click to expand...
Click to collapse
i do not see any Certified or not certified on play store settings.
SpectreZ said:
i do not see any Certified or not certified on play store settings.
Click to expand...
Click to collapse
Playstore->settings->device certification
Sir Can you give me Kitkat Rom please? The one i have B070 is bugged i think everytime i try to flash it with dload or fastboot Phone gets stuck in bootloop but the buged rom Chilemovisters one runs good. thank you.