Related
Hi,
For resume, i was just following frastertag instruction to change framework-res.apk with artic 3.0, and during the process i had a reboot from nowhere!!!
and now my phone is bootlooping on "droid" animation.
So what i did:
Trying to flash with alternative script from Kholk, but during the flash i had those error:
Code:
writing 'logo'...
(bootloader) no such partition
FAILED (remote: )
Code:
writing 'system'...
(bootloader) Preflash validation failure
FAILED (remote: )
it reboot and same probleme, just like nothing changed on my phone same bootanimation looping up.
It seems that my bootloader partition is broken.
Is there any solution to fix it or i have to send it to motorola ?
Thanks for your help!!
I had the same 1st error with logo partition but it continued and it frozen at system partition.
I unplugged usb cable and boot, I believed it was bricked, I have do the two times the flash to get a Razr booting correctly.
I change the line in the script: "flash logo logo.bin" to "flash logo.bin logo.bin"
and it worked and boot properly.
Thanks kholk for the tips.
i have a xperia mini st15i, i have unlocked bootloader , while trying to install cyanogenmod, ... i had to run boot.img using fastboot using cmd... as per instruction from official cyanoger forum.... and !!!!! i dunno what went wrong.. my phone wont turn on... wen i press the power button just small vibration.. then nothing! no light! no response to charger conenction or usb, cant enter fast boot... nothing!!!!! its totally bricked! or Dead! please help ASAP
this is my cmd screen log :
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot -i 0xfce flas
h boot boot.img
sending 'boot' (4872 KB)...
(bootloader) USB download speed was 9204kB/s
OKAY [ 0.549s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000148-0x00000179
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 0.960s]
finished. total time: 1.509s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot -i 0xfce rebo
ot
rebooting...
Here, check this thread by Someguyfromhell and hope it helps you
http://forum.xda-developers.com/showthread.php?t=1568792
You may try to access your phone via ADB. If this works, push stock kernel and a flash tool to your phone and flash a working kernel via adb shell.
I did this years ago on a HTC Magic, but dont remember very well.
You did hold volume up while connecting the powered off phone to your computer, did you?
Haltlos said:
You may try to access your phone via ADB. If this works, push stock kernel and a flash tool to your phone and flash a working kernel via adb shell.
I did this years ago on a HTC Magic, but dont remember very well.
You did hold volume up while connecting the powered off phone to your computer, did you?
Click to expand...
Click to collapse
Yes, he did it else kernel installation would not succeed.
The small vibration when starting the phone is normal, after a while the screen should turn on...
Someguyfromhell said:
Yes, he did it else kernel installation would not succeed.
Click to expand...
Click to collapse
Just to make sure , i remember a day where i thougt i have bricked a Vega Tablet. Trying to enter debug mode for hours while be in panic. Then i put the charger back in...
NOTHING WORKS! help
the mini has a small notification lights wight lights up wen i turn it on! but now nothing.. just a small vibration, connecting to charger doesnt light up screen, pressing volume up and connecting usb doesnt work, pressing down and connecting usb doesnt work, no led, no display light, even the small vibration is useless, as it vibrates again wen i press power button after a whili... what it seems like to me.. is a total bootloader failure.. is there a hard reset shortcut.. or can the computer used .. wen the phone is not detected at all? PLEASE HELP
This might be due to the broken kernel.
Download Stock ftf file and then flash it using flashtool.
You have to press VOLUME DOWN key while plugging in usb
brought my phone back to life!
Thanks ppl for ur replies, the problem was due to the kernel i guess, in face the boot.img provided by cyanogen still wont work! no idea why.. could this be because of a different baseband, or soemthing?... Anyways the phone never responded to usb connection, never got into fast boot or flash mode, until i RESTARTED my computer. after i restarted my pc , i was able to flash another kernel ... now im using a AOSP mini ics rom. which is kewl, thankx fellas
[email protected] said:
Thanks ppl for ur replies, the problem was due to the kernel i guess, in face the boot.img provided by cyanogen still wont work! no idea why.. could this be because of a different baseband, or soemthing?... Anyways the phone never responded to usb connection, never got into fast boot or flash mode, until i RESTARTED my computer. after i restarted my pc , i was able to flash another kernel ... now im using a AOSP mini ics rom. which is kewl, thankx fellas
Click to expand...
Click to collapse
Older versions of CyanogenMod kernels were indeed not working due to some bug.
The latest, FXP119, has kernel fixed and works great.
I have come across several posts the are identical or very similar to my issue. However, I am having an additional issue which seems to be the cause of my not being able to unbrick. I'll try to provide enough details, but let me know if I missed something important.
My prime appears to be completely bricked, because I tried to fix another problem. When I tried to upgrade a stock ICS prime to JellyBean, I had many problems because the recovery kept error out with the droid guy with the red triangle and ! symbol. Somehow, I ended up actually do it and ended up with the US_epad-user-10.4.2.15.zip rom (US_epad-10.4.2.15-20120917). Because I am overseas, I had problems installing some things in the market and was considering root or a custom rom. At some point, I unlocked the device, which still displays clearly every time I boot. While look through several things that appeared very straight-forward, I ultimately ended up with a brick. The device is stuck on the splash screen. I have access to fastboot. However, adb doesn't recognize the device.
When trying to RCK (or wipe data) from the bootloader, I get:
Code:
Booting Recovery kernel image
Booting failed
[COLOR="Red"]Unrecoverable bootloader error (0x00000000).[/COLOR]
This post:
[Q] Transformer Prime possibly bricked. Help?
appeared identical to my current problem. The suggested use of universal drivers has not helped, however.
This post:
[SOLVED] Can access fastboot but can't get past splash screen
also appears identical...
These two also appears to provide hope:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
[ROOT] Urkel's Fresh Start 1.0 (Jelly Bean - Unlocked bootloaders only)
...but ultimately, continue to evade my tablet.
Why? you may ask...
Well, it seems that I can boot into fastboot. When I manually run any command, it seems to work fine. But the prime becomes unresponsive to all subsequent commands. It requires that I force reboot and re-enter fastboot. When I try to run Urkel's Fresh Start, the wiping all runs smoothly, and the staging command
Code:
fastboot -i 0x0b05 flash staging system.blob
run smoothly. From that point, it becomes unresponsive again. It appears that although the flashing completes without errors, it doesn't take...or perhaps is inaccessible because the bootloader is jacked. Here's the output from Urkel's Fresh Start, for example:
Code:
Press any key to continue . . .
.: Now cleaning the TF201 partitions :.
erasing 'cache'...
OKAY [ 2.160s]
finished. total time: 2.160s
******************************
erasing 'userdata'...
OKAY [ 39.644s]
finished. total time: 39.645s
******************************
erasing 'recovery'...
OKAY [ 1.953s]
finished. total time: 1.954s
******************************
erasing 'staging'...
OKAY [ 0.948s]
finished. total time: 0.948s
******************************
erasing 'system'...
OKAY [ 2.208s]
finished. total time: 2.209s
******************************
.: Partitions now clean, continuing to reboot back into bootloader. Do not miss
selecting FASTBOOT with VOL+D and then VOL+U on the USB Icon. If you miss it no
big deal reboot back into FASTBOOT before continuing :.
Press any key to continue . . .
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
.: Confirm you are in FASTBOOT before continuing to flash a fresh image/blob. Th
is will take 3-5 minutes because of the size of the image :.
Press any key to continue . . .
sending 'staging' (537604 KB)...
OKAY [ 94.723s]
writing 'staging'...
OKAY [ 1.329s]
finished. total time: 96.054s
rebooting...
finished. total time: 0.548s
.: No need to set up the tablet but let the tablet fully boot to welcome screen
then hold down the power to shut if off. When off turn it back on and enter FAST
BOOT. Once at FASTBOOT then continue :.
Press any key to continue . . .
It appears fine...however, it doesn't reboot, even thought the command said it was successful. So, I try manually rebooting and get stuck at the welcome screen again. It's a vicious cycle... Anyhow, this type of situation is the same for all of the other workarounds that I have found to this problem.
It seems that fastboot is semi-responsive, but no actions that I take are recognized upon reboot. I would love to try and figure out why fastboot is having these issues... and unbrick my tablet. So, please let me know if I have missed any threads that have exactly this solution (ie. fastboot works...but not really).
Thanks in advance, and let me know if I missed details that are necessary.
flueterflam said:
I have come across several posts the are identical or very similar to my issue. However, I am having an additional issue which seems to be the cause of my not being able to unbrick. I'll try to provide enough details, but let me know if I missed something important.
My prime appears to be completely bricked, because I tried to fix another problem. When I tried to upgrade a stock ICS prime to JellyBean, I had many problems because the recovery kept error out with the droid guy with the red triangle and ! symbol. Somehow, I ended up actually do it and ended up with the US_epad-user-10.4.2.15.zip rom (US_epad-10.4.2.15-20120917). Because I am overseas, I had problems installing some things in the market and was considering root or a custom rom. At some point, I unlocked the device, which still displays clearly every time I boot. While look through several things that appeared very straight-forward, I ultimately ended up with a brick. The device is stuck on the splash screen. I have access to fastboot. However, adb doesn't recognize the device.
When trying to RCK (or wipe data) from the bootloader, I get:
Code:
Booting Recovery kernel image
Booting failed
[COLOR="Red"]Unrecoverable bootloader error (0x00000000).[/COLOR]
This post:
[Q] Transformer Prime possibly bricked. Help?
appeared identical to my current problem. The suggested use of universal drivers has not helped, however.
This post:
[SOLVED] Can access fastboot but can't get past splash screen
also appears identical...
These two also appears to provide hope:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
[ROOT] Urkel's Fresh Start 1.0 (Jelly Bean - Unlocked bootloaders only)
...but ultimately, continue to evade my tablet.
Why? you may ask...
Well, it seems that I can boot into fastboot. When I manually run any command, it seems to work fine. But the prime becomes unresponsive to all subsequent commands. It requires that I force reboot and re-enter fastboot. When I try to run Urkel's Fresh Start, the wiping all runs smoothly, and the staging command
Code:
fastboot -i 0x0b05 flash staging system.blob
run smoothly. From that point, it becomes unresponsive again. It appears that although the flashing completes without errors, it doesn't take...or perhaps is inaccessible because the bootloader is jacked. Here's the output from Urkel's Fresh Start, for example:
Code:
Press any key to continue . . .
.: Now cleaning the TF201 partitions :.
erasing 'cache'...
OKAY [ 2.160s]
finished. total time: 2.160s
******************************
erasing 'userdata'...
OKAY [ 39.644s]
finished. total time: 39.645s
******************************
erasing 'recovery'...
OKAY [ 1.953s]
finished. total time: 1.954s
******************************
erasing 'staging'...
OKAY [ 0.948s]
finished. total time: 0.948s
******************************
erasing 'system'...
OKAY [ 2.208s]
finished. total time: 2.209s
******************************
.: Partitions now clean, continuing to reboot back into bootloader. Do not miss
selecting FASTBOOT with VOL+D and then VOL+U on the USB Icon. If you miss it no
big deal reboot back into FASTBOOT before continuing :.
Press any key to continue . . .
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
.: Confirm you are in FASTBOOT before continuing to flash a fresh image/blob. Th
is will take 3-5 minutes because of the size of the image :.
Press any key to continue . . .
sending 'staging' (537604 KB)...
OKAY [ 94.723s]
writing 'staging'...
OKAY [ 1.329s]
finished. total time: 96.054s
rebooting...
finished. total time: 0.548s
.: No need to set up the tablet but let the tablet fully boot to welcome screen
then hold down the power to shut if off. When off turn it back on and enter FAST
BOOT. Once at FASTBOOT then continue :.
Press any key to continue . . .
It appears fine...however, it doesn't reboot, even thought the command said it was successful. So, I try manually rebooting and get stuck at the welcome screen again. It's a vicious cycle... Anyhow, this type of situation is the same for all of the other workarounds that I have found to this problem.
It seems that fastboot is semi-responsive, but no actions that I take are recognized upon reboot. I would love to try and figure out why fastboot is having these issues... and unbrick my tablet. So, please let me know if I have missed any threads that have exactly this solution (ie. fastboot works...but not really).
Thanks in advance, and let me know if I missed details that are necessary.
Click to expand...
Click to collapse
If you don't have universal naked drivers downloaded and installed, do that.... also you should install twrp as your recovery, just make sure you get the right one.... I think I read at the top you installed JB so your bootloader is probably JB...... don't install the ics twrp over the jb bootloader or you will have a unrecoverable mess I think.....
Gage_Hero said:
If you don't have universal naked drivers downloaded and installed, do that.... also you should install twrp as your recovery, just make sure you get the right one.... I think I read at the top you installed JB so your bootloader is probably JB...... don't install the ics twrp over the jb bootloader or you will have a unrecoverable mess I think.....
Click to expand...
Click to collapse
Hey thanks for the help. Unfortunately, as I mentioned, I already tried the naked drivers to no avail. Just to be safe, I tried once more, removed/deleted/uninstalled the drivers and even force turned off driver installation for good measure to make sure. I have the same behavior with both the ASUS drivers and the Universal Naked drivers.
I think I forgot to mention explicitly that I tried installing twrp as recovery. I was careful to get the JB bootloader. It hasn't helped. I tried it again today after the re-install of naked drivers. Same behavior as before. Fastboot appears to flash the blob successfully,, but then the prime becomes unresponsive, will not reboot via fastboot, and sticks at flash screen and no RCK.
Any other things that I could have missed or done incorrectly?
Bootloader Error
Hi,
any solution to this yet? I do have the exact same problem!
It seems to me the procedure is locked and it accepts only one comand (maybe the key) then rejects al subsequent comands.
.
From everything I have seen "Unrecoverable bootloader error" means exactly what it says. its unrecoverable. You need a new motherboard
Bootloader Error
Well, that's exactly what Asus wants us to think. My logical thinking tells me there is no defect other than a software failure in connection with Asus locking down bootloaders in order to torture their customers.
I can still access Fastboot, it is just locked down. I guess the first comand (which it always accepts should be a key to unlock the fastboot procedure, without that key nothing is possible. Why can they not recover it at the service center? Maybe they do not want the key to get public.
It's all business after all.
Still, they use open source software for free and then neglect warranty...
I just cannot understand. Well, not Asus for me again I guess...
whycali said:
From everything I have seen "Unrecoverable bootloader error" means exactly what it says. its unrecoverable. You need a new motherboard
Click to expand...
Click to collapse
Same problem, posted http://forum.xda-developers.com/showthread.php?t=2154851
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.
So before my phone got bricked, I first had been notified that there was an update for it's OS. So while I updated it, I noticed that it took quite a while. I fell asleep. When I woke up, it was on recovery mode. I tried wiping data & cache, but it doesn't work and says "Wipe data and cache failed".
I tried fastbooting. It worked when I flashed boot.img but when I tried on recovery.img it says that:
sending 'recovery' (5612 KB)...
OKAY [ 0.203s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.234s
I can somehow flash the recovery.img but that's about it.
Note that when I try to enter USB Mass Storage Mode and connect it to my PC, it somehow gets detected, but when I try to get in through internal storage it'll say "Please insert a disk to Removable (H".
I also tried removing the battery and then connecting it to my computer and the phone vibrates nonstop. It gets detected in the computer for a few seconds (I checked in the Device Manager and yes, I already installed drivers) and then vanishes. I also tried using SP Flash Tool
What do I do?
Note: Phone is rooted.