[Q] Unlock bootloader Flashtool - XPERIA X10 General

Hi,
i've just tried to unlock blootloader with flashtool,it returned me:
PHP:
Searching Xperia....
12/030/2011 10:30:00 - INFO - Found at USB\VID_0FCE&PID_ADDE\6&A050C15&0&1
12/030/2011 10:30:00 - INFO - VER="R8A013";DATE="20100119";TIME="17:24:00";
12/030/2011 10:30:00 - INFO - Start Reading property
12/030/2011 10:30:00 - INFO - Reading property finished.
12/030/2011 10:30:00 - INFO - You can now unplug and turn on device, then plug it again
12/030/2011 10:30:00 - INFO - Waiting for device
12/036/2011 10:36:04 - INFO - Connected device : X10
12/036/2011 10:36:04 - INFO - Installed version of busybox : BusyBox v1.18.4 (2011-04-04 18:40:20 CDT) multi-call binary.
12/036/2011 10:36:04 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
12/036/2011 10:36:05 - INFO - Root Access Allowed
12/036/2011 10:36:06 - INFO - Pushing .\devices\X10\features\X10UnlockBL\fixPart to /data/local/tmp
12/036/2011 10:36:06 - INFO - Running runfixPart as root thru sysrun
12/036/2011 10:36:06 - INFO - Successfully applied fixPart. Rebooting
12/036/2011 10:36:07 - INFO - Waiting for device
12/036/2011 10:36:41 - INFO - Pushing .\devices\X10\features\X10UnlockBL\mapper_2.6.29.ko to /data/local/tmp
12/036/2011 10:36:41 - INFO - Pushing .\devices\X10\features\X10UnlockBL\qsd8250bootwrite_semcSL to /data/local/tmp
12/036/2011 10:36:42 - INFO - Running runqsd8250bootwrite as root thru sysrun
12/036/2011 10:36:43 - INFO - Successfully applied unlock. Rebooting
Altough i see successfully applied unlock, is there a way to be sure it has done it correctly before applying doom's kernel or i can just expect flashtool log says the right?
Thanks

franceX said:
Hi,
i've just tried to unlock blootloader with flashtool,it returned me:
PHP:
Searching Xperia....
12/030/2011 10:30:00 - INFO - Found at USB\VID_0FCE&PID_ADDE\6&A050C15&0&1
12/030/2011 10:30:00 - INFO - VER="R8A013";DATE="20100119";TIME="17:24:00";
12/030/2011 10:30:00 - INFO - Start Reading property
12/030/2011 10:30:00 - INFO - Reading property finished.
12/030/2011 10:30:00 - INFO - You can now unplug and turn on device, then plug it again
12/030/2011 10:30:00 - INFO - Waiting for device
12/036/2011 10:36:04 - INFO - Connected device : X10
12/036/2011 10:36:04 - INFO - Installed version of busybox : BusyBox v1.18.4 (2011-04-04 18:40:20 CDT) multi-call binary.
12/036/2011 10:36:04 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
12/036/2011 10:36:05 - INFO - Root Access Allowed
12/036/2011 10:36:06 - INFO - Pushing .\devices\X10\features\X10UnlockBL\fixPart to /data/local/tmp
12/036/2011 10:36:06 - INFO - Running runfixPart as root thru sysrun
12/036/2011 10:36:06 - INFO - Successfully applied fixPart. Rebooting
12/036/2011 10:36:07 - INFO - Waiting for device
12/036/2011 10:36:41 - INFO - Pushing .\devices\X10\features\X10UnlockBL\mapper_2.6.29.ko to /data/local/tmp
12/036/2011 10:36:41 - INFO - Pushing .\devices\X10\features\X10UnlockBL\qsd8250bootwrite_semcSL to /data/local/tmp
12/036/2011 10:36:42 - INFO - Running runqsd8250bootwrite as root thru sysrun
12/036/2011 10:36:43 - INFO - Successfully applied unlock. Rebooting
Altough i see successfully applied unlock, is there a way to be sure it has done it correctly before applying doom's kernel or i can just expect flashtool log says the right?
Thanks
Click to expand...
Click to collapse
Just flash doomkernal and reboot,
If you see a white sony ericsson logo it has not worked...
dont forget the correct wifi modules for the kernal you flash

