Database Info

[Q] Should Verizon replace my phone?

I was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.

Should verizon replace your phone after you borked it? I think you already know the answer

xebryus said:
I was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.
Click to expand...
Click to collapse
long of it, no they shouldn't. will they? who knows, depends on if you tell them the truth or not.

Should they? Technically no. Will they? Sure. They would be happy to.

but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt

satseaker said:
but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt
Click to expand...
Click to collapse
Honestly, it doesn't matter if anyone can prove the software did it or not. He voided his warranty by rooting. But they likely will replace his phone, driving up the costs for future phones.
You rooted your phone. Take it for what it is...a non-warrantied phone.

Touchy
I will start off by saying I don't have a solid answer but being as it is a hardware problem they "should" fix it. Will they? Probably not. They'll take one look, see it's rooted, and tell you that you broke it by tampering with it. All bets are off as soon as the phone is rooted...unless you can unroot and take it in I think you're in trouble but since the button is broken you can't do anything with it. Good luck and let us know what you were able to get done.

I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?

This is why you should have ADB installed and working on your computer. Hook up the phone via USB, get into ADB and reboot into recovery. There are a few threads out there for ADB you should be able to find them using Google, hopefully that will be able to help you.

If you can get into the boot loader with and then you might be able to save your phone.. Maybe, not clear take your as card out and import the rhi, they might work...
Sent from my ThunderBolt using XDA App

if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.

