Related
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"
I have a mytouch 3g and it no longer boots into recovery. All I get it the first line:
Build : RA-saphire-v1.7.0G and nothing else.
The phone is still accessable via adb in recovery.
I have flashed recovery.img serveral times using fastboot but to know avail Looking at the kernel output, It appears that the mtdblock4 is corrupt and the recovery process hangs because of yaffs issues. Also just trying to mount /cache causes the command to hang.
Below is the relevant output:
Any suggestions on how to un-corrupt the cache partition?
[ 6.736572] Creating 6 MTD partitions on "msm_nand":
[ 6.736602] 0x0000024c0000-0x000002500000 : "misc"
[ 6.738555] 0x0000026c0000-0x000002bc0000 : "recovery"
[ 6.739868] 0x000002bc0000-0x000002e40000 : "boot"
[ 6.741058] 0x000002e40000-0x000008840000 : "system"
[ 6.742462] 0x000008840000-0x00000d840000 : "cache"
[ 6.743835] 0x00000d840000-0x000020000000 : "userdata"
..
[ 10.782379] yaffs: passed flags ""
[ 10.782714] yaffs: Attempting MTD mount on 31.4, "mtdblock4"
[ 12.179199] yaffs tragedy: Bad object type, 1 != 3, for object 4 at chunk 21738 during scan
[ 12.179901] ==>> yaffs bug: fs/yaffs2/yaffs_guts.c 6666
[ 12.180511] ==>> yaffs bug: fs/yaffs2/yaffs_guts.c 6666
[ 12.719390] yaffs tragedy: Bad object type, 1 != 3, for object 265 at chunk 17735 during scan
[ 13.914916] Unable to handle kernel paging request at virtual address cd7c40e4
**** RECOVERY HANGS HERE ******
gustden said:
I have a mytouch 3g and it no longer boots into recovery. All I get it the first line:
Build : RA-saphire-v1.7.0G and nothing else.
The phone is still accessable via adb in recovery.
I have flashed recovery.img serveral times using fastboot but to know avail Looking at the kernel output, It appears that the mtdblock4 is corrupt and the recovery process hangs because of yaffs issues. Also just trying to mount /cache causes the command to hang.
Below is the relevant output:
Any suggestions on how to un-corrupt the cache partition?
[ 6.736572] Creating 6 MTD partitions on "msm_nand":
[ 6.736602] 0x0000024c0000-0x000002500000 : "misc"
[ 6.738555] 0x0000026c0000-0x000002bc0000 : "recovery"
[ 6.739868] 0x000002bc0000-0x000002e40000 : "boot"
[ 6.741058] 0x000002e40000-0x000008840000 : "system"
[ 6.742462] 0x000008840000-0x00000d840000 : "cache"
[ 6.743835] 0x00000d840000-0x000020000000 : "userdata"
..
[ 10.782379] yaffs: passed flags ""
[ 10.782714] yaffs: Attempting MTD mount on 31.4, "mtdblock4"
[ 12.179199] yaffs tragedy: Bad object type, 1 != 3, for object 4 at chunk 21738 during scan
[ 12.179901] ==>> yaffs bug: fs/yaffs2/yaffs_guts.c 6666
[ 12.180511] ==>> yaffs bug: fs/yaffs2/yaffs_guts.c 6666
[ 12.719390] yaffs tragedy: Bad object type, 1 != 3, for object 265 at chunk 17735 during scan
[ 13.914916] Unable to handle kernel paging request at virtual address cd7c40e4
**** RECOVERY HANGS HERE ******
Click to expand...
Click to collapse
Did you try to install recovery via ROM Manager (acceable at market)??? And you must have root to do it. If you dont go to the www.theunlockr.com and how to's section has everything for magic
I have tried everything I can think of. Here is my lastest attempt:
1. Flash sappimg.zip using goldcard ( to get fastboot access )
2. Flashed recovery.img via fastboot
3. Flashed hboot.nb0 via fastboot
4. Flashed boot.img via fastboot
The phone does not boot, so installing anyting from market is impossible.
If you look at the output in the original post, booting into recovery fails trying to mount the CACHE partion. Is there any way to zero out the nand memory in the cache segment?
Try this:
Code:
fastboot erase cache
fastboot erase system
fastboot erase boot
fastboot erase data
It failed when I initially tried to do a fastboot erase cache...
I was able to create a file the size of cache space, consisting of all 0x00s and flashed that to the cache partition.
It gave me an error about no space left on the device, but now the "fastboot erase cache" works just fine I would think that both do the same thing!
Many thanks, everything seems normal at the moment!!!
Hi
I am having the same problem where mtdblock4 is corrupt (a crash just after flashing a rom)
Having a mt3g Fender I am s-on
I am not having any luck with the gold card I keep getting 'model ID incorrect'.. I have tried 2 sdcards many times..
is there anyway I can do this from adb? I am pretty much out of ideas.. I will keep at the gold card problem.. I made a gold card successfully for the initial rooting
any help is much appreciated
Edit:
Ok I managed to get this fixed without a goldcard!
I unzipped Ohsaka-SuperWipe_v2.zip
then used adb to push erase_image and SuperWipe.sh to /tmp/SuperWipe
chmod +x those then ./SuperWipe.sh
and problem solved..
what a PITA!
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...
So I have tried to root this device for about 5 hours now and I am at the end of my rope... I have downloaded and used the tool provided by rootjunkie to root this device. I get to the point where it tried to inject the root and this is the result of that.... but the read out is telling me that the changes trying to be made to the SU is that the operation is not permitted.
Will post CMD prompt below..
ANY help would be lovely, as my kindle now has supersu but it says my binary needs to be updated and when I use root check it shows I am not rooted... Thanks for the help in advance from a noobie.
The following is in my CMD prompt:
[*] NOTE this will not work unless your fastboot drivers are installed[*] see option 1 ADB Driver install.[*] Once the screen is black and says fastboot in the corner[*] press and key to continue the script.
--------------------------------------------------------------------------------
< waiting for device >
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.010s]
finished. total time: 0.010s
resuming boot...
OKAY [ -0.000s]
finished. total time: -0.000s
--------------------------------------------------------------------------------
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
remount succeeded
2374 KB/s (170232 bytes in 0.070s)
1 KB/s (1976 bytes in 1.000s)
3679 KB/s (75364 bytes in 0.020s)
3453 KB/s (5904943 bytes in 1.670s)
1463 KB/s (29972 bytes in 0.020s)
mkdir failed for /system/app/SuperSU, File exists
mkdir failed for /system/bin/.ext, File exists
cp: /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: Operati
on not permitted
cp: /system/xbin/daemonsu: Text file busy
cp: /system/xbin/supolicy: Operation not permitted
Unable to chmod /system/xbin/supolicy: Operation not permitted
chcon: Could not label /system/xbin/supolicy with ubject_r:system_file:s0: O
peration not permitted
cp: /system/bin/app_process32_original: Text file busy
--------------------------------------------------------------------------------
[*] Once the screen is black and says fastboot in the corner[*] press and key to continue the script.
--------------------------------------------------------------------------------
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.010s]
finished. total time: 0.010s
resuming boot...
OKAY [ 0.000s]
finished. total time: 0.000s
--------------------------------------------------------------------------------
[*] your device is rebooting and will finish the root process.
--------------------------------------------------------------------------------
remount succeeded
--------------------------------------------------------------------------------
[*] one last reboot to finish process
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
[*] process finished now just wait for your device to fully boot up[*] this will take some time if you are on the Optimizing system screen.[*] NOTE now that you have root please block ota updates option 4[*] so that you can keep it safe.
--------------------------------------------------------------------------------
Press any key to continue . . .[*] RootJunky OUT
hit ENTER to return to start:
hurddude said:
So I have tried to root this device for about 5 hours now and I am at the end of my rope... I have downloaded and used the tool provided by rootjunkie to root this device. I get to the point where it tried to inject the root and this is the result of that.... but the read out is telling me that the changes trying to be made to the SU is that the operation is not permitted.
Will post CMD prompt below..
ANY help would be lovely, as my kindle now has supersu but it says my binary needs to be updated and when I use root check it shows I am not rooted... Thanks for the help in advance from a noobie.
The following is in my CMD prompt:
[*] NOTE this will not work unless your fastboot drivers are installed
[*] see option 1 ADB Driver install.
[*] Once the screen is black and says fastboot in the corner
[*] press and key to continue the script.
--------------------------------------------------------------------------------
< waiting for device >
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.010s]
finished. total time: 0.010s
resuming boot...
OKAY [ -0.000s]
finished. total time: -0.000s
--------------------------------------------------------------------------------
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
remount succeeded
2374 KB/s (170232 bytes in 0.070s)
1 KB/s (1976 bytes in 1.000s)
3679 KB/s (75364 bytes in 0.020s)
3453 KB/s (5904943 bytes in 1.670s)
1463 KB/s (29972 bytes in 0.020s)
mkdir failed for /system/app/SuperSU, File exists
mkdir failed for /system/bin/.ext, File exists
cp: /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: Operati
on not permitted
cp: /system/xbin/daemonsu: Text file busy
cp: /system/xbin/supolicy: Operation not permitted
Unable to chmod /system/xbin/supolicy: Operation not permitted
chcon: Could not label /system/xbin/supolicy with ubject_r:system_file:s0: O
peration not permitted
cp: /system/bin/app_process32_original: Text file busy
--------------------------------------------------------------------------------
[*] Once the screen is black and says fastboot in the corner
[*] press and key to continue the script.
--------------------------------------------------------------------------------
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.010s]
finished. total time: 0.010s
resuming boot...
OKAY [ 0.000s]
finished. total time: 0.000s
--------------------------------------------------------------------------------
[*] your device is rebooting and will finish the root process.
--------------------------------------------------------------------------------
remount succeeded
--------------------------------------------------------------------------------
[*] one last reboot to finish process
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
[*] process finished now just wait for your device to fully boot up
[*] this will take some time if you are on the Optimizing system screen.
[*] NOTE now that you have root please block ota updates option 4
[*] so that you can keep it safe.
--------------------------------------------------------------------------------
Press any key to continue . . .
[*] RootJunky OUT
hit ENTER to return to start:
Click to expand...
Click to collapse
which fire do you have?
Sent from my KFFOWI using Tapatalk
sd_shadow said:
which fire do you have?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Well under the device options it says:
Device model:
fire (5th generation) it's the 7 inch tablet sold this past Christmas.
&
I am running the Fire OS v5.1.1
Do you need any more info?
hurddude said:
Well under the device options it says:
Device model:
fire (5th generation) it's the 7 inch tablet sold this past Christmas.
&
I am running the Fire OS v5.1.1
Do you need any more info?
Click to expand...
Click to collapse
This is the link to correct forum
http://forum.xda-developers.com/amazon-fire/help
Also
[Videos] Tutorials on how to root, flash roms and more on the Amazon Fire 5th gen.
Sent from my XT1060 using Tapatalk
I am also looking to root these devices, I have been working very hard at replacing the default firelauncher with a third party one, without the need to root. If you're interested in collaborating take a peek at my thread:
http://forum.xda-developers.com/hd8...zon-fire-hd-8-10-remove-firelauncher-t3286646
If you need anything tested on my HD 8 device, please let me know and I will do so promptly.
I still have not been successful with this root, after installing the correct adb and the software to root still getting the same errors spitting out in the cmd prompt. Any idea as to why it not letting me replace the SU!?
hurddude said:
I still have not been successful with this root, after installing the correct adb and the software to root still getting the same errors spitting out in the cmd prompt. Any idea as to why it not letting me replace the SU!?
Click to expand...
Click to collapse
If you have the 7" display Fire you are in the wrong forum. If you have an HD 8/10 then there is currently no root available.
hello
i have a lg v20 h990ds and i want to install twrp for install custom rom on my Phone
i Download Version 7 Android Firmware KDZ and Downgrade with lg up from android 8 to 7 and After try for install twrp recovery fail !
i,m downloaded any rev of android 7 kdz and flash with lg up and try to install twrp is fail !
list android 7 KDZ Rev i downloaded and try :
H990ds10h_00_OPEN_AME_DS_OP_0117.kdz
H990ds10e_00_OPEN_AME_DS_OP_0417.kdz
H990ds10b_00_OPEN_AME_DS_OP_1103.kdz
H990ds10d_00_OPEN_AME_DS_OP_1216.kdz
after flash firmware with lgup i try to install twrp have this Problem :
Step 1 :
C:\adb>step1.bat
C:\adb>adb push dirtysanta /storage/emulated/0
654 KB/s (18760 bytes in 0.027s)
C:\adb>adb push aboot.img /storage/emulated/0
2219 KB/s (2097152 bytes in 0.922s)
C:\adb>adb push dirtycow /data/local/tmp
1218 KB/s (9984 bytes in 0.008s)
C:\adb>adb push my-run-as /data/local/tmp
1349 KB/s (13796 bytes in 0.009s)
C:\adb>adb shell chmod 0777 /data/local/tmp/*
C:\adb>adb shell /data/local/tmp/dirtycow /system/bin/run-as /data/local/tmp/my-run-as
warning: new file size (13796) and file old size (14360) differ
size 14360
[*] mmap 0x743cc53000
[*] exploit (patch)
[*] currently 0x743cc53000=10102464c457f
[*] madvise = 0x743cc53000 14360
[*] madvise = 0 1048576
[*] /proc/self/mem -2122317824 1048576
[*] exploited 0x743cc53000=10101464c457f
C:\adb>adb shell /data/local/tmp/dirtycow /system/bin/applypatch /data/local/tmp/dirtycow
warning: new file size (9984) and file old size (165144) differ
size 165144
[*] mmap 0x76d9697000
[*] exploit (patch)
[*] currently 0x76d9697000=10102464c457f
[*] madvise = 0x76d9697000 165144
[*] madvise = 0 1048576
[*] /proc/self/mem 1367343104 1048576
[*] exploited 0x76d9697000=10102464c457f
C:\adb>adb shell
elsa:/ $ run-as con
elsa:/ # chmod 0777 /storage/emulated/0/*
elsa:/ # id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:shell:s0
elsa:/ #
Step 2 :
C:\adb>step2.bat
C:\adb>adb pull /storage/emulated/0/bootbackup.img
remote object '/storage/emulated/0/bootbackup.img' does not exist
C:\adb>adb pull /storage/emulated/0/abootbackup.img
remote object '/storage/emulated/0/abootbackup.img' does not exist
C:\adb>adb reboot bootloader
Step 3 :
C:\adb>step3.bat
C:\adb>fastboot flash boot boot1.img
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.341s]
writing 'boot'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.365s
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (24964 KB)...
OKAY [ 0.828s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.854s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.009s
Please help me to resolve this problem
Thanks , Regards
mo4sa said:
Please help me to resolve this problem
Click to expand...
Click to collapse
The solution to your problem it's simple enough... You don't follow the instructions the way they are supposed to be follow.
This thread you open about the TWRP failed to install, but it's failing to unlock your device, and it has an entire thread about it. Recently there's one user who has some problems on how to perform this unlock and since I'll not write again (because you and everyone can search ) So this is my most recent post with my considerations/instructions.
How can I say with confidence that you aren't following the instructions? Because on the same thread the most appropriate guide for the H990DS (I have the same device by the way) don't need the step3. And this clear message device is locked, so the unlock failed.
So take your time, read with care and attention what was already discussed on the links that I share here, and if you still have problems, post to the right thread and we can continue this discussion there so others could benefit of this experience as well.