Database Users

XIP extracting ... going from RUU/WWE to XIP.BIN

Starting with ababrekar's brilliant expose' on how to manually port an XIP from one device to another, there has been a great deal of attention paid to the process of getting the XIP.BIN isolated from the rest of the ROM.
I thought that I could try to contribute with the information others have shared with me. Ultimately, it may prove to be beneficial if there were a development thread dedicated to extracting the XIP.BIN.
credit to dcd, vetvito, ababrekar, gguruusa, lennysh. noonski and of course, all those who develop and update the various tools!
First off, you're best off if you start with a RUU/WWE from HTC/Sprint/Bell. etc.
1) The very first step in this process is to extract the NBH file that includes the OS. Do this by using WinRAR or WinZip to open the executable and look for the largest file with the extension NBH. In the case of our example, that file is VOGUIMG.nbh.
2) The next step is to break VOGUIMG.nbh into it's various pieces by executing the following:
Code:
nbhextract.exe VOGUIMG.nbh
The result is the following screen output:
Code:
=== NBHextract v1.0
=== Extract contents from HTC NBH files
=== (c)2007 xda-developers.com
=== by: pof & TheBlasphemer based on itsme perl scripts
Device: VOGU10000
CID: VZW__001
Version: 3.14.605.1
Language: USA
Extracting: 00_SPL.nb
Extracting: 01_MainSplash.nb
Encoding: 01_MainSplash.bmp
Extracting: 02_SubSplash.nb
Encoding: 02_SubSplash.bmp
Extracting: 03_Unknown.nb
Extracting: 04_OS.nb
We are after the XIP, which is contained within the file 04_OS.nb
3) The next step is to break 04_OS.nb into it's various pieces by executing the following:
Code:
nbsplit.exe –titan 04_OS.nb
The result is the following files:
Code:
04_OS.nb.extra
04_OS.nb.payload
We're still not there yet, as the XIP is contained inside 04_OS.nb.payload.
The address where the XIP.BIN ends can be found with imgfsfromnb:
Code:
rename 04_OS.nb.payload to OS.nb.payload
imgfsfromnb OS.nb.payload imgfs.bin
output:
Sector size is 0x800 bytes
ImgFs partition starts at 0x00680000 and ends at 0x05680000
Dumping IMGFS at offset 0x006c0000 (size 0x04fc0000)
Click to expand...
Click to collapse
In the next step, we use RomMaster and we feed it the start address and end address of the XIP.
Remember, these start and end addresses will vary from device to device and in the case of the same device but a custom rom, the address can vary from one custom rom to the other.
Ababrekar has suggested "the best way to find out the start address for each partition would be from the LBA in MBR region"
In the case of the Vogue, when dealing with non-custom ROMs, the XIP usually begins at 0x00320000.
So, the start address is 0x00320000 and you use imgfsfromnb.exe to get the end address 0x006c0000 and feed these two parameters as part of the input to RomMaster:
Code:
RomMaster.exe -x -w 5 -s 0x00320000 -e 0x006c0000 OS.nb.payload -o xip.bin
What this does is output a file (XIP.BIN) comprised of all the data between the two (-s START -e END) addresses (-s 0x00320000 -e 0x006c0000) fed into RomMaster.
XIP.BIN
None of this have I discovered myself. It is a compilation of instructions that I received from members credited above. What we could do with this thread is use it as a discussion point for others who have or are having problems getting the XIP out of the os.nb.payload.
Best regards,
-boggsie

bookmarked!
thank you very much for this information!

Awesome to see people like you getting such amazing info ot inthe open This is bound to help many Thanks and bookmarked to keep an eye on it

Do you know a way to get the XIP from a *.bin emulator image?

frauhottelmann said:
Do you know a way to get the XIP from a *.bin emulator image?
Click to expand...
Click to collapse
Anyone found answer for this?

xperea S firmware, for fun and research

http://www.mediafire.com/?j0anq7kfe...ajlhunt3jras6,c92jlnxd3vdngn8,i6hqic38gc4h68d
system is ext4 image, can be mounted with mount -o loop in linux or by utilizing latest version of ext3 driver ( 0.51 ) for windows.

Can me give someone the WLAN widget with the GPS think in?
Gesendet von meinem R800i

is it the system dump from xperia s...?????

is it dump? real one?
Sent from my X10i using XDA App

works on xperia arc s ?

download, extract, sin2img, mount, get files
Sent from my X10i using XDA App

how you get this ...??????

can someone help me with this Im stuck on mounting the annoying img file

tatit1011 said:
can someone help me with this Im stuck on mounting the annoying img file
Click to expand...
Click to collapse
you can unpack it without mounting, by using unyaffs : http://code.google.com/p/unyaffs/

It says broken image file, can someone upload the xperia S system folder? Thanks

can you provide the binaries you are using to unpack this ?
1- extrating with 7zip : Ok, there are 3 .sin files
2- sin2img I already had : Crash
3- I tried an other version : Ok ... but the .img file size is exactly the same as the .sin ...
4- unyaffs : Crash !
So I think I don't have the good binaries ...
Thanks

