hi, I tried to root my nexus 7, and all ok, but when I tried to exec flash google factory image, I've the following output
Downloading Factory Image...
--2013-01-24 02:07:53-- URL rejected
Resolving dl.google.com (dl.google.com)... 74.125.225.238, 74.125.225.224, 74.125.225.230, ...
Connecting to dl.google.com (dl.google.com)|74.125.225.238|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 291197311 (278M) [application/x-tar]
Saving to: `factory.tgz'
100%[===================================================================================>] 291.197.311 365K/s in 16m 6s
2013-01-24 02:24:00 (294 KB/s) - `factory.tgz' saved [291197311/291197311]
< waiting for device >
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.128s]
finished. total time: 0.129s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.238s]
finished. total time: 0.238s
erasing 'recovery'...
OKAY [ 0.136s]
finished. total time: 0.137s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.217s]
finished. total time: 0.218s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 3.612s]
finished. total time: 3.612s
sending 'bootloader' (2096 KB)...
OKAY [ 0.280s]
writing 'bootloader'...
OKAY [ 1.952s]
finished. total time: 2.232s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
sending 'radio' (16384 KB)...
OKAY [ 2.071s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.086s
rebooting into bootloader...
OKAY [ 4.012s]
finished. total time: 4.012s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 488804800 bytes
error: update package missing system.img
Press ENTER to return to the main menu...
I tred using another USB port, and cable, moving the app to another folder and re-run, but I've the same output.
This is awfull cause I can't boot my nexus, only re-flashing the recovery, I can boot it, but the O.S. not. My nexus is dead, what I can do?
My, OS, is Linux Mint Nadia
Related
Hi
Can I flash stock i9020 rom on Korean variant m200 ?
I want remove unwanted korean apps in it..can I do it ?
Dwars said:
Hi
Can I flash stock i9020 rom on Korean variant m200 ?
I want remove unwanted korean apps in it..can I do it ?
Click to expand...
Click to collapse
You can find the stock (factory image) firmware here.
Using the method in this guide, you can flash the image easily. Please be sure to download the latest image for m200 (sojuk, 4.1.1 (JRO03E) and not other Nexus S variants. Also, the guide is not for m200 but the procedure followed is same, so do not forget to replace the file names while performing the flashing process. :good:
help
can any one help me in flashing a custom rom to my nexus s m200... i have rooted my phone with unlock root.. runing jellybean 4.1.1 (official rom).. please explain me step by step..
ishan.ranatunga said:
can any one help me in flashing a custom rom to my nexus s m200... i have rooted my phone with unlock root.. runing jellybean 4.1.1 (official rom).. please explain me step by step..
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2034264
DJBhardwaj said:
You can find the stock (factory image) firmware here.
Using the method in this guide, you can flash the image easily. Please be sure to download the latest image for m200 (sojuk, 4.1.1 (JRO03E) and not other Nexus S variants. Also, the guide is not for m200 but the procedure followed is same, so do not forget to replace the file names while performing the flashing process. :good:
Click to expand...
Click to collapse
tried this method and files but when writing system.img showing failed.
Code:
C:\ADBFAST>fastboot devices
3531430F809D00EC fastboot
C:\ADBFAST>fastboot erase boot
erasing 'boot'... OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADBFAST>fastboot erase cache
erasing 'cache'... OKAY [ 2.094s]
finished. total time: 2.094s
C:\ADBFAST>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.031s]
finished. total time: 0.031s
C:\ADBFAST>fastboot erase system
erasing 'system'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADBFAST>fastboot erase userdata
erasing 'userdata'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADBFAST>fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
error: cannot load 'bootloader-crespo-i9020xxlc2.img'
C:\ADBFAST>fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
sending 'bootloader' (1536 KB)... OKAY [ 0.250s]
writing 'bootloader'... OKAY [ 0.359s]
finished. total time: 0.609s
C:\ADBFAST>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADBFAST>fastboot flash radio radio-crespo-i9020uclh1.img
sending 'radio' (12288 KB)... OKAY [ 1.938s]
writing 'radio'... OKAY [ 1.844s]
finished. total time: 3.781s
C:\ADBFAST>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADBFAST>fastboot -w update image-sojua-jzo54k.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020UCLH1
Serial Number........: 3531430F809D00EC
--------------------------------------------
checking product... OKAY [ 0.000s]
checking version-bootloader... OKAY [ 0.000s]
checking version-baseband... OKAY [ 0.000s]
sending 'boot' (3964 KB)... OKAY [ 0.672s]
writing 'boot'... OKAY [ 0.547s]
sending 'recovery' (4308 KB)... OKAY [ 0.719s]
writing 'recovery'... OKAY [ 0.609s]
sending 'system' (337599 KB)... OKAY [ 54.859s]
writing 'system'... FAILED (remote: Write Fail)
finished. total time: 57.422s
and when tried with 2nd file. now not able to erase userdata and system and at end system writing failed too.
Code:
C:\ADBFAST>fastboot devices
3531430F809D00EC fastboot
C:\ADBFAST>fastboot erase boot
erasing 'boot'... OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADBFAST>fastboot erase cache
erasing 'cache'... OKAY [ 2.141s]
finished. total time: 2.141s
C:\ADBFAST>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADBFAST>fastboot erase system
erasing 'system'... FAILED (remote: Erase Fail)
finished. total time: 0.016s
C:\ADBFAST>fastboot erase system
erasing 'system'... FAILED (remote: Erase Fail)
finished. total time: 0.031s
C:\ADBFAST>fastboot erase userdata
erasing 'userdata'... FAILED (remote: Erase Fail)
finished. total time: 0.000s
C:\ADBFAST>fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
sending 'bootloader' (1536 KB)... OKAY [ 0.266s]
writing 'bootloader'... OKAY [ 0.375s]
finished. total time: 0.641s
C:\ADBFAST>fastboot flash radio radio-crespo-i9020xxki1.img
sending 'radio' (12288 KB)... OKAY [ 1.922s]
writing 'radio'... OKAY [ 1.750s]
finished. total time: 3.672s
C:\ADBFAST>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADBFAST>fastboot -w update image-soju-jzo54k.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 3531430F809D00EC
--------------------------------------------
checking product... OKAY [ 0.000s]
checking version-bootloader... OKAY [ 0.000s]
checking version-baseband... OKAY [ 0.000s]
sending 'boot' (3964 KB)... OKAY [ 0.641s]
writing 'boot'... OKAY [ 0.563s]
sending 'recovery' (4308 KB)... OKAY [ 0.734s]
writing 'recovery'... OKAY [ 0.609s]
sending 'system' (337443 KB)... OKAY [ 55.547s]
writing 'system'... FAILED (remote: Write Fail)
finished. total time: 58.141s
my nexus info
Code:
INFOproduct: herring
INFOserialno: 3531430F809D00EC
INFOversion-hardware: REV 11
INFOversion-baseband: I9020XXKI1
INFOversion-bootloader: I9020XXLC2
INFOsecure: yes
INFOunlocked: yes
INFOoff-mode-charge: 1
all:
help me what is going wrong?
gsm city said:
tried this method and files but when writing system.img showing failed.
Code:
C:\ADBFAST>fastboot devices
3531430F809D00EC fastboot
C:\ADBFAST>fastboot erase boot
erasing 'boot'... OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADBFAST>fastboot erase cache
erasing 'cache'... OKAY [ 2.094s]
finished. total time: 2.094s
C:\ADBFAST>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.031s]
finished. total time: 0.031s
C:\ADBFAST>fastboot erase system
erasing 'system'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADBFAST>fastboot erase userdata
erasing 'userdata'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADBFAST>fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
error: cannot load 'bootloader-crespo-i9020xxlc2.img'
C:\ADBFAST>fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
sending 'bootloader' (1536 KB)... OKAY [ 0.250s]
writing 'bootloader'... OKAY [ 0.359s]
finished. total time: 0.609s
C:\ADBFAST>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADBFAST>fastboot flash radio radio-crespo-i9020uclh1.img
sending 'radio' (12288 KB)... OKAY [ 1.938s]
writing 'radio'... OKAY [ 1.844s]
finished. total time: 3.781s
C:\ADBFAST>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADBFAST>fastboot -w update image-sojua-jzo54k.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020UCLH1
Serial Number........: 3531430F809D00EC
--------------------------------------------
checking product... OKAY [ 0.000s]
checking version-bootloader... OKAY [ 0.000s]
checking version-baseband... OKAY [ 0.000s]
sending 'boot' (3964 KB)... OKAY [ 0.672s]
writing 'boot'... OKAY [ 0.547s]
sending 'recovery' (4308 KB)... OKAY [ 0.719s]
writing 'recovery'... OKAY [ 0.609s]
sending 'system' (337599 KB)... OKAY [ 54.859s]
writing 'system'... FAILED (remote: Write Fail)
finished. total time: 57.422s
and when tried with 2nd file. now not able to erase userdata and system and at end system writing failed too.
Code:
C:\ADBFAST>fastboot devices
3531430F809D00EC fastboot
C:\ADBFAST>fastboot erase boot
erasing 'boot'... OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADBFAST>fastboot erase cache
erasing 'cache'... OKAY [ 2.141s]
finished. total time: 2.141s
C:\ADBFAST>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADBFAST>fastboot erase system
erasing 'system'... FAILED (remote: Erase Fail)
finished. total time: 0.016s
C:\ADBFAST>fastboot erase system
erasing 'system'... FAILED (remote: Erase Fail)
finished. total time: 0.031s
C:\ADBFAST>fastboot erase userdata
erasing 'userdata'... FAILED (remote: Erase Fail)
finished. total time: 0.000s
C:\ADBFAST>fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
sending 'bootloader' (1536 KB)... OKAY [ 0.266s]
writing 'bootloader'... OKAY [ 0.375s]
finished. total time: 0.641s
C:\ADBFAST>fastboot flash radio radio-crespo-i9020xxki1.img
sending 'radio' (12288 KB)... OKAY [ 1.922s]
writing 'radio'... OKAY [ 1.750s]
finished. total time: 3.672s
C:\ADBFAST>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADBFAST>fastboot -w update image-soju-jzo54k.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 3531430F809D00EC
--------------------------------------------
checking product... OKAY [ 0.000s]
checking version-bootloader... OKAY [ 0.000s]
checking version-baseband... OKAY [ 0.000s]
sending 'boot' (3964 KB)... OKAY [ 0.641s]
writing 'boot'... OKAY [ 0.563s]
sending 'recovery' (4308 KB)... OKAY [ 0.734s]
writing 'recovery'... OKAY [ 0.609s]
sending 'system' (337443 KB)... OKAY [ 55.547s]
writing 'system'... FAILED (remote: Write Fail)
finished. total time: 58.141s
my nexus info
Code:
INFOproduct: herring
INFOserialno: 3531430F809D00EC
INFOversion-hardware: REV 11
INFOversion-baseband: I9020XXKI1
INFOversion-bootloader: I9020XXLC2
INFOsecure: yes
INFOunlocked: yes
INFOoff-mode-charge: 1
all:
help me what is going wrong?
Click to expand...
Click to collapse
Let me know the exact model number of your Nexus S?
I902OT, I92023, I9020A, M200, D720?
DJBhardwaj said:
Let me know the exact model number of your Nexus S?
I902OT, I92023, I9020A, M200, D720?
Click to expand...
Click to collapse
SHW-M200K (under battery)
and fastboot mode:
Code:
INFOproduct: herring
INFOserialno: 3531430F809D00EC
INFOversion-hardware: REV 11
INFOversion-baseband: I9020XXKI1
INFOversion-bootloader: I9020XXLC2
INFOsecure: yes
INFOunlocked: yes
INFOoff-mode-charge: 1
gsm city said:
SHW-M200K (under battery)
and fastboot mode:
Code:
INFOproduct: herring
INFOserialno: 3531430F809D00EC
INFOversion-hardware: REV 11
INFOversion-baseband: I9020XXKI1
INFOversion-bootloader: I9020XXLC2
INFOsecure: yes
INFOunlocked: yes
INFOoff-mode-charge: 1
Click to expand...
Click to collapse
So, which factory image are you using exactly?
DJBhardwaj said:
So, which factory image are you using exactly?
Click to expand...
Click to collapse
sojua-jzo54k-factory-1121b619
soju-jzo54k-factory-36602333
both tried
http://www.droidviews.com/nexus-s-guide-flash-android-4-1-2-jzo54k-factory-image/
gsm city said:
sojua-jzo54k-factory-1121b619
soju-jzo54k-factory-36602333
both tried
http://www.droidviews.com/nexus-s-guide-flash-android-4-1-2-jzo54k-factory-image/
Click to expand...
Click to collapse
Seems like you have the Korean variant. Go for m200 - sojuk
sorry for previous (i am trying a wrong img for my cell)
now i am trying with 4.1.1 sojuk-jro03e-factory-93a21b70
now downloaded from below link (sojuk for Nexus S (Korea version, m200)
https://developers.google.com/android/nexus/images#mysidspr
but still same problem.
important isue:
when trying to erase system and userdata.........process failed every time.
i think therefore this failed to writing system.img
Code:
C:\ADBFAST>fastboot devices
3531430F809D00EC fastboot
C:\ADBFAST>fastboot erase boot
erasing 'boot'... OKAY [ 0.031s]
finished. total time: 0.031s
C:\ADBFAST>fastboot erase cache
erasing 'cache'... OKAY [ 2.109s]
finished. total time: 2.109s
C:\ADBFAST>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADBFAST>fastboot erase system
erasing 'system'... [B][COLOR="Red"]FAILED[/COLOR][/B] (remote: Erase Fail)
finished. total time: 0.016s
C:\ADBFAST>fastboot erase userdata
erasing 'userdata'... [B][COLOR="red"]FAILED[/COLOR][/B] (remote: Erase Fail)
finished. total time: 0.016s
C:\ADBFAST>fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
sending 'bootloader' (1536 KB)... OKAY [ 0.250s]
writing 'bootloader'... OKAY [ 0.359s]
finished. total time: 0.609s
C:\ADBFAST>fastboot flash radio radio-crespo-m200krkc1.img
sending 'radio' (12288 KB)... OKAY [ 2.016s]
writing 'radio'... OKAY [ 1.828s]
finished. total time: 3.844s
C:\ADBFAST>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADBFAST>fastboot -w update image-sojuk-jro03e.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: M200KRKC1
Serial Number........: 3531430F809D00EC
--------------------------------------------
checking product... OKAY [ 0.016s]
checking version-bootloader... OKAY [ 0.000s]
checking version-baseband... OKAY [ 0.000s]
sending 'boot' (3964 KB)... OKAY [ 0.766s]
writing 'boot'... OKAY [ 0.547s]
sending 'recovery' (4308 KB)... OKAY [ 0.719s]
writing 'recovery'... OKAY [ 0.594s]
sending 'system' (294030 KB)... OKAY [ 48.094s]
writing 'system'... [B][COLOR="red"]FAILED [/COLOR][/B](remote: Write Fail)
finished. total time: 50.766s
my device is M200k korean
and i downoaded image files from developers google site
but these images are for crespo board.
and my cell board is herring
now where to download herring board image files for my device.
any help please?
ok i followed the steps i put FXZ_xt907 folder in the directory i got house of moto installed witch is C:\ copy and pasted all the FXZ files into the FXZ_xt907 folder then ran HouseOfMoto Batch file chose fastboot then chose 1 FULL_xt907 said ready to flash press any key i did that and it gave me this
Please ensure your phone is:
o] Charged
o] Connected to USB using your OEM cable
o] USB drivers are installed
o] Booted to AP Fastboot mode: [power off, hold volume down and press power]
Ready to flash...
Press any key to continue . . .
Flashing: FULL_xt907.bat
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
< waiting for device >
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.264s
sending 'sbl1' (100 KB)...
OKAY [ 0.019s]
writing 'sbl1'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.262s
sending 'sbl2' (125 KB)...
OKAY [ 0.038s]
writing 'sbl2'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.280s
sending 'sbl3' (512 KB)...
OKAY [ 0.049s]
writing 'sbl3'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.310s
sending 'rpm' (140 KB)...
OKAY [ 0.031s]
writing 'rpm'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.281s
sending 'tz' (192 KB)...
OKAY [ 0.016s]
writing 'tz'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.265s
sending 'aboot' (256 KB)...
OKAY [ 0.031s]
writing 'aboot'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.281s
sending 'modem' (30720 KB)...
OKAY [ 2.371s]
writing 'modem'...
Battery Low!!
FAILED (remote failure)
finished. total time: 2.621s
sending 'fsg' (2794 KB)...
OKAY [ 0.218s]
writing 'fsg'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.468s
erasing 'modemst1'...
OKAY [ 0.718s]
finished. total time: 0.718s
erasing 'modemst2'...
OKAY [ 0.718s]
finished. total time: 0.718s
sending 'logo' (1709 KB)...
OKAY [ 0.156s]
writing 'logo'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.406s
sending 'devtree' (512 KB)...
OKAY [ 0.047s]
writing 'devtree'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.296s
sending 'boot' (10240 KB)...
OKAY [ 0.796s]
writing 'boot'...
Battery Low!!
FAILED (remote failure)
finished. total time: 1.061s
sending 'recovery' (10240 KB)...
OKAY [ 0.796s]
writing 'recovery'...
Battery Low!!
FAILED (remote failure)
finished. total time: 1.046s
sending 'cdrom' (30720 KB)...
OKAY [ 2.388s]
writing 'cdrom'...
OKAY [ 3.121s]
sending 'cdrom' (22538 KB)...
OKAY [ 3.588s]
writing 'cdrom'...
OKAY [ 2.730s]
finished. total time: 11.842s
error: cannot load 'system.img.ext4'
erasing 'cache'...
OKAY [ 1.154s]
finished. total time: 1.154s
erasing 'userdata'...
OKAY [ 2.434s]
finished. total time: 2.434s
erasing 'tombstones'...
OKAY [ 0.889s]
finished. total time: 0.889s
rebooting...
finished. total time: -0.000s
Press any key to continue . . .
can i just charge the battery from fastboot cause mine doesnt say battery low cannot program just Battery Low
ok guys i got the droid razr M utility i just need to get my fasboot menu to say Battery OK i plug it into the wall and it brings up Battery OK but then when i go plug it back into the pc to flash my stock rom with the utility the fastboot menu sayes Battery Low so idk whats going on :/
Hi. I have a OPO that i cant flash or erase anything.
It`s encrypted and what i boot OS it`s asks for a code and it doesn`t meter which one i will write. The phone says:
View attachment 3283408
When i press on Reset Phone - nothing hepends.
Rebooting to recovery (The ColorOS recovery V1.2) and Wipe data and cache does nothing.
Flashing custom recovery or erasing user-data whiting fast-boot falls (with locked and unlocked boot-loader) s:
target reported max download size of 1073741824 bytes
sending 'modem' (56337 KB)...
OKAY [ 1.844s]
writing 'modem'...
FAILED (remote: flash write failure)
finished. total time: 6.893s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 1073741824 bytes
sending 'sbl1' (295 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
FAILED (remote: flash write failure)
finished. total time: 5.066s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.000s]
writing 'dbi'...
FAILED (remote: flash write failure)
finished. total time: 5.037s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 1073741824 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
FAILED (remote: flash write failure)
finished. total time: 5.064s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.016s]
writing 'rpm'...
FAILED (remote: flash write failure)
finished. total time: 5.057s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
sending 'tz' (283 KB)...
OKAY [ 0.015s]
writing 'tz'...
FAILED (remote: flash write failure)
finished. total time: 5.070s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.305s]
writing 'LOGO'...
FAILED (remote: flash write failure)
finished. total time: 5.366s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.019s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 8feeb7e6
--------------------------------------------
checking product...
OKAY [ 0.000s]
sending 'boot' (5606 KB)...
OKAY [ 0.188s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 5.257s
Press any key to exit...
Even flashing with MSM8974DownloadTool falls - only 8974_msimage.mbn flashes and phone power offs by it self.
Tried to temporary boot custom recovery and wipe anything - no lack.
Please help
I was given a xt1080 for repair
24.13.2.obake-maxx
SU6-7.2
Locked bootloader. No root. No adb access.
System boots but there is constants force close of background processes like gapps and acore.
I wanted to factory reset and I did but on reboot it had all the same apps and user data intact, no factory state.
Changing any config or uninstalling any app result in it being back after reboot.
What I've tried so far:
-Factory option in AP Fastboot menu. Reboots to system with all the data intact.
-Recovery option in AP Fastboot menu. Reboots to bootloader and states "Boot up failed".
-fastboot erase userdata
-fastboot -w
both with the resulting output:
erasing 'userdata'...
OKAY [ 0.500s]
erasing 'cache'...
OKAY [ 0.620s]
finished. total time: 1.120s
but sadly all userdata is sitting there intact after reboot.
I downloaded VZW-4.4.4-SU6-7.2-release-keys.xml.zip. Tried with RSDLite but it didn't detect the device.
I have installed the drivers and MotorolaDeviceManager. So I decompressed the firmware and flashed the partitions
using fastboot in a script. Resulting in all partitions being flashed OK but after reboot the device
was the same as before with all the apps and user data present. Spooky isn't it?
Can some one offer me any advice? Is it a hardware faliure?
Output of the script follows:
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe oem fb_mode_set
< waiting for device >
...
OKAY [ 0.109s]
finished. total time: 0.109s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.220s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
OKAY [ 0.444s]
finished. total time: 0.665s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.360s]
writing 'motoboot'...
flashing tz ...
flashing rpm ...
flashing aboot ...
flashing sbl1 ...
flashing sbl2 ...
flashing sbl3 ...
OKAY [ 4.540s]
finished. total time: 4.900s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash logo logo.bin
sending 'logo' (215 KB)...
OKAY [ 0.290s]
writing 'logo'...
OKAY [ 0.811s]
finished. total time: 1.102s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.900s]
writing 'boot'...
OKAY [ 1.872s]
finished. total time: 2.772s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 0.900s]
writing 'recovery'...
OKAY [ 1.512s]
finished. total time: 2.412s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash system system.img
sending 'system' (786432 KB)...
OKAY [ 49.426s]
writing 'system'...
OKAY [ 54.106s]
sending 'system' (531955 KB)...
OKAY [ 33.515s]
writing 'system'...
OKAY [ 36.056s]
finished. total time: 173.103s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash modem NON-HLOS.bin
sending 'modem' (54252 KB)...
OKAY [ 3.671s]
writing 'modem'...
OKAY [ 2.330s]
finished. total time: 6.002s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.419s]
finished. total time: 0.419s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.419s]
finished. total time: 0.419s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash fsg fsg.mbn
sending 'fsg' (538 KB)...
OKAY [ 0.330s]
writing 'fsg'...
OKAY [ 0.761s]
finished. total time: 1.092s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.649s]
finished. total time: 0.649s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 0.540s]
finished. total time: 0.540s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase customize
erasing 'customize'...
OKAY [ 0.150s]
finished. total time: 0.150s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase clogo
erasing 'clogo'...
OKAY [ 0.518s]
finished. total time: 0.518s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe oem config carrier gsm
...
Failed to flash config value
OKAY [ 0.149s]
finished. total time: 0.150s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe oem fb_mode_clear
...
OKAY [ 0.148s]
finished. total time: 0.148s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe reboot
rebooting...
finished. total time: 0.002s
I selected BP Tools in bootloader menu. Now I have adb access. Tried to delete some files, this is what I get:
[email protected]:/sdcard/dcim/Camera $ rm *
rm *
rm failed for IMG_20160222_223144143.jpg, Read-only file system
255|[email protected]:/sdcard/dcim/Camera $
In BP Tools mode various devices get detected. One of them is Motorola QC Diag Port, I installed the drivers.
Now it shows in QPST software. QPST has a Software Download utility that is suposed to flash bootloaders,
partitions images and whole firmware images. Does any one has any experience flashing with QPST?
Do you already resolve this issue? I got the same problem.
Please help me out my phone goes to crash dump mode while installing Pixel 5 - SPB3 - Android 12 Beta 3 for OnePlus 8 Series using video of #TechiBee
Following were the commands and errors ======
Pixel S for OnePlus8 Series
Make sure that Your phone is connected to Your PC and is in fastboot mode!
Flashing can take around 10-15 minutes
Disabling VBMETA..
Sending 'vbmeta' (8 KB) OKAY [ 0.011s]
Writing 'vbmeta' OKAY [ 0.006s]
Finished. Total time: 0.124s
Sending 'recovery' (102400 KB) OKAY [ 5.226s]
Writing 'recovery' OKAY [ 0.350s]
Finished. Total time: 5.679s
Sending 'dtbo_a' (24576 KB) OKAY [ 1.247s]
Writing 'dtbo_a' OKAY [ 0.078s]
Finished. Total time: 1.383s
Sending 'dtbo_b' (24576 KB) OKAY [ 0.540s]
Writing 'dtbo_b' OKAY [ 0.115s]
Finished. Total time: 0.667s
rebooting into fastboot OKAY [ 0.007s]
Finished. Total time: 0.042s
< waiting for any device >
Deleting 'system_b' OKAY [ 0.007s]
Finished. Total time: 0.008s
Deleting 'product_b' OKAY [ 0.006s]
Finished. Total time: 0.006s
Deleting 'system_ext_b' OKAY [ 0.006s]
Finished. Total time: 0.007s
Deleting 'system_a' OKAY [ 0.005s]
Finished. Total time: 0.006s
Deleting 'vendor_a' OKAY [ 0.005s]
Finished. Total time: 0.006s
Creating 'system_a' FAILED (remote: 'Not enough space for partition')
Finished. Total time: 0.006s
Creating 'vendor_a' FAILED (remote: 'Not enough space for partition')
Finished. Total time: 0.006s
Erasing 'system_ext_a' OKAY [ 0.036s]
Finished. Total time: 0.041s
Erasing 'product_a' OKAY [ 0.036s]
Finished. Total time: 0.043s
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/14 (262140 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 377.221s
finally my devies goes to crash dump mode and now only opens fastboot mode.
do msm
wawanRedblack said:
do msm
Click to expand...
Click to collapse
Besides EDL, he can also use fastboot mode
Update firmware,
if still stuck, try this in fastboot mode:
fastboot delete-logical-partition product_a
fastboot create-logical-partition product_a 100000
wawanRedblack said:
do msm
Click to expand...
Click to collapse
no response while trying msm please help me out
CDI-78 said:
Update firmware,
if still stuck, try this in fastboot mode:
fastboot delete-logical-partition product_a
fastboot create-logical-partition product_a 100000
Click to expand...
Click to collapse
how to update firmware in crash dump mode please help me
LR7875 said:
Besides EDL, he can also use fastboot mode
Click to expand...
Click to collapse
how to use fastboot mode to solve this problem please help
wawanRedblack said:
do msm
Click to expand...
Click to collapse
hello sir i tried to do msm but not dedected any devices while doing msm please help me
Crash Dump (9008/900E) mode need Qualcomm HS-USB driver:
Microsoft Update Catalog
www.catalog.update.microsoft.com
Kundan Shrestha said:
now only opens fastboot mode.
Click to expand...
Click to collapse
'Only opens fastboot mode'
should be
'cannot open fastboot mode'
from my understanding. But everyone has typos, sorry for the misunderstanding caused.
Did u try to format a d reinstall android 11??
Kundan Shrestha said:
Please help me out my phone goes to crash dump mode while installing Pixel 5 - SPB3 - Android 12 Beta 3 for OnePlus 8 Series using video of #TechiBee
Following were the commands and errors ======
Pixel S for OnePlus8 Series
Make sure that Your phone is connected to Your PC and is in fastboot mode!
Flashing can take around 10-15 minutes
Disabling VBMETA..
Sending 'vbmeta' (8 KB) OKAY [ 0.011s]
Writing 'vbmeta' OKAY [ 0.006s]
Finished. Total time: 0.124s
Sending 'recovery' (102400 KB) OKAY [ 5.226s]
Writing 'recovery' OKAY [ 0.350s]
Finished. Total time: 5.679s
Sending 'dtbo_a' (24576 KB) OKAY [ 1.247s]
Writing 'dtbo_a' OKAY [ 0.078s]
Finished. Total time: 1.383s
Sending 'dtbo_b' (24576 KB) OKAY [ 0.540s]
Writing 'dtbo_b' OKAY [ 0.115s]
Finished. Total time: 0.667s
rebooting into fastboot OKAY [ 0.007s]
Finished. Total time: 0.042s
< waiting for any device >
Deleting 'system_b' OKAY [ 0.007s]
Finished. Total time: 0.008s
Deleting 'product_b' OKAY [ 0.006s]
Finished. Total time: 0.006s
Deleting 'system_ext_b' OKAY [ 0.006s]
Finished. Total time: 0.007s
Deleting 'system_a' OKAY [ 0.005s]
Finished. Total time: 0.006s
Deleting 'vendor_a' OKAY [ 0.005s]
Finished. Total time: 0.006s
Creating 'system_a' FAILED (remote: 'Not enough space for partition')
Finished. Total time: 0.006s
Creating 'vendor_a' FAILED (remote: 'Not enough space for partition')
Finished. Total time: 0.006s
Erasing 'system_ext_a' OKAY [ 0.036s]
Finished. Total time: 0.041s
Erasing 'product_a' OKAY [ 0.036s]
Finished. Total time: 0.043s
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/14 (262140 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 377.221s
finally my devies goes to crash dump mode and now only opens fastboot mode.
Click to expand...
Click to collapse
Looks like you may. Need to resize your system partion