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"

Unsuccessfull root on lg g2 f320k20f

Hi,
2nd time trying to root but still some message about can't reate, start and failed to copy. Full results below also. I've use the files and methods heree:
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=45693809&nocache=1
Mounting system, pushing su binary and installing SuperSu...
2244 KB/s (1085140 bytes in 0.472s)
cp: can't create '/system/xbin/busybox': Read-only file system
failed to copy 'su' to '/system/xbin/daemonsu': Read-only file system
cp: can't stat '/system/xbin/daemonsu': No such file or directory
failed to copy 'install-recovery.sh' to '/system/etc/install-recovery.sh': Read-
only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to open /system/xbin/su: No such file or directory
Rebooting Phone.
***************************************************
***************************************************
You should hopefully now be fully rooted!!
Wait for your device to reboot and continue
with ioroot script to backup EFS...
***************************************************
***************************************************
/sdcard/modemst1.img: cannot open for write: Read-only file system
/sdcard/modemst2.img: cannot open for write: Read-only file system
remote object '/sdcard/modemst1.img' does not exist
remote object '/sdcard/modemst2.img' does not exist
++++++++++++++++++++++++++++++++++++++++FULL RESULT START+++++++++++++++++++++++++++
======adbd is already running as root
uid=0(root) gid=0(root) context=u:r:shell:s0
If you do NOT see uid=0(root) gid=0(root) above then
it is likely your device firmware is not supported or
USB mode was not toggled properly. You can try to
run the script again.
Press CTRL+c to stop this script...
If you DO see uid=0(root) gid=0(root) mentioned above...
CONGRATS.. Rooted ADB is now confirmed.
You will have a rooted ADB shell but no apps on the
phone will
'be' is not recognized as an internal or external command,
operable program or batch file.
PRESS ENTER to continue with full root.
PLEASE NOTE!
Continuing with full root can trip LG's rootchecker.
This means your phone will show ROOTED in Download mode.
You can remove root flag by flashing stock firmware...
.bin .tot or .kdz
If you do not want to possibly invalidate your warranty
press CTRL+c to stop this script...
*******************************************************
Press any key to continue . . .
Mounting system, pushing su binary and installing SuperSu...
2244 KB/s (1085140 bytes in 0.472s)
cp: can't create '/system/xbin/busybox': Read-only file system
failed to copy 'su' to '/system/xbin/daemonsu': Read-only file system
cp: can't stat '/system/xbin/daemonsu': No such file or directory
failed to copy 'install-recovery.sh' to '/system/etc/install-recovery.sh': Read-
only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to open /system/xbin/su: No such file or directory
Rebooting Phone.
***************************************************
***************************************************
You should hopefully now be fully rooted!!
Wait for your device to reboot and continue
with ioroot script to backup EFS...
***************************************************
***************************************************
/sdcard/modemst1.img: cannot open for write: Read-only file system
/sdcard/modemst2.img: cannot open for write: Read-only file system
remote object '/sdcard/modemst1.img' does not exist
remote object '/sdcard/modemst2.img' does not exist
***************************************************
***************************************************
EFS partitions now in ioroot folder on computer...
They are named modemst1.img and modemst2.img
They will come in handy in case of an emergency.
Store them somewhere you won't lose them.
IOroot is now complete.
***************************************************
***************************************************
Press any key to continue . . .
++++++++++++++++++++++FULL RESULT END++++++++++++++++++++

Same problem here, no solution yet.

LG G2 root
Hello guys,
is there any solution for this? I have same issue
Thank you

[Q] TWRP flashable ZIP for VS980 failed to flash under TWRP