sambastrakan said:
can you provide the binaries you are using to unpack this ?
1- extrating with 7zip : Ok, there are 3 .sin files
2- sin2img I already had : Crash
3- I tried an other version : Ok ... but the .img file size is exactly the same as the .sin ...
4- unyaffs : Crash !
So I think I don't have the good binaries ...
Thanks
Click to expand...
Click to collapse
THIS IS NOT YAFFS THIS IS EXT4
JUST MOUNT THE IMG IN LINUX AS EXT 4
(i hav not.done myself, I'm jus saying)
Sent from my X10i using XDA App

I also tried to mount the .img in DiskInternals Linux Reader without success. Until today it was working for any image available in xda-dev... so I think there is something special with these images ...
I will try directly in Linux to see ...
thx.

I can confirm it's not working.
Latest sin2img version gives a FileStream.Seek ArgumentException "Attempted seeking before the beginning of the stream.".
An older version creates an img file the same size as the sin, but unyaffs crashes with a segmentation fault / core dump and:
[email protected]:~$ dmesg | tail
[44637.019046] unyaffs[18031]: segfault at 1adb2b2c0 ip 0000000000400a08 sp 00007fffba023ca0 error 4 in unyaffs[400000+1000]
Click to expand...
Click to collapse
No mounting either, 'cause:
[email protected]:~$ sudo mount -t ext4 -o loop system.img /mnt/mountpoint/
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[email protected]:~$ dmesg | tail
[44678.194165] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
Click to expand...
Click to collapse
So, wasted time, I guess...

zdzihu has some tool to extract the package try that one. I think it's called auip.exe

ShyamSasi said:
zdzihu has some tool to extract the package try that one. I think it's called auip.exe
Click to expand...
Click to collapse
Thanks, but no luck with that one either. It keeps telling me the page size is wrong (tried with all three options)
Code:
[email protected]:~$ ./aIUP
aZuZu - Direct SIN / YAFFS Image Unpacker, v1.03.5. (c) aZuZu. 2011.
usage adiup [System.Img OR System.Sin] [Page Size] [Directory]
page size is one of 2048, 4096, 8192. - Sorry to lazy to encode auto detect. ;)
Tip: Directory - directory will be created if doesn't exist.
Supported: SE System.SIN files & Android System.IMG files.
[email protected]:~$ ./aIUP system.sin 4096 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
[email protected]:~$ ./aIUP system.sin 2048 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
[email protected]:~$ ./aIUP system.sin 8192 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
Same for the .img file.

crimilde said:
Thanks, but no luck with that one either. It keeps telling me the page size is wrong (tried with all three options)
Code:
[email protected]:~$ ./aIUP
aZuZu - Direct SIN / YAFFS Image Unpacker, v1.03.5. (c) aZuZu. 2011.
usage adiup [System.Img OR System.Sin] [Page Size] [Directory]
page size is one of 2048, 4096, 8192. - Sorry to lazy to encode auto detect. ;)
Tip: Directory - directory will be created if doesn't exist.
Supported: SE System.SIN files & Android System.IMG files.
[email protected]:~$ ./aIUP system.sin 4096 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
[email protected]:~$ ./aIUP system.sin 2048 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
[email protected]:~$ ./aIUP system.sin 8192 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
Same for the .img file.
Click to expand...
Click to collapse
What is your page files size? Those 3 are just examples. You need to find the page file of your PC.

ShyamSasi said:
What is your page files size? Those 3 are just examples. You need to find the page file of your PC.
Click to expand...
Click to collapse
Ah ok, sorry.
It's :
[email protected]:~$ getconf PAGESIZE
4096
Click to expand...
Click to collapse
Which I had already tried.

crimilde said:
Ah ok, sorry.
It's :
Which I had already tried.
Click to expand...
Click to collapse
I'll download it and try it today.

ShyamSasi said:
I'll download it and try it today.
Click to expand...
Click to collapse
yap please sone one fine a way to unpack it .......... ????
i am waiting too for it

[GUIDE] enable native VOIP in ICS ROMS

