Database Users

[Q] Help please, can't seem to reach Clockwork. Logs included, thanks!

Hi there. I got an Epic 4G not too long ago, and I've been attempting to root and install Clockwork to get some custom ROMs on it.
Installed Samsung drivers, phone connects fine. I'm not mounting the SD card, and I've tried it in Charge Only and USB Mass Storage modes.
I ran the sticky'd root method (2.2.6) from the Development subforum under the Epic 4G. Here is my log from that:
Code:
C:\Users\___>CD C:\Users\___\Desktop\Root
C:\Users\___\Desktop\root>adb devices
List of devices attached
D70024857e4d device
C:\Users\___\Desktop\root>run.bat
exploit and busybox made by joeykrim and one click installer made by noobnl and
firon
Press any key to continue . . .
copy and run the exploit (may take 2 minutes)
128 KB/s (5392 bytes in 0.041s)
3 KB/s (88 bytes in 0.026s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 2208
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
make it RW and move files
30 KB/s (687 bytes in 0.022s)
246 KB/s (26264 bytes in 0.104s)
355 KB/s (196521 bytes in 0.540s)
327 KB/s (14428 bytes in 0.043s)
9 KB/s (201 bytes in 0.020s)
413 KB/s (511436 bytes in 1.207s)
8 KB/s (203 bytes in 0.024s)
24 KB/s (479 bytes in 0.019s)
set permission
install busybox
push any key to reboot the phone
Press any key to continue . . .
Alright, so it rebooted. I can see SuperUser, and I can run apps that require root work perfectly (that screenshot one, etc).
So, I go to install Clockwork from the SDX forum (crossposted [link to noobnl's post spliced]). I ran "run-try-first.bat"
Code:
C:\Users\___>CD C:\Users\Media\Desktop\clockwork
C:\Users\___\Desktop\clockwork>adb devices
List of devices attached
D70024857e4d device
C:\Users\___\Desktop\clockwork>adb shell
$ su
su
# exit
exit
$ exit
exit
C:\Users\___\Desktop\clockwork>run-try-first.bat
one click installer and Clockworkmod Recovery v2.5.1.0 made by noobnl, skeeters
lint, and koush
Press any key to continue . . .
remove stock recovery patcher
mount: Operation not permitted
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
copy kernel and flasher
432 KB/s (313888 bytes in 0.708s)
462 KB/s (5820868 bytes in 12.299s)
flashing kernel
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
open device file: Permission denied
bmldevice_get_size: bmldevice_open failed!src: /sdcard/zImage
dst: /dev/block/bml8 partition size: 0x0
part_size: 0x0
reboot: Operation not permitted
wait 60 second
cleanup
done
Press any key to continue . . .
C:\Users\___\Desktop\clockwork>
So, that seems like it didn't really work. I rebooted and went to recovery with ADB on the computer, with the volume + camera + power method, and got the stock recovery each time.
I went back in and installed ROM Manager, and flashed the newest build for the Epic, didn't work, stock recovery with the E: verification failed error.
I returned to my PC to try "run-try-last.bat"
Code:
C:\Users\___\Desktop\clockwork>run-try-last.bat
one click installer and Clockworkmod Recovery v2.5.1.0 made by noobnl, skeetersl
int, and koush
Press any key to continue . . .
copy and run the exploit (may take 2 minutes)
146 KB/s (5392 bytes in 0.036s)
4 KB/s (88 bytes in 0.020s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 2209
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
remove stock recovery patcher
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
copy kernel and flasher
459 KB/s (313888 bytes in 0.667s)
343 KB/s (5820868 bytes in 16.535s)
flashing kernel
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /sdcard/zImage
dst: /dev/block/bml8 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 53700 bytes
read finished
wait 60 second
cleanup
done
Press any key to continue . . .
C:\Users\___\Desktop\clockwork>adb reboot recovery
Same thing, didn't work. I am currently guessing that the:
Code:
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
is the problem, since I can't seem to remove these files? I don't know.
Help is appreciated! Thanks much!
EDIT
Code:
C:\Users\Media>CD C:\Users\Media\Desktop\Root
C:\Users\Media\Desktop\root>adb shell mount -t rfs -o remount,rw /dev/block/stl9
/system
mount: Operation not permitted
C:\Users\Media\Desktop\root>adb shell
$ su
su
# mount -t rfs -o remount,rw /dev/block/stl9 /system
mount -t rfs -o remount,rw /dev/block/stl9 /system
# rm /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh
rm failed for /system/etc/install-recovery.sh, No such file or directory
# rm /system/recovery/recovery-from-boot.p
rm /system/recovery/recovery-from-boot.p
rm failed for /system/recovery/recovery-from-boot.p, No such file or directory
#
These files actually don't exist or something

I am having this exact same problem. When I try to use clockwork it goes to the stock android recovery mode and I receive the signature error.

are you rooted first?
nevermind sorry

I can finally answer w/ a why (in addition to an answer) - I think!
Before running the run last script open up an adb shell and type
Code:
su
remount rw
exit
exit
now run the script
I think this happens because the joeykim root leaves the system readonly?
Two other options if the above doesn't work:
1)Start fresh (reflash) from Odin and then install clockwork BEFORE rooting
2)Open up an adb shell and type the commands in the runlast script manually
hope that helps

jimmyz said:
I can finally answer w/ a why (in addition to an answer) - I think!
Before running the run last script open up an adb shell and type
Code:
su
remount rw
exit
exit
now run the script
I think this happens because the joeykim root leaves the system readonly?
Two other options if the above doesn't work:
1)Start fresh (reflash) from Odin and then install clockwork BEFORE rooting
2)Open up an adb shell and type the commands in the runlast script manually
hope that helps
Click to expand...
Click to collapse
I tried to do this and here is what I got. I may have messed up since I am new to this.
c:\samsung>adb shell
$ su
su
remount rw
remount rw
Permission denied
$ Remounting /system </dev/st19> in read/write mode
mount: Operation not permitted
$

