Related
Hello. I'm kinda new to all this android scene sooo have few questions. Updated mine XS via Flashtool, but stuck on rooting it .
When i access fastboot toolbox, and under "Select kernel to flash" select "recovery-nozomi.img" i get an error. Here's the log..
Code:
22/023/2012 03:23:44 - INFO - <- This level is successfully initialized
22/023/2012 03:23:44 - INFO - Flashtool Version 0.8.6.0 built on 2012-06-13 08:08:54
22/023/2012 03:23:44 - INFO - You can drag and drop ftf files here to start flashing them
22/023/2012 03:23:49 - INFO - Device disconnected
22/024/2012 03:24:10 - INFO - Device connected in fastboot mode
22/024/2012 03:24:17 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
22/024/2012 03:24:17 - INFO - Device Status: FASTBOOT mode
22/024/2012 03:24:19 - INFO - Device Status: FASTBOOT mode
22/024/2012 03:24:24 - INFO - Device Status: FASTBOOT mode
22/024/2012 03:24:25 - INFO - Fetching connected device info
22/024/2012 03:24:25 - INFO - Connected device info: [ PSDN:CB511WRU0U&ZLP ]
22/024/2012 03:24:28 - INFO - Fetching fastboot version info from connected device
22/024/2012 03:24:28 - INFO - FASTBOOT version info: [ version: 0.5 ]
22/024/2012 03:24:35 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\recovery-nozomi.img
22/024/2012 03:24:35 - INFO - Flashing selected kernel
22/024/2012 03:24:35 - INFO - sending 'boot' (5414 KB)...
22/024/2012 03:24:35 - INFO - FAILED (remote: The Device must be rooted first)
22/024/2012 03:24:35 - INFO - finished. total time: 0.009s
22/024/2012 03:24:35 - INFO - FASTBOOT Output:
sending 'boot' (5414 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.009s
22/024/2012 03:24:35 - INFO - Please check the log before rebooting into system
What i'm doing wrong?
Also i found prerooted ICS for my XS, but it's .img format. When i was updating i updated with ".ftf" file . How do i install that ".img" ? (via fastboot toolbox by selecting "select system to Flash" ??)
Thank you
Follow the instructions in this thread:-
http://forum.xda-developers.com/showthread.php?t=1723610
I did the ftf route then manually rooted.
Good Luck.
@op, Is your bootloader unlocked?
Sent from my LT26i using XDA
I think I'll try and help some more here, as sometimes the devs assume everyone is as sharp as they are!
This is the idiots guide, forgive me if I'm stating the obvious!
Ok, make sure you have the latest version of Flashtool installed, 0.8.6.0 is the latest I believe.
Download and copy the 6.1.a.0.452 ftf file to the firmwares folder of wherever you installed flashtool, mine is c:/Flashtool/firmwares.
Now, switch off the phone... Wait 20 seconds or so.
Whilst pressing the volume down button, connect the usb.
You should, if your drivers are installed correctly see device connected in flash mode appear in the window. The phones LED will be green.
Click the lightining flash button.
Select Flash Mode.
You will see the file listed in the 'select a firmware' window; select it.
If you do not wish to wipe data, then unselect the wipe data checkbox, I suggest you do wipe, click OK.
Flashtool now preps itself and some seconds later flashing should commence.
I've been re-faslhing mine as I write this, so I know it works.
Now, rooting... You will need an unlocked bootloader, assuming you have, if you have not, then check out the link:
http://forum.xda-developers.com/showthread.php?t=1527159
You may or may not be able to unlock the bootloader, depends who the provider/supplier was. Mine was from phones4u and was a generic unbranded unit.
Once, you have unlocked the bootloader then you can procede to rooting the phone.
I am assuming here that you have downloaded the following files:
CWM-SuperSU-v0.92.zip
kernel.rar
recovery-nozomi.img
You will also have installed Fastboot, and added it to your windows paths.
First things first, browse your Xperia from Filebrowser, and copy the file "CWM-SuperSU-v0.92.zip" to the root folder.
In Windows, browse to the folder containing the .img file and the extracted kernel.sin file. Launch a command prompt from that folder, do this by holding the shft key down when you right mouse and select 'open command window here'.
Now, if you have done your paths correctly etc, type fastboot, and you will get a list of the command options, this is just to prove your paths!
Type 'fastboot flash boot recovery-nozami.img'
You will get waiting for device...
Phone off, wait 20 seconds or so...
holding volume UP key, connect usb, device will flash.
Now, unplug the usb and power up the phone, you will see a menu, using the vol keys, up and down, 'select install zip from sdcard' using the camera button to select.
then select 'choose zip file from SD card'
You should see the 'CWM-SuperSU-v0.92.zip' we copied earlier at the bottom of the list, select it.
It should now have a little list with no's and a yes, so up/dpwn to the yes with the option to install and select.
That should install correctly, mine just has, and we are almost there.
In little menu at the top, select 'go back' and you will see an option to 'reboot system', do not select it yet!
Go back to your windows prompt, and type
Type 'fastboot flash boot kernel.sin'
Now back to the phone, and insert the usb cable... press the camera button and immediately press volume up, LED will turn blue. Now, this is where it may just be my PC, but what I need to do now, is hit return on the pc and it says Waiting for device, I quickly unplug the usb, and plug it back in, and it flashes the kernel.sin file.
The trick is in the 'reboot system' and getting the vol up timing right to enter the fastboot mode.
That's the way I've done it, and it all works perfectly. Hope it helps you.
first you need to unlock bootloader which MAY void your warranty, than you have to instal custom KERNEL, doomlord have wonderful kernel.
Than over kernel recovery flash pre rooted image.
I was not aware that the ICS ftf was not an official sony release; if it is signed by Sony, you do not need an unlocked bootloader.
Custom Kernel for ICS??? Since last night?
marjohn56 said:
I was not aware that the ICS ftf was not an official sony release; if it is signed by Sony, you do not need an unlocked bootloader.
Custom Kernel for ICS??? Since last night?
Click to expand...
Click to collapse
What you are doing above is trying to root, which for now needs a unlocked bootloader to do. The official firmware itself is signed so it's not an issue, but flashing recovery and switching out kernels is, and won't be allowed on a locked bootloader.
@electrash:
Doom hasn't built a kernel for ICS yet, right? It's not a good idea to flash a GB kernel over ICS, its a good way to break things :/.
Sent from my LT26i using XDA
Which his exactly what I wrote in my instructions; as I said, he can blow ICS, he may or may not be able to root.
I'm not trying to do anything... I've already done it.
Sent from my LT26i using Tapatalk 2
marjohn56 said:
Which his exactly what I wrote in my instructions; as I said, he can blow ICS, he may or may not be able to root.
I'm not trying to do anything... I've already done it.
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
Haha, thought you were the op asking that, sorry
*shuffles out of thread*
Sent from my LT26i using XDA
marjohn56, excellent instructions, thank you! As far as I saw this one is the only one that describes the process of flashing SU inside recovery. Thanks a lot!
The only thing I can add is that you may turn off your phone once SuperSU was installed. The phone will just not power on the actual system until kernel.sin will be flashed, it will be just booted to recovery every time. So once phone was turned off, just hold the volume up button and plug in the USB cable, then flash kernel.sin as described. The process of flashing kernel.sin is the same as flashing nozomi-recovery, from fastboot point of view. What we're doing is just putting recovery image to root the device and then putting kernel image back to work normally with the system.
Correct me if I'm wrong...
Hi,
I've been using CM7.2 with fxp 119 for some time and today tried an upgrade to fxp125.
Used flashtool to create a bundle with the kernel.sin that came in the zip file.
Flashed to x10.
Booted into cwm and selected install cm7.2 zip from sd card. All ok so far.
But when it rebooted it got stuck at the fxp boot screen, left it for about 30 mins and still nothing. So I pulled the battery and tried to boot it again, still nothing (stuck at fxp boot screen).
I tried wiping everything and re-installing cm7.2 but then it came up with an error (script aborted: assert failed: getprop) which I think means I deleted too much.
My next thought was to re-flash the kernel but now the phone won't boot into flash mode, holding the back button does nothing and it carries on into full phone mode then gets stuck at boot screen.
I tried varying combinations of buttons and try to do it quickly in flash mode before it jumps back to normal mode (which has worked long enough to flash a new kernel via flashtool) but it won't stay in flash mode long enough to get PC companion to repair it.
Any ideas on how to get it back up and running again on any rom?
from what i can understand is you CAN flash but its failing on pccompanion ?
so do you think you'll be able to flash a full rom trough flashtool ?
like this one for example
http://forum.xda-developers.com/showthread.php?t=1698204
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!FT 0.8 is mandatory to flash this bundle!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Yeah for some reason after a lot of attempts it did a couple of times. I had to preload Flashtool then held the back button whilst putting in the battery and plugging the USB at the same time. However it doesn't seem to do even do that any more.
If I plug it into a mains charger it tries to boot but stops at the bootscreen. If I try to plug it into the laptop on normal mode it tries does the same, if I plug it in whilst holding the back button it just tries to boot as normal then freezes at the bootscreen.
It just won't boot into flash mode at all any more.
ive helped someone before with about the same problem .
and at the end it turned out to be something silly .
so to make sure could you do the following steps.
1-Flashtool (select what to flash) then it will ask you to unplug, turn off phone etc.
2-unplug
3-take out battery
4-Replug
5-Hold back button and keep holding it
6-insert battery as your holding back button.
try flashing something you know that works / worked before . or the full rom linked i gave you.
the reason i ask you to do this is, if you cant flash or enter recovery what left right ?
Yep, am doing as you describe with a rom I know has worked before, but no matter how long I hold the back button it still starts to try to fully boot.
I've got the newest Flashtool but can't get that full ftf you linked, that file site doesn't seem to work for me, hasn't for months, just says it start downloading but never does.
The message from Flashtool (sounds serious):-
01/049/2012 19:49:34 - INFO - Selected X10_X10_X10.ftf
01/049/2012 19:49:34 - INFO - Preparing files for flashing
01/049/2012 19:49:34 - INFO - Please connect your device into flashmode.
01/049/2012 19:49:46 - INFO - Device connected in flash mode
01/049/2012 19:49:47 - INFO - Opening device for R/W
01/049/2012 19:49:47 - INFO - Reading device information
01/049/2012 19:49:47 - INFO - Phone ready for flashmode operations.
01/049/2012 19:49:47 - INFO - Start Flashing
01/049/2012 19:49:47 - INFO - Flashing loader
01/049/2012 19:49:47 - INFO - Ending flash session
01/049/2012 19:49:47 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
01/049/2012 19:49:47 - ERROR - Error flashing. Aborted
01/049/2012 19:49:47 - INFO - Device connected in flash mode
01/049/2012 19:49:48 - INFO - Device disconnected
01/049/2012 19:49:50 - INFO - Device connected in flash mode
ok next step is to try SEUS
instead of pc companinon.
http://sony-ericsson-update-service.en.uptodown.com/
get back to stock if possible and try again.
easy pesy
just revert back to stock 2.3.3 rom
open seus->support->update phone->in red color repair phone would be written in the window PRESS IT->wait then select your phone from the list....->it says take battery out for 5 secs->press back button and keep pressing it then connect the usb cable.....->voila it starts downloading stock rom from internet and then would update....
took 25mins with me
p.s till the process of selecting your phone you dont need to connectit just swtich off your phone.....
when I google it it seems to always point me in the direction of bootloader problems .
ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ER R_DYNAMIC="SIN header verification failed"
'''''I tried to figure out what's causing this and I end up with the "locked bootloader solution". I tried the instructions read here: http://unlockbootloader.sonymobile.com/instructions but when I typed ##7378423## no service menu was available...
'''''
answers that helped solve related!
If you didn't already have your bootloader unlocked and tools in place to reload the Android operating system (ie, ROMs or disk images), I strongly suspected you are completely screwed.
You can install an OS from scratch on your phone, but you need a specialized environment and tools to do so and those are often proprietary and/or secret. It is far easier to load a disk image (ROM) than do a base install. Either way, part of the process is an unlocked bootloader so that you can boot into an environment/tool instead of the existing OS. If you don't have a way to boot into something besides the installed system and have pooched that system - generally the only way you as a consumer have available to hack the bootloader - then you're up the creek. – Logos Apr 6 at 12:34
so basicly there saying if you did not unlock bootloader and a way of booting OTHER then the system itself ... you bricked it ..
if you cant flash
cant use recovery
whats left ?
Cheers for the comments about SEUS. However, before I had a chance to read them I had already read on another forum about someone using Wotan to repair a different model of Xperia that was in a similar state to mine. So I paid the fee and the thing worked.
It makes think it was something more to do with my laptop environment than the phone. Because the Wotan client came with it's own driver, which my device loaded and used when I connected it holding the back button, this seemed to make the phone stay in flash mode when connected.
From this experience I don't think holding the back button puts an X10 into flash mode, it merely asks the host 'can I be in flash mode?' and either the host says yes or no.
Awsome to hear you getting it up and running
Mind me asking if you installed flashtool drivers?
Sent from my x10 using xda premium
I woke up this morning, my Xperia U is hunging up, Radio Mode On.. So i unplug my headset.. But there's still a sound.. A sound like shhhhhh.. so what i did i remove the battery and turn it ON.. and it SONY loading with XPERIA, and it shutdown down or close i guess, and it turned on again and again.. so i'm worrying what happen on my phone...
So what i did is open the flashtool.. Im trying to Fastboot it but everytime a Press UP (Volume) and plug the USB to Computer
Info shows like this:
INFO: Drivers need to be installed for connected device
INFO: You can find them in the Driver folder of Flashtool
So i don't know what does it mean..
My 2nd try.. I flash it. i follow the procedures on how to flash.. then it goes well.
So im done flashing, i saw the Log, it says
23/000/2013 10:00:16 - INFO - Flashing finished.
23/000/2013 10:00:16 - INFO - Please unplug and start your phone
23/000/2013 10:00:16 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
23/000/2013 10:00:16 - INFO - Device connected in flash mode
So i guess everything is alright... when i turn it on... it brings back again.. Loading and Loading again and again..
I don't know what to do anymore, i keep on flashing all the time. I can't check my debugging because of it,,
I already fastboot my xperia with different ftf.. i got help from other forums because my phone is Rooted before, so i decided to bring it back to its original interface and state...
Some say the probable problem will be in memory... Please i need ur help...
Sorry for my grammar.
Which ftf did you flash??????
Blackmantra said:
I woke up this morning, my Xperia U is hunging up, Radio Mode On.. So i unplug my headset.. But there's still a sound.. A sound like shhhhhh.. so what i did i remove the battery and turn it ON.. and it SONY loading with XPERIA, and it shutdown down or close i guess, and it turned on again and again.. so i'm worrying what happen on my phone...
So what i did is open the flashtool.. Im trying to Fastboot it but everytime a Press UP (Volume) and plug the USB to Computer
Info shows like this:
INFO: Drivers need to be installed for connected device
INFO: You can find them in the Driver folder of Flashtool
So i don't know what does it mean..
My 2nd try.. I flash it. i follow the procedures on how to flash.. then it goes well.
So im done flashing, i saw the Log, it says
23/000/2013 10:00:16 - INFO - Flashing finished.
23/000/2013 10:00:16 - INFO - Please unplug and start your phone
23/000/2013 10:00:16 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
23/000/2013 10:00:16 - INFO - Device connected in flash mode
So i guess everything is alright... when i turn it on... it brings back again.. Loading and Loading again and again..
I don't know what to do anymore, i keep on flashing all the time. I can't check my debugging because of it,,
I already fastboot my xperia with different ftf.. i got help from other forums because my phone is Rooted before, so i decided to bring it back to its original interface and state...
Some say the probable problem will be in memory... Please i need ur help...
Sorry for my grammar.
Click to expand...
Click to collapse
Repair your phone with SUS, hopefully it will be back to its former stock glory.
SUS download page: http://www.sonymobile.com/gb/tools/update-service/
@[email protected] said:
Which ftf did you flash??????
Click to expand...
Click to collapse
I don't know if i answer you right but here's my FTF
ST25i firmware (France)
On my Firmware Folder: X10_V1_BLRelock.ftf
Some say it's Bootloop
Blackmantra said:
I don't know if i answer you right but here's my FTF
ST25i firmware (France)
On my Firmware Folder: X10_V1_BLRelock.ftf
Click to expand...
Click to collapse
Just try repairing it through PCC or sus..... As said by @up
Sent from my Xperia Sola using xda app-developers app
@[email protected] said:
Just try repairing it through PCC or sus..... As said by @up
Sent from my Xperia Sola using xda app-developers app
Click to expand...
Click to collapse
OK i will try with SUS... what is PCC?
@[email protected] said:
Just try repairing it through PCC or sus..... As said by @up
Sent from my Xperia Sola using xda app-developers app
Click to expand...
Click to collapse
Boss ang lumabas nung na SUS ko eh The Phone Contains modified software that cannot be updated
please i need help
Blackmantra said:
please i need help
Click to expand...
Click to collapse
First flash latest firmware using flashtool, then use SUS to repair your phone.
Latest firmware: http://forum.xda-developers.com/showthread.php?t=2028139
that should do it.
Mufrad said:
First flash latest firmware using flashtool, then use SUS to repair your phone.
Latest firmware: http://forum.xda-developers.com/showthread.php?t=2028139
that should do it.
Click to expand...
Click to collapse
Thank you sir... I will try it now.. hope my phone will be fix again... :crying:
Mufrad said:
First flash latest firmware using flashtool, then use SUS to repair your phone.
Latest firmware: http://forum.xda-developers.com/showthread.php?t=2028139
that should do it.
Click to expand...
Click to collapse
Sir i have a question, your firmware works on my phone but even im using my previous ftf there is something poping out saying that
"Factory start-up service, please wait for power off button" and after a min.. it turned off and off course i turned on and bootloop again..
Help please, anyone i'm losing hope to my phone
i do SUS right after flashing that latest FTF, it's still don;t work.. So turn ON my phone... there it goes.. Bootloopng again...
I guess the ftf is OKAY,,, but the problem is there is poping of Restarting or shutting down something.
i thought my phone is now okay, after i turned off automatically and i turn it ON, assuming that it goes again.. but it became okay for only 5 mins or so.. then it turned off again and boot looping again and again.. After i flash it with new version, and it fail, i flash it again with my stock ftf.. then it's goes well but the problem is the poping up "Factory startup service: wait for the power off button"...
And "Power off and use phone." i have no choice, i can only press Power Off..
Still hoping
Blackmantra said:
i thought my phone is now okay, after i turned off automatically and i turn it ON, assuming that it goes again.. but it became okay for only 5 mins or so.. then it turned off again and boot looping again and again.. After i flash it with new version, and it fail, i flash it again with my stock ftf.. then it's goes well but the problem is the poping up "Factory startup service: wait for the power off button"...
And "Power off and use phone." i have no choice, i can only press Power Off..
Still hoping
Click to expand...
Click to collapse
Fastboot a kernel with CWM and flash a custom ROM
Sent from my ST25i using xda app-developers app
To: satya-1998
Sir is that a App? if that's a kind of Apps well it will never work on my phone, i mean i already Download the App through PC because if i will turn on my WIFI on my phone, my Phone crashes and Bootlooping again.. i'm using ftf .54..
On FTF .54 i can't open my Wifi, it crashes and after it crash it goes to Bootloop.
On FTF .54 my Bluetooth has a problem, there is turning ON/OFF but it can't turned ON..
On FTF .54 It can't open the Radio even i put the jack.
But on my stock FTF(France)
There is TURN OFF Button right after i flash it.. and it's a bit laggy
So there it, i hope i deliver my problem clear... Hope we can see the problem...
Blackmantra said:
To: satya-1998
Sir is that a App? if that's a kind of Apps well it will never work on my phone, i mean i already Download the App through PC because if i will turn on my WIFI on my phone, my Phone crashes and Bootlooping again.. i'm using ftf .54..
On FTF .54 i can't open my Wifi, it crashes and after it crash it goes to Bootloop.
On FTF .54 my Bluetooth has a problem, there is turning ON/OFF but it can't turned ON..
On FTF .54 It can't open the Radio even i put the jack.
But on my stock FTF(France)
There is TURN OFF Button right after i flash it.. and it's a bit laggy
So there it, i hope i deliver my problem clear... Hope we can see the problem...
Click to expand...
Click to collapse
No, it's not an app. I hope your boot loader is unlocked. Install drivers for flash tool. Power off phone. Download sliding XU kernel, stock version and place img file in flash tool folder. Go to flash tool, press thunderbolt. Select fast boot. Make sure phone is off. Then connect usb in phone with volume up pressed. A blue led should glow. Then in the fastboot toolbox, press flash kernel and select the sliding XU img file. Let it complete flashing, remove phone from usb. Reboot and keep pressing volume up on Sony logo. You are now in cwm. You can flash a new Rom here
Sent from my ST25i using xda app-developers app
Here's the problem when i Press Up for Fastboot process
29/000/2013 15:00:12 - ERROR - Drivers need to be installed for connected device.
29/000/2013 15:00:12 - ERROR - You can find them in the drivers folder of Flashtool.
So i can't continue the Fastboot process...
And YES my bootloader is Unlock...
Install drivers from the drivers folder in flash tool. Try the fast boot after that.
Sent from my ST25i using xda app-developers app
do not flash BL relock
do not flash BL relock..
flash an international firmware...
check wipes and no final verification
Here's the Savelog, i don't know if i did it Right..
29/052/2013 17:52:09 - INFO - (bootloader) Download buffer format: boot IMG
29/052/2013 17:52:09 - INFO - (bootloader) Flash of partition 'boot' requested
29/052/2013 17:52:09 - INFO - (bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
29/052/2013 17:52:09 - INFO - (bootloader) Erase operation complete, 0 bad blocks encountered
29/052/2013 17:52:09 - INFO - (bootloader) Flashing...
29/052/2013 17:52:09 - INFO - (bootloader) Flash operation complete
29/052/2013 17:52:09 - INFO - OKAY [ 1.495s]
29/052/2013 17:52:09 - INFO - finished. total time: 1.996s
29/052/2013 17:52:09 - INFO - FASTBOOT Output:
sending 'boot' (9878 KB)...
(bootloader) USB download speed was 21250kB/s
OKAY [ 0.501s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.495s]
finished. total time: 1.996s
29/052/2013 17:52:09 - INFO - Please check the log before rebooting into system
29/052/2013 17:52:16 - INFO - Device will now exit fastboot mode and start booting into system
29/052/2013 17:52:17 - INFO - Device disconnected
29/052/2013 17:52:42 - INFO - Finished Fastboot Toolbox
Now after that, i press UP when SONY logo showed up so i can go to CWM... but its not.. I guess i have to throw my phone... i'm losing Patience :crying:
In the past i have once messed up the flashing of a rom and as a result my xperia neo v got stuck at boot loop at the "sony" logo
To fix it, all i did was to go into flashmode and flash the stock .ftf. After that, my phone would work again and i could flash my rom again.
However, now, my soft-bricked phone (same situation, bootloop at sony logo) is unable to go into flash mode and fastboot no matter which button it is i am holding. It just enters recovery mode no matter what i press.
When i hold volume down/menu/back button when i plug in, the phone vibrates and the sony logo appears, then the led light turns blue for a second then disappears, and enters recovery mode.
I am unsure whether my bootloader is unlocked as i may have relocked it in the past but i doubt it relocked it.
I did not find anything helpful after searching the forums for a solution for being unable to enter both flashmode and fastboot.
Re-flashing the rom, wiping cache partition, dalvik cache, factory reset, all of that did not work
Please help if you can :crying:
[EDIT]
Flashmode now works, but i get the header 6 error, so i am trying to use EMMA to fix my phone
[EDIT2]
EMMA worked! thanks guys for your suggestions.
credits to http://forum.xda-developers.com/showthread.php?t=2190272 for the suggestion
(in case anyone stumbles upon this thread and wants to try this solution)
on a side note my phone is now back to 2.3.4 haha
more problems incoming
Syntactic said:
In the past i have once messed up the flashing of a rom and as a result my xperia neo v got stuck at boot loop at the "sony" logo
To fix it, all i did was to go into flashmode and flash the stock .ftf. After that, my phone would work again and i could flash my rom again.
However, now, my soft-bricked phone (same situation, bootloop at sony logo) is unable to go into flash mode and fastboot no matter which button it is i am holding. It just enters recovery mode no matter what i press.
When i hold volume down/menu/back button when i plug in, the phone vibrates and the sony logo appears, then the led light turns blue for a second then disappears, and enters recovery mode.
I am unsure whether my bootloader is unlocked as i may have relocked it in the past but i doubt it relocked it.
I did not find anything helpful after searching the forums for a solution for being unable to enter both flashmode and fastboot.
Re-flashing the rom, wiping cache partition, dalvik cache, factory reset, all of that did not work
Please help if you can :crying:
Click to expand...
Click to collapse
How exactly did you brick it now?
Sent from my Xperia Neo V using xda app-developers app
use SUS ...((if bootloader is lock ))
or try to restore ur android backup from CWM
and if u think ur bootloader is unlock then try unlockbootloader flashtool
sagar.andro said:
use SUS ...((if bootloader is lock ))
or try to restore ur android backup from CWM
and if u think ur bootloader is unlock then try unlockbootloader flashtool
Click to expand...
Click to collapse
Im attempting SUS right now but it tells me my phone cant be identified
my android backup tells me MD5 checksum failed and i cant do anything about that because i cant get cmd to work..
[EDIT] SEUS gives me the 'your phone contains modified software' message and i relocked using flashtool but got the same message
sony service center last step ...........
or wait if any one give u some useful help
Attitude.SSJ said:
How exactly did you brick it now?
Sent from my Xperia Neo V using xda app-developers app
Click to expand...
Click to collapse
I simply did the standard procedure for flashing a new ROM.
1.kernel
2.factory reset, wipe cache partition, dalvik cache, format data , system, and cache, the likes
3. then i flashed a new rom. sjb5.5 and flashed the gapps zip
did i do anything wrong :/
Syntactic said:
I simply did the standard procedure for flashing a new ROM.
1.kernel
2.factory reset, wipe cache partition, dalvik cache, format data , system, and cache, the likes
3. then i flashed a new rom. sjb5.5 and flashed the gapps zip
did i do anything wrong :/
Click to expand...
Click to collapse
Which kernel?sjb needs a jb kernel...
Sent from my Xperia Neo V using xda app-developers app
Attitude.SSJ said:
Which kernel?sjb needs a jb kernel...
Sent from my Xperia Neo V using xda app-developers app
Click to expand...
Click to collapse
ahhh that must have been the problem.... i probably flashed a ICS kernel
i recovered phone using EMMA, and now i have a new problem :
06/038/2013 17:38:55 - INFO - Reading device information
06/039/2013 17:39:19 - INFO - Please connect your device into flashmode.
06/039/2013 17:39:20 - INFO - Opening device for R/W
06/039/2013 17:39:20 - INFO - Processing loader
06/039/2013 17:39:23 - INFO - Checking header
06/039/2013 17:39:23 - ERROR -
06/039/2013 17:39:23 - INFO - Your phone bootloader cannot be officially unlocked
06/039/2013 17:39:23 - INFO - You can now unplug and restart your phone
06/039/2013 17:39:30 - INFO - Selected MT11i / 4.1.B.0.431 / Customized Central Europe 3
06/039/2013 17:39:30 - INFO - Preparing files for flashing
06/039/2013 17:39:31 - INFO - Please connect your device into flashmode.
06/039/2013 17:39:32 - INFO - Opening device for R/W
06/039/2013 17:39:32 - INFO - Start Flashing
06/039/2013 17:39:32 - INFO - Processing loader
06/039/2013 17:39:32 - INFO - Checking header
06/039/2013 17:39:32 - INFO - Ending flash session
06/039/2013 17:39:32 - ERROR -
06/039/2013 17:39:32 - ERROR - Error flashing. Aborted
06/039/2013 17:39:32 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
the problem is that i see no error.
so im assuming its a header problem but i dont know how to fix it...
[EDIT] current phone :
using stock Xperia Neo V GB 2.3.4 (build 4.0.2.A.0.62 )
hello guys
I have Xperia P, rooted, bl unlocked ( for my bad ) CWM non bootable
first thing first I know there are similar posts on xda but I find my problem quite unique!
I think that my bootloader partition is corrupted or something,
this is what i get everytime flashing (doesn't matter what kind of kernel):
c:\Program Files\adt-bundle-windows-x86-20130729\sdk\platform-tools>fastboot flash boot kernel.elf
sending 'boot' (12436 KB)...
(bootloader) USB download speed was 21695kB/s
OKAY [ 0.609s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 32768 bad blocks encountered
FAILED (remote: Image won't fit, too many bad blocks!)
finished. total time: 0.631s
is that a hardware problem that can be repaired somehow, or I screwed up my phone for good?
funny thing is that I am able to boot my phone and work with it for a few minutes without any problem, but after that a bunch of "stopped working app" pop-ups appear making me unable even to click OK and only hard reset can get me out of that missery. The other thing is, that data on my phone are by some miracle always restored after every reboot. I delete app, reboot, app is back. I take photo, reboot, photo is not there.
Next funny thing- I managed to munt my sd card as mass storage, so I was able to format it with tools like SDformatter, HP USB disk storage format tool. After format I rewriten sd card with bunch of crap (movies and so on) just to make sure, old data are not there anymore. For my excitement, after reboot, old data which was on sd card before formating was back - every single one openable (and crap nowhere). Where does it recover from?
please guys help me, I'm struggling with my phone over one week now :crying:
skynetko said:
hello guys
I have Xperia P, rooted, bl unlocked ( for my bad ) CWM non bootable
first thing first I know there are similar posts on xda but I find my problem quite unique!
I think that my bootloader partition is corrupted or something,
this is what i get everytime flashing (doesn't matter what kind of kernel):
c:\Program Files\adt-bundle-windows-x86-20130729\sdk\platform-tools>fastboot flash boot kernel.elf
sending 'boot' (12436 KB)...
(bootloader) USB download speed was 21695kB/s
OKAY [ 0.609s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 32768 bad blocks encountered
FAILED (remote: Image won't fit, too many bad blocks!)
finished. total time: 0.631s
is that a hardware problem that can be repaired somehow, or I screwed up my phone for good?
funny thing is that I am able to boot my phone and work with it for a few minutes without any problem, but after that a bunch of "stopped working app" pop-ups appear making me unable even to click OK and only hard reset can get me out of that missery. The other thing is, that data on my phone are by some miracle always restored after every reboot. I delete app, reboot, app is back. I take photo, reboot, photo is not there.
Next funny thing- I managed to munt my sd card as mass storage, so I was able to format it with tools like SDformatter, HP USB disk storage format tool. After format I rewriten sd card with bunch of crap (movies and so on) just to make sure, old data are not there anymore. For my excitement, after reboot, old data which was on sd card before formating was back - every single one openable (and crap nowhere). Where does it recover from?
please guys help me, I'm struggling with my phone over one week now :crying:
Click to expand...
Click to collapse
try flashing stock ICS rom using flashtool
skyfast said:
try flashing stock ICS rom using flashtool
Click to expand...
Click to collapse
is it possible to flash stock rom using flashtool after unlocking bootloader?
Sent from my ST25i using xda premium
abyisforyou said:
is it possible to flash stock rom using flashtool after unlocking bootloader?
Sent from my ST25i using xda premium
Click to expand...
Click to collapse
Flashtool and pcc are different
Sent from my LT22i using xda premium
abyisforyou said:
is it possible to flash stock rom using flashtool after unlocking bootloader?
Sent from my ST25i using xda premium
Click to expand...
Click to collapse
yeah if it is a ftf file through flashboot mode.
didnt try .img file using fastboot mode though.
skyfast said:
try flashing stock ICS rom using flashtool
Click to expand...
Click to collapse
nope, it's no-go
I was trying to flash it with for about 3 different (ICS, JB) .tft
it always stucks at reading device information
27/005/2013 17:05:21 - INFO - <- This level is successfully initialized
27/005/2013 17:05:21 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
27/005/2013 17:05:21 - INFO - Device connected in flash mode
27/005/2013 17:05:54 - INFO - Selected Sony Xperia P LT22i / 6.1.1.B.1.54 / Sony
27/005/2013 17:05:54 - INFO - Preparing files for flashing
27/006/2013 17:06:32 - INFO - Please connect your device into flashmode.
27/006/2013 17:06:33 - INFO - Opening device for R/W
27/006/2013 17:06:34 - INFO - Reading device information
it will be like that for eternity
skynetko said:
nope, it's no-go
I was trying to flash it with for about 3 different (ICS, JB) .tft
it always stucks at reading device information
27/005/2013 17:05:21 - INFO - <- This level is successfully initialized
27/005/2013 17:05:21 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
27/005/2013 17:05:21 - INFO - Device connected in flash mode
27/005/2013 17:05:54 - INFO - Selected Sony Xperia P LT22i / 6.1.1.B.1.54 / Sony
27/005/2013 17:05:54 - INFO - Preparing files for flashing
27/006/2013 17:06:32 - INFO - Please connect your device into flashmode.
27/006/2013 17:06:33 - INFO - Opening device for R/W
27/006/2013 17:06:34 - INFO - Reading device information
it will be like that for eternity
Click to expand...
Click to collapse
try installing the driver in the flashtool first and also flashboot/fastboot driver as well if done.
flash the ftf file then
hard turn-off your phone by hitting power button and up volume then wait for 3 vibrations...
hold down-volume button before inserting the cable (light green indicator)
-feedbacks
@skynetko
And the phone is still operational?
skyfast said:
try installing the driver in the flashtool first and also flashboot/fastboot driver as well if done.
flash the ftf file then
hard turn-off your phone by hitting power button and up volume then wait for 3 vibrations...
hold down-volume button before inserting the cable (light green indicator)
-feedbacks
Click to expand...
Click to collapse
don't worry I am not that noob
drivers are installed properly, I know how to enter flashmode, fastboot, how to hardreset, but anyway I did what you told...reinstalled drivers, turned off device, holdin power+ volume up button until three continuos vibrations, connected in flashmode with green led indicator...still the same - READING DEVICE INFORMATION
ChikeD said:
@skynetko
And the phone is still operational?
Click to expand...
Click to collapse
yes it is, check my #1 post in this thread...I described the strange behaviour of my phone. I really don't understand. I can make phone calls,send messages, connect my laptop to its internet through its hotspot- in other words, everything works fine, but just for few minutes...
skynetko said:
don't worry I am not that noob
drivers are installed properly, I know how to enter flashmode, fastboot, how to hardreset, but anyway I did what you told...reinstalled drivers, turned off device, holdin power+ volume up button until three continuos vibrations, connected in flashmode with green led indicator...still the same - READING DEVICE INFORMATION
yes it is, check my #1 post in this thread...I described the strange behaviour of my phone. I really don't understand. I can make phone calls,send messages, connect my laptop to its internet through its hotspot- in other words, everything works fine, but just for few minutes...
Click to expand...
Click to collapse
i used to have this problem..when i inserted it to USB3.0 port...try changing to 2.0 port..
that should fix the problem..!
regards
kantry123
skynetko said:
yes it is, check my #1 post in this thread...I described the strange behaviour of my phone. I really don't understand. I can make phone calls,send messages, connect my laptop to its internet through its hotspot- in other words, everything works fine, but just for few minutes...
Click to expand...
Click to collapse
That's why I asked, because I wonder how it's working after earasing boot partition.
Did you flash stock kernel with fastboot (kernel.sin) and had those errors too?
I know there is format command in fastboot but never tried it, though bad blocks are usually at the device level and not sure there anything can be done about it.
kantry123 said:
i used to have this problem..when i inserted it to USB3.0 port...try changing to 2.0 port..
that should fix the problem..!
regards
kantry123
Click to expand...
Click to collapse
not my case...running on 4 years old laptop with 2.0 USB ports only...I made a new try on everyone, no change...
ChikeD said:
That's why I asked, because I wonder how it's working after earasing boot partition.
Did you flash stock kernel with fastboot (kernel.sin) and had those errors too?
I know there is format command in fastboot but never tried it, though bad blocks are usually at the device level and not sure there anything can be done about it.
Click to expand...
Click to collapse
yes, I made attempt with it, the same old story with every kernel - too many bad blocks as in the #1 post
skynetko said:
don't worry I am not that noob
drivers are installed properly, I know how to enter flashmode, fastboot, how to hardreset, but anyway I did what you told...reinstalled drivers, turned off device, holdin power+ volume up button until three continuos vibrations, connected in flashmode with green led indicator...still the same - READING DEVICE INFORMATION
yes it is, check my #1 post in this thread...I described the strange behaviour of my phone. I really don't understand. I can make phone calls,send messages, connect my laptop to its internet through its hotspot- in other words, everything works fine, but just for few minutes...
Click to expand...
Click to collapse
ohh silly me, well i was talking to your earlier response. i thought you cant detect your device on the flashtool, anyway whats your device current Rom and kernel?
skyfast said:
ohh silly me, well i was talking to your earlier response. i thought you cant detect your device on the flashtool, anyway whats your device current Rom and kernel?
Click to expand...
Click to collapse
Flashtool detect my device allright.
Android 4.1.2
FW: 6.2.A.1.100 Stock ROM
Kernel don't know if it has some name, it's the one from the doomlord root method
in phone it says
3.0.8+
[email protected]))
#1 SMP PREEMPT (and unimportant date numbers)
Is your Problem solved ?
I Have Your problem exactly in android 4.0.4 ...
Any Solution ?
---------- Post added at 08:12 PM ---------- Previous post was at 08:12 PM ----------
Is your Problem solved ?
I Have Your problem exactly in android 4.0.4 ...
Any Solution ?
Same with my Xperia T. It's like recovery restore a previous functional image and only works for few minutes.
My T can boot in flash and fastboot mode but halt on flashing
Enviado desde mi Nexus 10 usando Tapatalk 4
... some problem with my kids Xperia Sola. Has someone found a solution???? Please?
jack15381 said:
Is your Problem solved ?
I Have Your problem exactly in android 4.0.4 ...
Any Solution ?
---------- Post added at 08:12 PM ---------- Previous post was at 08:12 PM ----------
Is your Problem solved ?
I Have Your problem exactly in android 4.0.4 ...
Any Solution ?
Click to expand...
Click to collapse
Same problem with my old Xperia Sola... Has someone found a solution?
I did a google search and it seems to be due to bad blocks, and it seems that no one can recover the bad blocks. Thus, Flashtool can't install any firmware because not enough space. If you try with fastboot flash xxx.img it will say just that:
E:\Droid_XperiaSola\fastboot>fastboot flash boot boot.img
sending 'boot' (6148 KB)...
(bootloader) USB download speed was 11202kB/s
OKAY [ 0.582s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 32768 bad blocks encountered
FAILED (remote: Image won't fit, too many bad blocks!)
finished. total time: 0.624s
jpmaroco said:
Same problem with my old Xperia Sola... Has someone found a solution?
I did a google search and it seems to be due to bad blocks, and it seems that no one can recover the bad blocks. Thus, Flashtool can't install any firmware because not enough space. If you try with fastboot flash xxx.img it will say just that:
E:\Droid_XperiaSola\fastboot>fastboot flash boot boot.img
sending 'boot' (6148 KB)...
(bootloader) USB download speed was 11202kB/s
OKAY [ 0.582s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 32768 bad blocks encountered
FAILED (remote: Image won't fit, too many bad blocks!)
finished. total time: 0.624s
Click to expand...
Click to collapse
I also have this problem with my Xperia Sola. For two months I can't use my phone anymore due continues booting loop.
If there is anyone who's fixed the same issue, kindly share it with us.. Thank you in advance.