MSM7227 S1Boot has been patched to ignore SIN header signature by the_laser.
You need phone which you either did not unlock by cable, or phone which you unlocked via SEtool2 only.
If you unlocked with Omnius, in C:\ProgramData\Omnius for SE\Backups\Xperia X8
you have file called: Xperia X8_IMEI_DATE_SIMLock.opd
Note, the fixed S1Boot for other tools should come soon.
Restore that TA backup, then use semc.cmd in the_laser's release to unlock bootloader - you'll restore SIM lock this way!
Currently there is no unlocked bootloader for Omnius unlocked phones.
* Kernel build instructions in second post.
* Original post by the_laser with unlock instructions in third post.
What will this allow:
* custom kernels
* better/fully working Gingerbread
* no need for chroot to avoid init crash bug
* overclock/Synaptics fake DT/Cypress real DT/MDDI fix built in kernel
This will not enable:
* real DT on Synaptics digitizer
To make custom kernel:
1) Compile it.
2) Grab Image, not zImage
3) Make ramdisk.gz (cpio ramdisk content, then gzip the cpio archive)
4) Place both files in ./msm7227/sinTools
5) Name then image and ramdisk, no extension, remove existing files
6) Exectue example_build.cmd
7) Grab result.elf.sin from result.zip, rename to kernel.sin and pack in ftf bundle with patched loader.sin from ./msm7227/loader
8) Flash with FlashTool.
Greetings.
warning.
if you are not developer, please quit reading that post.
wait for user friendly tool with one big button.
here ( View attachment msm7227.7z) is toolset to permanently "unlock" semcboot of msm7227 semc phones.
that means, you can use own kernel and so on.
steps,precautions, etc.
unpack archive to any directory.
if you using eset antivirus or similar ****, it will find evil virus in adb.exe.
ignore that, it is not virus in any way, it is standard android debug bridge, bundled in one file to save space and usability.
now, if your phone unlocked officially:
flash phone with standard 2.0,2.1 android firmware,because kernel mapper module compiled for "2.6.29" kernel.
of course, enable "usb debugging"
run msm7227_semc.cmd,
( if you want, examine it before run, it is pretty straightforward. )
you will get similar output
Code:
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
1743 KB/s (585731 bytes in 0.328s)
error: protocol fault (no status)
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights.
192 KB/s (3087 bytes in 0.015s)
success
Waiting ...
Getting ROOT rights.
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
504 KB/s (8064 bytes in 0.015s)
Second, we need to write semcboot ;)
1130 KB/s (596916 bytes in 0.515s)
successfully wrote 0003ff00
Press any key to continue . . .
bingo, your phone now has unlocked bootloader.
if your phone unlocked by setool2 software, use msm7227_setool2.cmd
if your phone unlocked by 3rd-party software other than setool2, do not run anything -
it will disable radio capability of your phone and you will need to unlock phone by setool2 software.
to find out if you can safely unlock bootloader, here (View attachment s1tool.7z) is tool.
if you will see "NOT RECOGNIZED SIMLOCK CERTIFICATE", you should not use either of .cmd.
hopefully, mizerable flea and mOxImKo will release something similar for your phone.
okay, now about other details.
1.
unlocked bootloader require unlocked loader, yep ?
loader\loader.sin is special unlocked loader, which will be accepted ONLY after your "unlock" semcboot with previous steps.
to distinguish unlocked semcboot and original semcboot, first letter in version tag of semcboot output will be lower case, i. e. "r8A029"
( same applies for loader version tag )
so, all that stuff with signatures are not for us, so i removed them - loader will ignore signature part of SIN file.
2.
we should make SIN file somehow, right ?
for that i prepared "dumb" bin2sin utility.
Syntax : bin2sin [input] [partition info, 32 digits] [type] [block size]
Click to expand...
Click to collapse
[input] - is input binary file.
[partition info]
android implementation on s1 semc qualcomm phones based on partitions,so we MUST define it for our file.
you can get required partition info from standard semc sin files, it is first 0x10 bytes of DATA, right after header, i.e.
e10 kernel partition info
03000000010000402001000040000000
Click to expand...
Click to collapse
[type] - partition type, 9 - partition without spare, 0xA - partition with spare.
kernel partition is partition without spare.
if that parameter omitted, type = 9
[block size] - nand block size, if omitted, it is standard size 0x20000
there is example in sinTools\example_build.cmd
3.
kernel should be prepared specially to be accepted by semcboot.
for that there is tool bin2elf.
Syntax : bin2Elf.exe [nbrOfSegments] [EntryPoint] [Segment1] [LoadAddress1] [Attributes1] ...
Click to expand...
Click to collapse
we need 2 segments:
segment 1 is unpacked linux kernel image, i.e.
( e10/kernel/arch/arm/boot/Image )
it looks like entrypoint and load address for segment 1 is always same for all msm7227-based semc phone, it is 0x00208000
attributes for image 0x0
segment 2 is ramdisk.
it looks like entrypoint and load address for segment 1 is always same for all msm7227-based semc phone, it is 0x01000000
set attributes for ramdisk 0x80000000, that is extremly important.
there is simple kernel example in sinTools\example_build.cmd
ps.
@blagus:
NAND MPU disabler has only one relation to rFoNe - he took it from setool2, together with entire idea for msm7227 bypass.
your 6-wings friend with many nicks done exactly same.
NAND MPU has nothing to do with memory firewall, so it will not help with kexec things, however, who will care now.
edit:
there was minor flaw in msm7227_setool2.cmd - i forgot to change source bootwriter name and both .cmd wrote same semc boot:
flawed:
@echo Second, we need to write semcboot
bootTools\adb.exe push my7227bootwrite_semcSL /data/local/tmp/my7227bootwrite_setool2SL
Click to expand...
Click to collapse
correct:
@echo Second, we need to write semcboot
bootTools\adb.exe push my7227bootwrite_setool2SL /data/local/tmp/my7227bootwrite_setool2SL
Click to expand...
Click to collapse
of course, every developer or man with capability to read fixed it immediately.
just in case, i uploaded "fixed" package.
Ok, just because someone is asking what the hell is happened, got a request by Blagus to delete all posts but his first 2 and the_laser one, thread is now closeed untill Blagus will say me to open it.
How to verify if the bootloader on your phone is really unlocked
the_laser (earlier in this thread) said:
unlocked bootloader require unlocked loader, yep ?
loader\loader.sin is special unlocked loader, which will be accepted ONLY after your "unlock" semcboot with previous steps.
to distinguish unlocked semcboot and original semcboot, first letter in version tag of semcboot output will be lower case, i. e. "r8A029"
Click to expand...
Click to collapse
This means s1tool log file can provide us with verification if we unlocked bootloader correctly.
S1tool link: http://forum.xda-developers.com/showpost.php?p=17374120&postcount=26
Example of log file (mine):
Code:
9/9/2011 21:41:44 Welcome to S1 identify tool
9/9/2011 21:45:13
9/9/2011 21:45:13 TO CONNECT NEXT PHONES
9/9/2011 21:45:13 X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
9/9/2011 21:45:13 LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
9/9/2011 21:45:13 PRESS AND HOLD "BACK" BUTTON...
9/9/2011 21:45:13
9/9/2011 21:45:13 PLEASE ATTACH TURNED OFF PHONE NOW
9/9/2011 21:45:13
9/9/2011 21:45:46
[B][U]9/9/2011 21:45:46 RUNNING S1_EROM VER "r8A029"[/U][/B]
9/9/2011 21:45:46 SOFTWARE AID: 0001
9/9/2011 21:45:46 LOADER AID: 0001
9/9/2011 21:45:49 FLASH ID: "002C/00BC"
9/9/2011 21:45:49 LOADER VERSION: "R4A045"
9/9/2011 21:45:49
9/9/2011 21:45:49 MODEL (from GDFS): X8
9/9/2011 21:45:49 SOFTWARE VERSION: 1236-9291_2.1.1.A.0.6
9/9/2011 21:45:49 CUSTOM VERSION: 1241-3178_R1B
9/9/2011 21:45:49 FILESYSTEM VERSION: WORLD-1-8_2.1.1.A.0.6
9/9/2011 21:45:49 SERIAL NO: CB511SPH7Q
9/9/2011 21:45:49
[B][U]9/9/2011 21:45:49 SEMC SIMLOCK CERTIFICATE[/U][/B]
9/9/2011 21:45:49 Elapsed:36 secs.
If the line RUNNING S1_EROM FROM VER "#8A029" has a lowercase "r" letter replacing the "#" (RUNNING S1_EROM FROM VER "r8A029"), your bootloader has been unlocked . If it has an uppercase "R" replacing the "#" (RUNNING S1_EROM FROM VER "R8A029"), your bootloader is NOT unlocked .
Cheers ,
SpyderX
Im confused !!
are you saying my phone has to have been sim unlocked for this to work because i have not had my x8 sim unlocked and i unlocked my boot loader perfectly fine. and thanks to the devs for all their hard work. now just gotta compile my own kernal
Welcome to S1 identify tool
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "r8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"
MODEL (from GDFS): E15i
SOFTWARE VERSION: 1236-9291_2.1.1.A.0.6
CUSTOM VERSION: 1241-4091_R3B
FILESYSTEM VERSION: WORLD-1-8_2.1.1.A.0.6
SERIAL NO: CB511RZG51
SEMC SIMLOCK CERTIFICATE
Elapsed:56 secs.
Click to expand...
Click to collapse
Success ! ty Dev ! you r the best !
lotus13 said:
Success ! ty Dev ! you r the best !
Click to expand...
Click to collapse
i turned off my phone, click button in s1tool and connect my phone to computer with pressed back button? and nothing writes only
2011. 09. 09. 19:02:20 Welcome to S1 identify tool
2011. 09. 09. 19:03:03
2011. 09. 09. 19:03:03 TO CONNECT NEXT PHONES
2011. 09. 09. 19:03:03 X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
2011. 09. 09. 19:03:03 LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
2011. 09. 09. 19:03:03 PRESS AND HOLD "BACK" BUTTON...
2011. 09. 09. 19:03:03
2011. 09. 09. 19:03:03 PLEASE ATTACH TURNED OFF PHONE NOW
2011. 09. 09. 19:03:03
2011. 09. 09. 19:03:39 PROCEDURE STOPPED BY USER
2011. 09. 09. 19:03:39 Elapsed:250 secs.
Please help...
tony-noob said:
i turned off my phone, click button in s1tool and connect my phone to computer with pressed back button? and nothing writes only
2011. 09. 09. 19:02:20 Welcome to S1 identify tool
2011. 09. 09. 19:03:03
2011. 09. 09. 19:03:03 TO CONNECT NEXT PHONES
2011. 09. 09. 19:03:03 X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
2011. 09. 09. 19:03:03 LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
2011. 09. 09. 19:03:03 PRESS AND HOLD "BACK" BUTTON...
2011. 09. 09. 19:03:03
2011. 09. 09. 19:03:03 PLEASE ATTACH TURNED OFF PHONE NOW
2011. 09. 09. 19:03:03
2011. 09. 09. 19:03:39 PROCEDURE STOPPED BY USER
2011. 09. 09. 19:03:39 Elapsed:250 secs.
Please help...
Click to expand...
Click to collapse
1.TURN OFF YOUR PHONE.
2.Open S1tool.CLick DO JoB(right side)
3.On your phone:
a.Pressing the back key.connect you phone.untill s1tool says:SEMC SIMLOCK CERTIFICATE
b.DO NOT RELEASE THE BACK KEY!
lotus13 said:
1.TURN OFF YOUR PHONE.
2.Open S1tool.CLick DO JoB(right side)
3.On your phone:
a.Pressing the back key.connect you phone.untill s1tool says:SEMC SIMLOCK CERTIFICATE
b.DO NOT RELEASE THE BACK KEY!
Click to expand...
Click to collapse
i do this 5 times but nothing... its normal if i don't have unlocked sim?can this cause this problem?
lotus13 said:
1.TURN OFF YOUR PHONE.
2.Open S1tool.CLick DO JoB(right side)
3.On your phone:
a.Pressing the back key.connect you phone.untill s1tool says:SEMC SIMLOCK CERTIFICATE
b.DO NOT RELEASE THE BACK KEY!
Click to expand...
Click to collapse
Don't have the step 3.On your phone
Just
1.TURN OFF YOUR PHONE.
2.Open S1tool.CLick DO JoB(right side)
3.Pressing the back key.and then connect you phone.untill s1tool says:SEMC SIMLOCK CERTIFICATE
b.DO NOT RELEASE THE BACK KEY!
lovex8 said:
Don't have the step 3.On your phone
Just
1.TURN OFF YOUR PHONE.
2.Open S1tool.CLick DO JoB(right side)
3.Pressing the back key.and then connect you phone.untill s1tool says:SEMC SIMLOCK CERTIFICATE
b.DO NOT RELEASE THE BACK KEY!
Click to expand...
Click to collapse
LOOOOOOOOOOOOOOOL =)))
When i said : On your phone , i meant that the next steps should be done on the phone.as you see a.b.c.
you r an idiot.sorry for telling you this
I'm sorry to misunderstand you 'turn on your phone'..XD
Just forget what I said...I'm really sorry...
Aftrer connecting i got this message
Welcome to S1 identify tool
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
llbug:[\\?\USB#Vid_0fce&Pid_adde#5&256bc46a&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}] open error: "The device does not recognize the command"
Elapsed:30 secs.
where is the problem?
@ognjenr
Install X8 adb drivers.
Read this:
http://forum.xda-developers.com/showthread.php?t=1254225
First post step 7
By the way devs, I noticed that bootloader unlocking process puts 4 files in /data/local/tmp (expl, fixPart, mapper_2.6.29.ko and (in my case) my7227bootwrite_semcSL) and executes them.
Is it safe to remove these files? If no, what happens if we remove this files? And what happens if we format our phone's /data partition? Will these files be removed?
Sorry for asking so many questions but these questions are quite important as these pertain to S1Boot and meddling with S1boot can cause hard bricks .
SpyderX said:
By the way devs, I noticed that bootloader unlocking process puts 4 files in /data/local/tmp (expl, fixPart, mapper_2.6.29.ko and (in my case) my7227bootwrite_semcSL) and executes them.
Is it safe to remove these files? If no, what happens if we remove this files? And what happens if we format our phone's /data partition? Will these files be removed?
Sorry for asking so many questions but these questions are quite important as these pertain to S1Boot and meddling with S1boot can cause hard bricks .
Click to expand...
Click to collapse
android delete all files in this folder by each reboot,so after reboot they will be deleted.
XperianPro said:
android delete all files in this folder by each reboot,so after reboot they will be deleted.
Click to expand...
Click to collapse
No, android doesn't. I've rebooted my phone 6 times ever since unlocking my bootloader and the files are still there. Please do your research and experiment with what you have read before posting false information , especially because you are a "pro".
mine only got "available_frequencies" in data/local/tmp. i dont see those file you have
@moaj
Now that's very strange. Can you put an empty file in /data/local/tmp, reboot, and then see if the empty file is still there? Post your results here.
@Devs
To reiterate in case you only read the last few posts:
By the way devs, I noticed that bootloader unlocking process puts 4 files in /data/local/tmp (expl, fixPart, mapper_2.6.29.ko and (in my case) my7227bootwrite_semcSL) and executes them.
Is it safe to remove these files? If no, what happens if we remove this files? And what happens if we format our phone's /data partition? Will these files be removed?
Sorry for asking so many questions but these questions are quite important as these pertain to S1Boot and meddling with S1boot can cause hard bricks.
Related
Hi,
I tried to flash my Xperia X10 with DavinciTeam but I get the following error;
(#) DaVinci Service Client v22.76 (User: 50250 / Credits: 10)
New Device Connected On USBF1
Device Identification Started...
The IMEI of the product is:
35941903237050
Model info:
X10i
Security info:
Color: Red
LDR/SW/CUST AIDs: 0001/0001/0001
EROM info:
S1_EROM R8A013 1226-2253 [20100119 17:24:00]
Software info:
1227-4612_R2BA020
Customization info:
1235-7379 R9A
Language info:
1227-4607_R2BA020
Identification Time - 00:00:02
Done!
Service Selection Started...
Getting Software List From Server For: X10 / 0001 / Red...
SELECTED: Flash / Debrand / Re-Brand [SonyEricsson] X10 / 0001 / Red / R1FA014 / 3 AU/SENSUOUS BLACK (1234-4828/R8A | NAM1)
Script Execution Started...
Checking Files...
Starting up...
Script initialization. Please wait...
Loading S1 Loader... OK
20091222 15:39:00 S1_LOADER R4A024 1226-2250
Memory Stick: 8GB
Opening TA...FAILED
Reading TA Please Wait...FAILED
Execution Time - 00:00:09
Done!
Can somebody help me please.
Thank You
Ask the Davinci team theyre probably your best bet seeing as though you paid for it your entitled to help with their product.
Hi,
I bought Motorola Milestone 2 from UK(probably) two days ago and so far everything was fine. I tested WiFi and other tools and it worked pretty well.
Today, I had some auto-reboots when I was using phone, phone usually stopped during starting... but it backs to normal. Then I was calling to my friend, and decided to "END CALL", but nothing happened (I was unable to close this calling 'menu'). During this other apps works fine (I checked browser), then I decided to TURN OFF the phone.
Now I have problems with turning it on, during start I see motorola's logo, then it blinks for a moment and finally screen turns 80% black (a bit brighter than black one, there is some light ). I can't turn off the phone using top button, I have to pull out the battery. When phone is connected to USB, small white diode is working and I can TURN OFF the phone (but I have still the same problem during start).
I tried removing SIM card, SD card, both of them, I don't have "recovery menu" when I am pressing down X key and turning POWER ON (same things happen) - maybe I am doing something wrong during pressing Xkey and power key(??). I have only ARROW UP + POWER ON bootloader menu.
I spent over 6hours for searching solution - no results so far.
What should I do? THANKS IN ADVANCE FOR ANY SUGGESTIONS.
I logged to motoblur and my software version is 62.2.16.A953.Retail.en.GB.
I dont have a milestone 2, i have the original milestone though, and to fix this id just have to load the screen that comes up when you press the UP button on the dpad (arrow). Then plug your phone to your PC, open RSD lite and once your device has been detected you go ahead and flash a stock SBF file.
Hope that helps
XtriFe said:
I dont have a milestone 2, i have the original milestone though, and to fix this id just have to load the screen that comes up when you press the UP button on the dpad (arrow). Then plug your phone to your PC, open RSD lite and once your device has been detected you go ahead and flash a stock SBF file.
Hope that helps
Click to expand...
Click to collapse
Hi, I am thinking about it, I downloaded 5 different SBF files, but I am not sure which I should use in my motorola. I have it on my moto's box: SM, A953, GB, RETAIL, SLVR so it probably comes from UK.
Which version of RSD Lite should I use? I have RSD Lite 4.9
MILS2_U6_2.2.19_SIGNED_UCAMILESTONE2B1B80E100A.0R_USXMILE20OPTAU_P022_A016_M006_HWp2a_Service1FF.sbf.gz
MILA2_U6_3.12.0_SIGNED_US1MILESTONE2RETBRB125LA016.0R_GSXMILETRETBRLA_P026_A009_M012_HWp2a_Service1FF.sbf.gz
MILS2_U6_2.2.16_SIGNED_UCAMILESTONE2B1B80E100A.0R_USXMILE20O2DE_P038_A015_HWp2a_Service1FF.sbf.gz
MILS2_U6_2.2.16_SIGNED_UCAMILESTONE2B1B80E100A.0R_USXMILE20RTDACH_P016_A005_HWp2a_Service1FF.sbf.gz
MILS2_U6_2.2.19_SIGNED_USAMILESTONE2B1B80VF00B.0R_USXMILE20VFAU_P032_A012_M005_HWp2a_Service1FF.sbf.gz
MILS2_U6_2.2.16_SIGNED_UCAMILESTONE2B1B80E100A.0R_UCXMILE20RTGB_P029_A007_HWp2a_Service1FF.sbf.gz
My next problem is when I connect my moto with USB cable, I have something like this in RSD Lite app:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x007012
DRM Version: N / A
AP Die ID: 27200210dc245f010000d8fe0300
BP Die ID: 0000000000000000000000000000
AP Public ID: 48caac38e2b174c29ad89848c7df4d1dd7a87422
BP Public ID: 0000000000000000000000000000000000000000
Are N/A's okay? I do not want to destroy my phone after 2 days ;( (it's my 1st smarhphone)
edit: Well, I loaded the last SBF file and click START in RSD lite... - everythin was fine there but nothing happened with my phone, still the same problem. Any suggestions?
BTW. What will happen if I install another SBF file (german one instead of GB?)
saqus said:
BTW. What will happen if I install another SBF file (german one instead of GB?)
Click to expand...
Click to collapse
Will occur error halfway. You definitely need to flash the UK SBF rom. Follow below link http://megaupload.com/?d=Q29778GX
If you click the link and find out this message appear (The file you are trying to access is temporarily unavailable. Please try again later.) dun worry, try later. Is totally working. Just fix my unit just now with this UK SBF rom. Mine unit is bought from Clove, UK. Cheers...
Hm, I downloaded this file already from another site & I used it - nothing happened.
I will test this version now.
What is a bit weird, when I plug the phone in socket, I can see battery level animation but still can't turn on the phone, nothing happens after motorola's logo.
saqus said:
Hm, I downloaded this file already from another site & I used it - nothing happened.
I will test this version now.
What is a bit weird, when I plug the phone in socket, I can see battery level animation but still can't turn on the phone, nothing happens after motorola's logo.
Click to expand...
Click to collapse
Did you do it the right way? Mine unit auto turn on after finish flash the SBF rom. Then finally disconnect the usb cable.
My moto also turn of after finish, but I see only motorola logo and then blank screen again...
Which version of RSD Lite should I use? I have 4.6 now.
Use version 4.9
Sent from my Milestone 2 XDA App
I am uploading video right now with not working moto on Youtube You will show how amazing it is
http://www.youtube.com/watch?v=KHIZlyt6y94
ENJOY !
saqus said:
I am uploading video right now with not working moto on Youtube You will show how amazing it is
http://www.youtube.com/watch?v=KHIZlyt6y94
ENJOY !
Click to expand...
Click to collapse
Ill give you $300 for it. lol
Seriously though, its a matter of flashing the right SBF the right way. Find out how to get to the Bootloader on the milestone 2. On my milestone 1 all i have to do is keep the DPAD-UP button while turning the phone on.
Once you get there, plug your usb cable to your PC and RSD Lite will detect your phone which will let you flash your SBF file again. Id recommend flashing an UK stock one.
Also, have you installed the proper motorola USB drivers? remember you need to install the appropiate drivers depending on what OS you're using. (ie. Windows 7 x64, theres x64 motorola USB drivers you need to install)
I can imagine how sad you might be right now (after reading your comment on your youtube vid) but really, in my opinion, your phone is anything but permanently bricked
Let me know how that goes.
Good luck
To start Milestone2 into bootloader mode you should turn the phone on while holding the Volume Down and Camera buttons together.
r2beta0 said:
To start Milestone2 into bootloader mode you should turn the phone on while holding the Volume Down and Camera buttons together.
Click to expand...
Click to collapse
Wow, it's second method I think. I used KPAD+UP + POWER and it is also working.
Do you know another method to open RECOVERY MENU (originally X+POWER ON)?
Can someone tell me is this information about device in RSD LITE is good? (my previous post, bolded part)
http://screenshotuploader.com/s/lFoNJoaXJvJ
{
"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"
}
-----------------
Seriously though, its a matter of flashing the right SBF the right way. Find out how to get to the Bootloader on the milestone 2. On my milestone 1 all i have to do is keep the DPAD-UP button while turning the phone on.
Click to expand...
Click to collapse
I used DPAD-UP + POWER ON and I had Bootloader menu.
Once you get there, plug your usb cable to your PC and RSD Lite will detect your phone which will let you flash your SBF file again. Id recommend flashing an UK stock one.
Click to expand...
Click to collapse
I did it (with UK stuff).
Also, have you installed the proper motorola USB drivers? remember you need to install the appropiate drivers depending on what OS you're using. (ie. Windows 7 x64, theres x64 motorola USB drivers you need to install)
Click to expand...
Click to collapse
I think Yes, I have 32bit version.
I can imagine how sad you might be right now (after reading your comment on your youtube vid) but really, in my opinion, your phone is anything but permanently bricked
Click to expand...
Click to collapse
I have exam session right now and I am not thinking about this phone
I think also it is bricked, but there is still a hope!
If nothing new happen during few days (no new ideas) I will send it to repair-service ( I've just received bill from my seller ).
You've got to that RSDLite screen, seems like the program is detecting your phone ok. Go ahead and flash the UK ROM and see how it goes.
I flashed it several times before! When it reboot whole system, I see moto logo and then the same problem - nothing after... :\
Can anyone test something for me with milestone2?
Switch off the phone.
Hold X + POWER ON during the whole test (do not release keys!)
Will it stay on Motorola logo (when you release key it will open RECOVERY SCREEN)?
MY SELLER SAID THAT MY PHONE COMES FROM GERMANY (MOTOROLA'S SHOP FOR EMPLOYERS) BUT IT IS WITH ENGLISH SOFTWARE (and it obviously was). SHould I use another SBF file than GB?
saqus said:
Can anyone test something for me with milestone2?
Switch off the phone.
Hold X + POWER ON during the whole test (do not release keys!)
Will it stay on Motorola logo (when you release key it will open RECOVERY SCREEN)?
MY SELLER SAID THAT MY PHONE COMES FROM GERMANY (MOTOROLA'S SHOP FOR EMPLOYERS) BUT IT IS WITH ENGLISH SOFTWARE (and it obviously was). SHould I use another SBF file than GB?
Click to expand...
Click to collapse
You can use any EU software as long as the bands are compatible. German, GB, EU etc., etc.
I have a similar problem and I'm trying to flash a new SBF, but after flashing I get a checksum error and cant get it to work...
I've activated log, and this is what I get:
14:53:51, March 14, 2011
Line: 527
ERROR: AP Die ID: 237001055bf45e010000d8ff0100
14:53:51, March 14, 2011
Line: 534
ERROR: BP Die ID: 0000000000000000000000000000
14:53:51, March 14, 2011
Line: 541
ERROR: AP Public ID: 38607a9e7df8020ec7cca49460878683e6aaa390
14:53:51, March 14, 2011
Line: 548
ERROR: BP Public ID: 0000000000000000000000000000000000000000
14:57:43, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 32 checksums. File: 0x65A6, Phone: 0x67A6
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:57:44, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 33 checksums. File: 0x4C1B, Phone: 0x4E1B
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:58:08, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 39 checksums. File: 0xA01, Phone: 0xC872
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:58:08, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 40 checksums. File: 0xFDFF, Phone: 0x4A65
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:58:08, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 45 checksums. File: 0x6C96, Phone: 0x6E96
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:58:20, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 66 checksums. File: 0x3C24, Phone: 0x2C0E
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:58:20, March 14, 2011
Line: 1190
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
14:58:20, March 14, 2011
Line: 597
ERROR: Flash failure: Phone[0000]: Error verifying Code Group 32 checksums. File: 0x65A6, Phone: 0x67A6 (Error Code: 31),
Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=32
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
I didn't have anything similar to your problem - In my case everything was OKAY when I flashed my phone (of course phone didn't turn on ).
Yes same problem ... Very strange !!!
Since yesterday my MM2 is briqued on boot animation ....
I have test RSDlite (it's not the first time I use it) but nothing (with 2 SBF different)
RSDLite :
1) Download firmware ==> Ok
2) Installation ==> Ok
3) Reboot ==> block on boot animation .... (look screen say "reboot manually.." but my MM2 is power on )
Please Help me ......
Thanks in advance !
In SWDL.txt you can see :
04/07/11 14:08:52 [Device ID: 0] Please manually power up this phone.
04/07/11 14:08:52 00000f08 Phone.cpp
In file "FlashErrorLog04_07_10_49_19.log"
10:50:08, April 07, 2011
Line: 527
ERROR: AP Die ID: 2b10011191095f010000d8ff0200
10:50:08, April 07, 2011
Line: 534
ERROR: BP Die ID: 0000000000000000000000000000
10:50:08, April 07, 2011
Line: 541
ERROR: AP Public ID: a97b57b8d28c0bbcc1507d9c960995e319ee21db
10:50:08, April 07, 2011
Line: 548
ERROR: BP Public ID: 0000000000000000000000000000000000000000
Who can help please .... ???
{
"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"
}
I wrote this tutorial for every Xperia X8 user that really want to have high performance on his device.
Disclaimer : You are using this at your very own risk.I am not responsible if you don't follow my steps correctly or if your phone blows up after modifications.
Tutorials:
-How to unlock your bootloader in the easiest way ever
-How to flash a custom kernel and rom
-How to get 1GB+ internal memory
-How to swap
-How to get a performance plus
Index:
-Tutorials in second post
-Recommendations and credits in third post
Tutorials
Bootloader unlock
Notes
Take our the battery and check your manufacturing date.If it is 11W29 or above you will not be able to unlock your bootloader.If you try it can result in a hard-brick.
Disable your antivirus because it will interfere the process.It will find ADB.exe as a virus but it isn't a virus.
Requirements
Stock 2.1 Eclair
BaseBand M76XX-TSNCJOLYM-53404015
Some tools.Download here
Flashtool.Get it here
Gordon's Gate Driver.Get it here
Rooted phone.A good rooting tutorial here
Sony PC Companion.Get it at Sony Website.
Step-by-step
Download and extract the tools package I provided here
Install Gordon's Gate
Open Task Manager and kill ADB.exe process
If you don't have drivers for your X8 install PC Companion.
Now turn off your phone
Open S1tool and click on "DO JOB"
Now connect your phone to PC in Flashmode(Press and hold back button and connect the USB cable.Don't release the button until the phone is identified by S1tool)
You should see something like this
9/9/2011 21:41:44 Welcome to S1 identify tool
9/9/2011 21:45:13
9/9/2011 21:45:13 TO CONNECT NEXT PHONES
9/9/2011 21:45:13 X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
9/9/2011 21:45:13 LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
9/9/2011 21:45:13 PRESS AND HOLD "BACK" BUTTON...
9/9/2011 21:45:13
9/9/2011 21:45:13 PLEASE ATTACH TURNED OFF PHONE NOW
9/9/2011 21:45:13
9/9/2011 21:45:46
9/9/2011 21:45:46 RUNNING S1_EROM VER "r8A029"
9/9/2011 21:45:46 SOFTWARE AID: 0001
9/9/2011 21:45:46 LOADER AID: 0001
9/9/2011 21:45:49 FLASH ID: "002C/00BC"
9/9/2011 21:45:49 LOADER VERSION: "R4A045"
9/9/2011 21:45:49
9/9/2011 21:45:49 MODEL (from GDFS): X8
9/9/2011 21:45:49 SOFTWARE VERSION: 1236-9291_2.1.1.A.0.6
9/9/2011 21:45:49 CUSTOM VERSION: 1241-3178_R1B
9/9/2011 21:45:49 FILESYSTEM VERSION: WORLD-1-8_2.1.1.A.0.6
9/9/2011 21:45:49 SERIAL NO: CB511SPH7Q
9/9/2011 21:45:49
9/9/2011 21:45:49 SEMC SIMLOCK CERTIFICATE
9/9/2011 21:45:49 Elapsed:36 secs.
Look for RUNNING S1_EROM VER "x8A029"
Instead of x there should be "r" or "R"
If there is "r" your bootloader is already unlocked
If there is "R" your bootloader is locked
Now look for x SIMLOCK CERTIFICATE.
Instead of x there should be "SEMC" or "NOT RECOGNIZED"
If there is "SEMC" you can continue unlocking your bootloader
If there is "NOT RECOGNIZED" you can't unlock your bootloader (if you try you will not be able to use the phone for calls or SMS as it will lose the radio capability)
Before continue be sure that you have the SEMC SIMLOCK CERTIFICATE and kill any ADB.exe process
Disconnect device.Power on and after boot go into Settings>Applications>Development and check USB Debugging
Now run msm7227_semc.cmd and when prompted press any key to unlock your bootloader
Now you should see something like these
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
1743 KB/s (585731 bytes in 0.328s)
error: protocol fault (no status)
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights.
192 KB/s (3087 bytes in 0.015s)
success
Waiting ...
Getting ROOT rights.
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
504 KB/s (8064 bytes in 0.015s)
Second, we need to write semcboot
1130 KB/s (596916 bytes in 0.515s)
successfully wrote 0003ff00
Press any key to continue . . .
Now press any key to continue
Now your bootloader is unlocked
To test if it worked:
Open S1tool
Shut down your phone
Connect in Flashmode
You should see something like this
9/9/2011 21:41:44 Welcome to S1 identify tool
9/9/2011 21:45:13
9/9/2011 21:45:13 TO CONNECT NEXT PHONES
9/9/2011 21:45:13 X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
9/9/2011 21:45:13 LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
9/9/2011 21:45:13 PRESS AND HOLD "BACK" BUTTON...
9/9/2011 21:45:13
9/9/2011 21:45:13 PLEASE ATTACH TURNED OFF PHONE NOW
9/9/2011 21:45:13
9/9/2011 21:45:46
9/9/2011 21:45:46 RUNNING S1_EROM VER "r8A029"
9/9/2011 21:45:46 SOFTWARE AID: 0001
9/9/2011 21:45:46 LOADER AID: 0001
9/9/2011 21:45:49 FLASH ID: "002C/00BC"
9/9/2011 21:45:49 LOADER VERSION: "R4A045"
9/9/2011 21:45:49
9/9/2011 21:45:49 MODEL (from GDFS): X8
9/9/2011 21:45:49 SOFTWARE VERSION: 1236-9291_2.1.1.A.0.6
9/9/2011 21:45:49 CUSTOM VERSION: 1241-3178_R1B
9/9/2011 21:45:49 FILESYSTEM VERSION: WORLD-1-8_2.1.1.A.0.6
9/9/2011 21:45:49 SERIAL NO: CB511SPH7Q
9/9/2011 21:45:49
9/9/2011 21:45:49 SEMC SIMLOCK CERTIFICATE
9/9/2011 21:45:49 Elapsed:36 secs.
Look for RUNNING S1_EROM VER "x8A029"
Instead of x there is "r" or "R".
If there is "r" you succesfully unlocked your bootloader
If there is "R" your bootloader is still locked.In this case try again from first step.It must work
How to install custom kernel and ROM
Kernel
Notes
Your phone must have unlocked bootloader.If not follow the tutorial above.
You should choose a kernel compatible to desired ROM.
Requirements
BaseBand M76XX-TSNCJOLYM-53404015
Flashtool
Kernel .tft file provided by developer
A compatible custom ROM on SD-Card
Step-by-step
Go into your Flashtool folder
From there go into firmwares folder
Copy your .tft file in there
Power off your phone
Now run Flashtool.exe
Press Flash and connect phone in Flashmode
Now reboot phone and you will see kernel's bootanimation
Custom ROM
Notes
Make sure that the ROM is compatible with your kernel
Requirements
BaseBand M76XX-TSNCJOLYM-53404015
A custom ROM on the SD-Card
Step-by-step
Power on your device
When you see kernel's bootanimation quickly press the back button
Now you should be in ClockWorkMod Recovery
Select Wipe data
Select Install .zip from sd-card
Select the ROM you want
Wait until process is done
How to get 1GB+ Internal Memory and SWAP
Notes
Before starting back-up your SD-Card because it's content will be erased in process
After following the tutorial you will have big internal to install apps and you will not have to move them manually to SD-Card
Also you will have SWAP which is a + to RAM and make your device faster
Requirements
A rooted device
A Class 6 or above SD-Card (Class 4 is also good but not recommended)
A kernel/custom ROM with EXT3/4 and SWAP support (most have those features)
Terminal Emulator and Swapper2 installed on your phone.Both are free on Google Play
Step-by-step
Connect your X8 to PC and format SD-Card
Now disconnect it and reboot into CWM
From CWM go into Advanced and select Partition SD-Card
Here you can select what values you wish but I recommend you the following:
-EXT size 1GB
-SWAP size 256MB
Wait until it finishes.It will take a while.
After the process is done press back key to get back to first CWM menu
From here select Wipe Cache
After it finishes reboot
Now open Terminal Emulator
Type in the following
Code:
su (Press ENTER and allow Superuser acces)
a2sd xdata (Press ENTER and you will see some text and an approval to continue)
y
y
Now your phone will reboot
Now open Swapper2
Press menu key and go to Settings>Advanced
Check Use Swap Partition
Turn swap ON
To check if it worked do the following:
*For Internal Memory go to Settings>Storage and scroll down
*For SWAP open Terminal Emulator and type free.
It should look like this:
NOW TO CONNECT YOU PHONE TO PC IN MASS STORAGE MODE YOU NEED TO DISABLE SWAP FROM SWAPPER2 AND ENABLE IT BACK AFTER YOU DISCONNECT
How to get a performance plus
Notes
This is not my work.This made was created by LtHuNTer_StepheN.You can find original thread here.CONTINUE READING
I took this pack of tweaks and the hotfix for it and created a single package , that's why I put it here
Requirements
Optimization pack.Get it here
Any stock kernel
BaseBand M76XX-TSNCJOLYM-53404015
Features
FileSystem Optimizer
Kernel Optimizer
I/O Scheduler Optimizer
IPv4/IPv6 Optimizer
VM Management
RAM Optimizer
Step-by-step
Put the .zip on SD-Card
Reboot into CWM
Flash .zip
Wipe Cache
Reboot
Some tips
Overclock your device using SMARTASSv2 governor
Use task killers only when your phone lags much
Don't let the battery drain complete
Use simple themes.Maximum 7 mb because with higher the size , higher the resource consumption
Recommendations and credits
Recommendations
Custom ROMs
GingerZaraki - Original thread
GingerDX - Original thread
CM 7.2 - Original thread
MiniCM7 - Original thread
Kernels
nAa Gingerbread Kernel - Original thread
Alfs CM7 Kernel - Original thread
Credits
Code:
[list]
[*]lucastan96
[*]junghyun01
[*]dzolcp
[*]velnens123
[*]SpyderX
[*]LtHuNTer_StepheN
[/list]
IAmNice said:
Uh im not too sure but isnt this just a lot of copy paste? And rom recommandations were done by lucastan96 in his big list of roms(tag popular),kernels,other stuff. Also he listed lots of optimisations. He also made a thread on how to improve performance too. So I appreciate what you have done but it has been done before.
Sent from my E15i using xda app-developers app
---------- Post added at 08:34 PM ---------- Previous post was at 08:33 PM ----------
Also our device will not work as an high end device. We have weak hardware and no more android updates.
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
Umm this is not copy-paste.I wrote it by myself.Look at time when it was posted and time when edited.
I make recommendations from my own experience like lucastan96 maybe did from his
And work like a high-end device is a metaphor.I know our hardware is limited.
Using this tutorial and Chainfire3D from Google Play I can run Temple Run and Jetpack Joyride very smooth.
Sent from my E15i using Tapatalk 2
I have a 8GB card. What is the ideal size that i can set as internal memory?
Thanks for the post.
I have a querry on "How to get 1GB+ Internal Memory and SWAP"
I have got a 8GB class 6 card. What is the ideal size that i can sey as RAM and internal. I have seen u quoting as
-EXT size 1GB
-SWAP size 256MB
is it the same for all sized cards? Or does this vary depending upon card size
Thanx!
sachu21 said:
Thanks for the post.
I have a querry on "How to get 1GB+ Internal Memory and SWAP"
I have got a 8GB class 6 card. What is the ideal size that i can sey as RAM and internal. I have seen u quoting as
-EXT size 1GB
-SWAP size 256MB
is it the same for all sized cards? Or does this vary depending upon card size
Thanx!
Click to expand...
Click to collapse
s
Doesn't warry on sd-card size.Just your preferences.I put the sizes I got but you can put more or less
Good topic
Hello
I have a sony xperia e4 and have updated the phone. Since the update I cannot root it again. Does anyone knows the stock firmware build, so I can flash it to stock again please?
Thanks
Download xperia flashtool latest version, you can download firmware from "xperifirm" (include latest flashtool)
ulum.misbahul said:
Download xperia flashtool latest version, you can download firmware from "xperifirm" (include latest flashtool)
Click to expand...
Click to collapse
I downloaded the correct firmware from xpifirm but when trying to flash it it does not begin saying
07/036/2015 18:36:58 - INFO - Flashtool Version 0.9.18.6 built on 30-05-2015 22:30:00
07/036/2015 18:36:58 - INFO - Executing search strategies to find proxy selector
07/036/2015 18:36:58 - INFO - No proxy found for IE. Trying next one
07/036/2015 18:36:58 - INFO - No proxy found for firefox. Trying next one
07/036/2015 18:36:58 - INFO - No proxy found for java. Trying next one
07/036/2015 18:36:58 - INFO - Syncing devices from github
07/036/2015 18:36:58 - INFO - Scanning devices folder for changes.
07/037/2015 18:37:02 - INFO - Changes have been found. Doing a hard reset (removing user modifications).
07/037/2015 18:37:02 - INFO - Pulling changes from github.
07/037/2015 18:37:04 - INFO - Devices sync finished.
07/037/2015 18:37:09 - INFO - Selected Bundle for E2105. FW release : 24.0.A.3.8. Customization : Customized CE1
07/037/2015 18:37:09 - INFO - Preparing files for flashing
07/037/2015 18:37:09 - INFO - Device disconnected
07/038/2015 18:38:15 - INFO - Please connect your device into flashmode.
07/038/2015 18:38:22 - INFO - Device connected in flash mode
07/038/2015 18:38:22 - INFO - Opening device for R/W
07/038/2015 18:38:22 - INFO - Reading device information
07/038/2015 18:38:22 - INFO - Unable to read from phone after having opened it.
07/038/2015 18:38:22 - INFO - trying to continue anyway
Then it never continues. I can wait all day but nothing happens.
Also flashtool does not support my model. What a shame. there are all the xperia e models apart from e4.
May be not yet support, i do not see E21xx on device list,
Try go to androxyde flashtool thread: http://forum.xda-developers.com/showthread.php?t=920746
Or you can try flashing with sony pc companion, or with sony flashtool emma (unlocked devices)
Why, when I try to flash my xperia e4 e2105, it gives me error which says, : (Unable to read from phone after having opened it)?
Try re flash using sony pc companion,
I can't because I had unlocked the boot loader and pcc won't let me. I tried flash to system in fastboot mode and bricked it. It only boots up to sony and reboots. I can't see the reason why it is not letting me flash the files in flash mode. When I create a bundle there is my phone model number but it won't let me flash the ftt. It's like flashtool is not recognize my device. Also when you go to flashtool, devices, manage, cdfID Editor, my model is not listed.
How with emma flashtool?
Hi, I'm unable to boot and stuck at this error when try to flash: "For flashtool, Unknown Sources and Debugging must be checked in phone settings". I have been able to flash DoomKernelv22 using fastboot, but can't flash ftf file becuase usb debuggin and unknown sources is not enabled and since can't get to boot the phone, i don't know how to enable those or force to install frf file somehow. please help thanks a lot
xplorer11 said:
Hi, I'm unable to boot and stuck at this error when try to flash: "For flashtool, Unknown Sources and Debugging must be checked in phone settings". I have been able to flash DoomKernelv22 using fastboot, but can't flash ftf file becuase usb debuggin and unknown sources is not enabled and since can't get to boot the phone, i don't know how to enable those or force to install frf file somehow. please help thanks a lot
Click to expand...
Click to collapse
If you're using Flashtool you don't have to enable debugging. Just push the button to flash ant connect your phone in FLASH MODE when instructions appears. However, if you've unlocked bootloader phone you can fast-boot any rom you desire, just download ROM and use those commands (if you know where to put al files):
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
and/or other
thanks for answering
LaurynasVP said:
If you're using Flashtool you don't have to enable debugging. Just push the button to flash ant connect your phone in FLASH MODE when instructions appears. However, if you've unlocked bootloader phone you can fast-boot any rom you desire, just download ROM and use those commands (if you know where to put al files):
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
and/or other
Click to expand...
Click to collapse
When I use flashmode to install ftf file, it give me error:
Here is the log file:
02/010/2015 00:10:29 - INFO - Flashtool Version 0.9.19.0 built on 29-07-2015 12:00:00
02/010/2015 00:10:29 - INFO - Executing search strategies to find proxy selector
02/010/2015 00:10:29 - INFO - No proxy found for IE. Trying next one
02/010/2015 00:10:30 - INFO - No proxy found for firefox. Trying next one
02/010/2015 00:10:30 - INFO - No proxy found for java. Trying next one
02/010/2015 00:10:30 - INFO - Syncing devices from github
02/010/2015 00:10:31 - INFO - Scanning devices folder for changes.
02/010/2015 00:10:46 - INFO - Changes have been found. Doing a hard reset (removing user modifications).
02/010/2015 00:10:46 - INFO - Pulling changes from github.
02/010/2015 00:10:48 - INFO - Devices sync finished.
02/010/2015 00:10:53 - INFO - Device connected in flash mode
02/011/2015 00:11:08 - INFO - Device disconnected
02/011/2015 00:11:22 - INFO - Selected Bundle for Sony Xperia Z (C6603). FW release : 10.3.1.A.2.67. Customization : Generic ES
02/011/2015 00:11:22 - INFO - Preparing files for flashing
02/012/2015 00:12:25 - INFO - Device connected in flash mode
02/012/2015 00:12:39 - INFO - Please connect your device into flashmode.
02/012/2015 00:12:41 - INFO - Opening device for R/W
02/012/2015 00:12:41 - INFO - Reading device information
02/012/2015 00:12:41 - INFO - Phone ready for flashmode operations.
02/012/2015 00:12:41 - INFO - Opening TA partition 2
02/012/2015 00:12:41 - INFO - Current device : C6603 - CB5A1VJMRN - 1270-5695_R2E - 1269-5309_10.4.1.B.0.101 - GLOBAL-LTE_10.6.A.0.454
02/012/2015 00:12:41 - INFO - Closing TA partition
02/012/2015 00:12:41 - INFO - Start Flashing
02/012/2015 00:12:41 - INFO - Processing loader.sin
02/012/2015 00:12:41 - INFO - Checking header
02/012/2015 00:12:41 - INFO - Flashing data
02/012/2015 00:12:42 - INFO - Loader : S1_Root_5ca3 - Version : APQ8064_30 / Boot version : S1_Boot_Lagan_1.1_10 / Bootloader status : ROOTABLE
02/012/2015 00:12:42 - INFO - Transfer buffer size : 262144
02/012/2015 00:12:42 - WARN - File simlock.ta is ignored
02/012/2015 00:12:43 - INFO - You must have the according fsc script to flash this device.
02/012/2015 00:12:43 - INFO - Flashing finished.
02/012/2015 00:12:43 - INFO - Please unplug and start your phone
02/012/2015 00:12:43 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
xplorer11 said:
When I use flashmode to install ftf file, it give me error:
Here is the log file:
02/010/2015 00:10:29 - INFO - Flashtool Version 0.9.19.0 built on 29-07-2015 12:00:00
02/010/2015 00:10:29 - INFO - Executing search strategies to find proxy selector
02/010/2015 00:10:29 - INFO - No proxy found for IE. Trying next one
02/010/2015 00:10:30 - INFO - No proxy found for firefox. Trying next one
02/010/2015 00:10:30 - INFO - No proxy found for java. Trying next one
02/010/2015 00:10:30 - INFO - Syncing devices from github
02/010/2015 00:10:31 - INFO - Scanning devices folder for changes.
02/010/2015 00:10:46 - INFO - Changes have been found. Doing a hard reset (removing user modifications).
02/010/2015 00:10:46 - INFO - Pulling changes from github.
02/010/2015 00:10:48 - INFO - Devices sync finished.
02/010/2015 00:10:53 - INFO - Device connected in flash mode
02/011/2015 00:11:08 - INFO - Device disconnected
02/011/2015 00:11:22 - INFO - Selected Bundle for Sony Xperia Z (C6603). FW release : 10.3.1.A.2.67. Customization : Generic ES
02/011/2015 00:11:22 - INFO - Preparing files for flashing
02/012/2015 00:12:25 - INFO - Device connected in flash mode
02/012/2015 00:12:39 - INFO - Please connect your device into flashmode.
02/012/2015 00:12:41 - INFO - Opening device for R/W
02/012/2015 00:12:41 - INFO - Reading device information
02/012/2015 00:12:41 - INFO - Phone ready for flashmode operations.
02/012/2015 00:12:41 - INFO - Opening TA partition 2
02/012/2015 00:12:41 - INFO - Current device : C6603 - CB5A1VJMRN - 1270-5695_R2E - 1269-5309_10.4.1.B.0.101 - GLOBAL-LTE_10.6.A.0.454
02/012/2015 00:12:41 - INFO - Closing TA partition
02/012/2015 00:12:41 - INFO - Start Flashing
02/012/2015 00:12:41 - INFO - Processing loader.sin
02/012/2015 00:12:41 - INFO - Checking header
02/012/2015 00:12:41 - INFO - Flashing data
02/012/2015 00:12:42 - INFO - Loader : S1_Root_5ca3 - Version : APQ8064_30 / Boot version : S1_Boot_Lagan_1.1_10 / Bootloader status : ROOTABLE
02/012/2015 00:12:42 - INFO - Transfer buffer size : 262144
02/012/2015 00:12:42 - WARN - File simlock.ta is ignored
02/012/2015 00:12:43 - INFO - You must have the according fsc script to flash this device.
02/012/2015 00:12:43 - INFO - Flashing finished.
02/012/2015 00:12:43 - INFO - Please unplug and start your phone
02/012/2015 00:12:43 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
Click to expand...
Click to collapse
Do you have unlocked bootloader? IF yes, why didn't you try to flash ROM via fastboot instead?
Try flashing a newer FTF and uncheck TA partition.
Fastboot is beside the point and not a real flash, FTF is a full flash and should always work no matter what.
Sent from my Xperia Z using Tapatalk
thanks for your support
CosmicDan said:
Try flashing a newer FTF and uncheck TA partition.
Fastboot is beside the point and not a real flash, FTF is a full flash and should always work no matter what.
Sent from my Xperia Z using Tapatalk
Click to expand...
Click to collapse
I've tried everything through flashmode but it always gets stuck in usb debuggins and unknown sources error.
What I've found is that my device is locked, I've tried to unlock bootload using code sony provided me but it fails to do so:
fastboot -i 0x0fce oem unlock 0x441733FD90D750CE
...
FAILED (remote: Command did not succeed)
finished. total time: 0.039s
---
So bootloader is locked, is there any way to unlock it? I have sony xperia z c6603.
Probably corrupted bootloader or partition table, possibly from flashing TA. It happens. If that's the case, I think it's dead.
Don't worry about bootloader, one thing at a time - try to get a stock FTF flashed and working then worry about that later.
But the USB Debugging / Unknown Sources is *not* the error, this is irrelevant for flashmode and fastboot, Flashtool always says that. The real error is "You must have the according fsc script to flash this device". Google for that error for more advice. But as I said, you should try a different FTF. It could be a damaged file or incomplete download.
Also make sure you're running the latest Flashtool and installed the flashmode drivers from it.
Sent from my Xperia Z using Tapatalk
---------- Post added at 05:02 PM ---------- Previous post was at 04:57 PM ----------
Wait, are you using Flashtool 0.9.19.0? I just read that lots of people are having this error. Try older Flashtool version.
Sent from my Xperia Z using Tapatalk
Use an older version of flashtool, the newest doesn't support older devices. Use 0.9.18.6 instead
Just said that but anyway...
Seems like a pretty serious bug in Flashtool.
Sent from my Xperia Z using Tapatalk
CosmicDan said:
Just said that but anyway...
Seems like a pretty serious bug in Flashtool.
Sent from my Xperia Z using Tapatalk
Click to expand...
Click to collapse
It's not a bug as such. The file that the latest version complains of not being present has to be created by someone that has a Z.
It states fairly clearly that the Z isn't supported on the Flashtool downloads page.
This release is valid for ZL,Z1,Z2,Z3,Z3c,Z3+/Z4,Z4Tablet,E4,E4G,M2,M4 at the moment. As far as new fsc are added, more phone will be compatible. I need your help for that. I will add a tuto on how to generate / add new fsc. If your phone is not in this list, stick to the previous release (still online)
Click to expand...
Click to collapse
If I was at home, then I'd go ahead and create the fsc file, but I'm not and my Z is there.
If anyone else feels like doing it, then there are basic directions here.
Ah ok, so its just a temporary legacy regression and possibly the fsc will be included in later Flashtool versions.
Sent from my Xperia Z using Tapatalk
CosmicDan said:
Ah ok, so its just a temporary legacy regression and possibly the fsc will be included in later Flashtool versions.
Sent from my Xperia Z using Tapatalk
Click to expand...
Click to collapse
It will be included when someone with a Z creates it and sends it to Androxyde. I'm unable to do this for a few days, so hopefully someone else will do it before then.
Sent from my HTC One M9 using Tapatalk