Intel Atom Z3560 (Moorefield) - Not Flashing Correctly - Asus Zenpad 8.0 ROMs, Kernels, Recoveries, & Other

Hi,
I got an old Asus Android S 8.0 Z580CA tablet with above mentioned processor.
The bootloader is bricked, so I got a black screen all the time.
However, xFSTK downloader running on my Win7 PC seems to communicate with the tablet over USB.
In an attempt to restore the bootloader, I tried to flash the binaries dnx_fwr.bin, ifwi.bin and droidboot_dnx.img.POS_sign.bin
All went well at start but then xFSTK returned an error right after FW: Sending DnX DCFI00 : ER04 - see log file here after.
So I am left with some questions:
1) Any idea how to work around the error or solve the problem? What could be the cause for ER04?
2) Where could I download the latest binaries for the processor?
Thanks in advance
------------------------------------------------------------------------------------
xfstklog_Sat_18._Sep_12-42-22_2021.txt
12:42:21 - XFSTK Downloader API 1.7.0 Copyright (c) 2014 Intel Corporation
12:42:21 - fwdnx -- G:/Android/AsusZ580CA-BootloaderFirmware/xFSTK_ZE551ML-sal358-amtech.vn/dnx_fwr.bin
12:42:21 - fwimage -- G:/Android/AsusZ580CA-BootloaderFirmware/xFSTK_ZE551ML-sal358-amtech.vn/ifwi.bin
12:42:21 - osdnx -- N/A
12:42:21 - osimage -- G:/Android/AsusZ580CA-BootloaderFirmware/xFSTK_ZE551ML-sal358-amtech.vn/droidboot_dnx.img.POS_sign.bin
12:42:21 - gpflags -- 0x80000807
12:42:21 - XFSTK-LOG--virtual bool MerrifieldDownloader::SetDevice(IGenericDevice*)
12:42:21 - Initiating download...
12:42:21 - XFSTK-LOG--virtual bool MerrifieldDownloader::UpdateTarget()
12:42:21 - XFSTK-LOG--FWDnxPath -- G:/Android/AsusZ580CA-BootloaderFirmware/xFSTK_ZE551ML-sal358-amtech.vn/dnx_fwr.bin
12:42:21 - XFSTK-LOG--FWImagePath -- G:/Android/AsusZ580CA-BootloaderFirmware/xFSTK_ZE551ML-sal358-amtech.vn/ifwi.bin
12:42:21 - XFSTK-LOG--OSDnxPath -- N/A
12:42:21 - XFSTK-LOG--OSImagePath -- G:/Android/AsusZ580CA-BootloaderFirmware/xFSTK_ZE551ML-sal358-amtech.vn/droidboot_dnx.img.POS_sign.bin
12:42:21 - XFSTK-LOG--MiscDnxPath -- G:/Android/AsusZ580CA-BootloaderFirmware/xFSTK_ZE551ML-sal358-amtech.vn/dnx_fwr.bin
12:42:21 - XFSTK-LOG--MiscBinPath -- BLANK.bin
12:42:21 - XFSTK-LOG--Gpflags -- 80000807
12:42:21 - XFSTK-LOG--DebugLevel -- ffffffff
12:42:21 - XFSTK-LOG--UsbDelay ms -- 0
12:42:21 - XFSTK-LOG--TransferType -- USB
12:42:21 - XFSTK-LOG--WipeIFWI -- False
12:42:21 - XFSTK-LOG--Idrq -- False
12:42:21 - XFSTK-LOG--Verbose -- True
12:42:21 - XFSTK-LOG--void MerrifieldDownloader::Init()
12:42:21 - XFSTK-LOG--Open
12:42:21 - XFSTK-LOG--USB Device found - USBSN: A0E401E0A6806D3E9A29A4B1166ED7DB Address:3
12:42:21 - XFSTK-LOG--void MerrifieldDownloader::do_update(MerrifieldOptions*)
12:42:21 - XFSTK-LOG--Start
12:42:21 - XFSTK-LOG--Sending DnER...
12:42:21 - XFSTK-LOG--WriteOutPipe DnER
12:42:21 - XFSTK-LOG--WriteOutPipe 0
12:42:21 - XFSTK-LOG--Write --->DnER
12:42:21 - XFSTK-LOG--GetOpCode
12:42:21 - XFSTK-LOG--ReadInAck
12:42:21 - XFSTK-LOG--GetAck - DxxM(4)
12:42:21 - XFSTK-LOG--Visit
12:42:21 - XFSTK-LOG--FW: Handle None virgin part DnX ...
12:42:21 - XFSTK-LOG--LogProgress
12:42:21 - XFSTK-LOG--GetOpCode
12:42:21 - XFSTK-LOG--Changing to DLDR_STATE_FW_MISC ...
12:42:21 - XFSTK-LOG--InitNoSize
12:42:21 - XFSTK-LOG--CheckFile
12:42:21 - XFSTK-LOG--CheckFile
12:42:21 - XFSTK-LOG--G:/Android/AsusZ580CA-BootloaderFirmware/xFSTK_ZE551ML-sal358-amtech.vn/dnx_fwr.bin size:110888 bytes
12:42:21 - XFSTK-LOG--G:/Android/AsusZ580CA-BootloaderFirmware/xFSTK_ZE551ML-sal358-amtech.vn/dnx_fwr.bin size:110888 bytes
12:42:21 - XFSTK-LOG--InitFwImage
12:42:21 - XFSTK-LOG--allocating buffers for FW images...
12:42:21 - XFSTK-LOG--G:/Android/AsusZ580CA-BootloaderFirmware/xFSTK_ZE551ML-sal358-amtech.vn/ifwi.bin size:4194468 bytes
12:42:21 - XFSTK-LOG--G:/Android/AsusZ580CA-BootloaderFirmware/xFSTK_ZE551ML-sal358-amtech.vn/ifwi.bin size:4194468 bytes
12:42:21 - XFSTK-LOG--allocating buffers for primary/secondary security FW images...
12:42:21 - XFSTK-LOG--loading buffers for FW images...
12:42:21 - XFSTK-LOG--loading buffers for FUPH...
12:42:21 - XFSTK-STATUS--FW(Miscdnx) download is in progress ...
12:42:21 - XFSTK-LOG--StartFw
12:42:21 - XFSTK-LOG--sending 6 DWORDS of DnxFW size and checksum...
12:42:21 - XFSTK-LOG--WriteOutPipe (±
12:42:21 - XFSTK-LOG--WriteOutPipe 0
12:42:21 - XFSTK-LOG--Write --->(±
12:42:21 - XFSTK-LOG--LogProgress
12:42:21 - XFSTK-LOG--End of MrfdStHandleFwMisc
12:42:21 - XFSTK-LOG--LogProgress
12:42:21 - XFSTK-LOG--GetOpCode
12:42:21 - XFSTK-LOG--ReadInAck
12:42:21 - XFSTK-LOG--GetAck - DCFI00(6)
12:42:21 - XFSTK-STATUS--FW: Sending DnX DCFI00 ...
12:42:21 - XFSTK-LOG--WriteOutPipe __BINARY__
12:42:21 - XFSTK-LOG--WriteOutPipe 0
12:42:21 - XFSTK-LOG--Write --->__BINARY__
12:42:21 - XFSTK-LOG--LogProgress
12:42:21 - XFSTK-LOG--GetOpCode
12:42:21 - XFSTK-LOG--ReadInAck
12:42:22 - XFSTK-LOG--GetAck - ER04(4)
12:42:22 - XFSTK-LOG--LogError
12:42:22 - XFSTK-STATUS--Error Code: 40 - ER04 - SecurityInit
12:42:22 - XFSTK-LOG--void MerrifieldDownloader::do_abort()
12:42:22 - XFSTK-LOG--Abort
12:42:22 - XFSTK-STATUS--FAIL
12:42:22 - XFSTK-STATUS--Errors encounter during FW download. Aborting ...

Do you have a stock binaries (IFWI, droidboot for this device)? I assume that you are flashing with binaries for it. On top of that, have you tried xFSTK from Flash Phone Tool? AFAIU it's a combine to use instead of xFSTK separately. Also there is a version of xFSTK for Linux that is higher than what you have here.

Hi everybody .I have one windows tablet 8.1 (processor intel atom Z3735F. 1.83 Ghz) name redeer .I bought it from somebody but it is bricked I gues due to windows 10 upgrading and its getting until 4 % thats it stops right there and do nothing .
I thought its gonna be easy to install any linux or android on it but it become a nightmare because cant even enter into bios.Is there any tool or something just to give that option for booting from usb .I tried also with windows for trouble shouting usb but it doesnt work .perhaps have any idea how can i get rid of windows and install any system on it android ,linux etc .anything i dont care

maktir said:
(processor intel atom Z3735F. 1.83 Ghz)
Click to expand...
Click to collapse
This thread is about quite a different SoC.
maktir said:
I thought its gonna be easy to install any linux or android on it but it become a nightmare because cant even enter into bios.Is there any tool or something just to give that option for booting from usb .I tried also with windows for trouble shouting usb but it doesnt work .perhaps have any idea how can i get rid of windows and install any system on it android ,linux etc .anything i dont care
Click to expand...
Click to collapse
Perhaps this will help: https://hansdegoede.livejournal.com/25413.html

Related

[Q] rooting failure? st25i GB unlocked

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>cd android-sdk
C:\android-sdk>cd tools
C:\android-sdk\tools>fastboot.exe -i 0x0fce oem unlock 0xFF6C0B6CABAA77A3
... INFOUnlock phone requested
FAILED (remote: Phone is already unlocked!)
C:\android-sdk\tools>
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (13.10.2012) v15 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
@x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
1869 KB/s (119636 bytes in 0.062s)
remote object '/system/bin/ric' does not exist
.
Found Sony Backup-Restore.apk
LT26,LT22 etc. mode enabled!
.
Pushing busybox....
2338 KB/s (1085140 bytes in 0.453s)
Pushing su binary ....
2874 KB/s (91980 bytes in 0.031s)
Pushing Superuser app
2491 KB/s (996704 bytes in 0.390s)
Making busybox runable ...
.
Pushing fake Backup
2304 KB/s (73728 bytes in 0.031s)
Extracting fakebackup on device ...
Watch now your device. Select the backup named RootMe and restore it!
Starting: Intent { act=android.intent.action.VIEW dat=com.sonyericsson.vendor.ba
ckuprestore/.ui.BackupActivity }
Error: Activity not started, unable to resolve Intent { act=android.intent.actio
n.VIEW dat=com.sonyericsson.vendor.backuprestore/.ui.BackupActivity flg=0x100000
00 }
If all is successful i will tell you, if not this shell will run forever.
Running ......
05/040/2012 07:40:56 - INFO - <- This level is successfully initialized
05/040/2012 07:40:56 - INFO - Flashtool Version 0.9.8.0 built on 2012-10-01 19:35:32
05/040/2012 07:40:56 - INFO - You can drag and drop ftf files here to start flashing them
05/040/2012 07:40:58 - INFO - Device connected with USB debugging on
05/040/2012 07:40:59 - INFO - Connected device : ST25
05/040/2012 07:40:59 - INFO - Installed version of busybox : N/A
05/040/2012 07:40:59 - INFO - Android version : 2.3.7 / kernel version : 2.6.35.7+ / Build number : 6.0.B.3.184
05/041/2012 07:41:02 - INFO - Decrypting C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue.enc to C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue
05/041/2012 07:41:06 - INFO - Pushing C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue to /data/local/tmp
05/041/2012 07:41:06 - INFO - Pushing C:\Flashtool\.\devices\ST25\busybox\1.19.0\busybox to /data/local/tmp/busybox
05/041/2012 07:41:06 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
05/041/2012 07:41:07 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
05/041/2012 07:41:07 - INFO - Running part1 of Root Exploit, please wait
05/041/2012 07:41:26 - INFO - Waiting for device. After 60secs, stop waiting will be forced
05/042/2012 07:42:30 - INFO - Forced stop waiting.
05/042/2012 07:42:30 - ERROR - The part1 exploit did not work
05/042/2012 07:42:30 - INFO - Cleaning files
I want to root my phone mainly to clean **** like facebook and other which eat ram in stock rom. After that all i dont have any icons from supersu/superuser in list. In bin4ry script nothing happen but its supposed to show backup and restore window i think.
The method works only on ICS
Tapatalked !
Ok problem solved i uploaded rooted kernel for gb. And now all works fine. Topic can be closed or go to trash, thanks for reply.

dell venue 7 stock firmware/os image?

as directed from xda-assist,
dell venue 7 3730, it just quit working on me last week, been trying to fix it, tried to use clockwork but it couldnt format "data" so i tried to flash the image from http://forum.xda-developers.com/dell...o-4-3-t2906002 sadly i now have a paper weight, however, it shows up in intel soc and shows up on xFSTK-Downloader problem is i need the 4 bin files (firmware and os) for the 3730 (wifi only) but the dell "sources" only has the kernal image http://opensource.dell.com/releases/...verTrail_plus/ am i basically hosed here or does some one some where have the stock files?
note: at this point the tablet is "empty" and in "forced download" mode, fastboot and adb are not an option. it needs a reflash as mentioned.
a bit more details on how i wound up here. last week the tablet was working fine, i locked it, went to do other things, came back to find the screen black as youd expect but i could see the back light was on. i attempted to unlock it but it was un responsive. i wound up doing a hard reset.
tried to boot it up as per normal it looked like it was going to do that but got "stuck" on the dell logo for an hour. i did another hard reset and got in to droidboot, selected recovery only to have it do the same thing. i tried usinghttp://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 and seemed to work except it just sat there with that hat on. after trying to manually issue the commands to enter recovery (and it still getting stuck on the dell logo for over an hour) i gave up for a bit.. then i had a moment of "screw it" figured if it wasnt going to work i might as well run down the battery and toss it.
loaded clockwork through the CWM (i chould note the options where 5 then T3), and unplugged from the pc and walked off... a smidge over an hour later clockwork loaded, HOORAY! i thought, issued "recovery" after what seemed like forever it stated (going from memory here) "formatting \data,,,, unable to mount \data skipping" uh oh,, let it finish any way. only to have the same problem. after googling "unable to mount data" with my model number i ran across the aforementioned thread, flashed the "stock" imagies through fastboot, which seemed to work, but upon reboot i get nothing, no light nothing. however connected to the PC i can hear it connect > disconnect > disconnect. as mentioned if i put it in forced download mode it shows up under intel soc..
so im hoping some one around here has the 4 bin files i need to reflash the firmware/os since ill need to do it through xFSTK.. i "think" dell had them in sources, but a quick search shows some one asked about modifing it on july 7th, and on july 31st the folder in question was modified, so i guess some one at dell didnt like that..
any help would be apreciated, id prefer "none rooted" as i do use a few apps that consider root a "bad word" (i hate that) but at this point ill take what ever i can get.
if youve read this far, thank you! i know im long winded :laugh:
Sorry didn't read the whole post but stock files are here.
http://forum.xda-developers.com/showthread.php?p=51090040
social-design-concepts said:
Sorry didn't read the whole post but stock files are here.
http://forum.xda-developers.com/showthread.php?p=51090040
Click to expand...
Click to collapse
sorry no, those are image files, which would be fine if fastboot worked. this tablet is "blank" its in "forced download mode" i need the 4 bin files, 2 for firmware 2 for os, example if i was unbricking a venue 8 i could head over to dell sources, download the apropriate tgz file, inside said file would be the 4 bins i would load in to xFSTK i.e.
FW DnX= dnx_fwr_PRQ.bin
IFWI= for_product_ifwi_PRQ.bin
OS DnX= dnx_osr_PRQ.bin
OS Image= droidboot.img.POS.bin
the frustrating thing is, i know they existed because of this post http://en.community.dell.com/support-forums/mobile-devices/f/4585/t/19640340 on july 8th, like i said though, i guess some one at dell didnt like that because now the only thing that exists in that folder is the kernel.
thedragonmaster said:
sorry no, those are image files, which would be fine if fastboot worked. this tablet is "blank" its in "forced download mode" i need the 4 bin files, 2 for firmware 2 for os, example if i was unbricking a venue 8 i could head over to dell sources, download the apropriate tgz file, inside said file would be the 4 bins i would load in to xFSTK i.e.
FW DnX= dnx_fwr_PRQ.bin
IFWI= for_product_ifwi_PRQ.bin
OS DnX= dnx_osr_PRQ.bin
OS Image= droidboot.img.POS.bin
the frustrating thing is, i know they existed because of this post http://en.community.dell.com/support-forums/mobile-devices/f/4585/t/19640340 on july 8th, like i said though, i guess some one at dell didnt like that because now the only thing that exists in that folder is the kernel.
Click to expand...
Click to collapse
They never existed officially from Dell ever for the Venue 7 3730 but here these are for the KikKat v1.33 last kitkat build : View attachment ifwi.zip
ifwi.bin and dnx_fw.bin are from the Venue 7 KK4.4.2v1.33 OTA, fastboot.pos.img.bin is dumped from Venue 7 KK4.4.2v1.33 and just renamed to .img.bin and dnx_os.bin is from the unlock for the Venue 8 3830.
All those downloads i provided contain ifwi files the only file they might be missing is the dnx_os.bin but that can be used from the Venue 8 3830 believe me, my root method evolved out of the fact that i had bricked Venue 7 3730 and Dell wouldn't release those 4 files hope this helps you.
social-design-concepts said:
They never existed officially from Dell ever for the Venue 7 3730 but here these are for the KikKat v1.33 last kitkat build : View attachment 3456103
ifwi.bin and dnx_fw.bin are from the Venue 7 KK4.4.2v1.33 OTA, fastboot.pos.img.bin is dumped from Venue 7 KK4.4.2v1.33 and just renamed to .img.bin and dnx_os.bin is from the unlock for the Venue 8 3830.
All those downloads i provided contain ifwi files the only file they might be missing is the dnx_os.bin but that can be used from the Venue 8 3830 believe me, my root method evolved out of the fact that i had bricked Venue 7 3730 and Dell wouldn't release those 4 files hope this helps you.
Click to expand...
Click to collapse
thank you, sadly im getting a "Windriver Error: 0x20000015, Timeout expired" when i try. im wondering if my original theory of why this all happend to begin with, that the flash memory went bad is actually correct. either that or im doing some thing wrong.. but it does show under intel soc so im not sure how its a driver problem.. :: sigh :: ah well, it was worth a shot. thanks for the assist
Code:
xfstklog_Mon_Aug_31_12-01-23_2015.txt
12:01:09 - XFSTK Downloader API 1.5.1 Copyright (c) 2013 Intel Corporation
12:01:09 - fwdnx -- C:/Users/paul/Desktop/ifwi/dnx_fwr_firmware_P706T_NoModem.bin
12:01:09 - fwimage -- C:/Users/paul/Desktop/ifwi/ifwi_firmware_P706T_NoModem-F9.70.bin
12:01:09 - osdnx -- C:/Users/paul/Desktop/ifwi/dnx_pos.bin
12:01:09 - osimage -- C:/Users/paul/Desktop/ifwi/fastboot.pos.img.bin
12:01:09 - gpflags -- 0x80000007
12:01:09 - XFSTK-LOG--USBSN:--virtual bool CloverviewPlusDownloader::SetDevice(IGenericDevice*)
12:01:09 - Initiating download...
12:01:09 - XFSTK-LOG--USBSN:--virtual bool CloverviewPlusDownloader::UpdateTarget()
12:01:09 - XFSTK-LOG--USBSN:--FWDnxPath -- C:/Users/paul/Desktop/ifwi/dnx_fwr_firmware_P706T_NoModem.bin
12:01:09 - XFSTK-LOG--USBSN:--FWImagePath -- C:/Users/paul/Desktop/ifwi/ifwi_firmware_P706T_NoModem-F9.70.bin
12:01:09 - XFSTK-LOG--USBSN:--SoftfusesPath -- BLANK.bin
12:01:09 - XFSTK-LOG--USBSN:--OSDnxPath -- C:/Users/paul/Desktop/ifwi/dnx_pos.bin
12:01:09 - XFSTK-LOG--USBSN:--OSImagePath -- C:/Users/paul/Desktop/ifwi/fastboot.pos.img.bin
12:01:09 - XFSTK-LOG--USBSN:--MiscDnxPath --
12:01:09 - XFSTK-LOG--USBSN:--Gpflags -- 80000007
12:01:09 - XFSTK-LOG--USBSN:--DebugLevel -- ffffffff
12:01:09 - XFSTK-LOG--USBSN:--UsbDelay ms -- 0
12:01:09 - XFSTK-LOG--USBSN:--TransferType -- USB
12:01:09 - XFSTK-LOG--USBSN:--WipeIFWI -- False
12:01:09 - XFSTK-LOG--USBSN:--Idrq -- False
12:01:09 - XFSTK-LOG--USBSN:--Verbose -- True
12:01:09 - XFSTK-LOG--USBSN:--void CloverviewPlusDownloader::Init()
12:01:09 - XFSTK-LOG--USBSN:--Open
12:01:09 - XFSTK-LOG--USBSN:--void CloverviewPlusUtils::SetUsbsn(char*)
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--USB Device found - USBSN: 508639CE6B6240AA Address:11
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--void CloverviewPlusDownloader::do_update(CloverviewPlusOptions*)
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Start
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Sending DnER...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe DnER
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe 0
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Write --->DnER
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetOpCode
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--ReadInAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck - DFRM(0x4)
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--FW: Handle virgin part DnX ...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetOpCode
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Changing to DLDR_STATE_FW_NORMAL ...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--InitNoSize
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--CheckFile
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--CheckFile
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--C:/Users/paul/Desktop/ifwi/dnx_fwr_firmware_P706T_NoModem.bin size:99296 bytes
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--C:/Users/paul/Desktop/ifwi/dnx_fwr_firmware_P706T_NoModem.bin size:99296 bytes
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--InitFwImage
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--C:/Users/paul/Desktop/ifwi/ifwi_firmware_P706T_NoModem-F9.70.bin size:2031600 bytes
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--allocating buffers for FW images...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--C:/Users/paul/Desktop/ifwi/ifwi_firmware_P706T_NoModem-F9.70.bin size:2031600 bytes
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--allocating buffers for primary/secondary security FW images...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--loading buffers for FW images...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--loading buffers for primary/secondary security FW images...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--loading buffers for FUPH...
12:01:09 - XFSTK-STATUS--USBSN:508639CE6B6240AA--FW download is in progress ...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--StartFw
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--CLVP Total number of calculated steps : 28.000000
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--sending 6 DWORDS of DnxFW size and checksum...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe à?
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe 0
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Write --->à?
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--End of StHandleFwNormal
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetOpCode
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--ReadInAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck - DXBL(0x4)
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--FW: Sending DnX ...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--FwDXBL
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Sending FW Dnx data...5932e60
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe __BINARY__
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe 0
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Write --->__BINARY__
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--LogProgress
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetOpCode
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--ReadInAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck - RUPHS(0x8)
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--FW: Sending FW Update Profile Hdr Size...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe $
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe 0
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Write --->$
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--LogProgress
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetOpCode
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--ReadInAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck - RUPH(0x4)
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--FW: Sending FW Update Profile Hdr...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe __BINARY__
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe 0
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Write --->__BINARY__
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--LogProgress
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetOpCode
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--ReadInAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck - DMIP(0x4)
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--FW: Sending MIP...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe __BINARY__
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe 0
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Write --->__BINARY__
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--LogProgress
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetOpCode
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--ReadInAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck
12:01:14 - XFSTK-LOG--USBSN:508639CE6B6240AA--usb_bulk_read() fails
12:01:14 - XFSTK-LOG--USBSN:508639CE6B6240AA--Windriver Error: 0x20000015, Timeout expired
12:01:19 - XFSTK-LOG--USBSN:508639CE6B6240AA--usb_bulk_read() fails
12:01:19 - XFSTK-LOG--USBSN:508639CE6B6240AA--Windriver Error: 0x20000015, Timeout expired
12:01:23 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck - ER25(0x4)
12:01:23 - XFSTK-LOG--USBSN:508639CE6B6240AA--LogError
12:01:23 - XFSTK-STATUS--USBSN:508639CE6B6240AA--Error Code: 34 - ER25 - Storage Programming Error
12:01:23 - XFSTK-LOG--USBSN:508639CE6B6240AA--void CloverviewPlusDownloader::do_abort()
12:01:23 - XFSTK-LOG--USBSN:508639CE6B6240AA--Abort
12:01:23 - XFSTK-STATUS--USBSN:508639CE6B6240AA--FAIL
12:01:23 - XFSTK-STATUS--USBSN:508639CE6B6240AA--Errors encounter during FW download. Aborting ...
thedragonmaster said:
thank you, sadly im getting a "Windriver Error: 0x20000015, Timeout expired" when i try. im wondering if my original theory of why this all happend to begin with, that the flash memory went bad is actually correct. either that or im doing some thing wrong.. but it does show under intel soc so im not sure how its a driver problem.. :: sigh :: ah well, it was worth a shot. thanks for the assist
Code:
xfstklog_Mon_Aug_31_12-01-23_2015.txt
12:01:09 - XFSTK Downloader API 1.5.1 Copyright (c) 2013 Intel Corporation
12:01:09 - fwdnx -- C:/Users/paul/Desktop/ifwi/dnx_fwr_firmware_P706T_NoModem.bin
12:01:09 - fwimage -- C:/Users/paul/Desktop/ifwi/ifwi_firmware_P706T_NoModem-F9.70.bin
12:01:09 - osdnx -- C:/Users/paul/Desktop/ifwi/dnx_pos.bin
12:01:09 - osimage -- C:/Users/paul/Desktop/ifwi/fastboot.pos.img.bin
12:01:09 - gpflags -- 0x80000007
12:01:09 - XFSTK-LOG--USBSN:--virtual bool CloverviewPlusDownloader::SetDevice(IGenericDevice*)
12:01:09 - Initiating download...
12:01:09 - XFSTK-LOG--USBSN:--virtual bool CloverviewPlusDownloader::UpdateTarget()
12:01:09 - XFSTK-LOG--USBSN:--FWDnxPath -- C:/Users/paul/Desktop/ifwi/dnx_fwr_firmware_P706T_NoModem.bin
12:01:09 - XFSTK-LOG--USBSN:--FWImagePath -- C:/Users/paul/Desktop/ifwi/ifwi_firmware_P706T_NoModem-F9.70.bin
12:01:09 - XFSTK-LOG--USBSN:--SoftfusesPath -- BLANK.bin
12:01:09 - XFSTK-LOG--USBSN:--OSDnxPath -- C:/Users/paul/Desktop/ifwi/dnx_pos.bin
12:01:09 - XFSTK-LOG--USBSN:--OSImagePath -- C:/Users/paul/Desktop/ifwi/fastboot.pos.img.bin
12:01:09 - XFSTK-LOG--USBSN:--MiscDnxPath --
12:01:09 - XFSTK-LOG--USBSN:--Gpflags -- 80000007
12:01:09 - XFSTK-LOG--USBSN:--DebugLevel -- ffffffff
12:01:09 - XFSTK-LOG--USBSN:--UsbDelay ms -- 0
12:01:09 - XFSTK-LOG--USBSN:--TransferType -- USB
12:01:09 - XFSTK-LOG--USBSN:--WipeIFWI -- False
12:01:09 - XFSTK-LOG--USBSN:--Idrq -- False
12:01:09 - XFSTK-LOG--USBSN:--Verbose -- True
12:01:09 - XFSTK-LOG--USBSN:--void CloverviewPlusDownloader::Init()
12:01:09 - XFSTK-LOG--USBSN:--Open
12:01:09 - XFSTK-LOG--USBSN:--void CloverviewPlusUtils::SetUsbsn(char*)
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--USB Device found - USBSN: 508639CE6B6240AA Address:11
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--void CloverviewPlusDownloader::do_update(CloverviewPlusOptions*)
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Start
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Sending DnER...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe DnER
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe 0
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Write --->DnER
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetOpCode
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--ReadInAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck - DFRM(0x4)
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--FW: Handle virgin part DnX ...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetOpCode
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Changing to DLDR_STATE_FW_NORMAL ...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--InitNoSize
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--CheckFile
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--CheckFile
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--C:/Users/paul/Desktop/ifwi/dnx_fwr_firmware_P706T_NoModem.bin size:99296 bytes
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--C:/Users/paul/Desktop/ifwi/dnx_fwr_firmware_P706T_NoModem.bin size:99296 bytes
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--InitFwImage
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--C:/Users/paul/Desktop/ifwi/ifwi_firmware_P706T_NoModem-F9.70.bin size:2031600 bytes
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--allocating buffers for FW images...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--C:/Users/paul/Desktop/ifwi/ifwi_firmware_P706T_NoModem-F9.70.bin size:2031600 bytes
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--allocating buffers for primary/secondary security FW images...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--loading buffers for FW images...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--loading buffers for primary/secondary security FW images...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--loading buffers for FUPH...
12:01:09 - XFSTK-STATUS--USBSN:508639CE6B6240AA--FW download is in progress ...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--StartFw
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--CLVP Total number of calculated steps : 28.000000
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--sending 6 DWORDS of DnxFW size and checksum...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe à?
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe 0
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Write --->à?
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--End of StHandleFwNormal
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetOpCode
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--ReadInAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck - DXBL(0x4)
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--FW: Sending DnX ...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--FwDXBL
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Sending FW Dnx data...5932e60
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe __BINARY__
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe 0
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Write --->__BINARY__
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--LogProgress
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetOpCode
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--ReadInAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck - RUPHS(0x8)
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--FW: Sending FW Update Profile Hdr Size...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe $
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe 0
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Write --->$
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--LogProgress
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetOpCode
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--ReadInAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck - RUPH(0x4)
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--FW: Sending FW Update Profile Hdr...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe __BINARY__
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe 0
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Write --->__BINARY__
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--LogProgress
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetOpCode
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--ReadInAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck - DMIP(0x4)
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--FW: Sending MIP...
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe __BINARY__
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--WriteOutPipe 0
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--Write --->__BINARY__
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--LogProgress
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetOpCode
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--ReadInAck
12:01:09 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck
12:01:14 - XFSTK-LOG--USBSN:508639CE6B6240AA--usb_bulk_read() fails
12:01:14 - XFSTK-LOG--USBSN:508639CE6B6240AA--Windriver Error: 0x20000015, Timeout expired
12:01:19 - XFSTK-LOG--USBSN:508639CE6B6240AA--usb_bulk_read() fails
12:01:19 - XFSTK-LOG--USBSN:508639CE6B6240AA--Windriver Error: 0x20000015, Timeout expired
12:01:23 - XFSTK-LOG--USBSN:508639CE6B6240AA--GetAck - ER25(0x4)
12:01:23 - XFSTK-LOG--USBSN:508639CE6B6240AA--LogError
12:01:23 - XFSTK-STATUS--USBSN:508639CE6B6240AA--Error Code: 34 - ER25 - Storage Programming Error
12:01:23 - XFSTK-LOG--USBSN:508639CE6B6240AA--void CloverviewPlusDownloader::do_abort()
12:01:23 - XFSTK-LOG--USBSN:508639CE6B6240AA--Abort
12:01:23 - XFSTK-STATUS--USBSN:508639CE6B6240AA--FAIL
12:01:23 - XFSTK-STATUS--USBSN:508639CE6B6240AA--Errors encounter during FW download. Aborting ...
Click to expand...
Click to collapse
With the tablet connected to the PC open windows device manager and locate the tablet under Intel soc.
Press and hold power on the tablet until the device disappears this way you know you're starting from an off state then unplug the device.
Start the batch file for flashing the firmware then connect the device and it should start.
I always had failures trying to flash this tablet if the device wasn't in an off state when starting the firmware flash.
social-design-concepts said:
With the tablet connected to the PC open windows device manager and locate the tablet under Intel soc.
Press and hold power on the tablet until the device disappears this way you know you're starting from an off state then unplug the device.
Start the batch file for flashing the firmware then connect the device and it should start.
I always had failures trying to flash this tablet if the device wasn't in an off state when starting the firmware flash.
Click to expand...
Click to collapse
you mentioned a batch file, so now im thinking im doing this wrong, i was using the xfstk from the dell site (still getting those errors), i uninstalled that and the isoc driver, ive reinstalled the driver and now, batch file? should i be using something other than what im trying to use?
thedragonmaster said:
you mentioned a batch file, so now im thinking im doing this wrong, i was using the xfstk from the dell site (still getting those errors), i uninstalled that and the isoc driver, ive reinstalled the driver and now, batch file? should i be using something other than what im trying to use?
Click to expand...
Click to collapse
I'll play with it tonight I use a modified version of the batch files for the venue 8 3830 I haven't tested with the latest version of the soc / dnx driver but I'll test tonight and post the files I use f
social-design-concepts said:
I'll play with it tonight I use a modified version of the batch files for the venue 8 3830 I haven't tested with the latest version of the soc / dnx driver but I'll test tonight and post the files I use f
Click to expand...
Click to collapse
just wanted to touch base and see if you where able to test it out, and if it worked what i was doing wrong.
thedragonmaster
Click to expand...
Click to collapse
Have you tried using xfstk with ubuntu, a vmware may be.
Its only a suggestion..
http://www.hacktohell.org/2014/11/compiling-xfstk-on-ubuntu-1404-lts.html
Please reply if you get any hint.
the internal storage space is reduced.
social-design-concepts said:
They never existed officially from Dell ever for the Venue 7 3730 but here these are for the KikKat v1.33 last kitkat build : View attachment 3456103
ifwi.bin and dnx_fw.bin are from the Venue 7 KK4.4.2v1.33 OTA, fastboot.pos.img.bin is dumped from Venue 7 KK4.4.2v1.33 and just renamed to .img.bin and dnx_os.bin is from the unlock for the Venue 8 3830.
All those downloads i provided contain ifwi files the only file they might be missing is the dnx_os.bin but that can be used from the Venue 8 3830 believe me, my root method evolved out of the fact that i had bricked Venue 7 3730 and Dell wouldn't release those 4 files hope this helps you.
Click to expand...
Click to collapse
hi, by using the files provided by you, i find the internal storage space is reduced to 11.6g which should be more than 13g originally. the start logo is changed to Intel inside instead of Dell. What's the matter ? many thanks.
adarshprakash said:
Have you tried using xfstk with ubuntu, a vmware may be.
Its only a suggestion..
http://www.hacktohell.org/2014/11/compiling-xfstk-on-ubuntu-1404-lts.html
Please reply if you get any hint.
Click to expand...
Click to collapse
ive never been able to get a handle on linux, and heres why, when you follow the directions, stuff happens.
Code:
[email protected]:~/Desktop/tabsource/xfstk-build/linux-source-package$ export BUILD_VERSION=0.0.0
[email protected]:~/Desktop/tabsource/xfstk-build/linux-source-package$ sudo cmake .
**** Starting Downloader Build Configuration ****
-- The following C++ features are required:
CMake Error at CMakeLists.txt:58 (MESSAGE):
-- BUILD_VERSION is not set!
-- Configuring incomplete, errors occurred!
See also "/home/paul/Desktop/tabsource/xfstk-build/linux-source-package/CMakeFiles/CMakeOutput.log".
[email protected]:~/Desktop/tabsource/xfstk-build/linux-source-package$
i think its just a lost cause...
thedragonmaster said:
ive never been able to get a handle on linux, and heres why, when you follow the directions, stuff happens.
Code:
[email protected]:~/Desktop/tabsource/xfstk-build/linux-source-package$ export BUILD_VERSION=0.0.0
[email protected]:~/Desktop/tabsource/xfstk-build/linux-source-package$ sudo cmake .
**** Starting Downloader Build Configuration ****
-- The following C++ features are required:
CMake Error at CMakeLists.txt:58 (MESSAGE):
-- BUILD_VERSION is not set!
-- Configuring incomplete, errors occurred!
See also "/home/paul/Desktop/tabsource/xfstk-build/linux-source-package/CMakeFiles/CMakeOutput.log".
[email protected]:~/Desktop/tabsource/xfstk-build/linux-source-package$
i think its just a lost cause...
Click to expand...
Click to collapse
I think you missed a line..
export DISTRIBUTION_NAME=ubuntu14.04
export BUILD_VERSION=0.0.0
B/w I am not an expert at this..
adarshprakash said:
I think you missed a line..
export DISTRIBUTION_NAME=ubuntu14.04
export BUILD_VERSION=0.0.0
B/w I am not an expert at this..
Click to expand...
Click to collapse
nope, same problem
Code:
[email protected]:~/Desktop/tabsource/xfstk-build/linux-source-package$ export DISTRIBUTION_NAME=ubuntu14.04
[email protected]:~/Desktop/tabsource/xfstk-build/linux-source-package$ export BUILD_VERSION=0.0.0
[email protected]:~/Desktop/tabsource/xfstk-build/linux-source-package$ sudo cmake .
[sudo] password for paul:
**** Starting Downloader Build Configuration ****
-- The following C++ features are required:
CMake Error at CMakeLists.txt:58 (MESSAGE):
-- BUILD_VERSION is not set!
-- Configuring incomplete, errors occurred!
See also "/home/paul/Desktop/tabsource/xfstk-build/linux-source-package/CMakeFiles/CMakeOutput.log".
[email protected]:~/Desktop/tabsource/xfstk-build/linux-source-package$
im just going to assume that since its been a month since
social-design-concepts said:
I'll play with it tonight I use a modified version of the batch files for the venue 8 3830 I haven't tested with the latest version of the soc / dnx driver but I'll test tonight and post the files I use f
Click to expand...
Click to collapse
that they where unable to get it to work either.
my dell venue 7 wifi is not detected on PC after installing USB driver
Cmd shows 'waiting for device' always
when i start the .bat file it always shows waiting for device. please help me . i am struggling for a week now. please help

Flashtool error with KERNEL 2.6.32.61-nAa-jb-06

Hey guys
Need some help as i got serius issues getting my old X10 Mini updated.
its currently running an old nAa kernel and im looking at getting the latest one and also Android 4x on it.
Im using the Kernel posted here:
http://forum.xda-developers.com/showpost.php?p=64910212&postcount=267
When trying to flash this kernel using Flashtool i get this error and the whole process is done in a few seconds.
Code:
07/005/2016 19:05:16 - INFO - Device disconnected
07/005/2016 19:05:18 - INFO - Device connected in flash mode
07/005/2016 19:05:18 - INFO - Opening device for R/W
07/005/2016 19:05:18 - INFO - Reading device information
07/005/2016 19:05:18 - INFO - Phone ready for flashmode operations.
07/005/2016 19:05:18 - INFO - Opening TA partition 2
07/005/2016 19:05:18 - INFO - Current device : E10i - CB511KABUT - 1238-0549_R10B - 1235-3408_2.1.1.A.0.6 - WORLD-1-8_2.1.1.A.0.6
07/005/2016 19:05:18 - INFO - Closing TA partition
07/005/2016 19:05:18 - INFO - Start Flashing
07/005/2016 19:05:18 - INFO - Using an unofficial loader
07/005/2016 19:05:18 - INFO - Processing loader_unlocked.sin
07/005/2016 19:05:18 - INFO - Checking header
07/005/2016 19:05:18 - ERROR - Processing of loader_unlocked.sin finished with errors.
07/005/2016 19:05:18 - INFO - Ending flash session
Dunno why it gives error on loader_unlocked.sin , but its getting quite frustrating.
Not that this is a daily phone or anything, i just want it up and running with the latest Android it can handle and use it as a spare phone or just to have fun with this oldie.
Apriciate any help to solve this issue as i googled for days trying to figure it out.
Adding:
Also using Win10 64Bit.
Did disable driver signature and added the driverpack.
Still the same issue
Flashtool running Degub mode
Code:
08/031/2016 12:31:45 - INFO - Device connected in flash mode
08/031/2016 12:31:45 - INFO - Opening device for R/W
08/031/2016 12:31:45 - INFO - Reading device information
08/031/2016 12:31:45 - DEBUG - Reading packet from phone
08/031/2016 12:31:45 - DEBUG - IN : CommandID : 1 / Flags : false,false,false / Data length : 46 / Data CRC32 : [B3, CC, 8A, 78]
08/031/2016 12:31:45 - DEBUG - VER="r8A029";DATE="20100601";TIME="12:17:00";VER="r8A029";UNIQUE_DEV_ID="4B629045635A7AE04A6E21BE32598A2E4FD5CF80";CXC="1229-3593";TYPE="S1_EROM";SEC_LOCK_STATUS="LOCKED";MAN_ID="0020";DEV_ID="00BC";EROM_AID="0001";LOADER_AID="0001";SW_AID="0001";CUST_AID="0001";SIM_LOCK_AID="0001";IMEI="01231200502147";MSN="CB511KABUT";SIN_VER="0001";SIMLOCK_TAMP="TAMPERED";AID_TAMP="NOT_TAMPERED";LOADER_ROOT="S1_Loader_Root_8e35";EROM_ROOT="S1_EROM_Root_f54f";SW_ROOT="S1_SW_Root_3edc";CUST_ROOT="S1_Cust_Root_732f";SIM_LOCK_ROOT="S1_SL_Root_a640";HW_CONF_ROOT="S1_HWConf_Root_4b8c";
08/031/2016 12:31:46 - DEBUG - First command reply (hook) : PROT_VER="01";DATE="20100601";TIME="12:17:00";VER="r8A029";UNIQUE_DEV_ID="4B629045635A7AE04A6E21BE32598A2E4FD5CF80";CXC="1229-3593";TYPE="S1_EROM";SEC_LOCK_STATUS="LOCKED";MAN_ID="0020";DEV_ID="00BC";EROM_AID="0001";LOADER_AID="0001";SW_AID="0001";CUST_AID="0001";SIM_LOCK_AID="0001";IMEI="01231200502147";MSN="CB511KABUT";SIN_VER="0001";SIMLOCK_TAMP="TAMPERED";AID_TAMP="NOT_TAMPERED";LOADER_ROOT="S1_Loader_Root_8e35";EROM_ROOT="S1_EROM_Root_f54f";SW_ROOT="S1_SW_Root_3edc";CUST_ROOT="S1_Cust_Root_732f";SIM_LOCK_ROOT="S1_SL_Root_a640";HW_CONF_ROOT="S1_HWConf_Root_4b8c";
08/031/2016 12:31:46 - INFO - Phone ready for flashmode operations.
08/031/2016 12:31:46 - INFO - Opening TA partition 2
08/031/2016 12:31:46 - DEBUG - Writing packet to phone
08/031/2016 12:31:46 - DEBUG - OUT : CommandID : 9 / Flags : false,true,false / Data length : 1 / Data CRC32 : [EE, 0E, 61, 2C]
08/031/2016 12:31:46 - DEBUG - Reading packet from phone
08/031/2016 12:31:46 - DEBUG - IN : CommandID : 9 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
08/031/2016 12:31:46 - DEBUG - Writing packet to phone
08/031/2016 12:31:46 - DEBUG - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [F0, 01, 48, CC]
08/031/2016 12:31:46 - DEBUG - Reading packet from phone
08/031/2016 12:31:46 - DEBUG - IN : CommandID : 12 / Flags : false,false,false / Data length : 4 / Data CRC32 : [62, 4B, C8, A7]
08/031/2016 12:31:46 - DEBUG - Writing packet to phone
08/031/2016 12:31:46 - DEBUG - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [5D, EC, A5, 43]
08/031/2016 12:31:46 - DEBUG - Reading packet from phone
08/031/2016 12:31:46 - DEBUG - IN : CommandID : 12 / Flags : false,false,false / Data length : 10 / Data CRC32 : [5D, A9, 83, 87]
08/031/2016 12:31:46 - DEBUG - Writing packet to phone
08/031/2016 12:31:47 - DEBUG - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [46, 67, 65, F1]
08/031/2016 12:31:47 - DEBUG - Reading packet from phone
08/031/2016 12:31:47 - DEBUG - IN : CommandID : 12 / Flags : false,false,false / Data length : 14 / Data CRC32 : [3F, 7E, 77, 5F]
08/031/2016 12:31:47 - DEBUG - Writing packet to phone
08/031/2016 12:31:47 - DEBUG - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [D8, 03, F0, 52]
08/031/2016 12:31:47 - DEBUG - Reading packet from phone
08/031/2016 12:31:47 - DEBUG - IN : CommandID : 12 / Flags : false,false,false / Data length : 21 / Data CRC32 : [6A, E6, 13, 8A]
08/031/2016 12:31:47 - DEBUG - Writing packet to phone
08/031/2016 12:31:47 - DEBUG - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [DF, 6E, 34, 4B]
08/031/2016 12:31:47 - DEBUG - Reading packet from phone
08/031/2016 12:31:47 - DEBUG - IN : CommandID : 12 / Flags : false,false,false / Data length : 21 / Data CRC32 : [3D, 5D, 5C, 6B]
08/031/2016 12:31:47 - INFO - Current device : E10i - CB511KABUT - 1238-0549_R10B - 1235-3408_2.1.1.A.0.6 - WORLD-1-8_2.1.1.A.0.6
08/031/2016 12:31:47 - INFO - Closing TA partition
08/031/2016 12:31:47 - DEBUG - Writing packet to phone
08/031/2016 12:31:47 - DEBUG - OUT : CommandID : 10 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
08/031/2016 12:31:47 - DEBUG - Reading packet from phone
08/031/2016 12:31:47 - DEBUG - IN : CommandID : 10 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
08/031/2016 12:31:47 - INFO - Start Flashing
08/031/2016 12:31:47 - INFO - Using an unofficial loader
08/031/2016 12:31:47 - INFO - Processing loader_unlocked.sin
08/031/2016 12:31:47 - INFO - Checking header
08/031/2016 12:31:47 - DEBUG - Writing packet to phone
08/031/2016 12:31:47 - ERROR - Processing of loader_unlocked.sin finished with errors.
08/031/2016 12:31:47 - INFO - Ending flash session
08/031/2016 12:31:48 - DEBUG - Writing packet to phone
08/031/2016 12:31:48 - DEBUG - OUT : CommandID : 4 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
08/031/2016 12:31:48 - DEBUG - Reading packet from phone
08/031/2016 12:31:48 - DEBUG - IN : CommandID : 5 / Flags : true,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
08/031/2016 12:31:48 - DEBUG - Writing packet to phone
08/031/2016 12:31:48 - DEBUG - OUT : CommandID : 7 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
08/031/2016 12:31:48 - DEBUG - Reading packet from phone
i've now tried nAa's kernel for minicm7 ,9 and 10 also tried 2 diffrent phones and also a Win7 computer
same issue with loader_unlocked.sin on both computers and phones and on all 3 kernels.
Checked with s1tools and it says its unlocked as both phones has an identifier "r" and not "R"
Anyone have any idea what to try now ??
Myrmid0n said:
i've now tried nAa's kernel for minicm7 ,9 and 10 also tried 2 diffrent phones and also a Win7 computer
same issue with loader_unlocked.sin on both computers and phones and on all 3 kernels.
Checked with s1tools and it says its unlocked as both phones has an identifier "r" and not "R"
Anyone have any idea what to try now ??
Click to expand...
Click to collapse
You say in your first post that it's running an old nAa-kernel, but the output from flashtool suggests you're on the original stock firmware.
If you have flashed back to original firmware, it may have a 'locked' bootloader even though it was unlocked before (And the check says it is unlocked). Try the unlock procedure again and then try flashing a custom kernel.
SmG67 said:
You say in your first post that it's running an old nAa-kernel, but the output from flashtool suggests you're on the original stock firmware.
If you have flashed back to original firmware, it may have a 'locked' bootloader even though it was unlocked before (And the check says it is unlocked). Try the unlock procedure again and then try flashing a custom kernel.
Click to expand...
Click to collapse
Im running Minicm7 on both of them. Should be ok then or ?
Myrmid0n said:
Im running Minicm7 on both of them. Should be ok then or ?
Click to expand...
Click to collapse
The output from flashtool says you're on 2.1.1.A.0.6, which is stock firmware and not MiniCM7. Try the unlock procedure again and then try to flash a custom kernel.
SmG67 said:
The output from flashtool says you're on 2.1.1.A.0.6, which is stock firmware and not MiniCM7. Try the unlock procedure again and then try to flash a custom kernel.
Click to expand...
Click to collapse
Should i Flash stock first or just try to unlock it as is with Minicm7 on it ?
Been ages since i delt with this Phone, so i'd better find a guide again
Myrmid0n said:
Should i Flash stock first or just try to unlock it as is with Minicm7 on it ?
Been ages since i delt with this Phone, so i'd better find a guide again
Click to expand...
Click to collapse
According to flashtool it runs stock already... jus try the unlock procedure, I think flashtool can still do that for you without having to find the tutorial. See if that remedies your problems with flashing a kernel.
SmG67 said:
According to flashtool it runs stock already... jus try the unlock procedure, I think flashtool can still do that for you without having to find the tutorial. See if that remedies your problems with flashing a kernel.
Click to expand...
Click to collapse
no luck with flashtool.
dunno y its acting up. i mean,i did flash both phones ages ago with nAa kernel and MiniCM7.
So they should been unlocked allready back then or ?
Code:
11/026/2016 19:26:54 - INFO - (MainSWT.java:155) - Device connected in flash mode
11/026/2016 19:26:54 - INFO - (USBFlashWin32.java:24) - Opening device for R/W
11/026/2016 19:26:55 - INFO - (X10flash.java:1006) - Reading device information
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 1 / Flags : false,false,false / Data length : 46 / Data CRC32 : [B3, CC, 8A, 78]
11/026/2016 19:26:55 - DEBUG - (X10flash.java:1013) - VER="r8A029";DATE="20100601";TIME="12:17:00";
11/026/2016 19:26:55 - DEBUG - (X10flash.java:986) - PROT_VER="01";DATE="20100601";TIME="12:17:00";VER="r8A029";UNIQUE_DEV_ID="F4199098C2C4BF4E06936BBF9CF0DFF9429DA563";CXC="1229-3593";TYPE="S1_EROM";SEC_LOCK_STATUS="LOCKED";MAN_ID="0020";DEV_ID="00BC";EROM_AID="0001";LOADER_AID="0001";SW_AID="0001";CUST_AID="0001";SIM_LOCK_AID="0001";IMEI="01240300343741";MSN="CNBC003NUK";SIN_VER="0001";SIMLOCK_TAMP="TAMPERED";AID_TAMP="NOT_TAMPERED";LOADER_ROOT="S1_Loader_Root_8e35";EROM_ROOT="S1_EROM_Root_f54f";SW_ROOT="S1_SW_Root_3edc";CUST_ROOT="S1_Cust_Root_732f";SIM_LOCK_ROOT="S1_SL_Root_a640";HW_CONF_ROOT="S1_HWConf_Root_4b8c";
11/026/2016 19:26:55 - DEBUG - (X10flash.java:996) - First command reply (hook) : PROT_VER="01";DATE="20100601";TIME="12:17:00";VER="r8A029";UNIQUE_DEV_ID="F4199098C2C4BF4E06936BBF9CF0DFF9429DA563";CXC="1229-3593";TYPE="S1_EROM";SEC_LOCK_STATUS="LOCKED";MAN_ID="0020";DEV_ID="00BC";EROM_AID="0001";LOADER_AID="0001";SW_AID="0001";CUST_AID="0001";SIM_LOCK_AID="0001";IMEI="01240300343741";MSN="CNBC003NUK";SIN_VER="0001";SIMLOCK_TAMP="TAMPERED";AID_TAMP="NOT_TAMPERED";LOADER_ROOT="S1_Loader_Root_8e35";EROM_ROOT="S1_EROM_Root_f54f";SW_ROOT="S1_SW_Root_3edc";CUST_ROOT="S1_Cust_Root_732f";SIM_LOCK_ROOT="S1_SL_Root_a640";HW_CONF_ROOT="S1_HWConf_Root_4b8c";
11/026/2016 19:26:55 - INFO - (X10flash.java:1022) - Phone ready for flashmode operations.
11/026/2016 19:26:55 - INFO - (X10flash.java:440) - Opening TA partition 2
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 9 / Flags : false,true,false / Data length : 1 / Data CRC32 : [EE, 0E, 61, 2C]
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 9 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [F0, 01, 48, CC]
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 12 / Flags : false,false,false / Data length : 4 / Data CRC32 : [62, 4B, C8, A7]
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [5D, EC, A5, 43]
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 12 / Flags : false,false,false / Data length : 10 / Data CRC32 : [66, 85, B7, E5]
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [46, 67, 65, F1]
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 12 / Flags : false,false,false / Data length : 14 / Data CRC32 : [3F, 7E, 77, 5F]
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [D8, 03, F0, 52]
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 12 / Flags : false,false,false / Data length : 21 / Data CRC32 : [6A, E6, 13, 8A]
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [DF, 6E, 34, 4B]
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 12 / Flags : false,false,false / Data length : 21 / Data CRC32 : [3D, 5D, 5C, 6B]
11/026/2016 19:26:56 - INFO - (X10flash.java:589) - Current device : E10i - CNBC003NUK - 1238-0549_R10B - 1235-3408_2.1.1.A.0.6 - WORLD-1-8_2.1.1.A.0.6
11/026/2016 19:26:56 - INFO - (X10flash.java:449) - Closing TA partition
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 10 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 10 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
11/026/2016 19:26:56 - INFO - (X10flash.java:367) - Using an unofficial loader
11/026/2016 19:26:56 - INFO - (X10flash.java:323) - Processing loader_unlocked.sin
11/026/2016 19:26:56 - INFO - (X10flash.java:305) - Checking header
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:56 - ERROR - (X10flash.java:342) - Processing of loader_unlocked.sin finished with errors.
11/026/2016 19:26:56 - ERROR - (GetULCodeJob.java:136) -
11/026/2016 19:26:56 - INFO - (MainSWT.java:1313) - Your phone bootloader cannot be officially unlocked
11/026/2016 19:26:56 - INFO - (MainSWT.java:1314) - You can now unplug and restart your phone
Loaded old Emma. It says what you confirm: locked
So i'll try to get on it 2morrow and see if i can get it unlocked.
Only thing that puzzles med is: how did i manage to get nAa on it with cm7 in the first place if its locked?
Thanx a million for the help so far, will get back asap.
Btw. Should i try to get stock on it before unlocking or go ahead as is ?
Myrmid0n said:
Loaded old Emma. It says what you confirm: locked
So i'll try to get on it 2morrow and see if i can get it unlocked.
Only thing that puzzles med is: how did i manage to get nAa on it with cm7 in the first place if its locked?
Thanx a million for the help so far, will get back asap.
Btw. Should i try to get stock on it before unlocking or go ahead as is ?
Click to expand...
Click to collapse
You may have unlocked it and put nAa-kernel and MiniCM7 on it, but you seem to have flashed stock firmware back, with the original bootloader, that's why it appears locked. Just do the unlock procedure and then flash a new kernel.
SmG67 said:
You may have unlocked it and put nAa-kernel and MiniCM7 on it, but you seem to have flashed stock firmware back, with the original bootloader, that's why it appears locked. Just do the unlock procedure and then flash a new kernel.
Click to expand...
Click to collapse
Well.. im killing myself over this.
Started av fresh start today.
As SEUS is dead now i fired up PC Companion.
Restored the Phone to stock firmware again.
So now the old nAa is gone and its all official firmware and kernel.
I got superuser working as i can see it.
I run Semctools , it goes through with everything. No errors except for the standard
Protocol error when the Phone is rebooting.
Run Flashtool, choose the nAa kernel and press Flash.
Power up the Phone in flash flashmode and it gives the same error when flashing loader_unlocked.sin
I've tried running Semctools a couple more times but get the same issue with flashtool.
Also checked with s1tool which says "r" for unlocked and not "R" for locked ones
Also been looking in Sony's service menu which also says "r"
Dunno what to do anymore.
Thought Semc would unlock the bootloader, so i seriusly dunno what to try now.
Semc is this link btw
http://forum.xda-developers.com/showpost.php?p=17384177&postcount=3
Funny, i found my brothers old X10 mini pro and i am playing around with it.
I updated the firmware using PC Companion, now i am on Firmware Version 2.1-update1, Kernel Version 2.6.29 [email protected] #1, Build Number 2.1.1.C.0.0
Then I unlocked the bootloader using msm7227_semc.cmd and it worked (checked for lowercase 'r' using S1Tool).
After that I tried to flash another kernel to install a custom rom, but i get the same error message.
I tried to flash another firmware, too. Again, the same error message.
I tried to unlock the bootloader agin, this time using FlashTool. It says it can't be done:
14/045/2016 15:45:31 - INFO - Device connected in flash mode
14/045/2016 15:45:31 - INFO - Opening device for R/W
14/045/2016 15:45:31 - INFO - Device ready for R/W.
14/045/2016 15:45:31 - INFO - Reading device information
14/045/2016 15:45:31 - INFO - Phone ready for flashmode operations.
14/045/2016 15:45:31 - INFO - Opening TA partition 2
14/045/2016 15:45:31 - INFO - Current device : U20i - CB511PC6HD - 1238-7168_R5B - 1235-3411_2.1.1.C.0.0 - WORLD-1-8_2.1.1.C.0.0
14/045/2016 15:45:31 - INFO - Closing TA partition
14/045/2016 15:45:31 - INFO - Using an unofficial loader
14/045/2016 15:45:31 - INFO - Processing loader_unlocked.sin
14/045/2016 15:45:31 - INFO - Checking header
14/045/2016 15:45:31 - ERROR - Processing of loader_unlocked.sin finished with errors.
14/045/2016 15:45:31 - ERROR - Error in processHeader : null
14/045/2016 15:45:31 - INFO - Your phone bootloader cannot be officially unlocked
14/045/2016 15:45:31 - INFO - You can now unplug and restart your phone
Click to expand...
Click to collapse
This error appers on both, windows and linux systems.
tOmAtE said:
Funny, i found my brothers old X10 mini pro and i am playing around with it.
I updated the firmware using PC Companion, now i am on Firmware Version 2.1-update1, Kernel Version 2.6.29 [email protected] #1, Build Number 2.1.1.C.0.0
Then I unlocked the bootloader using msm7227_semc.cmd and it worked (checked for lowercase 'r' using S1Tool).
After that I tried to flash another kernel to install a custom rom, but i get the same error message.
I tried to flash another firmware, too. Again, the same error message.
I tried to unlock the bootloader agin, this time using FlashTool. It says it can't be done:
This error appers on both, windows and linux systems.
Click to expand...
Click to collapse
Exactly the same issue i got... even tried to replace the loader_unlocked.sin file in flashtool with msm7227 one.
Same result...
I think i found a solution.
When i started Flashtool out of a Terminal, i noticed some Java-Error-Messages printed to the terminal.
So the problem seems to be in the program itself, not in the flashing-setup.
Using an older version of Flashtool everything worked out.
I used Version 0.9.14.0 (downloaded from here), installed the included drivers and everything worked out.
I was able to flash Firmware 2.1.1.A.0.6 and after that another Kernel and right now i am installing CM10
SmG67 said:
You may have unlocked it and put nAa-kernel and MiniCM7 on it, but you seem to have flashed stock firmware back, with the original bootloader, that's why it appears locked. Just do the unlock procedure and then flash a new kernel.
Click to expand...
Click to collapse
tOmAtE said:
I think i found a solution.
When i started Flashtool out of a Terminal, i noticed some Java-Error-Messages printed to the terminal.
So the problem seems to be in the program itself, not in the flashing-setup.
Using an older version of Flashtool everything worked out.
I used Version 0.9.14.0 (downloaded from here), installed the included drivers and everything worked out.
I was able to flash Firmware 2.1.1.A.0.6 and after that another Kernel and right now i am installing CM10
Click to expand...
Click to collapse
Superb ?
Away at work atm, but will download and try at wednesday.
Did download some old version as i suspected it could be the issue, but havent tried it yet.
Will grab the one u posted instead to make sure it works.
Got 2 x10 mini an 1 X10 to freshen up for the fun of it.
Thanx a bunch for getting back with your solution ??
Worked like a charm with the older version ?

flashtool update 7.0 ERROR - Have read only 524256 byte(s) instead of 708740 byte(s)

when i flash android 7.0, flashtool said this text
18/000/2017 15:00:48 - ERROR - Have read only 524256 byte(s) instead of 708740 byte(s)
18/000/2017 15:00:48 - ERROR - Error flashing. Aborted
ckchakack said:
when i flash android 7.0, flashtool said this text
18/000/2017 15:00:48 - ERROR - Have read only 524256 byte(s) instead of 708740 byte(s)
18/000/2017 15:00:48 - ERROR - Error flashing. Aborted
Click to expand...
Click to collapse
Are you using the latest version of Flashtool?
(0.9.23.0)
http://www.flashtool.net/downloads.php
Flashtool not up-to-date.
ckchakack said:
when i flash android 7.0, flashtool said this text
18/000/2017 15:00:48 - ERROR - Have read only 524256 byte(s) instead of 708740 byte(s)
18/000/2017 15:00:48 - ERROR - Error flashing. Aborted
Click to expand...
Click to collapse
got the same proble, did you any find a solution ?
EDIT : Download the latest version of flashtool
WWeltmeister said:
Are you using the latest version of Flashtool?
(0.9.23.0)
http://www.flashtool.net/downloads.php
Click to expand...
Click to collapse
use this guide to update your flashtool to a version that supports nougat
Flashtool stuck
While flashing the flashtool stucks a the last packet:
17/038/2017 20:38:13 - DEBUG - (X10flash.java:313) - Sending part 704 of 704
17/038/2017 20:38:13 - DEBUG - (USBFlashWin32.java:51) - Writing packet to phone
17/038/2017 20:38:13 - DEBUG - (USBFlashWin32.java:69) - OUT : CommandID : 6 / Flags : false,true,false / Data length : 3109280 / Data CRC32 : 34 E2 4A 64
17/038/2017 20:38:13 - DEBUG - (USBFlashWin32.java:80) - Reading packet from phone
any idea?
Had the boot loader locked itself?
Fazettit said:
While flashing the flashtool stucks a the last packet:
17/038/2017 20:38:13 - DEBUG - (X10flash.java:313) - Sending part 704 of 704
17/038/2017 20:38:13 - DEBUG - (USBFlashWin32.java:51) - Writing packet to phone
17/038/2017 20:38:13 - DEBUG - (USBFlashWin32.java:69) - OUT : CommandID : 6 / Flags : false,true,false / Data length : 3109280 / Data CRC32 : 34 E2 4A 64
17/038/2017 20:38:13 - DEBUG - (USBFlashWin32.java:80) - Reading packet from phone
any idea?
Click to expand...
Click to collapse
Found it - I used the 32bit version and wait for about 15mins!

LWW bricked after flashing custom kernel

i decided to mess around with my old wt19 so after unlocking the bootloader i wanted to install a custom rom. I have some experience with that so im not a complete newbie
I have flashed roms and unlocked bootloaders on multiple devices. I always read carefully instructions etc.
But this one gave me a headache.
After deciding to install a custom rom i had to unlock the bootloader. I had problems with fastboot recognizing the device but after an hour and a half of so of reading ad searching i managed to get it working and unlocked the bootlader.
After that i spent about 50 mnutes looking for a good kernel and after failing to flash one via fastboot i used flashtool to do it.
I used this guide
After seeing no errors i unplugged the phone and tried booting. I pressed power button, the phone vibrated but the screen was always black and nothing happened.
Long pressing power button did not reset, completely unresponsive, i had to pull the battery out to make it vibrate again uppon booting but same thing happened, no response. Flashtool no longer recognises the device the ledt doesnt light up when charging but the phone got hot during this time indicating itwas trying to do something.
After a short while,maybe the battery died, but even pulling out the battery and trying to boot again did not make any vibration indicating it was completely dead.
Kernel i flashed was kappa kernel
I tried booting to kernels cwm recovery but nothing happened.
SO im out of ideas
Any suggestions ?
This is the flashtool log
15/003/2018 16:03:43 - INFO - Flashtool Version 0.9.25.0 built on 17-06-2018 16:00:00
15/003/2018 16:03:43 - INFO - Searching for a web proxy
15/003/2018 16:03:44 - INFO - No proxy found, using direct connection
15/003/2018 16:03:44 - INFO - Syncing devices from github
15/003/2018 16:03:44 - INFO - Opening devices repository.
15/003/2018 16:03:44 - INFO - Scanning devices folder for changes.
15/003/2018 16:03:52 - INFO - Pulling changes from github.
15/003/2018 16:03:53 - INFO - Devices sync finished.
15/003/2018 16:03:53 - INFO - Loading devices database
15/003/2018 16:03:53 - INFO - Loaded 112 devices
15/003/2018 16:03:53 - INFO - Starting phone detection
15/003/2018 16:03:56 - INFO - Device disconnected
15/027/2018 16:27:11 - INFO - Device connected with USB debugging on
15/027/2018 16:27:11 - INFO - Connected device : SonyEricson Xperia Live Walkman
15/027/2018 16:27:11 - INFO - Installed version of busybox : BusyBox v1.18.5 (2011-07-18 07:43:28 PDT) multi-call binary.
15/027/2018 16:27:11 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf / Platform : 32bits / Build number : 4.1.B.0.587
15/027/2018 16:27:11 - INFO - Checking root access
15/027/2018 16:27:12 - INFO - Installing toolbox to device...
15/027/2018 16:27:12 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
15/027/2018 16:27:12 - INFO - Running installftkit as root thru sysrun
15/027/2018 16:27:13 - INFO - Root Access Allowed
15/027/2018 16:27:28 - INFO - Device disconnected
15/027/2018 16:27:56 - INFO - Device connected with USB debugging off
15/027/2018 16:27:56 - INFO - For 2011 devices line, be sure you are not in MTP mode
15/027/2018 16:27:58 - INFO - Device connected with USB debugging on
15/027/2018 16:27:59 - INFO - Connected device : SonyEricson Xperia Live Walkman
15/027/2018 16:27:59 - INFO - Installed version of busybox : BusyBox v1.18.5 (2011-07-18 07:43:28 PDT) multi-call binary.
15/027/2018 16:27:59 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf / Platform : 32bits / Build number : 4.1.B.0.587
15/027/2018 16:27:59 - INFO - Checking root access
15/028/2018 16:28:01 - INFO - Root Access Allowed
15/030/2018 16:30:40 - INFO - Now plug your device in Fastboot Mode
15/030/2018 16:30:48 - INFO - Device disconnected
15/031/2018 16:31:05 - INFO - Device connected in fastboot mode
15/031/2018 16:31:34 - INFO - Selected kernel (boot.img or kernel.sin): C:\adb\platform-tools\KaCoconut2.img
15/031/2018 16:31:34 - INFO - Flashing selected kernel
15/031/2018 16:31:36 - INFO - target didn't report max-download-size
15/031/2018 16:31:36 - INFO - sending 'boot' (5580 KB)...
15/031/2018 16:31:36 - INFO - (bootloader) USB download speed was 9186kB/s
15/031/2018 16:31:36 - INFO - OKAY [ 0.629s]
15/031/2018 16:31:36 - INFO - writing 'boot'...
15/031/2018 16:31:36 - INFO - (bootloader) Download buffer format: boot IMG
15/031/2018 16:31:36 - INFO - (bootloader) Flash of partition 'boot' requested
15/031/2018 16:31:36 - INFO - (bootloader) S1 partID 0x00000003, block 0x00000148-0x00000179
15/031/2018 16:31:36 - INFO - (bootloader) Erase operation complete, 0 bad blocks encountered
15/031/2018 16:31:36 - INFO - (bootloader) Flashing...
15/031/2018 16:31:36 - INFO - (bootloader) Flash operation complete
15/031/2018 16:31:36 - INFO - OKAY [ 1.028s]
15/031/2018 16:31:36 - INFO - finished. total time: 1.657s
15/031/2018 16:31:36 - INFO - FASTBOOT Output:
target didn't report max-download-size
sending 'boot' (5580 KB)...
(bootloader) USB download speed was 9186kB/s
OKAY [ 0.629s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000148-0x00000179
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.028s]
finished. total time: 1.657s
15/031/2018 16:31:36 - INFO - Please check the log before rebooting into system
15/032/2018 16:32:53 - INFO - Device disconnected
15/040/2018 16:40:18 - INFO - Now plug your device in Fastboot Mode
15/042/2018 16:42:29 - INFO - Failed
Click to expand...
Click to collapse

Categories

Resources