Hello,
Wanted to enable VOIP on ICS, but couldn't find the info. After bricking my phone twice and fixing it again
I succeeded.
problems i encountered so far:
Fragmented info in the numerous treads that are around over voip
Incomplete manuals
People giving advice without trying it on their own phone first
Bugs
So this is what i did:
On the PC
Install latest Java Runtime Environment (current version 6 Update 31)
Install latest Java SE Development Kit (current version 7u3)
Install latest Android SDK then run SDK manager and install the suggested packages
Download latest APKtool (http://code.google.com/p/android-apktool/ version 1.4.3)
Install samsung USB drivers (available on sammobile.com)
Add the \bin, \tools and \platform-tools directory to the PATH variable
in windows 7, right click computer in start menu->properties->click advanced system properties->hit the button system variables and add them to the path variable.
In my case:
c:\Program Files\Java\jdk1.7.0_03\bin;c:\Program Files\Java\jre7\bin;c:\Program Files\Android\android-sdk\platform-tools;c:\Program Files\Android\android-sdk\tools
Reboot PC (just to be sure, its windows)
On the Phone
Rooted phone
Install rootexplorer (market)
Install clockworkmod recovery (download rommanager in market)
Install busybox (Market, Stephen Erickson)
CWM and Busybox needed in case you mess up
With Rootexplorer
goto /system/framework/ and make the directory R/W
copy /system/framework/framework-res.apk to /system/framework/framework-res.apk.bak
Copy /system/framework/framework-res.apk to PC
Back to PC
Make directory
c:\APKTool
unpack downloaded APKTool to this folder
copy framework-res.apk to this folder
this folder should now contain:
framework-res.apk
apktool.jar
The following info is from http://www.miui-au.com/add-ons/apktool/
open a command prompt in the APKTool directory and run the following command:
Code:
java -jar apktool.jar if framework-res.apk
Code:
java -jar apktool.jar d framework-res.apk
this should decompile framework-res.apk to a folder named framework-res
goto the following folder
c:\apktool\framework-res\res\values
edit (notepad) the following lines in the file bools.xml to
Code:
<bool name="config_sip_wifi_only">false</bool>
<bool name="config_built_in_sip_phone">true</bool>
Now we are going to compile framework-res.apk again
Code:
java -jar apktool.jar b framework-res
Due to a bug in either APKTool.jar or aapt.exe you will probable run into a number of errors that need to be fixed
Code:
apktool\framework-res\res\values\plurals.xml:79: error
: Multiple substitutions specified in non-positional format; did you mean to add
the formatted="false" attribute?
A fix is explained at the following site:
http://www.miui.nl/?page_id=2216
in every plurals.xml file that generates an error find the following section and change it to:
Code:
<plurals name="matches_found">
<item quantity="other">%d of %d</item>
<item quantity="one">1 match</item>
</plurals>
to
Code:
<plurals name="matches_found">
<item quantity="other">%1$d of %2$d</item>
<item quantity="one">1 match</item>
</plurals>
After fixing this (could be up to 80 files, depending on ROM)
we can successfully compile framework-res.apk
Code:
java -jar apktool.jar b framework-res
We should have one warning
Code:
W: Could not find sources
This is normal for framework-res.apk
After compilation we should have the following two new folders
Code:
c:\temp\apktool\framework-res\build\
c:\temp\apktool\framework-res\dist\
in the directory dist there is a newly created framework-res.apk
DO NOT USE THIS FILE, IT WILL BRICK YOUR PHONE
instead go to the directory
Code:
framework-res\build\apk\
there should be a file resources.arsc. This file contains all our modifications and is all we need.
Framework-res.apk is a compressed file. We can open it with a zip program. I used Total Commander for this (www.ghisler.com)
now open the original Framework-res.apk and copy (pack) our modified resources.arsc (overwrite the original)
Now we have a modified framework-res.apk with voip enabled
Next we have to make the following two files:
android.software.sip.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2009 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.
-->
<!-- This is the standard set of features for devices that support SIP API. -->
<permissions>
<feature name="android.software.sip" />
</permissions>
android.software.sip.voip.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2009 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.
-->
<!-- This is the standard set of features for devices that support SIP-based VoIP. -->
<permissions>
<feature name="android.software.sip" />
<feature name="android.software.sip.voip" />
</permissions>
Copy the three files back to the Phone
Back to Phone again
UNSUCCESSFUL COMPILING, WRONG COPYING OR PURE BAD LUCK CAN BRICK YOUR PHONE. BACKUP YOUR PHONE BEFORE PROCEEDING!
CONTINUE AT YOUR OWN RISK
FORGET ADB PUSH, BE SURE TO HAVE ROOTEXPORER
Everyone saying otherwise is:
a)lying
b)not running stock rom
c)lucky
d)laisy for not writing a decent HOWTO ADB PUSH
So go ahead with root explorer
Copy android.software.sip.xml and android.software.sip.voip.xml to /system/etc/permissions
Set the persissions to rw-r--r--
Change owner to user 0-Root, group 0-root
copy framework-res.apk to /system
Set the persissions to rw-r--r--
Change owner to user 0-Root, group 0-root
Move /system/framework-res.apk to /system/framework (be sure to make backup the original file)
After reboot VOIP is enabled
What if something goes wrong:
If all else fails flash your original rom
or (works only if you followed everything in this manual)
Reboot your Phone in recovery mode (press&hold home, volume-up, power button)
In recovery mode mount /system and /SDCARD
Connect your Phone (still in recovery mode) to the PC
on the PC open a command prompt
Type the following (sgs2)
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p9 /system
cp /system/framework/framework-res.apk.bak /system/framework/framework-res.apk.bak
reboot
this should copy the backup file back.
good luck

Hi. VOIP doesn't work in my country due to restrictions but you can try this.
1. Download anycut from the market.
2. Long hold desktop > add shortcut.
{
"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"
}
3. Click on Activity.
4. Click on SIP Settings.
5. An icon will appear on the desktop.
6. Click on icon and set it up as you wish.
I think this is a much simpler approach and just works without root or any modification.
Sent from my GT-I9100

If you wish then you can uninstall anycut after you finish. In its defense it is a 32kb program made by a Googler.
Sent from my GT-I9100

akbarhash said:
I think this is a much simpler approach and just works without root or any modification.
Click to expand...
Click to collapse
Nice try, but this will only work if voip is enabled first. basically this program only adds a shortcut to voip settings, but if the voip interface is disabled, this doesn't work.

nice effort but didn't work for me..

This is ok, but...
akbarhash said:
Hi. VOIP doesn't work in my country due to restrictions but you can try this.
1. Download anycut from the market.
2. Long hold desktop > add shortcut.
3. Click on Activity.
4. Click on SIP Settings.
5. An icon will appear on the desktop.
6. Click on icon and set it up as you wish.
I think this is a much simpler approach and just works without root or any modification.
Sent from my GT-I9100
Click to expand...
Click to collapse
This is ok for me, but don´t save the account, and checkit status forever. Any solution?
Thank.

im using bria
hi
its too long procedure. i m using bria on SGS rooted phone. and its work great.

adejager1 said:
UNSUCCESSFUL COMPILING, WRONG COPYING OR PURE BAD LUCK CAN BRICK YOUR PHONE.
Click to expand...
Click to collapse
Damn, which I have a lot

