Database Users

U8800: ping is high with all rom

Hi
I have tried all the rom for u8800 and all have this problem.
The ping from the phone to the gateway is unstable and high after few moments from the connection.
This is an example:
Immediately after activation of wifi the ping is very good( same as ubuntu) but after few moments the ping becomes high and remains so:
# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=3.66 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=2.16 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=2.25 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.12 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.55 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=2.07 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.09 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=1.12 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=1.12 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=1.19 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=2.35 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=2.04 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=3.02 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=2.22 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=3.26 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=68.7 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=91.1 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=114 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=35.6 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=57.1 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=79.8 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=105 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=126 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=51.5 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=71.8 ms
64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=94.4 ms
64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=117 ms
This is a big problem for voip.
Thanks
Fabry_XY

You're right, I've got the same problem...I think there's something wrong with the retransmit threshold. It goes up to 300ms within the 5 m from the router...

Agreed. The problem exists and occurs usually and randomly.

I have changed the beacon period of my router from 100 to 20, and this is the effect:
# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=34.0 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=35.8 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=14.7 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=40.4 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=42.1 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=44.2 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=25.4 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=25.7 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=29.4 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=31.1 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=33.0 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=35.0 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=37.1 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=39.0 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=41.1 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=43.0 ms

Oh, interesting...It's much more stable now. It doesn't really matter if it's 30-40ms, as long as it's consistent...How's the voip now?

katu2006 said:
Oh, interesting...It's much more stable now. It doesn't really matter if it's 30-40ms, as long as it's consistent...How's the voip now?
Click to expand...
Click to collapse
Now the voip is relatively stable and performance and quality are good.
Is present a few of lag and however the problem remains,the expected ping is of ~2ms and not ~30ms.
Fabry_XY
Edit:
Opening the sip client and making a call the ping decrease:
# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=40.4 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=42.4 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=44.5 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=25.3 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=25.6 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=7.24 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=31.3 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=32.7 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=1.18 ms --Here i make a call with sip client
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=1.57 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=1.16 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=1.35 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=1.49 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=1.99 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=2.32 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=2.08 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=2.32 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=1.66 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=1.97 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=1.54 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=1.27 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=39.8 ms --here i close the call
64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=42.0 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=44.1 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=25.3 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=27.4 ms
64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=29.3 ms
64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=31.1 ms
64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=33.2 ms
64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=34.9 ms
64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=39.9 ms

I believe this is the result of WIFI Power Save Poll mode in action. You can try disabling it and turn CAM (Continually Aware Mode) by setting
gEnableBmps=0
in
/system/etc/firmware/wlan/qcom_cfg.ini
(root required). You will get the minimal ping delays, but the tradeoff will be increased power consumption.

Thankyou.
The ping is always perfect now; i will test battery life

fabryxy said:
Thankyou.
The ping is always perfect now; i will test battery life
Click to expand...
Click to collapse
Please report your battery life observations in CAM mode, someone might be interested.

sorry to hijack this thread... but... I've updated to 2.3 and I don't see any VOIP settings to configure like in normal gingerbread phones... were did it go??

mebico said:
I believe this is the result of WIFI Power Save Poll mode in action. You can try disabling it and turn CAM (Continually Aware Mode) by setting
gEnableBmps=0
in
/system/etc/firmware/wlan/qcom_cfg.ini
(root required). You will get the minimal ping delays, but the tradeoff will be increased power consumption.
Click to expand...
Click to collapse
Did this and it seems also my wifi ap (tethering) problem where connection was being intermittently disconnected with B522 is now solved.

Thread Moved​
As the OP contains no development, I am going to move this to general.​

mebico said:
I believe this is the result of WIFI Power Save Poll mode in action. You can try disabling it and turn CAM (Continually Aware Mode) by setting
gEnableBmps=0
in
/system/etc/firmware/wlan/qcom_cfg.ini
(root required). You will get the minimal ping delays, but the tradeoff will be increased power consumption.
Click to expand...
Click to collapse
worked for me too now i can normally play online games

[Tutorial] How to build a ROM?

