Database Info

WIND G2X stock bootloader.

Alright xda, longtime lurker, crackflasher here.
Bought my G2x from WIND, gave the stock rom a tryout period which lasted a cool 2 days, and have been flashing since. Problem is my phone has been experiencing random shutdowns and reboots, screen bleeding and the standard nonsense, even before flashing; no matter what rom it is running even with my nandroid backup. It's kind of breaking my balls, and I've broken down and considered the possibility that my beloved phone is a lemon.
Now I'd like to see if I can get a replacement headset. Problem is that if I flash back to the stock bootloader it will look like a T-mobile phone and WIND will see that I've been buggering their TOS. Maybe I could send it straight to LG?
My main question is: is there anyway I can flash my nandroid backup along with the stock bootloader? Or am I just SOL?
Love this phone to death, and I accept the terms and responsibility of screwing with and trying new things. I should have returned the phone when I was having these issues on the stock rom... it was just so shiny and now I'm afraid I might pay a shiny replacement price as well.
Looking for a little empathy and answers if you can provide some.
Many thanks from maple syrup land,
- Zach

if you go to lg website and get thier mobile support tool. might have winds stock rom you can flash that should flash it all.

No linux support eh? Looks like I'm finding a buddy with windows...
Thanks for the advice!

Update:
Flashed new CWM via NVflash, phone only boots up into safe mode now, won't go to the CWM menu. I have a feeling I'm super boned, for one week, that was a fun 500 bucks, time to start saving Could LG's tool fix this?

talkingbird said:
Update:
Flashed new CWM via NVflash, phone only boots up into safe mode now, won't go to the CWM menu. I have a feeling I'm super boned, for one week, that was a fun 500 bucks, time to start saving Could LG's tool fix this?
Click to expand...
Click to collapse
It could possibly, it will do a factory flash, but only if the software recognizes the device.
Sent from somewhere with something using tapatalk

Found out what the problem was, I was on an older clockworkmod without ext4 support flashing ext4 roms.... whooops...
Flashed CWM 4 and had no issues with nandroid backup for a full charge cycle, thankfully.
Flashed EB and Trinity Kernel, undervolting like a beast with setcpu; no issues and some badass battery life. Went all the way to 0 and im charging to 100 to to reset the battery stats.
Hopefully after that it will be as smooth sailing as flashing goes
Screen bleeding be damned.
Thank you for your help!!!

I returned mine on 4th day cause to many random shutdown . I work at mobilicity and a customer said he bought g2x from T-Mobile and put cm7 no random reboots for him.

Got a random shutdown today, seems to happen when the phone is not in use, if im on it constantly, no problems. In my locker at work it just shuts off? wtf? Could be UV, I'll take it off for now.... One day left on warranty... ****.

[Q] Moto Defy Bricked :'(

Hi, I have had my moto defy for a while so I decided to root. I mucked around with root for a month or so and then run a custom rom (LiquidArc Gingerbread). That worked fine, for about 3 reboots.. then it got stuck on the Red M (I left it for 10 mins and it was still stuck).. so I ran RSD Lite v4.9 and flashed the Australia Telstra (my current provider) from: and - developers. com / sbf:defy.
RSD Lite told me it had passed, and then said to restart the phone, I did and now nothing... Black screen, EDIT: White L.E.D sometimes, no bootloader, bricked. It is still recognised in RSD and I have tried the same .sbf three times now but still no success.
I have read through http://forum.xda-developers.com/showthread.php?t=1066816 but I am not sure where to go from now.
If anyone could help me that would be super!
EDIT: I know cannot even get it detected in RSD Lite.. I have a White L.E.D as soon as I plug the phone into the computer... I have also tried the jump-start method with a spare USB cable I had..

I think I'm bricked too =/
Fastboot and RSD options both freeze/lock up on me.
I am able to get into recovery but my clockwork version 4.0.0.4 which is causing some SD Card detection issues.
Stuck in a bad way right now, can you get into both RSD and Fastboot options?

RSD does not freeze but it cannot detect the phone any more. It used to, and thats when I tried flashing three times, but now, nothing.

imnew,,,,,,

Please use the Q&A Forum for questions Thanks
Moving to Q&A

I have sent it in for repairs... They are going to phone me the cost of the repairs in a couple of days...