Dears,
I'm following this guide but I have a problem recompiling.
This is the log:
c:\APKtool>java -jar apktool.jar b framework-res
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
invalid resource directory name: c:\APKtool\framework-res\res/drawable-sw600dp-h
dpi
invalid resource directory name: c:\APKtool\framework-res\res/layout-sw400dp
invalid resource directory name: c:\APKtool\framework-res\res/layout-sw600dp
invalid resource directory name: c:\APKtool\framework-res\res/layout-w600dp
invalid resource directory name: c:\APKtool\framework-res\res/values-h720dp
invalid resource directory name: c:\APKtool\framework-res\res/values-sw360dp
invalid resource directory name: c:\APKtool\framework-res\res/values-sw400dp
invalid resource directory name: c:\APKtool\framework-res\res/values-sw600dp
invalid resource directory name: c:\APKtool\framework-res\res/values-sw600dp-lan
d
invalid resource directory name: c:\APKtool\framework-res\res/values-sw600dp-w10
24dp
invalid resource directory name: c:\APKtool\framework-res\res/values-sw600dp-w12
80dp
invalid resource directory name: c:\APKtool\framework-res\res/values-w360dp
invalid resource directory name: c:\APKtool\framework-res\res/values-w480dp
invalid resource directory name: c:\APKtool\framework-res\res/values-w500dp
invalid resource directory name: c:\APKtool\framework-res\res/values-w600dp
invalid resource directory name: c:\APKtool\framework-res\res/values-w720dp
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutExce
ption: could not exec command: [aapt, p, -F, C:\Users\FEDERI~1.RAM\AppData\Local
\Temp\APKTOOL1708831992001626862.tmp, -x, -S, c:\APKtool\framework-res\res, -M,
c:\APKtool\framework-res\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:193)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:301)
at brut.androlib.Androlib.buildResources(Androlib.java:248)
at brut.androlib.Androlib.build(Androlib.java:171)
at brut.androlib.Androlib.build(Androlib.java:154)
at brut.apktool.Main.cmdBuild(Main.java:182)
at brut.apktool.Main.main(Main.java:67)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\U
sers\FEDERI~1.RAM\AppData\Local\Temp\APKTOOL1708831992001626862.tmp, -x, -S, c:\
APKtool\framework-res\res, -M, c:\APKtool\framework-res\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:191)
... 6 more
c:\APKtool>​
I'm on Windows, so I think the problem is the / in the paths, but I don't know the cause of this.
I'm not a programmer.
Original framework-res.apk, APKtool and the framework-res folder with the already modified file are attached.
Can anybody gently help me?
Thank you so much.

I can get to the sip settings and add an account, but as this poster says, the account says "Checking status" forever. Also every now and then, the account simply disappears. There's no save button either.
Anyone with the same problems? Any ideas?

[GUIDE] how to extract system.img or data.img

Forever king's Guide
How to extract system.img or Data.img​
Want to Extract your precious files from your Nandroid backup?
You can do this easily by following this guide.
How to unyaffs (extracting system.img/data.img)
1 Download and extract Unyaffs In any folder
2 Now place you system.img/data.img in the folder in which you extracted unyaffs files.
3 Now open your Command prompt and CD to that folder (if windows7 just press shift+right click on that folder having things )
4 For extracting system.img
Type unyaffs.exe system.img
For extracing data.img
Type unyaffs.exe data.img​
5 Done.
When Done you will see 'end of the line'.
So it was easy! Press Thanks if it worked for you. Are you having any problems while following it? Please Reply to the thread, I'm here to help you.

Thanks...it helped me a lot
---------- Post added at 05:54 AM ---------- Previous post was at 05:46 AM ----------
Hi i get an error while dumping stack...any help?

This is what i am getting..
Code:
D:\\unyaffs>unyaffs.exe system.img
36 [main] unyaffs 668 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_
VIOLATION
35983 [main] unyaffs 668 open_stackdumpfile: Dumping stack trace to unyaffs.ex
e.stackdump
1362463 [main] unyaffs 668 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_
VIOLATION
1394073 [main] unyaffs 668 _cygtls::handle_exceptions: Error while dumping state
(probably corrupted stack)
D:\unyaffs>
Can you post some screenies of successful case.?

viijay4b7 said:
This is what i am getting..
Code:
D:\\unyaffs>unyaffs.exe system.img
36 [main] unyaffs 668 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_
VIOLATION
35983 [main] unyaffs 668 open_stackdumpfile: Dumping stack trace to unyaffs.ex
e.stackdump
1362463 [main] unyaffs 668 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_
VIOLATION
1394073 [main] unyaffs 668 _cygtls::handle_exceptions: Error while dumping state
(probably corrupted stack)
D:\unyaffs>
Can you post some screenies of successful case.?
Click to expand...
Click to collapse
dude! this comes only when your system.img/data.img's size is 150+ mb this is old version! i have done full decompiling! with no error!

forever king said:
dude! this comes only when your system.img/data.img's size is 150+ mb this is old version! i have done full decompiling! with no error!
Click to expand...
Click to collapse
Thanks for the info.
So, what is the solution for me? mine is about 400MB i guess. Also I hope it is ext4. Do you have a link to ext4 tools?

Exactly I need to extract my system.img so i can pull the fresh /system/build.prop from it. The file size is 500MB how do I extract it's contents?
thanks

Ext2Read its the solution for ext4 .img files on windows

Yep, it did the trick for me, thanks for the tips.

You can use Yaffe tool for extracting files sizing more than 150 MB.

http://forum.xda-developers.com/showthread.php?t=2294909
Check this topic

"The program can't start because cygwin1.dll is missing from your computer. Try reinstalling the program to fix this problem."

how to extract data.img ？
$ file data.img
data.img: data
Click to expand...
Click to collapse

I'll try

How do i extract the system.img straight from the phone? There is no available firmware for mine

[HowTo] Flash a stock ROM