Hello everybody. After many attempts to build a ROM I decided to share my knowledge with you
I'm going to show you how to build CM7 for X8 using official CM sources.
As the result you will have:
CyanogenMod in version 2.3.7 for X8 aka Shakira. You need to have unlocked bootloader and flash FXP kernel to use this ROM.
WARNING: This may brick your device. You have been warned!
What are the requirements?
0. A smart head, and being willing to learn something new.
1. A PC featuring a dual-core CPU (the more, the merrier) and at least 1.5GB RAM. Having a CPU that supports 64-Bit Mode (Intel EM64T / AMD64) and Paravirtualization (Intel VT-x / AMD-V) is required if you are planning to run a 64-Bit distribution.
2. A Linux based system such as Ubuntu or Linux Mint. My guide should work on any other Ubuntu based distribution as well, though you need to adapt commands in case you're running a RPM based Red Hat/Fedora/openSUSE distribution. To make things easier if your main OS is Windows you better consider using Linux in a Virtual Machine (VirtualBox recommended).
3. Speedy internet connection so the download of the CyangogenMod sources don't take forever.
4. About 50GB of FREE disk space.
5. Ability to access to Internet in Linux / your Virtual Machine so you can access Google and XDA to search for help, because everything that can go wrong will go wrong ;P
Shall we dance?
1. Download and install Linux. Linux is perfectly legal free opensource software; you won't go to jail for downloading it. I prefer Ubuntu 10.10 or Linux Mint 10 (which I'm using). The best choice is to use the respective 64-Bit edition. You may find links in next post.
2. There is a tool called "Terminal" - it's your new best friend. Create a shortcut in desktop.
How Linux look like
{
"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"
}
Just like Windows, but better
Paste this into terminal:
For Ubuntu below 11.04 use this:
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.8-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev openjdk-6-jdk pngcrush schedtool g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.3-multilib g++-4.3-multilib
NOTE: As for Ubuntu 11.04+ (also applies to Linux Mint 11+) see what Novek posted in the CMCompiler thread.
lib32readline5-dev has been replaced by lib32readline-gplv2-dev on 11.10
And "gcc-4.3-multilib g++-4.3-multilib" aren't used from 11.04 and up - not needed, so use this code:
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.8-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev openjdk-6-jdk pngcrush schedtool g++-multilib lib32z1-dev lib32ncurses5-dev
You may want to add that piece of intel.
This will install required packages. If you'll receive errors try to delete packages from above code.
After this you'll need to create folders for CM repo.
Type:
Code:
mkdir -p ~/bin
mkdir -p ~/android/system
PATH=~/bin:$PATH
You could name second folder as you want.
Next step: Repo installation
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
chmod is a very important command. It's allows you to give permissions for specific files/folders.
Next step: Downloading the beast
Remember to type correct folder name!
Code:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
repo sync -j10
-j attribute is responsible for number of processes taken in single action. If you have powerful PC you could use -j16 or even -j32. Bigger number - quicker extraction of files.
Get the ROM Manager just in case
Code:
~/android/system/vendor/cyanogen/get-rommanager
Next step: Download Android-SDK to make ADB work
Extract this to home directory, then
Code:
cd ~/android-sdk-linux/tools
./android
Just do what is shown in this movies:
Download all files and get ready.
Next step: Copy proprietary files (you need to have phone connected in debugging mode) - For proprietary files use stock ROM or official CM 7.1.
Type in terminal:
Code:
cd ~/android/system/device/semc/shakira/
./extract-files.sh
If you have problems copy adb file to this directory and edit extract-files.sh to have something like this:
./adb pull instead of adb pull
If you have troubles do this:
After installation open terminal and type:
Code:
export PATH=${PATH}:~/android-sdk-linux/tools
export PATH=${PATH}:~/android-sdk-linux/platform-tools
Put correct path to your adb.
Type
Code:
./adb devices
if you'll receive such line
Code:
"List of devices attached
???????????? no permissions"
do specific thing.
Code:
sudo touch /etc/udev/rules.d/51-android.rules && sudo sh -c "echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", SYSFS{idProduct}=="612e", MODE="0666"' >> /etc/udev/rules.d/51-android.rules" && sudo chmod 644 /etc/udev/rules.d/51-android.rules
If something goes wrong type
Code:
lsusb
to see which devices are connected and change code.
Then
Code:
sudo restart udev
sudo ./adb kill-server
sudo ./adb start-server
And it's ready to action.
Next step: Setting build environment
Type in terminal:
Code:
cd ~/android/system/
. build/envsetup.sh && breakfast shakira
You'll see the list of CM devices
Shakira is number 136 (right now is #144) - It won't work due to changes in CM device tree.
So use:
Code:
lunch cyanogen_shakira-eng
or
breakfast shakira
Next: Step - build!
All you need to do right now is type magic command "make"
Add -j4 to make it much quicker
To obtain update.zip file type
Code:
make -j4 bacon
Now wait patiently and fight errors
I'm glad if I helped somebody to build his/her first ROM.
If I made any mistakes feel free to correct me.
Thanks to B.Jay for help.
I spent some time to write this, so hit thanks button
You can also donate me. All donations are highly appreciated :beer:

Okay, since eagleeyetom decided to make his research about how to build CM7 public, here are a few thoughts of my own to accompany his guide...
If you're a Windows user and don't want to go through the hassle of dual-booting Linux with Windows XP/Vista/7 it's highly recommended that you install VirtualBox as your virtualization software (also download and install the Extensions Pack if you want to connect to your phone through USB right out of the VM!). Stay clear from VMware Player or VMware Workstation. Things like 3D acceleration will not work with VMware! A important aspect if you're opting to install a Gnome3/GTK3 based distribution release, or you simply want the eye-candy to make work more fun.
This means ... the specs of your system should be above "average". Since the Virtual Machine, into which you're going to install Linux, will need some RAM for its own don't even think about this approach if your system is at, or well below, 3GB RAM. Especially with Windows Vista or Windows 7 being your OS upon which VirtualBox will run you will find yourself in the situation very quickly that Windows sucks up a good Gigabyte of RAM just for itself - and keep in mind that VirtualBox will need a wee bit more than just the 1.5GB RAM (or whatever you're going to assign) + 8MB VRAM to run.
Of course you also need some spare space on your hard drive(s) as you need to create a Virtual Hard Drive for the Virtual Machine. 80GB should be considered the minimum here as you're going to need quite some space for the source, the temp files that get created during the compile, and the finalized ROM.
I'd recommend you partition your virtual hard drive this way...
~1GB ext4 as /boot
2* the amount of RAM you assigned to your VM as swap (3GB swap if your VM runs on 1.5GB RAM)
The rest ext4 as /
Stay away from btrfs as it will give terrible performance in a VM.
A better partitioning would be to keep / and /home separated in case you plan to upgrade the Linux installation in your VM...
~1GB ext4 as /boot
2* the amount of RAM you assigned to your VM as swap (3GB swap if your VM runs on 1.5GB RAM)
~10-15GB ext4 as /
The rest ext4 as /home
That way you won't lose your stuff in /home in case things go wrong at an dist-upgrade.
Once you got Linux Installed install the Guest Additions ... it'll make working with your Virtual Machine and switching back and forth between the host OS and your VM way easier. In case the build of the kernel modules bombs out with a error message open a terminal and issue "sudo apt-get install build-essentials" ... that should solve the problem.
While you should get by with 1.5GB RAM to build CM7 (aka "Gingerbread") Google specifies the use of a 64-Bit Linux Distribution and at least 8GB RAM to tinker around with Ice Cream Sandwich. If you want to play around with the CM9 sources once they become available to the masses you better keep the aforementioned system requirements in mind.
If you happen to have questions about setting up VirtualBox feel free to post.
Value added Links:
Linux Mint 10 (as used by eagleeyetom)
Download here
Linux Mint 12 (latest version at the time of writing)
Download here
Ubuntu Linux 10.04 LTS or 11.10
Download here

Great man
Tfs..!!
Sent from my Micromax A60 using xda premium

Thanks fir the guide. I bow have Linux on my own laptop

will definitely try to build my own rom,
thank you.

One Question , this rom will be for stock kernel am i right ?

This ROM will be for FXP kernel.
Sent from my X8 using xda premium

and last question , what android it will be , i mean version ? 2.3.5 or 2.3.7 ?
If it will be something like that im going to made my rom ;D

It's 2.3.7. The same as the latest nightly for Shakira. Good luck
Sent from my X8 using xda premium

Let us know of results of building your ROMs. If you have any questions or can't solve errors, post it here - maybe we will be able to handle them

Thanks for the nice tutorial. Will try it.
I think I need to update my laptop as well because I will like to try it for the ICS also.
Any ways thank you very much for the tutorial.

adb is givin me error and i do the second step "./adb pull instead of adb pull" it givis device not found....
what do i do?

After installation open termina and type:
Code:
export PATH=${PATH}:~/android-sdk-linux/tools
export PATH=${PATH}:~/android-sdk-linux/platform-tools
Put correct path to your adb.
Type ./adb devices if you'll receive such line "List of devices attached
???????????? no permissions" do specific thing.
Code:
sudo touch /etc/udev/rules.d/51-android.rules && sudo sh -c "echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", SYSFS{idProduct}=="612e", MODE="0666"' >> /etc/udev/rules.d/51-android.rules" && sudo chmod 644 /etc/udev/rules.d/51-android.rules
If something goes wrong type lsusb to see which devices are connected and change code.
Then
Code:
sudo restart udev
sudo ./adb kill-server
sudo ./adb start-server
And it's ready to action.

Allow me to add the following piece of intel about the "51-android.rules" file in /etc/udev/rules.d/
For Ubuntu 10.04 LTS / Ubuntu 10.10 / Linux Mint 9 / Linux Mint 10
The better format of the file would be...
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", SYSFS{idProduct}=="612e", SYMLINK+="android_adb", MODE="0666", GROUP="plugdev"
Starting with Ubuntu Linux 11.04 / Linux Mint 11 the format of the file has changed and needs to be written as...
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce:612e", SYMLINK+="android_adb", MODE="0666", GROUP="plugdev", TEST=="/var/run/ConsoleKit/database", RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
Just in case anyone following the guide doesn't run Lucid/Isadora or Maverick/Julia.

eagleeyetom said:
After installation open termina and type:
Code:
export PATH=${PATH}:~/android-sdk-linux/tools
export PATH=${PATH}:~/android-sdk-linux/platform-tools
Put correct path to your adb.
i did this and then i type ./adb devices
an shows bash: ./adb: No such file or directory
the path is the one
Click to expand...
Click to collapse

Leave out the ./ in front of adb
One you exported the path to where adb is located it will be found automatically.
./adb means that "adb" is located in the current directory you're in (./)
Also make sure that adb itself is executable!
---------- Post added at 03:02 PM ---------- Previous post was at 02:55 PM ----------
Also, to make the path thing permanent ...
- Open a terminal
- touch ~/.bashrc (in case the file doesn't exist)
- gedit ~/.bashrc
Insert ...
Code:
export PATH=${PATH}:~/android-sdk-linux/tools
export PATH=${PATH}:~/android-sdk-linux/platform-tools
- Save the file.
Now, every time you log in the path with automatically be added to the path search tree.

its done
[email protected] ~/android/system/device/semc/shakira $ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0bda:8197 Realtek Semiconductor Corp. RTL8187B Wireless Adapter
Bus 002 Device 002: ID 0fce:2149 Sony Ericsson Mobile Communications AB Xperia X8 (debug)
[email protected] ~/android/system/device/semc/shakira $ ./extract-files.sh
19 KB/s (822 bytes in 0.040s)
6 KB/s (281 bytes in 0.040s)
21 KB/s (896 bytes in 0.040s)
21 KB/s (896 bytes in 0.040s)
358 KB/s (31712 bytes in 0.086s)
remote object '/system/bin/port-bridge' does not exist
468 KB/s (23516 bytes in 0.049s)
109 KB/s (9260 bytes in 0.082s)
1550 KB/s (185892 bytes in 0.117s)
213 KB/s (17904 bytes in 0.081s)
158 KB/s (13336 bytes in 0.082s)
322 KB/s (29872 bytes in 0.090s)
749 KB/s (93940 bytes in 0.122s)
517 KB/s (54364 bytes in 0.102s)
480 KB/s (50364 bytes in 0.102s)
590 KB/s (66844 bytes in 0.110s)
892 KB/s (62692 bytes in 0.068s)
116 KB/s (9300 bytes in 0.078s)
797 KB/s (93004 bytes in 0.113s)
278 KB/s (25784 bytes in 0.090s)
716 KB/s (86708 bytes in 0.118s)
62 KB/s (5008 bytes in 0.078s)
remote object '/system/lib/libuim.so' does not exist
1784 KB/s (808160 bytes in 0.442s)
698 KB/s (78940 bytes in 0.110s)
391 KB/s (37856 bytes in 0.094s)
1561 KB/s (483024 bytes in 0.302s)
1064 KB/s (163608 bytes in 0.150s)
1910 KB/s (576104 bytes in 0.294s)
112 KB/s (9412 bytes in 0.081s)
573 KB/s (71700 bytes in 0.122s)
209 KB/s (17636 bytes in 0.082s)
1064 KB/s (171904 bytes in 0.157s)
400 KB/s (38372 bytes in 0.093s)
212 KB/s (17836 bytes in 0.081s)
400 KB/s (38396 bytes in 0.093s)
398 KB/s (38452 bytes in 0.094s)
1116 KB/s (190020 bytes in 0.166s)
448 KB/s (46856 bytes in 0.102s)
399 KB/s (38372 bytes in 0.093s)
1033 KB/s (183460 bytes in 0.173s)
673 KB/s (42492 bytes in 0.061s)
235 KB/s (22160 bytes in 0.091s)
327 KB/s (30144 bytes in 0.089s)
327 KB/s (30144 bytes in 0.089s)
1627 KB/s (590324 bytes in 0.354s)
27 KB/s (1156 bytes in 0.041s)
109 KB/s (9220 bytes in 0.082s)
19 KB/s (820 bytes in 0.040s)
17 KB/s (745 bytes in 0.040s)
15 KB/s (635 bytes in 0.040s)
31 KB/s (1297 bytes in 0.040s)
184 KB/s (15513 bytes in 0.081s)
412 KB/s (21613 bytes in 0.051s)
1033 KB/s (84571 bytes in 0.079s)
114 KB/s (9640 bytes in 0.082s)
158 KB/s (13340 bytes in 0.082s)
1314 KB/s (271892 bytes in 0.201s)
remote object '/system/etc/wifi/softap/tiwlan_ap.ini' does not exist
remote object '/system/etc/wifi/softap/tiwlan_firmware_ap.bin' does not exist
371 KB/s (34308 bytes in 0.090s)
1086 KB/s (162880 bytes in 0.146s)
1183 KB/s (210640 bytes in 0.173s)
694 KB/s (75656 bytes in 0.106s)
2024 KB/s (1746564 bytes in 0.842s)
393 KB/s (33514 bytes in 0.083s)
174 KB/s (287 bytes in 0.001s)
982 KB/s (95456 bytes in 0.094s)
91 KB/s (3823 bytes in 0.040s)
170 KB/s (13836 bytes in 0.079s)
119 KB/s (9640 bytes in 0.078s)
114 KB/s (9292 bytes in 0.079s)
69 KB/s (5576 bytes in 0.077s)
290 KB/s (26852 bytes in 0.090s)
210 KB/s (17780 bytes in 0.082s)
65 KB/s (5252 bytes in 0.078s)
114 KB/s (9172 bytes in 0.078s)
remote object '/system/app/AntHalService.apk' does not exist
4 KB/s (189 bytes in 0.040s)
20 KB/s (842 bytes in 0.040s)
remote object '/system/lib/libanthal.so' does not exist
[email protected] ~/android/system/device/semc/shakira $ . build/envsetup.sh && lunch
bash: build/envsetup.sh: No such file or directory
[email protected] ~/android/system/device/semc/shakira $ ./extract-files.sh19 KB/s (822 bytes in 0.040s)
6 KB/s (281 bytes in 0.040s)
21 KB/s (896 bytes in 0.040s)
21 KB/s (896 bytes in 0.040s)
358 KB/s (31712 bytes in 0.086s)
remote object '/system/bin/port-bridge' does not exist
468 KB/s (23516 bytes in 0.049s)
115 KB/s (9260 bytes in 0.078s)
1665 KB/s (185892 bytes in 0.109s)
223 KB/s (17904 bytes in 0.078s)
166 KB/s (13336 bytes in 0.078s)
337 KB/s (29872 bytes in 0.086s)
830 KB/s (93940 bytes in 0.110s)
563 KB/s (54364 bytes in 0.094s)
479 KB/s (50364 bytes in 0.102s)
636 KB/s (66844 bytes in 0.102s)
957 KB/s (62692 bytes in 0.063s)
115 KB/s (9300 bytes in 0.078s)
823 KB/s (93004 bytes in 0.110s)
291 KB/s (25784 bytes in 0.086s)
769 KB/s (86708 bytes in 0.110s)
62 KB/s (5008 bytes in 0.078s)
remote object '/system/lib/libuim.so' does not exist
2042 KB/s (808160 bytes in 0.386s)
752 KB/s (78940 bytes in 0.102s)
427 KB/s (37856 bytes in 0.086s)
1854 KB/s (483024 bytes in 0.254s)
1188 KB/s (163608 bytes in 0.134s)
2126 KB/s (576104 bytes in 0.264s)
117 KB/s (9412 bytes in 0.078s)
682 KB/s (71700 bytes in 0.102s)
208 KB/s (17636 bytes in 0.082s)
1178 KB/s (171904 bytes in 0.142s)
434 KB/s (38372 bytes in 0.086s)
222 KB/s (17836 bytes in 0.078s)
433 KB/s (38396 bytes in 0.086s)
434 KB/s (38452 bytes in 0.086s)
1267 KB/s (190020 bytes in 0.146s)
485 KB/s (46856 bytes in 0.094s)
433 KB/s (38372 bytes in 0.086s)
1293 KB/s (183460 bytes in 0.138s)
740 KB/s (42492 bytes in 0.056s)
447 KB/s (22160 bytes in 0.048s)
340 KB/s (30144 bytes in 0.086s)
340 KB/s (30144 bytes in 0.086s)
1983 KB/s (590324 bytes in 0.290s)
27 KB/s (1156 bytes in 0.040s)
114 KB/s (9220 bytes in 0.078s)
19 KB/s (820 bytes in 0.040s)
17 KB/s (745 bytes in 0.040s)
15 KB/s (635 bytes in 0.040s)
31 KB/s (1297 bytes in 0.040s)
193 KB/s (15513 bytes in 0.078s)
435 KB/s (21613 bytes in 0.048s)
1140 KB/s (84571 bytes in 0.072s)
120 KB/s (9640 bytes in 0.078s)
166 KB/s (13340 bytes in 0.078s)
1490 KB/s (271892 bytes in 0.178s)
remote object '/system/etc/wifi/softap/tiwlan_ap.ini' does not exist
remote object '/system/etc/wifi/softap/tiwlan_firmware_ap.bin' does not exist
388 KB/s (34308 bytes in 0.086s)
1183 KB/s (162880 bytes in 0.134s)
1334 KB/s (210640 bytes in 0.154s)
721 KB/s (75656 bytes in 0.102s)
2401 KB/s (1746564 bytes in 0.710s)
393 KB/s (33514 bytes in 0.083s)
6 KB/s (287 bytes in 0.040s)
844 KB/s (95456 bytes in 0.110s)
91 KB/s (3823 bytes in 0.040s)
172 KB/s (13836 bytes in 0.078s)
120 KB/s (9640 bytes in 0.078s)
115 KB/s (9292 bytes in 0.078s)
69 KB/s (5576 bytes in 0.078s)
303 KB/s (26852 bytes in 0.086s)
221 KB/s (17780 bytes in 0.078s)
65 KB/s (5252 bytes in 0.078s)
114 KB/s (9172 bytes in 0.077s)
remote object '/system/app/AntHalService.apk' does not exist
4 KB/s (189 bytes in 0.040s)
19 KB/s (842 bytes in 0.041s)
remote object '/system/lib/libanthal.so' does not exist
[email protected] ~/android/system/device/semc/shakira $ .build/envsetup.sh && lunch
bash: .build/envsetup.sh: No such file or directory
then it shows this... what to do???

brunodmsa said:
[email protected] ~/android/system/device/semc/shakira $ .build/envsetup.sh && lunch
bash: .build/envsetup.sh: No such file or directory
then it shows this... what to do???
Click to expand...
Click to collapse
I think you typoed, if that's a direct copy/paste.
There should be a space between the dot and build.
. build/envsetup.sh && lunch
NOT
.build/envsetup.sh && lunch

B.Jay said:
I think you typoed, if that's a direct copy/paste.
There should be a space between the dot and build.
. build/envsetup.sh && lunch
NOT
.build/envsetup.sh && lunch
Click to expand...
Click to collapse
it as a space and shows the same thing...
one q? why do i have to conect my x8 to pc?

Nice share
Nice share...thanks button pressed..Can im using Backbox linux boot from usb..

[Q] building CM11 help

okay so everything goes fine up till i get to the ./extract-files.sh where it comes up with
[email protected]:~/android/system/device/lge/mako# ./extract-files.sh
261 KB/s (21784 bytes in 0.081s)
413 KB/s (34448 bytes in 0.081s)
115 KB/s (9648 bytes in 0.081s)
126 KB/s (5464 bytes in 0.042s)
170 KB/s (14248 bytes in 0.081s)
705 KB/s (58848 bytes in 0.081s)
146 KB/s (12172 bytes in 0.081s)
1076 KB/s (125020 bytes in 0.113s)
462 KB/s (38576 bytes in 0.081s)
125 KB/s (5416 bytes in 0.042s)
remote object '/system/bin/mpdecision' does not exist
1088 KB/s (117324 bytes in 0.105s)
64 KB/s (5356 bytes in 0.081s)
214 KB/s (17804 bytes in 0.080s)
285 KB/s (28144 bytes in 0.096s)
507 KB/s (48292 bytes in 0.092s)
126 KB/s (5452 bytes in 0.042s)
364 KB/s (30088 bytes in 0.080s)
232 KB/s (19408 bytes in 0.081s)
1237 KB/s (207940 bytes in 0.164s)
remote object '/system/bin/thermald' does not exist
those are the only 2 things stopping me until this point

Guys over here may be able to help you http://forum.xda-developers.com/showthread.php?p=29363625
Sent from my Nexus 5 using XDA Free mobile app

Thanks I'll give it a look
Sent from my Nexus 4 using Tapatalk

LG G6 H872 tmobile shows qualcomm 9008 mode i need partition file to unbrick

hi I am looking LG-VS988 dump file or h872 dump file to unbrick my L6 H872 my phone in QUALCOMM 9008 mode please help
I need MSM8996 .mbn file and rawprogram0.xml
to restore back my device now stucked on Qualcomm HS-USB QDLoader 9008 mode
I have same phone working condition can anyone guide me how to read files from working phone ?
thanks in advance
please help

I have same brand and same problem nobody here have a solution...did You fix It? If Yes how? It is strange is pass more then One years and nobody found a solution

deepmobileworld said:
hi I am looking LG-VS988 dump file or h872 dump file to unbrick my L6 H872 my phone in QUALCOMM 9008 mode please help
I need MSM8996 .mbn file and rawprogram0.xml
to restore back my device now stucked on Qualcomm HS-USB QDLoader 9008 mode
I have same phone working condition can anyone guide me how to read files from working phone ?
thanks in advance
please help
Click to expand...
Click to collapse
I think you should flash some stock stuff to have it working again.
In order, you have to restore your stock KDZ: you can use this guide, or try this.
In addition, you could need to follow these steps to restore your Qualcomm micro-firmware (according to your chipset, you’ll have to use some different files).
If you tell me how to recreate this situation, I’ll try something.
Good luck! :fingers-crossed:

kdz extract linux sd card write done
command link https://mega.nz/#!cJ9WUAiA!TSt9L5G3C...n8vx0pQ9ToxCFw
https://forum.xda-developers.com/g4/...-qfil-t3748946
sorry bad english
[email protected]:~/Downloads$ sudo dmesg -c >> /dev/null
[sudo] password for aaya:
[email protected]:~/Downloads$ dmesg
[email protected]:~/Downloads$ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 58,4 GiB, 62730010624 bytes, 122519552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 122519551 122517504 58,4G c W95 FAT32 (LBA)
[email protected]:~/Downloads$ cd kdz
[email protected]:~/Downloads/kdz$ sudo -s
[email protected]:~/Downloads/kdz# dd if=PrimaryGPT.bin of=/dev/sdb
48+0 records in
48+0 records out
24576 bytes (25 kB, 24 KiB) copied, 0,0441583 s, 557 kB/s
[email protected]:~/Downloads/kdz# sync
[email protected]:~/Downloads/kdz# ls -la /dev/disk/by-partlabel
total 0
drwxr-xr-x 2 root root 60 Луу 18 19:32 .
drwxr-xr-x 7 root root 140 Луу 18 19:32 ..
lrwxrwxrwx 1 root root 10 Луу 18 18:35 EFI\x20System\x20Partition -> ../../sda1
[email protected]:~/Downloads/kdz# cd kdz
bash: cd: kdz: No such file or directory
[email protected]:~/Downloads/kdz# for i in $(ls *.bin |egrep -v "(GPT|userdata)");do echo dd if=$i of=/dev/disk/by-partlabel/${i/\.bin};done
dd if=abootbak.bin of=/dev/disk/by-partlabel/abootbak
dd if=aboot.bin of=/dev/disk/by-partlabel/aboot
dd if=apdp.bin of=/dev/disk/by-partlabel/apdp
dd if=boot.bin of=/dev/disk/by-partlabel/boot
dd if=cache.bin of=/dev/disk/by-partlabel/cache
dd if=cdt.bin of=/dev/disk/by-partlabel/cdt
dd if=cmnlib64bak.bin of=/dev/disk/by-partlabel/cmnlib64bak
dd if=cmnlib64.bin of=/dev/disk/by-partlabel/cmnlib64
dd if=cmnlibbak.bin of=/dev/disk/by-partlabel/cmnlibbak
dd if=cmnlib.bin of=/dev/disk/by-partlabel/cmnlib
dd if=ddr.bin of=/dev/disk/by-partlabel/ddr
dd if=devcfgbak.bin of=/dev/disk/by-partlabel/devcfgbak
dd if=devcfg.bin of=/dev/disk/by-partlabel/devcfg
dd if=devinfo.bin of=/dev/disk/by-partlabel/devinfo
dd if=dip.bin of=/dev/disk/by-partlabel/dip
dd if=dpo.bin of=/dev/disk/by-partlabel/dpo
dd if=drm.bin of=/dev/disk/by-partlabel/drm
dd if=eksst.bin of=/dev/disk/by-partlabel/eksst
dd if=encrypt.bin of=/dev/disk/by-partlabel/encrypt
dd if=factory.bin of=/dev/disk/by-partlabel/factory
dd if=fota.bin of=/dev/disk/by-partlabel/fota
dd if=fsc.bin of=/dev/disk/by-partlabel/fsc
dd if=fsg.bin of=/dev/disk/by-partlabel/fsg
dd if=grow2.bin of=/dev/disk/by-partlabel/grow2
dd if=grow3.bin of=/dev/disk/by-partlabel/grow3
dd if=grow4.bin of=/dev/disk/by-partlabel/grow4
dd if=grow5.bin of=/dev/disk/by-partlabel/grow5
dd if=grow6.bin of=/dev/disk/by-partlabel/grow6
dd if=grow.bin of=/dev/disk/by-partlabel/grow
dd if=hypbak.bin of=/dev/disk/by-partlabel/hypbak
dd if=hyp.bin of=/dev/disk/by-partlabel/hyp
dd if=keymasterbak.bin of=/dev/disk/by-partlabel/keymasterbak
dd if=keymaster.bin of=/dev/disk/by-partlabel/keymaster
dd if=keystore.bin of=/dev/disk/by-partlabel/keystore
dd if=lafbak.bin of=/dev/disk/by-partlabel/lafbak
dd if=laf.bin of=/dev/disk/by-partlabel/laf
dd if=misc.bin of=/dev/disk/by-partlabel/misc
dd if=modem.bin of=/dev/disk/by-partlabel/modem
dd if=modemst1.bin of=/dev/disk/by-partlabel/modemst1
dd if=modemst2.bin of=/dev/disk/by-partlabel/modemst2
dd if=mpt.bin of=/dev/disk/by-partlabel/mpt
dd if=msadp.bin of=/dev/disk/by-partlabel/msadp
dd if=persist.bin of=/dev/disk/by-partlabel/persist
dd if=pmicbak.bin of=/dev/disk/by-partlabel/pmicbak
dd if=pmic.bin of=/dev/disk/by-partlabel/pmic
dd if=raw_resourcesbak.bin of=/dev/disk/by-partlabel/raw_resourcesbak
dd if=raw_resources.bin of=/dev/disk/by-partlabel/raw_resources
dd if=rct.bin of=/dev/disk/by-partlabel/rct
dd if=recoverybak.bin of=/dev/disk/by-partlabel/recoverybak
dd if=recovery.bin of=/dev/disk/by-partlabel/recovery
dd if=reserve.bin of=/dev/disk/by-partlabel/reserve
dd if=rpmbak.bin of=/dev/disk/by-partlabel/rpmbak
dd if=rpm.bin of=/dev/disk/by-partlabel/rpm
dd if=sec.bin of=/dev/disk/by-partlabel/sec
dd if=sns.bin of=/dev/disk/by-partlabel/sns
dd if=spare1.bin of=/dev/disk/by-partlabel/spare1
dd if=spare2.bin of=/dev/disk/by-partlabel/spare2
dd if=ssd.bin of=/dev/disk/by-partlabel/ssd
dd if=system.bin of=/dev/disk/by-partlabel/system
dd if=tzbak.bin of=/dev/disk/by-partlabel/tzbak
dd if=tz.bin of=/dev/disk/by-partlabel/tz
dd if=xbl2bak.bin of=/dev/disk/by-partlabel/xbl2bak
dd if=xbl2.bin of=/dev/disk/by-partlabel/xbl2
dd if=xblbak.bin of=/dev/disk/by-partlabel/xblbak
dd if=xbl.bin of=/dev/disk/by-partlabel/xbl
[email protected]:~/Downloads/kdz# for i in $(ls *.bin |egrep -v "(GPT|userdata)");do dd if=$i of=/dev/disk/by-partlabel/${i/\.bin};done
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0645802 s, 32,5 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,033826 s, 62,0 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0139195 s, 37,7 MB/s
81920+0 records in
81920+0 records out
41943040 bytes (42 MB, 40 MiB) copied, 0,538989 s, 77,8 MB/s
1048576+0 records in
1048576+0 records out
536870912 bytes (537 MB, 512 MiB) copied, 6,8639 s, 78,2 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000314755 s, 13,0 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00478674 s, 110 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00568034 s, 92,3 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00660332 s, 79,4 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00483936 s, 108 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0297275 s, 70,5 MB/s
256+0 records in
256+0 records out
131072 bytes (131 kB, 128 KiB) copied, 0,00236585 s, 55,4 MB/s
256+0 records in
256+0 records out
131072 bytes (131 kB, 128 KiB) copied, 0,00274482 s, 47,8 MB/s
2048+0 records in
2048+0 records out
1048576 bytes (1,0 MB, 1,0 MiB) copied, 0,0135021 s, 77,7 MB/s
2048+0 records in
2048+0 records out
1048576 bytes (1,0 MB, 1,0 MiB) copied, 0,0120692 s, 86,9 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0153506 s, 34,2 MB/s
20480+0 records in
20480+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 0,13946 s, 75,2 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00688644 s, 76,1 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0049967 s, 105 MB/s
135168+0 records in
135168+0 records out
69206016 bytes (69 MB, 66 MiB) copied, 1,01334 s, 68,3 MB/s
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,0511182 s, 82,1 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00611613 s, 85,7 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0170799 s, 123 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000273026 s, 15,0 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000179081 s, 22,9 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000323429 s, 12,7 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,00018018 s, 22,7 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000267083 s, 15,3 MB/s
7080+0 records in
7080+0 records out
3624960 bytes (3,6 MB, 3,5 MiB) copied, 0,0571791 s, 63,4 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00556187 s, 94,3 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00537099 s, 97,6 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00457723 s, 115 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0146511 s, 35,8 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00600904 s, 87,2 MB/s
98304+0 records in
98304+0 records out
50331648 bytes (50 MB, 48 MiB) copied, 0,67333 s, 74,8 MB/s
98304+0 records in
98304+0 records out
50331648 bytes (50 MB, 48 MiB) copied, 0,616455 s, 81,6 MB/s
65536+0 records in
65536+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0,404057 s, 83,0 MB/s
176128+0 records in
176128+0 records out
90177536 bytes (90 MB, 86 MiB) copied, 1,1437 s, 78,8 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0244209 s, 85,9 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0240775 s, 87,1 MB/s
65536+0 records in
65536+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0,426183 s, 78,7 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00713832 s, 73,4 MB/s
65536+0 records in
65536+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0,405352 s, 82,8 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0956617 s, 5,5 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00720851 s, 72,7 MB/s
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,0700125 s, 59,9 MB/s
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,0754277 s, 55,6 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0422099 s, 12,4 MB/s
82944+0 records in
82944+0 records out
42467328 bytes (42 MB, 40 MiB) copied, 0,51604 s, 82,3 MB/s
82944+0 records in
82944+0 records out
42467328 bytes (42 MB, 40 MiB) copied, 0,542084 s, 78,3 MB/s
64+0 records in
64+0 records out
32768 bytes (33 kB, 32 KiB) copied, 0,00882342 s, 3,7 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0230715 s, 22,7 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0240835 s, 21,8 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00557492 s, 94,0 MB/s
12288+0 records in
12288+0 records out
6291456 bytes (6,3 MB, 6,0 MiB) copied, 0,100289 s, 62,7 MB/s
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,0708991 s, 59,2 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,042133 s, 49,8 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0214201 s, 24,5 MB/s
dd: writing to '/dev/disk/by-partlabel/system': No space left on device
1740777+0 records in
1740776+0 records out
891277312 bytes (891 MB, 850 MiB) copied, 11,3213 s, 78,7 MB/s
dd: writing to '/dev/disk/by-partlabel/tzbak': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0257604 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/tz': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0130488 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/xbl2bak': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0112316 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/xbl2': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00448855 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/xblbak': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00429619 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/xbl': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00457151 s, 0,0 kB/s
[email protected]:~/Downloads/kdz#

Hey Bro,
link Mega is encrypted, help
Regards

Nexus 7 2013 Unbricking Guide for Linux and Mac OS X

If your tablet can boot in fastboot mode, you do not need it.
Install VirtualBox
Import and run Microsoft free Windows virtual machine in VirtualBox
Follow Nexus 7 2013 Unbricking Guide for Windows 10 x64 with these VB modifications:
- after "turn on and connect N7 to PC", connect this device in VB:
{
"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"
}
- after "click Flash", connect this device (again) in VB:
"flashing is finished after 85 seconds" - it takes longer in VB, approximately 110 seconds:
This guide also applies to Windows 7 x86 (I tested IE9.Win7.VirtualBox.zip).
For Windows x86 the "Win10-x64-VID_05C6&PID_9008-v2.1.0.5.zip" driver is optional.

Linux' native N7 unbricking solution may be possible. I partially tested unbrick_8960:
- extract MPRG8064.hex and 8064_msimage.mbn from N7-MiFlash-min.zip and copy/overwrite files in the 'unbrick_8960-master\hexmbn\chips\apq8064' folder
- run the 'unbrick' script
Code:
lsusb
Bus 003 Device 006: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
chmod +x ./unbrick.sh
./unbrick.sh
unbrick_8960 v1.1
Originally by Darkspr1te, forked by aureljared.
See README for credits.
Available device files:
GT-I8730 SCH-I535
Enter your device model from above, case-sensitive: GT-I8730
(device model is irrelevant at this stage)
Supported chips:
apq8064 msm8930 msm8960
Enter your chip model from above, case-sensitive: apq8064
Checking for Qualcomm devices in QDLOAD mode... found!
Do you wish to upload MPRG8064.hex & 8064_msimage.mbn now? [y/n]: y
Executing qdload.pl...
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting Params...
Params: 08 01 06 00 90 00 00
Uploading file 'hexmbn/chips/apq8064/MPRG8064.hex' to QDLOAD...
Writing 1024 bytes to 0x2a000000; 166014 bytes left.
Writing 1024 bytes to 0x2a000400; 164990 bytes left.
Writing 1024 bytes to 0x2a000800; 163966 bytes left.
Writing 1024 bytes to 0x2a000c00; 162942 bytes left.
Writing 1024 bytes to 0x2a001000; 161918 bytes left.
Writing 1024 bytes to 0x2a001400; 160894 bytes left.
Writing 1024 bytes to 0x2a001800; 159870 bytes left.
Writing 1024 bytes to 0x2a001c00; 158846 bytes left.
Writing 1024 bytes to 0x2a002000; 157822 bytes left.
Writing 1024 bytes to 0x2a002400; 156798 bytes left.
Writing 1024 bytes to 0x2a002800; 155774 bytes left.
Writing 1024 bytes to 0x2a002c00; 154750 bytes left.
Writing 1024 bytes to 0x2a003000; 153726 bytes left.
Writing 1024 bytes to 0x2a003400; 152702 bytes left.
Writing 1024 bytes to 0x2a003800; 151678 bytes left.
Writing 1024 bytes to 0x2a003c00; 150654 bytes left.
Writing 1024 bytes to 0x2a004000; 149630 bytes left.
Writing 1024 bytes to 0x2a004400; 148606 bytes left.
Writing 1024 bytes to 0x2a004800; 147582 bytes left.
Writing 1024 bytes to 0x2a004c00; 146558 bytes left.
Writing 1024 bytes to 0x2a005000; 145534 bytes left.
Writing 1024 bytes to 0x2a005400; 144510 bytes left.
Writing 1024 bytes to 0x2a005800; 143486 bytes left.
Writing 1024 bytes to 0x2a005c00; 142462 bytes left.
Writing 1024 bytes to 0x2a006000; 141438 bytes left.
Writing 1024 bytes to 0x2a006400; 140414 bytes left.
Writing 1024 bytes to 0x2a006800; 139390 bytes left.
Writing 1024 bytes to 0x2a006c00; 138366 bytes left.
Writing 1024 bytes to 0x2a007000; 137342 bytes left.
Writing 1024 bytes to 0x2a007400; 136318 bytes left.
Writing 1024 bytes to 0x2a007800; 135294 bytes left.
Writing 1024 bytes to 0x2a007c00; 134270 bytes left.
Writing 1024 bytes to 0x2a008000; 133246 bytes left.
Writing 1024 bytes to 0x2a008400; 132222 bytes left.
Writing 1024 bytes to 0x2a008800; 131198 bytes left.
Writing 1024 bytes to 0x2a008c00; 130174 bytes left.
Writing 1024 bytes to 0x2a009000; 129150 bytes left.
Writing 1024 bytes to 0x2a009400; 128126 bytes left.
Writing 1024 bytes to 0x2a009800; 127102 bytes left.
Writing 1024 bytes to 0x2a009c00; 126078 bytes left.
Writing 1024 bytes to 0x2a00a000; 125054 bytes left.
Writing 1024 bytes to 0x2a00a400; 124030 bytes left.
Writing 1024 bytes to 0x2a00a800; 123006 bytes left.
Writing 1024 bytes to 0x2a00ac00; 121982 bytes left.
Writing 1024 bytes to 0x2a00b000; 120958 bytes left.
Writing 1024 bytes to 0x2a00b400; 119934 bytes left.
Writing 1024 bytes to 0x2a00b800; 118910 bytes left.
Writing 1024 bytes to 0x2a00bc00; 117886 bytes left.
Writing 1024 bytes to 0x2a00c000; 116862 bytes left.
Writing 1024 bytes to 0x2a00c400; 115838 bytes left.
Writing 1024 bytes to 0x2a00c800; 114814 bytes left.
Writing 1024 bytes to 0x2a00cc00; 113790 bytes left.
Writing 1024 bytes to 0x2a00d000; 112766 bytes left.
Writing 1024 bytes to 0x2a00d400; 111742 bytes left.
Writing 1024 bytes to 0x2a00d800; 110718 bytes left.
Writing 1024 bytes to 0x2a00dc00; 109694 bytes left.
Writing 1024 bytes to 0x2a00e000; 108670 bytes left.
Writing 1024 bytes to 0x2a00e400; 107646 bytes left.
Writing 1024 bytes to 0x2a00e800; 106622 bytes left.
Writing 1024 bytes to 0x2a00ec00; 105598 bytes left.
Writing 1024 bytes to 0x2a00f000; 104574 bytes left.
Writing 1024 bytes to 0x2a00f400; 103550 bytes left.
Writing 1024 bytes to 0x2a00f800; 102526 bytes left.
Writing 1024 bytes to 0x2a00fc00; 101502 bytes left.
Writing 1024 bytes to 0x2a010000; 100478 bytes left.
Writing 1024 bytes to 0x2a010400; 99454 bytes left.
Writing 1024 bytes to 0x2a010800; 98430 bytes left.
Writing 1024 bytes to 0x2a010c00; 97406 bytes left.
Writing 1024 bytes to 0x2a011000; 96382 bytes left.
Writing 1024 bytes to 0x2a011400; 95358 bytes left.
Writing 1024 bytes to 0x2a011800; 94334 bytes left.
Writing 1024 bytes to 0x2a011c00; 93310 bytes left.
Writing 1024 bytes to 0x2a012000; 92286 bytes left.
Writing 1024 bytes to 0x2a012400; 91262 bytes left.
Writing 1024 bytes to 0x2a012800; 90238 bytes left.
Writing 1024 bytes to 0x2a012c00; 89214 bytes left.
Writing 1024 bytes to 0x2a013000; 88190 bytes left.
Writing 1024 bytes to 0x2a013400; 87166 bytes left.
Writing 1024 bytes to 0x2a013800; 86142 bytes left.
Writing 1024 bytes to 0x2a013c00; 85118 bytes left.
Writing 1024 bytes to 0x2a014000; 84094 bytes left.
Writing 1024 bytes to 0x2a014400; 83070 bytes left.
Writing 1024 bytes to 0x2a014800; 82046 bytes left.
Writing 1024 bytes to 0x2a014c00; 81022 bytes left.
Writing 1024 bytes to 0x2a015000; 79998 bytes left.
Writing 1024 bytes to 0x2a015400; 78974 bytes left.
Writing 1024 bytes to 0x2a015800; 77950 bytes left.
Writing 1024 bytes to 0x2a015c00; 76926 bytes left.
Writing 1024 bytes to 0x2a016000; 75902 bytes left.
Writing 1024 bytes to 0x2a016400; 74878 bytes left.
Writing 1024 bytes to 0x2a016800; 73854 bytes left.
Writing 1024 bytes to 0x2a016c00; 72830 bytes left.
Writing 1024 bytes to 0x2a017000; 71806 bytes left.
Writing 1024 bytes to 0x2a017400; 70782 bytes left.
Writing 1024 bytes to 0x2a017800; 69758 bytes left.
Writing 1024 bytes to 0x2a017c00; 68734 bytes left.
Writing 1024 bytes to 0x2a018000; 67710 bytes left.
Writing 1024 bytes to 0x2a018400; 66686 bytes left.
Writing 1024 bytes to 0x2a018800; 65662 bytes left.
Writing 1024 bytes to 0x2a018c00; 64638 bytes left.
Writing 1024 bytes to 0x2a019000; 63614 bytes left.
Writing 1024 bytes to 0x2a019400; 62590 bytes left.
Writing 1024 bytes to 0x2a019800; 61566 bytes left.
Writing 1024 bytes to 0x2a019c00; 60542 bytes left.
Writing 1024 bytes to 0x2a01a000; 59518 bytes left.
Writing 1024 bytes to 0x2a01a400; 58494 bytes left.
Writing 1024 bytes to 0x2a01a800; 57470 bytes left.
Writing 1024 bytes to 0x2a01ac00; 56446 bytes left.
Writing 1024 bytes to 0x2a01b000; 55422 bytes left.
Writing 1024 bytes to 0x2a01b400; 54398 bytes left.
Writing 1024 bytes to 0x2a01b800; 53374 bytes left.
Writing 1024 bytes to 0x2a01bc00; 52350 bytes left.
Writing 1024 bytes to 0x2a01c000; 51326 bytes left.
Writing 1024 bytes to 0x2a01c400; 50302 bytes left.
Writing 1024 bytes to 0x2a01c800; 49278 bytes left.
Writing 1024 bytes to 0x2a01cc00; 48254 bytes left.
Writing 1024 bytes to 0x2a01d000; 47230 bytes left.
Writing 1024 bytes to 0x2a01d400; 46206 bytes left.
Writing 1024 bytes to 0x2a01d800; 45182 bytes left.
Writing 1024 bytes to 0x2a01dc00; 44158 bytes left.
Writing 1024 bytes to 0x2a01e000; 43134 bytes left.
Writing 1024 bytes to 0x2a01e400; 42110 bytes left.
Writing 1024 bytes to 0x2a01e800; 41086 bytes left.
Writing 1024 bytes to 0x2a01ec00; 40062 bytes left.
Writing 1024 bytes to 0x2a01f000; 39038 bytes left.
Writing 1024 bytes to 0x2a01f400; 38014 bytes left.
Writing 1024 bytes to 0x2a01f800; 36990 bytes left.
Writing 1024 bytes to 0x2a01fc00; 35966 bytes left.
Writing 1024 bytes to 0x2a020000; 34942 bytes left.
Writing 1024 bytes to 0x2a020400; 33918 bytes left.
Writing 1024 bytes to 0x2a020800; 32894 bytes left.
Writing 1024 bytes to 0x2a020c00; 31870 bytes left.
Writing 1024 bytes to 0x2a021000; 30846 bytes left.
Writing 1024 bytes to 0x2a021400; 29822 bytes left.
Writing 1024 bytes to 0x2a021800; 28798 bytes left.
Writing 1024 bytes to 0x2a021c00; 27774 bytes left.
Writing 1024 bytes to 0x2a022000; 26750 bytes left.
Writing 1024 bytes to 0x2a022400; 25726 bytes left.
Writing 1024 bytes to 0x2a022800; 24702 bytes left.
Writing 1024 bytes to 0x2a022c00; 23678 bytes left.
Writing 1024 bytes to 0x2a023000; 22654 bytes left.
Writing 1024 bytes to 0x2a023400; 21630 bytes left.
Writing 1024 bytes to 0x2a023800; 20606 bytes left.
Writing 1024 bytes to 0x2a023c00; 19582 bytes left.
Writing 1024 bytes to 0x2a024000; 18558 bytes left.
Writing 1024 bytes to 0x2a024400; 17534 bytes left.
Writing 1024 bytes to 0x2a024800; 16510 bytes left.
Writing 1024 bytes to 0x2a024c00; 15486 bytes left.
Writing 1024 bytes to 0x2a025000; 14462 bytes left.
Writing 1024 bytes to 0x2a025400; 13438 bytes left.
Writing 1024 bytes to 0x2a025800; 12414 bytes left.
Writing 1024 bytes to 0x2a025c00; 11390 bytes left.
Writing 1024 bytes to 0x2a026000; 10366 bytes left.
Writing 1024 bytes to 0x2a026400; 9342 bytes left.
Writing 1024 bytes to 0x2a026800; 8318 bytes left.
Writing 1024 bytes to 0x2a026c00; 7294 bytes left.
Writing 1024 bytes to 0x2a027000; 6270 bytes left.
Writing 1024 bytes to 0x2a027400; 5246 bytes left.
Writing 1024 bytes to 0x2a027800; 4222 bytes left.
Writing 1024 bytes to 0x2a027c00; 3198 bytes left.
Writing 1024 bytes to 0x2a028000; 2174 bytes left.
Writing 1024 bytes to 0x2a028400; 1150 bytes left.
Writing 1024 bytes to 0x2a028800; 126 bytes left.
Writing 126 bytes to 0x2a028c00; 0 bytes left.
Executing file...
Failed to get response.
Sending MAGIC...
Invalid MAGIC response.
If HEX/MBN uploaded correctly, please wait a while and re-run unbrick.sh
to continue the unbricking session. A screen showing device options may appear;
close this new screen.
If there was any error, do NOT disconnect device (or else you might not
get it to connect anymore)! Try running script again.
"Invalid MAGIC response" - MBN was not flashed, the script needs an update.