xebryus said:
I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?[/QUOTE
Did you try BOTH volume buttons at the same time? This got me to bootloader.
Click to expand...
Click to collapse

Just say you tried to install the last update and your phone wont boot now. They won't know the difference.

dpham00 said:
if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.
Click to expand...
Click to collapse
Caused by rooting or not, there is NO warranty once a phone is rooted. Has nothing to do with what caused the malfunction.
ADB reboot bootloader or recovery should work though, as long as he catches it with the right timing during the loop.
Sent from my ADR6400L using XDA App

Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.

you're probably aright since they might just get it and toss it in the "to be refurbed" bin. It costs a lot of money to test every return. Good luck and let us know how it turns out.

xebryus said:
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
If they do find out, they will charge you. Don't know if they will, but be prepared for the worst.
Sent from my ThunderBolt using Tapatalk

Yes, they get broken down abd only really check for water/physical damage
Sent from the Swag ThunderBolt ADR6400L with some GingerLove (Gingeritis 1.0) using XDA Premium App
Must Watch Before Any Forum Post http://goo.gl/b4IJJ

xebryus said:
Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
Congrats on getting a new phone I guess.
I have noticed Verizon has been VERY accomodating with these phones. One call is all that's needed to get a new phone. Im guess they're so generous because they devices have been so finnicky so far and they just want to keep people pleased for now.
I envision them cracking down hard sooner or later though. They're not stupid. They've already come down on tethering and such, so it probably wont be long until they get hardcore on replacements.

My son works for VZ...
and he takes your calls... and this is what he told me. Anything covered under insurance (Asurion), they really don't check/don't care about rooting. VZ, on the other hand, will look pretty extensively if it's covered under the warranty. They will look for rooting or anything else that would break warranty coverage.

qhusb_dload brick after bad vold.fstab edit

Sorry if this is the wrong place to post - just wanted to share my unpleasant experience.
I've bricked my phone in a peculiar way - it appears to be a hard brick, non-responsive to any buttons. Plugging in to the computer gets me the dreaded qhusb_dload QPST download mode. Not a good sign.
It wasn't due to faulty ROM flashing, either. I made a bad edit to /system/etc/vold.fstab fiddling with the way the internal and external SD cards get mounted - mmc1 instead of mmc2. After one reboot, I had some sd card corrupted errors. Proceeding to format the card may have been my fatal error. By the second reboot, I was bricked. D'oh. I imagine I had accidentally mounted a partition of the internal emmc that is critical to normal operations, then tried to wipe it.
From what I've read, a USB jig won't do much good, but it's worth a try.
Anyone messing around with their /system folder, be warned.

That's sux, but on a good note, $50 and a little waiting will get your phone back, or you could just warranty that sucker ;-) give more refurb units to some other xda members lol

I sense another refurb sale on ATT.com. Sorry to hear about that, sounds bad. No guts no glory right?

I purchased this as a refurb, too. The cycle continues...
Not sure how the whole exchange process will work in this case. I mean, I can exchange for a different phone, or a new Skyrocket and pay the difference, but I really had my heart set on a cheapo skyrocket. Perhaps if I take this up with Samsung instead?

Ur 90 warranty is over already? That sux then. I personally would pay $50 and get it de-bricked, its the cheapest/best option.

I didn't expect much in the way of warranties because I purchased this refurbished. With Samsung customer service I didn't have much luck. However, I just got off the phone with AT&T, and they're overnighting me a replacement, which is cool. They have a 30 day policy on any web store items, so I'm covered. Anyways, lesson learned

check this thread, please: http://forum.xda-developers.com/showthread.php?t=1522351

RussianBear said:
check this thread, please: http://forum.xda-developers.com/showthread.php?t=1522351
Click to expand...
Click to collapse
Are you in thw process of bringing that to the skyrocket?

silver03wrx said:
Are you in thw process of bringing that to the skyrocket?
Click to expand...
Click to collapse
we need all the help we can get. just a bunch of curious noobs, ya know
the main discovery we did with sensation was to make the emmc visible to any pc it's connected to, then overwriting whatever was messed up (like the hboot) with a stock version of that file.
in theory, you should be able to do this to any phone running on a qualcomm chipset once it's in the qhsusb_dload mode. still lots to test, but anyone is welcome to participate, of course!

Do you have a skyrocket that your testing on?
Obviously you know its much different then hboot
On htc.

silver03wrx said:
Do you have a skyrocket that your testing on?
Obviously you know its much different then hboot
On htc.
Click to expand...
Click to collapse
nope, just sensation. they both run on a qualcomm chipset though, so i'm just speculating here.
the bricks we're "saving" right now are for people that executed s-on without fully reading the instruction, thereby leaving them in qhsusb_dload mode. your cases might be specific to a different area, but the principal is still the same:
find what is messed up and replace it with the correct file via open emmc

Big progress made for APQ8060 and MSM86xx processors. Sensation hard brick solution coming very soon and SkyRocket/T-Mobile Galaxy S II solutions already solved...

What's this I smell? Possible de-brick
Sent from my SAMSUNG-SGH-I727

I also experience this problem on my xperia L
I messed up with vold.fstab and now my phone can't enter flashmode or it doesn't turn on also

amnher said:
I also experience this problem on my xperia L
I messed up with vold.fstab and now my phone can't enter flashmode or it doesn't turn on also
Click to expand...
Click to collapse
i have the same problem xperia miro
any updates ?

[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

Verizon S3 Wont turn on after proper rom flash

Ok, Phone was rooted suscessfully, Unlocked bootloader, was running a 4.2.2 Rom.
Buddy found the MS HD 10.0 Rom and wanted to try it. US phone. I looked at all the details and didnt see anything about it not being compatable.
Flashed the rom, went through all the GUID steps selected roms , styles etc etc, and It said completed "click here to reboot" So i did so.
Went black screen and now wont DO ANYTHING. cant get into download mode, recovery, a vibrate out of the phone, anything. Took the battery out for a min and plugged it in and get the orange light. Put the battery back in and STILL NOTHING. Please help! Buddy phone and he needs it

It's best to think of the international gs3 and us gs3 as two different phone. Because they are.
Flashing firmware meant for a different phone will result in a hard brick. Sorry

corbn89 said:
It's best to think of the international gs3 and us gs3 as two different phone. Because they are.
Flashing firmware meant for a different phone will result in a hard brick. Sorry
Click to expand...
Click to collapse
So its Done? :/..... He has a best but warranty . any way they can tell its been software tampered with at this point? So he can get a free one lol

As was said above, MS HD ROM is for the international S3 (i9300). It is important to make sure you are in the right forum before downloading and flashing any ROMs. Unfortunately, many still make this mistake. The only way to fix is to replace the phone or send it to these guys:
http://mobiletechvideos.mybigcommerce.com/

You can try and send it for JTAG repair (places like mobile tech) and they may be able to revive it.
But I'm not sure if places like best buy can positively confirm it was a bad flash if the phone is completely dead. I wouldn't think so but I'm not 100%

corbn89 said:
You can try and send it for JTAG repair (places like mobile tech) and they may be able to revive it.
But I'm not sure if places like best buy can positively confirm it was a bad flash if the phone is completely dead. I wouldn't think so but I'm not 100%
Click to expand...
Click to collapse
How about the Download Jig

If you are talking about Black Tie Insurance from Best Buy then you are fine and this is not fraud. Insurance is for boo boo's like dropping, smashing, flashing failures, drop in the toilet...all of that. They do not care if phone was rooted or misflashed. Insurance is not fraud, trying to get free replacements from the carrier under warranty by lying is.

[Q] T-Mobile LG Optimus F3 Forum?

Okay, so I know this phone doesn't exactly win the spec war, but it's awesome and would make a fantastic rooted phone. Unfortunately there isn't a forum here on XDA for the device (either because it's too new or there isn't a demand for it)
Do you guys think a forum will be made for this device? It'd be nice to at least have a place to say what root methods DON'T work (I've tried a few)
Thanks for the help, XDA rules!

I second this. I am planning on buying a new phone and after researching numerous phones out there based on my tastes and constraints, I think this phone works very well (another is Samsung Galaxy Exhibit 2). One flaw that I heard is the amount of storage in this phone is around 4gb. Without a way to put apps on an external SD card (which I believe would require a custom ROM), the storage would probably fill up pretty quickly. So it'll be great if XDA opened a forum for this phone.
As a side note if anyone can point to other devices that fit my needs I would be grateful:
- Less than 4.2" screen (preferably 4").
- Android only
I don't have any financial constraints or any favorite companies.
Thanks!

What root method did you find worked? Did you try framaroot? Also have you found any Roms?
Sent from my SPH-D710VMUB using Tapatalk 2

bbradf44 said:
What root method did you find worked? Did you try framaroot? Also have you found any Roms?
Sent from my SPH-D710VMUB using Tapatalk 2
Click to expand...
Click to collapse
I used Motochopper, worked like a charm. make sure you have the LG Optimus f3 drivers on your computer.(found on LG website)

habitforming said:
I used Motochopper, worked like a charm. make sure you have the LG Optimus f3 drivers on your computer.(found on LG website)
Click to expand...
Click to collapse
Ratified. Motochopper worked flawlessly for me as well.

richardpwnsner said:
Ratified. Motochopper worked flawlessly for me as well.[/QUOT
Anyone find a tethering ap that works?
Click to expand...
Click to collapse

wolfu11 said:
richardpwnsner said:
Ratified. Motochopper worked flawlessly for me as well.[/QUOT
Anyone find a tethering ap that works?
Click to expand...
Click to collapse
Do tethering apps need to be phone specific? I don't have data, but I'll let you know if I come across one.
Click to expand...
Click to collapse

Bad news
I have created the recovery tree, and have created a recovery.img for this phone. ok now heres the bad news OUR lg optimus f3 has a stock 3.4 kernel with a locked bootloader. Even worse news is that 3.4 "locking" features a sha5 hash system for its image/partitions (recovery, boot, and bootloader). Even worse news there is no known (or atleast what i know or have heard) way to get around this. The phone will be forever locked until lg updates or allows said lock to be removed. I have flashed the recovery and have had no damage to my device but it just sticks at "unsecure recovery" and does a hard reset (factory restore) every time i try to play with it which is a huge flaw if you ask me.
I have hexedited the bootloader and found that there is indeed "juicy" strings within that may tell to a future unlock these strings being
-Device UnLock!, so Boot Success!!
-oem unlock
-ERROR: Could not do normal boot. Reverting to fastboot mode
Also these strings could just be defualt with all lg bootloaders meaning....there is no hope.
My phone is without a soul and I will never be buy lg again.
If anyone is able to get into fastboot
1. PM ME
2. run : fastboot oem unlock
Again root for this phone works great as long as you dont touch recovery, bootloader, or boot partitions

inyourface09 said:
I have created the recovery tree, and have created a recovery.img for this phone. ok now heres the bad news OUR lg optimus f3 has a stock 3.4 kernel with a locked bootloader. Even worse news is that 3.4 "locking" features a sha5 hash system for its image/partitions (recovery, boot, and bootloader). Even worse news there is no known (or atleast what i know or have heard) way to get around this. The phone will be forever locked until lg updates or allows said lock to be removed. I have flashed the recovery and have had no damage to my device but it just sticks at "unsecure recovery" and does a hard reset (factory restore) every time i try to play with it which is a huge flaw if you ask me.
I have hexedited the bootloader and found that there is indeed "juicy" strings within that may tell to a future unlock these strings being
-Device UnLock!, so Boot Success!!
-oem unlock
-ERROR: Could not do normal boot. Reverting to fastboot mode
Also these strings could just be defualt with all lg bootloaders meaning....there is no hope.
My phone is without a soul and I will never be buy lg again.
If anyone is able to get into fastboot
1. PM ME
2. run : fastboot oem unlock
Again root for this phone works great as long as you dont touch recovery, bootloader, or boot partitions
Click to expand...
Click to collapse
Ugh. Thanks for the work. This is bad news indeed. I'll keep poking around and let you know if I find anything.

richardpwnsner said:
Ugh. Thanks for the work. This is bad news indeed. I'll keep poking around and let you know if I find anything.
Click to expand...
Click to collapse
Out of curiosity, any chance Loki would work? I'd be willing to give it a go if there's a decent chance—still within the 14 day exchange window .

Will motochopper work on any carrier version of this phone? Thanks!

jjfad said:
Will motochopper work on any carrier version of this phone? Thanks!
Click to expand...
Click to collapse
I've seen confirmations on three carriers (can't remember which ones off the top of my head, sorry [edit-well, T-Mobile and Virgin Mobile come to mind now]), so I'd assume the answer is yes. Regardless, I have yet to see anyone complain about adverse affects, so no reason not to try (though, grain of salt—I'm brand new to android).

For anyone that has this, how are the antennas on this phone?
I just ordered one from tmo and am hoping to get better reception at my house than from my Samsung or HTC.
Sent from my SGH-T999 using xda app-developers app

Steve5400 said:
For anyone that has this, how are the antennas on this phone?
I just ordered one from tmo and am hoping to get better reception at my house than from my Samsung or HTC.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
They seem better and with WIFI calling built in the phone hasn't skipped a beat.

Check my way!
http://forum.xda-developers.com/showthread.php?t=2420178&highlight=rooting+lg+optimus+f3
I failed rooting my phone with Windows system, maybe cause I'm not familiar with the process or I was just to lazy, but it does work if you use motochopper. Try looking it up youtube. You could try my method, it should work on Jellybean 4.1.2!

richardpwnsner said:
Out of curiosity, any chance Loki would work? I'd be willing to give it a go if there's a decent chance—still within the 14 day exchange window .
Click to expand...
Click to collapse
BAHAHA me to man i think im down to 10 days. Im trying to get some attention but i need someone who knows little endian, and their way around bootloaders. Id be willing to donate to someone who can help me out, also to support the other 3 variants (if the aboot differs).
I have a recovery created also and a device tree (needs gpio support for kernel).
And to awnser your question, yes loki will work IF i can get the needed values so that when recovery/boot is read into memory that it overwrites the security check feature in aboot. If the wrong values are give you may end up with a brick (very slim chance)

My return window just closed . If it helps, you can pull the open source from LG's website and merge it with the android source. I also discovered an even easier solution: set up the LG Sync application, and select the "upgrade recovery option". Then, when it begins downloading, remove your phone, set Windows (or your relevant OS) to show hidden files and folders, and go the the Program Data folder. There should be something like "PHONEAX" under the LG Electronics folder that will contain the full stock kdz file when the download is complete.
It's really kind of surprising that there's absolutely no dev love out there for the F3. I suppose it's because the phone is entry level, but it's really not that bad but for the storage. I got it as a gift, so no complaints here—of course, if anyone wants to donate a Note or Galaxy gratis, I suppose I'd be willing to switch .

I had a Galaxy S4 from Verizon. I switched to T-Mobile Because believe it or not the network is stronger where I work. Also, there pricing on plans cannot be beat. But, I digress. The Galaxy S4 being a Verizon device never really functioned the way it was supposed to on T-Mobiles network. It was unlocked however was still useless for 4G LTE and while I could do better than edge in some places, those places were few and far between. I started to assess what it is I actually used my phone for these days. I'm not into modding with custom ROMS and kernels anymore and I'm not much of a multi-tasker either so I decided that I did not need the super power device anymore. The specs on this phone are perfect for what I need my phone to do. Its been a long time since I have gone beyond rooting to remove bloat and tether. I agree that the storage on this sucks. I don't understand why there are any devices anymore that come with less than 32gb internal. storage is the cheapest thing that can be added to a device and its not as though it uses much physical space. other than the storage I will say that I am impressed with the quality of this device and I don't know that I would even put this as low as "entry level device." I would say its more of a mid-grade device. I am also happy with the reception on this device and its nice to have a compact phone again that actually fits comfortably in my hand and on my belt.

yutzyscott said:
I had a Galaxy S4 from Verizon. I switched to T-Mobile Because believe it or not the network is stronger where I work. Also, there pricing on plans cannot be beat. But, I digress. The Galaxy S4 being a Verizon device never really functioned the way it was supposed to on T-Mobiles network. It was unlocked however was still useless for 4G LTE and while I could do better than edge in some places, those places were few and far between. I started to assess what it is I actually used my phone for these days. I'm not into modding with custom ROMS and kernels anymore and I'm not much of a multi-tasker either so I decided that I did not need the super power device anymore. The specs on this phone are perfect for what I need my phone to do. Its been a long time since I have gone beyond rooting to remove bloat and tether. I agree that the storage on this sucks. I don't understand why there are any devices anymore that come with less than 32gb internal. storage is the cheapest thing that can be added to a device and its not as though it uses much physical space. other than the storage I will say that I am impressed with the quality of this device and I don't know that I would even put this as low as "entry level device." I would say its more of a mid-grade device. I am also happy with the reception on this device and its nice to have a compact phone again that actually fits comfortably in my hand and on my belt.
Click to expand...
Click to collapse
No argument here. I like it well enough, but I'm (1) a closet geek; and (2) a heavy multitasker, so given the option I'd prefer something with more screen space (I just graduated from law school, so I do a lot of reading on the go). As a phone, however, you really couldn't ask for more—the size otherwise pretty much perfect, it's relatively snappy with most applications, and once debloated the stock launcher is pretty good.
That being said, the second I see a safe way to deal with the bootloader pop up, I'm diving in, no question .

Decided to share my home screens.
Sent from my LG-P659 using XDA Premium 4 mobile app