Flash guide ZUK Z2 Pro - （Z2121）(QPST/QFIL):
-------------
Preamble:
This upgrade your Phone to Z2 Pro_CN_OPEN_USER_Q01002.1_M_ZUI_1.9.038_ST_160503 version, for example. Use the latest version of the software or the version for the actual operation.
Backup your data before processing the flash, in order to avoid loss of data!
-------------
--You'll need a USB-C data cable to proceed--
{
"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"
}
Theoretical it is possible to recover a bricked via this method. I you do this for the first time you need to download some tools. Without downloading and installing the tools this procedure will take about 4 minutes.
1.1 Download flashtool Download flashtool and ZUK USB driver
Code:
Download Flashtool
###REQUIRED### (QPST 2.7.434)
https://www.androidfilehost.com/?fid=24591000424948456
Download USB Drivers
###REQUIRED### (ZUK)
https://www.androidfilehost.com/?fid=24659325368664618
optional (Qualcomm normally installed by QPST flashtool setup)
https://www.androidfilehost.com/?fid=24591020540824824
Download and extract ADB and fastboot
Code:
###REQUIRED###
https://www.androidfilehost.com/?fid=24671318762848778
**Attention**
If you have Windows 8, 8.1, 10 installed, you have to disable driver verification.
See post #13 http://zukfans.eu/community/threads...://club.lenovo.com.cn/thread-1811698-1-1.html
ROM Source: http://club.lenovo.com.cn/thread-1812430-1-1.html​

Flash guide ZUK Z2 Pro internal SD-Card:
---This method only works, if your phone is able to boot---
Note:
Code:
Usually no data will be wiped. But to be save do a backup first.
##############A T T E N T I O N##############
DO NOT TRY TO FLASH VIA THIS METHOD, IF YOUR PHONE HAS A CUSTOM FIRMWARE *¹ !
If you try this nevertheless you phone will be bricked!​
#########################################
Information
If your phone has a official ROM/Firmware installed but it is rooted etc. it will work without bricks.
Let's get started
1.0 Download Firmware/ROM (.QSB)
Code:
###REQUIRED###
https://www.androidfilehost.com/?w=files&flid=94094
1.0.1 Extract the .7z file with ROM/Firmware you downloaded at 1.0
1.0.2 Connect the phone via USB-C cable to your computer and create a folder called "sdfuse" at the root of your internal storage.
1.0.3 Copy all the exctracted .qsp files into the sdfuse folder.
1.0.4 Shutdown the phone.
1.0.5 Hold down the volume- button and power on the phone. At second vibration release the power button, but still hold the volume- button. Now the developer recovery menue should be shown.
1.0.6 Select "Sd update" and confirm with power button.
1.0.7 Hit "apply" or "OK" with tapping on it. Now the flashing procedure will start immediatly. After this was successful hit the reboot button and you're done.
*¹ You flashed a Custom ROM via TWRP means Custom Firmware / Custom ROM. Furthermore if your merchant flashed a ROM with multilanguage support (more than English and Chinese) and it's unable to gain OTA update (non rooted - if you don't know what this is you are not rooted!) your device running on a Custom Firmware!

###################
FAQ:
Q: Is it possible to install via SD-Card update even if my bootloader is unlocked and my phone is rooted?
A: Yes, see video to convince yourself:
https://www.youtube.com/watch?v=-TwhMjePiTE
Q: It is'nd possible to get OTA updates alway got promting "No internet connection" how to fix this?
A: If you 1st try to delete data and cache from "Sys Upd" and reboot your phone, try again. If this will not solve this problem try to connect via Chinese VPN-Server. Head over to this thread: http://zukfans.eu/community/threads/ota-update-solution-for-noobs-like-me.192/
Thank you Donát Szabó for your support!
Q: How to install Google Play Store?
A: Download and install the APKs in this package: https://www.androidfilehost.com/?fid=24671318762848780
Q: I'm having trouble to get Google Play Store working, Error: "Can't download app.. XYZ can't be downloaded. Try again, and if the proble continues, get help toubleshooting. (Error retrieving information from server. [DF-DLA-15])
A: 1st update Google Play Store via "apkmirror.com". If the problem still occurs:
1. delete your Google Account from your mobile phone(Sync Data first!)
2. delete data and cache from Google Play Services and Google Play store (APP)
3. reboot your phone
4. singn in to your Google Account and try again to intall APPs from Google Play Store APP.
Q: How to get Google Contacts sync woking?
A: Download and install the APKs in this package: https://www.androidfilehost.com/?fid=24671318762848780
Q: I got this message: "Fail to load contents.xml: Invaild Path for Meta Build CONTENT XML, ignored: C:\...\...\contents.xml" how do I fix this?
A: Maybe the folder names are to long (NTFS ~200 caracters), rename the folder with the contents.xml located in to "abc" for example.
Q: I need a password to extract the archive.
A: Try "club.lenovo.com.cn" without the potation marks.
Q: I can press the Download-Button ... but the download failed with error:
"Download Fail:Sahara Fail: QSahara Server Fail: The name of directory is invalid
Finish download"
A: Try to close and reopen QFIL again, also unplug and replug your phone.
Still not fixed? Reboot your PC, Phone.
Q: While flashing process I got error: "Download Fail: Sahara Fail:QSaharaServer Fail: Process Fail". How to fix this?
A: You need to copy the ROM files into a short named folder and filename on the root of a harddrive.
Q: I still have issues with QFIL/QPST: "Download Fail: Sahara Fail:QSaharaServer Fail: Process Fail". Any solution?
A: Try this short tutorial: http://zukfans.eu/community/threads...rom-zuk-z2-pro-z2121-only.57/page-8#post-7282
(Thanks syedtahir16)
Q: How to relock the bootloader, if I unlocked it?
A: You only need to open a command promt and fastboot.exe. Type "fastboot oem lock" into that command promt while the phone has to be in fastboot mode.
Q: Were to get into fastboot mode?
A: Open a command promt and type in "adb reboot-bootloader". In return your phone has to be connected via USB and "USB debugging" must be enabled.
Q: How do I change the language from Chines to English?
A: Click this video, this will show you how to:
Q: How can I start into TWRP?
A: Try to download this TWRP: https://www.androidfilehost.com/?fid=24591000424960393
Reboot into Fastboot Mode and run this command: fastboot -i 0x2b4c boot recovery.img
Q: Is there a secret menu, where I can test there components?
A:Yes, try *#*#1111#*#*
Q: I'm unable to access the developer recovery where I'm flashing the Sdupdate. Is there a detailed manual?
A: Take a look here: http://zukfans.eu/community/index.php?posts/6160
(Thanks to schupfer)
###################​