Does anyone think it could be caused by the system update that has been rolling out? I downloaded that before I rooted.

I am having the same problem while trying to get Clockwork to work correctly on my Epic.
I also think that the problem is related to the install-recovery.sh and recovery-from-boot.p files. If I run a batch file (run.bat or run-try-first.bat or run-try-last.bat) the first problem is always when it tries to remove these files.
First I tried to just remove the install-recover.sh file
>adb shell rm /system/etc/install-recovery.sh
rm failed for /system/etc/install-recovery.sh, Read-only file system
The system reported that the file system was read-only.
Next I changed the file system to be writable.
>adb shell
$ su
su
# remount rw
remount rw
Remounting /system (/dev/stl9) in read/write mode
# exit
exit
$ exit
exit
This seemed to work ok and no errors were reported
Last I tried to delete the file again.
>adb shell rm /system/etc/install-recovery.sh
rm failed for /system/etc/install-recovery.sh, No such file or directory
This time the system reported that the file (or directory) was not found.
All of the updates have been applied to this phone.
I'm just getting into the Android world so I'm pretty lost right now. I am able to get into the clockwork recovery if I hold the volume-down, camera button and the power button down until the phone is fully turned on. I am not able to update the phone's rom and this problem seems to be tied back to that the phone is not "really" rooted (this is pretty much just a guess...)
Thank you in advance for any help or suggestions you may offer!
Scott

Hi there.
I've redone the entire phone a few times now with Odin. Each time I try a new method of root/flashing clockwork. I've tried in every combination:
-Using Noobl's stuff, including 2.2.7, 2.2.6, and I guess 2.2.5 or whatever he published before that
-Using Koush's clockwork and noobl's clockwork things, both -first and -last
-Pulling the battery during the clockwork reboot and using the camera + volume + power
-Using ADB rebooting and quick rebooting
-Remounting the system RW between root and clockwork, before both, etc
Nothing has worked, tried with no updates applied and with all 3, and with the first one. I guess this android stuff just isn't my cup of tea after all. Time to wait for WP7, I suppose (can't stand this 5 hour battery crap, was hoping to fix it). Tried it on 3 computers, done it every conceivable way.
Thanks to the modding community, rooting community, and everybody who writes the guides. I guess I'm just unlucky or something.
EDIT: Disregard that, randomly worked after pulling the battery during the reboot following Noobl's clockwork install...... well then

If you want to try one last time I would try to manually root etc by entering one line at a time via adb
Sent from my SPH-D700 using XDA App