Look into this thread:
Motorola Defy > Defy Android Development > [DEV][ROM] CyanogenMod 7 (Android 2.3.4)
they have much xperience with these things

Sent the phone to Motorola..
I expected to pay for the repairs and would have done so happily, but it came back 10 days later free of charge with a fresh install of 2.2
I won't be messing with custom rom's for a while

wahaha...i'm done with motorola products now...you want to hear my story?
I bought motorola defy last year when it came out. I was very happy and so i continued flashing froyo which was blazing fast over Eclair...but my multitouch started giving me trouble. I sent it to motorola. They returned my phone after 2 months. YES 2 MONTHS !
They had all kind of reasons behind it...but when i got my phone back i was soo happy you can't imagine how i felt when i held it in my hands...but then i wanted to check other 2.2 roms as well if they would fix the multitouch problem but they didn't and one day, the phone started to react strangly, random reboots, not turning on, battery drain and all sort of things even with the stock rom...
I sent motorola my phone back again and i recieved it after a month...when i tried turning it on, it didn't turn on...so i had to send it back again for another month...and in the end i told them to keep their product and refund me...they did refund me but it took them another month to do so...
Motorola has a really poor customer service, i advice you guys to ask for refund and get Galaxy S, it goes for the same price now lolz

Maybe Worse Than Bricked :(

Hi.
I received my captivate today.
I updated to 2.3.4, but could not unlock, also, that was with errors.
Then i tried AIO 3 Button Fix (in pit selected pit.pit and in pda pda.tar) then start.
Update has been completed and my Captivate turned off.
Now it doesn't turn on, it is on battery and plugged in, but has no reaction.
Is there any solution? I am very worried...
Sorry for my English.

Read read read... your phone its now hard bricked... look for unbrickable mod in development section
Sent from my I897 using xda premium

I'm sorry to have to tell you this, but it sounds like you hard bricked your phone.
Here's why: you flashed 2.3.4, which is Gingerbread. This loaded the Gingerbread bootloaders onto your phone.
You then flashed the 3-button fix. Which flashed 1/2 of the Froyo bootloaders onto your phone.
Your phone now can't understand how to boot up with a hybrid of Froyo and Gingerbread bootloaders. This means you will need to either get JTAG service or apply the Unbrickable Mod.

I was waiting for my phone for 3 weeks... i can afford myself neither of them, as i live in Georgia (Republic Of) and can't send my phone anywhere.
is this tutorial for hard brick phones?
Thanks.

The closest thing to a tutorial that a user can do to their phone is the Unbrickable Mod. It's a hardware modification that puts the phone into a development mode, that then allows the bootloaders to be rewritten to the phone.
In terms of cost, it's relatively inexpensive - you'll just need a soldering iron, some relay wire, and steady hands. Or, if you have an electronics store near you, you could see if they would be able to do it for you.
Beyond that, it depends how you got your phone. If you bought it from a retailer, and not Ebay, you could try and see if you can take it back. If you got it on Ebay, your options are limited to JTAG or Unbrickable Mod.

So, what is the end of story? Did you unbrick your phone?

Won't turn on and no charge light

Just sent my HTC Sensation off for repair under warranty due to this fault :
Running OpenSensation nightly 20120810 and TamCore 3.0.40 without any issues and updated the nightly every 2-3 days with no issues. had the phone 12 months and had it s-OFF and unlocked about 4 hours after buying it. At that time running CM7 as that's all there was, updated to various ROMs until I settled on OpenSensensation (tried CM9 a couple of times for a few days but prefer OpenSensation). All ROMs installed fine over the past 12 months
Installed Kingdoms and Lords off Google play (huge game 200MB data download via wireless), after first game phone froze and reset. So I reduced the overclock, game running fine. Had another game later on in night playing for about 15 minutes. Phone froze again, switched itself off and didn't come back on again !!!!
Tried charging it thinking battery was flat, no charge. Took battery out as it was an Anker 1900mah just in case it had blown. Put original HTC battery back in, no charge light, nothing. Took battery out and left it out 2-3 hours as suggested on 'net as it 'might' help
No charge, tried another USB lead plugged into desktop. Still no charge .... oh crap
Took to T-Mobile shop I got phone and explained situation, forgetting to mention it was running custom ROM, they tried. Still no charge, no reaction in shop. Zero, zip
They sent it off for inspection/repair yesterday under warranty and said it should take 2-4 weeks
It had been running custom firmware since the day I got it on contract and has never caused me any grief, apart from some roms running better than others while I made a choice which ROM to stick with
Question I'm asking is can HTC still test the phone even though its not taking a charge or I assume not powering and just froze and died, assuming the motherboard is fine does anybody know if they use test points that bypass the USB socket to power it up
And how can just playing a legitimate game downloaded off Google Play freeze the phone and shut it down never to power up again
I'm guessing the possibilities of a faulty USB charge socket, faulty power switch or fried CPU/GPU/motherboard considering it just froze and died
I used it as a phone but did play games quite a lot during the day when I had a few minutes while not working, and had it overclocked to around 1625-1728 which it ran stable at without overheating
If they send it back refusing to touch it due to finding custom firmware on it I'm looking at the Samsung galaxy SIII over the HTC Nexus One simply because the Samsung has a removal battery and additional microsd card slot where for some reason I assume is to make rooting more awkward the HTC has a hardwired battery and NO extra sim card slot. I was looking to replace it when my contract expired in February but if they refuse to fix it citing custom firmware (even though it has been working perfectly for 12 months running various custom firmware) I have no real choice but to buy out my contract and get a new contract. Bummer

Hmmmm,
Reading a few postings it appears there is a possibility that the motherboard is fried somehow, or a 'hard brick' through a bad ROM install ... I wasn't updating and firmware, not updating any ROMs
Just playing a game downloaded and installed off Google Play, but if it means the motherboard is fried then at least it means HTC will have to replace it as 'faulty' so saving me the upfront cost of buying out my contract thas has 6 months to run

Actually if you overclock the device or flash a kernel htc doesn't have to replace anything.. by "playing a game downloaded from google play" you mean "playing a game downloaded from google play on a device controlled by custom drivers which clearly make your device out of warranty". So I'm not sure.. altough it's possible that it's not the fault of the kernel but the mainboard had some issues. They are able to test the charging port and the main board seperately. Let us know abouth the end.

It would interesting to see HTC's response either way so I'll report back once they have a look at the phone
As I don't have a loan phone at present so have no phone until they get one back from customers having their phone repaired, I have to use the 'net to check on the status of the repair via the T-Mobile website

I got my phone back yesterday with a new motherboard, under warranty
Now seriously struggling to get it to S-OFF as its running HBoot 1.27 as teh guys in the shop also said its had "new firmware upgraded for you", or to prevent me from getting S-OFF
Tried the all in one kit, tried the 'official' unlocker method from HTC. Keep getting the same error about token mismatch when trying to unlock the bootloader
Reading postings from here and there it's suggested that as the motherboard has been changed and a new IMEI, the IMEI and hardware serial numbers now don't match so causing a mismatch between number so the unlock obviously fails
Looking at trying the JB_Bear flash wire trick when I have more time to see if that work with replacement motherboards, so any suggestions as I'm stuffed and want S-OFF as well as full root again. Unlocked it when it was running HBOOT 1.18 was a doddle but now its a pain and T-Mobile branding is pants so want to be able to have my phone how I want it without all the crappy restrictions
Unless somebody can S-OFF and root for me in the North-West Lancs area without sending the phone away, I'll have to do a bit more digging to see what I come up with

thescrapyard said:
I got my phone back yesterday with a new motherboard, under warranty
Now seriously struggling to get it to S-OFF as its running HBoot 1.27 as teh guys in the shop also said its had "new firmware upgraded for you", or to prevent me from getting S-OFF
Tried the all in one kit, tried the 'official' unlocker method from HTC. Keep getting the same error about token mismatch when trying to unlock the bootloader
Reading postings from here and there it's suggested that as the motherboard has been changed and a new IMEI, the IMEI and hardware serial numbers now don't match so causing a mismatch between number so the unlock obviously fails
Looking at trying the JB_Bear flash wire trick when I have more time to see if that work with replacement motherboards, so any suggestions as I'm stuffed and want S-OFF as well as full root again. Unlocked it when it was running HBOOT 1.18 was a doddle but now its a pain and T-Mobile branding is pants so want to be able to have my phone how I want it without all the crappy restrictions
Unless somebody can S-OFF and root for me in the North-West Lancs area without sending the phone away, I'll have to do a bit more digging to see what I come up with
Click to expand...
Click to collapse
for replaced mother boards ..there is a different version of jb ..check my soff guide ..link in my signature

Will let you know how it goes, thanks

Managed to get S-OFF using your method after a few tries did nothing so started making me nervous I was about to fry my new replacement motherboard, eventually it beeped and did the S-OFF by following yours steps to the letter
Problem is now, I want to remove the ***LOCKED*** but every recovery.img I try fails with a token error, which reading about it is down to teh bootloader apparently still locked
Also changed the HBOOT to your JB_HBOOT with no difference, still S-OFF but ***LOCKED***, so can't get the next step to get a fully rooted fully unlocked system so I can get back to where I was before the original motherboard died
I'm now looking at installing CM10 JellyBean 4.1 by KANG, I used to run OpenSensation CM9 quite happily and nightlies with zero issues installed a few ROMs over the past 12 months with a couple of minor issues I solved myself with reboot loops and ROMs getting confused and having to wipe the entire phone, plus when I wiped the core by accident during yet another ROM install .... that was fun to solve. Took a couple of days of reading about that one
Anyway, any suggestion as to how to get full unlocked or at least so I can install 4EXT recovery and SuperUser to get a bit further on the custom ROM route and get a phone that's what it should be instead of crippled by T-Mobile UK
Thanks for your help to get where I am so far

thescrapyard said:
Managed to get S-OFF using your method after a few tries did nothing so started making me nervous I was about to fry my new replacement motherboard, eventually it beeped and did the S-OFF by following yours steps to the letter
Problem is now, I want to remove the ***LOCKED*** but every recovery.img I try fails with a token error, which reading about it is down to teh bootloader apparently still locked
Also changed the HBOOT to your JB_HBOOT with no difference, still S-OFF but ***LOCKED***, so can't get the next step to get a fully rooted fully unlocked system so I can get back to where I was before the original motherboard died
I'm now looking at installing CM10 JellyBean 4.1 by KANG, I used to run OpenSensation CM9 quite happily and nightlies with zero issues installed a few ROMs over the past 12 months with a couple of minor issues I solved myself with reboot loops and ROMs getting confused and having to wipe the entire phone, plus when I wiped the core by accident during yet another ROM install .... that was fun to solve. Took a couple of days of reading about that one
Anyway, any suggestion as to how to get full unlocked or at least so I can install 4EXT recovery and SuperUser to get a bit further on the custom ROM route and get a phone that's what it should be instead of crippled by T-Mobile UK
Thanks for your help to get where I am so far
Click to expand...
Click to collapse
for flashing eng-hboot aka changing from LOCKED to Juopunutbear
check the troubleshoot point #3 solution in my soff guide ..its explained there
and for thanks ..there is a button to say that

All sorted, now running the latest nightly of Kanga JellyBean 4.1 and full rooted and back to how it was before the motherboard dies, apart from running Android 4.1
Also feels much smoother and much faster, even though its only running the default slight overclock that Kanga sets as teh default, so might leave it at that as it feels faster than previous when running OpenSensation 4.03
Great stuff

[Q] Should I format internal SD before ODIN?

I've basically had it with my Skyrocket, or rather, the Skyrocket that I have. It has always had atrocious battery life, exhibited weird behavior (like today when it lost nearly 20% of its battery in about 2 hours, and claiming the PHONE component was the prime culprit when I hadn't made a phone call) and also even after I unlocked the damn thing I still can't get it to force to 2G (yes I'm using an Unlocked RAT as well.) I'm still under warranty so I want a different one even if it is refurbished.
Anyways, I know the whole deal of using ODIN to return to Stock and making sure the Flash Counter isn't tripped, but in this day and age I'm paranoid about tech stuff having personal stuff getting stolen, so I'm tempted to wipe out the internal SD card, but I don't know if this is necessary and/or potentially harmful. Can I boot into Recovery and have it format my internal card, then ODIN back to Stock, or will this just cause more problems than it's worth?

