[Tutorial] How to build a ROM?

[Tutorial] How to build a ROM? - XPERIA X8 General

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..

Related

[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

giefroot - rooting tool (CVE-2014-4322)

giefroot
A tool to root your device using CVE-2014-7911 (by Keen Team) and CVE-2014-4322 (by zxz0O0).
System rw access & SuperSU installation.
Requirements
USB debugging enabled
Settings => About phone => Click 7 times on Android Build to unlock developer options
Allow mock locations
Settings => Developer Settings
adb drivers installed
Firmware < October 2014 (kernel and system)
How to use
Download the tool (latest version) and extract it
Start your device and plug it to your computer
Put your device in air plane mode
Run install.bat and follow the instructions on screen
Congratulations! You should now be rooted. If you get an error "Device not rooted", try running the tool a second time.
Don't forget to make a donation
If you are not rooted, see post #3 for possible solutions!
What can you do next
Make a donation to the people involved
Backup TA partition / DRM keys
http://forum.xda-developers.com/showthread.php?t=2292598
Install dualrecovery by [NUT]
Download Z??-lockeddualrecovery2.X.XXX-BETA.installer.zip from http://nut.xperia-files.com/, run install.bat and select Option #1
Note if you have problems after installing recovery, this thread is not the place to ask for help!
Download v3.1
Thanks to
Big thanks to Keen Team for developing the CVE-2014-7911 exploit.
Original thread: http://forum.xda-developers.com/mate-7/general/wip-mate-7-root-bl-unlock-t2995086/post57991147
Code:
88 a8P 88888888888 88888888888 888b 88
88 ,88' 88 88 8888b 88
88 ,88" 88 88 88 `8b 88
88,d88' 88aaaaa 88aaaaa 88 `8b 88
8888"88, 88""""" 88""""" 88 `8b 88
88P Y8b 88 88 88 `8b 88
88 "88, 88 88 88 `8888
88 Y8b 88888888888 88888888888 88 `888
Huawei Ascend Mate 7 root utility
Present by Keen Team:
Liang Chen, flanker017 - CVE-2014-7911 exploit
idl3r - Kernel vulnerability and exploit
Special thanks to:
Yaron Lavi and Nadav Markus from Palo Alto Networks for "Mock Location" trick
Chainfire for SuperSU
KingRoot (www.kingroot.net) for testing devices
Tested on MT7-TL10 and MT7-CL00 China Domestic edition with B122 SP06 (2014/12/30)
May or may not work on international editions
Additionally, thanks to:
Chainfire: SuperSU developer
MohammadAG: Disable RIC kernel module (Link)
idler1984: Trick for stopping system_server
RHBH, squabbi, minijaws, Desperanto86: Testing & debugging
Changelog
v3.1
Add new device D6643 and D6616 (see here)
Small fixes
.
v3
Fixed a few bugs allocating memory
Add some new devices / firmwares for compatibility
.
v2
Fix phone rebooting before exploit completed (thanks idler1984!)
Fix error allocating memory for exploit code
.
v1
Initial release
XDA:DevDB Information
giefroot - rooting tool, Tool/Utility for the OEM Cross Device Development
Contributors
zxz0O0
Version Information
Status: Beta
Created 2015-01-24
Last Updated 2015-05-03

Reserved
Help: My device is not supported
The tool uses static kernel addresses. To support a device, I need the following information from someone with stock kernel (supported firmware) and root:
Code:
cat /proc/version
su
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms > /data/local/tmp/kallsyms
chmod 777 /data/local/tmp/kallsyms
Upload kallsyms and show output of version command.
Currently as in v1 only Z3 Compact and Z3 is supported.

Reserved
I have supported firmware / kernel but still not rooted!
Solution 1:
Run the tool a few times
Solution 2:
Put your phone into safe mode and run the tool. To get the device into safe mode:
pkobier said:
Hold power button and than hold "Turn off". You will see prompt message to reboot phone in safe mode.
Click to expand...
Click to collapse
Solution 3:
Try running the tool on another computer
No solution works:
To speed up the support process you can provide the following output / information:
Device model / firmware version
Kernel version (cat /proc/version)
adb shell "ls -l /data/local/tmp/"
adb shell "cat /data/local/tmp/giefrootlog"
adb shell "cat /proc/last_kmsg"

The wait worth a lot... Thanks man, you are awesome!

can i use it on D6603?

@zxz0O0 : I have done everything but at the end, it's say "Error: device not rooted"?

thienbrand said:
@zxz0O0 : I have done everything but at the end, it's say "Error: device not rooted"?
Click to expand...
Click to collapse
Post this information: http://forum.xda-developers.com/showpost.php?p=58391697&postcount=3
and output of install.bat

Nice

zxz0O0 said:
I have supported firmware / kernel but still not rooted!
To speed up the support process you can provide the following output / information:
Device model / firmware version
Kernel version (cat /proc/version)
adb shell "ls -l /data/local/tmp/"
adb shell "cat /data/local/tmp/giefrootlog"
Click to expand...
Click to collapse
Device model / firmware version : D6603 / 23.0.A.2.93 Generic Global
Kernel version (cat /proc/version): 3.4.0-perf-g0961 cdf [email protected] #1 Tue-Aug 19 19:48:36 2014
adb shell "ls -l /data/local/tmp/":
C:\adb>adb shell "ls -l /data/local/tmp/"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
-rw-rw-rw- shell shell 4016989 2015-01-24 06:00 SuperSU.zip
-rwxrwxrwx shell shell 152 2015-01-24 17:50 a
-rwxrwxrwx shell shell 657704 2014-02-07 06:39 busybox
-rw-r--r-- root root 30184 2014-07-15 15:10 flatland
-rwxrwxrwx shell shell 17892 2015-01-24 20:13 getroot
-rwxrwxrwx shell shell 143 2015-01-24 05:06 giefroot
-rwxrwxrwx system system 181 2015-01-24 20:31 giefrootlog
-rw------- u0_a33 u0_a33 3774 2015-01-24 20:39 glsl_shader_log.txt
-rwxrwxrwx shell shell 752 2015-01-24 09:08 installsupersu.sh
-rwxrwxrwx shell shell 60799 2015-01-07 12:40 main
-rwxrwxrwx shell shell 0 2015-01-24 20:38 memfile
-rwxrwxrwx shell shell 13592 2014-07-20 23:10 modulecrcpatch
-rwxrwxrwx shell shell 1544 2015-01-24 10:13 systemrw.sh
-rwxrwxrwx shell shell 34473 2014-07-10 05:02 wp_mod.ko
adb shell "cat /data/local/tmp/giefrootlog":
C:\adb>adb shell "cat /data/local/tmp/giefrootlog"
giefroot (c) zxz0O0
query failed. trying another app...
getting ptr
getting offset
Error: Could not allocate memory for exploit code
getting root...
getuid: 1000
Error getting root
output of bat:
==============================================
= =
= giefroot v1 =
= created by zxz0O0 =
= =
= Many thanks to: =
= - [NUT] =
= - MohammadAG =
= - Keen Team =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
Make sure that you authorize the connection
if you get any message on the phone
=============================================
Device found
=============================================
Sending files
=============================================
9 KB/s (152 bytes in 0.015s)
1118 KB/s (17892 bytes in 0.015s)
25 KB/s (143 bytes in 0.005s)
1899 KB/s (60799 bytes in 0.031s)
13 KB/s (13592 bytes in 1.000s)
1 KB/s (1544 bytes in 1.000s)
2144 KB/s (34473 bytes in 0.015s)
2666 KB/s (4016989 bytes in 1.471s)
2417 KB/s (657704 bytes in 0.265s)
0 KB/s (752 bytes in 1.000s)
2766 KB/s (44259 bytes in 0.015s)
pkg: /data/local/tmp/exploitServiceApp.apk
Success
=============================================
Running exploit
=============================================
Please wait 70 seconds to let the device reboot
Error: device not rooted
Press any key to continue . . .

Hey, after root, can i update my device to latest firmware?

Thank so much my friend...
My small contribution: 8TJ698456J713772F

No success on my device:
Edit: after second attempt it did work
D5803
23.0.A.2.93
Kernel
3.4.0-perf-g0961cdf
[email protected] #1
Tue Aug 19 19:48:36 2014
Output of install.bat:
Code:
==============================================
= =
= giefroot v1 =
= created by zxz0O0 =
= =
= Many thanks to: =
= - [NUT] =
= - MohammadAG =
= - Keen Team =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
Make sure that you authorize the connection
if you get any message on the phone
=============================================
Device found
=============================================
Sending files
=============================================
9 KB/s (152 bytes in 0.015s)
1109 KB/s (17892 bytes in 0.015s)
0 KB/s (143 bytes in 1.000s)
3799 KB/s (60799 bytes in 0.015s)
13 KB/s (13592 bytes in 1.000s)
96 KB/s (1544 bytes in 0.015s)
2154 KB/s (34473 bytes in 0.015s)
3985 KB/s (4016989 bytes in 0.984s)
4567 KB/s (657704 bytes in 0.140s)
0 KB/s (752 bytes in 1.000s)
2767 KB/s (44259 bytes in 0.015s)
pkg: /data/local/tmp/exploitServiceApp.apk
Success
=============================================
Running exploit
=============================================
Please wait 70 seconds to let the device reboot
Error: device not rooted
Press any key to continue . . .
Output of
adb shell "ls -l /data/local/tmp/"
Code:
-rw-rw-rw- shell shell 4016989 2015-01-24 00:00 SuperSU.zip
-rwxrwxrwx shell shell 152 2015-01-24 11:50 a
-rwxrwxrwx shell shell 657704 2014-02-07 00:39 busybox
-rwxrwxrwx shell shell 17892 2015-01-24 14:13 getroot
-rwxrwxrwx shell shell 143 2015-01-23 23:06 giefroot
-rwxrwxrwx shell shell 752 2015-01-24 03:08 installsupersu.sh
-rwxrwxrwx shell shell 60799 2015-01-07 06:40 main
-rwxrwxrwx shell shell 0 2015-01-24 14:37 memfile
-rwxrwxrwx shell shell 13592 2014-07-20 17:10 modulecrcpatch
-rwxrwxrwx shell shell 1544 2015-01-24 04:13 systemrw.sh
-rwxrwxrwx shell shell 34473 2014-07-09 23:02 wp_mod.ko
Output of
adb shell "cat /data/local/tmp/giefrootlog"
Code:
/system/bin/sh: cat: /data/local/tmp/giefrootlog: No such file or directory
Edit:
After the second time, it did work.
Here is the output of the install.bat after second attempt:
Code:
Done. You can now unplug your device.
Enjoy root
=============================================
What to do next?
- Donate to the people involved
- Install dualrecovery by [NUT]
- Backup TA partition
Press any key to continue . . .

It didn't worked with my device.
Device model / firmware version:
Code:
D6643 / 23.0.A.2.93
Kernel version (cat /proc/version):
Code:
[email protected]:/ $ cat /proc/version
cat /proc/version
Linux version 3.4.0-perf-g18c6f85 ([email protected]) (gcc version 4.7 (GCC) )
#1 SMP PREEMPT Thu Sep 11 12:05:53 2014
[email protected]:/ $
adb shell "ls -l /data/local/tmp/":
Code:
[email protected]:/ $ ls -l /data/local/tmp
ls -l /data/local/tmp
-rw-rw-rw- shell shell 4016989 2015-01-23 21:00 SuperSU.zip
-rwxrwxrwx shell shell 152 2015-01-24 08:50 a
-rwxrwxrwx shell shell 657704 2014-02-06 21:39 busybox
-rw-r--r-- root root 30184 2014-07-15 06:10 flatland
-rwxrwxrwx shell shell 17892 2015-01-24 11:13 getroot
-rwxrwxrwx shell shell 143 2015-01-23 20:06 giefroot
-rwxrwxrwx system system 0 2015-01-24 11:44 giefrootlog
-rw------- system graphics 2654 2015-01-24 11:45 glsl_shader_log.txt
-rwxrwxrwx shell shell 752 2015-01-24 00:08 installsupersu.sh
-rwxrwxrwx shell shell 60799 2015-01-07 03:40 main
-rwxrwxrwx shell shell 0 2015-01-24 11:43 memfile
-rwxrwxrwx shell shell 13592 2014-07-20 15:10 modulecrcpatch
-rwxrwxrwx shell shell 1544 2015-01-24 01:13 systemrw.sh
-rwxrwxrwx shell shell 34473 2014-07-09 21:02 wp_mod.ko
[email protected]:/ $
adb shell "cat /data/local/tmp/giefrootlog":
Code:
[email protected]:/ $ cat /data/local/tmp/giefrootlog
cat /data/local/tmp/giefrootlog
[email protected]:/ $
As far I saw the system escalation was successful, so the 1st exploit worked, the problem was achieving root with system user.

At first it didn't work, the batch would report "Error: device not rooted", but I suspect that's because I declined the Google pop up to perform app checks. After I rebooted and accepted, it worked just fine.
So thank you very much. I will be making a small contribution shortly.

I'm also getting the "device not rooted" error.
Model: D6603
Firmware: 23.0.A.2.93 (1282-2729_23.0.A.2.93 GENERIC - user)
Kernel: Linux version 3.4.0-perf-g0961cdf ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Aug 19 19:48:36 2014
/data/local/tmp/
Code:
-rw-rw-rw- shell shell 4016989 2015-01-24 00:00 SuperSU.zip
-rwxrwxrwx shell shell 152 2015-01-24 11:50 a
-rwxrwxrwx shell shell 657704 2014-02-07 00:39 busybox
-rwxrwxrwx shell shell 17892 2015-01-24 14:13 getroot
-rwxrwxrwx shell shell 143 2015-01-23 23:06 giefroot
-rw------- system graphics 11058 2015-01-24 14:53 glsl_shader_log.txt
-rwxrwxrwx shell shell 752 2015-01-24 03:08 installsupersu.sh
-rwxrwxrwx shell shell 60799 2015-01-07 06:40 main
-rwxrwxrwx shell shell 0 2015-01-24 14:52 memfile
-rwxrwxrwx shell shell 13592 2014-07-20 18:10 modulecrcpatch
-rwxrwxrwx shell shell 1544 2015-01-24 04:13 systemrw.sh
-rwxrwxrwx shell shell 34473 2014-07-10 00:02 wp_mod.ko
giefrootlog is not there.
install.bat output:
Code:
==============================================
= =
= giefroot v1 =
= created by zxz0O0 =
= =
= Many thanks to: =
= - [NUT] =
= - MohammadAG =
= - Keen Team =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
Make sure that you authorize the connection
if you get any message on the phone
=============================================
Device found
=============================================
Sending files
=============================================
0 KB/s (152 bytes in 1.000s)
1118 KB/s (17892 bytes in 0.015s)
0 KB/s (143 bytes in 1.000s)
3799 KB/s (60799 bytes in 0.015s)
13 KB/s (13592 bytes in 1.000s)
96 KB/s (1544 bytes in 0.015s)
2156 KB/s (34473 bytes in 0.015s)
3528 KB/s (4016989 bytes in 1.111s)
3957 KB/s (657704 bytes in 0.162s)
0 KB/s (752 bytes in 1.000s)
2770 KB/s (44259 bytes in 0.015s)
pkg: /data/local/tmp/exploitServiceApp.apk
Success
=============================================
Running exploit
=============================================
Please wait 70 seconds to let the device reboot
Error: device not rooted
Press any key to continue . . .

RHBH said:
It didn't worked with my device.
[..]
Click to expand...
Click to collapse
Please pm me your gmail address for google hangout.
H117 said:
At first it didn't work, the batch would report "Error: device not rooted", but I suspect that's because I declined the Google pop up to perform app checks. After I rebooted and accepted, it worked just fine.
So thank you very much. I will be making a small contribution shortly.
Click to expand...
Click to collapse
Thanks for confirming. What is your device / version? So we can collect which are working.

H117 said:
At first it didn't work, the batch would report "Error: device not rooted", but I suspect that's because I declined the Google pop up to perform app checks. After I rebooted and accepted, it worked just fine.
So thank you very much. I will be making a small contribution shortly.
Click to expand...
Click to collapse
Also had problem at first to get root , didnt even see the popup but on my 5th try i did see it and all went fine . So people give it a few tries .
D5803 running 23.0.A.2.93

zxz0O0 said:
Please pm me your gmail address for google hangout.
Thanks for confirming. What is your device / version? So we can collect which are working.
Click to expand...
Click to collapse
Sure.
Device model / firmware version - D5803/23.0.A.2.93
Kernel version - 3.4.0-perf-g0961cdf

zxz0O0 said:
Please pm me your gmail address for google hangout.
Thanks for confirming. What is your device / version? So we can collect which are working.
Click to expand...
Click to collapse
D5803
23.0.A.2.93
Kernel
3.4.0-perf-g0961cdf
First time: exact same output as @darwusch, did not get the SU prompt after reboot
Second time: This time i waited for the command window to connect my phone, and i waited a bit after reboot before touching the phone. After unluck i got SU prompt , confirmed it and i got root.
Thanks for all!!

thienbrand said:
Device model / firmware version : D6603 / 23.0.A.2.93 Generic Global
Kernel version (cat /proc/version): 3.4.0-perf-g0961 cdf [email protected] #1 Tue-Aug 19 19:48:36 2014
adb shell "ls -l /data/local/tmp/":
C:\adb>adb shell "ls -l /data/local/tmp/"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
-rw-rw-rw- shell shell 4016989 2015-01-24 06:00 SuperSU.zip
-rwxrwxrwx shell shell 152 2015-01-24 17:50 a
-rwxrwxrwx shell shell 657704 2014-02-07 06:39 busybox
-rw-r--r-- root root 30184 2014-07-15 15:10 flatland
-rwxrwxrwx shell shell 17892 2015-01-24 20:13 getroot
-rwxrwxrwx shell shell 143 2015-01-24 05:06 giefroot
-rwxrwxrwx system system 181 2015-01-24 20:31 giefrootlog
-rw------- u0_a33 u0_a33 3774 2015-01-24 20:39 glsl_shader_log.txt
-rwxrwxrwx shell shell 752 2015-01-24 09:08 installsupersu.sh
-rwxrwxrwx shell shell 60799 2015-01-07 12:40 main
-rwxrwxrwx shell shell 0 2015-01-24 20:38 memfile
-rwxrwxrwx shell shell 13592 2014-07-20 23:10 modulecrcpatch
-rwxrwxrwx shell shell 1544 2015-01-24 10:13 systemrw.sh
-rwxrwxrwx shell shell 34473 2014-07-10 05:02 wp_mod.ko
adb shell "cat /data/local/tmp/giefrootlog":
C:\adb>adb shell "cat /data/local/tmp/giefrootlog"
giefroot (c) zxz0O0
query failed. trying another app...
getting ptr
getting offset
Error: Could not allocate memory for exploit code
getting root...
getuid: 1000
Error getting root
output of bat:
==============================================
= =
= giefroot v1 =
= created by zxz0O0 =
= =
= Many thanks to: =
= - [NUT] =
= - MohammadAG =
= - Keen Team =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
Make sure that you authorize the connection
if you get any message on the phone
=============================================
Device found
=============================================
Sending files
=============================================
9 KB/s (152 bytes in 0.015s)
1118 KB/s (17892 bytes in 0.015s)
25 KB/s (143 bytes in 0.005s)
1899 KB/s (60799 bytes in 0.031s)
13 KB/s (13592 bytes in 1.000s)
1 KB/s (1544 bytes in 1.000s)
2144 KB/s (34473 bytes in 0.015s)
2666 KB/s (4016989 bytes in 1.471s)
2417 KB/s (657704 bytes in 0.265s)
0 KB/s (752 bytes in 1.000s)
2766 KB/s (44259 bytes in 0.015s)
pkg: /data/local/tmp/exploitServiceApp.apk
Success
=============================================
Running exploit
=============================================
Please wait 70 seconds to let the device reboot
Error: device not rooted
Press any key to continue . . .
Click to expand...
Click to collapse
Have EXACTLY the same, except i'm on .98 fw. Will try in about 30 minutes.
atm: Z, Z3, Arc S, Play, S3, S3 Mini

[ROOT][Z-Z3] How to root 5.0 Lollipop with rootkitXperia

rootkitXperia is back again!
A Japanese developer, @cubeundcube made it possible to root some Android 5.0 Lollipop firmware directly (not 5.1 and 64bit devices, sadly...).
With new rootkitXperia, you don't need to roll back to KitKat when you lose root on locked bootloader!
Download
Download (only for M4 Aqua Dual E2363 *)
Download (for M4 Aqua E2303 **)
Supported device/version
Z2/Z3 variant
23.2.A.1.62
23.1.A.1.28
17.1.1.B.3.240 or .245 *Japanese model
23.0.B.1.38 *Japanese model
23.0.B.1.59 *Japanese model
23.0.C.0.350 *Japanese model
23.0.H.0.334 *Japanese model
Z1 variant
14.5.A.0.270
14.3.B.0.310 *Japanese model
Z variant
10.6.A.0.454
M4 Aqua Dual E2363 *
26.1.B.1.85
M4 Aqua E2303 **
26.1.A.1.128
* You can see some 5.1 firmwares in "support.txt", but "封鎖" means "blocked/patched", so they are not supported.
How to use rootkitXperia
1. Install adb driver for your device
2. Go to Settings > Developer options and tick USB debugging
3. Go to Settings > Security and tick Unknown sources
4. Connect your phone to your computer
5. Extract rootkitXperia_20150926.zip and run install.bat
6. When you see "— all finished —" in console, rooting is done.
NOTE: rootkitXperia won't install recovery or kill ric,
so you have to install XZDualRecovery.
Donate link for cubeundcube is here.
If you want to thank him, his first post for dev threads is here

The support file inside the tool says that support also 5.1.1 firmware at least the one for z1. Good thats a nice very nice news. Thanks

Here's the thing pulled through Google Translate:
■ domestic version
Z1 system: 14.3.B.0.310 previous
Z2 system: 17.1.1.B.3.240 (245) previous
Z3 system: 23.0.B.1.38 previous
■ Z2 & Z3 system (Overseas Version)
23.4.A.0.546 blockade
23.2.A.1.62 OK
23.1.A.1.28 OK
■ Z1 system (Overseas Version)
14.6.A.0.368 blockade
14.5.A.0.283 blockade
14.5.A.0.270 OK
■ Z system (Overseas Version)
10.7.A.0.222 blockade
10.6.A.0.454 OK
Click to expand...
Click to collapse
Domestic version means the Japanese versions. Probably.

I added Japanese models to the list.
You can see some 5.1 firmwares in "support.txt", but "封鎖" means "blocked/patched", so they are not supported.
[UPDATE]
Added C4, M4 Aqua and C5 Ultra

Awesome bro!!! but seems lost ADB Driver in the Folders ?

timlu85 said:
Awesome bro!!! but seems lost ADB Driver in the Folders ?
Click to expand...
Click to collapse
You have to set up by yourself.
It's really easy and you don't need to do again.

timlu85 said:
Awesome bro!!! but seems lost ADB Driver in the Folders ?
Click to expand...
Click to collapse
You can copy paste from wherever tool using adb like dualrecovery installer or kamome tool. Cheers
Enviado desde mi C6903 mediante Tapatalk

Too bad it's not working with z4 5.02 build .......

ibis69 said:
Too bad it's not working with z4 5.02 build .......
Click to expand...
Click to collapse
Yes all Z3+/Z4 firmwares are already patched before release.
Sony is so fast to patch exploits...

AndroPlus said:
rootkitXperia is back again!
Click to expand...
Click to collapse
Not working on C5Ultra

freddy1991 said:
Not working on C5Ultra
Click to expand...
Click to collapse
What version?

AndroPlus said:
What version?
Click to expand...
Click to collapse
The same build number you mentioned at op
The phone rebooted once and when it booted up, the terminal window said " removing temporary files" and "finished. Press any key to continue "..

freddy1991 said:
The same build number you mentioned at op
The phone rebooted once and when it booted up, the terminal window said " removing temporary files" and "finished. Press any key to continue "..
Click to expand...
Click to collapse
And no SuperSU?
If so I'll remove C5 Ultra from the list...

AndroPlus said:
And no SuperSU?
If so I'll remove C5 Ultra from the list...
Click to expand...
Click to collapse
Yes. There's no SuperSU.
Also not working for M4 Aqua Dual but my M4 has a higher build number than the one at OP.

I got error when rooting C5 Ultra Dual
--- Xperia rootkit 2015/09/26 ---
waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
783 KB/s (13640 bytes in 0.017s)
4906 KB/s (75364 bytes in 0.015s)
4878 KB/s (29972 bytes in 0.006s)
7227 KB/s (170232 bytes in 0.023s)
7678 KB/s (5904943 bytes in 0.751s)
7755 KB/s (1048328 bytes in 0.132s)
28 KB/s (58 bytes in 0.002s)
26 KB/s (55 bytes in 0.002s)
307 KB/s (629 bytes in 0.002s)
5051 KB/s (25863 bytes in 0.005s)
4424 KB/s (13592 bytes in 0.003s)
58 KB/s (60 bytes in 0.001s)
2572 KB/s (5268 bytes in 0.002s)
getroot start.
ro.build.product=arima6752_lwt_s_l
ro.build.id=29.0.B.0.161
ro.build.version.release=5.0
max_fds=4096
Creating target socket...OK.
3072 sockets created.
waiting for device...
error: protocol fault (no status)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
error:
removing temporary files...
adb server is out of date. killing...
* daemon started successfully *
rm: /data/local/tmp/getroot: No such file or directory
rm: /data/local/tmp/supolicy: No such file or directory
rm: /data/local/tmp/libsupol.so: No such file or directory
rm: /data/local/tmp/busybox: No such file or directory
rm: /data/local/tmp/00stop_ric: No such file or directory
rm: /data/local/tmp/99SuperSUDaemon: No such file or directory
rm: /data/local/tmp/install-recovery.sh: No such file or directory
rm: /data/local/tmp/ric_disabler_mod.ko: No such file or directory
rm: /data/local/tmp/copymodulecrc: No such file or directory
rm: /data/local/tmp/saferic: No such file or directory
rm: /data/local/tmp/install_tool.sh: No such file or directory
--- all finished ---
請按任意鍵繼續 . . .
Click to expand...
Click to collapse

beenoliu said:
I got error when rooting C5 Ultra Dual
Click to expand...
Click to collapse
Please try again after run this command:
adb kill-server
adb start-server
If it fails, C5 Ultra is not really supported.

AndroPlus said:
Please try again after run this command:
adb kill-server
adb start-server
If it fails, C5 Ultra is not really supported.
Click to expand...
Click to collapse
Got same error
Hope can fix soon

I have a M4 Auqa Dual (E2363), tried with both 26.1.B.2.102 and 26.1.B.2.129, there is no older firmware of this phone and it does not work.
the phone reboots and says all finished, but there is no SU loaded, and root is not there.
HTML:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\windows\system32>cd C:\Android\sdk\platform-tools
C:\Android\sdk\platform-tools>install.bat
--- Xperia rootkit 2015/09/26 ---
waiting for device...
307 KB/s (13640 bytes in 0.043s)
4089 KB/s (75364 bytes in 0.017s)
3644 KB/s (29972 bytes in 0.008s)
4147 KB/s (170232 bytes in 0.040s)
4590 KB/s (5904943 bytes in 1.256s)
3390 KB/s (1048328 bytes in 0.301s)
27 KB/s (58 bytes in 0.002s)
17 KB/s (55 bytes in 0.003s)
307 KB/s (629 bytes in 0.001s)
4205 KB/s (25863 bytes in 0.006s)
1203 KB/s (13592 bytes in 0.011s)
29 KB/s (60 bytes in 0.002s)
1725 KB/s (5268 bytes in 0.002s)
getroot start.
ro.build.product=E2363
ro.build.id=26.1.B.2.102
ro.build.version.release=5.0
max_fds=4096
Creating target socket...OK.
3072 sockets created.
waiting for device...
removing temporary files...
--- all finished ---
Press any key to continue . . .
C:\Android\sdk\platform-tools>

M4 Aqua E2303
not working @ both 2.99 and 1.28 firmwares

AndroPlus said:
Yes all Z3+/Z4 firmwares are already patched before release.
Sony is so fast to patch exploits...
Click to expand...
Click to collapse
unlike with the updates

Logcat/Recowvery issue

I've done it before but it seems like it's just not giving in this time. I had the phone rooted before and had to unroot for what I thought was going to be an insurance claim through my work (T-Mobile) and ended up just having some friends replace the screen for me. I went back to root the device again and still had all the same original files that I used to originally root and even locked and unlocked the bootloader again hoping that would fix my issue but I'm still getting hung at the logcat -s recowvery command. It shows <------- Beginning of system> <-------- Beginning of main> and just hangs and does nothing else.
text posted of every command I used to the exact instructions on @jcadduono post on how to root the h918
can't post screenshots because of new member.
Code:
C:\Users\Mike\Desktop\mini tools>adb devices
List of devices attached
LGH9185c391d6e device
C:\Users\Mike\Desktop\mini tools>adb push dirtycow /data/local/tmp
dirtycow: 1 file pushed. 0.3 MB/s (9984 bytes in 0.030s)
C:\Users\Mike\Desktop\mini tools>adb push recowvery-applypatch /data/local/tmp
recowvery-applypatch: 1 file pushed. 1.7 MB/s (18472 bytes in 0.011s)
C:\Users\Mike\Desktop\mini tools>adb push recowvery-app_process64 /data/local/tmp
recowvery-app_process64: 1 file pushed. 1.0 MB/s (10200 bytes in 0.010s)
C:\Users\Mike\Desktop\mini tools>adbpush recowvery-run-as /data/local/tmp
'adbpush' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Mike\Desktop\mini tools>adb push recowvery-run-as /data/local/tmp
recowvery-run-as: 1 file pushed. 0.9 MB/s (10192 bytes in 0.011s)
C:\Users\Mike\Desktop\mini tools>adb shell
elsa:/ $ cd /data/local/tmp
elsa:/data/local/tmp $ chmod 0777 *
/dirtycow /system/bin/applypatch recowvery-applypatch <
warning: new file size (18472) and file old size (165144) differ
size 165144
[*] mmap 0x7e70077000
[*] exploit (patch)
[*] currently 0x7e70077000=10102464c457f
[*] madvise = 0x7e70077000 165144
[*] madvise = 0 1048576
[*] /proc/self/mem 1367343104 1048576
[*] exploited 0x7e70077000=10102464c457f
./dirtycow /system/bin/app_process64 recowvery-app_process64 <
warning: new file size (10200) and file old size (18600) differ
size 18600
[*] mmap 0x7ddae0d000
[*] exploit (patch)
[*] currently 0x7ddae0d000=10102464c457f
[*] madvise = 0x7ddae0d000 18600
[*] madvise = 0 1048576
[*] /proc/self/mem -1971322880 1048576
[*] exploited 0x7ddae0d000=10102464c457f
elsa:/data/local/tmp $ exit
C:\Users\Mike\Desktop\mini tools>adb logcat -s recowvery
--------- beginning of system
--------- beginning of main

how to fix lgh918 recowvery issue
OfficialVillager said:
I've done it before but it seems like it's just not giving in this time. I had the phone rooted before and had to unroot for what I thought was going to be an insurance claim through my work (T-Mobile) and ended up just having some friends replace the screen for me. I went back to root the device again and still had all the same original files that I used to originally root and even locked and unlocked the bootloader again hoping that would fix my issue but I'm still getting hung at the logcat -s recowvery command. It shows <------- Beginning of system> <-------- Beginning of main> and just hangs and does nothing else.
text posted of every command I used to the exact instructions on @jcadduono post on how to root the h918
can't post screenshots because of new member.
Code:
C:\Users\Mike\Desktop\mini tools>adb devices
List of devices attached
LGH9185c391d6e device
C:\Users\Mike\Desktop\mini tools>adb push dirtycow /data/local/tmp
dirtycow: 1 file pushed. 0.3 MB/s (9984 bytes in 0.030s)
C:\Users\Mike\Desktop\mini tools>adb push recowvery-applypatch /data/local/tmp
recowvery-applypatch: 1 file pushed. 1.7 MB/s (18472 bytes in 0.011s)
C:\Users\Mike\Desktop\mini tools>adb push recowvery-app_process64 /data/local/tmp
recowvery-app_process64: 1 file pushed. 1.0 MB/s (10200 bytes in 0.010s)
C:\Users\Mike\Desktop\mini tools>adbpush recowvery-run-as /data/local/tmp
'adbpush' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Mike\Desktop\mini tools>adb push recowvery-run-as /data/local/tmp
recowvery-run-as: 1 file pushed. 0.9 MB/s (10192 bytes in 0.011s)
C:\Users\Mike\Desktop\mini tools>adb shell
elsa:/ $ cd /data/local/tmp
elsa:/data/local/tmp $ chmod 0777 *
/dirtycow /system/bin/applypatch recowvery-applypatch <
warning: new file size (18472) and file old size (165144) differ
size 165144
[*] mmap 0x7e70077000
[*] exploit (patch)
[*] currently 0x7e70077000=10102464c457f
[*] madvise = 0x7e70077000 165144
[*] madvise = 0 1048576
[*] /proc/self/mem 1367343104 1048576
[*] exploited 0x7e70077000=10102464c457f
./dirtycow /system/bin/app_process64 recowvery-app_process64 <
warning: new file size (10200) and file old size (18600) differ
size 18600
[*] mmap 0x7ddae0d000
[*] exploit (patch)
[*] currently 0x7ddae0d000=10102464c457f
[*] madvise = 0x7ddae0d000 18600
[*] madvise = 0 1048576
[*] /proc/self/mem -1971322880 1048576
[*] exploited 0x7ddae0d000=10102464c457f
elsa:/data/local/tmp $ exit
C:\Users\Mike\Desktop\mini tools>adb logcat -s recowvery
--------- beginning of system
--------- beginning of main
Click to expand...
Click to collapse
this is exzactly what happened to me any ideas how to correct it?

I recommend getting the stock kdz and flashing it to get you back to a true stock state. Don't use any kdz after 10j.
Who knows what was left behind when you unrooted. Unrooting doesn't return you to stock. It just unrooted you.
Once on a true stock system, recowvey should work.

androiddiego said:
I recommend getting the stock kdz and flashing it to get you back to a true stock state. Don't use any kdz after 10j.
Who knows what was left behind when you unrooted. Unrooting doesn't return you to stock. It just unrooted you.
Once on a true stock system, recowvey should work.
Click to expand...
Click to collapse
Unfortunately, that won't be the case on 10q or 10r. According to @runningnak3d, they've not only locked down qualcomm processors, but have also basically removed fastboot. There isn't any way to root beyond that update. not yet at least. and with antirollback being enabled now, no way to downgrade. We're stuck in a rut.

OfficialVillager said:
Unfortunately, that won't be the case on 10q or 10r. According to @runningnak3d, they've not only locked down qualcomm processors, but have also basically removed fastboot. There isn't any way to root beyond that update. not yet at least. and with antirollback being enabled now, no way to downgrade. We're stuck in a rut.
Click to expand...
Click to collapse
What firmware is the phone currently on?

androiddiego said:
What firmware is the phone currently on?
Click to expand...
Click to collapse
You'd have to check the about settings of your phone to know what you're on. The most recent is 10r. Im on 10q.

OfficialVillager said:
You'd have to check the about settings of your phone to know what you're on. The most recent is 10r. Im on 10q.
Click to expand...
Click to collapse
You're on 10q. That's why recowvery won't work. It work on 10j and below.

OfficialVillager said:
You'd have to check the about settings of your phone to know what you're on. The most recent is 10r. Im on 10q.
Click to expand...
Click to collapse
Sorry bud you can't root and if you try to go back to a rootable version you'll brick. This is even if you got there through a TWRP flashable zip, since they still update everything except recovery.

Try running logcat -s recowvery directly in an adb shell on the target device.

LG V20 9008 Error

I screwed up my V20.
Now the only thing the device manager sees is Qualcomm HS-USB QDLoader 9008.
Anybody know a fix?

bump
---------- Post added at 07:58 PM ---------- Previous post was at 07:52 PM ----------
looks like we just need board diag settings for the lg boardiag tool here https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868

For now, only LG can fix that. If your phone is still under warranty with your carrier, or with LG -- send it back. When I was starting off with the V20 before I understood that they used UFS memory now, and had updated protected boot, I bricked one phone twice, and another on purpose (to test something), and LG fixed both phones all three times.
-- Brian

Yeah. I ended up shipping it to them.
Already had an overheating issue so they didn't even check to see what was going on. They just replaced the mobo.
Thank you for the reply though.

Do you mind me asking what you did to get the 9008?
-- Brian

No not at all.
Let's see...If I remember right I was flashing firmware in LG UP and LG UP froze the device. And without thinking about it I pulled the battery and caused it not to install anything.
I have a H910 variant so there was no KDZ for it. So I had flashed the H910PR originally and it worked but I wanted root back so I was trying to flash I think either the H915 or H918. Pretty sure H915 KDZ.

H915 flashes fine on the H910 (only way to root it now). The H918 uses a different RSA key, so if you flash any other model's KDZ onto the H918, or the H918 KDZ onto any other model, it will have the wrong RSA key, and go into 9008 mode.
The other possibility, is that depending on which H910PR KDZ you flashed, it may have incremented the ARB (anti-rollback) version. If you then flashed the H915 KDZ, it may have had a lower ARB. If you flash firmware that has a lower ARB than what is on your phone, it also goes into 9008 mode.
-- Brian

Huh. Thank for that info.
Speaking of that I saw your H910M root and it worked but I ran into issues with LineageOS so I ended up forced to go back to stock and in doing so had to update to the SW:H91010p. Build:NRD90M.
I still have the dump from the root process though.
ARB is 0 you think I could flash it back to the H910M?

Yep! You can flash any firmware for a given model as long as the ARB is the same version or greater. ARB gets burned into QFPROM the first time XBL loads. So if you flash firmware that has a greater ARB, and your phone boots, you are now stuck on that ARB version. The H910 is ARB 0 for 10p, so you are fine flashing 10m.
-- Brian

Awesome. I'm doing a dumb just in case something goes awry.
Thank you.

runningnak3d said:
Do you mind me asking what you did to get the 9008?
-- Brian
Click to expand...
Click to collapse
I was shipping mine to them for a couple other issues, and was rooted with TWRP running the latest firmware on H918. I wanted to flash stock firmware to undo the root and TWRP so they wouldn't know it had been modified, but I also wanted to put it on an earlier firmware so I could root it again when I got it back, I was gonna tell them not to update the FW. Long story short I guess anti roll back was tripped despite the root and TWRP so LGUP wouldnt flash older firmware. I thought I'd be slick and flash the bootloader to an older one from twrp and see if LGUP would flash it then. Nope. Total brick. This is the first time I have ever full on bricked a device in over 10 years of modifying phones starting with windows mobile.

kdz extract for linux sd card write done
command link https://mega.nz/#!cJ9WUAiA!TSt9L5G3C...n8vx0pQ9ToxCFw
https://forum.xda-developers.com/g4/...-qfil-t3748946
[[email protected] ~]$ sudo dmesg -c >> /dev/null
[sudo] password for android:
[[email protected] ~]$ dmesg
[13324.923241] usb 1-2: new full-speed USB device number 11 using ohci-pci
[13325.594494] usb 1-2: config 1 interface 0 altsetting 0 endpoint 0x81 has invalid maxpacket 512, setting to 64
[13325.594499] usb 1-2: config 1 interface 0 altsetting 0 endpoint 0x2 has invalid maxpacket 512, setting to 64
[13325.618041] usb-storage 1-2:1.0: USB Mass Storage device detected
[13325.634811] scsi host3: usb-storage 1-2:1.0
[13326.672238] scsi 3:0:0:0: Direct-Access Mass Storage Device 1.00 PQ: 0 ANSI: 0 CCS
[13326.695215] sd 3:0:0:0: [sdb] 61857792 512-byte logical blocks: (31.7 GB/29.5 GiB)
[13326.707634] sd 3:0:0:0: [sdb] Write Protect is off
[13326.707636] sd 3:0:0:0: [sdb] Mode Sense: 03 00 00 00
[13326.722615] sd 3:0:0:0: [sdb] No Caching mode page found
[13326.722617] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[13326.802629] sdb: sdb1
[13326.859174] sd 3:0:0:0: [sdb] Attached SCSI removable disk
[[email protected] ~]$ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 29.5 GiB, 31671189504 bytes, 61857792 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 8192 61857791 61849600 29.5G c W95 FAT32 (LBA)
[[email protected] ~]$ cd /home/android/21y/
[[email protected] 21y]$ sudo -s
[fwul 21y]# dd if=PrimaryGPT.bin of=/dev/sdb
32768+0 records in
32768+0 records out
16777216 bytes (17 MB, 16 MiB) copied, 43.9727 s, 382 kB/s
[fwul 21y]# sync
[fwul 21y]# ls -la /dev/disk/by-partlabel/sbl1
lrwxrwxrwx 1 root root 10 May 3 09:17 /dev/disk/by-partlabel/sbl1 -> ../../sdb3
[fwul 21y]# cd /home/android/21y/
[fwul 21y]# sudo -s
[fwul 21y]# 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=factory.bin of=/dev/disk/by-partlabel/factory
dd if=felica.bin of=/dev/disk/by-partlabel/felica
dd if=hypbak.bin of=/dev/disk/by-partlabel/hypbak
dd if=hyp.bin of=/dev/disk/by-partlabel/hyp
dd if=laf.bin of=/dev/disk/by-partlabel/laf
dd if=modem.bin of=/dev/disk/by-partlabel/modem
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=recovery.bin of=/dev/disk/by-partlabel/recovery
dd if=rpmbak.bin of=/dev/disk/by-partlabel/rpmbak
dd if=rpm.bin of=/dev/disk/by-partlabel/rpm
dd if=sbl1bak.bin of=/dev/disk/by-partlabel/sbl1bak
dd if=sbl1.bin of=/dev/disk/by-partlabel/sbl1
dd if=sdibak.bin of=/dev/disk/by-partlabel/sdibak
dd if=sdi.bin of=/dev/disk/by-partlabel/sdi
dd if=sec.bin of=/dev/disk/by-partlabel/sec
dd if=system_691200.bin of=/dev/disk/by-partlabel/system_691200
dd if=tzbak.bin of=/dev/disk/by-partlabel/tzbak
dd if=tz.bin of=/dev/disk/by-partlabel/tz
[fwul 21y]# 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, 4.99972 s, 419 kB/s
4096+0 records in
4096+0 records out
2097152 bytes (2.1 MB, 2.0 MiB) copied, 5.16635 s, 406 kB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 1.42203 s, 369 kB/s
81920+0 records in
81920+0 records out
41943040 bytes (42 MB, 40 MiB) copied, 136.39 s, 308 kB/s
94208+0 records in
94208+0 records out
48234496 bytes (48 MB, 46 MiB) copied, 118.618 s, 407 kB/s
16384+0 records in
16384+0 records out
8388608 bytes (8.4 MB, 8.0 MiB) copied, 20.8579 s, 402 kB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 1.41575 s, 370 kB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 1.36919 s, 383 kB/s
98304+0 records in
98304+0 records out
50331648 bytes (50 MB, 48 MiB) copied, 121.167 s, 415 kB/s
176128+0 records in
176128+0 records out
90177536 bytes (90 MB, 86 MiB) copied, 219.763 s, 410 kB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 1.57476 s, 333 kB/s
65536+0 records in
65536+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 82.7691 s, 405 kB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 1.48758 s, 352 kB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 1.36699 s, 384 kB/s
8192+0 records in
8192+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 10.0502 s, 417 kB/s
8192+0 records in
8192+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 10.0968 s, 415 kB/s
81920+0 records in
81920+0 records out
41943040 bytes (42 MB, 40 MiB) copied, 103.158 s, 407 kB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 1.43053 s, 366 kB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 1.37484 s, 381 kB/s
2048+0 records in
2048+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 2.61353 s, 401 kB/s
2048+0 records in
2048+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 2.616 s, 401 kB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 1.38069 s, 380 kB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 1.35592 s, 387 kB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 1.37754 s, 381 kB/s
884736+0 records in
884736+0 records out
452984832 bytes (453 MB, 432 MiB) copied, 26.0372 s, 17.4 MB/s
2048+0 records in
2048+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 2.63721 s, 398 kB/s
2048+0 records in
2048+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 2.6402 s, 397 kB/s
[fwul 21y]#

aaya888 said:
kdz extract for linux sd card write done
command link https://mega.nz/#!cJ9WUAiA!TSt9L5G3C...n8vx0pQ9ToxCFw
https://forum.xda-developers.com/g4/...-qfil-t3748946
[[email protected] ~]$ sudo dmesg -c >> /dev/null
[sudo] password for android:
[[email protected] ~]$ dmesg
[13324.923241] usb 1-2: new full-speed USB device number 11 using ohci-pci
Why are you posting this in multiple threads?, zip it up and upload it somewhere, no one wants to scroll through that crap
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse

@aaya888 Dude, that is for creating a bootable SD card for the G4. The G4 uses eMMC NAND. It is NOT possible to create a bootable SD card for a phone that uses UFS NAND (like the G5, V20, G6, V30, G7).
Let me rephrase that. It is not possible without a firehose. With a firehose, you can change the bootpath to /dev/block/mmcblk0. However, if you have a firehose, then you don't need a bootable SD card to unbrick your phone.
-- Brian

runningnak3d said:
@aaya888 Dude, that is for creating a bootable SD card for the G4. The G4 uses eMMC NAND. It is NOT possible to create a bootable SD card for a phone that uses UFS NAND (like the G5, V20, G6, V30, G7).
Let me rephrase that. It is not possible without a firehose. With a firehose, you can change the bootpath to /dev/block/mmcblk0. However, if you have a firehose, then you don't need a bootable SD card to unbrick your phone.
-- Brian
Click to expand...
Click to collapse
https://mega.nz/#!UJk1HYRQ!SMufYIICHn1mC5UuzGJafKPVc4_IiV-Bf8Xp8T6oD-M
[email protected]:~/Downloads$ cd kdz
[email protected]:~/Downloads/kdz$ ls
abootbak.bin eksst.bin mksdcard recovery.bin
aboot.bin encrypt.bin modem.bin reserve.bin
apdp.bin factory.bin modemst1.bin rpmbak.bin
boot.bin fota.bin modemst2.bin rpm.bin
cdt.bin fsc.bin mpt.bin sd.img
cmnlib64bak.bin fsg.bin msadp.bin sec.bin
cmnlib64.bin hypbak.bin -o sns.bin
cmnlibbak.bin hyp.bin op.bin spare1.bin
cmnlib.bin -i partitions.txt spare2.bin
ddr.bin keymasterbak.bin persist.bin system.bin
devcfgbak.bin keymaster.bin pmicbak.elf tzbak.bin
devcfg.bin keystore.bin pmic.elf tz.bin
devinfo.bin lafbak.bin raw_resourcesbak.bin xbl2bak.elf
dip.bin laf.bin raw_resources.bin xbl2.elf
dpo.bin misc.bin rct.bin xblbak.elf
drm.bin mkgpt recoverybak.bin xbl.elf
[email protected]:~/Downloads/kdz$ sudo ./mksdcard -g -o f800l.img -p partitions.txt -i lk_sdrescue/build-msm8996 -i bootloaders-sdboot
[sudo] password for aaya:
=== Entry: name: laf, size: 49152, align: , type: 98523EC6-90FE-4C67-B50A-0FC59ED6F56D, format: , file: laf.bin
=== Entry: name: mpt, size: 49152, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: mpt.bin
=== Entry: name: drm, size: 12288, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: drm.bin
=== Entry: name: sns, size: 8192, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: sns.bin
=== Entry: name: misc, size: 49152, align: , type: 82ACC91F-357C-4A68-9C8F-689E1B1A23A1, format: , file: misc.bin
=== Entry: name: factory, size: 16384, align: , type: 20117F86-E985-4357-B9EE-374BC1D8487D, format: , file: factory.bin
=== Entry: name: encrypt, size: 1024, align: , type: 323EF595-AF7A-4AFA-8060-97BE72841BB9, format: , file: encrypt.bin
=== Entry: name: eksst, size: 1024, align: , type: 45864011-CF89-46E6-A445-85262E065604, format: , file: eksst.bin
=== Entry: name: rct, size: 64, align: , type: 8ED8AE95-597F-4C8A-A5BD-A7FF8E4DFAA9, format: , file: rct.bin
=== Entry: name: ssd, size: 1024, align: , type: 2C86E742-745E-4FDD-BFD8-B6A7AC638772, format: , file: ssd.bin
=== Entry: name: keystore, size: 1024, align: , type: DE7D4029-0F5B-41C8-AE7E-F6C023A02B33, format: , file: keystore.bin
=== Entry: name: persist, size: 32768, align: , type: 6C95E238-E343-4BA8-B489-8681ED22AD0B, format: , file: persist.bin
=== Entry: name: lafbak, size: 49152, align: , type: E0B10BE8-8B5F-46D0-BC9A-A629CC3E063D, format: , file: laf.bin
=== Entry: name: system, size: 1024, align: , type: 97D7B011-54DA-4835-B3C4-917AD6E73D74, format: , file: system.bin
=== Entry: name: cache, size: 1024, align: , type: 5594C694-C871-4B5F-90B1-690A6F68E0F7, format: , file: cache.bin
=== Entry: name: cust, size: 1024, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: cust.bin
=== Entry: name: op, size: 1024, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: op.bin
=== Entry: name: userdata, size: 1024, align: , type: 1B81E7E6-F50D-419B-A739-2AEEF8DA3335, format: , file: userdata.bin
=== Entry: name: grow, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: grow.bin
=== Entry: name: xbl, size: 2048, align: , type: DEA0BA2C-CBDD-4805-B4F9-F428251C3E98, format: , file: xbl.bin
=== Entry: name: xblbak, size: 2048, align: , type: DF24E5ED-8C96-4B86-B00B-79667DC6DE11, format: , file: xbl.bin
=== Entry: name: fota, size: 4096, align: , type: 86A7CB80-84E1-408C-99AB-694F1A410FC7, format: , file: fota.bin
=== Entry: name: fsg, size: 2048, align: , type: 638FF8E2-22C9-E33B-8F5D-0E81686A68CB, format: , file: fsg.bin
=== Entry: name: dip, size: 1024, align: , type: 4114B077-005D-4E12-AC8C-B493BDA684FB, format: , file: dip.bin
=== Entry: name: devinfo, size: 1024, align: , type: 65ADDCF4-0C5C-4D9A-AC2D-D90B5CBFCD03, format: , file: devinfo.bin
=== Entry: name: grow2, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: grow2.bin
=== Entry: name: xbl2, size: 2048, align: , type: DEA0BA2C-CBDD-4805-B4F9-F428251C3E98, format: , file: xbl.bin
=== Entry: name: xbl2bak, size: 2048, align: , type: DF24E5ED-8C96-4B86-B00B-79667DC6DE11, format: , file: xbl.bin
=== Entry: name: grow3, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: grow3.bin
=== Entry: name: ddr, size: 2048, align: , type: 20A0C19C-286A-42FA-9CE7-F64C3226A794, format: , file: ddr.bin
=== Entry: name: reserve, size: 64, align: , type: 7A37A18E-48F0-BCA5-935E-5795DBB57FF8, format: , file: reserve.bin
=== Entry: name: cdt, size: 8, align: , type: A19F205F-CCD8-4B6D-8F1E-2D9BC24CFFB1, format: , file: cdt.bin
=== Entry: name: spare1, size: 4096, align: , type: 7EFE5010-2A1A-4A1A-B8BC-990257813512, format: , file: spare1.bin
=== Entry: name: grow4, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: grow4.bin
=== Entry: name: boot, size: 32768, align: , type: 20117F86-E985-4357-B9EE-374BC1D8487D, format: , file: boot.bin
=== Entry: name: recovery, size: 32768, align: , type: 9D72D4E4-9958-42DA-AC26-BEA7A90B0434, format: , file: recovery.bin
=== Entry: name: recoverybak, size: 32768, align: , type: DF24E5ED-8C96-4B86-B00B-79667DC6DE11, format: , file: recovery.bin
=== Entry: name: tz, size: 2048, align: , type: A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4, format: , file: tz.bin
=== Entry: name: tzbak, size: 2048, align: , type: E6C8667F-8044-44A7-B1D9-BEFE88AAD86C, format: , file: tz.bin
=== Entry: name: aboot, size: 2048, align: , type: 400FFDCD-22E0-47E7-9A23-F16ED9382388, format: , file: aboot.bin
=== Entry: name: abootbak, size: 2048, align: , type: C993E3DF-FE66-49C9-8D8D-7C681C4DCAE9, format: , file: aboot.bin
=== Entry: name: raw_resources, size: 4096, align: , type: 4627AE27-CFEF-48A1-88FE-99C3509ADE26, format: , file: raw_resources.bin
=== Entry: name: raw_resourcesbak, size: 4096, align: , type: C1DAB2CF-697D-4665-B43D-00BA47487528, format: , file: raw_resources.bin
=== Entry: name: rpm, size: 256, align: , type: 098DF793-D712-413D-9D4E-89D711772228, format: , file: rpm.bin
=== Entry: name: rpmbak, size: 256, align: , type: 680CA584-238C-4E0F-8438-15F43257A055, format: , file: rpm.bin
=== Entry: name: hyp, size: 384, align: , type: E1A6A689-0C8D-4CC6-B4E8-55A4320FBD8A, format: , file: hyp.bin
=== Entry: name: hypbak, size: 384, align: , type: 24C03326-2523-4E03-8C5E-B07ED7A44CD9, format: , file: hyp.bin
=== Entry: name: pmic, size: 64, align: , type: C00EEF24-7709-43D6-9799-DD2B411E7A3C, format: , file: pmic.bin
=== Entry: name: pmicbak, size: 64, align: , type: 4E646DCC-29E2-459A-B7C5-618E6F3AD76A, format: , file: pmic.bin
=== Entry: name: devcfg, size: 64, align: , type: F65D4B16-343D-4E25-AAFC-BE99B6556A6D, format: , file: devcfg.bin
=== Entry: name: devcfgbak, size: 64, align: , type: 10A0C19C-516A-5444-5CE3-664C3226A794, format: , file: devcfg.bin
=== Entry: name: modem, size: 98304, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: modem.bin
=== Entry: name: sec, size: 16, align: , type: 303E6AC3-AF15-4C54-9E9B-D9A8FBECF401, format: , file: sec.bin
=== Entry: name: keymaster, size: 384, align: , type: 4F772165-0F3C-4BA3-BBCB-A829E9C969F9, format: , file: keymaster.bin
=== Entry: name: keymasterbak, size: 384, align: , type: 7C29D3AD-78B9-452E-9DEB-D098D542F092, format: , file: keymaster.bin
=== Entry: name: cmnlib, size: 384, align: , type: 73471795-AB54-43F9-A847-4F72EA5CBEF5, format: , file: cmnlib.bin
=== Entry: name: cmnlibbak, size: 384, align: , type: 7C29D3AD-78B9-452E-9DEB-D098D542F092, format: , file: cmnlib.bin
=== Entry: name: cmnlib64, size: 384, align: , type: 8EA64893-1267-4A1B-947C-7C362ACAAD2C, format: , file: cmnlib64.bin
=== Entry: name: cmnlib64bak, size: 384, align: , type: 379D107E-229E-499D-AD4F-61F5BCF87BD4, format: , file: cmnlib64.bin
=== Entry: name: apdp, size: 64, align: , type: E6E98DA2-E22A-4D12-AB33-169E7DEAA507, format: , file: apdp.bin
=== Entry: name: msadp, size: 64, align: , type: ED9E8101-05FA-46B7-82AA-8D58770D200B, format: , file: msadp.bin
=== Entry: name: dpo, size: 1024, align: , type: 11406F35-1173-4869-807B-27DF71802812, format: , file: dpo.bin
=== Entry: name: grow5, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: grow5.bin
=== Entry: name: modemst1, size: 2048, align: , type: EBBEADAF-22C9-E33B-8F5D-0E81686A68CB, format: , file: modemst1.bin
=== Entry: name: modemst2, size: 2048, align: , type: 0A288B1F-22C9-E33B-8F5D-0E81686A68CB, format: , file: modemst2.bin
=== Entry: name: fsc, size: 1024, align: , type: 57B90A16-22C9-E33B-8F5D-0E81686A68CB, format: , file: fsc.bin
=== Entry: name: spare2, size: 4096, align: , type: 40270447-93EC-4805-9779-83A3AE37CFF0, format: , file: spare2.bin
=== Entry: name: grow6, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: grow6.bin
=== Entry: name: persistent, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: persistent.bin
=== Entry: name: grow7, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: grow7.bin
=== Create file with size (kb): 559145
=== Create image file: f800l.img
1+0 records in
1+0 records out
1024 bytes (1,0 kB, 1,0 KiB) copied, 0,0229406 s, 44,6 kB/s
=== Create part: name:laf, size:49152, type:98523EC6-90FE-4C67-B50A-0FC59ED6F56D, align:, format:, file:
Creating new GPT entries.
Setting name!
partNum is 0
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:mpt, size:49152, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file:
Setting name!
partNum is 1
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:drm, size:12288, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file:
Setting name!
partNum is 2
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:sns, size:8192, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file:
Setting name!
partNum is 3
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:misc, size:49152, type:82ACC91F-357C-4A68-9C8F-689E1B1A23A1, align:, format:, file:
Setting name!
partNum is 4
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:factory, size:16384, type:20117F86-E985-4357-B9EE-374BC1D8487D, align:, format:, file:
Setting name!
partNum is 5
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:encrypt, size:1024, type:323EF595-AF7A-4AFA-8060-97BE72841BB9, align:, format:, file:
Setting name!
partNum is 6
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:eksst, size:1024, type:45864011-CF89-46E6-A445-85262E065604, align:, format:, file:
Setting name!
partNum is 7
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:rct, size:64, type:8ED8AE95-597F-4C8A-A5BD-A7FF8E4DFAA9, align:, format:, file:
Setting name!
partNum is 8
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:ssd, size:1024, type:2C86E742-745E-4FDD-BFD8-B6A7AC638772, align:, format:, file:
Setting name!
partNum is 9
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:keystore, size:1024, typeE7D4029-0F5B-41C8-AE7E-F6C023A02B33, align:, format:, file:
Setting name!
partNum is 10

REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: nameersist, size:32768, type:6C95E238-E343-4BA8-B489-8681ED22AD0B, align:, format:, file:
Setting name!
partNum is 11
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:lafbak, size:49152, type:E0B10BE8-8B5F-46D0-BC9A-A629CC3E063D, align:, format:, file:
Setting name!
partNum is 12
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:system, size:1024, type:97D7B011-54DA-4835-B3C4-917AD6E73D74, align:, format:, file:
Setting name!
partNum is 13
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:cache, size:1024, type:5594C694-C871-4B5F-90B1-690A6F68E0F7, align:, format:, file:
Setting name!
partNum is 14
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:cust, size:1024, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file:
Setting name!
partNum is 15
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: namep, size:1024, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file:
Setting name!
partNum is 16
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:userdata, size:1024, type:1B81E7E6-F50D-419B-A739-2AEEF8DA3335, align:, format:, file:
Setting name!
partNum is 17
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:grow, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file:
Setting name!
partNum is 18
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:xbl, size:2048, typeEA0BA2C-CBDD-4805-B4F9-F428251C3E98, align:, format:, file:
Setting name!
partNum is 19
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:xblbak, size:2048, typeF24E5ED-8C96-4B86-B00B-79667DC6DE11, align:, format:, file:
Setting name!
partNum is 20
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:fota, size:4096, type:86A7CB80-84E1-408C-99AB-694F1A410FC7, align:, format:, file:
Setting name!
partNum is 21
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:fsg, size:2048, type:638FF8E2-22C9-E33B-8F5D-0E81686A68CB, align:, format:, file:
Setting name!
partNum is 22
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:dip, size:1024, type:4114B077-005D-4E12-AC8C-B493BDA684FB, align:, format:, file:
Setting name!
partNum is 23
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:devinfo, size:1024, type:65ADDCF4-0C5C-4D9A-AC2D-D90B5CBFCD03, align:, format:, file:
Setting name!
partNum is 24
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:grow2, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file:
Setting name!
partNum is 25
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:xbl2, size:2048, typeEA0BA2C-CBDD-4805-B4F9-F428251C3E98, align:, format:, file:
Setting name!
partNum is 26
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:xbl2bak, size:2048, typeF24E5ED-8C96-4B86-B00B-79667DC6DE11, align:, format:, file:
Setting name!
partNum is 27
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:grow3, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file:
Setting name!
partNum is 28
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:ddr, size:2048, type:20A0C19C-286A-42FA-9CE7-F64C3226A794, align:, format:, file:
Setting name!
partNum is 29
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:reserve, size:64, type:7A37A18E-48F0-BCA5-935E-5795DBB57FF8, align:, format:, file:
Setting name!
partNum is 30
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:cdt, size:8, type:A19F205F-CCD8-4B6D-8F1E-2D9BC24CFFB1, align:, format:, file:
Setting name!
partNum is 31
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:spare1, size:4096, type:7EFE5010-2A1A-4A1A-B8BC-990257813512, align:, format:, file:
Setting name!
partNum is 32
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:grow4, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file:
Setting name!
partNum is 33
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:boot, size:32768, type:20117F86-E985-4357-B9EE-374BC1D8487D, align:, format:, file:
Setting name!
partNum is 34
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:recovery, size:32768, type:9D72D4E4-9958-42DA-AC26-BEA7A90B0434, align:, format:, file:
Setting name!
partNum is 35
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:recoverybak, size:32768, typeF24E5ED-8C96-4B86-B00B-79667DC6DE11, align:, format:, file:
Setting name!
partNum is 36
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:tz, size:2048, type:A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4, align:, format:, file:
Setting name!
partNum is 37
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:tzbak, size:2048, type:E6C8667F-8044-44A7-B1D9-BEFE88AAD86C, align:, format:, file:
Setting name!
partNum is 38
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:aboot, size:2048, type:400FFDCD-22E0-47E7-9A23-F16ED9382388, align:, format:, file:
Setting name!
partNum is 39
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:abootbak, size:2048, type:C993E3DF-FE66-49C9-8D8D-7C681C4DCAE9, align:, format:, file:
Setting name!
partNum is 40
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:raw_resources, size:4096, type:4627AE27-CFEF-48A1-88FE-99C3509ADE26, align:, format:, file:
Setting name!
partNum is 41
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:raw_resourcesbak, size:4096, type:C1DAB2CF-697D-4665-B43D-00BA47487528, align:, format:, file:
Setting name!
partNum is 42
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:rpm, size:256, type:098DF793-D712-413D-9D4E-89D711772228, align:, format:, file:
Setting name!
partNum is 43
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:rpmbak, size:256, type:680CA584-238C-4E0F-8438-15F43257A055, align:, format:, file:
Setting name!
partNum is 44
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:hyp, size:384, type:E1A6A689-0C8D-4CC6-B4E8-55A4320FBD8A, align:, format:, file:
Setting name!
partNum is 45
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:hypbak, size:384, type:24C03326-2523-4E03-8C5E-B07ED7A44CD9, align:, format:, file:
Setting name!
partNum is 46
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: namemic, size:64, type:C00EEF24-7709-43D6-9799-DD2B411E7A3C, align:, format:, file:
Setting name!
partNum is 47
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: namemicbak, size:64, type:4E646DCC-29E2-459A-B7C5-618E6F3AD76A, align:, format:, file:
Setting name!
partNum is 48
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:devcfg, size:64, type:F65D4B16-343D-4E25-AAFC-BE99B6556A6D, align:, format:, file:
Setting name!
partNum is 49
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:devcfgbak, size:64, type:10A0C19C-516A-5444-5CE3-664C3226A794, align:, format:, file:
Setting name!
partNum is 50
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:modem, size:98304, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file:
Setting name!
partNum is 51
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:sec, size:16, type:303E6AC3-AF15-4C54-9E9B-D9A8FBECF401, align:, format:, file:
Setting name!
partNum is 52
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:keymaster, size:384, type:4F772165-0F3C-4BA3-BBCB-A829E9C969F9, align:, format:, file:
Setting name!
partNum is 53
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:keymasterbak, size:384, type:7C29D3AD-78B9-452E-9DEB-D098D542F092, align:, format:, file:
Setting name!
partNum is 54
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:cmnlib, size:384, type:73471795-AB54-43F9-A847-4F72EA5CBEF5, align:, format:, file:
Setting name!
partNum is 55
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:cmnlibbak, size:384, type:7C29D3AD-78B9-452E-9DEB-D098D542F092, align:, format:, file:
Setting name!
partNum is 56
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:cmnlib64, size:384, type:8EA64893-1267-4A1B-947C-7C362ACAAD2C, align:, format:, file:
Setting name!
partNum is 57
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:cmnlib64bak, size:384, type:379D107E-229E-499D-AD4F-61F5BCF87BD4, align:, format:, file:
Setting name!
partNum is 58
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:apdp, size:64, type:E6E98DA2-E22A-4D12-AB33-169E7DEAA507, align:, format:, file:
Setting name!
partNum is 59
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:msadp, size:64, type:ED9E8101-05FA-46B7-82AA-8D58770D200B, align:, format:, file:
Setting name!
partNum is 60
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:dpo, size:1024, type:11406F35-1173-4869-807B-27DF71802812, align:, format:, file:
Setting name!
partNum is 61
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:grow5, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file:
Setting name!
partNum is 62
REALLY setting name!
---------- Post added at 06:29 AM ---------- Previous post was at 06:28 AM ----------
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:modemst1, size:2048, type:EBBEADAF-22C9-E33B-8F5D-0E81686A68CB, align:, format:, file:
Setting name!
partNum is 63
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:modemst2, size:2048, type:0A288B1F-22C9-E33B-8F5D-0E81686A68CB, align:, format:, file:
Setting name!
partNum is 64
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:fsc, size:1024, type:57B90A16-22C9-E33B-8F5D-0E81686A68CB, align:, format:, file:
Setting name!
partNum is 65
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:spare2, size:4096, type:40270447-93EC-4805-9779-83A3AE37CFF0, align:, format:, file:
Setting name!
partNum is 66
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:grow6, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file:
Setting name!
partNum is 67
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: nameersistent, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file:
Setting name!
partNum is 68
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
=== Create part: name:grow7, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file:
Setting name!
partNum is 69
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
[email protected]:~/Downloads/kdz$ sudo parted f800l.img print
Model: (file)
Disk /home/aaya/Downloads/kdz/f800l.img: 573MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 17,4kB 50,3MB 50,3MB laf
2 50,3MB 101MB 50,3MB mpt msftdata
3 101MB 113MB 12,6MB drm msftdata
4 113MB 122MB 8389kB sns msftdata
5 122MB 172MB 50,3MB misc
6 172MB 189MB 16,8MB factory
7 189MB 190MB 1049kB encrypt
8 190MB 191MB 1049kB eksst
9 191MB 191MB 65,5kB rct
10 191MB 192MB 1049kB ssd
11 192MB 193MB 1049kB keystore
12 193MB 227MB 33,6MB persist
13 227MB 277MB 50,3MB lafbak
14 277MB 278MB 1049kB system
15 278MB 279MB 1049kB cache
16 279MB 280MB 1049kB cust msftdata
17 280MB 281MB 1049kB op msftdata
18 281MB 282MB 1049kB userdata
19 282MB 286MB 4194kB grow msftdata
20 286MB 288MB 2097kB xbl
21 288MB 291MB 2097kB xblbak
22 291MB 295MB 4194kB fota
23 295MB 297MB 2097kB fsg
24 297MB 298MB 1049kB dip
25 298MB 299MB 1049kB devinfo
26 299MB 303MB 4194kB grow2 msftdata
27 303MB 305MB 2097kB xbl2
28 305MB 307MB 2097kB xbl2bak
29 307MB 312MB 4194kB grow3 msftdata
30 312MB 314MB 2097kB ddr
31 314MB 314MB 65,5kB reserve
32 314MB 314MB 8192B cdt
33 314MB 318MB 4194kB spare1
34 318MB 322MB 4194kB grow4 msftdata
35 322MB 356MB 33,6MB boot
36 356MB 389MB 33,6MB recovery
37 389MB 423MB 33,6MB recoverybak
38 423MB 425MB 2097kB tz
39 425MB 427MB 2097kB tzbak
40 427MB 429MB 2097kB aboot
41 429MB 431MB 2097kB abootbak
42 431MB 435MB 4194kB raw_resources
43 435MB 440MB 4194kB raw_resourcesbak
44 440MB 440MB 262kB rpm
45 440MB 440MB 262kB rpmbak
46 440MB 440MB 393kB hyp
47 440MB 441MB 393kB hypbak
48 441MB 441MB 65,5kB pmic
49 441MB 441MB 65,5kB pmicbak
50 441MB 441MB 65,5kB devcfg
51 441MB 441MB 65,5kB devcfgbak
52 441MB 542MB 101MB modem msftdata
53 542MB 542MB 16,4kB sec
54 542MB 542MB 393kB keymaster
55 542MB 543MB 393kB keymasterbak
56 543MB 543MB 393kB cmnlib
57 543MB 543MB 393kB cmnlibbak
58 543MB 544MB 393kB cmnlib64
59 544MB 544MB 393kB cmnlib64bak
60 544MB 544MB 65,5kB apdp
61 544MB 544MB 65,5kB msadp
62 544MB 545MB 1049kB dpo
63 545MB 549MB 4194kB grow5 msftdata
64 549MB 552MB 2097kB modemst1
65 552MB 554MB 2097kB modemst2
66 554MB 555MB 1049kB fsc
67 555MB 559MB 4194kB spare2
68 559MB 563MB 4194kB grow6 msftdata
69 563MB 567MB 4194kB persistent msftdata
70 567MB 572MB 4194kB grow7 msftdata
[email protected]:~/Downloads/kdz$ sudo dmesg -c >> /dev/null
[email protected]:~/Downloads/kdz$ dmesg
[email protected]:~/Downloads/kdz$ 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/kdz$ cd kdz
bash: cd: kdz: No such file or directory
[email protected]:~/Downloads/kdz$ sudo -s
[email protected]:~/Downloads/kdz# dd if=f800l.img of=/dev/sdb
1118290+0 records in
1118290+0 records out
572564480 bytes (573 MB, 546 MiB) copied, 160,036 s, 3,6 MB/s
[email protected]:~/Downloads/kdz# sync
[email protected]:~/Downloads/kdz# ls -la /dev/disk/by-partlabel
total 1935116
drwxr-xr-x 2 root root 1160 Луу 27 13:17 .
drwxr-xr-x 8 root root 160 Луу 27 07:19 ..
-rw-r--r-- 1 root root 2097152 Луу 27 13:14 aboot
-rw-r--r-- 1 root root 2097152 Луу 27 13:14 abootbak
-rw-r--r-- 1 root root 524288 Луу 27 13:14 apdp
-rw-r--r-- 1 root root 41943040 Луу 27 13:14 boot
-rw-r--r-- 1 root root 4096 Луу 27 13:14 cdt
-rw-r--r-- 1 root root 524288 Луу 27 13:14 cmnlib
-rw-r--r-- 1 root root 524288 Луу 27 13:14 cmnlib64
-rw-r--r-- 1 root root 524288 Луу 27 13:14 cmnlib64bak
-rw-r--r-- 1 root root 524288 Луу 27 13:14 cmnlibbak
-rw-r--r-- 1 root root 2097152 Луу 27 13:14 ddr
-rw-r--r-- 1 root root 131072 Луу 27 13:14 devcfg
-rw-r--r-- 1 root root 131072 Луу 27 13:14 devcfgbak
-rw-r--r-- 1 root root 1048576 Луу 27 13:14 devinfo
-rw-r--r-- 1 root root 1048576 Луу 27 13:14 dip
-rw-r--r-- 1 root root 524288 Луу 27 13:14 dpo
-rw-r--r-- 1 root root 10485760 Луу 27 13:14 drm
-rw-r--r-- 1 root root 524288 Луу 27 13:14 eksst
-rw-r--r-- 1 root root 524288 Луу 27 13:14 encrypt
-rw-r--r-- 1 root root 69206016 Луу 27 13:14 factory
-rw-r--r-- 1 root root 4194304 Луу 27 13:14 fota
-rw-r--r-- 1 root root 524288 Луу 27 13:14 fsc
-rw-r--r-- 1 root root 2097152 Луу 27 13:14 fsg
-rw-r--r-- 1 root root 17920 Луу 27 13:14 gpt
-rw-r--r-- 1 root root 34304 Луу 27 13:14 gpt_both0
-rw-r--r-- 1 root root 524288 Луу 27 13:14 hyp
-rw-r--r-- 1 root root 524288 Луу 27 13:14 hypbak
-rw-r--r-- 1 root root 524288 Луу 27 13:14 keymaster
-rw-r--r-- 1 root root 524288 Луу 27 13:14 keymasterbak
-rw-r--r-- 1 root root 524288 Луу 27 13:14 keystore
-rw-r--r-- 1 root root 50331648 Луу 27 13:14 lafbak
-rw-r--r-- 1 root root 21757952 Луу 27 13:14 misc
-rw-r--r-- 1 root root 0 Луу 27 13:14 modem
-rw-r--r-- 1 root root 2097152 Луу 27 13:14 modemst1
-rw-r--r-- 1 root root 2097152 Луу 27 13:14 modemst2
-rw-r--r-- 1 root root 0 Луу 27 13:14 mpt
-rw-r--r-- 1 root root 0 Луу 27 13:14 msadp
-rw-r--r-- 1 root root 33554432 Луу 27 13:14 persist
-rw-r--r-- 1 root root 0 Луу 27 13:14 raw_resources
-rw-r--r-- 1 root root 0 Луу 27 13:14 raw_resourcesbak
-rw-r--r-- 1 root root 524288 Луу 27 13:14 rct
-rw-r--r-- 1 root root 0 Луу 27 13:14 recovery
-rw-r--r-- 1 root root 0 Луу 27 13:14 recoverybak
-rw-r--r-- 1 root root 32768 Луу 27 13:14 reserve
-rw-r--r-- 1 root root 0 Луу 27 13:14 rpm
-rw-r--r-- 1 root root 0 Луу 27 13:14 rpmbak
-rw-r--r-- 1 root root 0 Луу 27 13:14 sec
-rw-r--r-- 1 root root 0 Луу 27 13:14 sns
-rw-r--r-- 1 root root 4194304 Луу 27 13:14 spare1
-rw-r--r-- 1 root root 2097152 Луу 27 13:17 spare2
-rw-r--r-- 1 root root 1720893440 Луу 27 13:15 system
lrwxrwxrwx 1 root root 10 Луу 27 10:52 Test\x20Partition -> ../../sda4
-rw-r--r-- 1 root root 0 Луу 27 13:15 tz
-rw-r--r-- 1 root root 0 Луу 27 13:15 tzbak
-rw-r--r-- 1 root root 0 Луу 27 08:07 xbl2
-rw-r--r-- 1 root root 0 Луу 27 08:07 xbl2bak
-rw-r--r-- 1 root root 0 Луу 27 08:07 xblbak

[email protected]:~/Downloads/kdz#
[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=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=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=op.bin of=/dev/disk/by-partlabel/op
dd if=persist.bin of=/dev/disk/by-partlabel/persist
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=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
[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,0643486 s, 32,6 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0526737 s, 39,8 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0249284 s, 21,0 MB/s
81920+0 records in
81920+0 records out
41943040 bytes (42 MB, 40 MiB) copied, 0,770998 s, 54,4 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000361113 s, 11,3 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,023943 s, 21,9 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0197682 s, 26,5 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0210129 s, 25,0 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0205953 s, 25,5 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0528205 s, 39,7 MB/s
256+0 records in
256+0 records out
131072 bytes (131 kB, 128 KiB) copied, 0,0161039 s, 8,1 MB/s
256+0 records in
256+0 records out
131072 bytes (131 kB, 128 KiB) copied, 0,00298831 s, 43,9 MB/s
2048+0 records in
2048+0 records out
1048576 bytes (1,0 MB, 1,0 MiB) copied, 0,0283786 s, 36,9 MB/s
2048+0 records in
2048+0 records out
1048576 bytes (1,0 MB, 1,0 MiB) copied, 0,0326182 s, 32,1 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0400563 s, 13,1 MB/s
20480+0 records in
20480+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 0,22146 s, 47,3 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00814724 s, 64,4 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0052311 s, 100 MB/s
135168+0 records in
135168+0 records out
69206016 bytes (69 MB, 66 MiB) copied, 1,38552 s, 49,9 MB/s
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,106935 s, 39,2 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00975353 s, 53,8 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0546581 s, 38,4 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0183304 s, 28,6 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0188219 s, 27,9 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,113713 s, 4,6 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00687672 s, 76,2 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00577225 s, 90,8 MB/s
98304+0 records in
98304+0 records out
50331648 bytes (50 MB, 48 MiB) copied, 1,08353 s, 46,5 MB/s
dd: writing to '/dev/disk/by-partlabel/laf': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00924235 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/misc': No space left on device
42497+0 records in
42496+0 records out
21757952 bytes (22 MB, 21 MiB) copied, 0,403093 s, 54,0 MB/s
dd: writing to '/dev/disk/by-partlabel/modem': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0290838 s, 0,0 kB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0590141 s, 35,5 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0569646 s, 36,8 MB/s
dd: writing to '/dev/disk/by-partlabel/mpt': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0378504 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/msadp': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0192231 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/op': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0228324 s, 0,0 kB/s
65536+0 records in
65536+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0,617191 s, 54,4 MB/s
dd: writing to '/dev/disk/by-partlabel/raw_resourcesbak': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0215163 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/raw_resources': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00581143 s, 0,0 kB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0158591 s, 33,1 MB/s
dd: writing to '/dev/disk/by-partlabel/recoverybak': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0129297 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/recovery': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00115132 s, 0,0 kB/s
64+0 records in
64+0 records out
32768 bytes (33 kB, 32 KiB) copied, 0,016151 s, 2,0 MB/s
dd: writing to '/dev/disk/by-partlabel/rpmbak': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0118379 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/rpm': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00103714 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/sec': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00582426 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/sns': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00913119 s, 0,0 kB/s
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,103569 s, 40,5 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0530615 s, 39,5 MB/s
dd: writing to '/dev/disk/by-partlabel/system': No space left on device
3361121+0 records in
3361120+0 records out
1720893440 bytes (1,7 GB, 1,6 GiB) copied, 31,5384 s, 54,6 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,0140009 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,127579 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=abootbak.bin of=/dev/disk/by-partlabel/abootbak
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0562202 s, 37,3 MB/s
[email protected]:~/Downloads/kdz# dd if=aboot.bin of=/dev/disk/by-partlabel/aboot
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0509847 s, 41,1 MB/s
[email protected]:~/Downloads/kdz# dd if=apdp.bin of=/dev/disk/by-partlabel/apdp
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0198957 s, 26,4 MB/s
[email protected]:~/Downloads/kdz# dd if=boot.bin of=/dev/disk/by-partlabel/boot
81920+0 records in
81920+0 records out
41943040 bytes (42 MB, 40 MiB) copied, 0,771567 s, 54,4 MB/s
[email protected]:~/Downloads/kdz# dd if=cache.bin of=/dev/disk/by-partlabel/cache
dd: failed to open 'cache.bin': No such file or directory
[email protected]:~/Downloads/kdz# dd if=cdt.bin of=/dev/disk/by-partlabel/cdt
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000216207 s, 18,9 MB/s
[email protected]:~/Downloads/kdz# dd if=cmnlib64bak.bin of=/dev/disk/by-partlabel/cmnlib64bak
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0289889 s, 18,1 MB/s
[email protected]:~/Downloads/kdz# dd if=cmnlib64.bin of=/dev/disk/by-partlabel/cmnlib64
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0250437 s, 20,9 MB/s
[email protected]:~/Downloads/kdz# dd if=cmnlibbak.bin of=/dev/disk/by-partlabel/cmnlibbak
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0177252 s, 29,6 MB/s
[email protected]:~/Downloads/kdz# dd if=cmnlib.bin of=/dev/disk/by-partlabel/cmnlib
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0159855 s, 32,8 MB/s
[email protected]:~/Downloads/kdz# dd if=ddr.bin of=/dev/disk/by-partlabel/ddr
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0672052 s, 31,2 MB/s
[email protected]:~/Downloads/kdz# dd if=devcfgbak.bin of=/dev/disk/by-partlabel/devcfgbak
256+0 records in
256+0 records out
131072 bytes (131 kB, 128 KiB) copied, 0,00671658 s, 19,5 MB/s
[email protected]:~/Downloads/kdz# dd if=devcfg.bin of=/dev/disk/by-partlabel/devcfg
256+0 records in
256+0 records out
131072 bytes (131 kB, 128 KiB) copied, 0,0130537 s, 10,0 MB/s
[email protected]:~/Downloads/kdz# dd if=devinfo.bin of=/dev/disk/by-partlabel/devinfo
2048+0 records in
2048+0 records out
1048576 bytes (1,0 MB, 1,0 MiB) copied, 0,0344104 s, 30,5 MB/s
[email protected]:~/Downloads/kdz# dd if=dip.bin of=/dev/disk/by-partlabel/dip
2048+0 records in
2048+0 records out
1048576 bytes (1,0 MB, 1,0 MiB) copied, 0,0525063 s, 20,0 MB/s
[email protected]:~/Downloads/kdz# dd if=dpo.bin of=/dev/disk/by-partlabel/dpo
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0367111 s, 14,3 MB/s
[email protected]:~/Downloads/kdz# dd if=drm.bin of=/dev/disk/by-partlabel/drm
20480+0 records in
20480+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 0,206695 s, 50,7 MB/s
[email protected]:~/Downloads/kdz# dd if=eksst.bin of=/dev/disk/by-partlabel/eksst
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00657176 s, 79,8 MB/s
[email protected]:~/Downloads/kdz# dd if=encrypt.bin of=/dev/disk/by-partlabel/encrypt
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00701394 s, 74,7 MB/s
[email protected]:~/Downloads/kdz# dd if=factory.bin of=/dev/disk/by-partlabel/factory
135168+0 records in
135168+0 records out
69206016 bytes (69 MB, 66 MiB) copied, 1,40961 s, 49,1 MB/s
[email protected]:~/Downloads/kdz# dd if=fota.bin of=/dev/disk/by-partlabel/fota
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,10445 s, 40,2 MB/s
[email protected]:~/Downloads/kdz# dd if=fsc.bin of=/dev/disk/by-partlabel/fsc
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00887572 s, 59,1 MB/s
[email protected]:~/Downloads/kdz# dd if=fsg.bin of=/dev/disk/by-partlabel/fsg
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0509349 s, 41,2 MB/s
[email protected]:~/Downloads/kdz# dd if=grow2.bin of=/dev/disk/by-partlabel/grow2
dd: failed to open 'grow2.bin': No such file or directory
[email protected]:~/Downloads/kdz# dd if=grow3.bin of=/dev/disk/by-partlabel/grow3
dd: failed to open 'grow3.bin': No such file or directory
[email protected]:~/Downloads/kdz# dd if=grow4.bin of=/dev/disk/by-partlabel/grow4
dd: failed to open 'grow4.bin': No such file or directory
[email protected]:~/Downloads/kdz# dd if=grow5.bin of=/dev/disk/by-partlabel/grow5
dd: failed to open 'grow5.bin': No such file or directory
[email protected]:~/Downloads/kdz# dd if=grow6.bin of=/dev/disk/by-partlabel/grow6
dd: failed to open 'grow6.bin': No such file or directory
[email protected]:~/Downloads/kdz# dd if=grow.bin of=/dev/disk/by-partlabel/grow
dd: failed to open 'grow.bin': No such file or directory
[email protected]:~/Downloads/kdz# dd if=hypbak.bin of=/dev/disk/by-partlabel/hypbak
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0266637 s, 19,7 MB/s
[email protected]:~/Downloads/kdz# dd if=hyp.bin of=/dev/disk/by-partlabel/hyp
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0173174 s, 30,3 MB/s
[email protected]spire-E1-531:~/Downloads/kdz# dd if=keymasterbak.bin of=/dev/disk/by-partlabel/keymasterbak
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00618144 s, 84,8 MB/s
[email protected]:~/Downloads/kdz# dd if=keymaster.bin of=/dev/disk/by-partlabel/keymaster
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00514745 s, 102 MB/s
[email protected]:~/Downloads/kdz# dd if=keystore.bin of=/dev/disk/by-partlabel/keystore
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00609891 s, 86,0 MB/s
[email protected]:~/Downloads/kdz# dd if=lafbak.bin of=/dev/disk/by-partlabel/lafbak
98304+0 records in
98304+0 records out
50331648 bytes (50 MB, 48 MiB) copied, 0,911995 s, 55,2 MB/s
[email protected]:~/Downloads/kdz# dd if=laf.bin of=/dev/disk/by-partlabel/laf
dd: writing to '/dev/disk/by-partlabel/laf': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00618895 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=misc.bin of=/dev/disk/by-partlabel/misc
dd: writing to '/dev/disk/by-partlabel/misc': No space left on device
42497+0 records in
42496+0 records out
21757952 bytes (22 MB, 21 MiB) copied, 0,410335 s, 53,0 MB/s
[email protected]:~/Downloads/kdz# dd if=modem.bin of=/dev/disk/by-partlabel/modem
dd: writing to '/dev/disk/by-partlabel/modem': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0249778 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=modemst1.bin of=/dev/disk/by-partlabel/modemst1
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0639324 s, 32,8 MB/s
[email protected]:~/Downloads/kdz# dd if=modemst2.bin of=/dev/disk/by-partlabel/modemst2
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0402436 s, 52,1 MB/s
[email protected]:~/Downloads/kdz# dd if=mpt.bin of=/dev/disk/by-partlabel/mpt
dd: writing to '/dev/disk/by-partlabel/mpt': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0221325 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=msadp.bin of=/dev/disk/by-partlabel/msadp
dd: writing to '/dev/disk/by-partlabel/msadp': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0142649 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=persist.bin of=/dev/disk/by-partlabel/persist
65536+0 records in
65536+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0,621584 s, 54,0 MB/s
[email protected]:~/Downloads/kdz# dd if=pmicbak.bin of=/dev/disk/by-partlabel/pmicbak
dd: writing to '/dev/disk/by-partlabel/pmicbak': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,000650274 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=pmic.bin of=/dev/disk/by-partlabel/pmic
dd: writing to '/dev/disk/by-partlabel/pmic': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00025464 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=raw_resourcesbak.bin of=/dev/disk/by-partlabel/raw_resourcesbak
dd: writing to '/dev/disk/by-partlabel/raw_resourcesbak': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0157091 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=raw_resources.bin of=/dev/disk/by-partlabel/raw_resources
dd: writing to '/dev/disk/by-partlabel/raw_resources': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00922587 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=rct.bin of=/dev/disk/by-partlabel/rct
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0247106 s, 21,2 MB/s
[email protected]:~/Downloads/kdz# dd if=recoverybak.bin of=/dev/disk/by-partlabel/recoverybak
dd: writing to '/dev/disk/by-partlabel/recoverybak': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0176765 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=recovery.bin of=/dev/disk/by-partlabel/recovery
dd: writing to '/dev/disk/by-partlabel/recovery': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,000869766 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=reserve.bin of=/dev/disk/by-partlabel/reserve
64+0 records in
64+0 records out
32768 bytes (33 kB, 32 KiB) copied, 0,0476047 s, 688 kB/s
[email protected]:~/Downloads/kdz# dd if=rpmbak.bin of=/dev/disk/by-partlabel/rpmbak
dd: writing to '/dev/disk/by-partlabel/rpmbak': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00965593 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=rpm.bin of=/dev/disk/by-partlabel/rpm
dd: writing to '/dev/disk/by-partlabel/rpm': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,000823096 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=sec.bin of=/dev/disk/by-partlabel/sec
dd: writing to '/dev/disk/by-partlabel/sec': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0037476 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=sns.bin of=/dev/disk/by-partlabel/sns
dd: writing to '/dev/disk/by-partlabel/sns': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00548995 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=spare1.bin of=/dev/disk/by-partlabel/spare1
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,102285 s, 41,0 MB/s
[email protected]:~/Downloads/kdz# dd if=spare2.bin of=/dev/disk/by-partlabel/spare2
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0504355 s, 41,6 MB/s
[email protected]:~/Downloads/kdz# dd if=ssd.bin of=/dev/disk/by-partlabel/ssd
dd: failed to open 'ssd.bin': No such file or directory
[email protected]:~/Downloads/kdz# dd if=system.bin of=/dev/disk/by-partlabel/system
dd: writing to '/dev/disk/by-partlabel/system': No space left on device
3361121+0 records in
3361120+0 records out
1720893440 bytes (1,7 GB, 1,6 GiB) copied, 31,5257 s, 54,6 MB/s
[email protected]:~/Downloads/kdz# dd if=tzbak.bin of=/dev/disk/by-partlabel/tzbak
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,000273897 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=tz.bin of=/dev/disk/by-partlabel/tz
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,000330047 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=xbl2bak.bin of=/dev/disk/by-partlabel/xbl2bak
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,000430381 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=xbl2.bin of=/dev/disk/by-partlabel/xbl2
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,000282129 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=xblbak.bin of=/dev/disk/by-partlabel/xblbak
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,000217358 s, 0,0 kB/s
[email protected]:~/Downloads/kdz# dd if=xbl.bin of=/dev/disk/by-partlabel/xbl
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,000417175 s, 0,0 kB/s
[email protected]:~/Downloads/kdz#

Mods need to ban this guy for posting this stuff in multiple threads after he was told previously not to.
Sent from my LG-H910 using XDA Labs

@cnjax I wish he wouldn't have posted this until we get Oreo, but since it is out there, he has almost figured out how to boot from an SD card. Also, the massive posts weren't needed, a link to pastebin would have sufficed.
This is the ultimate hole that LG can't patch (can't modify the PBL).
I won't post the proper way until we get Oreo (LG has wasted enough time trying to close holes), but if someone else wants to do a little work, this method will root the LS997, and the H932 V30.

runningnak3d said:
@cnjax I wish he wouldn't have posted this until we get Oreo, but since it is out there, he has almost figured out how to boot from an SD card. Also, the massive posts weren't needed, a link to pastebin would have sufficed.
This is the ultimate hole that LG can't patch (can't modify the PBL).
I won't post the proper way until we get Oreo (LG has wasted enough time trying to close holes), but if someone else wants to do a little work, this method will root the LS997, and the H932 V30.
Click to expand...
Click to collapse
It doesn't matter what he's almost figured out, there's no reason to post dumps on the forum in multiple places, he could simply post what he's done or figured out and if anyone wanted to see it, he could send it to them directly.
Sent from my LG-H910 using XDA Labs

Database Users

welcome