Installed The Boss Mod V.3
JuiceDefender, Superuser, ROM Manager
I can still only reach Clockwork via the Power + Volume + Camera, not through adb reboot or the clockwork menu...

juchmis said:
Installed The Boss Mod V.3
JuiceDefender, Superuser, ROM Manager
I can still only reach Clockwork via the Power + Volume + Camera, not through adb reboot or the clockwork menu...
Click to expand...
Click to collapse
This is expected behavior if you just used noobnl one click- it installs to bml8. IF you want to reach clockwork through Rom Manager you need to have a modified kernel (on bml7) which many of the custom Roms have built in. After you you do that adb reboot will work but only if you keep the appropriate clockworkwod mod update.zip in the root of your sdcard and select it through the "stock" recovery- this is "fakeflash"

[GUIDE] Beginner guide how to install new kernel from linux OS !!!

Let`s start from beginning...
First download attached file New kernell install.7z and unpack it on your desktop.
Then go to ADB install procedure...
Open Terminal and you will see something like this...
HINT:
The best way to install is to run on Root Terminal. This is placed on Applications -> System Tools.
On Ubuntu it is invisible by default and you must to enable it on System -> Preferences -> Main menu and make it visible.
That`t it... lets go to work...
Open terminal and you will see this...
[email protected]_name:~$
Then type this in your Terminal window. Only BOLD text must be typed... Don`t forget to press ENTER after type the command in Terminal.
And don`t forget to type your root password after sudo command.
[email protected]_name:~$ cd Desktop
[email protected]_name:~/Desktop$ cd ADB_install
[email protected]_name:~/Desktop/ADB_install$ sudo cp adb /usr/bin
[email protected]_name:~/Desktop/ADB_install$ sudo chmod +x /usr/bin/adb
Don`t forget that USB Debugging MUST be enabled on your phone !!!
Connect your phone via USB cable and type this...
[email protected]_name:~$ adb devices
After that you can see that is your device properly connected to your computer and will see this...
List of devices attached
0123456789ABCDEF device
Close Terminal window.
Now, the ADB is finished to install on your linux OS and your phone is visible on computer.
Now we can go to update kernel...
Download kernel as you wish. I`m usin a MDJ kernel but if you can, you may use any other kernel.
Create new folder on your desktop and place all files from archive into this folder.
Rename folder to some simple name. In my case this folder is named newkernel
In MDJ kernel files is this...
zImage
bcm4329.ko
tun.ko
cifs.ko
fuse.ko
msm_rmnet.ko
nls_utf8.ko
Copy attached install_kernel.sh script and place it into the newkernel folder.
After that, all kernel files, modules and install_kernel.sh script must be in root of newkernel folder.
Open Terminal window and see something like this...
[email protected]_name:~$
Type...
[email protected]_name:~$ cd Desktop
[email protected]_name:~/Desktop$ cd newkernel
[email protected]_name:~/Desktop/newkernel$ sh install_kernel.sh
After finish and after see All Done!!! massage, you must to reboot yor phone and your new kernel is up.
Or just type in existing Terminal window...
[email protected]_name:~$ adb reboot
Enyoy !!!
FileFixer.

Hello I have a question. Is it possible to do this from teminal inside Android and after installing the new kernel to reboot? Thanks.

Sticky please
very usefull should be a sticky!

ogoglass said:
Hello I have a question. Is it possible to do this from teminal inside Android and after installing the new kernel to reboot? Thanks.
Click to expand...
Click to collapse
You need to mount and remoun your boot.img from NAND to SD card. Yaffs2 must be installed on android but i have not found anywher yaffs2 for ARM processor.
Maybe some other want to help with this. Rework the sh cript is not a major problem.

ADB was installed correctly... but the installation kernel not work for me:
~$ cd Desktop
~/Desktop$ cd newkernel
~/Desktop/newkernel$ sh install_kernel.sh
install_kernel.sh: 1: @echo: not found
Creating directory and mounting /boot...
mkdir failed for /data/boot, File exists
Pushing zImage...
1427 KB/s (2401156 bytes in 1.642s)
Remounting system and pushing modules...
remount succeeded
310 KB/s (272851 bytes in 0.857s)
1459 KB/s (185916 bytes in 0.124s)
failed to copy 'cifs.ko' to '/system/lib/modules/cifs.ko': No space left on device
1579 KB/s (635894 bytes in 0.393s)
1294 KB/s (120735 bytes in 0.091s)
619 KB/s (28764 bytes in 0.045s)
Cleaning up...
rmdir failed for /data/boot, Directory not empty
All done!
~/Desktop/newkernel$