dvandam said:
I've basically had it with my Skyrocket, or rather, the Skyrocket that I have. It has always had atrocious battery life, exhibited weird behavior (like today when it lost nearly 20% of its battery in about 2 hours, and claiming the PHONE component was the prime culprit when I hadn't made a phone call) and also even after I unlocked the damn thing I still can't get it to force to 2G (yes I'm using an Unlocked RAT as well.) I'm still under warranty so I want a different one even if it is refurbished.
Anyways, I know the whole deal of using ODIN to return to Stock and making sure the Flash Counter isn't tripped, but in this day and age I'm paranoid about tech stuff having personal stuff getting stolen, so I'm tempted to wipe out the internal SD card, but I don't know if this is necessary and/or potentially harmful. Can I boot into Recovery and have it format my internal card, then ODIN back to Stock, or will this just cause more problems than it's worth?
Click to expand...
Click to collapse
Yes you can I have reformatted my internal several times before using Odin personally I just mount our to the pc and format that way. Spector7 has done they CWM using format emmc and said out worked fine but emmc is at your own risk I just format they pc
Sent from my SAMSUNG-SGH-I727 using xda premium

Okay next stupid question...
Would it not be easier to just install a Stock Rom then install Stock Recovery to get my phone back to regular state as mentioned here after I do a formatting, as opposed to going through all the ODIN stuff, which, if done wrong, can trip the flash counter more easily and thus leaving me with some explaining to do at the AT&T store?