Half-bricked
Hello,
I just recieved my new phone and wanted to update it right away but at this end I got it bricked , so fast...
At first, I followed your 2nd method via internal-sd.
Everything went ok until the reboot.
Unfortunately, it gets stuck at the ZUK logo.
Nothing moving forward.
So then I used the first method, QPST/QFIL one.
But here comes a new problem, at one point, I get the following error message:
Download Fail: Sahara Fail:QSaharaServer Fail: Process fail.
Could you please help me to make it works?
Here is the complete log:
Validating Application Configuration
Load APP Configuration
COM:7
SAHARA:True
SAHARA:
SEARCHPATH:C:\
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:UFS
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:True
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
METABUILD:C:\abc\abc\contents.xml
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\
Meta Build Content XML Path: C:\abc\abc\contents.xml
Search File: prog_ufs_firehose_8996_ddr.elf
search form search path:C:\abc\abc\.\
Search File: rawprogram_unsparse0.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram1.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram2.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram3.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram_unsparse4.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram5.xml
search form search path:C:\abc\abc\.\
Search File: patch0.xml
search form search path:C:\abc\abc\.\
Search File: patch1.xml
search form search path:C:\abc\abc\.\
Search File: patch2.xml
search form search path:C:\abc\abc\.\
Search File: patch3.xml
search form search path:C:\abc\abc\.\
Search File: patch4.xml
search form search path:C:\abc\abc\.\
Search File: patch5.xml
search form search path:C:\abc\abc\.\
RAWPROGRAM file path: C:\abc\abc\.\rawprogram_unsparse0.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram1.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram2.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram3.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram_unsparse4.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram5.xml
PATCH file path:C:\abc\abc\.\patch0.xml
PATCH file path:C:\abc\abc\.\patch1.xml
PATCH file path:C:\abc\abc\.\patch2.xml
PATCH file path:C:\abc\abc\.\patch3.xml
PATCH file path:C:\abc\abc\.\patch4.xml
PATCH file path:C:\abc\abc\.\patch5.xml
Process Index:0
Meta Build Content XML Path: C:\abc\contents.xml
Search File: prog_ufs_firehose_8996_ddr.elf
search form search path:C:\abc\.\
Search File: rawprogram_unsparse0.xml
search form search path:C:\abc\.\
Search File: rawprogram1.xml
search form search path:C:\abc\.\
Search File: rawprogram2.xml
search form search path:C:\abc\.\
Search File: rawprogram3.xml
search form search path:C:\abc\.\
Search File: rawprogram_unsparse4.xml
search form search path:C:\abc\.\
Search File: rawprogram5.xml
search form search path:C:\abc\.\
Search File: patch0.xml
search form search path:C:\abc\.\
Search File: patch1.xml
search form search path:C:\abc\.\
Search File: patch2.xml
search form search path:C:\abc\.\
Search File: patch3.xml
search form search path:C:\abc\.\
Search File: patch4.xml
search form search path:C:\abc\.\
Search File: patch5.xml
search form search path:C:\abc\.\
RAWPROGRAM file path: C:\abc\.\rawprogram_unsparse0.xml
RAWPROGRAM file path: C:\abc\.\rawprogram1.xml
RAWPROGRAM file path: C:\abc\.\rawprogram2.xml
RAWPROGRAM file path: C:\abc\.\rawprogram3.xml
RAWPROGRAM file path: C:\abc\.\rawprogram_unsparse4.xml
RAWPROGRAM file path: C:\abc\.\rawprogram5.xml
PATCH file path:C:\abc\.\patch0.xml
PATCH file path:C:\abc\.\patch1.xml
PATCH file path:C:\abc\.\patch2.xml
PATCH file path:C:\abc\.\patch3.xml
PATCH file path:C:\abc\.\patch4.xml
PATCH file path:C:\abc\.\patch5.xml
Start Download
Program Path:C:\abc\prog_ufs_firehose_8996_ddr.elf
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM7 -s 13:C:\abc\prog_ufs_firehose_8996_ddr.elf 'Current working dir: C:\Users\Jean-François\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\abc\prog_ufs_firehose_8996_ddr.elf
20:42:54: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
20:42:54: ERROR: function: sahara_main:854 Sahara protocol error
20:42:54: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Update of 18/98 => everything is now solved.
I changed from my laptop to my HTPC and everything went fine... My Zuk Z2 pro works again!!!! I am so happy.

password for rom z2 pro
hello, when extracting the Rom you ask me what a password, send me through my email [email protected]

Hello,
If you read the entire post, you will find it I promise .
FAQ is always your best friend.

I am also having the same issue. I am currently on mokee custom rom. I want to return to stock and can enter edl mode. Phone is detected as usb-qdloader 9008. Tried QPST tool on 2 different computers, both have the same sahara fail error. Any help guys?

You need to extract all ROM files into drive C using a short folder name
e.g. C:\zuk\
no subfolders