This seems to be an old problem.
My VS980 is on TWRP v2.8.0.1, and I see there is a newer TWRP from the official site: openrecovery-twrp-2.8.1.0-vs980.zip
So I downloaded that and put it on sdcard, by "installing" this zip, the error was as follows:
Code:
Installing '/usb_otg/ROM/openrecovery-twrp-2.8.1.0-vs980.zip'...
Checking for MD5 file...
MD5 matched
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
*******************************
* TWRP Recovery by Dees_Troy *
*******************************
minzip: Extracted file "/tmp/loki.sh"
minzip: Extracted file "/tmp/loki/loki_flash"
minzip: Extracted file "/tmp/loki/loki_patch"
about to run program [/tmp/loki.sh] with 1 args
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.033627 seconds, 29.7MB/s
[+] loki_patch v2.1
[-] Unsupported aboot image.
run_program: child exited with status 1
script aborted: assert failed: run_program("/tmp/loki.sh") == 0
assert failed: run_program("/tmp/loki.sh") == 0
Is it because my aboot is already lokified? Or am I doing the upgrade wrong?

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

Moto E4 (Qualcomm) new september update?

It looks like a new update is out for the Qualcomm, factory unlocked version of the Moto E4. I see the update number as "npqs26.69-27-3" and a description of "Security updates through September 1, 2017".
Anyone know how the update can be applied for those of us that are rooted? Has anyone already performed the update? Any issues to report?

You have to go fully stock to update. Probably will involve wiping the device.

I have the Verizon variant Moto E4, bought from Walmart in $40 deal in August, unlocked from eBay and then it started working for me for my AT&T SIM, yesterday I mistakenly updated the same to NDQ26.69-23-3 and now it is not working for my AT&T Sim. can anyone suggest what to do ? Has anyone run into this issue ?

Update unsuccessful on unlocked and rooted Moto E4 Qualcomm Perry
I have a moto e4 (qualcomm, perry) bought from Amazon (unlocked, no added) and have a CDMA trackfone-verizon sim. Phone is working fine, but the update will not apply. It gives me an error and indicates the update was unsuccessful. The bootloader is unlocked and the phone is rooted.
The issue seems to be the sha1 sum of by boot partition (see last_log below). I downloaded the stock rom for this device from https :// firmware.center/firmware/Motorola/Moto%20E4/Stock/
I believe the right one is PERRY_NPQ26.69-27_cid50_subsidy-DEFAULT_regulatory-XT1768_CFC_CANADA.xml.zip because Settings->About Phone->Build number is "NPQ26.69-27" and cat /proc/cpuinfo indicates "Device: perry". Does anybody else find it frustrating that I cannot get this file directly from motorola?
Inside that zip is a boot.img file. The sha1 sum of that file (computed with openssl sha1 boot.img) is 8f6e5f9814b84c48054bc9fd3df9f91610b85e09, which exactly matches the red text in the log file below. Also the length, 16777216, matches my current boot partition to the byte. I was hoping that simply writing this to the boot partition would fix the issue, but that was a big mistake. I copied the file to the phone and executed:
$ dd if=/dev/block/bootdevice/by-name/boot of=boot.img.orig #to save a backup of the original partition
$ dd if=boot.img of=/dev/block/bootdevice/by-name/boot
this bricked the device and it wouldn't boot. Didn't even make it to the Motorola splash screen. After some digging I was able to use fastboot on my PC to restore the boot.img.orig using:
PC$ fastboot flash:raw boot boot.img.orig
This restored the device to functioning order, but I was still not able to install the update. After this, tried to boot the stock boot image without flashing it using:
PC$ fastboot boot boot.img
This caused it to hang forever at the blue motorola splash screen. Power cycling cleared the issue as expected.
As you probably guessed by now, I am an experienced linux user, but new to android and really don't know what I am doing. @madbat99 suggests that I will have to flash the complete stock rom, wiping the device. I know how to backup, both with a backup app and with twrp, so wiping won't be a huge issue. Does anybody know how to flash a full rom? I am using gentoo linux and have fastboot and adb installed and can communicate with the bootloader, I have just never flashed a phone before. Should I expect to have to relock the bootloader for the update to apply? Afterwords, I am going to have to re-unlock the bootloader, re-root the device and then restore all my backups, correct?
I really want to apply this update due to the large gaping security holes it patches.
The relevant section of /cache/recovery/last_log are: (I bolded what I think is the real error)
[ 1.687300] I:whole-file signature verified against RSA key 0
[ 1.687314] I:verify_file returned 0
[ 1.687376] Installing update...
[ 1.729707] installing gptupgrade updater extensions
[ 1.739414] file_contexts.bin is taken from /file_contexts.bin
[ 1.740818] Mount command parameters gotten in updater script
[ 1.740855] mount point :/oem location: /dev/block/bootdevice/by-name/oem , file system type :ext4
[ 1.741029] secontext for the mount point /oem is ubject_remfs:s0
[ 1.744665] Source: motorola/perry/perry:7.1.1/NPQ26.69-27/31:user/release-keys
[ 1.744695] Target: motorola/perry/perry:7.1.1/NPQS26.69-27-3/3:user/release-keys
[ 1.744704] Verifying current system...
[ 2.115566] contents of partition "/dev/block/bootdevice/by-name/boot" didn't match EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938
[ 2.115605] file "EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938" doesn't have any of expected sha1 sums; checking cache
[ 2.115664] failed to stat "/cache/saved.file": No such file or directory
[ 2.115675] failed to load cache file
[ 2.115687] dump_badfile is failed: EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938 is not present
[ 2.115720] script aborted: E3005: "EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938" has unexpected contents.
[ 2.154752] E:Error in /cache/Blur_Version.26.11.31.perry.retail.en.US.zip
[ 2.154825] (Status 7)
[ 2.187583]
[ 2.209427] W:failed to read uncrypt status: No such file or directory
[ 2.209642] I:/cache/Blur_Version.26.11.31.perry.retail.en.US.zip
[ 2.209652] 0
[ 2.209660] time_total: 1
[ 2.209668] retry: 0
[ 2.209675] target_build: 3
[ 2.209682] source_build: 31
[ 2.209689] error: 3005
[ 2.209699] Installation aborted.

