Related
Hi i had just flashed my phone back to standard rom with seus, and had rooted and was removing bloatware.
i used ADB Mask Controller for removing files because it was faster, but on the list of non essential apps i chose the ones a i wanted to get rid of, and accidentally clicked "delete all", because i thought it meant the all the files on the list. after that, i rebooted and the phone was dead, seus cant find it or anything, but now a day later when i press the power button, the led on the front blinks red a couple of times...
is it completely dead or is there a chance of getting it up and running again?
try flashtools
you should try bin4ry's flash tools it works most of times, there are a few tutorials around the forum but in general you just have to turn the phone off completely start flash tools select flash, select firmware and connect your phone pressing the back button just like in seus , also try posting problems like this in the general section, i know i'm no mod, but it helps keeping th forum clean , but don't sweat it, i think we all have done this when we started (i know i did XD)
Sorry if i posted it the wrong place, didnt think of other places cuz my bookmark leads me there.
Thanks for replying, but my problem is that i cant turn it on, when i press the power button, the only thing that happens is the led flashes red a few times.
Blinking red means that battery is empty. You can to charge it a bit with AC charger and then try to boot the phone.
yeah, sorry for the scolding , and i think it flashes red a few times because the battery drained, and flashtools is a pc program like seus, you don't have to turn your phone on, you connect it turned off, it is for flashing firmware to your phone and i recommended it because i think the reason your phone died is because of the missing apps, think of flashtools as a much MUCH better program for repairing your phone than the pc companion one or seus
also, here is a link to the main post for flashtools
http://forum.xda-developers.com/showthread.php?t=825664
edit: wiilweer beat me to it , and great port by the way, haven't tried it myself because my xrecovery is not working, but it looks great, specialy the 1000 in benchmark =O, excellent work men, thanks for the froyo port and your work
Thanks ill take a look at it again, hadnt seen the thread u linked now.
its been charging for a few hours and still just blinking... and it was at 100% when i started messing it up
maybe it is a stupid thing but...
have you tried
1) center hardware button + power for a few seconds?
2) disconnecting and reconnecting battery?
in the worst case you can try charging it with an external charger
but this means disassembling your mini:
http://www.ifixit.com/Teardown/Sony-Ericsson-Xperia-X10-Mini-E10i-Teardown/3124/1
Gx3 said:
maybe it is a stupid thing but...
have you tried
1) center hardware button + power for a few seconds?
2) disconnecting and reconnecting battery?
in the worst case you can try charging it with an external charger
but this means disassembling your mini:
http://www.ifixit.com/Teardown/Sony-Ericsson-Xperia-X10-Mini-E10i-Teardown/3124/1
Click to expand...
Click to collapse
Yea i tried that, but it didnt do anything.
maybe it just cant charge the battery. i could try to connect the battery from my gf's x10 mini
PressEsc said:
Thanks ill take a look at it again, hadnt seen the thread u linked now.
its been charging for a few hours and still just blinking... and it was at 100% when i started messing it up
Click to expand...
Click to collapse
The issue is not batery, its system files.
Do you have recovery instaled?
If no, download the flash tool and e10i firmware from this thread:
http://forum.xda-developers.com/showpost.php?p=10879519&postcount=2%22SE%20Firmware%20Files[/URL][/B]%3Cbr%20/%3E[URL=%22http://forum.xda-developers.com/showpost.php?p=10879528&postcount=3
Happy flashing.
Looks like its working now.
it wouldnt charge the battery, so i took the battery from another x10 mini, and then i flashed it. pc companion could find it and flash, with power from another battery
Dunno why it wouldnt charge the battery, maybe i deleted stuff that had something to do with power management.
Thanks for helping, i was already looking to buy another phone.
Thread belongs in the general section.
i have the very same problem !! ... WHAT did u dooo 2 fix this ?? am hopeless
try charging it and not with usb, if it wont start, try an external power source.
does it blink red when u press power botton?
Just want to share this, I do not create this procedure, and I forgot where I seen this.
1. Open SEUS, one it ask you to disconnect and connect. follow the next procedure.
2. Connect your X10 mini or Pro. Disregard SEUS Procedure
3. Press the Middle+Right+Power Button at the same time.
4. Once Screen Goes Blank, release all button except the middle.
5. now you could Update using SEUS.
Hope that help.
Sira. said:
i have the very same problem !! ... WHAT did u dooo 2 fix this ?? am hopeless
Click to expand...
Click to collapse
if the procedure above is not working you should try to recharge the battery or use one from another mini charged before trying that cause if battery is drained you won't be able to repair firmware...
http://www.ifixit.com/Teardown/Sony-Ericsson-Xperia-X10-Mini-E10i-Teardown/3124/1
PressEsc said:
Looks like its working now.
it wouldnt charge the battery, so i took the battery from another x10 mini, and then i flashed it. pc companion could find it and flash, with power from another battery
Dunno why it wouldnt charge the battery, maybe i deleted stuff that had something to do with power management.
Thanks for helping, i was already looking to buy another phone.
Click to expand...
Click to collapse
would u like 2 help me then >??
what is it doing?
I spent the whole yesterday afternoon and night and this morning trying to figure out what happened to my 'dead' x10 mini.
It has been lying there for over a year since I last tried reviving it.
Long story short, I forgot that I had flashed miniCM kernel on it. For some reason it just entered boot loop with Sony Ericsson logo and restarting and refused to charge. Then tried SEUS and Sony Update supposedly 'flashed' successfully, but I still could not get it to boot nor charge. Flashtool also was used to try a couple of other ROMs, until it dawned upon me I should flash back miniCM ROM since I think I had last used it year ago.
Voila it worked and I pressed BACK several times while the nAa logo came up. CWM was back. I jumped for joy... now I'm charging it and also downloading miniCM10 with gapps.
I really hope this helps - and that it would work for some of you out there in deep frustration. All the best! :good:
mcmlxxvi said:
I spent the whole yesterday afternoon and night and this morning trying to figure out what happened to my 'dead' x10 mini.
It has been lying there for over a year since I last tried reviving it.
Long story short, I forgot that I had flashed miniCM kernel on it. For some reason it just entered boot loop with Sony Ericsson logo and restarting and refused to charge. Then tried SEUS and Sony Update supposedly 'flashed' successfully, but I still could not get it to boot nor charge. Flashtool also was used to try a couple of other ROMs, until it dawned upon me I should flash back miniCM ROM since I think I had last used it year ago.
Voila it worked and I pressed BACK several times while the nAa logo came up. CWM was back. I jumped for joy... now I'm charging it and also downloading miniCM10 with gapps.
I really hope this helps - and that it would work for some of you out there in deep frustration. All the best! :good:
Click to expand...
Click to collapse
Looks like I went ahead of myself.
It managed to stay on in CWM... and I even managed to install update.zip and gapps, but once out of it the phone simply refuses to boot.
SEUS managed to flash stock ROM on it as well. However, even after leaving it hooked to the USB overnight (it only gets warm from this, not wall plug charger), it constantly looping in a flash mode (green LED) and then low batt mode (blinking red LED), it failed to boot up successfully on its own. After flashing the sony ericsson or custom ROM logo, it would go into a boot loop until the battery drains. Upon connecting back to wall charger, the first time it actually flashes real quick split seconds battery indicator of 2 out of 3, then go into the said boot loop again.
I really dunno if the battery's fried or did I do something wrong to hard brick it.
Disclaimer:
I have the same problem this guy have:
http://forum.xda-developers.com/showthread.php?t=1036327
But no one in the thread was able to understand him, so I'm trying to open a new thread to organize the thoughts (there are too many people with too many problems posting there).
What happened:
I have a 1-month-old Defy. On the 2nd day I already had it rooted, running froyo (with Pays ROM), overclocked, undervolted and all this stuff. Three days ago, suddenly, it started to FC apps randomly. So I wiped. Then it became stuck on M logo. No big deal.
I tried then to reflash the SBF via RSDLite, but for some reason I only had the previous SBF (3.4.2-155-2) and my phone was running on 3.4.3-11. Don't know if it has downgradeability issues, but I couldn't flash it. It threw some checksum errors in the process and wasn't able to finish the process. Then my phone became "Code Corrupt". I was still able to see it in RSDLite. No big deal.
I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal.
I read about the MacGyver method, but prefered instead to use a universal charger to charge my battery. Was charging all night, seem to work on other defy (tested it later). But, now, my phone makes no response to battery insertion. Not even power+vol up, nothing. No white led, no bootloader, no code corrupt, no nothing. Ok, that's a big deal.
If I connect it to USB, nothing happens. No driver instalation, no device recognized, no RSDLite, no bootloader, no white led. Nothing.
The only response I have from the phone is: if I pull the battery and put it again while connected to USB, the computer will make an USB connection sound, then 2 seconds later, it makes an USB disconnection sound. If I open the device manager, it shows the Motorola Device for 2 seconds (OMAP something) and then it desapears. So I'm not able to see it in RSDLite.
I tried even to power up the phone with the MacGyver-crafted USB cable (with and without battery inserted together), but the computer response is the same. That is the only thing that makes me believe that my Defy isn't entirely dead. But isn't much useful after all.
Hope I explained it well. I'm one of those guys who doesn't speak english well, so I hope you guys understand me . Thanks in advance.
I would really like to be helpful, but it looks, that you tried everything. Only one thing. Try to check the battery voltage and if you can, try another battery in your phone. The charger could broke your battery, even if it one time worked in another phone.
Try reinstall usb drivers, rsdlite, different usb port, and different pc.
@peetr_
The battery seems to still work, as putting it in the phone makes it to be recognized (for 2 seconds) on the PC. Also, the phone seems to get a little warm while with the battery.
@ABC_Universal
I tried. Installed all the drivers in another PC I have here and tried the same methods I said before. Same results.
If you're planning to dumb the phone into a dumb site.. let me know when and where...
Ok... you need to narrow down the possibility here by putting another full charged battery and see if the phone do get connected status via PC. External charger might just toast your battery if you read carefully your entire story back starting from this line "I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal."
External charger might giving out totally different voltage/current rating from the defy own charger.
im having the same issue, did you solve it?
im having the same issue, did you solve it?
try putting a different Defy's battery, doesn't work just give it for RMA... you'll get a replacement. looks like a hardware problem to me...
You have tried the McGyver-trick?
I tried using another battery in it and didn't work. I was far from a computer when I tried, so I didn't check if I was able to connect it to PC (even if the screen was totally black). But if it was a battery problem, I was expecting at least the bootloader to appear, but still nothing happened.
I took it to RMA two weeks ago. Here in Brazil they take too long to return it =/. Still waiting.
skattegat: I tried. With and without battery inserted together. Both cases, I was only able to listen the USB connection start and end, 2 seconds later. I know the cable was working because even without battery, when I touch the wires, I was able to listen the usb connection sound.
Ok. At least you have the time now to enjoy your sunny weather in Brazil...
RSD lite sucks... Well it doesn't suck but it refuses to work anymore no matter what I do!
Use sbf_flash in linux and it should do the trick! PM me if you need help
First flash the sbf. Then enter stock recovery and do the recovery from there. Flashing does not wipe cache. But after the flash the recovery will do the wipe automaticly.
Sent from my MB525 cm7quarx
Just a follow up:
My phone returned today from the warranty. Is fully working now, but I noticed the IMEI has changed. So I guess they changed the entire circuit.
It's not helpful for those who have the same problem, but I'm happy again
i have problem too..
I made a mistake in ROM CM7: I "install the 2nd init". and the results stuck on the boot logo .. : (
I finally went into the boot loader, then flash again use 3.4.2_177 SBF-005_NORDIC (do not wipe the data) .. remain stuck at the boot logo. and I try to use flash SBF-Stock.UKTmobile 3.4.3_11 (not wipe the data) and the results .... still stuck>> it's just an animated logo appears only.
AND THEN ---------------------------------
for this case:
I want to get into stock recovery:
1. defy turn off, turn the power button + volume down (hold a while)
2. logo appears>> android +! (the menu does not appear anything)
3. and I do not know anymore what should I do: (
please help me Quarx
thanks before
Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Fotogravin said:
Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
it's work..!! sorry i ask same question on other thread.
i'm so confuse
makasih gan
hey omneon are you able to solve your problem..plz help me man mine defy is stuck on m logo. same problem like your..
I just rooted my HTC Desire and installed CM7 on it (loved it on my HTC Legend). But suddenly today, after I turned Wifi on, it started rebooting all the time, couldn't do anything to stop it. I thought "Hey, there was the radio flash thing in the tutorial that I didn't do yet, I'll try that out" so I flashed the radio. Then I chose reboot system, but it just booted to a logo with an android coming out of a trash can, and looked kinda stuck there. So I took out the battery and plugged back in. Now if I try to turn it on, it'll just vibrate 7 times - no picture or anything. Also there's no LED when I plug it to the charger.
I had those 7 vibrates too.
Happened after i flashed the cm7 hboot over my stock hboot while trying to enter recovery. After i re-flashed my recovery using fastboot, everything worked again. What happens if you try to power up while holding down vol- ? Did you use fastboot or your phones recovery mode to install the radio?
I am not able to start in recovery or anything. I tried vol. down + power and back + power and no matter what I try, it just vibrates 7 times. I used the recovery mode to install the radio.
You could try to connect your phone via usb and check if fastboot discovers your device. If yes, flash hboot and recovery using fastboot. If not, well... i dont have a clue. Sorry :/
Computer discovers nothing when I plug in the phone.
Bad news when u pulled battery u interrupt the process n u now have a bricked device I would b very surprised if u managed to do anything
Pulling battery when doin a radio update is a BIG NO NO I'm sorry but ur stuck with a 400+ mirror now
Please look at this link
http://www.google.co.uk/m/search?site=images&client=ms-android-htc&hl=en&gl=uk&source=mog&aq=&oq=&aqi=&fkt=&fsdt=&cqt=&rst=&htf=&his=&maction=&q=android+radio+update#i=95
If that the image u saw when u pulled battery ur defo screwed
The Best Things Come To Those Who Wait
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
U need to copy the link for some reason its not showing up
Pm the link u have
The Best Things Come To Those Who Wait
Inrego said:
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
Click to expand...
Click to collapse
inrego
yes the image u just sent me is correct
the image showing would of ment it was installing the radio and because u pulled battery u have corrupt the flash and unfortuntly bricked ur device
i will look for a solution on the net but im not sure if ill find anythink sorrry
Inrego said:
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
Click to expand...
Click to collapse
heres a few thread about some pulling battery on radio flash
http://android.modaco.com/content/g...m/304368/can-the-nexus-one-be-bricked/#entry0
http://android.modaco.com/content/h...50/help-cannot-turn-on-after-flash-new-radio/
i cant find anythink about fixin the issue sorry
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Inrego said:
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Click to expand...
Click to collapse
all depends on if ur on warranty if u have receipt and warranty then all is ok with out them u stuck basically
sorry couldn't help more hopefully lesson learnt playing with radio is risky business
Yea got warranty and reciept and all that, so np there
Inrego said:
Yea got warranty and reciept and all that, so np there
Click to expand...
Click to collapse
nice one then just make up a bull**** reason ok well hope u get a replacement
Wait a minute...
Inrego said:
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Click to expand...
Click to collapse
For the record to help some of you out who ended up here Googling: I had a similar issue. My HTC Desire SV did not boot, and when charging, only had an orange flashing light, and the phone vibrated 7 times. I did 2 things that got it back up:
1) left the phone off for say 10 minutes (I read about overheating issues in general, although the phone did not feel hot).
2) removed the battery for a couple of minutes.
VERY IMPORTANT: for step 2: make sure to have the battery removed long enough to drain internal charge. I removed and installed the battery in a second or so at first, and still the phone did not boot. After leaving out the battery long enough, it booted again. It appears to me that the issue in my case was a rather big internal charge capacity which kept internal state (memory and/or CPU?) from booting. Hope this helps...
I just wanted to try the latest CM9 after locking bootloader for a return. It unlocked, flashed fine, rebooted a few times. I was going to relock it so I used "reboot to bootloader". It was charging, it shut down and never turned back on. Removing the battery didn't help either. When I connect it to the PC, it recognizes OMAP4400 but doesn't install any drivers. I don't see how it can be bricked as I just rebooted to bootloader. It's been charging for a few hours and I haven't touched it since. I'm going to try the USB Jig soon, any additional help would be greatly appreciated..
If you're unlucky, you've hard-bricked it, somehow...
Try pressing (Just) Volume down + power...
That also gets you into Oding mode...
If that don't work, then sorry... I wouldn't know any other solution. Try the jig, if you want, but it's not put, that it'll work.
Well, best of uck!!
Hope you fix it!
LG familyguy59
Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.
The phone will work plugged in without the battery in under normal conditions, and that it's showing up at all is a good sign.
Have you used fastboot before successfully? You may need to load drivers manually. This thread links a few different options you can try:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
freemini said:
Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.
Click to expand...
Click to collapse
My guess is that if it is showing as OMAP, it is a sign that bootloader is not working at all, I've seen some topics of panda boards (that use the same processor) with the same symptons when bootloader was lost...
Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.
freemini said:
Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.
Click to expand...
Click to collapse
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...
familyguy59 said:
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...
Click to expand...
Click to collapse
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone
freemini said:
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone
Click to expand...
Click to collapse
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^
familyguy59 said:
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^
Click to expand...
Click to collapse
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.
freemini said:
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.
Click to expand...
Click to collapse
Well, I wish best of luck, in that matter!
I still think, it's an unwanted brick, though...
I've looked, but can't find anything, whilst the phone is booted in Android, so, I'll restart it in a minute, and then have a look ^^
just not touching it until get my new sim) it's ok
hi all!
finally i've got a problem after flashing cm10a1, to be honest after trying to flash ivendor's camera patch on it
so i've got my phone not working
simple switch on, recovery and DL mode are not working while unplugged
when plugged into wall charger the screen light up for several seconds, the battery icon appears and then phone switches off.. and this show is repeated.
normal and recovery modes are unavailable but DL mode can be reached. i plan to charge it for an hour and then try odin flashing yes?
dimaka1256 said:
hi all!
finally i've got a problem after flashing cm10a1, to be honest after trying to flash ivendor's camera patch on it
so i've got my phone not working
simple switch on, recovery and DL mode are not working while unplugged
when plugged into wall charger the screen light up for several seconds, the battery icon appears and then phone switches off.. and this show is repeated.
normal and recovery modes are unavailable but DL mode can be reached. i plan to charge it for an hour and then try odin flashing yes?
Click to expand...
Click to collapse
You have no choice but to flash stock rom
Then reflash cwm. Cm10 and gapps
But I find cm10 really laggy
I restored it back to cm9 already
Sent from my GT-I8150 using xda app-developers app
last time that's happened to me, they change the motherboard (I'm lucky that under the warranty). I already tried flash stock rom with odin 5 times, but no luck. If flashing with odin didn't resurrect your phone, I recommended you to bring your phone to samsung service center, tell to them you encounter a problem when updating software via kies, if you lucky enough they will change your motherboard for free. goodluck!
loading DL mode when attached to usb..
chose everything, hit start...
the phone reboots and writes something like "rimware upgrade encountered an issue. Pleas select recovery mode in Kies and try again."
but after this it connects to odin!
i press start once again and it starts flashing.. and gets this..
but nothing changes, disconnected phone is dead, connected to usb/wall enters DL mode
planning a trip to service center...
hell yeah!!!!
took the battery out and took some beer from the fridge)
after drinking it put the battery in and loaded the DL mode
flashing with Odin succeeded!
just got stock 2.3 loaded, going to fridge for another beer)
rooting-flashing cwm-restoring cm9 backup to go)
thx for support guys!
Good news mate
Sent from my GT-I8150 using Tapatalk 2
you will be laughing, but i got it again..
i just put my sim card in..
and got the same thing again..
at least it now normally flashes via Odin..
maybe try to replace my sim?
Maybe, I dont really sure and know about that, I never experience that
Sent from my GT-I8150 using Tapatalk 2
Did you just un-bricked a phone? I mean i had that issue once too and got it sent back to the service centre. Congrats dude.
now recovered cm9 from backups
holding my sim in old nokia for calls)
going to carrier's office 2morrow for a free new sim card)
dimaka1256 said:
now recovered cm9 from backups
holding my sim in old nokia for calls)
going to carrier's office 2morrow for a free new sim card)
Click to expand...
Click to collapse
Holy ****! I though you phone had bricked for good. Lucky you managed come out of it. Hope you can exchange with the new sim and nothing bad happen.
Note; I hope you will keep on using Galaxy W
dunno how did it happen, but now it's ok, to be consistent i'll wait for a new sim, i have an old nokia for calls) and feeling myself a lucky bastard
sure i'll continue using my phone, i'm addicted to it a friend of mine has bought ace2 and i just hate it's pseudo-chromed stripe arount the front(the same as ace1)
now we even have alpha of JB and our custom CM10 on 512 ram will be better than sammy's JB on 768)) and it's a question of time when they get it.. especially in ukraine lol