FileFixer said:
You need to mount and remoun your boot.img from NAND to SD card. Yaffs2 must be installed on android but i have not found anywher yaffs2 for ARM processor.
Maybe some other want to help with this. Rework the sh cript is not a major problem.
Click to expand...
Click to collapse
mkyaffs2image command comes on most builds of android that are rooted

really cannot understand, please, advise for noob:
is this manual for Linux OS PC or Windows PC?
which exact Terminal you mean?

Excellent Job! Sticky for noobs!

dimdimdim said:
really cannot understand, please, advise for noob:
is this manual for Linux OS PC or Windows PC?
Click to expand...
Click to collapse
primarily for Linux,
I have run it under OSX
but ADB can run under everything.

internauta2000 said:
ADB was installed correctly... but the installation kernel not work for me:
~$ cd Desktop
~/Desktop$ cd newkernel
~/Desktop/newkernel$ sh install_kernel.sh
install_kernel.sh: 1: @echo: not found
Creating directory and mounting /boot...
mkdir failed for /data/boot, File exists
Pushing zImage...
1427 KB/s (2401156 bytes in 1.642s)
Remounting system and pushing modules...
remount succeeded
310 KB/s (272851 bytes in 0.857s)
1459 KB/s (185916 bytes in 0.124s)
failed to copy 'cifs.ko' to '/system/lib/modules/cifs.ko': No space left on device
1579 KB/s (635894 bytes in 0.393s)
1294 KB/s (120735 bytes in 0.091s)
619 KB/s (28764 bytes in 0.045s)
Cleaning up...
rmdir failed for /data/boot, Directory not empty
All done!
~/Desktop/newkernel$
Click to expand...
Click to collapse
This is correct on my PC...
~/Desktop/newkernel$ sh install_kernel.sh
install_kernel.sh: 1: @echo: not found
Creating directory and mounting /boot...
Pushing zImage...
1994 KB/s (2401156 bytes in 1.175s)
Remounting system and pushing modules...
remount succeeded
1809 KB/s (272851 bytes in 0.147s)
1775 KB/s (185916 bytes in 0.102s)
1951 KB/s (3056268 bytes in 1.529s)
1964 KB/s (635894 bytes in 0.316s)
1643 KB/s (120735 bytes in 0.071s)
663 KB/s (28764 bytes in 0.042s)
Cleaning up...
All done!
Do you have a rooted phone or you not have more free space on your phone?
Look at this line when start sh script...
mkdir failed for /data/boot, File exists
and this...
failed to copy 'cifs.ko' to '/system/lib/modules/cifs.ko': No space left on device

g30rg10u said:
primarily for Linux,
I have run it under OSX
but ADB can run under everything.
Click to expand...
Click to collapse
which are requirements for adb and how to run if I already have on my windows7 android sdk?

g30rg10u said:
primarily for Linux,
I have run it under OSX
but ADB can run under everything.
Click to expand...
Click to collapse
actually, adb.exe's window I'm trying to run under platform-tools disappears after a second.
what's my problem? (besides "invalid user", of course)

Ok...
The build is Gauner HD-FI 0.3 and understand that is routed by default ... Correct me if not...
With respect to free space on the phone, is a TMUS with 1024 Mb in ROM... shown that limited ... I do not know because it shows to have 431 Mb free...
This is what marks my last attempt:
...
install.sh: 1: @echo: not found
Creating directory and mounting /boot...
mkdir failed for /data/boot, File exists
Pushing zImage...
1653 KB/s (1708764 bytes in 1.009s)
Remounting system and pushing modules...
remount succeeded
1508 KB/s (272303 bytes in 0.176s)
1404 KB/s (184956 bytes in 0.128s)
failed to copy 'cifs.ko' to '/system/lib/modules/cifs.ko': No space left on device
1577 KB/s (633598 bytes in 0.392s)
1312 KB/s (117451 bytes in 0.087s)
654 KB/s (27800 bytes in 0.041s)
Cleaning up...
rmdir failed for /data/boot, Directory not empty
All done!
What confuses me even more you can look into the following screenshorts
It has installed the new kernel?

