Related
It won't start unless plugged it shows empty battery. sometimes when i unplug it stays connected. In usb settings if choose mass storage it seems to get in a loop of connect-disconnect. I have tried flashing different roms but it didn't fix. Any idea of what is happening? Could it be hardware problem?
I've got the same problem, I've tried every kind of wipe, flash with repartition, clearing stats and so on. I'm starting to suspect it's a hardware issue. The Phone seems to always think it's plugged into USB no matter what, it keeps rebooting to the battery icon over and over until I plug it onto a power source and then it boots fine.
After that I can get it back to normalish by rebooting with the power disconnected using the extended power menu in Darkys Rom.
Can anyone help? When I get back from my trip I'll likely flash it back to stock and send it in for repair, or just ***** at bell and get another new phone.
I'm having the same issue, I've searched all over internet and I found other posts with the same problem.. and no one has found a solution for this.
I think is a hardware problem. after having this I've bought a chinese compatible battery, and when I put that battery in, the phone boots up without even pressing the power on button, so weeeird!
With the original one.. there is no way to boot up without plug the phone. I've had the phone working well for more than 5 months
if someone finds a solution please tell!
thanks in advanced!
I had the some problem and more. I did something and this one has gone. I think i replaced a new update.zip in the phone and that solve it but i am not 100% sure. My phone starts normal but when its off sometimes the battery still flashes. In a week or so i will send it to waranty i think.
grofudaniel said:
I had the some problem and more. I did something and this one has gone. I think i replaced a new update.zip in the phone and that solve it but i am not 100% sure. My phone starts normal but when its off sometimes the battery still flashes. In a week or so i will send it to waranty i think.
Click to expand...
Click to collapse
what did you did? so do you think it's a software problem?
I tried to use a non-original battery and when I put in this new battery, the phone boots up without even press any button. so something it's really wrong. if I try the same with the original battery.. nothing happens, the screen is black unless I plug the phone to the charger.
well, at least I can boot my phone without plugging it this way.
I look forward to know more details about this issue.
thanks!
I look forward to know more details about this issue.
Search loads of posts on this topic . Dont know if problem solved or not .
jje
JJEgan said:
I look forward to know more details about this issue.
Search loads of posts on this topic . Dont know if problem solved or not .
jje
Click to expand...
Click to collapse
unfortunately I've done the search in this forum and I haven't found any solution for this, I can't believe it!
regards!
This problem is back again. I can`t start the phone unless it is plugged. I am with the nervs down at this moment.
what makes me crazy is to not know if it's a software or hardware failure!
in my case seems to be a hardware problem unless the phone recognize the non original battery and that makes a software change that makes the phone to boot.
I'll wait until the gingerbread update, and if after update it doesn't work, I will bring the phone to samsung repair point.
I see that I'm not alone with this problem.
Maby if i could connect the phone on usb to pc i would do something but that dosent work either for me so god have mercy.
I had that problem for a few weeks. Went away with a firmware change. Flashed back to stock and then docs rom. No idea what it was. Just went away.
Are you sure the battery is charged? I had the exact same problem on cm7, turned out my battery ran flat overnight
Sent from my GT-I9000 using XDA Premium App
Try this:
Format all your mounts in recovery mode with Clockworkmod. You can do this by going to 'mounts and storage' and formatting boot, system, data, cache. I did sdcard and sd-ext to be sure).
When you have done that install a 2.2.1 stock rom and the problem should be fixed. From here you can install custom rom's again.
Also try disabling any lagfixes (also via CMW)
KeesKaas said:
Try this:
Format all your mounts in recovery mode with Clockworkmod. You can do this by going to 'mounts and storage' and formatting boot, system, data, cache. I did sdcard and sd-ext to be sure).
When you have done that install a 2.2.1 stock rom and the problem should be fixed. From here you can install custom rom's again.
Also try disabling any lagfixes (also via CMW)
Click to expand...
Click to collapse
OK, I'll do that thanks for the suggestion.
I only have one more doubt left, If I do that, after formating everything in clockworkmod.. What does it happens to the phone? is it going to be able to boot after formating all of this? I'm asking this because I don't know how to download the official rom without using kies and the phone booted up and connected via usb cable.
thanks so much!
I've got the same problem.
I thought it was me trying to flash JVK, but after flashing and reflashing 2.2.1 and 2.3.3 and back with bootloaders the problem stayed. I'll try the format "everything" from CWM, hope this will work.
Still abit strange
(BTW I recently was in sub 15 degrees temperatures, surely this isn't the case??)
I had a problem like this where I was getting USB connected coming up again and again and my phone not starting when it wasn't plugged in.
This sounds dumb and I may just have been lucky but I turned USB debugging off and it stopped, left it off for a day or so, a couple restarts later I thought I'd see if it was still playing up so re-enabled it and nope everything's ok again. That was a couple weeks ago and so far so good, I hadn't seen any reports of anyone else with this.
Might be worth a try
Oh I'm using Darkys 9.5 by the way
My problem got worst! My phone would not charge at all until i reflashed. It now charge and boot normaly without to have it plugged, but my pc don't recognize it, not even in download mode with odin. I quess it has something to do with the hardwhare because both times the problem started when i charged it in the same plug.
i had the same problem,I just cleaned the usb port,plugged in the cable without connecting it to the pc or power source,and it started now it's ok
Me too
Another victim of this issue.
I was running a Darky Rom when I first noticed it... I think I was on Ficeto's 2.3.5 JVT. s
I have tried several steps to rid myself of this issue, with no success:
1. Reflashed ROM CWM
2. Reflashed Kernal CWM
3. Factory Reset, format internal SD, & ODIN flash Stock ROM.
4. Wipe & Flash Juwe ROM.
5. Each time, I also wiped the Dalvik Cache and battery stats.
I have tried leaving the battery out for a lengthy period, I have tried draining the battery all the way down, charging all the way up.
At least with the Launcher I am using now, it has the "Reboot" option instead of just turn off. However, I have to make sure I have a USB cable close by and charger in the car all the time now, just in case it runs out of juice or locks up for some reason and needs a battery pull.
Frustrating... Of course, the warranty expired the end of October.
If anyone has successfully completed the recommendation of formatting boot, system, data and cache and flashing stock Froyo? If you have done it, PLEASE post your detailed steps and the result so we don't waste time repeating something that won't work.
I was eyeing the SGS 2, but with all of the issues the market went through with the SGS, I am thinking maybe I should get away from Samsung...
MM
Hello everyone, long time reader, first time poster (with a real query).
Actually last Friday my cappy started to show 100% of the battery after being for some time in use, so I reboot it trying to solve the issue.
After the boot, the cell shows the Initially Battery screen for 2 seconds with the battery without charge then turns off. Tried several times and also using a second battery with full charge and same problem persisted.
10 minutes later without having a battery inside the phone, it boots but when I rebooted the problem arises again.
This weekend I installed Illuminance 3.01, after that I have installed CM9 (very nice ROM) and the battery problem still is happening. I am able to use the phone but I don´t know for how much more.
Any suggestion?
Thanks,
Martin
have you tried to wipe battery stats in recovery ?
Felixcm88 said:
have you tried to wipe battery stats in recovery ?
Click to expand...
Click to collapse
Yesterday night I did a wipe battery stats and the problem still is there.
It starts with the loop and the only way I can start the phone is plugging it then it shows the actual charge of the battery and after that I can boot.
It must be something "deeper" than the rom...
Anybody?
Thanks
Somebody can help?
I am having the exact same issue, stock froyo 2.2 rooted 5 months ago. I'm trying everything before updating to 2.3, I'll let you know if I find a fix, please do the same.
Searching google is not working this time, it's been 3 days...
Things I've tried:
1- From recovery, boot phone. Problem persists after phone is turned off.
2- Boot from revovery, then reset to factory settings, after rese, same issue.
3- Wipe cache from recovery. Problem still there.
4- Wipe cache+user data from recovery. Same thing.
5- repeating 1-4 without SD card or SIM card.
- Wipe battery data... nothing...
- Unrooting, same issue, rooted again.
- Run root fixes with Titanium backup. Same...
- Removing battery for hours, while charging it externally, replace battery, same issue.
All to no success. Things yet to try:
- Update to 2.3 using kies
- Update to beta 2.3.5 using odin
- Update to custom rom, maybe try 3 or 4 different...
- Cry, then save and buy a new phone, use cappy as shiny paperweight...
Please let me know if you could fix it...
I'm not sure what you mean when you say "initial battery screen."
But if I am to understand the rest, your problem is:
initial boot - runs fine, but battery stays at 100% no matter how long it runs.
reboot - phone now says the battery is suddenly dead, and shuts-off.
further reboots - same
You can't get the phone to fully boot till the battery is left out for a while and the phone is fully de-energized.
You have tried a different battery and it behaves the same.
- - - - - -
Have you tried using a known "good" battery? (a new one or one from someone who's phone works fine)
Also, what happens if you plug in the USB while the phone is off? (after the inital boot, when it is stuck in the "dead battery loop.")
Still dead after installing update and 2 custom roms...
Yes I tried a good battery from another cappy, if I plug in the cable it does the same, instead of normally booting, it displays an empty battery and goes off.
I am able to make it work but only entering the restore mode, so I cannot for example be on a trip and reset the phone for whatever reason...
have you tried using a different kernel?
Sent from my SGH-I897 using XDA App
sorry, but how can I try a different kernel? do i need to change the rom?
Nah, kernels can be flashed independent of ROMs just look through development for topics that have "[Kernel]" as the fist word in their title.
If you have gone and loaded two custom ROMs and it still persist then it's not a kernel issue. As the kernel is always changed along with the ROM.
That said, I can only think of two other possibilities: one being dirt or such making a short in the contacts of the usb (does it sometimes think it is plugged in when it's not), two something in the circuitry for the battery randomly went bad.
Try cleaning the socket for the usb. If that does not fix then assume the worst
leaked from my ICS- FUSED SGS I897 contaminating you via XDA app.
Ok, here's the thing, I left it without the battery for 24 hrs, then it was worst. The phone would not turn on at all. However, after that I tried putting the battery in while holding the power button, it worked!!! it's better than having to connect to the computer, but still, I don't want to have to do this every time... flashing roms now to try again.
We're getting somewhere now...
DaNaRkI could be right about it being a circuitry problem (which would suck). With that in mind, have you checked to make sure the prongs which connect the battery to the phone are still in good shape?
When you flashed the roms, are you doing complete wipes? (wiping the cache/dalvik/data)? It might be worth it to go one step beyond that and format all the partitions and then reflash. I think if you do that, you could basically rule out any software problems.
Be sure to back up your data!
P.S. When you do all this wiping and formating and reflashing, boot up and check to see if the problem is still there before you put your data back on jic there is some weird corruption in your data which is causing this.
ok.
have you checked to make sure the prongs which connect the battery to the phone are still in good shape?
yes I have, they're perfect
When you flashed the roms, are you doing complete wipes?
many times, actually
I have yet to format all partitions, how can I do that?
Thanks!!
and yes, all my data is well backed up in my PC and cloud...
---------- Post added at 12:31 AM ---------- Previous post was at 12:09 AM ----------
this is rather odd, just tried to factory reset again, then restarted using the battery method, then... turned it off, and now it boots normally!!!
Thanks for your help !!!
I have the same problem. What exactly did you do? I use a custom rom, and I flashed stock gingerbread 2.3.4.
Formatting the partitions won't do anything, since the phone won't even turn on sometimes. So when exactly did this problem start happening? Was it after a particular flash or other incident?
Hi all,
seems like my OB is broken. But just in case this is still a repairable issue and since I would of course love to keep my good ol' OB, I'm posting my issue. Maybe there is still hope
It all started after OTA-Update from CM10 nightly to the stable release. I noticed that from time to time the power button did not work after charging the device over night. So for example, the device woultn't wake up when pressing the power button, but reconnecting to the charger did the trick. But then again, I often coudn't turn it back to sleep with the button.
Every time that issue appeared, the OB acted normally after removing the battery for a moment.
But not today.
Again, I couldn't get it to lock when it was active because the power button did not work. So I decided to wait until the screen turned off after the timeout which it actually did. But then again, I couldn't wake it up.
So, starting with the "normal" procedure, I removed the battery for a moment and tried to turn it back on, thinking that it'll be just fine again. But not this time. It didn't react at all. Even after connecting it to the charger - the display turned on and showed the charging animation, but I couldn't get the device to boot.
Next step: Common unbrick procedure. Since it was the only thing I could still do with the OB, I reflashed the good old patched v20n using SmartFlash. I used the exact same program and bin files that I used long ago when I initially rooted the device. So that should have worked like a charm. It didn't.
First try: Flashed with SmartFlash and restored an old nandroid with Zeus ROM on it. Rebooted and... oh great it's stuck already on the LG logo.
Okay, 2nd try: Flashed again but this time just selected the reboot option in CWM. Device boots, plays the animated LG bootlogo and reboots into bootlooop....
So far about my poor OB
Now does anybody have any idea what could have gone wrong with the device?
Of course it could just be a coincidence that these issues started right after the update and the cause may be an ancual failure of the HW button.
But really, how likely is that keeping in mind that my OB worked like a charm all the time before the update?
Any ideas, comments or even suggestions what else I could try?
Smartflash must unbrick the device if the problem is not a hardware problem, if you have tried it and it didn´t work, i am pretty sure that you have to take the phone to warranty.
Anyway, you can try to flash a patched bin/fls with root and recovery, after flash phone will go to recovery, then do a full wipe (Data, cache and dalvik) and reboot.
Reflashed with SmartFlash (to get into CWM), wiped all, booted v20n; no power button, all other HW-Buttons work :/
Hardware problem.
That's what I thought as well, but:
Just managed to restore my Zeus ROM Nandroid image, cleared cache and it booted without problems. Aaand: Power button is working again! Locking/unlocking as well as turning on/off the device entirely works normal!
Now seriously, this issue keeps buggin me - how can something like that happen at all??
I mean, if I would mess with the key mapping and remove the mappings of the power button, it might not work anymore for locking and unlocking the phone. But what could possibly cause that button to not even work for powering on the device? I always thought that must be a hard-wired functionality??
Ok well first i gotta say sorry if this is the wrong thread, first one tho.
So, 2 days ago i got a i9001 and it was already rooted.
I installed cwm via odin(cuz i wanted cm10) but little did i know the cwm was messed up
when i first booted into it i saw "E:Can't mount /cache/recovery/command" since im kinda noobish
in all of this i ignored it(i still do, dunno if that was the cause)and when i rebooted from cwm just to
get into the android system to call a friend before i start installing cm10, the phone booted into cwm
again, i though i pressed smth so i rebooted again, and then i knew it was a stuck bootloop.
Then my brain made up this weird conclusion that if i install cm10 and gaps maybe it will fix the bootloop
.. so i did and it did nothing, i wiped the dalvik cache and everything, and then in a german forum i found
this little thing "9001_stock_recovery-signed.zip" i flashed it with cwm aaand now, every time i boot it
with the power key, it shows the samsung first logo, that only says SAMSUNG and then it goes black
it does nothing after that, if i try to volume up+power it boots past the samsung logo but goes into some
box with an arrow coming out of it and some android logo, if i try to enter download mode, it says RAMDUMP
MODE Cause: Force Upload.
Thats all i can give as info. If anyone has the good heart to help me.. please do so.
And please be really specific like ur explaining to a total newcomer.
have a read here http://forum.xda-developers.com/showthread.php?p=30415128
Thx, but i just lost all hope, after i fixed everything.. Installed a stock 2.3.6 i tried to flash another cm10,by
Some doomsday dude and the camera wsnt working so i decided to try the other cm10 that bricked my
Device , after flashing it and gapps i pressed reboot system and after it went black to reboot i expected
The usual samsung logo but unfortunately it never came, the phone is now literally a brick, no sign of
Life i tried to get the battery off and press the power button for some minutes.. Nothin happens..
IceVip said:
Ok well first i gotta say sorry if this is the wrong thread, first one tho.
So, 2 days ago i got a i9001 and it was already rooted.
I installed cwm via odin(cuz i wanted cm10) but little did i know the cwm was messed up
when i first booted into it i saw "E:Can't mount /cache/recovery/command" since im kinda noobish
in all of this i ignored it(i still do, dunno if that was the cause)and when i rebooted from cwm just to
get into the android system to call a friend before i start installing cm10, the phone booted into cwm
again, i though i pressed smth so i rebooted again, and then i knew it was a stuck bootloop.
Then my brain made up this weird conclusion that if i install cm10 and gaps maybe it will fix the bootloop
.. so i did and it did nothing, i wiped the dalvik cache and everything, and then in a german forum i found
this little thing "9001_stock_recovery-signed.zip" i flashed it with cwm aaand now, every time i boot it
with the power key, it shows the samsung first logo, that only says SAMSUNG and then it goes black
it does nothing after that, if i try to volume up+power it boots past the samsung logo but goes into some
box with an arrow coming out of it and some android logo, if i try to enter download mode, it says RAMDUMP
MODE Cause: Force Upload.
Thats all i can give as info. If anyone has the good heart to help me.. please do so.
And please be really specific like ur explaining to a total newcomer.
Click to expand...
Click to collapse
THIS - to go back to stock firmware
After flashing CWM and you get stuck in a bootloop into recovery, do THIS.
Additionally, read from HERE and HERE
Good Luck
I have the same issue, I took my phone to a service and even JTAG failed, it seems the emmc is broken. How can a ROM update physically damage the memory?!
eminence84 said:
I have the same issue, I took my phone to a service and even JTAG failed, it seems the emmc is broken. How can a ROM update physically damage the memory?!
Click to expand...
Click to collapse
JTAG has failed?
The emmc-chip has a special function for erasing partitions. this function is only useable by kernels over 3.x. it is bad that our emmc-chip has a bug. when using this function of the chip to erasing the data partition, the chip damages itself. the data partition cant be used anymore.
for more infos read in the threads and in the links for sgs2 and note.
if i'm wrong please correct me
So is there absolutely nothing I can do to recover my phone?
i would say no.
but if you store the data partition on ext.sd and make a rom that can use it, it is possible to use the phone as normal... like Ivendor did for a short time (if i'm right?)
Can you please detail the steps, what should I do?
Right now the phone is hard-bricked, absolutely no signs of life, can't enter download mode, nothing.
does odin detects your phone? nothing on the screen?
Not sure about Odin, but besides that nothing on the screen, not even when plugging the charger. I took it to a phone service to rewrite the memory with JTAG, and they said it hangs at about 20% and the memory is damaged. I don't understand, the phone is almost new, all I wanted was a lousy update from CM9 to CM10...
i assume that the problem at 20% was the damaged emmc data partition
edit:
but theres a big chance that i'm wrong and your chip is really fully broken. maybe you get the people at service center to be interested in your phone. maybe they can give you more information.
i don't know my phone is working.
what recovery had you installed to update? what did you do? wipe data/cache,... ?
Yes, probably. So, you say there's a posibility to use an external SD card as data partition?
edited my post...
eminence84 said:
Yes, probably. So, you say there's a posibility to use an external SD card as data partition?
Click to expand...
Click to collapse
yes, but you must be able to flash roms to your phone,.as example.by odin.
or the JTAG repair center can flash roms?
Probably they can, but I think I'll buy a JTAG interface and study this myself...
eminence84 said:
Probably they can, but I think I'll buy a JTAG interface and study this myself...
Click to expand...
Click to collapse
I think it takes a lot of time to know how things work...
what if your phone memory is completely dead? the you have bought the JZAG box for nothing...
but for sure it will be interesting how it works.
how much does such a interface cost about? (^^ more than a quarter of a phone? )
I found one at about 12$... I think it might be worth a shot
But yeah, I'm aware it would take some time until I can handle it well, and I'm not sure I have it.
I also considered buying another i9001, but I'm not sure what caused mine to fail, I want Android 4.1 in the new one, too, it really bugs me off I don't know the exact cause of the failure, so I won't repeat it again. I did everything exactly by the steps I found here on the forum, I used ivendor's ROM and updated CWM to 6.0.2.8.
be sure it is not only an adapter.
someone knows if you can write parts of the memory with something like these?
hello all!
my phone was working properly (rooted but not boot unlocked)
pc companion told me there were a new version availlable (.253) I accepted, install, reboot, everything was fine.
I tried to backup my data in order to change the sd card to a bigger one...then it told me there was a problem while backuping so I did a reboot
this is where the problem begins:
now I have a white triangle with a screwdriver in it and a blue bar below it with an animation inside and it's stuck there...what does it mean for a start?
can you please help?
I'd like to recover it in order to get back my data (photos and video I wanted to put on the new sd card)
tried flashtool but it doesn't recognise the phone...
note: before doing all that, free space was low on my XZ internal storage (like 300 megs)
dave_id said:
hello all!
my phone was working properly (rooted but not boot unlocked)
pc companion told me there were a new version availlable (.253) I accepted, install, reboot, everything was fine.
I tried to backup my data in order to change the sd card to a bigger one...then it told me there was a problem while backuping so I did a reboot
this is where the problem begins:
now I have a white triangle with a screwdriver in it and a blue bar below it with an animation inside and it's stuck there...what does it mean for a start?
can you please help?
I'd like to recover it in order to get back my data (photos and video I wanted to put on the new sd card)
tried flashtool but it doesn't recognise the phone...
note: before doing all that, free space was low on my XZ internal storage (like 300 megs)
Click to expand...
Click to collapse
Unplug your phone from the USB cable and then start, see if that helps
This is exactly what I've encountered, can't find much help in the web, re-flash with wipe cache no joy, in the end re-flash with wipe data boot normally, last backup was 4 days old, restore and lost 4 days game progress...
Sent from my C6603 using XDA Premium HD app
That's strange.
Also had the same.
I updated to the .253 ROM and firmware etc and everything working fine.
I then rebooted after removing some system apps and got this.
I left it for a while and still stuck there.
Pressed a few buttons and still nothing then it suddenly rebooted (not sure if related to pressing the buttons or not) and everything was fine.
Then when it booted up it did the NFC firmware update so maybe related to that.
Not had it since and rebooted a few times.
Phil
thanks for replying guys.
problem really is that I can't use flashtool, for some reason I can't go in flashboot mode (green led right?)
and in fact I don't know all the key pressing procedures (if someone can post them all)
...but I think I got the press down and connect right, problem is that I have the green led for less than one second and then nothing...
dave_id said:
thanks for replying guys.
problem really is that I can't use flashtool, for some reason I can't go in flashboot mode (green led right?)
and in fact I don't know all the key pressing procedures (if someone can post them all)
...but I think I got the press down and connect right, problem is that I have the green led for less than one second and then nothing...
Click to expand...
Click to collapse
Hi,
I also encountered this when I tried to use the old root method of .253. (yah, stupid of me but managed to salvage)
Just let it run for like 20 minutes or so and it will reboot subsequently. (As long as the progress bar still move, you should be ok)
Seems like a self-recovery process in place I guess.
yeah I guess you're right , but the first time was so long (more than 20 minutes ) so I thought it was dead...it is obviously some kind of self repair,
because now after a lot of reboots it suddenly started correctly after 5minutes of this blue bar moving....and now working? WTF?
things that I did in case it could help:
-used flashtool beta 4
-flashed a base .434 in blind mode (choosed xperia Z in the list)
-went into flashboot (press down and then plug usb) I had the green light for just a second...(I also installed EMMA drivers from sony , don't know if it helped)
-reboot then wait (I put it also on the docking bay , don't know if it helped as well but it made the blue bar go faster it seems, not sure tho...)
I used "hard boot" also : just jkeep pressing up and the power button until it vibrates 3 times.
maybe just puting it on the dock and then wait (quite some time) is enough (and makes sense)
I just had the same issue - WTF!!!
I just let it sit there for a while and it automatically started.
This is f*** crazy smart (stupid) phone.
DOn't know exactly what my wife did, but I doubt she flashed anything:laugh:
The battery died, she conncted to the charger, most probably with pushing some of the volume buttons and phone booted into Triange mode. Now it's stuk in this mode since an our.
I did Hard reset, but after phone is plug into wall charger it automatically boots in Triange mode.
This is in stock ROM without any modifications, unlocking, anything.
esselite said:
This is f*** crazy smart (stupid) phone.
DOn't know exactly what my wife did, but I doubt she flashed anything:laugh:
The battery died, she conncted to the charger, most probably with pushing some of the volume buttons and phone booted into Triange mode. Now it's stuk in this mode since an our.
I did Hard reset, but after phone is plug into wall charger it automatically boots in Triange mode.
This is in stock ROM without any modifications, unlocking, anything.
Click to expand...
Click to collapse
Just wait - sometimes it takes a while but it'll eventually boot up.
I think [NUT] said somewhere that this is a repair of certain permissions by the phone itself. I've only ever had this for some minutes - but it is possible if the battery an out it could invoke this. Shouldn't be anything to worry about.
And I think fastboot is blue led - you could try flashmode.
I tend to do lots and lots of flashing and mods so I've seen it several times. The first time caught me by surprise and lasted for a long time...now I'm just used to it ..
In my case waiting in triangle mode did not helped. Was waiting 5 hours at work. I flashed with flashtool again stock ROM without wiping data and still no response.
FInally flashed with wipe and phone is running but all data gone. What a crap.