Database Users

Help, Can't flash Sbl.bin

Well, just like the thread title says, i can't flash Sbl.bin neither from Odin nor Heimdall. With Odin it just hangs in Sbl.bin and Heimdall fails after a couple of minutes waiting. Trying to flash it with Heimdall in verbose mode gives an "Error -7". Can someone help me? I'm trying to flash the new bootloaders included with JVK to solve the problem with the screen.
My phone is a Galaxy S I9000T
Thanks in advance.

Same problem here, except that I'm able in theory to flash with Heimdall. However, the result is like I hadn't flashed bootloaders (screen corruption, loss of recovery mode), this only happens with rom XXJVK.
My I9000T (from Telhell) actually runs XWJS8 but with modem TDOJP1 for unknown reason as I don't mix components intentionally.

Try flashing JPU JV1 or any other firmware with the bootloaders and see if you are facing the same issue.
Sent from my GT-I9000 using XDA App

Have you tried flashing the 3 files from Samfirmware?
I tried with the 3 files posted here on XDA and they would never flash.
It just hung... I had to pull the phone because no progress happening. Got the Phone to PC error screen. Luckily was able to force it into download mode again with the three button sequence. Took over a minute of holding the combo to get it there.
So yeah... Just try the 3 sbl files from Samfirmware and they should flash without a hitch.

Flashing bootloaders on their own is a bad idea. Just reflash the whole package.

Hello again,
I can't reflash the whole package because it hangs every time it tries to write the Sbl.bin file. I'm trying to flash the bootloaders because, somehow, i managed to flash the JVK ROM and i have issues with my screen and i can't enter in recovery mode.
I already tried with all of the heimdall bootloaders in Perka's File Stash, but i get the same result. Verbose mode in Heimdall when i try (and fail) to flash Sbl.bin says this:
Uploading secondary bootloader
0%File Part #0... Response: 0 0 0 0 0 0 0 0
File Part #1... Response: 0 0 0 0 1 0 0 0
File Part #2... Response: 0 0 0 0 2 0 0 0
File Part #3... Response: 0 0 0 0 3 0 0 0
File Part #4... Response: 0 0 0 0 4 0 0 0
File Part #5... Response: 0 0 0 0 5 0 0 0
File Part #6... Response: 0 0 0 0 6 0 0 0
File Part #7... Response: 0 0 0 0 7 0 0 0
File Part #8... Response: 0 0 0 0 8 0 0 0
File Part #9... Response: 0 0 0 0 9 0 0 0
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet.
Failed to confirm end of file transfer sequence!
Secondary bootloader upload failed!
Re-attaching kernel driver...
Any idea?

froysm said:
Hello again,
I can't reflash the whole package because it hangs every time it tries to write the Sbl.bin file. I'm trying to flash the bootloaders because, somehow, i managed to flash the JVK ROM and i have issues with my screen and i can't enter in recovery mode.
I already tried with all of the heimdall bootloaders in Perka's File Stash, but i get the same result. Verbose mode in Heimdall when i try (and fail) to flash Sbl.bin says this:
Uploading secondary bootloader
0%File Part #0... Response: 0 0 0 0 0 0 0 0
File Part #1... Response: 0 0 0 0 1 0 0 0
File Part #2... Response: 0 0 0 0 2 0 0 0
File Part #3... Response: 0 0 0 0 3 0 0 0
File Part #4... Response: 0 0 0 0 4 0 0 0
File Part #5... Response: 0 0 0 0 5 0 0 0
File Part #6... Response: 0 0 0 0 6 0 0 0
File Part #7... Response: 0 0 0 0 7 0 0 0
File Part #8... Response: 0 0 0 0 8 0 0 0
File Part #9... Response: 0 0 0 0 9 0 0 0
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet.
Failed to confirm end of file transfer sequence!
Secondary bootloader upload failed!
Re-attaching kernel driver...
Any idea?
Click to expand...
Click to collapse
Try flashing the complete package, Use Odion 1.7 or 1.8 this will fix the issue

lvvine said:
Try flashing the complete package, Use Odion 1.7 or 1.8 this will fix the issue
Click to expand...
Click to collapse
Nope, i tried with Odin 1.7 and Odin 1.8 and it was the same, it just can't pass from Sbl.bin, any other idea?