dvandam said:
Okay next stupid question...
Would it not be easier to just install a Stock Rom then install Stock Recovery to get my phone back to regular state as mentioned here after I do a formatting, as opposed to going through all the ODIN stuff, which, if done wrong, can trip the flash counter more easily and thus leaving me with some explaining to do at the AT&T store?
Click to expand...
Click to collapse
I would Wipe after stock rom modem and recovery that way if it bricks att will need to fix it
Use the CWM method.

Well I returned to stock and am planning on going to AT&T after work to demand a replacement. Maybe I can use my charm and wit to negotiate into getting an upgrade to a S3 if they don't have any Skyrockets in stock, but then again I'm a guy who plays the lottery, so I'll keep my expectations in check. Worst case scenario and they just turn me down I'll brick the damn thing intentionally and then say "Oh it stopped working after the most recent update." Wish me luck.

TBQH, I'd just brick it in Kies by restoring to 2.3.5 and unpluggig during the ICS update. Tell them that you were updating to 4.0, and the thing wouldn't turn back on afterwards. If nothing else, AT&T will help get things with Sammy in order.
I wouldn't even bring up the other problems
Sent from my SGH-I727 using Tapatalk 2

T.J. Bender said:
TBQH, I'd just brick it in Kies by restoring to 2.3.5 and unpluggig during the ICS update. Tell them that you were updating to 4.0, and the thing wouldn't turn back on afterwards. If nothing else, AT&T will help get things with Sammy in order.
I wouldn't even bring up the other problems
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Sorry I have no idea how Kies works (never had a need to use it as I just flash everything) That's a program you install on your CPU right and then do the update by downloading in Kies and then plugging the phone into the CPU to download to it?

