Database Users

[Tutorial] How to build a ROM?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] Need Help!!! Not able to root Defy Plus..

Not able to root Defy Plus..
Build number: 4.5.1-134_dfp-231
tried all versions of super one click..
but no luck..

Hi.
Use this
http://forum.xda-developers.com/showthread.php?t=1595013

Thank you. . It worked...
Sent from my MB526 using XDA

Pls help me!!!
Hi,
I'm trying to root my Motorola Defy plus.
Android:2.3.6
System Version:45.0.2310.MB526.AsiaRetail.en.03
Baseband version:EPU93_U_00.60.03
Kernal version: 2.6.32.9
BUILD NO: 4.5.1-134_DFP-231
It seems I'm not having write access for System folder...
Can any one help me to get rid of it...
My log is below.....
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
256 KB/s (23060 bytes in 0.087s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
368 KB/s (1075144 bytes in 2.845s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
48 KB/s (439 bytes in 0.008s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 94% bytes
test: 94%: bad number
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
rm: can't remove '/system/app/Maps.apk': Read-only file system
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .​
Thanks in advance..

Try this method as only this method works on BL7.
http://forum.xda-developers.com/showthread.php?t=1542956

Bharath256 said:
Hi,
I'm trying to root my Motorola Defy plus.
Android:2.3.6
System Version:45.0.2310.MB526.AsiaRetail.en.03
Baseband version:EPU93_U_00.60.03
Kernal version: 2.6.32.9
BUILD NO: 4.5.1-134_DFP-231
It seems I'm not having write access for System folder...
Can any one help me to get rid of it...
Thanks in advance..
Click to expand...
Click to collapse
you seriously need to read the threads prior to posting.. Its been answered like a 100 times..

MY Defy+ got rooted
Thanks a lot.....my defy+ got rooted....:victory::good:

[Q:SOLVED] su : not found; rooted without root access

Hello.
Some of you might already have heard this question, but didn't seem to find an specific answer for my phone > Canadian S4 SGH I377M running Android 4.3
After the first time, I've tried installing a custom recovery (after rooting with motochopper). I've got an error because I wasn't granted root access. Tried to see with an app : no root access neither. Verified with a terminal : no root access. Tried re-rooting, it shows the following message :
Code:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *[*] Device found.[*] Pushing exploit...
4439 KB/s (1283460 bytes in 0.282s)[*] Pushing root tools...
4758 KB/s (366952 bytes in 0.075s)
3837 KB/s (1867568 bytes in 0.475s)
2829 KB/s (1578585 bytes in 0.544s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS][*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.[*] Cleaning up...[*] Exploit complete. Press enter to reboot and exit.
What is there left to do?

gr4v1ty said:
Hello.
Some of you might already have heard this question, but didn't seem to find an specific answer for my phone > Canadian S4 SGH I377M running Android 4.3
After the first time, I've tried installing a custom recovery. I've got an error because I wasn't granted root access. Tried to see with an app : no root access neither. Verified with a terminal : no root access. Tried re-rooting, it shows the following message :
Code:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *[*] Device found.[*] Pushing exploit...
4439 KB/s (1283460 bytes in 0.282s)[*] Pushing root tools...
4758 KB/s (366952 bytes in 0.075s)
3837 KB/s (1867568 bytes in 0.475s)
2829 KB/s (1578585 bytes in 0.544s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS][*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.[*] Cleaning up...[*] Exploit complete. Press enter to reboot and exit.
What is there left to do?
Click to expand...
Click to collapse
What methods have you tried? Did you try the Chainfire Auto Root?

DeadlySin9 said:
What methods have you tried? Did you try the Chainfire Auto Root?
Click to expand...
Click to collapse
It was motochopper. Sorry forgot to mention. Also here the output of the root checker pro app
Code:
Root Access is not properly configured or was not granted.
Super User Application Status:
Superuser application - is NOT installed.
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your SGH-I337M device by Root Checker Pro version 1.3.5 from joeykrim in the Android Market - http://goo.gl/NcnHn
EDIT : Solved by using CF-Auto-root : http://forum.xda-developers.com/showthread.php?t=2293800
Sent from my SGH-I337M using Tapatalk

Problem Installing TWRP 2.7 (D802)

Im having a problem installing TWRP 2.7.0.0 on my D802 Phone. Well i have all the drivers installed and already rooted and things but i can't install it.
Please check this:
Code:
Install Recovery...
3888 KB/s (67688 bytes in 0.017s)
3636 KB/s (67020 bytes in 0.018s)
3442 KB/s (8869888 bytes in 2.516s)
/dev/block/platform/msm_sdcc.1/by-name/aboot: cannot open for read: Permission d
enied
Unable to open /data/local/tmp/aboot.img: No such file or directory
[+] loki_patch v2.1
[-] Failed to open /data/local/tmp/aboot.img for reading.
[+] loki_flash v2.0
[-] Failed to open aboot for reading.
Press any key to Reboot into recovery or disconnect USB cable from PC now...
Thank you

b4mb1_ said:
Im having a problem installing TWRP 2.7.0.0 on my D802 Phone. Well i have all the drivers installed and already rooted and things but i can't install it.
Please check this:
Code:
Install Recovery...
3888 KB/s (67688 bytes in 0.017s)
3636 KB/s (67020 bytes in 0.018s)
3442 KB/s (8869888 bytes in 2.516s)
/dev/block/platform/msm_sdcc.1/by-name/aboot: cannot open for read: Permission d
enied
Unable to open /data/local/tmp/aboot.img: No such file or directory
[+] loki_patch v2.1
[-] Failed to open /data/local/tmp/aboot.img for reading.
[+] loki_flash v2.0
[-] Failed to open aboot for reading.
Press any key to Reboot into recovery or disconnect USB cable from PC now...
Thank you
Click to expand...
Click to collapse
Are you using autorec??
Sent from my LG-D800 using XDA Free mobile app

Nigglenuts said:
Are you using autorec??
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
I fixed it bro. i just used autorec and it got fine. No problems now my problem is on the kernel thing.
Code:
forum.xda-developers.com/lg-g2/help/wrong-kernel-pardus-hdc-7-7-t2860574

[Discussion] Z3+/Z4 Recovery/kernel Development thread [UB/LB]

Hello Guys
i am new to z3+/z4 thread
but never matters
i would like to have some small discussion about recoveries and kernels
i am not new to build recoveries and kernels or roms
for now guys i need your help on getting me some files
i need kernel.sin from ftf of your latest build from sony
cause i cant download whole ftf for small mb file
hope you understand me
so guys provide me the kenrel.sin so that i can try to provide working recoveries / kernels / roms
for both locked and unlocked bootloaders
Best regards

venkat kamesh said:
Hello Guys
i am new to z3+/z4 thread
but never matters
i would like to have some small discussion about recoveries and kernels
i am not new to build recoveries and kernels or roms
for now guys i need your help on getting me some files
i need kernel.sin from ftf of your latest build from sony
cause i cant download whole ftf for small mb file
hope you understand me
so guys provide me the kenrel.sin so that i can try to provide working recoveries / kernels / roms
for both locked and unlocked bootloaders
Best regards
Click to expand...
Click to collapse
this is kernel.sin from e6533
https://drive.google.com/file/d/0B5Rlv3cCMcOkYXZaVlFudXU4eE0/view
when you finish please mention me in a reply
go ahead <3

Sony guy said:
this is kernel.sin from e6533
https://drive.google.com/file/d/0B5Rlv3cCMcOkYXZaVlFudXU4eE0/view
when you finish please mention me in a reply
go ahead <3
Click to expand...
Click to collapse
thank you
finally a build.prop from system folder
and yes i will inform you guys once built

venkat kamesh said:
thank you
finally a build.prop from system folder
and yes i will inform you guys once built
Click to expand...
Click to collapse
Kernel.sin and build.prop from the latest firmware : 28.0.A.7.31

test recoveries
ChrisJ951 said:
Kernel.sin and build.prop from the latest firmware : 28.0.A.7.31
Click to expand...
Click to collapse
Thank you guys
For providing required files
I had finally built recoveries (test recoveries)
And installer scripts by @[NUT]
All you need is root then try installer pack
Of you have any recoveries try flash pack
Report me if you test them.... So that I can move forward with additional development
Flashable pack
Installer pack
Best regards

Did you test it on your device, or did you build without actual device?
I built TWRP for Z4T but there's touch problem, so I'd like to know how to fix if you already tested on Z3+.

AndroPlus said:
Did you test it on your device, or did you build without actual device?
I built TWRP for Z4T but there's touch problem, so I'd like to know how to fix if you already tested on Z3+.
Click to expand...
Click to collapse
What kind of touch problem? I have solved that for various devices in the past, based on a fix from @DooMLoRD and @Dees_Troy and also a fix I developed together with @rachitrawat.
Who can point me to a device repository so I can have a look at the code and files used to build it?

[NUT] said:
What kind of touch problem? I have solved that for various devices in the past, based on a fix from @DooMLoRD and @Dees_Troy and also a fix I developed together with @rachitrawat.
Who can point me to a device repository so I can have a look at the code and files used to build it?
Click to expand...
Click to collapse
Touch doesn't work at all, only power key works.
I used official device tree from
https://github.com/sonyxperiadev?tab=repositories
and modified (contains unneeded things while trying...)
https://github.com/AndroPlus-org/android_device_sony_kitakami

[NUT] said:
What kind of touch problem? I have solved that for various devices in the past, based on a fix from @DooMLoRD and @Dees_Troy and also a fix I developed together with @rachitrawat.
Who can point me to a device repository so I can have a look at the code and files used to build it?
Click to expand...
Click to collapse
Sure I will update my source file to git when I reach home
And androplus I haven't tested them... I just built them..
I am gonna get this device in a week (online shop)
So started work.....

AndroPlus said:
Touch doesn't work at all, only power key works.
I used official device tree from
https://github.com/sonyxperiadev?tab=repositories
and modified (contains unneeded things while trying...)
https://github.com/AndroPlus-org/android_device_sony_kitakami
Click to expand...
Click to collapse
I have no Z4/Z3+ nor do I own a Tablet Z4 but I will try to help out.
Do you have a log from TWRP which I can view?
Make sure you tap the screen a few times before you copy the log.

could be fixed witth the new binaries
I had built the AOSP for the Tablet Z4 and complained about touch not working.
Jerpela informed me that he put up a new revision.
I can not see that from the commit logs on GitHub (he also wrote he had done stagefright patches- checked a few minutes ago, where?). Maybe he meant updated binaries on SONY developer world...

@venkat kamesh
Sony Z3+ and I tried your Installer Pack, here is the log and i was choosing option 1 (SuperSU) coz phone is rooted
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= By Venkat kamseh =
= Scripts by Nut =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is ivy
Firmware is 28.0.A.7.24
=============================================
Step2 : Sending the recovery files.
=============================================
1 KB/s (30 bytes in 0.015s)
986 KB/s (15757 bytes in 0.015s)
31 KB/s (501 bytes in 0.015s)
11 KB/s (12198 bytes in 1.000s)
1778 KB/s (56834 bytes in 0.031s)
192 KB/s (3082 bytes in 0.015s)
24 KB/s (385 bytes in 0.015s)
2940 KB/s (657704 bytes in 0.218s)
2566 KB/s (3730720 bytes in 1.419s)
2493 KB/s (2827723 bytes in 1.107s)
2439 KB/s (2377056 bytes in 0.951s)
556 KB/s (8889 bytes in 0.015s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 657704 Jan 27 2015 /data/local/tmp/recover
y/busybox
Drücken Sie eine beliebige Taste . . .
##########################################################
#
# Installing XZDR version 2.8.1 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
find: /dev/block/platform/msm_sdcc.1/by-name/: No such file or directory
BusyBox v1.20.2-jb static (2012-11-25 17:47 +0100) multi-call binary.
Usage: blockdev OPTION BLOCKDEV
--setro Set ro
--setrw Set rw
--getro Get ro
--getss Get sector size
--getbsz Get block size
--setbsz BYTES Set block size
--getsz Get device size in 512-byte sectors
--getsize64 Get device size in bytes
--flushbufs Flush buffers
--rereadpt Reread partition table
Copy recovery files to system.
Rename stock chargemon
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Creating /system/.XZDualRecovery to store a backup copy of busybox.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event2!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Results:
Feeling was like recovery, but didnt enter recovery.
I was trying start - wait for green light then i pressed vol - and a short time pink LED came. But no enter to recovery, after ca. 20 sec newstart into normal mode.
The same with start, waiting for green light then press vol +
Sorry bro, no success but thanks for your work, I stay tuned and if you got a new version i test it.
best reguards.
Edit: following error message in log
find: /dev/block/platform/msm_sdcc.1/by-name/: No such file or directory
tree in my phone z3+:
/dev/block/platform/f9824900.sdhci/by-name/...
/dev/block/platform/f98a4900.sdhci/by-num/...
i try with my path and following resuluts, here is the log
(edited files: chargemon.sh, installrecovery.sh, rickiller.sh)
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= By Venkat kamseh =
= Scripts by Nut =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is ivy
Firmware is 28.0.A.7.24
=============================================
Step2 : Sending the recovery files.
=============================================
0 KB/s (30 bytes in 1.000s)
15 KB/s (15761 bytes in 1.000s)
0 KB/s (501 bytes in 1.000s)
11 KB/s (12198 bytes in 1.000s)
3557 KB/s (56834 bytes in 0.015s)
3 KB/s (3090 bytes in 1.000s)
24 KB/s (385 bytes in 0.015s)
2940 KB/s (657704 bytes in 0.218s)
3072 KB/s (3730720 bytes in 1.185s)
2765 KB/s (2827723 bytes in 0.998s)
2755 KB/s (2377056 bytes in 0.842s)
556 KB/s (8893 bytes in 0.015s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 657704 Jan 27 2015 /data/local/tmp/recover
y/busybox
Drücken Sie eine beliebige Taste . . .
##########################################################
#
# Installing XZDR version 2.8.1 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
Copy recovery files to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event2!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries!
=============================================
still the same result, green LED goes to pink led for one second, but Sony Xperia loader screen stays hard. No recovery.
My laptop is searching for a new driver called: "MTP-USB-Device" but don't find it.
the device hardware id is: USB\VID_18D1&PID_4EE2&REV_0310&MI_00
i was editing my C:\Windows\inf\wpdmtp.inf file with following:
[Generic.NTx86]
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
[Generic.NTamd64]
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
but no results, still didn't find the drivers
this is all what i can test, pleast stay tuned and make more tests for me
greetings

[NUT] said:
I have no Z4/Z3+ nor do I own a Tablet Z4 but I will try to help out.
Do you have a log from TWRP which I can view?
Make sure you tap the screen a few times before you copy the log.
Click to expand...
Click to collapse
USB isn't detected by PC in TWRP and I can't create full log...
Is there any other way to make log?
Here's last_log from /cache/recovery:
http://x.andro.plus/1Lvvhom

Sacktreter said:
@venkat kamesh
Sony Z3+ and I tried your Installer Pack, here is the log and i was choosing option 1 (SuperSU) coz phone is rooted
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= By Venkat kamseh =
= Scripts by Nut =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is ivy
Firmware is 28.0.A.7.24
=============================================
Step2 : Sending the recovery files.
=============================================
1 KB/s (30 bytes in 0.015s)
986 KB/s (15757 bytes in 0.015s)
31 KB/s (501 bytes in 0.015s)
11 KB/s (12198 bytes in 1.000s)
1778 KB/s (56834 bytes in 0.031s)
192 KB/s (3082 bytes in 0.015s)
24 KB/s (385 bytes in 0.015s)
2940 KB/s (657704 bytes in 0.218s)
2566 KB/s (3730720 bytes in 1.419s)
2493 KB/s (2827723 bytes in 1.107s)
2439 KB/s (2377056 bytes in 0.951s)
556 KB/s (8889 bytes in 0.015s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 657704 Jan 27 2015 /data/local/tmp/recover
y/busybox
Drücken Sie eine beliebige Taste . . .
##########################################################
#
# Installing XZDR version 2.8.1 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
find: /dev/block/platform/msm_sdcc.1/by-name/: No such file or directory
BusyBox v1.20.2-jb static (2012-11-25 17:47 +0100) multi-call binary.
Usage: blockdev OPTION BLOCKDEV
--setro Set ro
--setrw Set rw
--getro Get ro
--getss Get sector size
--getbsz Get block size
--setbsz BYTES Set block size
--getsz Get device size in 512-byte sectors
--getsize64 Get device size in bytes
--flushbufs Flush buffers
--rereadpt Reread partition table
Copy recovery files to system.
Rename stock chargemon
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Creating /system/.XZDualRecovery to store a backup copy of busybox.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event2!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Results:
Feeling was like recovery, but didnt enter recovery.
I was trying start - wait for green light then i pressed vol - and a short time pink LED came. But no enter to recovery, after ca. 20 sec newstart into normal mode.
The same with start, waiting for green light then press vol +
Sorry bro, no success but thanks for your work, I stay tuned and if you got a new version i test it.
best reguards.
Edit: following error message in log
find: /dev/block/platform/msm_sdcc.1/by-name/: No such file or directory
tree in my phone z3+:
/dev/block/platform/f9824900.sdhci/by-name/...
/dev/block/platform/f98a4900.sdhci/by-num/...
i hope this helps
Click to expand...
Click to collapse
Seeing that XZDR log... I have a few things to add for @venkat kamesh
First of all, update your XZDR repository to 2.8.21, this is better suited to work with and defeat the SELinux and Sony RIC security features in Lollipop. 2.8.1 will not work on Lollipop.
Then update the following lines at these points to match the correct block device path where @Sacktreter here already stated.
https://github.com/xNUTx/XZDualRecovery/blob/2.8-RELEASE/src/chargemon.sh#L253-L254
https://github.com/xNUTx/XZDualRecovery/blob/2.8-RELEASE/src/chargemon.sh#L336-L337
https://github.com/xNUTx/XZDualRecovery/blob/2.8-RELEASE/patches/all/twrp/etc/twrp.fstab#L1-L5
https://github.com/xNUTx/XZDualRecovery/blob/2.8-RELEASE/src/installrecovery.sh#L126
change /dev/block/platform/msm_sdcc.1 to /dev/block/platform/f9824900.sdhci on all the above lines.
This is the reason why I didn't release XZDR for the Z3+/Z4/TabZ4 yet, too much difference with the Shinano and older device trees.
That should be solved with 2.9 though...
---------- Post added at 03:15 PM ---------- Previous post was at 03:04 PM ----------
AndroPlus said:
USB isn't detected by PC in TWRP and I can't create full log...
Is there any other way to make log?
Here's last_log from /cache/recovery:
http://x.andro.plus/1Lvvhom
Click to expand...
Click to collapse
What OS do you run on your pc? Does windows register anything (even if it's just an unknown device) on the usb port?

[NUT] said:
What OS do you run on your pc? Does windows register anything (even if it's just an unknown device) on the usb port?
Click to expand...
Click to collapse
Windows 10 and there's no unknown device.
I can connect my Z3 in TWRP, so maybe something is preventing loading of init scripts.

AndroPlus said:
Windows 10 and there's no unknown device.
I can connect my Z3 in TWRP, so maybe something is preventing loading of init scripts.
Click to expand...
Click to collapse
Well, I suspect the USB device might also have a different name from the shinano hardware, which causes TWRP to mis configure the USB stack, or ignore it altogether...
See if you can find the USB root hub/controller in the ROM inside the /sys/class directory or a mention of the location in the init.usb.rc setup files (there should be at least one shell script being executed to set up the USB stack), see if you can find a device name there and then match that with the one in the kitakami repo's. The mention of this can be in either the device or the common repository.

@Nut
its a pleasure for me to talk with the master (i smile)
i dont wanna open a new answer so i edit my answer, sorry but in future i answer in a new post. Please watch my second result, i changed the path and the log is without errors, but still no enter to recovery. I konw you can help.
Edit: as you told the version 2.8.1 is needed update to version 2.8.21, now i understand and I wait. Sorry for my bad english, german is my favorite language

Sacktreter said:
@Nut
its a pleasure for me to talk with the master (i smile)
i dont wanna open a new answer so i edit my answer, sorry but in future i answer in a new post. Please watch my second result, i changed the path and the log is without errors, but still no enter to recovery. I konw you can help.
Edit: as you told the version 2.8.1 is needed update to version 2.8.21, now i understand and I wait. Sorry for my bad english, german is my favorite language
Click to expand...
Click to collapse
I saw your edit before, just post a new reply if you have any updates, makes it easier to track progress
In your USB driver inf file, you should remove &MI_00 from the device ID lines, this makes it match anything which starts with VID_18D1&PID_4EE2
https://github.com/xNUTx/XZDualReco...y/files/adbdrivers/android_winusb.inf#L28-L40
I'm not saying to use the ID's from this inf file, because this driver is meant for the ID's I am using in the recoveries for the 'official' XZDR releases.

init.kitakami.usb.rc
@Nut
see attachment from my karin_windy AOSP build

@AndroPlus scrap that search, I think something else is wrong. Seeing the usb config posted by @DHGE and the init in the aosp repositories I think twrp might be crashing when it finishes loading. Though the log you provided doesn't specify this (restart counter), it does seem to restart at some point...