froysm said:
Nope, i tried with Odin 1.7 and Odin 1.8 and it was the same, it just can't pass from Sbl.bin, any other idea?
Click to expand...
Click to collapse
Get the bootloaders from my files and flash with heimdall.
Link in my sig.

Perka said:
Get the bootloaders from my files and flash with heimdall.
Link in my sig.
Click to expand...
Click to collapse
I already tried with the 5 Heimdall Bootloaders in your File Stash, but nothing changes.

Are you by any chance trying to flash bootloaders from I9000 International on I9000T?

[Ramad] said:
Are you by any chance trying to flash bootloaders from I9000 International on I9000T?
Click to expand...
Click to collapse
Try the 2.1 single file package meant for your region. You can download it from samfirmware I think.

[Ramad] said:
Are you by any chance trying to flash bootloaders from I9000 International on I9000T?
Click to expand...
Click to collapse
Yes, that is exactly what i am trying to do, the first bootloader passes, but the secondary not. Should i wait for a Gingerbread ROM for my model of Galaxy S?

Lol ... No words ...

froysm said:
Yes, that is exactly what i am trying to do, the first bootloader passes, but the secondary not. Should i wait for a Gingerbread ROM for my model of Galaxy S?
Click to expand...
Click to collapse
Yeah I know exactly what your're talking about. I recommend flasing always with Heimdall, try again flashing bootloaders but before make sure U first put the phone in USB Debugging mode before enter in Download mode. Hope this helps.

froysm said:
Yes, that is exactly what i am trying to do, the first bootloader passes, but the secondary not. Should i wait for a Gingerbread ROM for my model of Galaxy S?
Click to expand...
Click to collapse
Please don't do it, there is a reason that your device refuses to be flashed with the Sbl.bin from the International I9000, don't you agree?

[Ramad] said:
Please don't do it, there is a reason that your device refuses to be flashed with the Sbl.bin from the International I9000, don't you agree?
Click to expand...
Click to collapse
Well, since pretty much everything available for the i9000 also works for the i9000T i thought it would work, i mean, the only the only thing that everyone says is different (In the forums, obviuosly) is that the i9000T uses the 850 band, but i must be wrong. Also, i don't see other i9000T users complaining about bootloaders... maybe they haven't tried... Thanks anyway, i'll stick with FroYo ROMs for the moment.

Froysm, I'm with Telcel as well and I'm experiencing the same!
I flashed it successfully with JPY ROM...
When I tried to update to JS5 ROM, Odin hung at sbl.bin...
And then began my nightmare... It is soft bricked. I can get to Recovery and Download, but the phone is not working beyond that.
I tried to flash back to JPY, and it is booting, but it fails to present the "login screen"... and it keeps vibrating from time to time (every 20 seconds or so)
Someone told me that JPU is the way to go in this cases, but it hangs at sbl.bin as well.
I've read that JM8 (eclair 2.1) should fix this problem, but I've also read that it may hardbrick the phone... so, I'm in a researching stage right now...
Did you soft bick your phone with the sbl.bin issue?
How did you get it back?
I'm kinda savvy in technical stuff, but I'm a newcomer to android, so I'm kinda lost. I don't know if you can help me...
I'm thinking of getting my phone back to telcel and ask for a replacement, but that wouldn't help in my learning. I want to seize this issue to get to know android, but I need someone to lead me or someone that can show me the way... lots of information, and I don't know where to start.
Cheers!

My exact problem is described in the following thread>
http://forum.xda-developers.com/showthread.php?p=12630868#post12630868
Thanks for any help!

Oh, damn Telcel! I'm with Telcel too and I'll be happy to help you.
Sent from my GT-I9000 using Tapatalk

Temp Root Problems

Hi,
I am trying to temp root my device (2.50.405.2) so that I can backup all my app data before I root my device. However I am getting problems. I am using the fre3vo software, and what I get is the following error message.
adb server is out of date. killing...
* daemon started successfully *
612 KB/s (0 bytes in 9796.000s)
15 KB/s (0 bytes in 15837.001s)
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 0
bits_per_pixel: 32
activate: 16
height: 106
width: 62
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Potential exploit area found at address fbb6c1ff:e01.
Payload verification failed.
Click to expand...
Click to collapse
Anyone seen this before? I heard a factory reset will solve this but I don't want to do this until I have all my app data backed up. I don't want to lose it before i root. Any ideas?

Hi, thought I bump this up to see if anyone would be able to help.