Mathisou said:
Hello,
I just recieved my new phone and wanted to update it right away but at this end I got it bricked , so fast...
At first, I followed your 2nd method via internal-sd.
Everything went ok until the reboot.
Unfortunately, it gets stuck at the ZUK logo.
Nothing moving forward.
So then I used the first method, QPST/QFIL one.
But here comes a new problem, at one point, I get the following error message:
Download Fail: Sahara Fail:QSaharaServer Fail: Process fail.
Could you please help me to make it works?
Here is the complete log:
Validating Application Configuration
Load APP Configuration
COM:7
SAHARA:True
SAHARA:
SEARCHPATH:C:\
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:UFS
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:True
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
METABUILD:C:\abc\abc\contents.xml
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\
Meta Build Content XML Path: C:\abc\abc\contents.xml
Search File: prog_ufs_firehose_8996_ddr.elf
search form search path:C:\abc\abc\.\
Search File: rawprogram_unsparse0.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram1.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram2.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram3.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram_unsparse4.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram5.xml
search form search path:C:\abc\abc\.\
Search File: patch0.xml
search form search path:C:\abc\abc\.\
Search File: patch1.xml
search form search path:C:\abc\abc\.\
Search File: patch2.xml
search form search path:C:\abc\abc\.\
Search File: patch3.xml
search form search path:C:\abc\abc\.\
Search File: patch4.xml
search form search path:C:\abc\abc\.\
Search File: patch5.xml
search form search path:C:\abc\abc\.\
RAWPROGRAM file path: C:\abc\abc\.\rawprogram_unsparse0.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram1.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram2.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram3.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram_unsparse4.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram5.xml
PATCH file path:C:\abc\abc\.\patch0.xml
PATCH file path:C:\abc\abc\.\patch1.xml
PATCH file path:C:\abc\abc\.\patch2.xml
PATCH file path:C:\abc\abc\.\patch3.xml
PATCH file path:C:\abc\abc\.\patch4.xml
PATCH file path:C:\abc\abc\.\patch5.xml
Process Index:0
Meta Build Content XML Path: C:\abc\contents.xml
Search File: prog_ufs_firehose_8996_ddr.elf
search form search path:C:\abc\.\
Search File: rawprogram_unsparse0.xml
search form search path:C:\abc\.\
Search File: rawprogram1.xml
search form search path:C:\abc\.\
Search File: rawprogram2.xml
search form search path:C:\abc\.\
Search File: rawprogram3.xml
search form search path:C:\abc\.\
Search File: rawprogram_unsparse4.xml
search form search path:C:\abc\.\
Search File: rawprogram5.xml
search form search path:C:\abc\.\
Search File: patch0.xml
search form search path:C:\abc\.\
Search File: patch1.xml
search form search path:C:\abc\.\
Search File: patch2.xml
search form search path:C:\abc\.\
Search File: patch3.xml
search form search path:C:\abc\.\
Search File: patch4.xml
search form search path:C:\abc\.\
Search File: patch5.xml
search form search path:C:\abc\.\
RAWPROGRAM file path: C:\abc\.\rawprogram_unsparse0.xml
RAWPROGRAM file path: C:\abc\.\rawprogram1.xml
RAWPROGRAM file path: C:\abc\.\rawprogram2.xml
RAWPROGRAM file path: C:\abc\.\rawprogram3.xml
RAWPROGRAM file path: C:\abc\.\rawprogram_unsparse4.xml
RAWPROGRAM file path: C:\abc\.\rawprogram5.xml
PATCH file path:C:\abc\.\patch0.xml
PATCH file path:C:\abc\.\patch1.xml
PATCH file path:C:\abc\.\patch2.xml
PATCH file path:C:\abc\.\patch3.xml
PATCH file path:C:\abc\.\patch4.xml
PATCH file path:C:\abc\.\patch5.xml
Start Download
Program Path:C:\abc\prog_ufs_firehose_8996_ddr.elf
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM7 -s 13:C:\abc\prog_ufs_firehose_8996_ddr.elf 'Current working dir: C:\Users\Jean-François\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\abc\prog_ufs_firehose_8996_ddr.elf
20:42:54: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
20:42:54: ERROR: function: sahara_main:854 Sahara protocol error
20:42:54: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Update of 18/98 => everything is now solved.
I changed from my laptop to my HTPC and everything went fine... My Zuk Z2 pro works again!!!! I am so happy.
Click to expand...
Click to collapse
Please help me. I have the same . Even short path c/zuk dont work

Wow thank you for posting this!