maurerpe said:
I have a moto e4 (qualcomm, perry) bought from Amazon (unlocked, no added) and have a CDMA trackfone-verizon sim. Phone is working fine, but the update will not apply. It gives me an error and indicates the update was unsuccessful. The bootloader is unlocked and the phone is rooted.
The issue seems to be the sha1 sum of by boot partition (see last_log below). I downloaded the stock rom for this device from https :// firmware.center/firmware/Motorola/Moto%20E4/Stock/
I believe the right one is PERRY_NPQ26.69-27_cid50_subsidy-DEFAULT_regulatory-XT1768_CFC_CANADA.xml.zip because Settings->About Phone->Build number is "NPQ26.69-27" and cat /proc/cpuinfo indicates "Device: perry". Does anybody else find it frustrating that I cannot get this file directly from motorola?
Inside that zip is a boot.img file. The sha1 sum of that file (computed with openssl sha1 boot.img) is 8f6e5f9814b84c48054bc9fd3df9f91610b85e09, which exactly matches the red text in the log file below. Also the length, 16777216, matches my current boot partition to the byte. I was hoping that simply writing this to the boot partition would fix the issue, but that was a big mistake. I copied the file to the phone and executed:
$ dd if=/dev/block/bootdevice/by-name/boot of=boot.img.orig #to save a backup of the original partition
$ dd if=boot.img of=/dev/block/bootdevice/by-name/boot
this bricked the device and it wouldn't boot. Didn't even make it to the Motorola splash screen. After some digging I was able to use fastboot on my PC to restore the boot.img.orig using:
PC$ fastboot flash:raw boot boot.img.orig
This restored the device to functioning order, but I was still not able to install the update. After this, tried to boot the stock boot image without flashing it using:
PC$ fastboot boot boot.img
This caused it to hang forever at the blue motorola splash screen. Power cycling cleared the issue as expected.
As you probably guessed by now, I am an experienced linux user, but new to android and really don't know what I am doing. @madbat99 suggests that I will have to flash the complete stock rom, wiping the device. I know how to backup, both with a backup app and with twrp, so wiping won't be a huge issue. Does anybody know how to flash a full rom? I am using gentoo linux and have fastboot and adb installed and can communicate with the bootloader, I have just never flashed a phone before. Should I expect to have to relock the bootloader for the update to apply? Afterwords, I am going to have to re-unlock the bootloader, re-root the device and then restore all my backups, correct?
I really want to apply this update due to the large gaping security holes it patches.
The relevant section of /cache/recovery/last_log are: (I bolded what I think is the real error)
[ 1.687300] I:whole-file signature verified against RSA key 0
[ 1.687314] I:verify_file returned 0
[ 1.687376] Installing update...
[ 1.729707] installing gptupgrade updater extensions
[ 1.739414] file_contexts.bin is taken from /file_contexts.bin
[ 1.740818] Mount command parameters gotten in updater script
[ 1.740855] mount point :/oem location: /dev/block/bootdevice/by-name/oem , file system type :ext4
[ 1.741029] secontext for the mount point /oem is ubject_remfs:s0
[ 1.744665] Source: motorola/perry/perry:7.1.1/NPQ26.69-27/31:user/release-keys
[ 1.744695] Target: motorola/perry/perry:7.1.1/NPQS26.69-27-3/3:user/release-keys
[ 1.744704] Verifying current system...
[ 2.115566] contents of partition "/dev/block/bootdevice/by-name/boot" didn't match EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938
[ 2.115605] file "EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938" doesn't have any of expected sha1 sums; checking cache
[ 2.115664] failed to stat "/cache/saved.file": No such file or directory
[ 2.115675] failed to load cache file
[ 2.115687] dump_badfile is failed: EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938 is not present
[ 2.115720] script aborted: E3005: "EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938" has unexpected contents.
[ 2.154752] E:Error in /cache/Blur_Version.26.11.31.perry.retail.en.US.zip
[ 2.154825] (Status 7)
[ 2.187583]
[ 2.209427] W:failed to read uncrypt status: No such file or directory
[ 2.209642] I:/cache/Blur_Version.26.11.31.perry.retail.en.US.zip
[ 2.209652] 0
[ 2.209660] time_total: 1
[ 2.209668] retry: 0
[ 2.209675] target_build: 3
[ 2.209682] source_build: 31
[ 2.209689] error: 3005
[ 2.209699] Installation aborted.
Click to expand...
Click to collapse
I hate to quote a post that long but you cannot install an official update on a rooted device with custom recovery.
If you have the correct firmware for your device, you need to extract it, rename .xml files to .img and flash with fastboot.
But it really needs to be correct firmware. I don't know the correct one for your device.
Might help
---------- Post added at 09:12 PM ---------- Previous post was at 09:00 PM ----------

