here is the exploid.c file, the problem is that tha x8 and x10 have different drivers and etc. pls help to rewrite this script to exploid.
the wrong is:
memset(pwd, 0, sizeof(pwd));
readlink("/proc/self/fd/0", pwd, sizeof(pwd));
if (strncmp(pwd, "/dev/pts/", 9) != 0)
in my phone there is not self folder in my proc directory. where is it?
a programmer and android pro can make exploid for x8.
*update:
in fact, i am compiling it to xperia x8. i hope it will woork.
..good info.. please make for x8
What is it trying to exploit?
a-k-t-w said:
What is it trying to exploit?
Click to expand...
Click to collapse
Did you read the title? "help to exploid to root x8 2.1" its to properly root 2.1 i believe...
I uh. I meant, how is it trying to achieve the exploit. Udev exploit?
Edit: How recent is the exploit?
and is it work? i think no
the exploit is for CVE-2009-1185 and it's probably patched. here's the output.
$ cd sqlite_stmt_journals
$ ./exploid
[*] Android local root exploid (C) The Android Exploid Crew
[+] Using basedir=/sqlite_stmt_journals, path=/sqlite_stmt_journals/exploid
[+] opening NETLINK_KOBJECT_UEVENT socket
[-] bind: Address already in use
$ ./exploid
[*] Android local root exploid (C) The Android Exploid Crew
[+] Using basedir=/sqlite_stmt_journals, path=/sqlite_stmt_journals/exploid
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.
there is no triggering. the /proc/self/fd/0 is present on my device:
$ ls -l /proc/self/fd
lrwx------ shell shell 2010-12-15 23:22 0 -> /dev/pts/4
i've got it too, but it's didn't work. as say sonty, google patched this hole
Hmm, I figured as much.
thank you.
Thanks for what?
Hi,
AAHK is failing on my Desire HD. Can someone please help. This is my first ever try to ROOT. Thanks.
Android version 2.3.5
HTC Sense version: 3.0
Software number: 3.12.405.1
Kernel version: 2.6.35.10-g931a37e
[email protected] #1
Wed Nov 9 14.04.03 CST 2011
Baseband version: 12.65.60.29U_26.14.04.28_M
Build number: 3.12.405.1 CL199157 release-keys
AND here is whats failing:
Ace Advanced Hack Kit [Linux/OSX/Windows] attn1 2011/2012
___________________________
MAIN MENU | |
| Only ONE Menu Step to: |
1 - Hack Ace <----------------------------+ * S-OFF |
| * SIM Unlock |
2 - DONATE (Encouraged, but optional) | * SuperCID |
psas.revskills.de/?q=goldcard | * Root |
eff.org | * Busybox |
| |
************************************************** ********************
o - Options Menu (Return to Stock, Flash radios, etc)
************************************************** ********************
t - Toggle Flash Method - current method is fastbootRUU
************************************************** *******************
q - Quit
[Select and press Enter]1
3.12.405.1
This version of Android cannot use the hack kit at this time.
You can downgrade if you like, then rerun the hack step.
WARNING: THIS WILL WIPE DATA
[Would you like to downgrade? y/n]y
Download this RUU? [y,n]y
--2012-09-06 10:37:22-- tau.shadowchild.nl/files/PD98IMG-GB2.zip
Resolving tau.shadowchild.nl... 176.9.40.154
Connecting to tau.shadowchild.nl|176.9.40.154|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 259503624 (247M) [application/zip]
Saving to: `PD98IMG/PD98IMG-GB2.zip'
100%[======================================>] 259,503,624 4.62M/s in 83s
2012-09-06 10:38:45 (2.99 MB/s) - `PD98IMG/PD98IMG-GB2.zip' saved [259503624/259
503624]
a67daa6baa7ef085307593fef6329d14 *PD98IMG/PD98IMG-GB2.zip
Flash the downgrade RUU? [y,n]y
pushing rom to sdcard - this takes time please be patient.
1532 KB/s (259503624 bytes in 165.328s)
Setting up to temproot....
cannot stat 'tools/bin/zergRush': No such file or directory
2320 KB/s (572752 bytes in 0.241s)
1174 KB/s (19240 bytes in 0.016s)
going for temproot using zergRush....
/data/local/tmp/zergRush: not found
setting mainver lower for downgrade...
--set_version set. VERSION will be changed to: 1.31.405.6
Misc partition is "/dev/block/mmcblk0p17"
Patching and backing up misc partition...
Error opening input file.
Creating goldcard....
HTC android goldcard tool Copyright (C) 2011, Wayne D. Hoxsie Jr.
Original code by B. Kerler. Special thanks to ATTN1 and the XDA team.
Donations can be made to the Electronic Frontier Foundation:
eff.org/
or to B. Kerler:
psas.revskills.de
/dev/block/mmcblk1: cannot open for write: Permission denied
starting downgrade...
** The phone will now reboot into HBOOT.
** It will then check the file just sent.
** If everything is okay, the phone will
** prompt you to continue by pressing
** VOLUME UP. It will reboot, flashing twice.
**** PUSH POWER WHEN THIS STEP COMPLETES ****
If downgrade is successful, you may set up the phone and try to hack it again.
Once the downgrade is successful, press a key to return to the menu......
Otherwise, cut and paste the output to the screen into a text file for evaluatio
n.... then press a key.
Press any key to continue . . .
AND THE DISPLAY ON PHONE -- ON A WHITE SCREEN
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011,19:06:24
HBOOT
Main Version is older!
Update Fail
Press <POWER> to reboot.
--------------------------------------------------------
Would really apperciate some guidance in sorting this out. Thanks. Val.
valmiki.biswas said:
Hi,
AAHK is failing on my Desire HD. Can someone please help. This is my first ever try to ROOT. Thanks.
Android version 2.3.5
HTC Sense version: 3.0
Software number: 3.12.405.1
Kernel version: 2.6.35.10-g931a37e
[email protected] #1
Wed Nov 9 14.04.03 CST 2011
Baseband version: 12.65.60.29U_26.14.04.28_M
Build number: 3.12.405.1 CL199157 release-keys
AND here is whats failing:
Ace Advanced Hack Kit [Linux/OSX/Windows] attn1 2011/2012
___________________________
MAIN MENU | |
| Only ONE Menu Step to: |
1 - Hack Ace <----------------------------+ * S-OFF |
| * SIM Unlock |
2 - DONATE (Encouraged, but optional) | * SuperCID |
psas.revskills.de/?q=goldcard | * Root |
eff.org | * Busybox |
| |
************************************************** ********************
o - Options Menu (Return to Stock, Flash radios, etc)
************************************************** ********************
t - Toggle Flash Method - current method is fastbootRUU
************************************************** *******************
q - Quit
[Select and press Enter]1
3.12.405.1
This version of Android cannot use the hack kit at this time.
You can downgrade if you like, then rerun the hack step.
WARNING: THIS WILL WIPE DATA
[Would you like to downgrade? y/n]y
Download this RUU? [y,n]y
--2012-09-06 10:37:22-- tau.shadowchild.nl/files/PD98IMG-GB2.zip
Resolving tau.shadowchild.nl... 176.9.40.154
Connecting to tau.shadowchild.nl|176.9.40.154|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 259503624 (247M) [application/zip]
Saving to: `PD98IMG/PD98IMG-GB2.zip'
100%[======================================>] 259,503,624 4.62M/s in 83s
2012-09-06 10:38:45 (2.99 MB/s) - `PD98IMG/PD98IMG-GB2.zip' saved [259503624/259
503624]
a67daa6baa7ef085307593fef6329d14 *PD98IMG/PD98IMG-GB2.zip
Flash the downgrade RUU? [y,n]y
pushing rom to sdcard - this takes time please be patient.
1532 KB/s (259503624 bytes in 165.328s)
Setting up to temproot....
cannot stat 'tools/bin/zergRush': No such file or directory
2320 KB/s (572752 bytes in 0.241s)
1174 KB/s (19240 bytes in 0.016s)
going for temproot using zergRush....
/data/local/tmp/zergRush: not found
setting mainver lower for downgrade...
--set_version set. VERSION will be changed to: 1.31.405.6
Misc partition is "/dev/block/mmcblk0p17"
Patching and backing up misc partition...
Error opening input file.
Creating goldcard....
HTC android goldcard tool Copyright (C) 2011, Wayne D. Hoxsie Jr.
Original code by B. Kerler. Special thanks to ATTN1 and the XDA team.
Donations can be made to the Electronic Frontier Foundation:
eff.org/
or to B. Kerler:
psas.revskills.de
/dev/block/mmcblk1: cannot open for write: Permission denied
starting downgrade...
** The phone will now reboot into HBOOT.
** It will then check the file just sent.
** If everything is okay, the phone will
** prompt you to continue by pressing
** VOLUME UP. It will reboot, flashing twice.
**** PUSH POWER WHEN THIS STEP COMPLETES ****
If downgrade is successful, you may set up the phone and try to hack it again.
Once the downgrade is successful, press a key to return to the menu......
Otherwise, cut and paste the output to the screen into a text file for evaluatio
n.... then press a key.
Press any key to continue . . .
AND THE DISPLAY ON PHONE -- ON A WHITE SCREEN
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011,19:06:24
HBOOT
Main Version is older!
Update Fail
Press <POWER> to reboot.
--------------------------------------------------------
Would really apperciate some guidance in sorting this out. Thanks. Val.
Click to expand...
Click to collapse
The download is flaw...your antivirus ate Zergrush from the tools>bin folder. That is what is used to get temproot and set the main version lower. Make sure that u disable every AV soft in your PC and then re download the Hack Kit from here: http://tau.shadowchild.nl/attn1/?p=74l
valmiki.biswas said:
Hi,
AAHK is failing on my Desire HD. Can someone please help. This is my first ever try to ROOT. Thanks.
Android version 2.3.5
HTC Sense version: 3.0
Software number: 3.12.405.1
Kernel version: 2.6.35.10-g931a37e
[email protected] #1
Wed Nov 9 14.04.03 CST 2011
Baseband version: 12.65.60.29U_26.14.04.28_M
Build number: 3.12.405.1 CL199157 release-keys
AND here is whats failing:
Ace Advanced Hack Kit [Linux/OSX/Windows] attn1 2011/2012
___________________________
MAIN MENU | |
| Only ONE Menu Step to: |
1 - Hack Ace <----------------------------+ * S-OFF |
| * SIM Unlock |
2 - DONATE (Encouraged, but optional) | * SuperCID |
psas.revskills.de/?q=goldcard | * Root |
eff.org | * Busybox |
| |
************************************************** ********************
o - Options Menu (Return to Stock, Flash radios, etc)
************************************************** ********************
t - Toggle Flash Method - current method is fastbootRUU
************************************************** *******************
q - Quit
[Select and press Enter]1
3.12.405.1
This version of Android cannot use the hack kit at this time.
You can downgrade if you like, then rerun the hack step.
WARNING: THIS WILL WIPE DATA
[Would you like to downgrade? y/n]y
Download this RUU? [y,n]y
--2012-09-06 10:37:22-- tau.shadowchild.nl/files/PD98IMG-GB2.zip
Resolving tau.shadowchild.nl... 176.9.40.154
Connecting to tau.shadowchild.nl|176.9.40.154|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 259503624 (247M) [application/zip]
Saving to: `PD98IMG/PD98IMG-GB2.zip'
100%[======================================>] 259,503,624 4.62M/s in 83s
2012-09-06 10:38:45 (2.99 MB/s) - `PD98IMG/PD98IMG-GB2.zip' saved [259503624/259
503624]
a67daa6baa7ef085307593fef6329d14 *PD98IMG/PD98IMG-GB2.zip
Flash the downgrade RUU? [y,n]y
pushing rom to sdcard - this takes time please be patient.
1532 KB/s (259503624 bytes in 165.328s)
Setting up to temproot....
cannot stat 'tools/bin/zergRush': No such file or directory
2320 KB/s (572752 bytes in 0.241s)
1174 KB/s (19240 bytes in 0.016s)
going for temproot using zergRush....
/data/local/tmp/zergRush: not found
setting mainver lower for downgrade...
--set_version set. VERSION will be changed to: 1.31.405.6
Misc partition is "/dev/block/mmcblk0p17"
Patching and backing up misc partition...
Error opening input file.
Creating goldcard....
HTC android goldcard tool Copyright (C) 2011, Wayne D. Hoxsie Jr.
Original code by B. Kerler. Special thanks to ATTN1 and the XDA team.
Donations can be made to the Electronic Frontier Foundation:
eff.org/
or to B. Kerler:
psas.revskills.de
/dev/block/mmcblk1: cannot open for write: Permission denied
starting downgrade...
** The phone will now reboot into HBOOT.
** It will then check the file just sent.
** If everything is okay, the phone will
** prompt you to continue by pressing
** VOLUME UP. It will reboot, flashing twice.
**** PUSH POWER WHEN THIS STEP COMPLETES ****
If downgrade is successful, you may set up the phone and try to hack it again.
Once the downgrade is successful, press a key to return to the menu......
Otherwise, cut and paste the output to the screen into a text file for evaluatio
n.... then press a key.
Press any key to continue . . .
AND THE DISPLAY ON PHONE -- ON A WHITE SCREEN
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011,19:06:24
HBOOT
Main Version is older!
Update Fail
Press <POWER> to reboot.
--------------------------------------------------------
Would really apperciate some guidance in sorting this out. Thanks. Val.
Click to expand...
Click to collapse
You must turn off all anti viruses progrom on you pc and try again
Sent from my HTC Desire HD A9191 using xda app-developers app
Thankyou so so much(mghboy). It worked. I however has to install a ROM from microSD as the gingerbread didnt really work. But thanks again.
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.