hello, please friends this is so urgent, i downloaded existenz ultra and super su fix
i installed revoery 4.4.1
booted in cwm recovery, wiped system, data, cache, and then i chose go back to main menu, and it's stuck in recovery, i mean waited and no instructions appeared, just done in the buttom, and the cwm background, so i force stop my sp using off butoon, till 3 vibrations,
connected it in fashmod, every thing goes smooth till fa=lashing data message, but the progress bar is not moving
i tried extracting boot.img from existenz rom, but couldn't make my sp go to fastboot mod
please help me friends, i need my phone, and don't have replacement as am in college
24/047/2014 13:47:00 - INFO - Flashtool Version 0.9.18.3 built on 10-20-2014 08:00:00
24/047/2014 13:47:00 - INFO - Executing search strategies to find proxy selector
24/047/2014 13:47:00 - INFO - No proxy found for IE. Trying next one
24/047/2014 13:47:00 - INFO - Proxy found for firefox
24/047/2014 13:47:00 - INFO - Syncing devices from github
24/047/2014 13:47:00 - INFO - Scanning devices folder for changes.
24/047/2014 13:47:04 - INFO - Pulling changes from github.
24/047/2014 13:47:05 - INFO - Devices sync finished.
24/047/2014 13:47:09 - INFO - Device disconnected
24/047/2014 13:47:10 - INFO - Flash canceled
24/048/2014 13:48:31 - ERROR - This action can only be done in fastboot mode
24/049/2014 13:49:41 - ERROR - This action can only be done in fastboot mode
24/049/2014 13:49:45 - ERROR - This action needs a connected device in ADB mode
24/049/2014 13:49:51 - ERROR - This action can only be done in fastboot mode
24/049/2014 13:49:56 - ERROR - This action can only be done in fastboot mode
24/050/2014 13:50:00 - INFO - Device Status: NOT FOUND
24/050/2014 13:50:02 - INFO - Device Status: NOT FOUND
24/050/2014 13:50:03 - INFO - Device Status: NOT FOUND
24/050/2014 13:50:37 - INFO - Device connected in flash mode
24/050/2014 13:50:44 - ERROR - This action needs a connected device in ADB mode
24/050/2014 13:50:46 - ERROR - This action can only be done in fastboot mode
24/050/2014 13:50:47 - INFO - Device Status: NOT FOUND
24/050/2014 13:50:49 - INFO - Device Status: NOT FOUND
24/050/2014 13:50:55 - ERROR - This action can only be done in fastboot mode
24/051/2014 13:51:16 - INFO - Device disconnected
24/052/2014 13:52:40 - INFO - Selected Bundle for Sony Xperia SP (C5303). FW release : 12.1.A.1.207. Customization : AU
24/052/2014 13:52:40 - INFO - Preparing files for flashing
24/052/2014 13:52:52 - INFO - Please connect your device into flashmode.
24/053/2014 13:53:20 - INFO - Device connected in flash mode
24/053/2014 13:53:20 - INFO - Opening device for R/W
24/053/2014 13:53:20 - INFO - Reading device information
24/053/2014 13:53:20 - INFO - Phone ready for flashmode operations.
24/053/2014 13:53:20 - INFO - Current device : C5303 - YT910BZRF0 - 1271-7710_R2B - 1269-3538_12.1.A.1.207 - GLOBAL-LTE_12.1.A.1.207
24/053/2014 13:53:20 - INFO - Start Flashing
24/053/2014 13:53:20 - INFO - Processing loader.sin
24/053/2014 13:53:20 - INFO - Checking header
24/053/2014 13:53:20 - INFO - Flashing data
24/053/2014 13:53:20 - INFO - Processing of loader.sin finished.
24/053/2014 13:53:24 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B023 / Bootloader status : NOT_ROOTABLE
24/053/2014 13:53:25 - INFO - Processing partition-image.sin
24/053/2014 13:53:25 - INFO - Checking header
24/053/2014 13:53:25 - INFO - Flashing data
24/053/2014 13:53:28 - INFO - Processing of partition-image.sin finished.
24/053/2014 13:53:28 - INFO - No bootdelivery to send
24/053/2014 13:53:28 - INFO - Processing kernel.sin
24/053/2014 13:53:28 - INFO - Checking header
24/053/2014 13:53:28 - INFO - Flashing data
24/053/2014 13:53:34 - INFO - Processing of kernel.sin finished.
24/053/2014 13:53:34 - INFO - Processing fotakernel.sin
24/053/2014 13:53:34 - INFO - Checking header
24/053/2014 13:53:34 - INFO - Flashing data
24/053/2014 13:53:38 - INFO - Processing of fotakernel.sin finished.
24/053/2014 13:53:38 - INFO - Processing amss_fs_2.sin
24/053/2014 13:53:38 - INFO - Checking header
24/053/2014 13:53:38 - INFO - Flashing data
24/053/2014 13:53:39 - INFO - Processing of amss_fs_2.sin finished.
24/053/2014 13:53:39 - INFO - Processing amss_fs_1.sin
24/053/2014 13:53:39 - INFO - Checking header
24/053/2014 13:53:39 - INFO - Flashing data
24/053/2014 13:53:41 - INFO - Processing of amss_fs_1.sin finished.
24/053/2014 13:53:41 - INFO - Processing amss_fsg.sin
24/053/2014 13:53:41 - INFO - Checking header
24/053/2014 13:53:41 - INFO - Flashing data
24/053/2014 13:53:43 - INFO - Processing of amss_fsg.sin finished.
24/053/2014 13:53:43 - INFO - Processing apps_log.sin
24/053/2014 13:53:43 - INFO - Checking header
24/053/2014 13:53:43 - INFO - Flashing data
24/053/2014 13:53:44 - INFO - Processing of apps_log.sin finished.
24/053/2014 13:53:44 - INFO - Processing cache.sin
24/053/2014 13:53:44 - INFO - Checking header
24/053/2014 13:53:44 - INFO - Flashing data
24/053/2014 13:53:49 - INFO - Processing of cache.sin finished.
24/053/2014 13:53:49 - INFO - Processing system.sin
24/053/2014 13:53:49 - INFO - Checking header
24/053/2014 13:53:50 - INFO - Flashing data
24/058/2014 13:58:42 - INFO - Processing of system.sin finished.
24/058/2014 13:58:42 - INFO - Processing userdata.sin
24/058/2014 13:58:42 - INFO - Checking header
24/058/2014 13:58:43 - INFO - Flashing data
am using win7 please guys help me, installed all drivers following technosparks instructions, every thing,
I don't see any error in the logs? Could you elaborate on what happened?
TechnoSparks said:
I don't see any error in the logs? Could you elaborate on what happened?
Click to expand...
Click to collapse
hello again, my phone is alive again, i won't mess with it till my exams are over.
here is what happened
i kept staring at the flashtool log, and suddenly i got flash complete message bla bla bla
i booted my phone and it's working again, but took more than usual to boot, about 5 minuts, last time i flashed a rom it took just 2 minuts or less..
i think that my flashtool has a glitch, because it was flashing, but with no green progress bar ..., i feel sorry for y phone i disconnected it about 5 times during flashing, i wonder what are the consequences ? please techno sparks if you have any comment about this and about what happened, share it with me, i want to learn and add something to my dictionary
also i have few other questions if you don't mind please answer them :
1) is what happened to me during the CWR normal ? common bug ? or am the first unlucky one to get this error .. ? i mean every thing was going smooth, till i chose the go back to main menu, the menu disappears, and only the log on the bottom is still there, showing done as last command
2) what do you recommend as a recovery to use in the future ? i thought to use CWR beceause most rom tutorials recommend it... also i never used or explored the other recoveries
3) why does my phone after it was bricked( shows sony logo when i turn it on, and stucks there for ever) connects to usb in flashmod automatically when i connect it to pc, even if i press the up vol button to connect it in fastboot mod
4) why won't my phone go to fastboot mod( as you've seen in the log in my first post)
5) all i wanted was to use the boot.img(kernel isn't it ?) from existenz rom( as i thought it has recovery preinstalled on it) and skip things a bit( installing original ftf, root, install recovery ...) and boot directly to revory and flash existenz...
6)as a thought not a question, i will try to answer the 5th question, ===> fastboot is only available to devices with ubl ?? but if the phone gets bricked similar to my casr, and even though it has ubl, , i think it won't boot to fastboot beceause all system and data are deleted ? this means the phone has no kernel or anything inside to boot into.
sorry if this has been too long or has very stupid questions, but im still getting into android world and the way is still too long to get to your level, and i want to get there asap
Gamer4Life said:
hello again, my phone is alive again, i won't mess with it till my exams are over.
here is what happened
i kept staring at the flashtool log, and suddenly i got flash complete message bla bla bla
i booted my phone and it's working again, but took more than usual to boot, about 5 minuts, last time i flashed a rom it took just 2 minuts or less..
i think that my flashtool has a glitch, because it was flashing, but with no green progress bar ..., i feel sorry for y phone i disconnected it about 5 times during flashing, i wonder what are the consequences ? please techno sparks if you have any comment about this and about what happened, share it with me, i want to learn and add something to my dictionary
also i have few other questions if you don't mind please answer them :
1) is what happened to me during the CWR normal ? common bug ? or am the first unlucky one to get this error .. ? i mean every thing was going smooth, till i chose the go back to main menu, the menu disappears, and only the log on the bottom is still there, showing done as last command
2) what do you recommend as a recovery to use in the future ? i thought to use CWR beceause most rom tutorials recommend it... also i never used or explored the other recoveries
3) why does my phone after it was bricked( shows sony logo when i turn it on, and stucks there for ever) connects to usb in flashmod automatically when i connect it to pc, even if i press the up vol button to connect it in fastboot mod
4) why won't my phone go to fastboot mod( as you've seen in the log in my first post)
5) all i wanted was to use the boot.img(kernel isn't it ?) from existenz rom( as i thought it has recovery preinstalled on it) and skip things a bit( installing original ftf, root, install recovery ...) and boot directly to revory and flash existenz...
6)as a thought not a question, i will try to answer the 5th question, ===> fastboot is only available to devices with ubl ?? but if the phone gets bricked similar to my casr, and even though it has ubl, , i think it won't boot to fastboot beceause all system and data are deleted ? this means the phone has no kernel or anything inside to boot into.
sorry if this has been too long or has very stupid questions, but im still getting into android world and the way is still too long to get to your level, and i want to get there asap
Click to expand...
Click to collapse
First boot after flashing the stock ROM always takes time with any phone. You should have already knew that.
Do not attempt to pull out your phone during flashing process. This could give you a hard-brick!! If you want to know what happened, the phone literally stops receiving data from the computer, and whatever the thing that was in the flashing process, will become incomplete on your phone. Say, flashtool is flashing system.sin and then you disconnected it, this will cause your phone to have a faulty /system partition.
CWM shouldn't act that way. I recommend reinstalling the recovery thoroughly
I prefer CWM
The phone was unable to find the correct boot flag OR unable to find the ROM's necessary init (startup) files. Flashmode and fastboot mode however are hardware exclusive. But I don't know what will happen if we wipe /boot partition. However I strongly suggest don't do that.
Now, to answer your question accurately, it seemed your phone was still on the bootloader, that is why your phone automatically connects as flashmode. The boot sequence are POWER > Bootloader > ROM.
No you must install the original ftf as mentioned in the thread. If you want shortcut you may use MrSteve555's guide on how to make a stock ROM flashable zip here: http://forum.xda-developers.com/showpost.php?p=54351969&postcount=2 .
boot.img is an image for the /boot partition in the rootfs (root of the file system).
Fastboot mode is available for all android devices! It doesn't matter if it is UBL or LBL, fastboot mode is always there by default unless altered by any third-party.
To boot into fastboot mode, you'll need to hold volume up when requested in the Flashtool. YOU MUST FIRST turn off your phone.
I don't know where fastboot resides, I am sorry. But I am sure fastboot is not in the /system nor /data. Kernel is a layer that enables software to interact with hardware, thus, what you have mentioned is correct.
No problem, I always be glad to answer any questions when I know the answers
thanks again, still have few other questions if you don't mind :
1) my was my phone stuck in the bootloader? i thought that turning it off from the back button would make it turn off completely, then it would boot all over again
2) i tried connecting my phone whilst holding the volume up button, but it won't connect in fastboot mod
3)when i tried flashing the boot.img, i thought that it's the kernel
in another thread in this forum you posted instructions to another newbie fella, telling him to flash William kernel and as it has preinstalled recoveries, then just boot into one and flash a rom directly, saving the time of flashing stock ftf, rooting... etc
Gamer4Life said:
thanks again, still have few other questions if you don't mind :
1) my was my phone stuck in the bootloader? i thought that turning it off from the back button would make it turn off completely, then it would boot all over again
2) i tried connecting my phone whilst holding the volume up button, but it won't connect in fastboot mod
3)when i tried flashing the boot.img, i thought that it's the kernel
in another thread in this forum you posted instructions to another newbie fella, telling him to flash William kernel and as it has preinstalled recoveries, then just boot into one and flash a rom directly, saving the time of flashing stock ftf, rooting... etc
Click to expand...
Click to collapse
The button is for a forced reset. If you have problems with your boot partition, your phone will never boot, regardless of how many times you have use the hardware reset button lol
That is weird. Could you confirm that you have done it correctly?
boot.img is a /boot partition img file. Kernel files resides in there.
Sorry for the extreme lateness. I am now no longer have hours of free time lol
can someone tell me how to fix it
accidently i wipe my system and lose my recovery im on locked bootlooader.My phone wont charge and got bootloop, i cant enter flashmode cuz dont have enough battery (i think) when i charge my phone its just make the red led on and stuck on sony logo.
1. Prepare FlashTool for flashing the firmware.
a. If you have enough juice left(about 20%), flash the full firmware.
b. If you are running on sparks, flash only the kernel.
2. Connect your phone to your PC via USB.
3. Open your back cover and while pressing the volume down button, press that yellow button using a pencil till you see a green LED.
4. Flashtool starts flashing whatever you chose earlier.
If you flashed only the kernel, charge your phone completely, and then flash the full firmware.
Hope this solves it.
Hit a Thanks if it helped.
Thanks, I can get in flashmode but got this
14/032/2015 21:32:28 - INFO - Processing cache.sin
14/032/2015 21:32:28 - INFO - Checking header
14/032/2015 21:32:29 - INFO - Flashing data
14/032/2015 21:32:31 - INFO - Processing of cache.sin finished.
14/032/2015 21:32:31 - INFO - Processing system.sin
14/032/2015 21:32:31 - INFO - Checking header
14/032/2015 21:32:31 - INFO - Flashing data
14/036/2015 21:36:04 - ERROR - Processing of system.sin finished with errors.
14/036/2015 21:36:04 - INFO - Ending flash session
14/036/2015 21:36:04 - ERROR - 31 : A device attached to the system is not functioning.
14/036/2015 21:36:04 - ERROR - Error flashing. Aborted
14/036/2015 21:36:05 - INFO - Device disconnected
14/036/2015 21:36:06 - INFO - Device connected with USB debugging off
14/036/2015 21:36:06 - INFO - For 2011 devices line, be sure you are not in MTP mode
14/036/2015 21:36:10 - INFO - Device disconnected
i got this when i flashing the firmware what it means??
Will you please elaborate on how you 'accidentally' managed to wipe your system partition?[emoji6]
Please flash again after changing the 'Log level' to 'debug' in the help menu and post the log.[emoji4]
So, I just bought a Z3C, I had a Z1 before, it was rooted with locked bootloader, so I understand some of the stuff.
Anyway, I applied root, installed the Dual Recovery, did a backup of my DRM keys, and everything went alright, then there was this update, which I remembered that, on the Z1, I would lose root and Dual Recovery after it was done, but since I already knew they worked, I thought about installing it (Can't remember which version it was, but I think it was a KitKat version).
Anyway, the phone rebooted, it goes "Sony", then the official recovery android logo with the error message in RED. I did notice though that there seemed to be another screen an instant before the error showed up.
I can run fastboot, tried "reboot-bootloader, it gave me a finished, but seems like it did nothing, as it's still recognized by fastboot. If I try to run normally, it gives me the update error. Is there a way to fix this? There is nothing on the phone, so wipe is not a problem (Unless it may affect the SD, which would be bad).
Download an ftf for your phone. Flash it via flashtool using flash mode (flashception)
Try 23.2.A.1.62 HK ftf from the list of ftfs in xda.
Sent from my D5833 using XDA Free mobile app
Tried, but no success. Tried 2 times, below is the log. One thing I found out is that, this bootloop is based on a 1 minute Flash Mode (message: Device connected in flash mode) and 30 seconds of Sony logo - Update Failed (message: Device Disconnected), and seems like I can't stop it, like fully turning it off by holding the button next to the SIM card slot until the 3 vibes, it always disconnects and tries to boot, looping every time it's connected.
It basically disconnects while the files are prepared, but when it finishes, if the phone is disconnected, it will give a "waiting for phone popup", then the phone returns to flashmode, and then there are the errors below.
As an extra piece of the behaviour, not sure if it helps, but while flashmode seems to be tied to normal boot, fastboot works alright, no reboot, constantly connected.
18/054/2015 16:54:55 - INFO - Device connected in flash mode
18/055/2015 16:55:03 - INFO - Selected Bundle for Sony Xperia Z3 Compact (D5833). FW release : 23.2.A.1.62 R8C. Customization : CUSTOMIZED HK
18/055/2015 16:55:03 - INFO - Preparing files for flashing
18/055/2015 16:55:56 - INFO - Device disconnected
18/056/2015 16:56:33 - INFO - Device connected in flash mode
18/057/2015 16:57:34 - INFO - Device disconnected
18/058/2015 16:58:03 - INFO - Device connected in flash mode
18/059/2015 16:59:04 - INFO - Device disconnected
18/059/2015 16:59:05 - INFO - Please connect your device into flashmode.
18/059/2015 16:59:33 - INFO - Device connected in flash mode
18/059/2015 16:59:34 - INFO - Opening device for R/W
18/059/2015 16:59:34 - INFO - Reading device information
18/059/2015 16:59:34 - INFO - Unable to read from phone after having opened it.
18/059/2015 16:59:34 - INFO - trying to continue anyway
18/059/2015 16:59:34 - INFO - Start Flashing
18/059/2015 16:59:34 - INFO - Processing loader.sin
18/059/2015 16:59:34 - INFO - Checking header
18/059/2015 16:59:34 - ERROR - Processing of loader.sin finished with errors.
18/059/2015 16:59:34 - INFO - Ending flash session
18/059/2015 16:59:34 - ERROR - Error in processHeader : 1 : Incorrect function.
18/059/2015 16:59:34 - ERROR - Error flashing. Aborted
18/059/2015 16:59:34 - INFO - Device connected in flash mode
18/059/2015 16:59:55 - INFO - Device disconnected
18/000/2015 17:00:31 - INFO - Device connected in flash mode
18/000/2015 17:00:49 - INFO - Selected Bundle for Sony Xperia Z3 Compact (D5833). FW release : 23.2.A.1.62 R8C. Customization : CUSTOMIZED HK
18/000/2015 17:00:49 - INFO - Preparing files for flashing
18/001/2015 17:01:32 - INFO - Device disconnected
18/001/2015 17:01:34 - INFO - Device connected in flash mode
18/002/2015 17:02:06 - INFO - Please connect your device into flashmode.
18/002/2015 17:02:07 - INFO - Opening device for R/W
18/002/2015 17:02:07 - INFO - Reading device information
18/002/2015 17:02:07 - INFO - Unable to read from phone after having opened it.
18/002/2015 17:02:07 - INFO - trying to continue anyway
18/002/2015 17:02:07 - INFO - Start Flashing
18/002/2015 17:02:07 - INFO - Processing loader.sin
18/002/2015 17:02:07 - INFO - Checking header
18/002/2015 17:02:07 - ERROR - Processing of loader.sin finished with errors.
18/002/2015 17:02:07 - INFO - Ending flash session
18/002/2015 17:02:07 - ERROR - Error in processHeader : 1 : Incorrect function.
18/002/2015 17:02:07 - ERROR - Error flashing. Aborted
18/002/2015 17:02:08 - INFO - Device connected in flash mode
18/002/2015 17:02:34 - INFO - Device disconnected
Click to expand...
Click to collapse
So, I sent it back to the store to see if they could fix it, and well, they did, not sure what authorized stores have, but anyway, they fixed the bootloop, all data was wiped (It's like new), and they updated it to 5.0.2, so now I need to downgrade and do the whole job again.
hello. im just wiped all my system in phone, when try on phone can see only logo and then black sreen
I read need flash phone
ok i download flashtool then
C6603_10.1.A.1.434_UK unbranded
Try flash and get error
09/009/2016 18:09:14 - INFO - Selected C6603 / 10.1.A.1.434 / UK unbranded
09/009/2016 18:09:14 - INFO - Preparing files for flashing
09/009/2016 18:09:38 - INFO - Device disconnected
09/009/2016 18:09:41 - INFO - Please connect your device into flashmode.
09/010/2016 18:10:30 - INFO - Device connected in flash mode
09/010/2016 18:10:31 - INFO - Opening device for R/W
09/010/2016 18:10:31 - INFO - Reading device information
09/010/2016 18:10:31 - INFO - Phone ready for flashmode operations.
09/010/2016 18:10:32 - INFO - Start Flashing
09/010/2016 18:10:32 - INFO - Processing loader
09/010/2016 18:10:32 - INFO - Checking header
09/010/2016 18:10:32 - INFO - Ending flash session
09/010/2016 18:10:32 - ERROR - Error in processHeader : 31 : A device attached to the system is not functioning.
09/010/2016 18:10:32 - ERROR - Error flashing. Aborted
Maybe someone can help?
+ i always get different erros or just stuck...
Lets go together through this, lets take some steps to determine the problem.
1. Check the firmware! Make sure you are installing the right firmware and the download is not corrupted.
2. Check the DRIVER!!! Always important to uninstall the driver restart your pc, and then install the official fastboot driver from Sony Developers site.
3. Check your cable! Try with another cable, yours might be faulty
4.Check your timing, make sure you plug the phone into flashmode just the right second, you dont have much time, try several times until you get it right.
Quote me on this thread or PM me because I might not read it. Good luck!
Hello it seems that I can't boot my phone in to Flash Mode. I looked up into forums on how to boot X8 to Flash Mode and so I followed it, Hold the back button-connect the usb cable-wait for the green led. It did work, but after some time, the green led will disappear and it will try to boot on the OS.
I need to flash stock rom on it because I soft-bricked my device. The Flashtool recognizes the phone in Flash Mode but when I start flashing the rom, it gives me the instuctions to place the device on Flash Mode, but then when the green LED dissapears, the instruction windows too, and flashtool starts to flash but then failed with an error, here is the output log from Flashtool..
HTML:
16/001/2018 09:01:54 - INFO - <- This level is successfully initialized
16/001/2018 09:01:54 - INFO - Flashtool Version 0.6.9.1 built on 2012-04-09 19:22:19
16/001/2018 09:01:54 - INFO - You can drag and drop ftf files here to start flashing them
16/001/2018 09:01:58 - INFO - Device disconnected
16/002/2018 09:02:09 - INFO - Device connected in flash mode
16/002/2018 09:02:17 - INFO - Selected Sony_Ericsson_Xperia_X8_E15i_3836_2.1.1.A.0.6_Customized_India.ftf
16/002/2018 09:02:17 - INFO - Preparing files for flashing
16/002/2018 09:02:19 - INFO - Please connect your device into flashmode.
16/002/2018 09:02:19 - INFO - Opening device for R/W
16/002/2018 09:02:19 - INFO - Reading device information
16/002/2018 09:02:23 - INFO - Start Flashing
16/002/2018 09:02:23 - INFO - Ending flash session
16/002/2018 09:02:23 - ERROR -
16/002/2018 09:02:23 - ERROR - Error flashing. Aborted
16/002/2018 09:02:24 - INFO - Device disconnected
16/002/2018 09:02:31 - INFO - Device connected with USB debugging off
16/002/2018 09:02:31 - INFO - For 2011 devices line, be sure you are not in MTP mode
I need to fix this phone badly, for I don't have any backup phone except for this one.