dvandam said:
Sorry I have no idea how Kies works (never had a need to use it as I just flash everything) That's a program you install on your CPU right and then do the update by downloading in Kies and then plugging the phone into the CPU to download to it?
Click to expand...
Click to collapse
Correct go too the android development thread and check out Vimcom stick alright so just check it or its not bad
Sent from my SAMSUNG-SGH-I727 using xda premium

Looks like I may have given myself a reason to return it before I could intentionally brick it via Kies..
I just ODINed back to stock and now the device is stuck in a boot loop. I double checked the download mode and it didn't trip the counter, so at least they can't accuse me of messing with it in that regard. I do hope that a new phone helps my problems, because quite frankly it's hard to stick with the Skyrocket in general after seeing the smoothness of the Galaxy Nexus (which my wife has) or the robust beast that is the SIII. I swear though if the Nexus 4 had LTE I'd have already ordered it, paid for same day shipping, and taken the entire day off to be able to play with it. Oh if ONLY they had included LTE... I would have paid $100 extra for that even..

Update on this..
Brought it to my local store, only to be referred to the one and only repair center in the state. They said they were going to try and restore the stock firmware onto the device. I started to get worried as I thought they may be able to undo what I had done. About 15 minutes later they gave up. I think they were trying to use Kies as opposed to ODIN. I didn't want to give on that I really knew my way around the phone and may have done the work myself. Anyways they gave me a new phone and sent me on my way.
I flashed CM10 M2 on my device again. As far as battery life goes.. it seems pretty comparable to what I had before. At this point I don't feel like going back to get yet ANOTHER Skyrocket. I suppose I'm just stuck with this battery life forever.
On a side note, even though for many of us this may be common knowledge, for everyone else, if your device is bricked, whether intentional or not, MAKE SURE YOU WIPE YOUR FLASH COUNT BEFORE BRINGING IN FOR SERVICE! The first thing the tech people are going to do is put your device into Download mode and hook it up to a CPU to flash original firmware. Unless they're COMPLETELY ignorant or don't care, if they see that custom Rom counter tripped then they're not going to touch your device.

