ok, so i'm a noob and i tried to install a custom rom on my x10 mini.
i was running 2.1update1 branded and simlocked.
somehow i managed to do everything wrong, because i bricked it in a way that i haven't seen in the other "bricked" threads.
so here's what i can't do now:
boot normally
boot into xrecovery
flash using SEUS (i get the error flash failed)
flash using flashtool (same thing)
whenever i hit the "on" button on my phone it vibrates and after a couple of seconds there is a screen (for about five seconds) that shows an exclamation mark inside a triangle and a phone lying next to it. after that the phone switches off again.
i've attached an image of the screen and the flashtool savelog from my last two attempts.
thanks in advance!
update:
also tried se's pc companion, same thing, i just get an error and it says to contact se support...
Have you tried using SEUS multiple times?
This happened to me aswell, but after trying SEUS a few times I noticed that the % that it failed at werent the same.
So I tried a few times before I could get it to flash properly back to OFW.
I also belive I used a different computer on my last attempt (Belive that was the time it finally worked.)
So I'd suggest that you'd try a different computer 1st. If it still doesnt work. Flash it a few times with SEUS and check if the % it fails at is the same each time. If not. Just retry and it should work out.
(I came out of it just fine doing this.)
You should give it a try.
Hope I could help out.
thanks for the tip!
using SEUS it doesn't abort at the same % everytime, sometimes its around 10% and sometimes it gets to 99%.
i have already tried it multiple times, but i'll try again using a different computer.
hope it works, lets find out...
thanks alot for the info, it worked like a charm!
installed SEUS on a different machine and it worked perfectly the first time i tried!
now that its working again, time to try getting that cm6 on there
Happy that it worked!
Know how horrid it feels when you think your phone is dead.
Feel free to ask questions about installing CM6\7 aswell if youre wondering on something.
Have installed CM6\7 several times on my X10 Mini. Failed tons of times to get everything working 100%.
Related
Hi,
I've already read a number of threads both on this forum and others, but need someone to point me in the right direction.
I recently installed Chewitts Dark theme and all was well, at this stage I became over confident and tried to install final simple theme also from this forum and this is where my problems started.
Once the simple theme had completed my phone started to a boot loop and i was gutted. I then tried PC suite and nothing, then after some reading I tried SEUS and it does not recognise my phone.
I can now get PC suite to recognise the phone, however it asks me to mount the SD card, which I can't do as the phone screen show a battery symbol with a flash through it.
I've found the following threads,
http://forum.xda-developers.com/showthread.php?t=683793 (seems complicated)
http://forum.xda-developers.com/showthread.php?t=776278 (seems simple)
but need help, I need something like an idiots guide please.....
what can I try next?
sannan06 said:
Hi,
I've already read a number of threads both on this forum and others, but need someone to point me in the right direction.
I recently installed Chewitts Dark theme and all was well, at this stage I became over confident and tried to install final simple theme also from this forum and this is where my problems started.
Once the simple theme had completed my phone started to a boot loop and i was gutted. I then tried PC suite and nothing, then after some reading I tried SEUS and it does not recognise my phone.
I can now get PC suite to recognise the phone, however it asks me to mount the SD card, which I can't do as the phone screen show a battery symbol with a flash through it.
I've found the following threads,
http://forum.xda-developers.com/showthread.php?t=683793 (seems complicated)
http://forum.xda-developers.com/showthread.php?t=776278 (seems simple)
but need help, I need something like an idiots guide please.....
what can I try next?
Click to expand...
Click to collapse
Fingers crossed I've sorted the problem..
Took the Sim and SD card out and tried SEUS again, this time it worked and only gave me the option to update software. I've just finished and all seems well.
Now i need to root and try and install another theme....
Thanks to all who have contributed to a number of threads on here....only by reading most of the comments was I able to solve my problem....
sannan06 said:
Fingers crossed I've sorted the problem..
Took the Sim and SD card out and tried SEUS again, this time it worked and only gave me the option to update software. I've just finished and all seems well.
Now i need to root and try and install another theme....
Thanks to all who have contributed to a number of threads on here....only by reading most of the comments was I able to solve my problem....
Click to expand...
Click to collapse
If anyone bricks their phone this does work. I picked the wrong flash last night and it looped my phone and removed Xrecovery. Tried Seus with sdcard installed still looped. Removed sdcard and tried again. Works perfectly. Seus installed 2.1 generic.
Close call. Don't try to flash phone after working 14hr days. Lesson learned.
So i have tried Jit enabler v2 and bricked my SE
it freezes at Sony Ericsson logo,
what i can do is boot via xrecovery and since there i dont know how to remove Jit enabler,
Any advice?
Depending on what version of firmware you have, you need to download : http://forum.xda-developers.com/showthread.php?t=902974
and install as update.zip "*10* 2.0.A.0.*** Disable JIT.zip". That should help. If not, clear dalvik cache and reboot.
thanks, but how to put it to SD card because since its bircked i cant properly connect the phone so PC would read its SD card?
newestuser said:
thanks, but how to put it to SD card because since its bircked i cant properly connect the phone so PC would read its SD card?
Click to expand...
Click to collapse
I suppose that You don't have any card reader :/
I don't really remember if ADB works in xRecovery mode, but You can try, to unpack the "disable jit" package, and push manually files to "/system/bin", and "system/lib". The build.prop should not be a problem tho. You can do that with http://forum.xda-developers.com/showthread.php?t=868423 but, as I said, I'm not sure about working ADB in xRecovery. I figure You don't have enough time to push files on "Sony Ericsson" logo, cuz it reboots ;/
Just try.
thanks for helping out!
unfortunetly i have a reader, and only remembered after i did via xrecovery full reset (wipe data). BUT it still didnt booted, froze uppon sony ericsson logo, so im now moving files you gave a link and praying xrecovery still works
You moved to fast with wipe
I don't really know what to say to You right now.
but seems there is xrecovery backup, so in case...i think maybe i can reinstall via update service, than restore backup i made before wiping data out and installing jit disabler. Well thats by my logic should work. But im not really expierienced with phones and dont have x10 for a long time...
Unfortunately that I think is the last thing it's left to do. Just repair the phone via SEUS. I don't want to be a ****, but it's a bitter lesson for You, that if You have xRecovery, and ADB enabled theres always a way to get passed "Sony Ericsson logo reboot". Wipe was just to fast thinking. Hope You don't get in a trouble like that ever.
Yea, i tried too long time ago JiT v2 and i also bricked my phone, i also installed by accident wrong firmware ver JiT v1 and ended up, again, with a brick.
I that case, only solution to it is to Reflash whole firmware again. Trust me, i tried all possible solutions and it didnt worked. Luckily i had my contacts backed up on my g account.
I also learned my lesion hard way, and, this is 100% true.. "If you have xRec be sure to always have a backup."
P.S. Dont worry, mini/pro dont die that easily.. Its just get hardly wounded, it will always recover, but sometimes with memory loss (since u didnt had a backup)
When i first time bricked my phone it was a day old, i freaked out, but manage to get a grip and searched forum a bit. Since i like experimenting with my software i manager to brick my phone 10+ times per day..
And.. guess what phone im using now? x10 mini
Well, yea often flashes are not a big problem, but i don't wish that to anybody, cuz as you said, and all know it's a pain in the ass to get back settings, and all the data.
"Bricking" is defiantly to strong word. Boot loops, or hanging on SE logo is far from bricking, we always have a chance to "repair" our devices by ourself, so no problem here. The real problem can be in the future, when boot loader get fully cracked, and for example we interrupt his flashing process - situation well known for other android phones users. Phone gets bricked, and theres **** we can do about it, cuz recovery is obviously not working.
I did learned something else back then (5 years ago) when flashing my phone with with a desktop PC and suddenly power failure.. bricked my phone which not even got any bootloader to start with. Since that moment I always use my laptop to flash my phone as it has battery to continue the flashing process in case power failure happen again.
farsight73 said:
Since that moment I always use my laptop to flash my phone as it has battery to continue the flashing process in case power failure happen again.
Click to expand...
Click to collapse
Amen to that.
I got this phone from ebay, and it worked a few days before I flashed it so I know it's not hardware or a bad flash on their part because it was stock when I got it. Anyway, I flashed the generic fw through flashtool and it was working fine for awhile until one day it froze and nothing was responsive. The battery died, and I recharged it and threw it into flash mode to repair the firmware through SEUS, and it got it working for awhile until it happened again. So instead I went ahead and used flashtool to put AT&T's fw back on the phone. After I did that, the phone now only vibrates when I turn it on and then does nothing. If it does do something, it just continuously vibrates until I pull the battery. I tried using SEUS and Flashtool to flash another fw because I can get it to flash mode, but it says failed everytime no matter what firmware I use. And SEUS fails right up front when trying to repair. Any ideas?
Pull out the battery....plug the usb cable...run latest flash tool...click on flash button..when it is searching for the fone then put back the battery with pressing the return key.
Recheck the latest driver for 2.3.3
Did it work?
Dude are you aware of rooting procedures?
First you should flash the stock rom back in, then you flash some pre-rooted GB rom. Threads on X10 Android Development are full of options.
jeancca said:
Dude are you aware of rooting procedures?
First you should flash the stock rom back in, then you flash some pre-rooted GB rom. Threads on X10 Android Development are full of options.
Click to expand...
Click to collapse
Dude did you even read my post?
I've been a member here for 3 years and have been flashing Android to phones ever since then. I have looked at the troubleshoots but they were all giving a failed flash. Not to mention this has nothing to do with root or GB, I was talking stock firmware, this brick happened before SE pushed out the GB update.
To subhanker.ds, thank you for the input, I'll give it a shot.
EDIT: Just got the same error
Uploaded with ImageShack.us
As per your screen shot, debugging mode is of....but it is not possible to on now as ur phone is dead.
I think somehow jeancca is correct...use rooting process..(no need to flash any rom)..it will automatically turn on debugging mod & then you flash ur rom...
Hope ur prob will be solved dear...
I've tried several rooting methods that and they all state I should turn on Unknown Sources and Debugging. But I cannot do this, is there a way that will force it into usb debugging as you said?
Actually at the time of flashing debugging mode automatically turn on...
Anyway i'm not getting any clue...although you can try to flash only system.sin file.then see what will happen....best of luck...
I've tried everything I can think of and I still can't get it to work. A new symptom has came up though, when I try and connect it to my PC, it will go into flash mode but after awile the LED goes off but is still recognized by the PC as being in flash mode. Same goes for when I plug it into the charging cable.
Bump.
Sorry for doing it, but is there anyone out there that can help me?! I had to think I have a $200 paperweight.
Hi..... I mentioned this on another post but thought I might see if this might help you. Although I didn't mention the use of other Flashtools in the other thread, I did end up trying Flashtool 2.8.0 and 2.9.1 and the latest edition. In the end I ended up going with the 2.8.0 to start fresh and since that was the one that was used for An Android 2.1, I flashed back to 2.1. With a few instances like those you mention I tried this and worked out.
What I did was open my devices and printers (control panel) and noticed the SEMC USB or IDE blah blah......The device pops up when connecting my phone. I would flash my phone and the go to the "Turn on phone and check debug" and ..... Same as you green light (Flash) would go on and then nothing.
What I did was unplug my phone and Uninstall the device used (SEMC USB or IDE, it named itself differently on an occasion or two) and then started my Flashtool then tried again. Goto Flashtool and prepare your Flash and wait for it to load up (took some time once or twice but....) connect your phone and try again.
I have been messing around with a bunch of apps and FW's and ROMS and lately Unlocking the BootLoader.
Some you can just goto Task Manager and Stop the ADB.exe processes but this uninstall worked excellent for me when needed.
Hope this solves your issue. Good Luck. Oh you may not need the other Flashtools but I have them on file just in case because 2.9.1 gave me a problem before when doing something. You might be able to do with whatever Flashtool you are using but just thought I would share my experience.
I have the same problem . i I flashed it with X10i rom but work for while and after 1 or 2 hours hanged and when i remove the battery it's hang in sony ericsson .
After that I flashed it with SEUS and upgrade to official rom 2.3.3
and has the same problem .DO THINK IT IS A HARDWARE PROBLEM
Tingles said:
Hi..... I mentioned this on another post but thought I might see if this might help you. Although I didn't mention the use of other Flashtools in the other thread, I did end up trying Flashtool 2.8.0 and 2.9.1 and the latest edition. In the end I ended up going with the 2.8.0 to start fresh and since that was the one that was used for An Android 2.1, I flashed back to 2.1. With a few instances like those you mention I tried this and worked out.
What I did was open my devices and printers (control panel) and noticed the SEMC USB or IDE blah blah......The device pops up when connecting my phone. I would flash my phone and the go to the "Turn on phone and check debug" and ..... Same as you green light (Flash) would go on and then nothing.
What I did was unplug my phone and Uninstall the device used (SEMC USB or IDE, it named itself differently on an occasion or two) and then started my Flashtool then tried again. Goto Flashtool and prepare your Flash and wait for it to load up (took some time once or twice but....) connect your phone and try again.
I have been messing around with a bunch of apps and FW's and ROMS and lately Unlocking the BootLoader.
Some you can just goto Task Manager and Stop the ADB.exe processes but this uninstall worked excellent for me when needed.
Hope this solves your issue. Good Luck. Oh you may not need the other Flashtools but I have them on file just in case because 2.9.1 gave me a problem before when doing something. You might be able to do with whatever Flashtool you are using but just thought I would share my experience.
Click to expand...
Click to collapse
Thanks a lot, I will give this a shot as soon as I get home. I'll keep my fingers crossed that this may help me and the others having this sort of issue.
Mobark, I don't think it's a hardware issue. For awhile I was thinking it was a dead screen, but from the people I have heard that did indeed have dead screens, they have lines in the center of the screen while my screen just doesn't turn on.
Hi everyone i am having the same problem my phone only vibrates for sec and the green led just flash for sec than nothing but my phone goes into flash mode but the flash aborts i have also made a thread in which i fully listed my progess and software i used http://forum.xda-developers.com/showthread.php?t=1257581
Nope, didn't seem to work. I think my problem is the phone doesn't want to stay in Flash mode for some reason.
I fix this error, i download and flash this, next i updated in SEUS, my phone is Xperia Play
Sorry for my bad english.
Ok, so I upgraded to 3.0.0 and tried flashing the generic fw again to no avail. And as far as above, the firmware isn't for the x10, it's for the Play, Arc, and Neo.
This is what i did
Not sure if this will work for you but this is how I fixed my phone.
When I first changed the rom on my phone i was on baseband 435. I never changed the baseband with the custom rom install.
My friend factory erased the phone and then it would take 45 - 50 mins to finish booting (would turn on i would see se logo and 50 mins later I'd get to a stock "slide to unlock screen" upon doing so i would get a black bg with the custom batt meter and clock at the top. it also dected the sd wasnt plugged in.
While the phone was on, Sony Ericsson pc Companion would say please mount sd card, and that i couldnt do.
While trying to use flashtool 2.9.1 it would say please put the phone in debuggign mode.
At this point, your ss shows you making it further than i did. because mine wouldnt make it past the date/time (yours starts flashing an fails some way through).
I tried 4 roms and none of them worked.
Then i found http://www.multiupload.com/9H20YEXEHR and After updating to flash tool 3.0.0, and using the stock rom that i posted the link to, It worked. but i had to try a few times. At http://forum.xda-developers.com/showthread.php?t=920746 There are 3 different stock roms for x10a (I used the first one in the x10a list)
I used the one that matched my baseband. Try an match yours if you know it.
When i connected usb, the phone would not turn on. The phone would only turn on with batt in. So i connected usb, held back and put batt in.
Doing this worked, I held the back button until the flash completed.
Also as a note, I did not change the bootloader, that could be why it would boot after 50 mins or so.
I hope this helps.
-Mike
I got a new xperia active st17i yesterday, it was on gingerbread fw.
I used flashtool to unlock the bootloader. I reset the phone but it hung on the sony logo, which was odd. (I have unlocked and flashed around a dozen xperias and this has never happened). I pulled the battery and turned it back on and it boot looped on the sony logo. (left it for several minutes to be sure). Every time it was switched on after that the screen powered on but remained blank.
I flashed the Rage kernel for GB. Turned the phone on and the sony logo came up, went bright, and I got into CWM recovery ;0) all good I thought. I rebooted the phone. It started up, the sony logo came up, went bright, the animation started but then crashed/hung. I left if for a few minutes and nothing, so I pulled the battery. After this, no screen function at all, no back light, completely dead. ;0( When I power on the phone it vibrates and after a few seconds the front led flashes blue and goes out.
Fast boot works, Flash mode works, Flash tool lets me lock and unlock the phone, flash kernels (rage/X-kernel and Lupus) and ftf firmwares ... S1 tool sees my phone, pc companion updates the phone perfectly, but still no screen.
I read the other ST17i bricked threads here and looked at trying the Wotan server method but the phones date code is not covered, its newer than the ones Wotan cover (maybe an issue?).
I have not idea right now, apart from I have hard bricked it somehow. (searching for 'st17i dead screen' gives a few results from Sony's service forum with similar sounding phone activity, with no resolutions). Searching for bricked st17i all relate to soft bricked devices.
As the phone is brand new, I am not sure about the bootloader issue, is it still covered by warranty? The phones current state is locked and fully updated via pc companion, as it was out of the box.
Any advice and help will be greatly appreciated!
Fixed!!! ... (see edit)
I started from 100% scratch. I use an old laptop with winxp to do all my phone work. I did a factory reset on it (begrudgingly) and reinstalled everything*. ADB, flashtool, drivers/kernels etc. (Its now working a lot better I have noticed).
Bear in mind my phones state was factory stock ics 4.1.B.0.587 and locked.
I unlocked the phones bootloader in flastool, it turned on?! Resurrected.
I flashed the ics rage kernel and installed a custom rom, backed up x2 ;0) I AM HAPPY :0D
I honestly tried everything methodically beforehand, hence my post!
*Is it possible to install a corrupt zip? I noticed when downloading files that some were showing as downloaded but were not the correct file size. I only noticed this when grabbing a kernel file, its size was around 6.7mb but the file I had on my desktop was 633kb, it unpacked and came up with the correct size of 6.7mb? (downloaded on my main work laptop with windows 8.1). I had so many bits and pieces on my xp laptop, swapping files from usb pens etc I will assume this could have been my issue!
lol... I must have spent near to 6+ hours reading about tespoint method flashing, TA restoring/backup up, and a whole range of other bricked device issues... I am educated a little bit more now, in more ways heheh...
Update....
The phone worked for about 30 minutes and then a blank screen again. No CWM, because of blank screen. Had fastboot and flashmode still.
So from scratch again, I relocked and flashed with original ftf CE (I have two CE ftf's of different sizes (will need to do homework on these)). The phone was still dead? When plugged into my pc (tried all three USB ports), sometimes when in fastboot/flashmode the device keeps connecting/disconnecting randomly, which is definitely wrong. Possibly my problem is a bad port or maybe the micro usb cable, or loose connection somewhere? Irdk? So now I tried a brand new sony, original, cable and all seems fine again. So, used flashtool to unlock, flash kernel, get to CWM, use my backup and the phone is working again.... but for how long? There's definitely an issue with the ftf files (mabye something to do with my corrupt file size problem? Will go to another place to grab these from and if the phone goes off again will try). odd.
**last edit**
The phone is now running okay. I had a dud battery, which I was using/swapping between several phones that I was returning to stock. It was showing 100% charged but upon disconnecting USB the phone died. Took me the best part of two days to figure that one out... I know! (I'm very busy). So it was possibly the bad battery all along!
It's my beloved I9100P. Last night it strangely failed. I realised in the morning when the alarm didn't go off. The phone was switched off.
When I tried to switch on, it got stuck in boot loop. The carrier animation and samsung logo will keep repeating. So I thought I will go into recover mode and do a factory reset. Phone went into factory mode the first time. I thought let me do a restart from there, just to see what happens. At this point, I noticed a lot of red errors on recovery mode screen, most of which saying something like "unable to mount /cache". I restarted it, but unfortunately the phone again went into boot loop.
Now when I tried, it refused to go even to recovery mode. I tried several times, but every time it got stuck on Samsung Galaxy logo.
It went into download mode fine, so I thought I will flash Orange UK carrier ROM. I downloaded the ROM and tried flashing with ODIN. ODIN recognised the device, but the flashing failed with error "Complete (Write) operation failed".
I don't know what to do now, have exhausted all option that I knew.
Any help in reviving my phone please?
@kaushal101 Keep yourphone phone connected to your pc and keep it in download mode. Dont disconnect it it could turn into a hardbrick which you can't fix without jtag repair service.
What you could do is see or you have installled all drivers, kies is disabled, right odin version. Google the problem and you would probably find an answer fast. I hope this message isnt too late..
wulsic said:
@kaushal101 Keep yourphone phone connected to your pc and keep it in download mode. Dont disconnect it it could turn into a hardbrick which you can't fix without jtag repair service.
What you could do is see or you have installled all drivers, kies is disabled, right odin version. Google the problem and you would probably find an answer fast. I hope this message isnt too late..
Click to expand...
Click to collapse
Interesting. After trying several things, I did unplugged it from the machine. It shows the upgrade failed warning message whenever I try to switch it on now, which was expected.
I can still go to download mode and restart the ODIN flashing original Orange firmware process, but it fails with the same error. The only difference is, the first time it failed on CACHE step. Now it is failing one step earlier, at NAND writing stage.
Is there any hope? I had kies disabled etc., but will give it another shot. My phone was accessible with kies and I could also upload my development APKs from Android studio. So I think drivers shouldn't be a problem.
@kaushal101 I dont really have much knowledge about the s2 anymore, so the only good thing I can suggest is to google the problem and get more people to your thread here to help you and or find other threads about the same thing.
It is good that your phone can still go into downloadmode, I think there is still hope to fix your phone
wulsic said:
@kaushal101 I dont really have much knowledge about the s2 anymore, so the only good thing I can suggest is to google the problem and get more people to your thread here to help you and or find other threads about the same thing.
It is good that your phone can still go into downloadmode, I think there is still hope to fix your phone
Click to expand...
Click to collapse
Thanks for keeping the hope alive!
Have followed XDA's S2-ODIN troubleshoot guide, with no luck so far. Tried different versions of ODIN, reinstalled USB drivers, made sure KIES is removed from processes etc. None has helped so far. I'll keep looking!
kaushal101 said:
Thanks for keeping the hope alive!
Have followed XDA's S2-ODIN troubleshoot guide, with no luck so far. Tried different versions of ODIN, reinstalled USB drivers, made sure KIES is removed from processes etc. None has helped so far. I'll keep looking!
Click to expand...
Click to collapse
Did you tryed another stock rom version?
Try other usb cable.
Sounds weird but try to leave the battery out of your phone for like a couple minutes
Try other usb port.
Try other computer:silly:
These are the things I can think of atm.
Have tried other USB port. Have tried a different firmware.
Am going to try a different PC today, will also give different cable a shot. But the cable I'm using is Samsung official one which came with the phone. And I've been uploading APKs using this cable fine, so am quite sure the cable is fine. But still, will give it a shot. Thanks for replying