z82anu said:
I have the Verizon variant Moto E4, bought from Walmart in $40 deal in August, unlocked from eBay and then it started working for me for my AT&T SIM, yesterday I mistakenly updated the same to NDQ26.69-23-3 and now it is not working for my AT&T Sim. can anyone suggest what to do ? Has anyone run into this issue ?
Click to expand...
Click to collapse
i have the verizon variant and updated to this patch back in October when it came out and i'm still using my cricket sim in it with no problems. are you still having the issue?

madbat99 said:
I hate to quote a post that long but you cannot install an official update on a rooted device with custom recovery.
If you have the correct firmware for your device, you need to extract it, rename .xml files to .img and flash with fastboot.
But it really needs to be correct firmware. I don't know the correct one for your device.
Might help
---------- Post added at 09:12 PM ---------- Previous post was at 09:00 PM ----------
Click to expand...
Click to collapse
Thank you @madbat99 . Using this method I was able to flash back to stock and install the update. The update works fine with my tracfone-verizon sim. I am not having the issue reported by @z82anu
To automate the process, I wrote a perl script that parses the servicefile.xml or flashfile.xml, verifies all the steps are valid, verifies that all files exist, verifies the md5 sums, and then executes the appropriate fastboot commands. It can be downloaded from https://github.com/maurerpe/stock-flash Hopefully, this will help other linux users looking to flash back to stock. Should work on window and Mac as well, but I haven't tested it.