Searched the forum but found nothing to fit my problem (at least no thread with a solution...)
I have an Xperia U with ICS ST25i_6.0.B.3.184_Generic_World.
Rooted, unlocked.
Was dreadfully slow and cashed all the time, so i tried to restore the factory default with the Sony Bridge for Mac.
That started, the failed mid-process and told me that he cannot communicate with the installer on the phone.
Of cause boot-up was not happening anymore after this - just a short xperia logo and then some icon telling me that it won't start.
Tried to use flashtool several times.
Flashmode starts, logs this to the console and dowsn't seem to do anything substancial afterwards:
Code:
08/028/2013 22:28:51 - INFO - (MainSWT.java:131) - Device connected in flash mode
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1020
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 35632
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 2097152 ; Partition block size : 512 ; Partition size : 1.0Gb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 4308
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 4194304 ; Partition block size : 512 ; Partition size : 2.0Gb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1438
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 32768 ; Partition block size : 512 ; Partition size : 16.0Mb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1279
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 6144 ; Partition block size : 512 ; Partition size : 3.0Mb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1069
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 256 ; Partition block size : 512 ; Partition size : 0.128Mb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1689
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 16384 ; Partition block size : 512 ; Partition size : 8.0Mb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1602
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 512000 ; Partition block size : 512 ; Partition size : 250.0Mb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1020
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1438
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 32768 ; Partition block size : 512 ; Partition size : 16.0Mb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1028
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 542856009
The green LED goes off after some 20 or 30 seconds and nothing happens.
Phone is stuck with the red loading-LED on and won't do anything afterwards.
Holding VolUp + Power after battry-cycling just makes the blue LED blink once and gives single vibration.
Then the phone goes into the red-LED stasis as well.
The screen doesn't show anything anymore at any time / action.
Is there still hope or will I open a second thread to ask for new phone recommendations?
Post flashtool full log with default log level(info)
IAmNice said:
Have you tried charging the phone for a few hours? Can you boot into fastboot mode? If you can try fastbooting a kernel.
Click to expand...
Click to collapse
Fastboot wont work. Although I installed the driver, rebooted, etc.
Flashtool says:
Code:
08/001/2013 23:01:57 - ERROR - (MainSWT.java:117) - Drivers need to be installed for connected device.
08/001/2013 23:01:57 - ERROR - (MainSWT.java:118) - You can find them in the drivers folder of Flashtool.
It's an XP SP3 running in a Parallels VM.
Reactions to plugging in/out are "normal" in windows terms. The usual "plig plong" and for Fastboot the little popup on the icons tray and the driver-installer popping up. Maybe I need to unload some driver or install a separate pack?
IAmNice said:
If flashtool says so I would do it.
Click to expand...
Click to collapse
I would if I could. Or if he would. Or if he would recognize it when installed
The driver installer says he did it and it doesn't change anything.
But seriously: Is there a way to see if the driver is already there, or remove and reinstall it or just manually add some package?
Bro you got a mac user here also.
Go to flashtool website and download the MAC VERSION of flashtool. Parallels/vmware is very buggy with flashtool as the device connects to the mac, needs some time to the vm. By then, the device would already time out and auto disconnect.
Sent from my LT22i using xda premium
AndroidNoob69 said:
Go to flashtool website and download the MAC VERSION of flashtool. Parallels/vmware is very buggy with flashtool as the device connects to the mac, needs some time to the vm. By then, the device would already time out and auto disconnect.
Click to expand...
Click to collapse
Ah there is a new version for mac? Neat!
So far I only found the terminal version.
That said I used the win/VM version to unlock and flash my phone - went well before.
I also have news:
I kept the phone charging over night and now it won't launch into ANY mode any more.
No Fastboot, no Flashmode. Reset doesn't do nothing.
Time to whip out the JTAG module and solder some adapters?
@brainzilla :hey mate dont worry its not a bigger problem..as you can access fastboot and flashboot so dont worry about the brick ..it is just softbrick..if possible do it in a xp sp3 system..
1.download flashtool for windows 32bit
2.install it
3.inside the installation folder you will find driver installation folder & click it
4.choose fastboot option which is just below the all options
5.connect your device to system with fastboot mod(power (+) vol+)
6.it will show to install driver ..then click it and go to advance option and then choose from hard disk
7.click f1boots driver or something which will be shown
8.then again put the device into fastboot mod
9.it will show your device in flashtool as connected in fastboot
10.Easily flash a kernel and then a custom rom and voila
---------- Post added at 08:43 PM ---------- Previous post was at 08:40 PM ----------
brainzilla said:
Ah there is a new version for mac? Neat!
So far I only found the terminal version.
That said I used the win/VM version to unlock and flash my phone - went well before.
I also have news:
I kept the phone charging over night and now it won't launch into ANY mode any more.
No Fastboot, no Flashmode. Reset doesn't do nothing.
Time to whip out the JTAG module and solder some adapters?
Click to expand...
Click to collapse
means when you are connecting to pc what is happening??are you getting any vibration when try to switch on the device??
bibhu059 said:
means when you are connecting to pc what is happening??are you getting any vibration when try to switch on the device??
Click to expand...
Click to collapse
As of this morning nothing happens anymore.
Well the charge-indicator is red when plugged in. That's it.
No vibrations, further lights or reaction from PC or Mac.
brainzilla said:
As of this morning nothing happens anymore.
Well the charge-indicator is red when plugged in. That's it.
No vibrations, further lights or reaction from PC or Mac.
Click to expand...
Click to collapse
led is getting off after sometime???and when you are trying to click power botton red led is blinking for a while??
bibhu059 said:
led is getting off after sometime???and when you are trying to click power botton red led is blinking for a while??
Click to expand...
Click to collapse
Stays on as long as power is present.
Clicking any button does nothing.
Yesterday evening when I plugged it in for the night to charge the LED went red and the phone entered Flashmode immediately - flashmode stopped after the timeout and when unplugging the charge-LED stayed red forever. Re-plugging didn't change anything, Flashmode didn't start a second time. Taking out the battery made it go off and it stayed like that until plugging it in the next time.
brainzilla said:
Stays on as long as power is present.
Clicking any button does nothing.
Yesterday evening when I plugged it in for the night to charge the LED went red and the phone entered Flashmode immediately - flashmode stopped after the timeout and when unplugging the charge-LED stayed red forever. Re-plugging didn't change anything, Flashmode didn't start a second time. Taking out the battery made it go off and it stayed like that until plugging it in the next time.
Click to expand...
Click to collapse
as no botton is working..no flashmod..fastboot mod..nothing means hard brick..have you made anythng with ta backup or something??
Btw do you have warranty?
trancyh but
bibhu059 said:
have you made anythng with ta backup or something??
Btw do you have warranty?
Click to expand...
Click to collapse
Dunno - what is TA Backup? Only place I saw that is in Flashtool to exclude TA I think.
I still have warranty, but I used the sony site to get an unlock-code.
So it's gonna at least cost me some €. Will call em tomorrow.
Used ones are from 80€ upwards, so I wonder how much Sony will charge...
brainzilla said:
Dunno - what is TA Backup? Only place I saw that is in Flashtool to exclude TA I think.
I still have warranty, but I used the sony site to get an unlock-code.
So it's gonna at least cost me some €. Will call em tomorrow.
Used ones are from 80€ upwards, so I wonder how much Sony will charge...
Click to expand...
Click to collapse
listen dont worry..before taking to sony service center again check for all options(fastboot,flashmod)..if nothing is hapening then
take it to service center and act as a noob..if they ask what happen just say updating phone software through pc companion..after updataion it is not getting on..only this much with a louder voice and dont let them you have unlocked the device..i have recently changed my board by applying this..so good luck
bibhu059 said:
if nothing is hapening then take it to service center and act as a noob..if they ask what happen just say updating phone software through pc companion.. so good luck
Click to expand...
Click to collapse
Hehe thanks. But the german site doesn't even list any phone-repair-centers.
But I will try to find out more tomorrow. The only work till 6
The thing is u played with pcc with unlocked bl... did u relocked it before doing something with pcc? here is the trouble i guess!
I don t know how xU is done but if nobody could repair it for u ,u should buy a battery and change it... Or at least unconnect yours for cuple of minutes then replug it and plug charger on...
because kernel don t start so battery not charging thats why every one should do flashing and everything could mess the phone with at least 60% of battery in case something like that happens... theres a thread somewhere in xda for recovery from brick, find it i must go to bed lollll
sent with my Nypon using tapatalk 2
Alx31TLse said:
I don t know how xU is done but if nobody could repair it for u ,u should buy a battery and change it... Or at least unconnect yours for cuple of minutes then replug it and plug charger on...
Click to expand...
Click to collapse
Ahhh! I see!
The digital limbo it was in caused the charger to stop working and sucked the battery dead.
So the red LED now just tells me the battery is at 0%.
Will try to recharge with my bench-supply.
But those batteries are a pain in the ass to interface...
Like i said im not sure but look flashing a kernel takes average one sec!
And only led and no screen on u know what i mean...if u could have just a bit of juice then its enough to fastboot. U must unplug battery cuz u will never be able to start it if not...
And soon as u could flash kernel then u touch nothing plug in charger for cuple hours and u should be good to flash a ftf and run on it for a day
And please guys...u have u bl? FORGOT PCC lolll unless u relock it...i didn t start pcc since almost a year
sent with my Nypon using tapatalk 2
OK guys thanks for all the technical and moral support so far!
I figured a way to load my battery with a bench-supply.
The procedure involved springs from a pen, small screws from an old HDD, micro-clamps, multimeter-cables/probes, silver tape and a toolmaker's vice....
By the way: The BA600 Battery is protected by a small circuit - so you need more than the nominal 4.2V to charge it.
I set it to the 5.1V a regular USB-charger outputs and it did the trick in about 2hrs.
Anyhow I was then able to use the latest OSX version of Flashtool in Fastboot mode and flash a kernel.
Then I used the Flashmode and flashed the s*** out of it.
That said: It works again! :good: :good: :good:
So at least I have gingerbread back and will give Cyan 10.0 a try.
THANKS TO ALL OF YOU GUYS!
Seriously! Wicked good support here!
Happy for u.
Im sure next time u ll b careful
sent with my Nypon using tapatalk 2
Alx31TLse said:
Im sure next time u ll b careful
Click to expand...
Click to collapse
More like "Next time I know what I do because I learned it the hard way..."
The whole documentation and "support" for the procedures is quite complicated in my opinion.
I mean how complicated is it to code a HELP-button into Flashtool?
Anyways - thanks again!
Related
NEW - March 2011
A method of booting custom kernels (using kexec) has been developed. Thanks Bin4ry, zdzihu, MrHassell, blagus, and all other devs who are working hard to make this stable.
The bootloader protection has been bypassed!
zdzihu said:
Bootloader is broken/bypassed!
Big bad huge font to avoid confusion =)
@Goroh_kun:
Buddy, I know you're still reading this forums so... I just want you to know that you are absolutely BRILLIANT. You're a STAR.
BIG thanks for all your contributions into this project! Nothing, and I mean NOTHING would happen without you.
@devs:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@SE: lads, it's your turn now - please unlock it already. I promise we won't brick our phones
@all: DON'T ask for details. I will post here when I'm ready to do so. Today (I guess?) is the Arc release date and stuff, I don't want to mess around...
Still busy working abroad,
Cheers,
z
Click to expand...
Click to collapse
Link to 2.1 alpha kernel (2.6.29)
http://forum.xda-developers.com/showpost.php?p=12578251&postcount=848
OLD
Important info!
http://forum.xda-developers.com/showpost.php?p=12298790&postcount=811
Link to FlashTool
http://forum.xda-developers.com/showthread.php?t=920746
Here are some posts:
MrHassell said:
Yes and yes - while rebooting and as zdzihu previously reported kexec is viable.
http://forum.xda-developers.com/showpost.php?p=8714275&postcount=407
zdzihu
override partition table using kernel command line. Tried (via kexec) and it worked.
Code:
mtdparts=msm_nand:[email protected](appslog),[email protected](cache),[email protected](system),[email protected](userdata),[email protected](loader)
Bin4ry - tawrite - http://forum.xda-developers.com/showpost.php?p=8931422&postcount=442
cat /proc/mtd
mtd0 cache
mtd1 appslog
mtd2 userdata
mtd3 system
My final post on the subject. Have better things to do now the media have landed au reviour.
Click to expand...
Click to collapse
Bin4ry's kexec kit posts
http://forum.xda-developers.com/showpost.php?p=12240639&postcount=708 - V1
http://forum.xda-developers.com/showpost.php?p=12245719&postcount=711 - V2
http://forum.xda-developers.com/showpost.php?p=12260334&postcount=724 - V3
MrHassell's V3 test log
http://forum.xda-developers.com/showpost.php?p=12261764&postcount=729
21st March 2011, onwards
Bin4ry said:
Can you try to run it on chargemon script instead of xRec?
So that we can run it at the very beginning of boot process. Maybe this is a solution!
This should work in the chargemon script:
exec /data/local/tmp/run.sh
WARNING!
JUST TRY THIS IF YOU KNOW WHAT YOU ARE DOING !
Regards
Click to expand...
Click to collapse
Androxyde said:
chargemon the safer way :
Just before recovery if then else :
if [ -e /data/local/tmp/kexec ]
then
rm -r /data/local/tmp/kexec
exec /data/local/tmp/run.sh
fi
so from the OS, touch /data/local/tmp/kexec the reboot and it will boot the kexec script and remove the kexec file so that the next boot or reboot will go fine
Click to expand...
Click to collapse
Bin4ry said:
So, 2 users with bb58 had booted fine then WLOD.
Seems the initial idea is working
Now fix the problems and all is good ?
Regards
Click to expand...
Click to collapse
DooMLoRD's test
http://forum.xda-developers.com/showpost.php?p=12266289&postcount=750
Bin4ry's edited chargemon file
http://forum.xda-developers.com/showpost.php?p=12266422&postcount=753
Comment from DooMLoRD - actually about the above file.
DooMLoRD said:
just an additional comment...
the following chargemon will work only for recovery flashed through Flashtool v0.2.8 for stock roms only
also please do not try that chargemon on CM7RC2 roms (u wont be able to get into the OS cause recovery on CM7RC2 is shifted to /system/recovery/
also the line chroot / /init will work for 2.3 roms but is not compatible with 2.2 roms... for 2.2 roms u need /system/bin/chroot / /init
Click to expand...
Click to collapse
x10b's test
x10b said:
boot.img installed >> boots normal got my radio, wifi , everything works fine...
FW : 2.1.1.A.0.16
BB : 2.1.58
test ok......
Click to expand...
Click to collapse
x10b's test video
http://forum.xda-developers.com/showpost.php?p=12287032&postcount=798
DooMLoRD's edited (universal) chargemon file
http://forum.xda-developers.com/showpost.php?p=12267053&postcount=762
Important for 'non-devs' - also look at DooMLoRD's post ahead
wolfilein said:
@all
you shouldn't flash the file with xrecovery!
you should extract it to
/data/local/tmp/
on you phone
and replace the /system/bin/chargemon with the one bin4ry has posted some posts ago
after that make it executable
with
chmod 755 /system/bin/chargemon
then create the file /data/local/tmp/kexec
with
touch /data/local/tmp/kexec
and then reboot you phone should load the new kernel
Click to expand...
Click to collapse
DooMLoRD's post in reply to above:
http://forum.xda-developers.com/showpost.php?p=12267467&postcount=766
jerpelea said:
cm7 boots with custom kernel
Click to expand...
Click to collapse
More testing:
DooMLoRD said:
test with Stock SE ROM FW: 2.1.A.0.435 | BB: 2.1.54
booted into OS but no radio, strange question mark symbol on top of battery symbol (in notification bar)... phone rebooted in few seconds couldnt get into "About Phone"... though no LED notifications of any sort... even have made a video of boot up process [it look good on handset ] will post it here in a while
EDIT:
on second attempt tried to get to "About Phone" asap... under "Kernel Version" it was "unknown"... and then the system immediately rebooted...
keep up the great work Bin4ry and all other devs...
Click to expand...
Click to collapse
DooMLoRD's bootup video
http://forum.xda-developers.com/showpost.php?p=12269301&postcount=775
Androxyde said:
I am on stock firmware A.0.16
I modded my chargemon to implement booting cust kernels from it and a gscript script shortcut on the desktop to reboot.
I tried these :
Reboot custom kernel with stock BB .58 : booted / no radio / reboot in less than 1 minute
Reboot custom kernel with BB 55 : same as with .58
Reboot custom kernel with BB 52 : booted / no radio / no reboot
Reboot stock rom with BB 52 : no radio
So with my last try I cannot conclude anything about the "no radio"
Will keep you informed with my further tests
Click to expand...
Click to collapse
More tests from DooMLoRD
http://forum.xda-developers.com/showpost.php?p=12272634&postcount=784
http://forum.xda-developers.com/showpost.php?p=12282471&postcount=789
http://forum.xda-developers.com/showpost.php?p=12303304&postcount=812
Bin4ry's kernel patches, config and build script from zdzihu:
http://forum.xda-developers.com/showpost.php?p=12272201&postcount=781
Bin4ry's kernel based on SE .435 kernel sources
http://forum.xda-developers.com/showpost.php?p=12275044&postcount=786
Aeny's tests
Aeny said:
x10i | J's CM7 RC2 V10a | BaseBand 2.0.46 | boot.img: 22.03.11-00_25
-Same behavior as BB 2.0.52
-(Stock kernel + this BaseBand = WLOD reboot loop.)
x10i | J's CM7 RC2 V10a | BaseBand 2.0.49 | boot.img: 22.03.11-00_25
-Same behavior as BaseBand 2.0.52
x10i | J's CM7 RC2 V10a | BaseBand 2.0.52 | boot.img: 22.03.11-00_25
-Screen not waking up by pressing any buttons, to wake up press any button, then press the screen. If "Screen-on" and/or "Screen-off" animations are enabled in CM-Settings then screen cannot be woken up at all.
-Battery shows a percentage, but does not indicate charging, however the battery level is going up.
-Time seems to update once every few (10~11) minutes instead of every minute & always starts counting from 1/1/1970 -1h:00m at boot.
-WiFi shows "error" under settings but does magically work, just can't be turned off.
-Bluetooth doesn't want to turn on.
-Baseband: "Unknown".
-Kernel Version: 2.6.29Bin4ry "[email protected] #1".
-no reboots (running 15minutes).
-screen doesn't auto-turn off but dims instead.
-Battery status shows as "unknown" under settings -> about phone -> status.
-No USB.
-LED doesn't light up while charging.
x10i | J's CM7 RC2 V10a | BaseBand 2.1.54 | boot.img: 22.03.11-00_25
-Freezes after 2~5seconds(can't see if WLOD because LED doesn't work).
-(Stock kernel + this BaseBand = WLOD reboot loop.)
x10a | J's CM7 RC2 V10a | BB 2.1.54 | boot.img: 22.03.11-00_25
-Freezes after 2~5seconds->reboot(can't see if WLOD because LED doesn't work).
-(Stock kernel + this BaseBand = WLOD reboot loop.)
Click to expand...
Click to collapse
Aeny said:
x10i | Build: 2.1.A.435 | BaseBand: 2.1.54 | boot.img: 22.03.11-00_25
-Booted into OS: YES
-Radio: NO
-Reboot in few seconds: YES
-Questionmark on battery: YES
-BaseBand: Unknown
-kernel: 2.6.29Bin4ry [email protected] #1
x10i | Build: 2.1.A.435 | BaseBand: 2.1.58 | boot.img: 22.03.11-00_25
-Booted into OS: YES
-Radio: NO
-Reboot in few seconds: YES
-Questionmark on battery: YES
-BaseBand: Unknown
-kernel: 2.6.29Bin4ry [email protected] #1
x10i | Build: 2.1.A.435 | BaseBand: 2.1.54(a) | boot.img: 22.03.11-00_25
-Booted into OS: YES
-Radio: NO
-Reboot in few seconds: YES
-Questionmark on battery: YES
-BaseBand: Unknown
-kernel: 2.6.29Bin4ry [email protected] #1
x10i | Build: 2.1.A.435 | BaseBand: 2.1.55(a) | boot.img: 22.03.11-00_25
-Booted into OS: YES
-Radio: NO
-Reboot in few seconds: YES
-Questionmark on battery: YES
-BaseBand: Unknown
-kernel: 2.6.29Bin4ry [email protected] #1
Back to CM7 for me, SE's rom felt like playing a game @ 2FPS.
~Aeny
Click to expand...
Click to collapse
Ahmed radi's tests
Ahmed radi said:
boot.img: 22.03.11-00_25 / FW: SE 2.1 / BB 2.1.54
its work great !
boot normaly then radio work and WiFi also work !
boot.img: 22.03.11-00_25 / FW: SE 2.1 / BB 2.0.52
freeze on SE logo fo about 5~9 sec | no radio (insert SIM) | Wifi work
@ Bin4ry
good look bro
Click to expand...
Click to collapse
Ahmed radi said:
@ DooMLoRD
good now we have conferm that bin4ry kernel work with .54
i try also 52 but there is no radio !
i reflash the phone with 54 BB but also get no signal !
any idea about this ?
@bin4ry
could we convert the .img to .sin ?
Click to expand...
Click to collapse
Bin4ry said:
No, sin is the signature header. For that we need the signing key and we don't have it!
Regards
Click to expand...
Click to collapse
Ahmed radi said:
good lack Bin4ry !
test report :
X10 2.1 .435
BB54
run gr8 ,with Xda then reboot in se rom with radia and i test wifi and its work also!
edit :
BB58 also just like above !
>after we have sacsesfully loud Bin4ry kernel , could we have muiltitouch(not just dual) ? thanx
Click to expand...
Click to collapse
More info from Bin4ry
http://forum.xda-developers.com/showpost.php?p=12285626&postcount=795
shyvue's test
shvyue said:
I'm new to this but what i did is, copy all files from bootkit to /data/local/tmp
adb shell
$ su
# chmod 06755 run.sh
# ./run.shls
Phone shows fast-usb reboot, then a cute dog at top-left, then xda-developer with brown background.
SE stock image:
2.1.A.435
x10i-2.1.58 white led after xda-developer image then reboot with SE logo, etc
x10i-2.1.54 white led after xda-developer image then reboot with SE logo, etc
Click to expand...
Click to collapse
mpasanthosh's test
http://forum.xda-developers.com/showpost.php?p=12311351&postcount=816
Starting from 14th January 2011
blagus said:
Hi to all developers!
I haven't read whole thread, but I'm sure bootloader hasn't been cracked yet.
I spoke to a source who know really a lot about SE phones. He has been investigating X10 a lot and I got some info from him. He might be able to give me some further info but only if you are willing to read and try to accept my post and not just tell me "Xperia is different SE phone".
Believe me, he knows a lot about how X10 boots/works, and what's happening inside it (software part). He's been investigating phones since DB2020, and knows something about phones even before that.
As first, when I told him about "bootloader" he wasn't 100% sure what is that.
Most correct structure of X10 boot process and all "parts" involved is:
first, "real" ROM, which is actually one time programmable and can't be ever reprogrammed, is started.
In EROM, there's signature which is checked by ROM at beginning of boot - if signature is OK, ROM proceeds with running EROM and leaves it to continue boot process.
That is: checking signatures of everything that it runs directly, and then launches it if signatures are OK.
He also said that ROM is very incorrect name for phone's firmware - because ROM is actually thing that I mentioned above. Of course, you don't have to rename all ROMs to FW now, however it would be good if at least here in development thread correct names are used because that would help you, me in understanding what you're talking about - because I have knowledge from A1/A2 series and now he proved me that I was right about what I was saying - and him in understanding and possibly some further small tips.
He said that the thing that launches actual firmware - Android, is S1Boot, and it actually is in some structural way connected with A1's EROM and A2's SEMCBOOT.
(That is the thing I've been trying to say some time ago however no one was listening to me, nor wanted to check it - everyone was just saying "No, this phone is different from other SE phones.)
That then means that getting developer (more understandable - "brown") loader.sin - which actually contains S1Boot, or as you probably call it, bootloader - won't help you because in that S1Boot, there are flags that define if brown image will be accepted or not.
Also, in ROM there is root certificate (Qualcomm), "first in the chain" he said, not Red - retail, or Brown - developer one. S1Boot is also signed with that root certificate, and even existing S1Boot in our Xperias contain both Red and Brown certificates (unlike on A1/A2, where there is either red which accepts just red flashes, or brown which accepts them all), and only thing that differs is flags which tells EROM/S1Boot should it accept brown flash or not.
Note: Do not mix root certificate that is S1Boot signed with, and Red/Brown located inside it!
You can easily check this by opening existing, "usual" available for download here loader.sin in Notepad and you'll first find few certificates - S1_loader_root, S1_EROM_root, etc. and after that S1_loader_test, S1_EROM_test, etc. - same names, but instead of root it says test - this proves that there are both red and brown certificates.
He also said that
"brown sin-s can be self-produced... usually the brown RSA keys are available".
That means that if we put brown RSA key before header of pre-patched loader.img, we would get brown signed loader.sin, and we would just have to find a way to change flag to make the phone accept that brown image.
About pre-patching: yes, S1Boot has to be patched in order to accept unsigned flashes - whether it's just changing those flags, or rewriting it - however in that case still original root certificate must stay inside because it's checked by ROM.
And last thing is that he said that "SE used to disable Jtag on retail phones".
I remember that someone here mentioned Jtag but I don't know what was the result.
To receive further help/tips from him, following questions must be answered:
Question 1: To what exactly do you refer when speaking about bootloader? Now when I explained about S1Boot, can we actually say that bootloader = S1Boot (similar to) > A1's EROM (similar to) > A2's SEMCBOOT?
Question 2: What's contained in boot.img, if S1Boot is inside loader.img/loader.sin?
Best regards
Click to expand...
Click to collapse
25th January 2011
Bin4ry said:
Anyone wants to try my modded kexec-tool? I hope i have found a solution, but don't know yet, because my netbook still compiles the kernel ..... (for another 20 hours )
Regards
Bin4ry
Click to expand...
Click to collapse
Bin4ry said:
Since Maxrfon didn't answered my last mail again (he's very busy now) i had spare time and worked on this little tool once more =)
I hope we can boot another kernel with kexec-tool now.
for that we need a zImage and a initrd + some bootparameters for the kernel (root partition)
So if anyone want to try i would be lucky. My compilation was broken and now i have to start again :'(
So i anyone here wants help to try i would be lucky =)
Regards
Click to expand...
Click to collapse
26th January 2011
Bin4ry said:
Yes a initrd is needed, because i have not found the initrd location in virtual memory now, so i cannot point to it from kexec
Code:
kexec -l /zImage --apend="root........" --file="/initrd"
kexec -e -f
also you should appen the root partition.
It would be nice if someone could upload a zImage, i'm still stuck in compiling it *LoL* ****ing netbook is compiling 15 hours and then it aborts with some errors ^^
Regards
Click to expand...
Click to collapse
blagus said:
Put kexec in /system, chmod 777
Put ramdisk_orig.tgz and zImage to / and chmod 777
Code:
# kexec-tool -l /zImage --append="/" --initrd="/ramdisk_orig.tgz"
# kexec-tool -fe
After reboot zImage and initrd dissapear from /
Maybe if I put them in /system... I'll try that and let you know result.
Click to expand...
Click to collapse
Bin4ry said:
@Shamux thanks for the kernel.
@blagus:
You have to append the root partition to kernel parameters, else it will not detect it!
It's just like you want to boot a normal kernel on pc
Try adding --append="root=/dev/blablabla rw"
check which one is root partition (don't know now) and then check again if it works.
What we really neew is some kmsg log or smth.
Also Z mentioned to compile the kernel with semc-es209ra-capk config.
A minimal config will be a better way to start because something is breaking up we cannot find it.
But if we can boot minimal kernel, we can try to add more and more step by step and find the problem =)
Regards
Click to expand...
Click to collapse
blagus said:
Hmm... then, a little bit of experimenting is required...
I've got new info regarding bootloader cracking, from my source again
In theory it's very simple and you probably know that already: we calculate prime numbers that public key is made from - one key is enough, second can be calculated with
key ÷ 1st prime formula. But, you already know that.
Now, how to get these keys? Probably you know that too but let me repeat:
with OpenSSL we can get certificates from loader.sin. For example, this is interesting part of S1_loader_root (root certificate):
Code:
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public Key: (1024 bit)
Modulus (1024 bit):
00:ea:a5:f7:7d:bd:67:21:33:04:00:ea:91:b0:c6:
cd:38:6c:aa:da:60:c1:77:e2:24:67:be:b7:da:4f:
e6:e5:92:fd:5b:b4:1a:97:54:cb:2f:7d:b1:63:e3:
d4:43:b9:a6:91:70:36:9f:5f:3a:7a:0e:2c:a7:44:
3b:40:84:0f:40:79:4a:b7:e8:58:d7:47:15:29:79:
07:b7:65:7b:d3:6d:40:10:29:78:c5:8f:51:b0:6e:
38:a9:97:1c:ff:1e:e5:bc:0d:22:1c:08:22:db:ad:
40:6f:2f:28:8a:8f:5c:38:d3:2a:96:72:48:66:28:
07:80:11:f1:62:f9:d3:40:a7
Exponent: 65537 (0x10001)
Modulus here is public key.
Just give this modulus to the CPUs and GPUs and let them calculate primes.
With these primes, calculation of private key should be trivial.
Update: this key is what we need to crack, that's it. Then, we can even make our own certificate - just like now there are, for example, s1_loader (Red, retail) and s1_loader_test (Brown, developer), we can make our own s1_loader_xda... and then, if it's issuer is S1_Loader_Root_f851 (like it is in root certificate attached here), and it is present in all parts of loader.sin (signature, signature of loader payload data) then phone will accept it.
Yes, that's right: this "Modulus" number above is the one that we need to crack in order to modify bootloader.
Update: if there's something confusing in this certificate, it's probably the fact that it's issuer and subject are same: yes, it's self-signed. But unfortunately, it won't work if we make our self-signed certificate
Click to expand...
Click to collapse
arkedk said:
Don't know if this is any help or useful info for any of the devs.
But managed to check the code in the lib_s1_verification.so file
Here's the boot sequence.
These files is what I know has something to do with the s1:
/lib/lib_s1_verification.so
/bin/linker
/bin/s1_verification_test
I don't know what I'm looking at here, but just wanted to see if I could make some kind of contribution to get the bootloader opened up.
Also attached the dedexed files from within semc_bootinfoif.jar if those are useful to anyone.
Assuming this is the Booting Sequence:
Click to expand...
Click to collapse
I tried typing in 'adb root enable' and this appeared (see attachment).
If we can get a developer rom somehow, we could enable root.
If unclear, it says that 'adbd cannot run as root in production builds'.
I think that Sony Ericsson's adb drivers are causing this. If we could hack into the official android one, we could maybe unlock some adb commands (adb shell doesn't even allow any command to work!)
Very good idea to start a new thread. Please someone of the moderators delete all future comments that are not related to root!
I finally compiled the tardis program but it doesn't work
Here my original post :
-----
This didn't work on X10. But possibly someone will try it on other devices.
Usage: ./tardis <BIG FILE>
Big file should be ~ 100mb
------
-Bin4ry
Gathered Information about the kernel and mount points so far:
Kernel Version: Linux version 2.6.29-rel ([email protected]) (gcc version 4.2.1) #2 PREEMPT Wed Mar 10 16:53:36 JST 2010
(notice it's been compiled on march 10 so it might have been patched until february)
Internal flash partitions:
/dev/block/mtdblock2 /system yaffs2 ro 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock1 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/loop0 /cdrom iso9660 ro 0 0
4Mb ramdisk: tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
Inside the software update package, there are a lot of files:
update.xml -> update template, it says not to erase amss_fs.sin, maybe that's why it's empty...
preset.ta ->
Inside there's this:
Code:
// preset.ta has same format as TA file generated by FXTool
// Specification document: 69/159 35-LXE 108 116 Uen, Rev PA3
// Format:
// [TAPartition<HEX8>]{1}
// [UnitID<HEX32> UnitSize<HEX16> Data<HEX8>{UnitSize}]{n}
// (c) Sony Ericsson Mobile Communications AB, 2009
02
000008FD 0010 00 00 08 00 05 00 00 00 0E 00 00 00 08 00 00 00
00000961 0004 FE FF FF FF
amss_fs.sin -> no idea...but it seems empty as the cache 639 byte
apps_log.sin -> template for wiping mtdblock0 partition? (639 byte)
cache.sin -> template for wiping cache partition (like data partition, 639 byte)
fota0.sin -> ?
fota1.sin -> ?
boot.sin -> our beloved boot.img? (5.4 mbytes)
recovery.sin -> it looks like we have a recovery mode after all (not just safe mode)
dsp1.sin -> dsp firmware?
amss.sin -> Radio firmware?
metadata.dat -> 536 bytes, I guess it will be package metadata
simlock.ta -> 1,3 kb
system_S1-SW-LIVE....sin -> 195Mb, system partition
userdata_S1-SW-LIVE....sin -> 4,8kb, template for wiping data partition, maybe it has some file in there... haven't checked yet.
Things I tried so far:
m7 exploit. It seems fixed on this kernel (that or it might need some tinkering to the code)
exit_notify() local root exploit. suid_dumpable is 0 on /proc, so useless
h00ly**** exploit. Bin4ry tried this, but it seems it didn't work either.
Good thing: Sony Ericsson update service is programmed in java, and lollylost100 has already managed to make the program dump update images decrypted, so we might have a chance with that.
Also, bootloader starts if you take out the battery, plug usb and then turn it back in. It goes on for 10 seconds, after that, it times out and reboots to normal. So maybe if we don't mess with the bootloader we can restore it no matter what happens to the rest of the flash (don't trust this much)
About the mtd partitions, there are only four visible to Android, but there have to be more.
Radio partition, recovery partition (if it flashes it will be somewhere, unless its just a kernel+ramdisk that boots when in 'safe mode'), bootloader and such. Where are they hidden?
I have a copy of the running configuration for the kernel from .16 version, if anybody wants, I can put it somewhere.
If you wan't to retrieve it from your phone just do:
cat /proc/config.gz > /sdcard/config.gz
from adb/local terminal.
@HunteronX: that error it gives you is because you need a dev firmware, or being able to do a 'su', to get root access, it's not a driver problem. If you do "adb shell" you get a terminal with user id 2000 (shell), but no way of getting id 0 (root) with official firmware (unless hacking).By the way, that post you pasted from me is very outdated and there's not much useful information so you can remove it from the first post Thanks for starting a new thread, hopefully we'll manage to keep it clean!
Regards, Biktor
biktor_gj said:
update.xml -> update template, it says not to erase amss_fs.sin, maybe that's why it's empty...
Click to expand...
Click to collapse
Code:
<?xml version="1.0" encoding="utf-8" ?>
<UPDATE>
<NOERASE>amss_fs.sin</NOERASE>
</UPDATE>
HunteronX said:
I tried typing in 'adb root enable' and this appeared (see attachment).
If we can get a developer rom somehow, we could enable root.
If unclear, it says that 'adbd cannot run as root in production builds'.
I think that Sony Ericsson's adb drivers are causing this. If we could hack into the official android one, we could maybe unlock some adb commands (adb shell doesn't even allow any command to work!)
Click to expand...
Click to collapse
This information is Wrong.
ADB is not allowed to run as root on Any production builds, not only Sony Ericsson.
Also all "normal" ADB commands work.
My Contribution: The only Directory where you can put native executables is /data
sim-value said:
This information is Wrong.
ADB is not allowed to run as root on Any production builds, not only Sony Ericsson.
Also all "normal" ADB commands work.
My Contribution: The only Directory where you can put native executables is /data
Click to expand...
Click to collapse
confirmed, all production build android we couldn't enable root. that is too easy.
we do can write and excute in /data. It use to be an exploit moving data form
/data to /system but now that hole is close, thoe move request get kill on the way.
Still no sign of recovery or bootloader access. ADB reboot won't help as you will get the normal bootup screen.
SEUS flash mode can be turn on and detect USB SEMC Flash Device in Linux and Mac OS, but after 20 - 30 second
it will shut it self and reboot in normal mode. there might be some trigger here.
funfobia said:
confirmed, all production build android we couldn't enable root. that is too easy.
we do can write and excute in /data. It use to be an exploit moving data form
/data to /system but now that hole is close, thoe move request get kill on the way.
Still no sign of recovery or bootloader access. ADB reboot won't help as you will get the normal bootup screen.
SEUS flash mode can be turn on and detect USB SEMC Flash Device in Linux and Mac OS, but after 20 - 30 second
it will shut it self and reboot in normal mode. there might be some trigger here.
Click to expand...
Click to collapse
Ok, thanks for telling me that - looks like i've got a lot to learn...
@biktor_gj I've hopefully now removed all the information you wanted.
/data is not the only place where you can run binaries, you can also execute them from /sqlite_stmt_journal ramdisk. The only issue is after rebooting the phone files will disappear, but /data has the nosuid flag enabled on the mount command, but that flag doesn't exist on the sqlite tmpfs.
Regards
I just sniffed yesterday the packets when SEUS is connecting to the Sonyerricsson Serve.
What I found out is that SEUS is requesting following IP: 195.95.193.10
If you enter this in your browser it returns following:
ma3.extranet.sonyericsson.com
There you can download a software called EMMA. Someone knows what's that for a software?
goroh_kun said:
I uploaded mtd dump program for xperia with my mtd_nand_ex module.
It includes souce code, and static linked binary.
http://hotfile.com/dl/52240500/a1a6e72/mtd_raw_dump.zip.html
With normal mtd-utils(nand-dump), you can't rip complete nand image.
so I have to change mtd mode to RAW MODE.
the raw image includes OOB(Out Of Band) area, so we have to
calculate ECC（Error Correction Code） to get its executable image.
Click to expand...
Click to collapse
I write program to rip original image from mtd raw image.
http://hotfile.com/dl/52522564/4d776ac/mtd_analyze.zip.html
I'm working to figure out how oob area works.
if you have any information please contact me, or write message here!
Try another method to run modified kernel.
hi, all
I found that the method modifying boot or recovery area is not good way,
because these partition are signed with SE signature, and it seems that
bootloader check its SHA hash and signature everytime on boot process.
so I try another approach that
execute another kernel, from original SE kernel like kexec method.
but original SE kernel is not configured with CONFIG_KEXEC.
so I have to modify kexec interfaces from system calls to proc filesystem
access.
http://hotfile.com/dl/52604229/240e97c/kexec_ex.zip.html
http://hotfile.com/dl/52609760/96288b5/kexec-tools.tgz.html
It seems work to boot new kernel. you have to build kernel with initrd image.
wait for details..
we have 2 options
patch loader or go kexec
flash tools for x10 nand
happy play
http://hotfile.com/dl/53734913/3b68720/flash_tools.tar.bz2.html
rosco16 said:
Great!!!
If you had flashed NAND ...is it correct to say that x10 is root 100% already ??
cheers
Click to expand...
Click to collapse
NO
- we can dump and flash nand (tested tools)
- SE boot (kernel is signed like .sin files) and our boot is not signed so it will not boot
WE need kexec to load our kernel or patch bootloader not to check for signed kernel
@custom rom Cyanogen V6 alpha is compiled but we can not boot it
zephyrix said:
Dump the bootloader, patch it, then rewrite.
Click to expand...
Click to collapse
)
you are so funny
if it was that simple we would do it
zephyrix said:
Dump the bootloader, patch it, then rewrite.
Click to expand...
Click to collapse
First, bootloader and fota applications have some kind of lock and cannot be read (unlike boot, recovery amss & dsp). Second, to patch a bootloader you need to disassemble it, find all the points where it checks for signatures, and patch them. Then you need to test it, and if you mess it once, 400$ phone to the trash. Much more useful to have kexec working, since with it you could, in theory, boot the bootloader from ram, to check if patching goes good and do all the testing withour breaking anything. And you could run a kernel of choice.
Things aren't as easy as that I'm affraid...
How to dump bootloader
Hi, all
try this to dump your bootloader.
http://hotfile.com/dl/53890681/9e4b303/spldump.zip.html
the SPL image remains in internal RAM address 0x0 - 0x100000.
I wrote a driver to dump this area through /proc/splimage.
goroh_kun said:
Hi, all
try this to dump your bootloader.
http://hotfile.com/dl/53890681/9e4b303/spldump.zip.html
the SPL image remains in internal RAM address 0x0 - 0x100000.
I wrote a driver to dump this area through /proc/splimage.
Click to expand...
Click to collapse
I love you goroh, thank you very very much
On a side note, is it just me or it is full of checks everywhere?
biktor_gj said:
I love you goroh, thank you very very much
On a side note, is it just me or it is full of checks everywhere?
Click to expand...
Click to collapse
yep is full
thanks goroh
but dump seems to be wrong
after 0x3000 is padding
next block is at 0x100000
@kexec we need to somehow patch it to load the loader
okay so first of all this is the fifth X10 ive either owned or repaired for someone. i know its almost impossible to brick the device.
the problem is, every other time i plugged it into SEUS it would check the software, tell me its up to date, then give me the option to install or exit.
this time, its telling me its up to date, but only giving me the option to exit.
i tried reflashing another x10 to make sure the install option was still there, and it was.
then back to this one, and again only "Exit".
Flashtool just gives me an error
please note: i dont know what went wrong with this device. it belongs to a friend of a friend whos x10 i fixed previously with SEUS then flashed with flashtool. all i know is that it wont turn on. there are no signs of being dropped, water damage, anything weird. looks brand new
when i plug it in, regardless of battery level(i have a few here to choose from), the LED will always light up green for 60 seconds or so, then go out. when i try to turn it on, it vibrates as usual, then nothing happens until i pop the battery out again.
when she handed me the phone in the first place i obviously went for the power button, and it DID blink red, im unsure if it was 1-3-5-xx times as i had just blown smoke into my own eyes on accident lol. i left it on a charger for a good hour before doing anything else, and no dice.
any help would be greatly appreciated
cmross13 said:
okay so first of all this is the fifth X10 ive either owned or repaired for someone. i know its almost impossible to brick the device.
the problem is, every other time i plugged it into SEUS it would check the software, tell me its up to date, then give me the option to install or exit.
this time, its telling me its up to date, but only giving me the option to exit.
i tried reflashing another x10 to make sure the install option was still there, and it was.
then back to this one, and again only "Exit".
Flashtool just gives me an error
please note: i dont know what went wrong with this device. it belongs to a friend of a friend whos x10 i fixed previously with SEUS then flashed with flashtool. all i know is that it wont turn on. there are no signs of being dropped, water damage, anything weird. looks brand new
when i plug it in, regardless of battery level(i have a few here to choose from), the LED will always light up green for 60 seconds or so, then go out. when i try to turn it on, it vibrates as usual, then nothing happens until i pop the battery out again.
when she handed me the phone in the first place i obviously went for the power button, and it DID blink red, im unsure if it was 1-3-5-xx times as i had just blown smoke into my own eyes on accident lol. i left it on a charger for a good hour before doing anything else, and no dice.
any help would be greatly appreciated
Click to expand...
Click to collapse
Sounds like a battery problem. I read about a guy who put his battery in the freezer after his started having that same blink. So i guess leave it in there for an hour then charge it . Then try again
Sent from my x10 on gingerbread
so your battery is over 50%?
Lion3494 said:
Sounds like a battery problem. I read about a guy who put his battery in the freezer after his started having that same blink. So i guess leave it in there for an hour then charge it . Then try again
Sent from my x10 on gingerbread
Click to expand...
Click to collapse
Freezer? R u kidding me? Battery life span gets shortened when cold so how would a freezer sort it out?
Sent from my X10i using XDA Premium App
Sorry double post
Sent from my X10i using XDA Premium App
cmross13 said:
okay so first of all this is the fifth X10 ive either owned or repaired for someone. i know its almost impossible to brick the device.
the problem is, every other time i plugged it into SEUS it would check the software, tell me its up to date, then give me the option to install or exit.
this time, its telling me its up to date, but only giving me the option to exit.
i tried reflashing another x10 to make sure the install option was still there, and it was.
then back to this one, and again only "Exit".
Flashtool just gives me an error
please note: i dont know what went wrong with this device. it belongs to a friend of a friend whos x10 i fixed previously with SEUS then flashed with flashtool. all i know is that it wont turn on. there are no signs of being dropped, water damage, anything weird. looks brand new
when i plug it in, regardless of battery level(i have a few here to choose from), the LED will always light up green for 60 seconds or so, then go out. when i try to turn it on, it vibrates as usual, then nothing happens until i pop the battery out again.
when she handed me the phone in the first place i obviously went for the power button, and it DID blink red, im unsure if it was 1-3-5-xx times as i had just blown smoke into my own eyes on accident lol. i left it on a charger for a good hour before doing anything else, and no dice.
any help would be greatly appreciated
Click to expand...
Click to collapse
The red flashing LED was a battery fault. "badly charged"
The green led is that the phone is stuck in flash mode.
The fact that Seus and Flash tool does not fix it is odd.
Have you tried to flash it again?
I'm having the same exact problem right now. My X10 hasnt worked since last monday. Ordered new battery and should arrive today. I will let you know what my results are. Hopefully it fixes the problem.
OmegaRED^ said:
The red flashing LED was a battery fault. "badly charged"
The green led is that the phone is stuck in flash mode.
The fact that Seus and Flash tool does not fix it is odd.
Have you tried to flash it again?
Click to expand...
Click to collapse
well since i have two x10's here, plus my phone, and only two wall chargers, one had to stay on usb charge overnight(5-6 hours). i accidentally left the broken x10 on usb charge. when i woke up, it was flashing red led consistently. i unplugged, removed battery, reinserted, three red leds. gonna fool around swapping batteries and see what happens.
the SEUS thing is whats bothering me
edit: swapped dead phones battery in working x10 and plugged into wall, it was fully dead, despite being charged for hours on USB. was blinking red, then solid red, indicating that it was charging.
put fully charged(eh, 95%) battery in broken x10. tried to power on, got vibrate and one quick greed led. nothing else happened, no screen on, so Sony logo, nothing. SEUS failed again, Flashtool failed again
bad battery back in bad phone on wall charge, did not try to power on. blinks green a few times or so, then nothing happens.
try using a different computer or different USB port or reinstall the USB drivers
In my case SEUS also show that windows (with exit only). Previous i normally reflash firmware many times without problems.
you can try wotanserver flashing tool, it's free but you need to register http://www.wotanserver.com/en/sony-ericsson/se/xperia-x10/debranding-flash
it will generate log file while flashing, post it here if it will not work
nightspirit said:
you can try wotanserver flashing tool, it's free but you need to register http://www.wotanserver.com/en/sony-ericsson/se/xperia-x10/debranding-flash
it will generate log file while flashing, post it here if it will not work
Click to expand...
Click to collapse
as you will see, i tried it twice, with no luck
WotanClient 3.2.0 - www.WotanServer.com [3002000]
Microsoft Windows 7 Home Premium Edition Service Pack 1 (build 7601), 64-bit ENU (ENU)
[APPSTART] checking version for WotanClient.exe...
[APPSTART] Filename: WotanClient.exe
[APPSTART] Local hash: A0E30E60BB942D2A80AC1C324AC8069F2A98EB98
[APPSTART] Remote hash: a0e30e60bb942d2a80ac1c324ac8069f2a98eb98
[APPSTART] checking version for data/data3.zip...
[INET] saving http://storage.wotanserver.com/version/data3.zip as data3.zip
[INET] connecting server...
[INET] getting file info...
[INET] filesize: 460 KB
[INET] downloading...
[INET] done.
[APPSTART] ZIP: unpacking data...
Connect your phone pressing "C"...
phone found: DCU-60 @ PORT01
initializing...
IDENT: PROT_VER="01";DATE="20100119";TIME="17:24:00";VER="R8A013";UNIQUE_DEV_ID="B465230A21F33504282A5C2DFFDA4C295092BEC2";CXC="1226-2253";TYPE="S1_EROM";SEC_LOCK_STATUS="LOCKED";HASH_PUB_KEY="00000000000000000000000000000000";EROM_AID="0001";LOADER_AID="FFFF";SW_AID="FFFF";CUST_AID="FFFF";SIM_LOCK_AID="FFFF";IMEI="00000300000000";MSN="CB511LKDCJ";SIN_VER="0001";SIMLOCK_TAMP="";AID_TAMP="NOT_TAMPERED";LOADER_ROOT="S1_Loader_Root_f851";EROM_ROOT="S1_EROM_Root_b15e";SW_ROOT="S1_SW_Root_ac12";CUST_ROOT="S1_Cust_Root_5789";SIM_LOCK_ROOT="S1_SL_Root_f20d";HW_CONF_ROOT="S1_HWConf_Root_ee5d";
S1 QSD8250 platform detected
done.
X10a (1237-3761_R38A)
PLATFORM DB0101
IMEI: 00000300000000
MODEL: X10a
OTP: N/A CID 00
EROM: N/A CID 00
SIMLOCK: NO
CDA: 1237-3761_R38A N/A (N/A)
FIRMWARE: R2CA016
Importing settings...
Settings imported.
short name: [X10]
phone found
>> Downloading necessary files...
SELECTED PHONE: X10
SELECTED FW: 2.0.2.A.0.24
SELECTED CDA: Generic Trade US (2.1.1) (X10a)
>> RXBfbd888ad4208b88e5f2ba20fe8a73c29
>> downloading...
[INET] saving http://storage.wotanserver.com/RXBfbd888ad4208b88e5f2ba20fe8a73c29 as RXBfbd888ad4208b88e5f2ba20fe8a73c29
[INET] connecting server...
[INET] getting file info...
[INET] filesize: 32 MB
[INET] downloading...
[INET] done.
Filesize: 34040005
>> File ready and CRC is OK
>> RXCaee1e90a00ca8f9d45d19440da4a41d6
>> downloading...
[INET] saving http://storage.wotanserver.com/RXCaee1e90a00ca8f9d45d19440da4a41d6 as RXCaee1e90a00ca8f9d45d19440da4a41d6
[INET] connecting server...
[INET] getting file info...
[INET] filesize: 84 KB
[INET] downloading...
[INET] done.
Filesize: 86063
>> File ready and CRC is OK
>> RXDbc3fac0b6cc7dd5d9c1109bf3940f893
>> downloading...
[INET] saving http://storage.wotanserver.com/RXDbc3fac0b6cc7dd5d9c1109bf3940f893 as RXDbc3fac0b6cc7dd5d9c1109bf3940f893
[INET] connecting server...
[INET] getting file info...
[INET] filesize: 243 MB
[INET] downloading...
[INET] done.
Filesize: 255556425
>> File ready and CRC is OK
>> download completed.
>> Booting phone...
ERROR: file header write failed!
ERROR: file header write failed!
Connect your phone pressing "C"...
phone found: DCU-60 @ PORT01
initializing...
IDENT: PROT_VER="01";DATE="20100119";TIME="17:24:00";VER="R8A013";UNIQUE_DEV_ID="B465230A21F33504282A5C2DFFDA4C295092BEC2";CXC="1226-2253";TYPE="S1_EROM";SEC_LOCK_STATUS="LOCKED";HASH_PUB_KEY="00000000000000000000000000000000";EROM_AID="0001";LOADER_AID="FFFF";SW_AID="FFFF";CUST_AID="FFFF";SIM_LOCK_AID="FFFF";IMEI="00000300000000";MSN="CB511LKDCJ";SIN_VER="0001";SIMLOCK_TAMP="";AID_TAMP="NOT_TAMPERED";LOADER_ROOT="S1_Loader_Root_f851";EROM_ROOT="S1_EROM_Root_b15e";SW_ROOT="S1_SW_Root_ac12";CUST_ROOT="S1_Cust_Root_5789";SIM_LOCK_ROOT="S1_SL_Root_f20d";HW_CONF_ROOT="S1_HWConf_Root_ee5d";
done.
S1 QSD8250 platform detected
X10a (1237-3761_R38A)
PLATFORM DB0101
IMEI: 00000300000000
MODEL: X10a
OTP: N/A CID 00
EROM: N/A CID 00
SIMLOCK: NO
CDA: 1237-3761_R38A N/A (N/A)
FIRMWARE: R2CA016
Importing settings...
Settings imported.
short name: [X10]
phone found
>> Downloading necessary files...
SELECTED PHONE: X10
SELECTED FW: 2.0.2.A.0.24
SELECTED CDA: Generic Trade US (2.1.1) (X10a)
>> RXBfbd888ad4208b88e5f2ba20fe8a73c29
>> found cached, checking integrity...
Filesize: 34040005
>> File ready and CRC is OK
>> RXCaee1e90a00ca8f9d45d19440da4a41d6
>> found cached, checking integrity...
Filesize: 86063
>> File ready and CRC is OK
>> RXDbc3fac0b6cc7dd5d9c1109bf3940f893
>> found cached, checking integrity...
Filesize: 255556425
>> File ready and CRC is OK
>> download completed.
>> Booting phone...
ERROR: file header write failed!
ERROR: file header write failed!
can anybody translate?
Translation = SE faulty failures. This problem persists too often on this phone...
okay. can anybody help me fix or is it doomed?
motibbs96 said:
Translation = SE faulty failures. This problem persists too often on this phone...
Click to expand...
Click to collapse
It's a case of the NAND memory dying for some reason.
I'm not sure if it's the heat or just crappy chips on the board.
Been seeing posts like this more and more these days.
OmegaRED^ said:
It's a case of the NAND memory dying for some reason.
I'm not sure if it's the heat or just crappy chips on the board.
Been seeing posts like this more and more these days.
Click to expand...
Click to collapse
Yea, I mean I love SE. But they just didn't put enough effort in to this phone. It has sooo much more potential. ROM's definitely help bring it out. But all these little faults we keep seeing happen with the phone here at XDA just drives me crazy. I know some of you have X10's that run great and I'm real happy for you, but there is still too many of us that have too many issues. I paid $550 USD for mine a year ago cause I fell in love with the phone, I was hoping my investment would last AT LEAST 2 years. sigh.... Oh well. Sorry to go on a kind of little rant there..
header failed error is due to win7 plz try flashing on winxp it work same problem i have got and i try in winxp gudluck
Xperia X10 won't start
I try on XP but same error came, here is my log......guys has someone solved this problem??? Please help I try everything but nothing works...:
WotanClient 3.2.0 - [3002000]
Microsoft Windows XP Professional Service Pack 2 (build 2600) ENU (MKI)
[APPSTART] checking version for WotanClient.exe...
[APPSTART] Filename: D:\Wotan\WotanClient.exe
[APPSTART] Local hash: A0E30E60BB942D2A80AC1C324AC8069F2A98EB98
[APPSTART] Remote hash: a0e30e60bb942d2a80ac1c324ac8069f2a98eb98
[APPSTART] checking version for data/data3.zip...
[APPSTART] Filename: D:\Wotan\data\data3.zip
[APPSTART] Local hash: 05E27BBCB846FDB0A25932E3D21484E2476DD9A2
[APPSTART] Remote hash: 05e27bbcb846fdb0a25932e3d21484e2476dd9a2
Connect your phone pressing "C"...
phone found: DCU-60 @ PORT01
initializing...
done.
X10i (1233-7029_R12A)
PLATFORM DB0101
IMEI: 00000300000000
MODEL: X10i
OTP: N/A CID 00
EROM: N/A CID 00
IDENT: PROT_VER="01";DATE="20100119";TIME="17:24:00";VER="R8A013";UNIQUE_DEV_ID="9E0B0CE5B678062A95F1238465472D7B24778F8B";CXC="1226-2253";TYPE="S1_EROM";SEC_LOCK_STATUS="LOCKED";HASH_PUB_KEY="00000000000000000000000000000000";EROM_AID="0001";LOADER_AID="FFFF";SW_AID="FFFF";CUST_AID="FFFF";SIM_LOCK_AID="FFFF";IMEI="00000300000000";MSN="CB511H4PVL";SIN_VER="0001";SIMLOCK_TAMP="";AID_TAMP="NOT_TAMPERED";LOADER_ROOT="S1_Loader_Root_f851";EROM_ROOT="S1_EROM_Root_b15e";SW_ROOT="S1_SW_Root_ac12";CUST_ROOT="S1_Cust_Root_5789";SIM_LOCK_ROOT="S1_SL_Root_f20d";HW_CONF_ROOT="S1_HWConf_Root_ee5d";
S1 QSD8250 platform detected
SIMLOCK: NO
CDA: 1233-7029_R12A N/A (N/A)
FIRMWARE: R2BA024
Importing settings...
Settings imported.
short name: [X10]
phone found
>> Downloading necessary files...
SELECTED PHONE: X10
SELECTED FW: 3.0.1.G.0.75
SELECTED CDA: Generic Trade Global Market (2.3.3)
>> RXBbbdb6225ee7fd45659f2991da30986d9
>> found cached, checking integrity...
Filesize: 31420997
>> File ready and CRC is OK
>> RXCd5468f34428154ae0b0a5379165fcb29
>> found cached, checking integrity...
Filesize: 115849
>> File ready and CRC is OK
>> RXD350dbcb6c166946bd52bc309bc6745bc
>> found cached, checking integrity...
Filesize: 136289686
>> File ready and CRC is OK
>> download completed.
>> Booting phone...
ERROR: file header write failed!
ERROR: file header write failed!
Connect your phone pressing "C"...
phone found: DCU-60 @ PORT01
initializing...
IDENT: PROT_VER="01";DATE="20100119";TIME="17:24:00";VER="R8A013";UNIQUE_DEV_ID="9E0B0CE5B678062A95F1238465472D7B24778F8B";CXC="1226-2253";TYPE="S1_EROM";SEC_LOCK_STATUS="LOCKED";HASH_PUB_KEY="00000000000000000000000000000000";EROM_AID="0001";LOADER_AID="FFFF";SW_AID="FFFF";CUST_AID="FFFF";SIM_LOCK_AID="FFFF";IMEI="00000300000000";MSN="CB511H4PVL";SIN_VER="0001";SIMLOCK_TAMP="";AID_TAMP="NOT_TAMPERED";LOADER_ROOT="S1_Loader_Root_f851";EROM_ROOT="S1_EROM_Root_b15e";SW_ROOT="S1_SW_Root_ac12";CUST_ROOT="S1_Cust_Root_5789";SIM_LOCK_ROOT="S1_SL_Root_f20d";HW_CONF_ROOT="S1_HWConf_Root_ee5d";
done.
X10i (1233-7029_R12A)
PLATFORM DB0101
IMEI: 00000300000000
MODEL: X10i
OTP: N/A CID 00
EROM: N/A CID 00
S1 QSD8250 platform detected
SIMLOCK: NO
CDA: 1233-7029_R12A N/A (N/A)
FIRMWARE: R2BA024
Importing settings...
Settings imported.
short name: [X10]
phone found
>> Downloading necessary files...
SELECTED PHONE: X10
SELECTED FW: 2.1.A.0.435
SELECTED CDA: Generic Trade Global Market (2.1.1)
>> RXC4dce5acfa8fe873865bc321c4ef77368
>> downloading...
[INET] saving D:\Wotan\data\flashes\RXC4dce5acfa8fe873865bc321c4ef77368
[INET] connecting server...
[INET] getting file info...
[INET] filesize: 84 KB
[INET] downloading...
Filesize: 86063
[INET] done.
>> File ready and CRC is OK
>> RXB97b668777e3650ec81948f6e3af107d2
>> downloading...
[INET] saving D:\Wotan\data\flashes\RXB97b668777e3650ec81948f6e3af107d2
[INET] connecting server...
[INET] getting file info...
[INET] filesize: 32 MB
[INET] downloading...
[INET] done.
Filesize: 34131918
>> File ready and CRC is OK
>> RXD2b79c4a598c359b673eb8ea1f0cc8d12
>> downloading...
[INET] saving D:\Wotan\data\flashes\RXD2b79c4a598c359b673eb8ea1f0cc8d12
[INET] connecting server...
[INET] getting file info...
[INET] filesize: 249 MB
[INET] downloading...
[INET] done.
Filesize: 261428738
>> File ready and CRC is OK
>> download completed.
>> Booting phone...
ERROR: file header write failed!
ERROR: file header write failed!
Me too
OmegaRED^ said:
It's a case of the NAND memory dying for some reason.
I'm not sure if it's the heat or just crappy chips on the board.
Been seeing posts like this more and more these days.
Click to expand...
Click to collapse
i have the same symptoms on my phone.
i know this sounds bad. but is there a way to fix this? or i mean, if i bring the phone to a service center, would they be able to fix it?
have anyone tried and have their phones fixed with this kind of issue?
Hi from the newbie front... I searched on xda but did not find an answer to my problem: this x10 so far has defied all attempts to root it.
Specs:
x10i
GB 2.3.3 (ota)
Baseband 2.1.71
Kernel 2.6.29-00054-g5f01537
Build 3.0.1.G.0.75
(bought in Germany 11.11 with 1.6, ota to 2.3.3 in US 11.11)
What I tried so far:
Gingerbreak - spins for hours w/o results
X10root 1.0 - crashes after hitting “Root” button
z4root 1.3 - freezes
SuperOneClick - forgot why it didn't work
DooMLoRD_v1_ROOT – paths not recognized/found
flashtool 0.6.7 - stops at installing busybox. Gave up after waiting ca. 35 min. The Logfile:
20/000/2012 14:00:15 - INFO - <- This level is successfully initialized
20/000/2012 14:00:16 - INFO - Flashtool Version 0.6.7.0 built on 2012-01-15 22:00:21
20/000/2012 14:00:22 - INFO - Device disconnected
20/005/2012 14:05:40 - INFO - Device connected with USB debugging off
20/005/2012 14:05:40 - INFO - For 2011 devices line, be sure you are not in MTP mode
20/005/2012 14:05:41 - INFO - Device connected with USB debugging on
20/005/2012 14:05:47 - INFO - Connected device : X10
20/005/2012 14:05:47 - INFO - Installed version of busybox : N/A
20/005/2012 14:05:47 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537
20/006/2012 14:06:44 - INFO - Pushing C:\Flashtool\.\devices\X10\busybox\1.19.0\busybox to /data/local/tmp/busybox
All PC-based attempts (vs. apk's) I tried on an Intel-iMac with Parallels and also on a Windows PC, except flashtool.
With very limited knowledge and competence, I'm now at my wit's end. Rather maddening.
What did I overlook, and what can I do?
TIA for your help!
Try flash a pre-rooted stock 2.3.3 ROM
1) Download ftf here: http://forum.xda-developers.com/showthread.php?p=16121725
2) Find the folder where flashtool is & place the ftf in /flashtool/firmwares/
3) Flaaaaash!
Thanks for the tip. This is the dreaded part where the palms get sweaty, heat comes on and I start scratching my earlobe nervously.
Not sure if I can/should tackle this – as mentioned before "...very limited knowledge and competence". At least I'm honest about my limitations
Selam Çok Türkiye'de bir Alman başbakanının abd'de (hope babylon didn't mangle this)
Root_Unroot_Sonyv1.5 on http://knowmydroid.com/blog/root-your-android-handset-in-just-a-single-click worked – the only one.
Hi mates¡
First of all, sorry for my english.
I didnt want open a thread for my issue but i cant find anthing thath work for me. I began to comment the issue at Pandemic's thread (it's the guide that I below to flash). When I read the answers is like my problem is so weird...
Well, my setup:
* Neo Mt15i with 0.62 stock
* Pc with a clean installation of Ubuntu 12.04
* I installed Java JDK with this Guide:
http://forums.team-nocturnal.com/showthread.php/772
* I installed ADB with that:
http://forums.team-nocturnal.com/showthread.php/773
After that, I add tu /udev/rules/ with my IDVENDOR and IDPRODUCT (I get it using the terminal using "$ lsusb". I readed it from a guide at XDA but cant find now, later I will edit this and add the link ) the line from flashtool web:
Add these rules to /etc/udev :
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="*", MODE="0777"
Click to expand...
Click to collapse
Click to expand...
Click to collapse
* Download Flashtool 0.6.9.1;M check Md5 (OK) and extrac in home folder (my user folder)
* Download 2 differents files of firmware 0.42 GLOBAL for MT15i; I cant find the MD5 of those
PROCESS
Well, doing all of that Flashtool can recognise my Neo ON with Usb debbuging ON; third applications ON; MSC ON
FLASHTOOL LOG:
02/058/2012 11:58:14 - INFO - <- This level is successfully initialized
02/058/2012 11:58:14 - INFO - Flashtool Version 0.6.9.1 built on 2012-04-09 19:43:11
02/058/2012 11:58:14 - INFO - You can drag and drop ftf files here to start flashing them
02/058/2012 11:58:19 - INFO - Device disconnected
02/058/2012 11:58:28 - INFO - Device connected with USB debugging off
02/058/2012 11:58:28 - INFO - For 2011 devices line, be sure you are not in MTP mode
02/058/2012 11:58:29 - INFO - Device connected with USB debugging on
02/058/2012 11:58:30 - INFO - Connected device : MT15
02/058/2012 11:58:30 - INFO - Installed version of busybox : N/A
02/058/2012 11:58:30 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
Click to expand...
Click to collapse
Afterthat click flash; select Firmware (on fw folder) and connect the phone on FLASHMODE when the prompt order and thats its my LOG:
02/058/2012 11:58:54 - INFO - Device disconnected
02/059/2012 11:59:10 - INFO - Selected MT15i_4.0.2.A.0.42_Global.ftf
02/059/2012 11:59:10 - INFO - Preparing files for flashing
02/059/2012 11:59:12 - INFO - Please connect your device into flashmode.
02/059/2012 11:59:17 - INFO - Device connected in flash mode
02/059/2012 11:59:17 - INFO - Phone ready for flashmode operations.
02/059/2012 11:59:17 - INFO - Start Flashing
02/059/2012 11:59:17 - INFO - Flashing loader
02/059/2012 11:59:19 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : NOT_ROOTABLE
02/059/2012 11:59:19 - INFO - Flashing adsp.sin
02/059/2012 11:59:23 - INFO - Ending flash session
02/059/2012 11:59:39 - ERROR - Transferred 41472 bytes of 65536
02/059/2012 11:59:39 - ERROR - Error flashing. Aborted
02/059/2012 11:59:40 - INFO - Device disconnected
Click to expand...
Click to collapse
I must to unplug the NEO because it dont work. When I do this LOG its the 10 time i tried, and never works, even I wait for half hour. Thats because I didnt wait this time, always its the same...
I will update that with SCREENSHOTS later... For a easier understanding.
* I must use a virtual machine to install SEUS or PCCOMPANION, because of that I create that with VIRTUAL BOX and install winXP. I try flashtool here too.
I installed JavaJDK; SDK; DRIVERS from drivers folder of Flashtool.
No works either...The same result
I think to create another VM with win7 to try on that but i will do it later.
Thats all my problem, i dont know what more I can do...Could you help me??
Many many thanks for all those wath read the long text and dont get tired of my english.
Your udev rules is flaky, flashtool is a more than just adb.
Use the one from here
http://forum.xda-developers.com/showthread.php?p=25511424
Also don't connect the phone till it tells you
Sent from my MT11i using Tapatalk
Thanks for the fast answer.
In the link that you wrote before there are another link of minus,and those are dead links...
My android rules in udev have more info, I copy that of the link I posted before about install ADB. At final of these links I write that one of FLAHTOOL web. I found another three lines to write here but im not at pc and I havent the links here... This three lines was writed for a Spanish xdader at a thread its the only thing I remember.
Later I will post the link and my android rules.
Any idea for now?
Sent from my MT15i using XDA
The link is not dead, click standard view, then back then refresh it will work
Sent from my MT11i using Tapatalk
Sorry men, its true, I check ir fast and didnt think too much...tomorrow I will try them on pc.
I will search info about these files because I dont know anything,
There are another thread talking about them, or an howto install them?? Im not at pc and search here its worth....
Im so noob at linux too
But I learn fast when something its interesting to me, and ubuntu surprise so much to me.
Many many thanks for your help
Sent from my MT15i using XDA
which language installed on your ubuntu is it non-english
exactly flashtool have some issues on non-english OS
you can put this line on flashtool executable file
export LANG=en_US.UTF-8
than flashtool will work fine
EDIT:flashtool was updated to 0.7.1.0 you can get it from here
mpiekp said:
The link is not dead, click standard view, then back then refresh it will work
Sent from my MT11i using Tapatalk
Click to expand...
Click to collapse
I change my android.rule file, I put yours one. Continue cant flashing, and when I connect with the phone ON Flashtool recognise it, and ADB too (with "$ adb devices").
The first one I have was three lines (one/conecction mode) which I get from this thread:
http://forum.xda-developers.com/showthread.php?t=1612273
Thats one is my actual 99-android.rules
http://tinypaste.com/91108a48
yacloo said:
which language installed on your ubuntu is it non-english
exactly flashtool have some issues on non-english OS
you can put this line on flashtool executable file
export LANG=en_US.UTF-8
than flashtool will work fine
EDIT:flashtool was updated to 0.7.1.0 you can get it from here
Click to expand...
Click to collapse
Thanks men, I have spanish language installed on Ubuntu, and i havent any idea of where I have to put that line of code when I open it with gEdit.
could I change my language now for that?
I see now that always that I unplugg the phone flashtool first say that is in Usb debuging OFF and then says thats its ON,,,I saw it on other thread (which i cant found for now)
With the new version of Flashtool i have always the same problem:
04/000/2012 05:00:01 - INFO - <- This level is successfully initialized
04/000/2012 05:00:01 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:14
04/000/2012 05:00:01 - INFO - You can drag and drop ftf files here to start flashing them
04/000/2012 05:00:01 - INFO - Device disconnected
04/000/2012 05:00:11 - INFO - Selected MT15i_4.0.2.A.0.42_Vodafone.ftf
04/000/2012 05:00:11 - INFO - Preparing files for flashing
04/000/2012 05:00:11 - INFO - Please connect your device into flashmode.
04/000/2012 05:00:16 - INFO - Device connected in flash mode
04/000/2012 05:00:17 - INFO - Reading device information
04/000/2012 05:00:37 - INFO - Start Flashing
04/000/2012 05:00:37 - INFO - Flashing loader
04/000/2012 05:00:37 - INFO - Ending flash session
04/000/2012 05:00:37 - ERROR -
04/000/2012 05:00:37 - ERROR - Error flashing. Aborted
04/000/2012 05:00:37 - INFO - Device disconnected
Click to expand...
Click to collapse
With olders flashtools have same issues that before, starts but stops randomly...nothing changes after all...for now I hope.
The ways off today:
* 3 FTF 0.42 global and vodafone for MT15i
* 3 versions of FLASHTOOL (all with md5 OK)
* Repeat after fail, dont use before SEUS
* Ubuntu and Winxp on VM
Thanks for all the support
pollolpc said:
Thanks men, I have spanish language installed on Ubuntu, and i havent any idea of where I have to put that line of code when I open it with gEdit.
could I change my language now for that?
Click to expand...
Click to collapse
open FlashTool file and your file must look like this
#!/bin/sh
export BASEDIR=$(dirname $0)
export system64=$(uname -m)
export LANG=en_US.UTF-8
if test -z "${JAVA_HOME}"
then
if test "${system64}" = "x86_64"
then
export JAVA_HOME=${BASEDIR}/x10flasher_lib/linjre64
else
export JAVA_HOME=${BASEDIR}/x10flasher_lib/linjre32
fi
echo "JAVA_HOME not set. Using default value : ${JAVA_HOME}"
fi
chmod 755 ${BASEDIR}/x10flasher_lib/adb.linux
chmod 755 ${BASEDIR}/x10flasher_lib/fastboot.linux
chmod 755 ${BASEDIR}/x10flasher_lib/adb.mac
chmod 755 ${BASEDIR}/x10flasher_lib/fastboot.mac
if test -e ${JAVA_HOME}/bin/java
then
$JAVA_HOME/bin/java -Xms128m -Xmx512m -jar x10flasher.jar
else
echo "No Java in specified path in JAVA_HOME=${JAVA_HOME}"
echo "Set the variable to a valid Java installation"
fi
Click to expand...
Click to collapse
Because I didnt knew how insert that line in FLASHTOOL i tried to do other thing; change language on a terminal wich will run flashtool....i dont have idea if this is stupid....but i tried, nothing to loose i thinked....
"change the language with that :
$ export LANG=en_US.UTF-8
Click to expand...
Click to collapse
I copied the info give me the terminal, i didnt know if this could be helpful...
Post at tiny paste for a cleaner post:
http://tinypaste.com/38e38b82
yacloo said:
open FlashTool file and your file must look like this
Click to expand...
Click to collapse
Ok many many thanks, i give a try richt now
Didnt work bro, try to start flashing but stops suddenly without flash any file. Before didnt try flash, stops at READ DEVICE...
Heres the log:
http://tinypaste.com/37c68abc
Thanks a lot for your attention
pollolpc said:
Didnt work bro, try to start flashing but stops suddenly without flash any file. Before didnt try flash, stops at READ DEVICE...
Heres the log:
http://tinypaste.com/37c68abc
Thanks a lot for your attention
Click to expand...
Click to collapse
I think you are using 64-bit ubuntu
Check that libusb-1.0 is installed. On 64bits system, both 64bit and 32bit should be installed
hope can work
yacloo said:
I think you are using 64-bit ubuntu
Check that libusb-1.0 is installed. On 64bits system, both 64bit and 32bit should be installed
hope can work
Click to expand...
Click to collapse
Im usin 64 bits, yes. I think I installed them...I check Synaptics:
Uploaded with ImageShack.us
Both ticked from bottom no?
I think only 64bit libusb installed
You can get it those files for 32 bit from packages.ubuntu.com
Both files are same low versioned one for old applications
Sent from my MT11i using XDA
yacloo said:
I think only 64bit libusb installed
You can get it those files for 32 bit from packages.ubuntu.com
Both files are same low versioned one for old applications
Sent from my MT11i using XDA
Click to expand...
Click to collapse
Im reading about this, i found that if I install 32 bits package, uninstall 64 bits....that isnt a problem? ... I found this in another forum:
http://askubuntu.com/questions/127701/gcc-m32-cannot-find-libraries
You could install the 32-bit packages for these libraries:
$ sudo apt-get install libusb-dev:i386 libX11-dev:i386
Note, however, that this will remove the 64-bit versions. Probably it's better to use a chroot (e.g. with cowbuilder or pbuilder) or Qemu image for this kind of thing. E.g. create the file ~/.pbuilderrc-precise-i386:
# Set this to the distribution you want to build for
DISTRIBUTION=precise
# The architecture you want to build for
ARCHITECTURE=i386
# The directory in which to store the chroot base image
BASEPATH=/var/cache/pbuilder/base-precise-i386.cow
# The repositories to be enabled in the /etc/apt/sources.list
COMPONENTS="main universe"
# If you want to speed things up with ccache, enable these options
export CCACHE_DIR="/var/cache/pbuilder/ccache"
export PATH="/usr/lib/ccache:${PATH}"
# List here all packages you need to build your software
# (e.g. build-essential, libusb-dev, libX11-dev, etc.)
EXTRAPACKAGES=ccache
# List here all directories from you system that should be visible inside the chroot
BINDMOUNTS="${CCACHE_DIR} ${HOME}/projects"
Then install cowbuilder and create the base image as follows:
$ sudo apt-get install cowbuilder
$ sudo cowbuilder --create --configfile ~/.pbuilderrc-precise-i386
Lastly, enter the chroot and finish configuring it (copy over configuration files:
$ sudo cowbuilder --login --save-after-exec --configfile ~/.pbuilderrc-precise-i386
You can exit the chroot using Ctrl+D or using exit. Now you have set up your base-image. In the future, don't use the --save-after-exec flag any more when entering the chroot. This ensures that all the modifications will be discarded after you leave the chroot, ensuring a clean build environment for future builds.
Now you should be able to enter the chroot and build your software:
$ sudo cowbuilder --login --configfile ~/.pbuilderrc-precise-i386
% cd $HOME/projects/foo
% # build project foo
Note, however, that the files created in this way will be owned by root. Hence, out-of-source builds are a very good idea.
Click to expand...
Click to collapse
I dont know what to do
pollolpc said:
Im reading about this, i found that if I install 32 bits package, uninstall 64 bits....that isnt a problem? ... I found this in another forum:
http://askubuntu.com/questions/127701/gcc-m32-cannot-find-libraries
I dont know what to do
Click to expand...
Click to collapse
That was ia32 lib issue install both files and ia32 lib file other 64 ones will not be removed
Sent from my MT11i using XDA
I check that with this: $ dpkg -l libusb\* and I have this versions:
||/ Nombre Versión Descripción
+++-==============-==============-============================================
ii libusb-0.1-4 2:0.1.12-20 userspace USB programming library
ii libusb-1.0-0 2:1.0.9~rc3-2u userspace USB programming library
un libusb-1.0-0-d <ninguna> (no hay ninguna descripción disponible)
un libusb0 <ninguna> (no hay ninguna descripción disponible)
ii libusbmuxd1 1.0.7-2 USB multiplexor daemon for iPhone and iPod T
Click to expand...
Click to collapse
0,1.4 is 32 bits or im wrong again?
The last version of flashtool say that:
04/015/2012 07:15:07 - INFO - <- This level is successfully initialized
04/015/2012 07:15:07 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:14
04/015/2012 07:15:07 - INFO - You can drag and drop ftf files here to start flashing them
04/015/2012 07:15:08 - INFO - Device connected with USB debugging on
04/015/2012 07:15:09 - INFO - Connected device : MT15
04/015/2012 07:15:09 - INFO - Installed version of busybox : N/A
04/015/2012 07:15:09 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
04/015/2012 07:15:09 - INFO - Phone in recovery mode
04/015/2012 07:15:09 - INFO - Root Access Allowed
WTF? Im still at 0.62 on "about"
Sorry for be worried
...I have an update avaiable ny OTA....The 0.62...and my about section sqy 0.62 too..:banghead:
Sent from my MT15i using XDA
pollolpc said:
I check that with this: $ dpkg -l libusb\* and I have this versions:
0,1.4 is 32 bits or im wrong again?
The last version of flashtool say that:
04/015/2012 07:15:07 - INFO - <- This level is successfully initialized
04/015/2012 07:15:07 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:14
04/015/2012 07:15:07 - INFO - You can drag and drop ftf files here to start flashing them
04/015/2012 07:15:08 - INFO - Device connected with USB debugging on
04/015/2012 07:15:09 - INFO - Connected device : MT15
04/015/2012 07:15:09 - INFO - Installed version of busybox : N/A
04/015/2012 07:15:09 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
04/015/2012 07:15:09 - INFO - Phone in recovery mode
04/015/2012 07:15:09 - INFO - Root Access Allowed
WTF? Im still at 0.62 on "about"
Sorry for be worried
Click to expand...
Click to collapse
download those files and install via dpkg -i *.deb
libusb-0.1-4_0.1.12-20_i386.deb
libusb-1.0-0_1.0.9~rc3-2ubuntu1_i386.deb
and you have to search on synaptic for ia32-libs and ia32-libs-multiarch
than install those packages
if doesn't work switch to 32bit ubuntu or 32bit windows for better compatibility
It's working fine here on 64 12.4
If the above doesn't work, I'll post a list of installed packages, should sort you out
Sent from my MT11i using Tapatalk
Overcoming Unknow Baseband
[Permit sharing]
For those of you who have problems sim card & baseband & IMEI invalid and have tried to do with mtk droid tools or other tools but still have guns could be the solution as follows:
the above problems become invalid due to partition damaged secro.img crushed data from another partition
to fix it please go to the scene:
- Take secro.img from stock rom.
if you do not have please download LINK
[For Evercoss A7T MT6572]:
http://www.4shared.com/get/xzSpG0F8ba/A7TFile_Flashing_Unknow_Baseba.html
- Do not forget the extracted files first
The folder contains a scatter file MT6572
And secro.img
- Please Turn HH
FLASH WITH flashtool:
- Open flashtool
- Input files scatter mt6572
- Check the list SEC_RO [secro.img]
- Turn off and unplug the battery HH her
- Click download> ok / yes
- Colokin HH usb and plug the battery into its
- Wait until the exit popup green color
- ENDS
- Well already in its baseband tuh sumon
NB: For links SP Flash Tool pulls out in doc !!!!!!
DWYOR
Agus salam MK
https://m.facebook.com/agus.romanc?refid=18
Credit:
fithrul Azmi
Deva R Renjani
Spoiler for unknow fix solved baseband
nice guide bro..
thanks.