Related
I just purchased this phone (i9100) last night after a long travel to track it down. today I simply wanted to update the firmware on it and I was using Odin3 v1.85 to do it but It failed and stayed like that for an hr with the phone in the download mode. I finally disconnected the phone and started it back up and it said " firmware upgrade encountered" with the phone on icon on the left a yellow triangles in the middle and a computer on the right side. Almost looks as though the symbols and words are cutting off the screen.
I can boot into the Download mode but the computer does not recognize the phone anymore nor does Odin or Kies. So I cant even attempt to re-flash the damn thing... I'm so upset right now and feel like taking a hammer to this damn phone...
Any help would be greatly appreciated. I've don't everything when it comes to drivers uninstalling Kies, using other computers without Kies installed, different ports and cables. I've done it all as far as i can see.... also I cant return the damn thing as i didn't buy it from a store. so im **** out of luck if i cant get this working.... PLS HELP!
Are you sure you are downloading the right version of the drivers? I ask because it sounds like you bought the international galaxy s II and not the Epic 4G Touch but you asking the question in the E4GT forums.
The phone is Sprint branded and so is the box.
jettienne12 said:
The phone is Sprint branded and so is the box.
Click to expand...
Click to collapse
Okay, so for future reference... you have the D710, NOT the i9100. (The i9100 is the international SGS2, different enough from the Epic Touch that you can't flash i9100 firmware.)
That said, if you can get into download mode then all is not lost!!
Restart your computer. Also, when you use odin, be sure to go into your Windows task manager and close any Kies tasks/processes that may be running in background. You only need Kies for the drivers it provided when you installed it onto your pc.
Suggest you put your phone into download mode, and follow the instructions in the 1st post in this thread:
http://forum.xda-developers.com/showthread.php?t=1282420
I tried the instructions in the link. however, the problem seems to that the phone is not being detected by the computer or the drivers dont seem to be working. I tried this on my other computer and while the phone is in download mode it is still not being detected by the computer or odin.... what can be causing this as before the firmware update that failed it was being detected perfectly fine.
I pretty much have the exact same problem as posted here.
http://forum.xda-developers.com/showthread.php?p=18176145#post18176145
jettienne12 said:
I pretty much have the exact same problem as posted here.
http://forum.xda-developers.com/showthread.php?p=18176145#post18176145
Click to expand...
Click to collapse
Sorry to be the bearer of bad news, but I was never able to get any computer to recognize the phone in that state. I was able to take it to the Sprint store and they ended up giving me a new one for a small service charge. Since you didn't get it at a store I would contact Samsung and give them the story that cooza suggests in the thread you linked. Good luck and post back if you ever get it working, I am still curious as to what was wrong.
The only thing that might be hampering your effort is Kies might be still active. I overlooked this instruction (as was mentioned in a previous post). Before starting Odin or connecting your phone go into Windows task manager (ctrl/alt/del) and click on processes. Scroll down and you'll probably see a Kies process running. End that process, then try it again.
.....
Sorry but Kies has been completely uninstalled from this computer and the other computer.
are you plugging the phone before or after entering download mode?
I did both before and after to see if that would make a difference, but no go.
jettienne12 said:
Sorry but Kies has been completely uninstalled from this computer and the other computer.
Click to expand...
Click to collapse
I thought you needed the drivers from Kies?
.....
I installed the drivers without it, I downloaded the drivers for my model phone from another member who suggested it.
Try deleting the drivers that u have and reinstalling kies. Use different usb ports.
Sent From My Evo Killer!!!
i would reinstall kies..... or if you have a linux box maybe try heimdall > http://forum.xda-developers.com/showthread.php?t=755265 to flash
Guys, I tried Ubuntu but with no luck. The computer simply will not detect the phone. At this point I believe only Samsung can fix or replace this. I will contact them tomorrow and see. Maybe they will do it for free or maybe they will charge a small fee (small I hope if any) but thank you all for the help.
Yes, i'm a total noob, sorry everyone. I tried to root my T Mobile Galaxy S2 using the Kies/Odin method, and now i'm getting nothing but a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I would happily follow those directions, but now Kies won't recognize my device?!?!? I also can not get back into download mode. I have no idea what to do. Is there anyone out there that can help?
Can you still turn your phone on and use it?
Sent from my SGH-T989 using XDA App
He can not use the phone
Sent from my ADR6400L using Tapatalk
Hey I was wondering if u can help my friend out it seems like u were trying to be nice but here's his story he was trying to root his phone I don't know what method but it dud require Odin and some file called Hercules witch I think is cwm but I don't know were he went wrong but now when he tries to boot up it takes him to a black screen that says in red writing Odin mode..product name sgh t898, custom binary: no , current binary Samsung official and below all that there is a phone and yellow warning symbol with it saying firmware upgrade encounter an issue. Please select recovery in kies and try again
Sent from my ADR6400L using Tapatalk
my ADR6400L using Tapatalk
This is what he gets is anyone willing to help
Sent from my ADR6400L using Tapatalk
All you need to do is flash it using Odin. Grab the stock rom from the general forum of the galaxy s2 and flash it using Odin.
Sent from my SGH-T989 using Tapatalk
Did/does Odin recognize the phone? If it does then go ahead and flash the stock Odin firmware package and that should take care of the problem. Same thing happenend to me and all you need to do is set everything up just like normal, go into DL mode and give Odin a few seconds to find a com port and hit start...just pretend the warning is not there.
I have the same thing ...
I was doing a stock upgrade through Kies, and my computer decided to be dumb and install a windows update and restart the computer... I now see the same thing, i had the stock rom, but it was rooted, and when I try to go back in Odin, it never recognizes the phone... Kies won't recognize the phone, neither will Odin... Am I just returning this phone or what?
EDIT: Nevermind, I only bought it 2 days ago, so I just exchanged the phone
Yes, you can flash from that screen -- I managed to brick my Vibrant that way a number of times, and as long as you get that screen (or the Android digging screen) it's recoverable. KIES should be able to recover it as should Odin -- if it DOESN'T work turn OFF the computer (all the way off) and restart it then try again.
Samsung's USB drivers have a habit of getting confused and causing flash failures both in KIES and Odin.
Be aware that if you're trying to use KIES and the "latest" firmware is a non-wipe firmware (as the updates from T-Mobile are) it will happily load onto the phone something that will bootloop into the stock recovery and refuse to start! If you get hosed like this you probably need to Odin back to the ORIGINAL firmware so you get a "full" flash, then use KIES (or ODIN) again to perform the update.
UntamedDeviance said:
I have the same thing ...
I was doing a stock upgrade through Kies, and my computer decided to be dumb and install a windows update and restart the computer... I now see the same thing, i had the stock rom, but it was rooted, and when I try to go back in Odin, it never recognizes the phone... Kies won't recognize the phone, neither will Odin... Am I just returning this phone or what?
EDIT: Nevermind, I only bought it 2 days ago, so I just exchanged the phone
Click to expand...
Click to collapse
Were you able to exchange your device? And if you did, what did the T-Mobile reps ask you? and what did you tell them? I ran into the very same problem. I tried everything but I'm still stuck on that screen. I don't want T-Mobile to think I purposely did something to make the phone that way.
Hope I'm not too late to help: I had same problem and used odin to fix.
Here's what I did:
Download stock kernel in tar form from the Android devel forum. Start odin, click check box in PDA, click PDA button then select the kernel you just downloaded.
Insert usb into your phone (I left my cord connected to my computer). Start phone in download mode (up+down keys). Once it's started ib DL mode, unplug the usb cord, then after just a few moments plug it in again. If necessary, let it set a few moments until Odin recognizes the device (yellow stripe in id:com to the upper left), now click start in odin.
That fixed my problem. After that I read and reread everything I could get my hands on, but I think I tried flashing a i1900 kernel.....big duh to me, but maybe I'm not that dumb after all!! But, soon after I was able to root, and have flashed several custom ROMs since my little bump in the road.
Mrplennium said:
Were you able to exchange your device? And if you did, what did the T-Mobile reps ask you? and what did you tell them? I ran into the very same problem. I tried everything but I'm still stuck on that screen. I don't want T-Mobile to think I purposely did something to make the phone that way.
Click to expand...
Click to collapse
Yeah, I just walked in, brought my receipt and box, and told them I needed a new phone because mine bricked while doing a stock update...they were happy to do it... every one there knew I had previously rooted it as well...
Sent from my SGH-T989 using xda premium
i used this method to root my phone, you need to use odin and flash a new rom
Mrplennium said:
Were you able to exchange your device? And if you did, what did the T-Mobile reps ask you? and what did you tell them? I ran into the very same problem. I tried everything but I'm still stuck on that screen. I don't want T-Mobile to think I purposely did something to make the phone that way.
Click to expand...
Click to collapse
Took mine to a store, they didn't have any white kits in stock so they told me to call and tell them that it doesn't turn on, got a replacement ordered without having to troubleshoot over the phone.
Had that happen the first day I got the device trying to root up. Accdently pulled usb while updating. All i did was Hold VOL UP + DOWN And Plug usb in and download mode came right back up and started the process all over again.
It was a success as.
M&S
Worked!
Thank you!
Overseas and very stressed!!
i had a problem updating -- same error message "firmware upgrade encountered an issue" -- kies can NOT connect to my device. ODIN will not install ICS.. ODIN will not install GINGERBREAD either...
i have the SGH-T989 (t-mobile GS2)
nothing will update. i can't back out to revert to the gingerbread OS i was running previously...
can anyone help me out?
email direct or respond here... thanks for anyone's help
have the same problem
tried to downgrade from ics to 2.3.6 and odin gived me a fail message,after that nothing works i i connect it to the charger it says firmware upgrade encountered an issue.please select recovery mode in kies and try again.
but kies doesn`t recognize me and odin neither.
i can go to download mode with my jig but like i said odin does not give me the yellow symbol.....
is it bricked???
atilla88 said:
have the same problem
tried to downgrade from ics to 2.3.6 and odin gived me a fail message,after that nothing works i i connect it to the charger it says firmware upgrade encountered an issue.please select recovery mode in kies and try again.
but kies doesn`t recognize me and odin neither.
i can go to download mode with my jig but like i said odin does not give me the yellow symbol.....
is it bricked???
Click to expand...
Click to collapse
we don't have ICS... so I'm not sure if you're in the correct section. is your phone's variant the t-mobile t989 hercules s2?
don't do anything with kies, go to download/odin mode and flash a fresh download of whatever you messed up on... or I would just flash a complete stock ROM.. the ones ending with ".tar.md5".. that should save your phone.
Teo032 said:
we don't have ICS... so I'm not sure if you're in the correct section. is your phone's variant the t-mobile t989 hercules s2?
don't do anything with kies, go to download/odin mode and flash a fresh download of whatever you messed up on... or I would just flash a complete stock ROM.. the ones ending with ".tar.md5".. that should save your phone.
Click to expand...
Click to collapse
i used a ics rom from xda and my phone is a european s2 without branding,i just saw this thread here and posted my problem.
like i said odin didn`t recognizes me so i can`t flash anything...
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Sorry to hear that. This is something I learned (second hand, thank god) when I had my Galaxy S1. Odin can simultaneously be the best and worst tool you use.
Sent from my Galaxy Nexus
ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
rayiskon said:
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
I had a feeling that it wasn't truly bricked, but since my phone's USB driver (or whatever aspect of USB data transfer) was malfunctioning I couldn't do anything about it. I think of it this way: if in that state my phone had a 5% chance of being recognized by Odin, and if my phone already had less than a 20% chance of being recognized before the soft-brick, then I had a 1% chance or less that it would even show up in Odin and even lower odds at a successful flash. Regardless, Verizon agreed to send me a warranty replacement.
iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
Same here with the vibrant. IIRC there was a special way to get your phone to recognize Odin when it happened. Something like plugging in the phone to the computer and then pulling the battery. Odin even worked when I borked a flash and the screen wouldn't even turn on. I would think the nexus could be brought back similarly.
But if the USB port is on the fritz I'm not sure I would want to bring it back.
As far as I'm concerned Odin is the worst thing you can hook up to your devce. No single program has bricked more devices than Odin.
______________
Just Flash It !!!
on my old SGS1 there was chance get back bricked device by method called "JIG"..(its hardware way get back download mode) but i dont study it more...
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
try to use another cable to connect ur phone to pc
just flash stock via odin, it's not bricked.
My s2 sometimes has that problem when i flash stock
eksasol said:
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
Click to expand...
Click to collapse
I appreciate the advice but I no longer have that phone. My replacement should come today.
With regards to the drivers, I was referring to the drivers on the phone not on the computer. I honestly don't know if there are USB drivers on the phone (I would think there are) or even if those drivers were causing the malfunction.
The first thing I'm doing this afternoon is plugging my replacement phone into my computer. If the new one doesn't work right then I'll have to make a trip to the Apple store because the problem will almost certainly be my laptop. I'll also owe a big apology to Verizon.
I first rooted my phone and then I attempted to download Ice Cream Sandwich on my Sprint Samsung Galaxy s2 4g Touch. During the download to my phone (using odin) my computer said that the update failed. My phone is saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." When I try to connect my phone to my computer, it will not detect it at all. And when I tried to put my phone in download mode, the upper left hand corner says Low Battery!! Can't Download in red letters (even when it is plugged into my computer). My LED light is also flashing blue. I just wanna restore my phone to factory settings or whatever I can do to make it work again. Thanks in advance for any help, it is really appreciated.
You should have read more....
Sent from my SPH-D710 using xda premium
STLBleedBlue said:
I first rooted my phone and then I attempted to download Ice Cream Sandwich on my Sprint Samsung Galaxy s2 4g Touch. During the download to my phone (using odin) my computer said that the update failed. My phone is saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." When I try to connect my phone to my computer, it will not detect it at all. And when I tried to put my phone in download mode, the upper left hand corner says Low Battery!! Can't Download in red letters (even when it is plugged into my computer). My LED light is also flashing blue. I just wanna restore my phone to factory settings or whatever I can do to make it work again. Thanks in advance for any help, it is really appreciated.
Click to expand...
Click to collapse
I got that message before and just knew I was screwed but I did some reading before panicking and these are the steps I took to recover from it.
Before you start pop out your sd card (hopefully you have an adapter or another device you can use to load stuff onto the card.
Put your phone on the wall charger for at least an hour to get some juice into the battery.
While the battery is charging go find a ROM you can flash via recovery as well as the el26 cwm kernel.
Then pop out your sd card and load the EL26 cwm kernel and ROM onto the sd card. (I would suggest maybe something from Calkulin or sfhub for ease)
Hold volume up + power to get into recovery mode, which you can still hopefully do.
Flash the el26cwm kernel and then the ROM.
Reboot
With any luck when you reboot your phone should come up.
Good luck.
It won't let me into recovery mode unfortunately.
STLBleedBlue said:
It won't let me into recovery mode unfortunately.
Click to expand...
Click to collapse
Well that sucks. I'm unsure what else you can try.
I assume you've pulled the battery then tried to go into recovery and/or Odin?
Have you tried other cables, usb ports or computers? Re-downloaded the drivers?
Sounds like u tried to Odin the international ICS. U will need to look into jtag service or having the device replaced via TEP, insurance or a warranty replacement. Like fryingpan said you should have done more research before trying to install custom firmware.
We are legion, for we are many.
you might be able to fix it with jtag
Sent from my SPH-D710 using Tapatalk 2
It would help to know what file you were trying to flash. Where did you find it?
STLBleedBlue said:
It won't let me into recovery mode unfortunately.
Click to expand...
Click to collapse
DID you CHARGED IT for at least AN HOUR as Eso recommend you? if not then plug it in to a wall and wait then try download mode again because is telling you NO BATTERY NO JUICE available. 20 minutes is not enough to get some juice to perform an ODIN Flash.
Hello.
I've tried to update from leak 4.1.2 to final version but bricked the phone. Everything went well until restart. Progress bar in recovery went to the end, odin told that it's finished and it restarts the headset (green square) but the phone did not started.
Battery is OK, the phone does not start in normal mode nor in recovery ( +vol- +home +power) however, when i try to run recovery and the USB cable is plugged, my PC says that new device is found ("u8500 usb rom")
Odin dont see the phone.
Is there something that may help?
EDIT: ok, I found that in most cases only sending the phone to retailer will help. Please, anyone know if after they reflash the board they will know that I flashed the phone in past? (flash counter was "2" )
Can u enter the download mode and try a reflash? I got the same Problem with my first ace 2. Under jellybean the touchscreen did not work anymore and gingerbread wasnt able to Boot (downgrading and upgrading With pit file worked a lot of times before). Then i tried „heimdall" (an alternative To Odin) and.... Totally bricked my phone... No download mode Or something and the phone wasnt able to turn on. But Samsung gave me a New phone and because the download mode didnt work they couldnt check the flash counter....
forgottnxd said:
Can u enter the download mode and try a reflash? I got the same Problem with my first ace 2. Under jellybean the touchscreen did not work anymore and gingerbread wasnt able to Boot (downgrading and upgrading With pit file worked a lot of times before). Then i tried „heimdall" (an alternative To Odin) and.... Totally bricked my phone... No download mode Or something and the phone wasnt able to turn on. But Samsung gave me a New phone and because the download mode didnt work they couldnt check the flash counter....
Click to expand...
Click to collapse
Found several methods to unbrick. Quite cheap (first 2 $ jig second 20$ jtag). My man at Samsung says that it is possible to read flash counter even at hard-brick state so Sammy service is a last resort
Will update if it works
They can check flash counter when phone is hard brick? Put cable from wall into ace 2 usb port - you burn it. Then they cant check.
piecho said:
Hello.
I've tried to update from leak 4.1.2 to final version but bricked the phone. Everything went well until restart. Progress bar in recovery went to the end, odin told that it's finished and it restarts the headset (green square) but the phone did not started.
Battery is OK, the phone does not start in normal mode nor in recovery ( +vol- +home +power) however, when i try to run recovery and the USB cable is plugged, my PC says that new device is found ("u8500 usb rom")
Odin dont see the phone.
Is there something that may help?
EDIT: ok, I found that in most cases only sending the phone to retailer will help. Please, anyone know if after they reflash the board they will know that I flashed the phone in past? (flash counter was "2" )
Click to expand...
Click to collapse
Hi, I had also hard bricked my phone some weeks ago. You can read it here.
http://forum.xda-developers.com/showthread.php?p=39350626#post39350626
Now is my phone back, 100% working. I was very surprised, the flash counter was still saying "2". Probably, they have no time to check it. Or for service station is it OK to have more business. I did not pay any money.