gregbradley said:
Just flash doomkernal and reboot,
If you see a white sony ericsson logo it has not worked...
dont forget the correct wifi modules for the kernal you flash
Click to expand...
Click to collapse
can i ask i already unlock botloader already, how i flash wolffbreak room??? i flashed the doomkernel kernel, it stuck at doom kernel logo cannot enter into xrecovery??thn how should i flash it?

Related

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

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

Rooting problems (with details)

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.

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

Hello Guys
i am new to z3+/z4 thread
but never matters
i would like to have some small discussion about recoveries and kernels
i am not new to build recoveries and kernels or roms
for now guys i need your help on getting me some files
i need kernel.sin from ftf of your latest build from sony
cause i cant download whole ftf for small mb file
hope you understand me
so guys provide me the kenrel.sin so that i can try to provide working recoveries / kernels / roms
for both locked and unlocked bootloaders
Best regards
venkat kamesh said:
Hello Guys
i am new to z3+/z4 thread
but never matters
i would like to have some small discussion about recoveries and kernels
i am not new to build recoveries and kernels or roms
for now guys i need your help on getting me some files
i need kernel.sin from ftf of your latest build from sony
cause i cant download whole ftf for small mb file
hope you understand me
so guys provide me the kenrel.sin so that i can try to provide working recoveries / kernels / roms
for both locked and unlocked bootloaders
Best regards
Click to expand...
Click to collapse
this is kernel.sin from e6533
https://drive.google.com/file/d/0B5Rlv3cCMcOkYXZaVlFudXU4eE0/view
when you finish please mention me in a reply
go ahead <3
Sony guy said:
this is kernel.sin from e6533
https://drive.google.com/file/d/0B5Rlv3cCMcOkYXZaVlFudXU4eE0/view
when you finish please mention me in a reply
go ahead <3
Click to expand...
Click to collapse
thank you
finally a build.prop from system folder
and yes i will inform you guys once built
venkat kamesh said:
thank you
finally a build.prop from system folder
and yes i will inform you guys once built
Click to expand...
Click to collapse
Kernel.sin and build.prop from the latest firmware : 28.0.A.7.31
test recoveries
ChrisJ951 said:
Kernel.sin and build.prop from the latest firmware : 28.0.A.7.31
Click to expand...
Click to collapse
Thank you guys
For providing required files
I had finally built recoveries (test recoveries)
And installer scripts by @[NUT]
All you need is root then try installer pack
Of you have any recoveries try flash pack
Report me if you test them.... So that I can move forward with additional development
Flashable pack
Installer pack
Best regards
Did you test it on your device, or did you build without actual device?
I built TWRP for Z4T but there's touch problem, so I'd like to know how to fix if you already tested on Z3+.
AndroPlus said:
Did you test it on your device, or did you build without actual device?
I built TWRP for Z4T but there's touch problem, so I'd like to know how to fix if you already tested on Z3+.
Click to expand...
Click to collapse
What kind of touch problem? I have solved that for various devices in the past, based on a fix from @DooMLoRD and @Dees_Troy and also a fix I developed together with @rachitrawat.
Who can point me to a device repository so I can have a look at the code and files used to build it?
[NUT] said:
What kind of touch problem? I have solved that for various devices in the past, based on a fix from @DooMLoRD and @Dees_Troy and also a fix I developed together with @rachitrawat.
Who can point me to a device repository so I can have a look at the code and files used to build it?
Click to expand...
Click to collapse
Touch doesn't work at all, only power key works.
I used official device tree from
https://github.com/sonyxperiadev?tab=repositories
and modified (contains unneeded things while trying...)
https://github.com/AndroPlus-org/android_device_sony_kitakami
[NUT] said:
What kind of touch problem? I have solved that for various devices in the past, based on a fix from @DooMLoRD and @Dees_Troy and also a fix I developed together with @rachitrawat.
Who can point me to a device repository so I can have a look at the code and files used to build it?
Click to expand...
Click to collapse
Sure I will update my source file to git when I reach home
And androplus I haven't tested them... I just built them..
I am gonna get this device in a week (online shop)
So started work.....
AndroPlus said:
Touch doesn't work at all, only power key works.
I used official device tree from
https://github.com/sonyxperiadev?tab=repositories
and modified (contains unneeded things while trying...)
https://github.com/AndroPlus-org/android_device_sony_kitakami
Click to expand...
Click to collapse
I have no Z4/Z3+ nor do I own a Tablet Z4 but I will try to help out.
Do you have a log from TWRP which I can view?
Make sure you tap the screen a few times before you copy the log.
could be fixed witth the new binaries
I had built the AOSP for the Tablet Z4 and complained about touch not working.
Jerpela informed me that he put up a new revision.
I can not see that from the commit logs on GitHub (he also wrote he had done stagefright patches- checked a few minutes ago, where?). Maybe he meant updated binaries on SONY developer world...
@venkat kamesh
Sony Z3+ and I tried your Installer Pack, here is the log and i was choosing option 1 (SuperSU) coz phone is rooted
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= By Venkat kamseh =
= Scripts by Nut =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is ivy
Firmware is 28.0.A.7.24
=============================================
Step2 : Sending the recovery files.
=============================================
1 KB/s (30 bytes in 0.015s)
986 KB/s (15757 bytes in 0.015s)
31 KB/s (501 bytes in 0.015s)
11 KB/s (12198 bytes in 1.000s)
1778 KB/s (56834 bytes in 0.031s)
192 KB/s (3082 bytes in 0.015s)
24 KB/s (385 bytes in 0.015s)
2940 KB/s (657704 bytes in 0.218s)
2566 KB/s (3730720 bytes in 1.419s)
2493 KB/s (2827723 bytes in 1.107s)
2439 KB/s (2377056 bytes in 0.951s)
556 KB/s (8889 bytes in 0.015s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 657704 Jan 27 2015 /data/local/tmp/recover
y/busybox
Drücken Sie eine beliebige Taste . . .
##########################################################
#
# Installing XZDR version 2.8.1 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
find: /dev/block/platform/msm_sdcc.1/by-name/: No such file or directory
BusyBox v1.20.2-jb static (2012-11-25 17:47 +0100) multi-call binary.
Usage: blockdev OPTION BLOCKDEV
--setro Set ro
--setrw Set rw
--getro Get ro
--getss Get sector size
--getbsz Get block size
--setbsz BYTES Set block size
--getsz Get device size in 512-byte sectors
--getsize64 Get device size in bytes
--flushbufs Flush buffers
--rereadpt Reread partition table
Copy recovery files to system.
Rename stock chargemon
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Creating /system/.XZDualRecovery to store a backup copy of busybox.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event2!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Results:
Feeling was like recovery, but didnt enter recovery.
I was trying start - wait for green light then i pressed vol - and a short time pink LED came. But no enter to recovery, after ca. 20 sec newstart into normal mode.
The same with start, waiting for green light then press vol +
Sorry bro, no success but thanks for your work, I stay tuned and if you got a new version i test it.
best reguards.
Edit: following error message in log
find: /dev/block/platform/msm_sdcc.1/by-name/: No such file or directory
tree in my phone z3+:
/dev/block/platform/f9824900.sdhci/by-name/...
/dev/block/platform/f98a4900.sdhci/by-num/...
i try with my path and following resuluts, here is the log
(edited files: chargemon.sh, installrecovery.sh, rickiller.sh)
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= By Venkat kamseh =
= Scripts by Nut =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is ivy
Firmware is 28.0.A.7.24
=============================================
Step2 : Sending the recovery files.
=============================================
0 KB/s (30 bytes in 1.000s)
15 KB/s (15761 bytes in 1.000s)
0 KB/s (501 bytes in 1.000s)
11 KB/s (12198 bytes in 1.000s)
3557 KB/s (56834 bytes in 0.015s)
3 KB/s (3090 bytes in 1.000s)
24 KB/s (385 bytes in 0.015s)
2940 KB/s (657704 bytes in 0.218s)
3072 KB/s (3730720 bytes in 1.185s)
2765 KB/s (2827723 bytes in 0.998s)
2755 KB/s (2377056 bytes in 0.842s)
556 KB/s (8893 bytes in 0.015s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 657704 Jan 27 2015 /data/local/tmp/recover
y/busybox
Drücken Sie eine beliebige Taste . . .
##########################################################
#
# Installing XZDR version 2.8.1 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
Copy recovery files to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event2!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries!
=============================================
still the same result, green LED goes to pink led for one second, but Sony Xperia loader screen stays hard. No recovery.
My laptop is searching for a new driver called: "MTP-USB-Device" but don't find it.
the device hardware id is: USB\VID_18D1&PID_4EE2&REV_0310&MI_00
i was editing my C:\Windows\inf\wpdmtp.inf file with following:
[Generic.NTx86]
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
[Generic.NTamd64]
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
but no results, still didn't find the drivers
this is all what i can test, pleast stay tuned and make more tests for me
greetings
[NUT] said:
I have no Z4/Z3+ nor do I own a Tablet Z4 but I will try to help out.
Do you have a log from TWRP which I can view?
Make sure you tap the screen a few times before you copy the log.
Click to expand...
Click to collapse
USB isn't detected by PC in TWRP and I can't create full log...
Is there any other way to make log?
Here's last_log from /cache/recovery:
http://x.andro.plus/1Lvvhom
Sacktreter said:
@venkat kamesh
Sony Z3+ and I tried your Installer Pack, here is the log and i was choosing option 1 (SuperSU) coz phone is rooted
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= By Venkat kamseh =
= Scripts by Nut =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is ivy
Firmware is 28.0.A.7.24
=============================================
Step2 : Sending the recovery files.
=============================================
1 KB/s (30 bytes in 0.015s)
986 KB/s (15757 bytes in 0.015s)
31 KB/s (501 bytes in 0.015s)
11 KB/s (12198 bytes in 1.000s)
1778 KB/s (56834 bytes in 0.031s)
192 KB/s (3082 bytes in 0.015s)
24 KB/s (385 bytes in 0.015s)
2940 KB/s (657704 bytes in 0.218s)
2566 KB/s (3730720 bytes in 1.419s)
2493 KB/s (2827723 bytes in 1.107s)
2439 KB/s (2377056 bytes in 0.951s)
556 KB/s (8889 bytes in 0.015s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 657704 Jan 27 2015 /data/local/tmp/recover
y/busybox
Drücken Sie eine beliebige Taste . . .
##########################################################
#
# Installing XZDR version 2.8.1 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
find: /dev/block/platform/msm_sdcc.1/by-name/: No such file or directory
BusyBox v1.20.2-jb static (2012-11-25 17:47 +0100) multi-call binary.
Usage: blockdev OPTION BLOCKDEV
--setro Set ro
--setrw Set rw
--getro Get ro
--getss Get sector size
--getbsz Get block size
--setbsz BYTES Set block size
--getsz Get device size in 512-byte sectors
--getsize64 Get device size in bytes
--flushbufs Flush buffers
--rereadpt Reread partition table
Copy recovery files to system.
Rename stock chargemon
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Creating /system/.XZDualRecovery to store a backup copy of busybox.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event2!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Results:
Feeling was like recovery, but didnt enter recovery.
I was trying start - wait for green light then i pressed vol - and a short time pink LED came. But no enter to recovery, after ca. 20 sec newstart into normal mode.
The same with start, waiting for green light then press vol +
Sorry bro, no success but thanks for your work, I stay tuned and if you got a new version i test it.
best reguards.
Edit: following error message in log
find: /dev/block/platform/msm_sdcc.1/by-name/: No such file or directory
tree in my phone z3+:
/dev/block/platform/f9824900.sdhci/by-name/...
/dev/block/platform/f98a4900.sdhci/by-num/...
i hope this helps
Click to expand...
Click to collapse
Seeing that XZDR log... I have a few things to add for @venkat kamesh
First of all, update your XZDR repository to 2.8.21, this is better suited to work with and defeat the SELinux and Sony RIC security features in Lollipop. 2.8.1 will not work on Lollipop.
Then update the following lines at these points to match the correct block device path where @Sacktreter here already stated.
https://github.com/xNUTx/XZDualRecovery/blob/2.8-RELEASE/src/chargemon.sh#L253-L254
https://github.com/xNUTx/XZDualRecovery/blob/2.8-RELEASE/src/chargemon.sh#L336-L337
https://github.com/xNUTx/XZDualRecovery/blob/2.8-RELEASE/patches/all/twrp/etc/twrp.fstab#L1-L5
https://github.com/xNUTx/XZDualRecovery/blob/2.8-RELEASE/src/installrecovery.sh#L126
change /dev/block/platform/msm_sdcc.1 to /dev/block/platform/f9824900.sdhci on all the above lines.
This is the reason why I didn't release XZDR for the Z3+/Z4/TabZ4 yet, too much difference with the Shinano and older device trees.
That should be solved with 2.9 though...
---------- Post added at 03:15 PM ---------- Previous post was at 03:04 PM ----------
AndroPlus said:
USB isn't detected by PC in TWRP and I can't create full log...
Is there any other way to make log?
Here's last_log from /cache/recovery:
http://x.andro.plus/1Lvvhom
Click to expand...
Click to collapse
What OS do you run on your pc? Does windows register anything (even if it's just an unknown device) on the usb port?
[NUT] said:
What OS do you run on your pc? Does windows register anything (even if it's just an unknown device) on the usb port?
Click to expand...
Click to collapse
Windows 10 and there's no unknown device.
I can connect my Z3 in TWRP, so maybe something is preventing loading of init scripts.
AndroPlus said:
Windows 10 and there's no unknown device.
I can connect my Z3 in TWRP, so maybe something is preventing loading of init scripts.
Click to expand...
Click to collapse
Well, I suspect the USB device might also have a different name from the shinano hardware, which causes TWRP to mis configure the USB stack, or ignore it altogether...
See if you can find the USB root hub/controller in the ROM inside the /sys/class directory or a mention of the location in the init.usb.rc setup files (there should be at least one shell script being executed to set up the USB stack), see if you can find a device name there and then match that with the one in the kitakami repo's. The mention of this can be in either the device or the common repository.
@Nut
its a pleasure for me to talk with the master (i smile)
i dont wanna open a new answer so i edit my answer, sorry but in future i answer in a new post. Please watch my second result, i changed the path and the log is without errors, but still no enter to recovery. I konw you can help.
Edit: as you told the version 2.8.1 is needed update to version 2.8.21, now i understand and I wait. Sorry for my bad english, german is my favorite language
Sacktreter said:
@Nut
its a pleasure for me to talk with the master (i smile)
i dont wanna open a new answer so i edit my answer, sorry but in future i answer in a new post. Please watch my second result, i changed the path and the log is without errors, but still no enter to recovery. I konw you can help.
Edit: as you told the version 2.8.1 is needed update to version 2.8.21, now i understand and I wait. Sorry for my bad english, german is my favorite language
Click to expand...
Click to collapse
I saw your edit before, just post a new reply if you have any updates, makes it easier to track progress
In your USB driver inf file, you should remove &MI_00 from the device ID lines, this makes it match anything which starts with VID_18D1&PID_4EE2
https://github.com/xNUTx/XZDualReco...y/files/adbdrivers/android_winusb.inf#L28-L40
I'm not saying to use the ID's from this inf file, because this driver is meant for the ID's I am using in the recoveries for the 'official' XZDR releases.
init.kitakami.usb.rc
@Nut
see attachment from my karin_windy AOSP build
@AndroPlus scrap that search, I think something else is wrong. Seeing the usb config posted by @DHGE and the init in the aosp repositories I think twrp might be crashing when it finishes loading. Though the log you provided doesn't specify this (restart counter), it does seem to restart at some point...

Help root ZTE Blade A512

I need help, I wanted to do my ZTE to 512 and I can not do it at all. Of all the programs that support the device I get the following:
--- = SRS One-Click-Root v5.1 =
16:30:09 - Starting ADB Server ..
16:30:16 - Manufacturer: ZTE
16:30:16 - Model: ZTE BLADE A512
16:30:17 - Android Version: 6.0.1
16:30:17 - Build ID: VDF-A512B01-PT_MR03b
16:30:17 - Board ID: MSM8917
16:30:17 - Chipset Platform: msm8937
16:30:17 - Getting OffSets ..: error: only position independent executables (PIE) are supported. (False)
16:30:18 - Query Server for Best Method .. Found Rootkit: 8
---- = Start Rooting Process .. Please Wait = ----
16:30:19 [+] Testing exploit: root8 (please wait ..)
16:30:21 [+] Remounting / system Filesystem as R / W ..
16:30:21 [+] Installing SU Binary ...
16:30:22 [+] Installing SuperUser APK ...
16:30:23 [+] Remounting / system Filesystem as R / O ..
16:30:28 [+] Rooting Complete!
It gives indication that it gets root but it does not stay.
Another program that supposedly works is this one spoken in this video:
Https://www.youtube.com/watch?v=w_U_pjwE_3Q
Program: http://kidapso.com/autorootdl I can not test because I can not download even responding to the proposed surveys.
If you know of any solutions, share. Thank you
Build ID: VDF-A512B01-PT_MR03b

Somebody helps me please...

I bought a Sony Z3 (SOL26 AU) from my friends 3 days ago.
After that, I started to flash the lastest stock for the phone. But the weird thing is no matter I use which version of Flashtool, I can not flash the 23.5.A.1.291 ftf to my phone.
If I use the flashtool-0.9.15.0, flash 23.5.A.1.291, it will show - ERROR - - INFO - Cannot open bundle. Flash operation canceled.
If I use the Flashtool 0.9.18.6, flash 23.5.A.1.291, it will show - ERROR - root : this bundle is not valid.
If I use the Flashtool 0.9.34.0, flash 23.5.A.1.291, it shows
25/026/2022 22:26:41 - INFO - Using Gordon gate drivers version 3.1.0.0
25/026/2022 22:26:42 - INFO - Opening device for R/W
25/026/2022 22:26:42 - INFO - Device ready for R/W.
25/026/2022 22:26:42 - INFO - Reading device information
25/026/2022 22:26:42 - INFO - Phone ready for flashmode operations.
25/026/2022 22:26:42 - INFO - Opening TA partition 2
25/026/2022 22:26:42 - INFO - Current device : D6603 - CB5A270HY4 - 1286-2777_R9B - 1282-2729_23.0.A.2.93 - GLOBAL-LTE_23.0.A.2.93
25/026/2022 22:26:42 - INFO - Closing TA partition
25/026/2022 22:26:42 - INFO - Start Flashing
25/026/2022 22:26:42 - INFO - Processing loader.sin
25/026/2022 22:26:42 - INFO - Checking header
25/026/2022 22:26:42 - INFO - Flashing data
25/026/2022 22:26:42 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_27 / Boot version : S1_Boot_MSM8974AC_LA3.0_52-2 / Bootloader status : ROOTED
25/026/2022 22:26:42 - INFO - Max packet size set to 512K
25/026/2022 22:26:42 - INFO - USB buffer size set to 512K
25/026/2022 22:26:42 - INFO - Parsing boot delivery
25/026/2022 22:26:42 - INFO - No flash script found. Using 0.9.18 flash engine
25/026/2022 22:26:42 - INFO - Opening TA partition 2
25/026/2022 22:26:43 - INFO - Writing TA unit 00002774. Value : 01
25/026/2022 22:26:43 - INFO - Closing TA partition
25/026/2022 22:26:43 - INFO - Phone boot version : S1_Boot_MSM8974AC_LA3.0_52-2. Boot delivery version : S1_Boot_MSM8974AC_LA3.0-M-3
25/026/2022 22:26:43 - INFO - Going to flash boot delivery
25/026/2022 22:26:43 - INFO - Opening TA partition 2
25/026/2022 22:26:43 - INFO - Processing emmc_appsboot_S1_Boot_MSM8974AC_LA3_0_M_3_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
25/026/2022 22:26:43 - INFO - Checking header
25/026/2022 22:26:43 - ERROR - Processing of emmc_appsboot_S1_Boot_MSM8974AC_LA3_0_M_3_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin finished with errors.
25/026/2022 22:26:43 - INFO - Ending flash session
25/026/2022 22:26:43 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="80080021";
25/026/2022 22:26:43 - ERROR - Error flashing. Aborted
Does anybody help me with this situation??? I had tried it for 3 days which made me mad....
Btw, I can use any version of Flashtool to flash the KK stock ftf successfully... I don't understand why...The stock ftf I had change 3 version, but lead to the same error.....
hey, i dont very good with english, but you verify before the model of the FTF? in the log your phone is identified with the number D6603 ( idont know is the ftf model info or the actual device), the FTF must match the same model number. hope this helps...

Categories

Resources