Related
i have just rooted my tf701
but i messed up the bootanimation.zip
and want to revert the stock
i have downloaded WW_epaduser_10_14_1_47_UpdateLauncher
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot reboot boo
tloader
< waiting for device >
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash boot
boot.img
< waiting for device >
target reported max download size of 643825664 bytes
sending 'boot' (5936 KB)...
OKAY [ 0.806s]
writing 'boot'...
OKAY [ 0.200s]
finished. total time: 1.006s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash syst
em blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.580s]
sending 'system' (1379 KB)...
OKAY [ 0.193s]
writing 'system'...
OKAY [ 0.057s]
finished. total time: 1.830s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash syst
em WW_epaduser_10_14_1_47_UpdateLauncher.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.108s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
OKAY [ 86.138s]
writing 'system'...
OKAY [ 17.136s]
sending sparse 'system' (340068 KB)...
OKAY [ 46.638s]
writing 'system'...
OKAY [ 9.278s]
finished. total time: 160.298s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.021s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
but i am still stuck in the asus logo
someone help
now fastboot wont even work someone help
D3LTA-V said:
i have just rooted my tf701
but i messed up the bootanimation.zip
and want to revert the stock
i have downloaded WW_epaduser_10_14_1_47_UpdateLauncher
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot reboot boo
tloader
< waiting for device >
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash boot
boot.img
< waiting for device >
target reported max download size of 643825664 bytes
sending 'boot' (5936 KB)...
OKAY [ 0.806s]
writing 'boot'...
OKAY [ 0.200s]
finished. total time: 1.006s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash syst
em blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.580s]
sending 'system' (1379 KB)...
OKAY [ 0.193s]
writing 'system'...
OKAY [ 0.057s]
finished. total time: 1.830s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash syst
em WW_epaduser_10_14_1_47_UpdateLauncher.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.108s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
OKAY [ 86.138s]
writing 'system'...
OKAY [ 17.136s]
sending sparse 'system' (340068 KB)...
OKAY [ 46.638s]
writing 'system'...
OKAY [ 9.278s]
finished. total time: 160.298s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.021s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
but i am still stuck in the asus logo
someone help
now fastboot wont even work someone help
Click to expand...
Click to collapse
First I would retry >fastboot flash staging blob
also that updateLauncher.zip you have has to be extracted once more to get a UL-K00C-WW-10.14.1.47-user.zip then flash that. You will get the parse errors but let it finish. Gonna take awhile.
schmeggy929 said:
First I would retry >fastboot flash staging blob
also that updateLauncher.zip you have has to be extracted once more to get a UL-K00C-WW-10.14.1.47-user.zip then flash that. You will get the parse errors but let it finish. Gonna take awhile.
Click to expand...
Click to collapse
flash drgravy's recovery.img, the v47 blob, start recovery, sideload update 47 zip (this works without errors)
Well now I can't even go into fastboot.
I press and hold vol down and power button. My tf701 justremain stuck at the device is unlocked
so you can't enter the bootloader selection screen?
what does your pc detect when connecting it?
i can only get into APX mode thats all
what firmware version was it when you rooted? was it WW 47?
26 ww
D3LTA-V said:
26 ww
Click to expand...
Click to collapse
so you had root and a running V10.26.1.7
and did this?
WARNING: DO NOT FOLLOW THESE STEPS!
fastboot flash boot boot.img (of the 10_14_1_47)
fastboot flash system blob (of the 10_14_1_47)
fastboot flash system WW_epaduser_10_14_1_47_UpdateLauncher.zip
fastboot reboot
If you did, you bricked it at the point where you flashed the old boot.img (remember, 47 is the old one) and misflashed the blob to system (blob goes to staging...).
all I know can help here, is nvflash (apx), but I have not seen one supporting the TF701...
what can i do now?
i cant access fastboot
only can access apx
D3LTA-V said:
what can i do now?
i cant access fastboot
only can access apx
Click to expand...
Click to collapse
if that's what you did, I can't help you.
so the only thing i can do is to send to the service center?
D3LTA-V said:
so the only thing i can do is to send to the service center?
Click to expand...
Click to collapse
well it's "wait until someone leaks a newer nvflash", or "try sending it back". but I'm pretty sure they're going to charge you a fair amount of cash to fix it, as you voided the warranty (the unlocker app calls home, that's a fact). But I might be wrong. If I were you, I'd wait for a fix. But I'm rather patient. Maybe someone else has better idea...
D3LTA-V said:
so the only thing i can do is to send to the service center?
Click to expand...
Click to collapse
Well send it back in to a service center or Asus is the only thing you can do now.
Since you are rooted and unlocked (do you have some more experience with this?) it is possible to brick your device,
Especially when you make a mistake by flashing the wrong files.
Sad but **** happens.
Someone at Google's mess the links. Here are the correct ones...
NEXUS 5 hammerhead:
https://dl.google.com/dl/android/aosp/hammerhead-kot49h-factory-02006b99.tgz
NEXUS 7 2013 razor:
https://dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz
NEXUS 7 2013 razorg
https://dl.google.com/dl/android/aosp/razorg-kot49h-factory-49789b24.tgz
NEXUS 4 occam:
https://dl.google.com/dl/android/aosp/occam-kot49h-factory-02e344de.tgz
NEXUS 10 mantaray:
https://dl.google.com/dl/android/aosp/mantaray-kot49h-factory-174ba74f.tgz
NEXUS 7 2012 nakasi:
https://dl.google.com/dl/android/aosp/nakasi-kot49h-factory-5e9db5e1.tgz
NEXUS 7 2012 nakasig:
https://dl.google.com/dl/android/aosp/nakasig-kot49h-factory-83d93b5f.tgz
How did u found the correct links?
btw, downloading, THANKS
C4SCA said:
How did u found the correct links?
btw, downloading, THANKS
Click to expand...
Click to collapse
The last 8 chars of the link really are the first 8 chars of the SHA-1 Checksum (that is correct).
You rock man! Thanks!
Does google release odex versions ?
Sent from my SM-N900T using Tapatalk
alleyezondisromo said:
Does google release odex versions ?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Yes, these images are odexed.
thanks [email protected]!!!!
flashing!
Thanks pal. really needed this.
Thanks! Was just about to flash my phone when I realized the links on Google's website doesn't work!
Sfkn2 said:
Thanks! Was just about to flash my phone when I realized the links on Google's website doesn't work!
Click to expand...
Click to collapse
lol me too...I was all excited, then I realized I just get a 404 error. I actually thought they just hadn't finished uploading the images and jumped the gun posting links. Glad I saw this thread!!
Thank you. I downloaded Android SDK, copied the dll's and fastboot/adb from the platform-tools folder to C:\windows\syswow64\ and then extracted the occam-kot49h tgz and modified the flash-all.bat as to remove the "-w" (wipe) command from the fastboot update command and then I threw my phone into fastboot mode and opened up a command prompt and ran that flash-all.bat, upgraded from 4.4 to 4.4.2 seamlessly with no data loss. Of course I did lose root as expected and I suppose I should have removed/commented out the flashboot radio command line so I could have kept LTE, oh well I'll fix that later. Thanks again.
hi thanx for the links
after downloading i had this error:
Code:
[email protected]:~/occam-kot49h$ sudo sh flash-all.sh
sending 'bootloader' (2203 KB)...
OKAY [ 0.104s]
writing 'bootloader'...
OKAY [ 0.766s]
finished. total time: 0.869s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 2.128s]
writing 'radio'...
OKAY [ 2.805s]
finished. total time: 4.934s
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'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.98
Serial Number........: 0216337d9153f835
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6340 KB)...
OKAY [ 0.301s]
writing 'boot'...
OKAY [ 0.334s]
sending 'recovery' (6888 KB)...
OKAY [ 0.344s]
writing 'recovery'...
OKAY [ 0.392s]
erasing 'system'...
OKAY [ 0.716s]
sending 'system' (713960 KB)...
OKAY [ 33.568s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 47.589s
i need some help
(BTW i executed the flash-all.sh script after deleting the "-w" option and deleting userdata.img)
activexda said:
i need some help
(BTW i executed the flash-all.sh script after deleting the "-w" option and deleting userdata.img)
Click to expand...
Click to collapse
Are you using the latest SDK? That error usually means that the version of the fatsboot command isn't one liked by the bootloader.
VivaErBetis said:
Are you using the latest SDK? That error usually means that the version of the fatsboot command isn't one liked by the bootloader.
Click to expand...
Click to collapse
ok i will download the "SDK Tools Only" package, thats all what i need right?
activexda said:
ok i will download the "SDK Tools Only" package, thats all what i need right?
Click to expand...
Click to collapse
Yes, and inside it the latest “platform tools“.
VivaErBetis said:
Yes, and inside it the latest “platform tools“.
Click to expand...
Click to collapse
ok, after trying with latest sdk i still have the same problem
is there anybody managed to install the factory image?
Maybe you messed up the script.
gm007 said:
Maybe you messed up the script.
Click to expand...
Click to collapse
i don't think so
script:
Code:
#!/bin/sh
# Copyright 2012 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.98.img
fastboot reboot-bootloader
sleep 5
fastboot update image-occam-kot49h.zip
Maybe download the file again.
activexda said:
i need some help
(BTW i executed the flash-all.sh script after deleting the "-w" option and deleting userdata.img)
Click to expand...
Click to collapse
gm007 said:
Maybe download the file again.
Click to expand...
Click to collapse
I would definitely download the file again. Did you check the MD5 sum?
Q&A for [22/07][ROM][STOCK]v2.1.0.13.001
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [22/07][ROM][STOCK]v2.1.0.13.001. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Paleskin said:
I got error with fastboot stop working
Click to expand...
Click to collapse
Me too.
In windows 10 and windows 7
Please fix it Sir.
Hello.
It`s a great work.
Thank you very match.
But have a fail in flash process.
CUSTOM and PRELOAD OKEY, but when tool begin flash SYSTEM, it write error "parse size".
This problem only with two last points: SYSTEM and next (i dont remember how it`s called)
Also, when i fire up telephone, it stop on title NOKIA.
But TWRP work and when i try to reboot after "fix permissions" it write "OS not install".
And all time TWRP write in LOG "can`t mount E:/SYSTEM"
Thanks for help)
I got this error
'mode' is not recognized as an internal or external command,
operable program or batch file.
Flashing started...
...
OKAY [ -0.000s]
finished. total time: -0.000s
Flashing RECOVERY
target reported max download size of 301989888 bytes
sending 'recovery' (7708 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.265s]
finished. total time: 0.515s
Flashing KERNEL
target reported max download size of 301989888 bytes
sending 'boot' (7274 KB)...
OKAY [ 0.234s]
writing 'boot'...
OKAY [ 0.281s]
finished. total time: 0.515s
Flashing SYSTEM
target reported max download size of 301989888 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.577s]
sending sparse 'system' (270414 KB)...
OKAY [ 9.469s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 10.062s
Flashing CUSTOM
target reported max download size of 301989888 bytes
Invalid sparse file format at header magi
sending sparse 'custom' (267176 KB)...
OKAY [ 9.313s]
writing 'custom'...
FAILED (remote: Unknown chunk type)
finished. total time: 9.329s
...
OKAY [ 0.000s]
finished. total time: 0.000s
Flashing finished...
Press any key to continue . . .
@symbuzzer @symbuzzer @symbuzzer
good job
thank bro
tool good
thinhx2 said:
tool good
Click to expand...
Click to collapse
Hi,bro
I am also use Nokia x2ds I am active dual sim with internet on cm12.1
But after reboot ist not work so bro
Tell me how to extract system.IMG file ..and repack
So I can fix ril bug and also try to fix camera....
can you make a flashable zip file contain original boot files
Hi all,
My RAZR i softbricked almost a year ago. I am determined that I will get my holidays pictures from it... please help me do so!
It gets stuck on the intel page when booting normally, I can access fastboot however I think the phone must be locked. In AP fastboot the options are:
Normal Powerup
Recovery
Factory
BP Tools
Switch Console
Power Off
Recovery will ocassionally take me to the sick looking droid.
When trying through RSD Lite I get stuck at 3/10 "boot_signed", and the phone says "preflash validation failed". I think this may be because the fastboot is locked?
When running through this guide: https://forum.xda-developers.com/showthread.php?t=2390573 unbrick.bat can't find libusb0.dll (possibly a windows 10 issue?).
I can't actually remember what version of Android I was running, however I'm pretty sure it was JB.
If anyone can advise as to what I should try next, or whether I can't recover my pictures at all, then please do get in touch.
Greg
GrogSym said:
Hi all,
My RAZR i softbricked almost a year ago. I am determined that I will get my holidays pictures from it... please help me do so!
It gets stuck on the intel page when booting normally, I can access fastboot however I think the phone must be locked. In AP fastboot the options are:
Normal Powerup
Recovery
Factory
BP Tools
Switch Console
Power Off
Recovery will ocassionally take me to the sick looking droid.
When trying through RSD Lite I get stuck at 3/10 "boot_signed", and the phone says "preflash validation failed". I think this may be because the fastboot is locked?
When running through this guide: https://forum.xda-developers.com/showthread.php?t=2390573 unbrick.bat can't find libusb0.dll (possibly a windows 10 issue?).
I can't actually remember what version of Android I was running, however I'm pretty sure it was JB.
If anyone can advise as to what I should try next, or whether I can't recover my pictures at all, then please do get in touch.
Greg
Click to expand...
Click to collapse
First u can try to flash those images manually. The fastboot command then will say a bit more than just that error.
So flash the system and boot image manually.
We can't unlock the bootloader because u will lose all data from the phone.
Hazou said:
First u can try to flash those images manually. The fastboot command then will say a bit more than just that error.
So flash the system and boot image manually.
We can't unlock the bootloader because u will lose all data from the phone.
Click to expand...
Click to collapse
When I try to flash the boot image through fastboot, I get the following:
C:\Users\Greg\Desktop>fastboot boot boot_signed
creating boot image...
creating boot image - 11536384 bytes
downloading 'boot.img'...
OKAY [ 1.432s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 1.626s
Presumably because this is restricted (ie no root)?
When I try the image file I get:
C:\Users\Greg\Desktop>fastboot flash system system_signed
(bootloader) Variable not supported!
target reported max download size of 104857600 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 733045500 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 626995964 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 515375868 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 407782140 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 296858364 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 185189116 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 74765052 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 8956 is not a multiple of the block size 4096
sending sparse 'system' (90258 KB)...
error: write_sparse_skip_chunk: don't care size 733045500 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 733045500 is not a multiple of the block size 4096
OKAY [ 8.452s]
writing 'system'...
FAILED (remote: Preflash validation failed)
finished. total time: 8.825s
Am I doing something wrong?
GrogSym said:
When I try to flash the boot image through fastboot, I get the following:
C:\Users\Greg\Desktop>fastboot boot boot_signed
creating boot image...
creating boot image - 11536384 bytes
downloading 'boot.img'...
OKAY [ 1.432s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 1.626s
Presumably because this is restricted (ie no root)?
Click to expand...
Click to collapse
Nope, "root" is only a system thingy and is most commonly used in Android when u can access system files while u are on a running system.
In this case the command "boot" is restricted in the bootloader. No way to enable that one for us. U need to use "flash"
GrogSym said:
When I try the image file I get:
C:\Users\Greg\Desktop>fastboot flash system system_signed
(bootloader) Variable not supported!
target reported max download size of 104857600 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 733045500 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 626995964 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 515375868 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 407782140 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 296858364 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 185189116 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 74765052 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 8956 is not a multiple of the block size 4096
sending sparse 'system' (90258 KB)...
error: write_sparse_skip_chunk: don't care size 733045500 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 733045500 is not a multiple of the block size 4096
OKAY [ 8.452s]
writing 'system'...
FAILED (remote: Preflash validation failed)
finished. total time: 8.825s
Am I doing something wrong?
Click to expand...
Click to collapse
Are u using the "fastboot" executable from the Android sdk? I recommend in this case to use the "mFastboot" executable.
The mfastboot executable in the RSD-Lite package should work just fine.
Just make sure u are using the latest JB (4.1.2) rsd-lite package.
Hazou said:
Nope, "root" is only a system thingy and is most commonly used in Android when u can access system files while u are on a running system.
In this case the command "boot" is restricted in the bootloader. No way to enable that one for us. U need to use "flash"
Are u using the "fastboot" executable from the Android sdk? I recommend in this case to use the "mFastboot" executable.
The mfastboot executable in the RSD-Lite package should work just fine.
Just make sure u are using the latest JB (4.1.2) rsd-lite package.
Click to expand...
Click to collapse
Thank you so much for your continued help - I'm afraid I'm no further ahead. I have tried the following:
C:\Users\Greg\Desktop>mfastboot flash boot boot_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'boot' (11264 KB)...
OKAY [ 1.421s]
writing 'boot'...
FAILED (remote: Preflash validation failed)
finished. total time: 1.799s
C:\Users\Greg\Desktop>mfastboot flash system system_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
Multi-Flash is enabled!
sending 'system' (102400 KB)...
OKAY [ 9.850s]
writing 'system'...
FAILED (remote: Preflash validation failed)
finished. total time: 10.479s
C:\Users\Greg\Desktop>
The phone returns: (...security version downgraded then)
PIV block validation failed
EIV block validation failed for system
Invalid PIV image: system
Fastboot command failed
Does this suggest I am using the wrong image file? CFC_9.8.2I-50_SMI-29_S7_USASMIJBRTGB.xml
I can't see an alternative for a UK phone on 4.1.2
Maybe I could just fly you to my house and you can fix it for me If there is a tutorial that I should be following that I have missed, then please do let me know.
Many thanks again,
Greg
GrogSym said:
Thank you so much for your continued help - I'm afraid I'm no further ahead. I have tried the following:
C:\Users\Greg\Desktop>mfastboot flash boot boot_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'boot' (11264 KB)...
OKAY [ 1.421s]
writing 'boot'...
FAILED (remote: Preflash validation failed)
finished. total time: 1.799s
C:\Users\Greg\Desktop>mfastboot flash system system_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
Multi-Flash is enabled!
sending 'system' (102400 KB)...
OKAY [ 9.850s]
writing 'system'...
FAILED (remote: Preflash validation failed)
finished. total time: 10.479s
C:\Users\Greg\Desktop>
The phone returns: (...security version downgraded then)
PIV block validation failed
EIV block validation failed for system
Invalid PIV image: system
Fastboot command failed
Does this suggest I am using the wrong image file? CFC_9.8.2I-50_SMI-29_S7_USASMIJBRTGB.xml
I can't see an alternative for a UK phone on 4.1.2
Maybe I could just fly you to my house and you can fix it for me If there is a tutorial that I should be following that I have missed, then please do let me know.
Many thanks again,
Greg
Click to expand...
Click to collapse
We can't get around that. The error message indicates that the wrong system or other images are flashed into the device. Sry, I have no clue on how to restore that.
Kitkat?
Could it be that failed OTA updates won't allow downgrades?
I have a xt890 that is bootlooping with the very same errors while trying to fastboot flash 4.1.2 en.GB.
I'm coming to the conclusion that the OTA Update partially succeeded and its no longer accepting JB firmware...
Hazou said:
We can't get around that. The error message indicates that the wrong system or other images are flashed into the device. Sry, I have no clue on how to restore that.
Click to expand...
Click to collapse
I am using QFIL to try and revive my X4, but I have no idea how to get into EDL mode when I cannot do anything with the device. Computer recognizes it when I plug it in as Quectel QDLoader 9008 in Ports, but that's it.
Any suggestions would be appreciated. I don't want to have to pay MOTO to fix it if possible.
I've exhausted every resource I have.
Thank you anyone that can help or at least point me in the right direction.\
EDIT: When I was eMMC Software Download app, phone shows in COM3 Download mode, but I need an XML file to flash with that tool and don't know how to get that.
I have never heard of this method. I've never hard bricked my device either. How did this happen was it by a bad flash or corrupt update? I found this https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Maybe it will help. Their may be a way to do it instead of xml. Either way it goes xml is just acompressed file with the ROM in it. Is it possible to find a file compressor with .xml format?
Knowing previous Moto phones you'll need a blankflash file that only Lenovo/Motorola has and may or may not get leaked in the future. Just to make sure, you really can't enter into fastboot mode.?
DustArma said:
Knowing previous Moto phones you'll need a blankflash file that only Lenovo/Motorola has and may or may not get leaked in the future. Just to make sure, you really can't enter into fastboot mode.?
Click to expand...
Click to collapse
No, my power went out in the middle of fastboot flashing and screwed up all the partitions. I am stuck without the blankflash.. Thank you for replying to try to help.
christopher68369 said:
I have never heard of this method. I've never hard bricked my device either. How did this happen was it by a bad flash or corrupt update? I found this https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Maybe it will help. Their may be a way to do it instead of xml. Either way it goes xml is just acompressed file with the ROM in it. Is it possible to find a file compressor with .xml format?
Click to expand...
Click to collapse
Yes, already read all of that, doesn't help. Unfortunately, I am at ground zero still.
johnjingle said:
Yes, already read all of that, doesn't help. Unfortunately, I am at ground zero still.
Click to expand...
Click to collapse
you can not take it to the Moto warranty? you do not have to know how the phone went blank...
bookworth said:
you can not take it to the Moto warranty? you do not have to know how the phone went blank...
Click to expand...
Click to collapse
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
LazyCountry said:
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
Click to expand...
Click to collapse
Bro! It's works! Thanks for blank-flash for my soft bricked moto x4.
O link não funciona
LazyCountry said:
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
Click to expand...
Click to collapse
Please guy, this link not work! Help me Please. Thanks
silvamatta said:
Please guy, this link not work! Help me Please. Thanks
Click to expand...
Click to collapse
It does, if you follow his instructions stated after the link.
Consegui agora!
jhedfors said:
It does, if you follow his instructions stated after the link.
Click to expand...
Click to collapse
Thanks Very much! work perfectly
Hi. I have a similar issue where all I have is the Qualcomm QD Loader 9008 and I attempted to use the blank flash to resolve it but I got the following error:
**** Log buffer [000001] 2018-07-26_14:55:02 ****
[ 0.000] Opening device: \\.\COM6
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 172 (0xac)
[ 0.004] ...cpu.sn = 2293722822 (0x88b76ec6)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.006] ...filename = pkg.xml
[ 0.007] Loading programmer
[ 0.008] ...filename = programmer.elf
[ 0.008] Sending programmer
[ 0.196] Handling things over to programmer
[ 0.197] Identifying CPU version
[ 0.197] Waiting for firehose to get ready
[ 3.212] ...SDM630 1.0
[ 3.213] Determining target secure state
[ 3.215] ...secure = yes
[ 3.238] Configuring device...
[ 3.243] Flashing GPT...
[ 3.243] Flashing partition with gpt.bin
[ 3.247] Initializing storage
[ 4.421] Target NAK!
[ 4.421] ...ERROR: Failed to open the SDCC Device slot 0 partition 0
[ 4.422] ...ERROR: Failed to open the device 1 slot 0 partition 0
[ 4.423] ...INFO: Device type 1, slot 0, partition 0, error 0
[ 4.423] ...WARN: Get Info failed to open 1 slot 0, partition 0, error 0
[ 4.424] ...ERROR: Failed to get device info slot:0artition:0
[ 4.424] ...GetStorageInfo Failed - storage_device_get_info() returned FALSE
[ 4.424] ...ERROR 14: Line 1283: HANDLE_STORAGE_INFO_FAILURE
[ 4.424] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 4.424] Check qboot_log.txt for more details
[ 4.425] Total time: 4.426s
[ 4.425]
[ 4.425] qboot version 3.86
[ 4.425]
[ 4.425] DEVICE {
[ 4.425] name = "\\.\COM6",
[ 4.425] flags = "0x144",
[ 4.425] addr = "0x62FD64",
[ 4.425] sahara.current_mode = "0",
[ 4.425] api.buffer = "0x2B15020",
[ 4.425] cpu.serial = "2293722822",
[ 4.425] cpu.id = "172",
[ 4.425] cpu.sv_sbl = "1",
[ 4.425] cpu.name = "SDM630",
[ 4.425] storage.type = "eMMC",
[ 4.425] sahara.programmer = "programmer.elf",
[ 4.425] module.firehose = "0x2A51630",
[ 4.425] api.firehose = "0xF2EF68",
[ 4.425] cpu.ver = "256",
[ 4.425] cpu.vername = "1.0",
[ 4.425] fh.max_packet_sz = "1048576",
[ 4.425] fh.storage_inited = "1",
[ 4.425] provisioning_may_hang = "true",
[ 4.425] }
[ 4.425]
silvamatta said:
Please guy, this link not work! Help me Please. Thanks
Click to expand...
Click to collapse
You mean you can't download ?
waltwittman1 said:
Hi. I have a similar issue where all I have is the Qualcomm QD Loader 9008 and I attempted to use the blank flash to resolve it but I got the following error: (log text omitted)
Click to expand...
Click to collapse
I got a similar error when I tried the blank-flash on my bricked Moto X4. @waltwittman1 please let me know if you find a solution.
serial_write() Error
After running blank-flash.sh with the phone connected and VolDown+Power held, I only can get this error. Anyone have any ideas or a singleimage.bin file for a Moto X4 XT1900-1 (Android One)?
Motorola qboot utility version 3.86
[ 0.000] Opening device: /dev/ttyUSB1
[ 0.000] Detecting device
[ 21.382] ...cpu.id = 172 (0xac)
[ 21.382] ...cpu.sn = 4247084357 (0xfd255d45)
[ 21.382] Opening singleimage
[ 21.382] Loading package
[ 21.384] ...filename = pkg.xml
[ 21.385] Loading programmer
[ 21.385] ...filename = programmer.elf
[ 21.385] Sending programmer
[ 21.570] Handling things over to programmer
[ 21.570] Identifying CPU version
[ 21.570] Waiting for firehose to get ready
[ 24.570] serial_write(), line 280: Input/output error
[104.005] Waiting for firehose to get ready
[107.005] serial_write(), line 280: Input/output error
ttyUSB Permissions Linux
mistryous said:
After running blank-flash.sh with the phone connected and VolDown+Power held, I only can get this error. Anyone have any ideas or a singleimage.bin file for a Moto X4 XT1900-1 (Android One)?
[ 24.570] serial_write(), line 280: Input/output error
[104.005] Waiting for firehose to get ready
[107.005] serial_write(), line 280: Input/output error
Click to expand...
Click to collapse
While I was running as root on my Linux system, this was solved as an issue between the device showing up on /dev/ttyUSB0 initially. I set permissions correctly there, but it reconnects with VolDown+Power on /dev/ttyUSB1 which had limited permissions. While udev rules could solve it, I was lucky to catch the device correctly in time to manually change the permissions and have blankflash progress all the way through. [Upon further thought root should have solved this, so it is likely just an issue with how devices/permissions are set up on my system].
Owner trashed the blankflash file. Can anyone hook me up please?
Here you go.
luvcustom said:
Owner trashed the blankflash file. Can anyone hook me up please?
Click to expand...
Click to collapse
This is the one I use. This is my first post to the XDA forums so they prevented me from linking to my dropbox. So, replace the [dot] with a . and you should be good.
.dropbox [dot] com/s/3xi85sy207x3vs6/blankflash.zip?dl=0[/url]
Win 10 waiting for device message and nothing more.
and no 9008 port
moved