from the Fre3vo thread
#teamwin is proud to announce the Fre3vo tool for the HTC EVO 3D and Sensation!
Click to expand...
Click to collapse
So it would seem to me your problem is that you have neither a EVO 3D or a Sensation, simples!

Nope, it has been used before on other DHD.
http://forum.xda-developers.com/showthread.php?t=905003

My bad, the fre3vo threads are out of date it seems, digging around it suggests that a simple reboot and trying again seems to work, I am assuming it didn't in your case?

done that and it didn't work
I was told over at androidforums to reset the phone, but if I do that I lose my app data. Need to back it up before I root.

springy said:
done that and it didn't work
I was told over at androidforums to reset the phone, but if I do that I lose my app data. Need to back it up before I root.
Click to expand...
Click to collapse
My backup app doesn't require root like titanium backup, you can use it prior to root. once rooted restore and switch to titanium.

naailalzuhir said:
My backup app doesn't require root like titanium backup, you can use it prior to root. once rooted restore and switch to titanium.
Click to expand...
Click to collapse
Again, it doesn't back up the application data. Only the .apk. You need root to do this.

Unofficial cyanogenmod7.2.0 rc for malata t8 mcc nvflash mode with sod fixed

[only mcc models
First flash ota 20110524 to return at original cwm and do wipe data and wipe partion cache
This will make clean instalation
unrar archivehttp://www.mediafire.com/?adu3kmqhxkb8hfi
run nv flash
go recovery
format system
wipe dalvik cache
mount usb
copy update
copy gapps
copy kernel
flash them with same way
done
lcd density at 120
Stable with pershoot tweaks preload
Major bug have been fixed
Sound improved with beats audio
external sdcard fixed
Sleep fixed
Hd video and mkv video format playable with external. Player like mx video
System improved with init.d tweks
new theme ics
camera work with skype
bravia engine drivers added
set 775 permission system/etc/be photo
set 775 permission system/etc/be movie
Kill app via long press choice will help you
To my daughter Jan
malata t8 unofficial cyanogenmod 7.2.0 RC nvflash mode for mcc device
congratulation goes whyberg for that wonderfull work
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Use at your own risk its not my responsibility if brick your device
download firmware
http://www.mediafire.com/?p66bpjp1qeug6vs
download latest gapps
http://www.mediafire.com/?zglnipcv34kdt49
Click to expand...
Click to collapse
unpacks the archive
includes device "-" + "power" (APX mode)
running the batch file download [1GB | 512MB]
after the device goes into overdrive long press power off
includes device "+" + "power" (recovery mode)
now you must input and export usb cable in & out with usb mount from recovery mode until computer regognize your tablet as storage
copy the update zip and gapps zip into
pour through recovery archive with firmware update-cm-7.2.0-RC0-smb_a9701-KANG-signed.zip & and latest gapps on SDCARD
set after "install from SDcard" both before reboot
Click to expand...
Click to collapse
libcamera.so.ziphttp://forum.xda-developers.com/attachment.php?attachmentid=896892&d=1328950465
Installetion via ADB
1. unzip libcamera.so.zip
2. adb remount
3. adb push libcamera.so /system/lib/libcamera.so
Manual
With root explorer paste libcamera.so into
System/lib and give read write permission as the other
Before reboot
Via recovery(libcamera.so-update.zip)http://forum.xda-developers.com/attachment.php?attachmentid=896903&d=1328951238
Skype 2.6.0.95 version worked!!!
Gtalk video not! but in`s not a camera problem...
Click to expand...
Click to collapse
not working
video accelerator
as all gtablet must install externall video code
like
mxvideo apk
Click to expand...
Click to collapse
Best flash player with this rom is 10.3
Working you tube like a charm
New google play without errors
http://i.minus.com/1331477283/iiYu2AW7DQxVWHgoI7qIbA/dJCxyuh2eNq0W.apk
Click to expand...
Click to collapse
you must be carefull
do not partion sd
do not fix permission
it may brick
enjoy
Click to expand...
Click to collapse

confirmed working!!!!!!!
Thanks geowolf........ youre the man
I'd go as far as to say.... Best Malata zpad t8 rom I've found and was easy to install (as per instructions above you need to install zip files BEFORE first boot)
Shame about no camera. Does anyone know of a fix?
I'm off to 4pda. ru to check for updates

camera fix found
hXXp://cyanogenmod.googlecode.com/issues/attachment?aid=44480005000&name=CM07CameraFix.zip&token=HIEuD7abnRfewkHvEaa8YkZSjZg%3A1328138144361
just copy .so files over /system/lib using root explorer and set permissions same as other files
reboot
install included camera.apk if needed
Happy days

Anything for us poor mcb owners?

Hello,
I have an evolio neura tablet, which I understand is the romanian version of malata zpad t8, how do I know which serial I have, because as for as I understand there are two types of models MCB and MCC.
-also because I am new to the android family can someone explain step by step how to upgrade the rom?
Thanks

cociuba said:
Hello,
I have an evolio neura tablet, which I understand is the romanian version of malata zpad t8, how do I know which serial I have, because as for as I understand there are two types of models MCB and MCC.
-also because I am new to the android family can someone explain step by step how to upgrade the rom?
Thanks
Click to expand...
Click to collapse
Hello
There three models mca. Which doesn't use interval memory and was the easy way to upgrade any ron
Mcb its little confuse what type of nand type are use in previous update of official firmware was problem to install mcc nand type sound errors and. Not compatible firmsware
Only if know what type of you use proceed to this
and mcc with interval memory the things are very dangerous .this nvflash regognize your interval memory as SD card and sdcatd turns as emcc folder
Ihave test it to emmc models.
Under the tap of sim card has the type of memory that you use
Open the tap. And has a specification note with numbers
Something like that ( emmc34567886)

i cant find the serial under the gsm tap, is there another posibility of finding it?

cociuba said:
i cant find the serial under the gsm tap, is there another posibility of finding it?
Click to expand...
Click to collapse
At settings
About option
Give a report

Hi geowolf,
Many thanks for what you're doing.
I also have an evolio neura - malata zpad t8 rebranded.
In the "about tablet" option I only have:
Model number - Evopad
Android version - 2.2
Baseband version - R2A11
Kernel version - 2.6.32.0-00252-gf1df521-dirty [email protected] #5
Build number - 20110712_EW
Hope it helps.
Also do you think that we could get ics on this?
Thank you!

this is the result from using one of the updates for the tablet, it seems that the update uses the emmc.bat
c:\neura\neura [email protected]>download_EMMC_1G.bat
c:\neura\neura [email protected]>"nvflash.exe" --bct Malata_a02_12Mhz_H5PS1G83EFR-S6C_ 333Mhz_1GB_emmc_THGBM1G6D4EBAI4_x8.bct --setbct --bl bootloader.bin --configfile android_fastboot_emmc_full_more.cfg --odmdata 0x3c0c0011 --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x171411c040a08297
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file:Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_emmc_THGBM1G6D4EBAI4_x8.bct - 4080/4080 bytes sent
Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_emmc_THGBM1G6D4EBAI4_x8.bct sent successfully
odm data: 0x3c0c0011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
945472/945472 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Click to expand...
Click to collapse
EE

bungadudu said:
Hi geowolf,
Many thanks for what you're doing.
I also have an evolio neura - malata zpad t8 rebranded.
In the "about tablet" option I only have:
Model number - Evopad
Android version - 2.2
Baseband version - R2A11
Kernel version - 2.6.32.0-00252-gf1df521-dirty [email protected] #5
Build number - 20110712_EW
Hope it helps.
Also do you think that we could get ics on this?
Thank you!
Click to expand...
Click to collapse
One more
Is rooted ?
If open root directory with root explorer is any directory like emmc. emmb ....
China Malata 3g models are mmc
But Russian 3q models has been moderate with erricson 3g spare even are, or not 3g
Maybe and the Romanian models has been modified
With 3g
Try with root explorer to find mount points
And from market android system info has an option to find mount points
Check it out .
Its to early for ice cream

cant find the mount points but I attached diskstat and partition file
diskstat
7 0 loop0 0 0 0 0 0 0 0 0 0 0 0
7 1 loop1 0 0 0 0 0 0 0 0 0 0 0
7 2 loop2 0 0 0 0 0 0 0 0 0 0 0
7 3 loop3 0 0 0 0 0 0 0 0 0 0 0
7 4 loop4 0 0 0 0 0 0 0 0 0 0 0
7 5 loop5 0 0 0 0 0 0 0 0 0 0 0
7 6 loop6 0 0 0 0 0 0 0 0 0 0 0
7 7 loop7 0 0 0 0 0 0 0 0 0 0 0
179 48 mmcblk3 17433 44474 1532199 120670 136737 577806 3635982 18924640 0 1974930 19139480
179 49 mmcblk3p1 4495 282 286484 26080 3 0 6 20 0 15010 26080
179 50 mmcblk3p2 12 61 290 10 133 6864 27988 57350 0 11350 57360
179 51 mmcblk3p3 9 61 278 20 8 1 36 550 0 550 570
179 52 mmcblk3p4 0 0 0 0 0 0 0 0 0 0 0
179 53 mmcblk3p5 0 0 0 0 0 0 0 0 0 0 0
179 54 mmcblk3p6 9475 27970 846506 75240 115761 534552 2610508 14212670 0 1796540 14288720
179 55 mmcblk3p7 5 0 10 10 0 0 0 0 0 10 10
179 56 mmcblk3p8 3432 16100 398591 19310 20832 36389 997444 4654050 0 276190 4766740
254 0 dm-0 40 0 1066 340 0 0 0 0 0 130 340
254 1 dm-1 805 0 74867 14710 0 0 0 0 0 7710 14710
254 2 dm-2 34 0 478 30 0 0 0 0 0 30 30
254 3 dm-3 406 0 37090 4450 0 0 0 0 0 2180 4450
254 4 dm-4 80 0 6210 1040 0 0 0 0 0 330 1040
254 5 dm-5 118 0 6850 3190 0 0 0 0 0 810 3190
254 6 dm-6 635 0 47366 5750 0 0 0 0 0 2640 5750
Click to expand...
Click to collapse
partition
major minor #blocks name
7 0 2111 loop0
7 1 48888 loop1
7 2 2111 loop2
7 3 30177 loop3
7 4 4190 loop4
7 5 7308 loop5
7 6 24980 loop6
179 48 15648768 mmcblk3
179 49 327680 mmcblk3p1
179 50 65536 mmcblk3p2
179 51 32768 mmcblk3p3
179 52 1 mmcblk3p4
179 53 32768 mmcblk3p5
179 54 2097152 mmcblk3p6
179 55 8192 mmcblk3p7
179 56 13081600 mmcblk3p8
254 0 2110 dm-0
254 1 48888 dm-1
254 2 2110 dm-2
254 3 30177 dm-3
254 4 4189 dm-4
254 5 7308 dm-5
254 6 24979 dm-6
Click to expand...
Click to collapse

cociuba said:
cant find the mount points but I attached diskstat and partition file
diskstat
partition
Click to expand...
Click to collapse
The most important is that previous update you use was emmc

ok, so I can use your build?
if yes please explain one more time the steps, thanks.
also is it possible to use clockworkmod? or how can i make a backup of the rom that I am using

Hello All!
I build this rom from Cyanogen source +
1. kernel from Pershoot(MegaMonstr
2. MDM modems patch (my malata wifi version + F3607GW module with GPS)
3. Camera patch for Skype form toshiba ac100
4. /dev/hands
There are additional wishes?
Sorry for my english

@whyberg -does gsm work?

cociuba said:
@whyberg -does gsm work?
Click to expand...
Click to collapse
voice? i don't know, F3607gw can't support voice calls
gprs/edge/umts data worked well

whyberg said:
Hello All!
I build this rom from Cyanogen source +
1. kernel from Pershoot(MegaMonstr
2. MDM modems patch (my malata wifi version + F3607GW module with GPS)
3. Camera patch for Skype form toshiba ac100
4. /dev/hands
There are additional wishes?
Sorry for my english
Click to expand...
Click to collapse
thanks for all
great job
the post belong to you from now
it would greatfull if post your libcamera .so for working skype
thanks we wait for this long time
i hope for the next...

I will soon test your rom, but I would like to know if something goes wrong can I revert to the stock rom, and how?
thanks for your work.
ps: is it possible to install the rom from a linux machine (ubuntu)?

geowolf1000 said:
thanks for all
great job
the post belong to you from now
it would greatfull if post your libcamera .so for working skype
thanks we wait for this long time
i hope for the next...
Click to expand...
Click to collapse
View attachment libcamera.so.zip
Installetion via ADB
1. unzip libcamera.so.zip
2. adb remount
3. adb push libcamera.so /system/lib/libcamera.so
Via recovery(View attachment libcamera.so-update.zip)
Skype from market last version worked!!!
Gtalk video not! but in`s not a camera problem...
cociuba said:
I will soon test your rom, but I would like to know if something goes wrong can I revert to the stock rom, and how?
thanks for your work.
ps: is it possible to install the rom from a linux machine (ubuntu)?
Click to expand...
Click to collapse
Download stock rom from hardware developer website and reinstall it
What device you have?
My working computer under debian

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

[ROOT][Z-Z3] How to root 5.0 Lollipop with rootkitXperia

rootkitXperia is back again!
A Japanese developer, @cubeundcube made it possible to root some Android 5.0 Lollipop firmware directly (not 5.1 and 64bit devices, sadly...).
With new rootkitXperia, you don't need to roll back to KitKat when you lose root on locked bootloader!
Download
Download (only for M4 Aqua Dual E2363 *)
Download (for M4 Aqua E2303 **)
Supported device/version
Z2/Z3 variant
23.2.A.1.62
23.1.A.1.28
17.1.1.B.3.240 or .245 *Japanese model
23.0.B.1.38 *Japanese model
23.0.B.1.59 *Japanese model
23.0.C.0.350 *Japanese model
23.0.H.0.334 *Japanese model
Z1 variant
14.5.A.0.270
14.3.B.0.310 *Japanese model
Z variant
10.6.A.0.454
M4 Aqua Dual E2363 *
26.1.B.1.85
M4 Aqua E2303 **
26.1.A.1.128
* You can see some 5.1 firmwares in "support.txt", but "封鎖" means "blocked/patched", so they are not supported.
How to use rootkitXperia
1. Install adb driver for your device
2. Go to Settings > Developer options and tick USB debugging
3. Go to Settings > Security and tick Unknown sources
4. Connect your phone to your computer
5. Extract rootkitXperia_20150926.zip and run install.bat
6. When you see "— all finished —" in console, rooting is done.
NOTE: rootkitXperia won't install recovery or kill ric,
so you have to install XZDualRecovery.
Donate link for cubeundcube is here.
If you want to thank him, his first post for dev threads is here

The support file inside the tool says that support also 5.1.1 firmware at least the one for z1. Good thats a nice very nice news. Thanks

Here's the thing pulled through Google Translate:
■ domestic version
Z1 system: 14.3.B.0.310 previous
Z2 system: 17.1.1.B.3.240 (245) previous
Z3 system: 23.0.B.1.38 previous
■ Z2 & Z3 system (Overseas Version)
23.4.A.0.546 blockade
23.2.A.1.62 OK
23.1.A.1.28 OK
■ Z1 system (Overseas Version)
14.6.A.0.368 blockade
14.5.A.0.283 blockade
14.5.A.0.270 OK
■ Z system (Overseas Version)
10.7.A.0.222 blockade
10.6.A.0.454 OK
Click to expand...
Click to collapse
Domestic version means the Japanese versions. Probably.

I added Japanese models to the list.
You can see some 5.1 firmwares in "support.txt", but "封鎖" means "blocked/patched", so they are not supported.
[UPDATE]
Added C4, M4 Aqua and C5 Ultra

Awesome bro!!! but seems lost ADB Driver in the Folders ?

timlu85 said:
Awesome bro!!! but seems lost ADB Driver in the Folders ?
Click to expand...
Click to collapse
You have to set up by yourself.
It's really easy and you don't need to do again.

timlu85 said:
Awesome bro!!! but seems lost ADB Driver in the Folders ?
Click to expand...
Click to collapse
You can copy paste from wherever tool using adb like dualrecovery installer or kamome tool. Cheers
Enviado desde mi C6903 mediante Tapatalk

Too bad it's not working with z4 5.02 build .......

ibis69 said:
Too bad it's not working with z4 5.02 build .......
Click to expand...
Click to collapse
Yes all Z3+/Z4 firmwares are already patched before release.
Sony is so fast to patch exploits...

AndroPlus said:
rootkitXperia is back again!
Click to expand...
Click to collapse
Not working on C5Ultra

freddy1991 said:
Not working on C5Ultra
Click to expand...
Click to collapse
What version?

AndroPlus said:
What version?
Click to expand...
Click to collapse
The same build number you mentioned at op
The phone rebooted once and when it booted up, the terminal window said " removing temporary files" and "finished. Press any key to continue "..

freddy1991 said:
The same build number you mentioned at op
The phone rebooted once and when it booted up, the terminal window said " removing temporary files" and "finished. Press any key to continue "..
Click to expand...
Click to collapse
And no SuperSU?
If so I'll remove C5 Ultra from the list...

AndroPlus said:
And no SuperSU?
If so I'll remove C5 Ultra from the list...
Click to expand...
Click to collapse
Yes. There's no SuperSU.
Also not working for M4 Aqua Dual but my M4 has a higher build number than the one at OP.

I got error when rooting C5 Ultra Dual
--- Xperia rootkit 2015/09/26 ---
waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
783 KB/s (13640 bytes in 0.017s)
4906 KB/s (75364 bytes in 0.015s)
4878 KB/s (29972 bytes in 0.006s)
7227 KB/s (170232 bytes in 0.023s)
7678 KB/s (5904943 bytes in 0.751s)
7755 KB/s (1048328 bytes in 0.132s)
28 KB/s (58 bytes in 0.002s)
26 KB/s (55 bytes in 0.002s)
307 KB/s (629 bytes in 0.002s)
5051 KB/s (25863 bytes in 0.005s)
4424 KB/s (13592 bytes in 0.003s)
58 KB/s (60 bytes in 0.001s)
2572 KB/s (5268 bytes in 0.002s)
getroot start.
ro.build.product=arima6752_lwt_s_l
ro.build.id=29.0.B.0.161
ro.build.version.release=5.0
max_fds=4096
Creating target socket...OK.
3072 sockets created.
waiting for device...
error: protocol fault (no status)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
error:
removing temporary files...
adb server is out of date. killing...
* daemon started successfully *
rm: /data/local/tmp/getroot: No such file or directory
rm: /data/local/tmp/supolicy: No such file or directory
rm: /data/local/tmp/libsupol.so: No such file or directory
rm: /data/local/tmp/busybox: No such file or directory
rm: /data/local/tmp/00stop_ric: No such file or directory
rm: /data/local/tmp/99SuperSUDaemon: No such file or directory
rm: /data/local/tmp/install-recovery.sh: No such file or directory
rm: /data/local/tmp/ric_disabler_mod.ko: No such file or directory
rm: /data/local/tmp/copymodulecrc: No such file or directory
rm: /data/local/tmp/saferic: No such file or directory
rm: /data/local/tmp/install_tool.sh: No such file or directory
--- all finished ---
請按任意鍵繼續 . . .
Click to expand...
Click to collapse

beenoliu said:
I got error when rooting C5 Ultra Dual
Click to expand...
Click to collapse
Please try again after run this command:
adb kill-server
adb start-server
If it fails, C5 Ultra is not really supported.

AndroPlus said:
Please try again after run this command:
adb kill-server
adb start-server
If it fails, C5 Ultra is not really supported.
Click to expand...
Click to collapse
Got same error
Hope can fix soon

I have a M4 Auqa Dual (E2363), tried with both 26.1.B.2.102 and 26.1.B.2.129, there is no older firmware of this phone and it does not work.
the phone reboots and says all finished, but there is no SU loaded, and root is not there.
HTML:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\windows\system32>cd C:\Android\sdk\platform-tools
C:\Android\sdk\platform-tools>install.bat
--- Xperia rootkit 2015/09/26 ---
waiting for device...
307 KB/s (13640 bytes in 0.043s)
4089 KB/s (75364 bytes in 0.017s)
3644 KB/s (29972 bytes in 0.008s)
4147 KB/s (170232 bytes in 0.040s)
4590 KB/s (5904943 bytes in 1.256s)
3390 KB/s (1048328 bytes in 0.301s)
27 KB/s (58 bytes in 0.002s)
17 KB/s (55 bytes in 0.003s)
307 KB/s (629 bytes in 0.001s)
4205 KB/s (25863 bytes in 0.006s)
1203 KB/s (13592 bytes in 0.011s)
29 KB/s (60 bytes in 0.002s)
1725 KB/s (5268 bytes in 0.002s)
getroot start.
ro.build.product=E2363
ro.build.id=26.1.B.2.102
ro.build.version.release=5.0
max_fds=4096
Creating target socket...OK.
3072 sockets created.
waiting for device...
removing temporary files...
--- all finished ---
Press any key to continue . . .
C:\Android\sdk\platform-tools>

M4 Aqua E2303
not working @ both 2.99 and 1.28 firmwares

AndroPlus said:
Yes all Z3+/Z4 firmwares are already patched before release.
Sony is so fast to patch exploits...
Click to expand...
Click to collapse
unlike with the updates