phoenixtraveller said:
FOR ALL THOSE WANTING UBUNTU/LINUX:
You just use DAF.EXE and DFT-Android (Desire original release with Magldr) partition layout.
Unyaffs BOOT.IMG and copy initrd.gz
Copy over ALL ubuntu \linux\ files to sdcard root (not \linux).
rename main adb_htc_leo_zimage to just zImage.
do not rename initrd.cpio.gz as ppl are doing: use initrd.gz from DFT' Android BOOT.IMG (unyaffs).
Now you can copy over all rootfs.ext2 to the appropriate partitions in NAND and Run.
Any suggestions on how to improve this?
Proper layout settings for flash.cfg?
I get to keyboard etc then cant use it (no usb connected - no touch).
But point is: IT WORKS AS LONG:
1) INITRD.GZ is Magldr compatible and matches flash.cfg/AD-NAND-partion (why I did this proof-of-concept with DFT's initrd)
2) rootfs.ext2 must now be mounted.
3) usb keyboard etc? internet? POWER?
self notes: for future ref: install magldr, do dft-droid-daf.exe, copy linux: ren htc_adb_zimage to just zImage. then. USE THE INITRD.GZ from inside DFT's BOOT.IMG. !!!
make magldr/ubuntu work: ad hardreset, install dft-android by daf.exe, copy all \linux\ files to root. rename files like so: (above)
Magldr and Ubuntu working: ok... You need to make sure your initrd.gz initial ramdisk is in sync with the nand partitioning by daf.exe so...
---
Update:
Hmmm.. Looks like--> It is mounting rootfs.ext2 --> by itself in - NAND? SDCARD? Will update but seems to have booted properly !!! Takes a LONG time and black screen etc for ages before "desktop" - mentions "adb" and other things in verbose output during "boot". Someone please let me know thoughts as I am nt kernel developer (drivers etc) and new to Linux. Thankyou. This is my first day on XDA. My first intro to all of this so sorry if over-posting or in wrong spot.
---
Update2:
Linux penguin screen verbose:
ANDROID unable to open persistent property directory
init: cannot find /system/...
(a lot of them)
then: enabling adb, adb open, et etc etc, host does not support read-only switch assuming write-enable...
mmc1: new high speed sdhc card at address b504
then a lot of lines with numbers microp set bkl(9) and ACR= FL= RAAC=
power button works as in screensaver/lock... this all leads up to keyboard and desktop eventually !!!
any ideas ?
Click to expand...
Click to collapse
It takes forever: but it is till going and ALIVE.
Can anyone please help getting Ubuntu/Linux up over Magldr-NAND/SD ***properly***?
Happy (as explained above) to make donation $$$.

Can you post a simple step by step guide for us Windows users?
I really dont know how to make it work.
Thanks.

i am getting a strange error after i connect the phone.
[email protected]:~/Desktop$ cd
ADB_install/ Backup/ Rom Android/
[email protected]:~/Desktop$ cd
ADB_install/ Backup/ Rom Android/
[email protected]:~/Desktop$ cd ADB_install/
[email protected]:~/Desktop/ADB_install$ sudo cp adb /usr/bin
[sudo] password for ionut:
[email protected]:~/Desktop/ADB_install$ sudo chmod +x /usr/bin/adb
[email protected]:~/Desktop/ADB_install$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
???????????? no permissions
[email protected]:~/Desktop/ADB_install$ adb devices
List of devices attached
???????????? no permissions
i am using on the phone this nand build: [03 Jan][NAND][data.img with copy from phone]LEO "Stock Desire" MOD
thanx

solved.
service MUST be started as root. if you are getting this error try this:
[email protected]:~$ sudo su -
[sudo] password for ionut: <<type root password >>
[email protected]:~# adb kill-server
[email protected]:~# adb start-server
[email protected]:~# adb devices
List of devices attached
0123456789ABCDEF device
seems it's working

The best way to install is to run on Root Terminal. This is placed on Applications -> System Tools.
On Ubuntu it is invisible and you must to enable it on System -> Preferences -> Main menu and make it visible.

[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:

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

[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