Related
Hi,
I tried to update to Android 4.2 (from 4.1.2) today, but it failed at the stock recovery saying:
[..]
assert failed: apply_patch_check("/system/app/Books.apk", ........
Installation aborted.
Screenshot: https://www.dropbox.com/s/b8lk0n147cbcfuv/20121114_121646_4_bestshot.jpg
Using Titanium Backup I used to make Google Books a Userland application and uninstalled it a while ago, because I wanted to remove some bloatware. I installed the backup I had and made it a system-application again, but its still giving me that error. Even factory reset didnt help.
What options do I have? How can I flash the full image?
Kind regards
Alex
Nevermind, I found the factory image at
https://developers.google.com/android/nexus/images#nakasijop40c
Downloaded it, did a titanium backup, flashed image via flash-all.bat, restored root, restored backup and 4.2 with root is all up and running now.
Same problem with apply_patch_check error bij update.
Also try to flash full factory image 4.2 by fastboot.
After install and reboot, Google icon in screen, doesn't startup.
That 5x but no success.
Same install with factory image 4.1.2 and no problem.
Help!
---------- Post added at 01:10 PM ---------- Previous post was at 01:02 PM ----------
Hello Alex,
You said, flashed bij Flash-all.bat.
How does that work? You may have a brief description of how you do it?
Thank you!
In the .zip you downloaded, there is a file called flash-all.bat. For example it does this for the WiFi version:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.13.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jop40c.zip
echo Press any key to exit...
pause >nul
exit
Check your version an run it in platform-tools with all content beeing there of course. Its quite easy
You sense about PATH I do not understand.
The rest I have indeed done in cmd
I have indeed PlatformTools and I have all five files in that folder.
Same folder where adb.exe also capable.
I've done in cmd in the platformtools path:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.13.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-jop40c.zip
Then start the nexus7 but remains on the startup screen on the google logo.
Am I forgetting something?
whats the output of the fastboot commands from above?
I have the same problem but with GooglePinyinime.apk.
Have just worked out how to sideload using adb and am getting stuck on this error.
I did freeze this app using titanium pro, then unfroze it when I upgraded to 4.1.2 ota successfully, so can't understand why its pulling up an error now?
Am a bit of a noob with these commands so would be very grateful for any help.
Am on stock rom, rooted and no custom recovery.
Thanks.
Sent from my Nexus 7 using Tapatalk 2
simacca said:
I have the same problem but with GooglePinyinime.apk.
Have just worked out how to sideload using adb and am getting stuck on this error.
I did freeze this app using titanium pro, then unfroze it when I upgraded to 4.1.2 ota successfully, so can't understand why its pulling up an error now?
Am a bit of a noob with these commands so would be very grateful for any help.
Am on stock rom, rooted and no custom recovery.
Thanks.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Do you have fastboot installed on your computer? I am not in front of my development computer so I can't give you specific details but I had a several modifications to /system so I didn't bother trying to reverse them and instead flashed the original 4.1.2 system.img.
The (rough) procedure for this is:
1. Backup your current 4.1.2 rom in case you can't live with 4.2
2. Plug the nexus into your computer and boot into the bootloader (up vol + down vol + power)
3. On your computer, download the 4.1.2 factory image from https://dl.google.com/dl/android/aosp/nakasi-jzo54k-factory-973f190e.tgz
4. Unzip the image and then unzip the zip file that was inside the image (I can't remember the name but I believe there is only one)
5. If you unzipped everything correctly you should have a system.img file, open a command window and navigate to the directory that contains the system.img file and type:
Code:
fastboot flash system system.img
Sorry I don't have the specific details. If no one else has filled in the missing file names by the time I get home and you are comfortable with this procedure I will update this with the proper names.
C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-group
er-4.13.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.290s]
writing 'bootloader'...
OKAY [ 1.252s]
finished. total time: 1.548s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
C:\android-sdk-windows\platform-tools>fastboot -w update image-nakasi-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.13
Baseband Version.....: N/A
Serial Number........: 015d2578a3140811
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4942 KB)...
OKAY [ 0.599s]
writing 'boot'...
OKAY [ 0.405s]
sending 'recovery' (5444 KB)...
OKAY [ 0.660s]
writing 'recovery'...
OKAY [ 0.348s]
erasing 'system'...
OKAY [ 0.155s]
sending 'system' (477136 KB)...
OKAY [ 60.010s]
writing 'system'...
OKAY [ 23.794s]
erasing 'userdata'...
OKAY [ 1.092s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 27.895s]
erasing 'cache'...
OKAY [ 0.119s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 1.940s]
rebooting...
finished. total time: 117.197s
C:\android-sdk-windows\platform-tools>
Nexus root toolkit works
Nexus root toolkit works like a champ for restoring stock if you need it.
Works flawlessly in windows 7 for me.
http://www.wugfresh.com/nrt/
The real issue with the the assert errors is that you changed something you should not have. The 4.2 update hash checks the original system apps for consistency. If you changed any of the System apps outside of an official update you get the assert errors when trying to flash the new update.
Have the same problem...
[..]
assert failed: apply_patch_check("/system/app/Books.apk", ........
Installation aborted.
Anyone manage ti fix it without restoring original rom would be nice....
alex2308 said:
Nevermind, I found the factory image at
https://developers.google.com/android/nexus/images#nakasijop40c
Downloaded it, did a titanium backup, flashed image via flash-all.bat, restored root, restored backup and 4.2 with root is all up and running now.
Click to expand...
Click to collapse
Hi Alex,
Did flashed factory image returned our Nexus like a new phone or just restoring system files? I want to flash factory image but afraid if it's like a factory reset
everyday_ said:
Hi Alex,
Did flashed factory image returned our Nexus like a new phone or just restoring system files? I want to flash factory image but afraid if it's like a factory reset
Click to expand...
Click to collapse
Its like a full factory reset, everything is gone (also the /sdcard folder with the downloads and stuff). Restoring was pretty easy, I copied the /sdcard stuff via USB to my computer and used titanium backup to backup the apps with settings (and copied that too to my computer). The only thing I had to setup again was WiFi, Homescreen and Email (although you can backup them via Titanium, which I didnt).
Mathijs17 said:
C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-group
er-4.13.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.290s]
writing 'bootloader'...
OKAY [ 1.252s]
finished. total time: 1.548s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
C:\android-sdk-windows\platform-tools>fastboot -w update image-nakasi-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.13
Baseband Version.....: N/A
Serial Number........: 015d2578a3140811
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4942 KB)...
OKAY [ 0.599s]
writing 'boot'...
OKAY [ 0.405s]
sending 'recovery' (5444 KB)...
OKAY [ 0.660s]
writing 'recovery'...
OKAY [ 0.348s]
erasing 'system'...
OKAY [ 0.155s]
sending 'system' (477136 KB)...
OKAY [ 60.010s]
writing 'system'...
OKAY [ 23.794s]
erasing 'userdata'...
OKAY [ 1.092s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 27.895s]
erasing 'cache'...
OKAY [ 0.119s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 1.940s]
rebooting...
finished. total time: 117.197s
C:\android-sdk-windows\platform-tools>
Click to expand...
Click to collapse
Did you do a erase or just flash over them?
I had a perfectly working rooted Nexus 6 with twrp recovery. There was, a screen defect, and I was about to send it to Motorola under warranty., and needed to reset to factory. I guess I did this in the wrong order.
First, I did a "fastboot oem lock" which worked (too well)
Then I went into recovery (twrp) and used factory reset, which failed.
When I try and reboot the system, I get into a blinking teamwin screen.
The USB connection still works, andI can get to fastboot bootloader, , but can no longer oem unlock , "Check 'Allow OEM Unlock' in Developer Options.".
All the bootloader options, recovery, factory, bp tools all go to the flashing teamwin.
Is there any way to recover from this? Help!
kmandel said:
I had a perfectly working rooted Nexus 6 with twrp recovery. There was, a screen defect, and I was about to send it to Motorola under warranty., and needed to reset to factory. I guess I did this in the wrong order.
First, I did a "fastboot oem lock" which worked (too well)
Then I went into recovery (twrp) and used factory reset, which failed.
When I try and reboot the system, I get into a blinking teamwin screen.
The USB connection still works, andI can get to fastboot bootloader, , but can no longer oem unlock , "Check 'Allow OEM Unlock' in Developer Options.".
All the bootloader options, recovery, factory, bp tools all go to the flashing teamwin.
Is there any way to recover from this? Help!
Click to expand...
Click to collapse
since you still have twrp installed, you might have a chance. but your one and only option would be to fastboot format userdata and cache.
>since you still have twrp installed, you might have a chance. but your one and only option would be to fastboot format userdata and cache.
I suppose twrp is still installed, if thats what gives the teamwin loop. I can't actually get into twrp.
Would I be issuing two separate fastboot formats, or can I specify both userdata and cache on the same fastboot format.
If this actually worked, is the expectation that I could boot the system?
kmandel said:
>since you still have twrp installed, you might have a chance. but your one and only option would be to fastboot format userdata and cache.
I suppose twrp is still installed, if thats what gives the teamwin loop. I can't actually get into twrp.
Would I be issuing two separate fastboot formats, or can I specify both userdata and cache on the same fastboot format.
If this actually worked, is the expectation that I could boot the system?
Click to expand...
Click to collapse
yes. if you didnt have twrp installed, then id say you have a 0% chance. with twrp being installed, your chances went up dramatically, like a 50-50 chance.
Hint...
TeamWinRecoveryProject TWRP
Formats should fix that
Then youncan flash.a.rom.and.enable oem.unlock
Protip. Never lock the bootloader until you are back to complete stock. Basically, you don't start with it. You end with it.
graydiggy said:
Protip. Never lock the bootloader until you are back to complete stock. Basically, you don't start with it. You end with it.
Click to expand...
Click to collapse
Protip #2: Never lock the bootloader unless you intend to return it for repair.
cam30era said:
Protip #2: Never lock the bootloader unless you intend to return it for repair.
Click to expand...
Click to collapse
You didn't read the OP, did you?
graydiggy said:
You didn't read the OP, did you?
Click to expand...
Click to collapse
Yes, but it was long enough that I forgot.
cam30era said:
Yes, but it was long enough that I forgot.
Click to expand...
Click to collapse
some of us must be older than others :angel:
simms22 said:
some of us must be older than others :angel:
Click to expand...
Click to collapse
You bet!
Ok, I hate to act needy but I'm afraid of screwing this up beyond hope.
I assume that I first do
fastboot format userdata
fastboot format cache
Then what? Reboot?
If so what would I expect to see, Lolipop or twrp, or something else?
If its not Lollipop I guess I need to load a rom. Until now the only rom's I've loaded
are the factory firmware with "flash-all". But that needs oem unlock which I can't do.
kmandel said:
Ok, I hate to act needy but I'm afraid of screwing this up beyond hope.
I assume that I first do
fastboot format userdata
fastboot format cache
Then what? Reboot?
If so what would I expect to see, Lolipop or twrp, or something else?
If its not Lollipop I guess I need to load a rom. Until now the only rom's I've loaded
are the factory firmware with "flash-all". But that needs oem unlock which I can't do.
Click to expand...
Click to collapse
after, try booting up or try booting into twrp and see if you can load a rom, gapps, and supersu. if you dont have gapps or supersu, youll be fine this time. most importantly would be booting up and enabling oem unlocking in dev options.
Well I did the formats, and then a reboot. This time it boots into rotating colored balls
which seemed hopeful However, its been a half an hour now and they are still rotating.
I know this can go for a while, and am hesitant to interrupt it. but this seems ominous.
As far as the formats, here is the output
# fastboot format userdata
erasing 'userdata'...
OKAY [ 0.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 59751923712
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14587872
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3653632 inodes and 275392/14587872 blocks
sending 'userdata' (141067 KB)...
writing 'userdata'...
(bootloader) Unlock before flashing
FAILED (remote failure)
finished. total time: 5.065s
# fastboot format cache
erasing 'cache'...
OKAY [ 0.030s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'cache' (6248 KB)...
writing 'cache'...
(bootloader) Unlock before flashing
FAILED (remote failure)
finished. total time: 0.241s
kmandel said:
Well I did the formats, and then a reboot. This time it boots into rotating colored balls
which seemed hopeful However, its been a half an hour now and they are still rotating.
I know this can go for a while, and am hesitant to interrupt it. but this seems ominous.
As far as the formats, here is the output
# fastboot format userdata
erasing 'userdata'...
OKAY [ 0.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 59751923712
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14587872
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3653632 inodes and 275392/14587872 blocks
sending 'userdata' (141067 KB)...
writing 'userdata'...
(bootloader) Unlock before flashing
FAILED (remote failure)
finished. total time: 5.065s
# fastboot format cache
erasing 'cache'...
OKAY [ 0.030s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'cache' (6248 KB)...
writing 'cache'...
(bootloader) Unlock before flashing
FAILED (remote failure)
finished. total time: 0.241s
Click to expand...
Click to collapse
kmandel said:
Well I did the formats, and then a reboot. This time it boots into rotating colored balls
which seemed hopeful However, its been a half an hour now and they are still rotating.
I know this can go for a while, and am hesitant to interrupt it. but this seems ominous.
As far as the formats, here is the output
# fastboot format userdata
erasing 'userdata'...
OKAY [ 0.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 59751923712
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14587872
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3653632 inodes and 275392/14587872 blocks
sending 'userdata' (141067 KB)...
writing 'userdata'...
(bootloader) Unlock before flashing
FAILED (remote failure)
finished. total time: 5.065s
# fastboot format cache
erasing 'cache'...
OKAY [ 0.030s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'cache' (6248 KB)...
writing 'cache'...
(bootloader) Unlock before flashing
FAILED (remote failure)
finished. total time: 0.241s
Click to expand...
Click to collapse
Boot to TWRP. Download a ROM from development forums to your PC. Connect your nexus to PC while it's booted to TWRP. You should see the nexus internal storage show up on your PC. Drag and drop or copy and paste the ROM from PC to internal storage. Flash ROM with TWRP. Boot up, skip all set up, enable developer options and then boot to bootloader and fastboot OEM unlock.
To make a long story short: SUCCESS!
The longer story was that there were complications.
-- Filemanager came up with an empty "SHAMU' that it couldn't write to
- I used adb push to get a rom image over to the rootfs
- the install had trouble with the data partition. I had to format
- turned out the rootfs partition was a bad place for the rom image, had to move it to /data
- install of rom from twrp finally worked
- using the new rom to enable oem unlocking worked
- flash-all of factory image failed. Had to individually flashboot flash piece by piece for some reason.
Finally: SUCCESS. Thanks for all you help!!
kmandel said:
To make a long story short: SUCCESS!
The longer story was that there were complications.
-- Filemanager came up with an empty "SHAMU' that it couldn't write to
- I used adb push to get a rom image over to the rootfs
- the install had trouble with the data partition. I had to format
- turned out the rootfs partition was a bad place for the rom image, had to move it to /data
- install of rom from twrp finally worked
- using the new rom to enable oem unlocking worked
- flash-all of factory image failed. Had to individually flashboot flash piece by piece for some reason.
Finally: SUCCESS. Thanks for all you help!!
Click to expand...
Click to collapse
I had the same problem can you have me please advise what did you do
kmandel said:
To make a long story short: SUCCESS!
The longer story was that there were complications.
-- Filemanager came up with an empty "SHAMU' that it couldn't write to
- I used adb push to get a rom image over to the rootfs
- the install had trouble with the data partition. I had to format
- turned out the rootfs partition was a bad place for the rom image, had to move it to /data
- install of rom from twrp finally worked
- using the new rom to enable oem unlocking worked
- flash-all of factory image failed. Had to individually flashboot flash piece by piece for some reason.
Finally: SUCCESS. Thanks for all you help!!
Click to expand...
Click to collapse
You certainly made a mountain out of a mole hill here.
fastboot format cache
fastboot format userdata - this should fix TWRP like I said on page 1.
Boot into TWRP and tick the box "enable mtp" then copy a rom to from your computer using windows explorer like you would if it was booted to android.
Why would you put data on rootfs?
Important lesson, if you're going to be rooted, know your phone
I had my nexus 6 rooted and unlocked then wanted to unroot to be able to upsdate to M.
Although when I tried to re-flash it ended up not being able to boot back up. now i have a nexus in bootloader but cannot get the system.img to flash.
I have tried doing all indiviually as well as using the flash all.bat . and i get this error everytime
sending sparse 'system' (522932 KB)...
FAILED (data transfer failure (Unknown error))
I have also tried using twrp to move over the .zip of the factory 5.1.1 and it just stops transferring about a 3rd of the way through.
I am fairly certain that i have the latest fastboot as well as all the latest from the sdk tools manager
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.133s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.363s]
finished. total time: 0.497s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (85419 KB)...
OKAY [ 2.790s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.142s]
finished. total time: 3.932s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 28474998784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6951904
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...: moto-apq8084-71.10
Baseband Version.....: D4.0-9625-02.101
Serial Number........: ZX1G22CVC4
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.003s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (7741 KB)...
OKAY [ 0.250s]
writing 'boot'...
OKAY [ 0.109s]
sending 'recovery' (8331 KB)...
OKAY [ 0.297s]
writing 'recovery'...
OKAY [ 0.125s]
sending sparse 'system' (522932 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 21.199s
Press any key to exit...
It looks like a connection problem somewhere. Are you able to try a new cable or USB port?
If you have the SDK installed make sure it's updated or use mfastboot either one will work with the larger file sizes.
http://mark.cdmaforums.com/ADB.htm
=====how to flash dead Nokia x2 readed as [ RELINK HS-USB QD-LOADER 9008 ] instead of [ QHSUSB_BULK ]=====
all u need is:
1- Nokia x2 firmware files from here insert your product code ,click submit then download all the files in the list and put them together in one folder [i named it "RM-1013"]
2- QPST_2.7.422 or here
3- QDLoader HS-USB Driver or here
**remove the phone's battery and put it back after 5 seconds connect the phone with usb cable**
After downloading and installing all files
open start menu and type in search QFIL
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
open QFIL in "programmer path" map it to the firmware and select:
"rm1013_2.1.0.13_user_prog_emmc_firehose_8x10.mbn"
next press "Load XML" then type in file name *.xml press open and chose:
"rm1013_2.1.0.13_059V782_001_rawprogram_unsparse_ui.xml"
then it will automatically ask u for "Patch File"
type in file name *.xml press open and chose:
P12027803dpi600_label_layout.xml
last thing press Download and take a little rest while the rom is being downloaded to your Nokia x2 :silly:
Facing any problem ? list it below
sry for bad english
Very easy http://forum.xda-developers.com/nokia-x2/help/how-to-recover-hard-bricked-nokia-x2-t3072157
But thank bro for tip
thinhx2 said:
Very easy http://forum.xda-developers.com/nokia-x2/help/how-to-recover-hard-bricked-nokia-x2-t3072157
But thank bro for tip
Click to expand...
Click to collapse
you're welcome
this also works with all Snapdragon devices
thinhx2 said:
Very easy http://forum.xda-developers.com/nokia-x2/help/how-to-recover-hard-bricked-nokia-x2-t3072157
But thank bro for tip
Click to expand...
Click to collapse
this does not work forr me. i am getting this error.
Failed using Sahara protocol
Exception:
Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownloadException: Failed using Sahara protocol ---> Nokia.Delta.Gemini.EmergencyDownload.SaharaException: Image transfer ended with failure: InvalidImageTypeReceived
at Nokia.Delta.Gemini.EmergencyDownload.Sahara.Download(String filePath)
at Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownload.SetToFirehoseMode()
--- End of inner exception stack trace ---
at Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownload.SetToFirehoseMode()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__15(Object state)
---------- Post added at 11:17 AM ---------- Previous post was at 11:09 AM ----------
Ramy3r said:
=====how to flash dead Nokia x2 readed as [ RELINK HS-USB QD-LOADER 9008 ] instead of [ QHSUSB_BULK ]=====
all u need is:
1- Nokia x2 firmware files from here insert your product code ,click submit then download all the files in the list and put them together in one folder [i named it "RM-1013"]
2-QPST_2.7.422
3- QDLoader HS-USB Driver
**remove the phone's battery and put it back after 5 seconds connect the phone with usb cable**
After downloading and installing all files
open start menu and type in search QFIL
open QFIL in "programmer path" map it to the firmware and select:
"rm1013_2.1.0.13_user_prog_emmc_firehose_8x10.mbn"
next press "Load XML" then type in file name *.xml press open and chose:
"rm1013_2.1.0.13_059V782_001_rawprogram_unsparse_ui.xml"
then it will automatically ask u for "Patch File"
type in file name *.xml press open and chose:
P12027803dpi600_label_layout.xml
last thing press Download and take a little rest while the rom is being downloaded to your Nokia x2 :silly:
Facing any problem ? list it below
**Note**
Works with all snapdragon devices
so if u have another device all u need to change is the firmware files
sry for bad english
Click to expand...
Click to collapse
download links for drivers not working.
jkenic said:
download links for drivers not working.
Click to expand...
Click to collapse
broken links updated
thx for informing me
jkenic said:
this does not work forr me. i am getting this error.
Failed using Sahara protocol
Exception:
Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownloadException: Failed using Sahara protocol ---> Nokia.Delta.Gemini.EmergencyDownload.SaharaException: Image transfer ended with failure: InvalidImageTypeReceived
at Nokia.Delta.Gemini.EmergencyDownload.Sahara.Download(String filePath)
at Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownload.SetToFirehoseMode()
--- End of inner exception stack trace ---
at Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownload.SetToFirehoseMode()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__15(Object state)
---------- Post added at 11:17 AM ---------- Previous post was at 11:09 AM ----------
download links for drivers not working.
Click to expand...
Click to collapse
bro has install nokia care suite?
thinhx2 said:
bro has install nokia care suite?
Click to expand...
Click to collapse
it is the ncs that is giving me the error. i have done everything needed to be done to get my x2 back....
---------- Post added at 02:54 PM ---------- Previous post was at 02:39 PM ----------
Ramy3r said:
broken links updated
thx for informing me
Click to expand...
Click to collapse
u re welcome but number 2 download link still not working.......
jkenic said:
it is the ncs that is giving me the error. i have done everything needed to be done to get my x2 back....
---------- Post added at 02:54 PM ---------- Previous post was at 02:39 PM ----------
u re welcome but number 2 download link still not working.......
Click to expand...
Click to collapse
sry fixed and add links from google drive
Ramy3r said:
=====how to flash dead Nokia x2 readed as [ RELINK HS-USB QD-LOADER 9008 ] instead of [ QHSUSB_BULK ]=====
all u need is:
1- Nokia x2 firmware files from here insert your product code ,click submit then download all the files in the list and put them together in one folder [i named it "RM-1013"]
2- QPST_2.7.422 or here
3- QDLoader HS-USB Driver or here
**remove the phone's battery and put it back after 5 seconds connect the phone with usb cable**
After downloading and installing all files
open start menu and type in search QFIL
open QFIL in "programmer path" map it to the firmware and select:
"rm1013_2.1.0.13_user_prog_emmc_firehose_8x10.mbn"
next press "Load XML" then type in file name *.xml press open and chose:
"rm1013_2.1.0.13_059V782_001_rawprogram_unsparse_ui.xml"
then it will automatically ask u for "Patch File"
type in file name *.xml press open and chose:
P12027803dpi600_label_layout.xml
last thing press Download and take a little rest while the rom is being downloaded to your Nokia x2 :silly:
Facing any problem ? list it below
**Note**
Works with all snapdragon devices
so if u have another device all u need to change is the firmware files
sry for bad english
Click to expand...
Click to collapse
i go an error
Start Download
Program Path:C:\Users\EJINI\Desktop\New folder\RM-1013-1\rm1013_2.1.0.13_user_prog_emmc_firehose_8x10.mbn
COM Port number:9
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
almost same with the nokia care suite.
jkenic said:
i go an error
Start Download
Program Path:C:\Users\EJINI\Desktop\New folder\RM-1013-1\rm1013_2.1.0.13_user_prog_emmc_firehose_8x10.mbn
COM Port number:9
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
almost same with the nokia care suite.
Click to expand...
Click to collapse
Do u have any problems with ur operating system maybe its not running very well or u have some program that interferes with the download/flashing process
Sent from my Nokia_X2 using XDA Labs
There's nothing wrong with the OS that I know of.... Maybe it's the phone...did not work with windows 10
jkenic said:
There's nothing wrong with the OS that I know of.... Maybe it's the phone...did not work with windows 10
Click to expand...
Click to collapse
Sry for late comment .. Win 10 has a lot of support issues like the error 0x000007 with some games and programs ... I recommend win 7 for best results
Sent from my Nokia_X2 using XDA Labs
Work with lumia devices?
thinhx2 said:
Work with lumia devices?
Click to expand...
Click to collapse
i tested this only on android devices i'm not sure about windows phone tbh
but if it has same files "firehose , rawprogram and label layout" included in firmware files then its possible
error
Hi guys. Please help me with an error. If the firmware gets up in the middle of it.
Hoоdlum said:
Hi guys. Please help me with an error. If the firmware gets up in the middle of it.
Click to expand...
Click to collapse
First of all have you downloaded the full firmware files ? "66 files, 902 MB"
Sent from my Nokia X2 using XDA Labs
Ramy3r said:
First of all have you downloaded the full firmware files ? "66 files, 902 MB"
Sent from my Nokia X2 using XDA Labs
Click to expand...
Click to collapse
66 Yes 902mb file, but it does not end here from another site. Here's why not swing.
Hoоdlum said:
66 Yes 902mb file, but it does not end here from another site. Here's why not swing.
Click to expand...
Click to collapse
Try again using the version I posted of qpst
Sent from my Nokia ara using XDA Labs
Ramy3r said:
Try again using the version I posted of qpst
Sent from my Nokia ara using XDA Labs
Click to expand...
Click to collapse
I downloaded from your site on the links firmware driver program. Error exact same stands in the middle.
That log
Code:
[FONT="Verdana"][B]Validating Application Configuration
Load APP Configuration
COM:-1
SAHARA:True
SAHARA:C:\RM-1013\rm1013_2.1.0.12_user_prog_emmc_firehose_8x10.mbn
SEARCHPATH:C:\RM-1013
RAWPROGRAM:
rm1013_2.1.0.12_059V786_001_rawprogram_unsparse_ui.xml
PATCH:
P12026702dpi600_label_layout.xml
ACKRAWDATAEVERYNUMPACKETS:True
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:True
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
READBACKMODE:0
RESETAFTERDOWNLOAD:True
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: C:\RM-1013
RAWPROGRAM file path: C:\RM-1013\rm1013_2.1.0.12_059V786_001_rawprogram_unsparse_ui.xml
PATCH file path:C:\RM-1013\P12026702dpi600_label_layout.xml
Programmer Path:C:\RM-1013\rm1013_2.1.0.12_user_prog_emmc_firehose_8x10.mbn
Start Download
Program Path:C:\RM-1013\rm1013_2.1.0.12_user_prog_emmc_firehose_8x10.mbn
COM Port number:9
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Enable Ack Raw Data Every 100Packets
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:9
Sending NOP
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
Set TxBuffer 0xc000, RxBuffer 0x4000
Firehose configure packet sent successfully!
ReadBackMode:No_Readback
Disable read back
Total Bytes To Program 0x37226800
Download Image
PROGRAM: Replace the partition sectors number 0x20000 to file size in sector 0x125c3
PROGRAM: Partition 0, Sector: 16384, Length: 75203 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_NON-HLOS.bin
FireHose Log: start 16384, num 75203
FireHose Log: Write failed Sector 16480, Errno 2
FireHose Log: Finished sector address 16480
PROGRAM: Written Bytes 0x24b8600 (64)
Program Size: 36.72 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x1ec
PROGRAM: Partition 0, Sector: 147456, Length: 492 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_sbl1.mbn
FireHose Log: start 147456, num 492
FireHose Log: Write failed Sector 147456, Errno 2
FireHose Log: Finished sector address 147456
PROGRAM: Written Bytes 0x3d800 (64)
Program Size: 0.24 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x1ec
PROGRAM: Partition 0, Sector: 148480, Length: 492 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_sbl1.mbn
FireHose Log: start 148480, num 492
FireHose Log: Write failed Sector 148480, Errno 2
FireHose Log: Finished sector address 148480
PROGRAM: Written Bytes 0x3d800 (64)
Program Size: 0.24 MB
PROGRAM: Replace the partition sectors number 0x100 to file size in sector 0x2d
PROGRAM: Partition 0, Sector: 149504, Length: 45 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_sdi.mbn
FireHose Log: start 149504, num 45
FireHose Log: Write failed Sector 149504, Errno 2
FireHose Log: Finished sector address 149504
PROGRAM: Written Bytes 0x5a00 (64)
Program Size: 0.02 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x3aa
PROGRAM: Partition 0, Sector: 180224, Length: 938 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_emmc_appsboot.mbn
FireHose Log: start 180224, num 938
FireHose Log: Write failed Sector 180224, Errno 2
FireHose Log: Finished sector address 180224
PROGRAM: Written Bytes 0x75400 (64)
Program Size: 0.46 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x3aa
PROGRAM: Partition 0, Sector: 181248, Length: 938 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_emmc_appsboot.mbn
FireHose Log: start 181248, num 938
FireHose Log: Write failed Sector 181248, Errno 2
FireHose Log: Finished sector address 181248
PROGRAM: Written Bytes 0x75400 (64)
Program Size: 0.46 MB
PROGRAM: Replace the partition sectors number 0x3e8 to file size in sector 0x128
PROGRAM: Partition 0, Sector: 182272, Length: 296 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_rpm.mbn
FireHose Log: start 182272, num 296
FireHose Log: Write failed Sector 182272, Errno 2
FireHose Log: Finished sector address 182272
PROGRAM: Written Bytes 0x25000 (64)
Program Size: 0.14 MB
PROGRAM: Replace the partition sectors number 0x3e8 to file size in sector 0x128
PROGRAM: Partition 0, Sector: 183272, Length: 296 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_rpm.mbn
FireHose Log: start 183272, num 296
FireHose Log: Write failed Sector 183272, Errno 2
FireHose Log: Finished sector address 183272
PROGRAM: Written Bytes 0x25000 (64)
Program Size: 0.14 MB
PROGRAM: Replace the partition sectors number 0x5000 to file size in sector 0x38d5
PROGRAM: Partition 0, Sector: 196608, Length: 14549 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_boot.img
FireHose Log: start 196608, num 14549
FireHose Log: Write failed Sector 196608, Errno 2
FireHose Log: Finished sector address 196608
PROGRAM: Written Bytes 0x71aa00 (64)
Program Size: 7.10 MB
PROGRAM: Replace the partition sectors number 0x3e8 to file size in sector 0x297
PROGRAM: Partition 0, Sector: 229376, Length: 663 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_tz.mbn
FireHose Log: start 229376, num 663
FireHose Log: Write failed Sector 229376, Errno 2
FireHose Log: Finished sector address 229376
PROGRAM: Written Bytes 0x52e00 (64)
Program Size: 0.32 MB
PROGRAM: Replace the partition sectors number 0x3e8 to file size in sector 0x297
PROGRAM: Partition 0, Sector: 230376, Length: 663 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_tz.mbn
FireHose Log: start 230376, num 663
FireHose Log: Write failed Sector 230376, Errno 2
FireHose Log: Finished sector address 230376
PROGRAM: Written Bytes 0x52e00 (64)
Program Size: 0.32 MB
PROGRAM: Partition 0, Sector: 344064, Length: 262160 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_1.img
FireHose Log: start 344064, num 262160
FireHose Log: Write failed Sector 344064, Errno 2
FireHose Log: Finished sector address 344064
PROGRAM: Written Bytes 0x8002000 (64)
Program Size: 128.01 MB
PROGRAM: Partition 0, Sector: 606600, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_2.img
FireHose Log: start 606600, num 16
FireHose Log: Write failed Sector 606600, Errno 29
FireHose Log: Finished sector address 606600
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 610352, Length: 257992 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_3.img
FireHose Log: start 610352, num 257992
FireHose Log: Write failed Sector 610352, Errno 2
FireHose Log: Finished sector address 610352
PROGRAM: Written Bytes 0x7df9000 (64)
Program Size: 125.97 MB
PROGRAM: Partition 0, Sector: 868352, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_4.img
FireHose Log: start 868352, num 16
FireHose Log: Write failed Sector 868352, Errno 2
FireHose Log: Finished sector address 868352
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 872104, Length: 258384 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_5.img
FireHose Log: start 872104, num 258384
FireHose Log: Write failed Sector 872104, Errno 2
FireHose Log: Finished sector address 872104
PROGRAM: Written Bytes 0x7e2a000 (64)
Program Size: 126.16 MB
PROGRAM: Partition 0, Sector: 1130496, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_6.img
FireHose Log: start 1130496, num 16
FireHose Log: Write failed Sector 1130496, Errno 2
FireHose Log: Finished sector address 1130496
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1130888, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_7.img
FireHose Log: start 1130888, num 16
FireHose Log: Write failed Sector 1130888, Errno 2
FireHose Log: Finished sector address 1130888
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1134640, Length: 95712 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_8.img
FireHose Log: start 1134640, num 95712
FireHose Log: Write failed Sector 1134640, Errno 2
FireHose Log: Finished sector address 1134640
PROGRAM: Written Bytes 0x2ebc000 (64)
Program Size: 46.73 MB
PROGRAM: Partition 0, Sector: 1392640, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_9.img
FireHose Log: start 1392640, num 16
FireHose Log: Write failed Sector 1392640, Errno 2
FireHose Log: Finished sector address 1392640
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1654784, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_10.img
FireHose Log: start 1654784, num 16
FireHose Log: Write failed Sector 1654784, Errno 29
FireHose Log: Finished sector address 1654784
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1655176, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_11.img
FireHose Log: start 1655176, num 16
FireHose Log: Write failed Sector 1655176, Errno 29
FireHose Log: Finished sector address 1655176
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1777664, Length: 11376 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_cache_1.img
FireHose Log: start 1777664, num 11376
FireHose Log: Write failed Sector 1777664, Errno 2
FireHose Log: Finished sector address 1777664
PROGRAM: Written Bytes 0x58e000 (64)
Program Size: 5.55 MB
PROGRAM: Replace the partition sectors number 0x5000 to file size in sector 0x3ca9
PROGRAM: Partition 0, Sector: 1974272, Length: 15529 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_recovery.img
FireHose Log: start 1974272, num 15529
FireHose Log: Write failed Sector 1974272, Errno 2
FireHose Log: Finished sector address 1974272
PROGRAM: Written Bytes 0x795200 (64)
Program Size: 7.58 MB
PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x1
PROGRAM: Partition 0, Sector: 1998848, Length: 1 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_misc_erase.img
FireHose Log: start 1998848, num 1
ReadFile last error: 0
PROGRAM: Written Bytes 0x200 (64)
Program Size: 0.00 MB
PROGRAM: Partition 0, Sector: 2015232, Length: 262136 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_059V786_001.custom_1.img
WriteFile last error: 0
PROGRAM: Send XML command fail code: 9
Failed to write C:\RM-1013\rm1013_2.1.0.12_059V786_001.custom_1.img to the device
Download Fail:FireHose Fail Failed to Upload the emmc images to the phone using Firehose.
Finish Download[/B][/FONT]
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot edl
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Creating filesystem with parameters:
Size: 122758868992
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29970427
Block groups: 915
Reserved block group size: 1024
Created filesystem with 11/7495680 inodes and 518576/29970427 blocks
target reported max download size of 536870912 bytes
wiping cache...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
erasing 'userdata'...
OKAY [ 0.005s]
sending 'userdata' (145110 KB)...
OKAY [ 4.174s]
writing 'userdata'...
OKAY [ 1.607s]
erasing 'cache'...
OKAY [ 0.017s]
sending 'cache' (6248 KB)...
OKAY [ 0.209s]
writing 'cache'...
OKAY [ 0.073s]
finished. total time: 6.091s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update "C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn_dcb9895fd6.tar"
error: failed to open zip file 'C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn_dcb9895fd6.tar': Invalid file
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update "C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn_dcb9895fd6.img
error: failed to open zip file 'C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn_dcb9895fd6.img': Invalid file
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update "C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn"
W/ ( 5580): Unable to open 'C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn': Permission denied
error: failed to open zip file 'C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn': I/O Error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update "C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn\images\boot.img"
error: failed to open zip file 'C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn\images\boot.img': Invalid file
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update "C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn.zip"
W/ ( 1184): Unable to open 'C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn.zip': Permission denied
error: failed to open zip file 'C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn.zip': I/O Error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update "C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn"
W/ ( 9664): Unable to open 'C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn': Permission denied
error: failed to open zip file 'C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn': I/O Error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update "C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn"
W/ ( 8648): Unable to open 'C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn': Permission denied
error: failed to open zip file 'C:\Users\Administrator\Desktop\globalrom\lithium_images_6.11.10_20161110.0000.00_6.0_cn': I/O Error
C:\Program Files (x86)\Minimal ADB and Fastboot>
I fastboot -w then proceeded to run a fastboot update and as shown receive a failed to open zip file.
I only tried "fastboot update" after having no success with the mi flash tool ( after selecting directory of .tgz file and hitting refresh the program fails to respond). I only then downloaded the MiPCSuite after the phone got bricked and now it won't connect to computer. Any ideas? Please help.
As you can see from the commands ran, I used winzip to unzip and tried flashing .img with no success.
Hi guys ended up downloading the beta mi flash tool, still didn't work. re-extracted the .tgz and saw that the first extraction did not unzip all files.
Did it again and it was able to flash.
that's fortunate.