Develop Bugs

Is it easy/hard to brick the Galaxy?

Hi,
1. For a month ago i've learned how to root my galaxy s2, and since then i've flashed new ROM's and kernels almost every week, and thats because almost everyone told me that it was almost impossible to brick the phone.
In 2 days i will recive my new Galaxy Nexus, and i don't know if i will Root it or not, is it worth doing this to this phone?
thanks

People say it's almost impossible.. Just search the threads where people think they bricked their phones

It is EXTREMELY hard to brick the Galaxy Nexus.
And it is definitely worth rooting. There are some amazing ROMs and kernels available

Learning to root and use android from scratch, I bricked this fella at least six times, but mostly due to bad file transfers and user error.
Use a toolkit, wugfresh's makes it excessivlely easy.
Sent from my Galaxy Nexus using xda premium

I did not wipe data out before flashing, my phone could not start. I thought i bricked my phone but after went to recovery mode to wipe data, my phone worked fine.

As far as I know, the only time that you can brick this phone is when flashing bootloaders. For example, the lights go out during the 2 secs required to flash it. But the window of opportunity is so small you have to really be unlucky, and if you have UPS or do it on a laptop, that won't be a problem at all. The more probable scenario is flashing a corrupted image of the bootloader (that's what md5 checksums are for) or, god forbid, a bootloader for a completely different device (that's what intelligence is for). Besides, you shouldn't be flashing bootloaders all the time. Maybe once every time a new version of ICS comes out.

TwilightSparkle said:
I bricked this fella at least six times
Click to expand...
Click to collapse
So what you really mean, is that you didn't actually brick it once?

Lol - interesting thread...
I'll bet that I can brick one in a few minutes, so it can't be that hard... xD

I was under the impression that bricking can also occur by mismatching radios/kernels/roms, not just the wrong bootloader. Like using a 4.0.2 version of one with a 4.0.3 version of another, for instance. I want to upgrade from 4.0.2 to 0.3 or 0.4 but I'm not sure of the correct order of updating everything, since I've customized all of them. Unless I'm just mistaken altogether...

thirtynation said:
I was under the impression that bricking can also occur by mismatching radios/kernels/roms, not just the wrong bootloader. Like using a 4.0.2 version of one with a 4.0.3 version of another, for instance. I want to upgrade from 4.0.2 to 0.3 or 0.4 but I'm not sure of the correct order of updating everything, since I've customized all of them. Unless I'm just mistaken altogether...
Click to expand...
Click to collapse
No. As long as your volume button and power button are not broken, you can start into the bootloader and start over.
Bricking is a very final thing that one can not repeat on the same device. Once bricked, it's only good as a paperweight. If you can revive the device, then it was never bricked in the first place

Wrong radio will brick your device for certain. Kernel and ROM not so much...

danger-rat said:
Wrong radio will brick your device for certain. Kernel and ROM not so much...
Click to expand...
Click to collapse
I thought CWM just gives an error and doesn't complete the flash in that scenario, no..?

danger-rat said:
Wrong radio will brick your device for certain. Kernel and ROM not so much...
Click to expand...
Click to collapse
I thought I remembered reading that in some /r/android comments a few months ago. Thanks for confirming.
So since I'm on 4.0.2 running the leaked 4.0.3 radios, if I wanted to run 4.0.4 everything would you recommend just reverting back to pure stock 4.0.2 via this thread or similar method, and then going from there?

Vangelis13 said:
I thought CWM just gives an error and doesn't complete the flash in that scenario, no..?
Click to expand...
Click to collapse
Not confirmed with this phone, but typically the bootloader will do an md5 type check, but recovery doesn't. If you disable signature verification in recovery, then it's all in your hands...

j.go said:
[snip]
The more probable scenario is flashing a corrupted image of the bootloader (that's what md5 checksums are for) or, god forbid, a bootloader for a completely different device (that's what intelligence is for). Besides, you shouldn't be flashing bootloaders all the time. Maybe once every time a new version of ICS comes out.
Click to expand...
Click to collapse
Not sure if the bootloader flow is the same on the Galaxy Nexus (probably not), but on the Nexus One, the bootloader will not flash a bootloader that is not signed. Period. Unless of course there is no NAND lock (i.e., S-OFF for HTC devices).

Afaik,you have to screw up fast boot to truly brick the device. Not even messed up boot loaders will brick it. You can always go to fastboot and factory restore.
Sent from my Galaxy Nexus

psycho2097 said:
Afaik,you have to screw up fast boot to truly brick the device. Not even messed up boot loaders will brick it. You can always go to fastboot and factory restore.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Dare you to flashable radio from another phone...

danger-rat said:
Dare you to flashable radio from another phone...
Click to expand...
Click to collapse
LOL!!!!!
Sent from my Galaxy Nexus using Tapatalk

I Dare y'all to flash the 4.0.4 update on a GSM phone. ;P
Sent from my Galaxy Nexus using xda premium

No lockscreen or Market/Google Play

Hey there,
So I just got my GSM Galaxy Nexus in the mail today and found a couple things to be a bit odd. You see, my package came with 2 Galaxy Nexuses (or nexi?) and my brother's phone seemed completely normal. It had Android 4.0.4 which he instantly got an update for Jellybean. My phone on the other hand was a bit off, as stated previously. My Galaxy Nexus shipped with Android 4.0.1, when i went to the "about phone" tab, there was no option to even check for a system update, my lock screen doesn't work (security settings are on slide yet the power button just wakes my screen and no sliding to unlock required), I have no market or google play store, I can't add a Gmail account under the "accounts and sync" tab, and my home button wasn't working (factory resetting fixed this).
I'm honestly just stuck on what to do about this device. I've factory reset this device 5 times already and nothing else has worked except for fixing the home button which wasn't working on my initial boot up.
Is there any solution to this Nexus or do I just have a defective one?

U can get rif of lock screen in the setting>security>screen lock<none
Sent from my Galaxy Nexus using xda premium

In Settings - About Phone, what is your Build Number? Also your brother's?
Any why couldn't you have picked your brother's phone out of the box?

netbuzz said:
In Settings - About Phone, what is your Build Number? Also your brother's?
Any why couldn't you have picked your brother's phone out of the box?
Click to expand...
Click to collapse
Build Number: full_maguro-eng 4.0.1 ICL23D 347 test-keys
And why couldn't I have picked my brother's? Haha I don't know!

They sent you a phone with an early engineering build. This can be easily fixed by flashing the stock Google image.
Here's a guide with all the info you need. http://forum.xda-developers.com/showthread.php?t=1626895
If you are in the US flash the takju build. Elsewhere the yakju build.
I'll hang out here for a while. If you have any questions reply here and I'll help!
Sent from my Nexus 7 using xda premium

airkenada said:
U can get rif of lock screen in the setting>security>screen lock<none
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The problem is that my settings are set to slide yet my phone is acting as if it's set to none

El Daddy said:
They sent you a phone with an early engineering build. This can be easily fixed by flashing the stock Google image.
Here's a guide with all the info you need. http://forum.xda-developers.com/showthread.php?t=1626895
If you are in the US flash the takju build. Elsewhere the yakju build.
I'll hang out here for a while. If you have any questions reply here and I'll help!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Does this void any warranty?

BrokeEven said:
Does this void any warranty?
Click to expand...
Click to collapse
You won't have a problem with warranty if you are running a stock build.

http://www.blogcdn.com/www.engadget.com/media/2011/11/nexnex20111117103746mat400mat400.jpg
Can you compare whether your phone and your brother's have some of these apps? I'm betting its your phone.....

maschiosoosai said:
Can you compare whether your phone and your brother's have some of these apps? I'm betting its your phone.....
Click to expand...
Click to collapse
Ha yeah! The not-so-normal apps that I have on my phone include "Angry GPS", "Dev Tools", and "SUB PBA Test". I checked with my Brother's Nexus running JB and he's got none of those. I called into Google's hotline for Nexus support and was able to get in touch with one of the supervisors. I was told that the device I received was a Developer's Model and that it was the "strangest thing ever".

El Daddy said:
You won't have a problem with warranty if you are running a stock build.
Click to expand...
Click to collapse
So, the instructions involve unlocking my bootloader (a task I know very little about!). To be honest, I don't have much experience with the mobile development. The only thing I've done in terms of tweaking with phones is following the instruction with the ace hack kit to root my phone (which seemed a lot more simplier than these instruction) and flashing custom ROMs.
To further my previous question, since the instructions say unlock the bootloader, does that invalidate my phone's warranty if I were to return anytime within its warranty period with an unlocked bootloader running stock android? (Would they even check/realize?)
And lastly, how safe is this procedure (returning the stock?) Is there a chance to brick my device?

BrokeEven said:
So, the instructions involve unlocking my bootloader (a task I know very little about!). To be honest, I don't have much experience with the mobile development. The only thing I've done in terms of tweaking with phones is following the instruction with the ace hack kit to root my phone (which seemed a lot more simplier than these instruction) and flashing custom ROMs.
To further my previous question, since the instructions say unlock the bootloader, does that invalidate my phone's warranty if I were to return anytime within its warranty period with an unlocked bootloader running stock android? (Would they even check/realize?)
And lastly, how safe is this procedure (returning the stock?) Is there a chance to brick my device?
Click to expand...
Click to collapse
You need to unlock your bootloader to flash the images. You can always relock your bootloader if you wish. You won't have an issue with the warranty.
Flashing the images the way I provided is a good way to learn the basics and will be beneficial in the future. It's very easy to learn. Just follow the link step by step. Flashing with fastboot is the safest way to do things and there is a very small chance of you bricking your phone.
Also what did google tell you to do when you called them?

Development Tools
maschiosoosai said:
Can you compare whether your phone and your brother's have some of these apps? I'm betting its your phone.....
Click to expand...
Click to collapse
I just got another Nexus from Play Store.
It's in developer mode, without Google apps and filled with a bunch of testing tools, like AngryGPS and Screen Test, the same menu in this image from maschiosoosa.
I tried to call Google Support and they give me two options.. One is doing exactly what everybody does.. Flash a stock Google image (but they said: "it's a very difficult way" lol) or the second, they will call Samsung for a replacement.
It's not a defective device, but it's kind of getting a Windows 8 Consumer Preview. A thing that it's not finished yet. Shame on Goole. lol
I'll flash of course.. It seems the bootloader is unlocked and its probably easy to do the flash thing.
Hey BrokeEven, if you got your device from Play Store you can ask for a replacement (if you are not sure of the flash image).
And probably your bootloader is already unlocked (at least if you received this same dev tool device).

El Daddy said:
You need to unlock your bootloader to flash the images. You can always relock your bootloader if you wish. You won't have an issue with the warranty.
Flashing the images the way I provided is a good way to learn the basics and will be beneficial in the future. It's very easy to learn. Just follow the link step by step.
Also what did google tell you to do when you called them?
Click to expand...
Click to collapse
Thank you, I'm gonna give it a shot!
When I called Google and talked to one of the supervisors, he was almost excited to hear about such an "interesting" story and said, "It looked like you may have gotten a rooted or developers model" and "If i got a dev model, I'd just keep it haha - but that's just me" I proceeded to ask him about whether or not it'd be a safe idea to keep the phone and do my own tweaking and such. He responded by telling me that even if i was to safely flash back to stock, it'd be "hard to prove" to Google or Samsung that I hadn't tampered with it. He was a cool guy
So let's say I did in fact get a rooted model by mistake, is there any way I'd be able to figure out if the bootloader is locked or not (even though rooted doesn't necessarily mean it has an unlocked bootloader)?

BrokeEven said:
Thank you, I'm gonna give it a shot!
When I called Google and talked to one of the supervisors, he was almost excited to hear about such an "interesting" story and said, "It looked like you may have gotten a rooted or developers model" and "If i got a dev model, I'd just keep it haha - but that's just me" I proceeded to ask him about whether or not it'd be a safe idea to keep the phone and do my own tweaking and such. He responded by telling me that even if i was to safely flash back to stock, it'd be "hard to prove" to Google or Samsung that I hadn't tampered with it. He was a cool guy
So let's say I did in fact get a rooted model by mistake, is there any way I'd be able to figure out if the bootloader is locked or not (even though rooted doesn't necessarily mean it has an unlocked bootloader)?
Click to expand...
Click to collapse
Yep... The same case... The guys on Google are very funny. lol
Reboot your device and check if theres a unlocked locker at the bottom of the Google logo screen.

BrokeEven said:
Thank you, I'm gonna give it a shot!
When I called Google and talked to one of the supervisors, he was almost excited to hear about such an "interesting" story and said, "It looked like you may have gotten a rooted or developers model" and "If i got a dev model, I'd just keep it haha - but that's just me" I proceeded to ask him about whether or not it'd be a safe idea to keep the phone and do my own tweaking and such. He responded by telling me that even if i was to safely flash back to stock, it'd be "hard to prove" to Google or Samsung that I hadn't tampered with it. He was a cool guy
So let's say I did in fact get a rooted model by mistake, is there any way I'd be able to figure out if the bootloader is locked or not (even though rooted doesn't necessarily mean it has an unlocked bootloader)?
Click to expand...
Click to collapse
Reboot the phone, when it's rebooting (showing google logo) if there's unlocked sign (lock that is unlocked) under the google logo, then it's unlocked Nexus. If you only see Google logo, then it's just locked Nexus

I don't know whether this is a curse or a blessing... I remembered when i ordered this phone I said "meh, I'm not gonna bother with rooting and flashing ROMs. I'll just stick to stock. And so Google sends me a Nexus with an unlocked bootloader and now force me to flash back to stock (or root) in order to get my phone fully functional
One pic is my unlocked bootloader, the other is a picture of my ALL the apps on my phone

Cool so you are already unlocked. Just download the images and flash away!
Sent from my Nexus 7 using xda premium

El Daddy said:
Cool so you are already unlocked. Just download the images and flash away!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Just one question and this may be a simple one...
It's step 8 under subsection C. What does it mean to open the command prompt in the same directory? And sorry in advance! I need you to be very simple in explaining this to me. To my knowledge, I thought you just open the command prompt. How do you open the command prompt in the same directory?

BrokeEven said:
Just one question and this may be a simple one...
It's step 8 under subsection C. What does it mean to open the command prompt in the same directory? And sorry in advance! I need you to be very simple in explaining this to me. To my knowledge, I thought you just open the command prompt. How do you open the command prompt in the same directory?
Click to expand...
Click to collapse
On windows just hold down shift while you right click in the folder. You will see open command prompt here or similar.
Sent from my Nexus 7 using Tapatalk 2

[Q] Some Rooting Questions About The Nexus 7 Flo

Hi,
Sorry for the silly questions. I just want to quickly check some things about the Nexus 7 Flo.
QUESTION 1: I'm constantly scared of bricking my device when rooting it. If I brick it when rooting, will ASUS repair it? If not, is there a tool I can use to unbrick?
QUESTION 2: If I use the All-In-One toolkit, how likely is a soft brick/hard brick? Can I un-everything (unroot + lock + install stock ROM + stock recovery) using the All-In-One toolkit if I need to?
QUESTION 3: If something happens with the hardware (e.g. port broken, screen cracked) and I am everything'ed (root + unlock + ROM installed + custom recovery), will ASUS repair it?
QUESTION 4: Can we get ParanoidAndroid 3+ for Nexus 7 Flo yet?
Thank you, and sorry for the noob questions!

OrangeFlash81 said:
QUESTION 1: I'm constantly scared of bricking my device when rooting it. If I brick it when rooting, will ASUS repair it? If not, is there a tool I can use to unbrick?
Click to expand...
Click to collapse
As far as I know, you don't have to unlock the bootloader to root. If you do, and need a repair, see question 2.
OrangeFlash81 said:
QUESTION 2: If I use the All-In-One toolkit, how likely is a soft brick/hard brick? Can I un-everything (unroot + lock + install stock ROM + stock recovery) using the All-In-One toolkit if I need to?
Click to expand...
Click to collapse
I would say unlikely to soft brick, and very unlikely to hard brick. And yes, you should be able to undo everything with a toolkit / fastboot commands.
OrangeFlash81 said:
QUESTION 3: If something happens with the hardware (e.g. port broken, screen cracked) and I am everything'ed (root + unlock + ROM installed + custom recovery), will ASUS repair it?
Click to expand...
Click to collapse
If the USB port breaks you might have a problem, since you need USB connection to issue fastboot commands, which are used to restore the device to locked, stock state. If the firmware is altered and/or the bootloader is unlocked, the warranty is void.
OrangeFlash81 said:
QUESTION 4: Can we get ParanoidAndroid 3+ for Nexus 7 Flo yet?
Click to expand...
Click to collapse
Patience...

If the firmware is altered and/or the bootloader is unlocked, the warranty is void.
Click to expand...
Click to collapse
@ameinild, will ASUS still repair it for me (but for a fee), or will they refuse to repair it at all? I don't understand warranties

OrangeFlash81 said:
@ameinild, will ASUS still repair it for me (but for a fee), or will they refuse to repair it at all? I don't understand warranties
Click to expand...
Click to collapse
Honestly I have no idea. I'm not too sure about how vendor repairs work either.
But as long as you don't erase or corrupt your bootloader (which would be an amazingly stupid thing to do) or smash your USB port, you should be good.

@ameinild, I have another question: Will ASUS know my device has been previously rooted or unlocked? Is there a triangle or something? Thanks!
Sent from my XT890 using xda app-developers app

OrangeFlash81 said:
@ameinild, I have another question: Will ASUS know my device has been previously rooted or unlocked? Is there a triangle or something? Thanks!
Click to expand...
Click to collapse
I'm pretty sure they can't know that in any way - I don't believe Nexus devices have a counter...

ameinild said:
Honestly I have no idea. I'm not too sure about how vendor repairs work either.
But as long as you don't erase or corrupt your bootloader (which would be an amazingly stupid thing to do) or smash your USB port, you should be good.
Click to expand...
Click to collapse
Not entirely true. Ordered mine from B&H, rooted, etc., and woke the next morning with a hard brick. Even restoring through fastboot did not work. So I wiped system, recovery, and boot, relocked the bootloader, and sent the device back for a refund. Just received the refund today without question. Simply told the customer service dude the device wouldn't boot when I received it. I know, a little dishonest, but I followed all instructions to a T, I believe it was a hardware issue anyway, though I only overclocked to 1800 or so.

dillinjer said:
Not entirely true. Ordered mine from B&H, rooted, etc., and woke the next morning with a hard brick. Even restoring through fastboot did not work. So I wiped system, recovery, and boot, relocked the bootloader, and sent the device back for a refund. Just received the refund today without question. Simply told the customer service dude the device wouldn't boot when I received it. I know, a little dishonest, but I followed all instructions to a T, I believe it was a hardware issue anyway, though I only overclocked to 1800 or so.
Click to expand...
Click to collapse
But you still managed to relock your bootloader, meaning fastboot worked which is the important thing.

[Q] Should I unroot and relock my bootloader before returning Nexus 7?

I am yet another victim to dead pixels and pretty bad screen bleed so I will be returning my Nexus 7 to Walmart and picking up a new one from OfficeMax.
Should I relock my bootloader and unroot or just format data and leave it up to Walmart? I assume they are just going to send it back to Asus. What are the chances that there will be any kind of trouble since my warranty is technically void since I unlocked the bootloader and rooted it.
Thanks ahead of time.

If it were me I would unroot it and relock the bootloader just to be safe.

Im looking to unroot mines as well but dont know where to get the files to flash back to stock through fastboot, any help is appreciated...thnx

nyjohn said:
Im looking to unroot mines as well but dont know where to get the files to flash back to stock through fastboot, any help is appreciated...thnx
Click to expand...
Click to collapse
stock system.img is here:
https://mega.co.nz/#!PBIiEbBJ!bKpdHxegOVlde12nsu_ulEyRq7UsANLLQab1IZjLIGc
"fastboot flash system system.img"
should do it i think

Nbsss said:
stock system.img is here:
https://mega.co.nz/#!PBIiEbBJ!bKpdHxegOVlde12nsu_ulEyRq7UsANLLQab1IZjLIGc
"fastboot flash system system.img"
should do it i think
Click to expand...
Click to collapse
Has anyone done this successfully?

rumatt said:
Has anyone done this successfully?
Click to expand...
Click to collapse
Me lol

I ended up restoring my device to stock everything, formatting data, and relocking my bootloader. Wasn't a problem at all returning it.

AFAIK Google has yet to release the stock image for the N7 2013.

danvee said:
AFAIK Google has yet to release the stock image for the N7 2013.
Click to expand...
Click to collapse
Yep, but a few minutes on Google or XDA search will yield you some images dumped from real-life Flo units, so you're good on that front for now.
cyberprodigy said:
I am yet another victim to dead pixels and pretty bad screen bleed so I will be returning my Nexus 7 to Walmart and picking up a new one from OfficeMax.
Should I relock my bootloader and unroot or just format data and leave it up to Walmart? I assume they are just going to send it back to Asus. What are the chances that there will be any kind of trouble since my warranty is technically void since I unlocked the bootloader and rooted it.
Thanks ahead of time.
Click to expand...
Click to collapse
Always do your own data formatting to be on the safe side. It's not like companies will maliciously steal your data, but mistakes happen and people can be careless. With Nexus devices, by the way, your warranty is basically protected so long as you go back to stock.

Rirere said:
Yep, but a few minutes on Google or XDA search will yield you some images dumped from real-life Flo units, so you're good on that front for now.
Click to expand...
Click to collapse
Is it a true system image? A true system image will overwrite or recreate all partitions. IDK if these will do that...

danvee said:
Is it a true system image? A true system image will overwrite or recreate all partitions. IDK if these will do that...
Click to expand...
Click to collapse
...a true system image will do no such thing. You do know what an image is, right? It's an exact copy of the state of storage media at the time of the image's creation. If you flash any image-- stock, modified, whatever-- it will overwrite whatever you tell it to overwrite.
You're mixing up the images with the flash-all script Google is nice and includes for you in their downloads.

rumatt said:
Has anyone done this successfully?
Click to expand...
Click to collapse
I just did it because I'm sending both my original with all the screen issues (backlight bleeding, dead pixels) along with the "replacement" that was on the charger for about three hours and then decided to up and die all together back for a refund. The image flashed just fine so the device is now relocked and hopefully I can get my money back.

joshtheitguy said:
I just did it because I'm sending both my original with all the screen issues (backlight bleeding, dead pixels) along with the "replacement" that was on the charger for about three hours and then decided to up and die all together back for a refund. The image flashed just fine so the device is now relocked and hopefully I can get my money back.
Click to expand...
Click to collapse
question....if you're rooted on stock ROM and just relock the bootloader....doesn't that wipe everything anyway? isn't that a security feature of unlocking and relocking the bootloader? or will it retain root.

Ed 115 said:
question....if you're rooted on stock ROM and just relock the bootloader....doesn't that wipe everything anyway? isn't that a security feature of unlocking and relocking the bootloader? or will it retain root.
Click to expand...
Click to collapse
It only wipes it when you unlock so locking it after changing anything will give you a device with a locked boot loader in the condition it was when you relocked it.

Factory images have been released by the way...
Sent from my Nexus 10 using Tapatalk 4

Question about voiding warranty.

Ok so I'm not asking on how to install a rom or anything like that. It's just that I haven't rooted a phone or installed a different rom in so long that I just don't know what's changed. So I just got a LG G4, and I wanted to install Cyanogenmod just because I like the customization options it had back then and I'm sure it's gotten better now (on that note can you still revert to stock roms on phones?). So here's the thing, I just got the phone today, and it's brand new. Now I'm afraid something might go wrong with the phone (other than bricking which would be my fault) and I want to be able to send it in and get it fixed or replaced. I remember a while back there was something you'd installed that it would reset the counter (flash counter?) so it would seem like it was not rooted. Is that still around or anything like that so technically I'm not voiding my warranty just yet?

Why don't you read the forum a little bit more
Sent from my LG-H811 using Tapatalk

Currently the only you can do on this phone (unless you have tmobile or international) is root as the bootloader is locked. The only possible roms we'd have are stock modded roms that we can flash the system.imgs for.

soulysephiroth said:
Currently the only you can do on this phone (unless you have tmobile or international) is root as the bootloader is locked. The only possible roms we'd have are stock modded roms that we can flash the system.imgs for.
Click to expand...
Click to collapse
I do have T-Mobile., so does that mean I can or can't? So if I understood this correctly, stock modded roms can be used to reset the flash counter or do you mean revert it back to unrooted stock or both?
shook187 said:
Why don't you read the forum a little bit more
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Great stuff man, thanks.

Dagobert_ said:
Great stuff man, thanks.
Click to expand...
Click to collapse
I thanked you on accident I wish I could unthank you.
But yeah just read up instead of posting about flash counter which is non existing and have never existed on a LG phone.
Sent from my LG-H811 using Tapatalk