Mathisou said:
Hello,
I just recieved my new phone and wanted to update it right away but at this end I got it bricked , so fast...
At first, I followed your 2nd method via internal-sd.
Everything went ok until the reboot.
Unfortunately, it gets stuck at the ZUK logo.
Nothing moving forward.
So then I used the first method, QPST/QFIL one.
But here comes a new problem, at one point, I get the following error message:
Download Fail: Sahara Fail:QSaharaServer Fail: Process fail.
Could you please help me to make it works?
Here is the complete log:
Validating Application Configuration
Load APP Configuration
COM:7
SAHARA:True
SAHARA:
SEARCHPATH:C:\
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:UFS
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:True
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
METABUILD:C:\abc\abc\contents.xml
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\
Meta Build Content XML Path: C:\abc\abc\contents.xml
Search File: prog_ufs_firehose_8996_ddr.elf
search form search path:C:\abc\abc\.\
Search File: rawprogram_unsparse0.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram1.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram2.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram3.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram_unsparse4.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram5.xml
search form search path:C:\abc\abc\.\
Search File: patch0.xml
search form search path:C:\abc\abc\.\
Search File: patch1.xml
search form search path:C:\abc\abc\.\
Search File: patch2.xml
search form search path:C:\abc\abc\.\
Search File: patch3.xml
search form search path:C:\abc\abc\.\
Search File: patch4.xml
search form search path:C:\abc\abc\.\
Search File: patch5.xml
search form search path:C:\abc\abc\.\
RAWPROGRAM file path: C:\abc\abc\.\rawprogram_unsparse0.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram1.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram2.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram3.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram_unsparse4.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram5.xml
PATCH file path:C:\abc\abc\.\patch0.xml
PATCH file path:C:\abc\abc\.\patch1.xml
PATCH file path:C:\abc\abc\.\patch2.xml
PATCH file path:C:\abc\abc\.\patch3.xml
PATCH file path:C:\abc\abc\.\patch4.xml
PATCH file path:C:\abc\abc\.\patch5.xml
Process Index:0
Meta Build Content XML Path: C:\abc\contents.xml
Search File: prog_ufs_firehose_8996_ddr.elf
search form search path:C:\abc\.\
Search File: rawprogram_unsparse0.xml
search form search path:C:\abc\.\
Search File: rawprogram1.xml
search form search path:C:\abc\.\
Search File: rawprogram2.xml
search form search path:C:\abc\.\
Search File: rawprogram3.xml
search form search path:C:\abc\.\
Search File: rawprogram_unsparse4.xml
search form search path:C:\abc\.\
Search File: rawprogram5.xml
search form search path:C:\abc\.\
Search File: patch0.xml
search form search path:C:\abc\.\
Search File: patch1.xml
search form search path:C:\abc\.\
Search File: patch2.xml
search form search path:C:\abc\.\
Search File: patch3.xml
search form search path:C:\abc\.\
Search File: patch4.xml
search form search path:C:\abc\.\
Search File: patch5.xml
search form search path:C:\abc\.\
RAWPROGRAM file path: C:\abc\.\rawprogram_unsparse0.xml
RAWPROGRAM file path: C:\abc\.\rawprogram1.xml
RAWPROGRAM file path: C:\abc\.\rawprogram2.xml
RAWPROGRAM file path: C:\abc\.\rawprogram3.xml
RAWPROGRAM file path: C:\abc\.\rawprogram_unsparse4.xml
RAWPROGRAM file path: C:\abc\.\rawprogram5.xml
PATCH file path:C:\abc\.\patch0.xml
PATCH file path:C:\abc\.\patch1.xml
PATCH file path:C:\abc\.\patch2.xml
PATCH file path:C:\abc\.\patch3.xml
PATCH file path:C:\abc\.\patch4.xml
PATCH file path:C:\abc\.\patch5.xml
Start Download
Program Path:C:\abc\prog_ufs_firehose_8996_ddr.elf
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM7 -s 13:C:\abc\prog_ufs_firehose_8996_ddr.elf 'Current working dir: C:\Users\Jean-François\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\abc\prog_ufs_firehose_8996_ddr.elf
20:42:54: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
20:42:54: ERROR: function: sahara_main:854 Sahara protocol error
20:42:54: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Update of 18/98 => everything is now solved.
I changed from my laptop to my HTPC and everything went fine... My Zuk Z2 pro works again!!!! I am so happy.
Click to expand...
Click to collapse
I'm running into the exact same issue. Did you do anything different on the new machine? Unfortunately I do not have another machine to try.. Any helps would be great
EDIT: I was able to get this work. The trick is to click "Download Content" as sooooooon as you hit enter on "adb reboot edl"
And once I did that, I did not get the Sahara error but another random error. Tried a different port on my laptop and it worked perfectly

My Gapps sync are not working!
When i put my login information the google account isn´t syncing!

question
Sorry I am new to this. I purchased a yuk z2 pro 6gb ram 128gb storage and it comes with the international custom ROM put on by the reseller. I would like to change it back to the original oem rom. Is this the directions to follow? If this is the wrong directions can you please show me the correct directions.
Thanks

Zuk Z2 pro bricked
Hello,
thank you for this very detailed description of the process!
I did try it and something went wrong, I do not know where I went off protocol, yet now my phone is unresponsive.
It is fully loaded.
LED is blue, screen black.
Long pressing Vol up plus power -> short vibration and green LED, ZUK logo appears shortly, then screen is black and LED blue again.
When USB is conneted, QFIL 2.0.0.4 does recognize a phone. Chirp on the PC. QUALCOMM HS-USB Diagnostics 900E (COM5) in top line of QFIL
When I try to flash, however, it shows:
"Switch to EDL
Download fail: switch to EDL FailFailed to switch to Emergency Download mode
Finish download."
To me, this seems as a complete brick event.
Could someone of the experts please help me to revive the phone?
Thanks!

Google Tap & Go
Hi,
I would like to get all my apps, and settings back from my One Plus on cm13 to My brand new Zuk Z2 Pro.
How do i make it ?
Must i flash it ?
Thanks

What I understand, you can use miFlash to Flash the qfil according to htt p://www.androidbrick.com/zuk-z2-z2-pro-qpst-qfil-miflash-rom-flashing-guide/

I become always this failer when I will flash my Bricked Z2 Pro
PATCH file path:\zuk\Z2121_CN_OPEN_USER_Q01017.1_M_ZUI_2.3.044_ST_161013_qpst\.\patch5.xml
Process Index:0
Start Download
COM Port number:10
Switch To EDL
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode
Finish Download

Qfil won't recognize zuk z2 pro. Do you have any idea why ?

How do I install these qualcomm drivers ? They aren't executable

I successfully flashed the device according to the logs, but I'm still stuck with a test mode boot loop. I guess my phone is good for the garbage?