dvandam said:
Update on this..
Brought it to my local store, only to be referred to the one and only repair center in the state. They said they were going to try and restore the stock firmware onto the device. I started to get worried as I thought they may be able to undo what I had done. About 15 minutes later they gave up. I think they were trying to use Kies as opposed to ODIN. I didn't want to give on that I really knew my way around the phone and may have done the work myself. Anyways they gave me a new phone and sent me on my way.
I flashed CM10 M2 on my device again. As far as battery life goes.. it seems pretty comparable to what I had before. At this point I don't feel like going back to get yet ANOTHER Skyrocket. I suppose I'm just stuck with this battery life forever.
On a side note, even though for many of us this may be common knowledge, for everyone else, if your device is bricked, whether intentional or not, MAKE SURE YOU WIPE YOUR FLASH COUNT BEFORE BRINGING IN FOR SERVICE! The first thing the tech people are going to do is put your device into Download mode and hook it up to a CPU to flash original firmware. Unless they're COMPLETELY ignorant or don't care, if they see that custom Rom counter tripped then they're not going to touch your device.
Click to expand...
Click to collapse
Did you get a brand new phone or a refurbished?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Not sure. I'd guess refurbished as they basically had buckets in on their wall that had a wide assortment of various phones for replacement. Overall though I'm not going to fight over refurbished vs getting a brand new one. I could just as easily get a bad refurb as I could get a lemon new.
Honestly at this point I'm more annoyed with the lack of "snappiness" of this phone. As I said it doesn't help that my wife has a Galaxy Nexus (which quite frankly even ran ICS better than my Skyrocket ever did) so to see how my system is "supposed" to run and not have it just bugs me. Seeing the Galaxy S3 in action makes me so envious with that gorgeous screen and snappy response just makes me regret more and more that day nearly a year ago when my 21 month old for grabbed my Nexus One and I didn't tackle her before she threw it down the stairs. Being forced to buy a phone well before I wanted to buy a new one as I wanted to wait for LTE deployment in my area, (which I STILL don't have BTW) and now regretting a year later just... ugh.. For all the crap Apple gets with their phones, at least it's easy to pick out which phone of theirs is the best available at any given time, and (assuming they don't change to the iPad release schedule) you can feel confident it'll stay top of the line for a year.
Sorry for the /rant there

dvandam said:
Not sure. I'd guess refurbished as they basically had buckets in on their wall that had a wide assortment of various phones for replacement. Overall though I'm not going to fight over refurbished vs getting a brand new one. I could just as easily get a bad refurb as I could get a lemon new.
Honestly at this point I'm more annoyed with the lack of "snappiness" of this phone. As I said it doesn't help that my wife has a Galaxy Nexus (which quite frankly even ran ICS better than my Skyrocket ever did) so to see how my system is "supposed" to run and not have it just bugs me. Seeing the Galaxy S3 in action makes me so envious with that gorgeous screen and snappy response just makes me regret more and more that day nearly a year ago when my 21 month old for grabbed my Nexus One and I didn't tackle her before she threw it down the stairs. Being forced to buy a phone well before I wanted to buy a new one as I wanted to wait for LTE deployment in my area, (which I STILL don't have BTW) and now regretting a year later just... ugh.. For all the crap Apple gets with their phones, at least it's easy to pick out which phone of theirs is the best available at any given time, and (assuming they don't change to the iPad release schedule) you can feel confident it'll stay top of the line for a year.
Sorry for the /rant there
Click to expand...
Click to collapse
You're confused.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2