Database Info

[Q] Back to ICS from CM10 - Atrix 2

Hello,
I followed step-by-step this thread.( http://forum.xda-developers.com/showthread.php?t=1982982 )
Since I ve been a listener and this is first time caller, Im not allowed to reply in Developer section until 10 post are made.
This is my first post and need help.
Everything works just as the DEV explained. The bugs are the known ones, and it works...fine.
But, things like the camera bug (3rd party apps cant use it, like instagram, guess Skype, Google Now, etc...), screenshots and auto-rotation made me want to go back. (I could manage the APN thing by following one of the replier's advices)
So, question is: Is out there a more stable CM10 ROM? (I know the link I related isnt from actual CM10, yet a modified one. But after reaserch I found that the original CM10 also have this same known issues). If there isn't. Is there a way to go back to a bug-free ICS version?
If there is, I would need a step-by-step guide.
Thanks in advance for all replies.
______
Motorola Atrix 2 - CM10/MagicMod ROM

WaltLlanos said:
Hello,
I followed step-by-step this thread.( http://forum.xda-developers.com/showthread.php?t=1982982 )
Since I ve been a listener and this is first time caller, Im not allowed to reply in Developer section until 10 post are made.
This is my first post and need help.
Everything works just as the DEV explained. The bugs are the known ones, and it works...fine.
But, things like the camera bug (3rd party apps cant use it, like instagram, guess Skype, Google Now, etc...), screenshots and auto-rotation made me want to go back. (I could manage the APN thing by following one of the replier's advices)
So, question is: Is out there a more stable CM10 ROM? (I know the link I related isnt from actual CM10, yet a modified one. But after reaserch I found that the original CM10 also have this same known issues). If there isn't. Is there a way to go back to a bug-free ICS version?
If there is, I would need a step-by-step guide.
Thanks in advance for all replies.
______
Motorola Atrix 2 - CM10/MagicMod ROM
Click to expand...
Click to collapse
Sure you can go back to stock ICS.
Find the FXZ file for your region here: http://sbf.droid-developers.org/edison/list.php
Follow The noob guide on how to flash FXZ here: http://forum.xda-developers.com/showthread.php?t=1396650

HELP!!
Waiting4MyAndroid said:
Sure you can go back to stock ICS.
Find the FXZ file for your region here: http://sbf.droid-developers.org/edison/list.php
Follow The noob guide on how to flash FXZ here: http://forum.xda-developers.com/showthread.php?t=1396650
Click to expand...
Click to collapse
I followed the steps to flash the SBF and give my Atrix 2 the stock ICS version again.
I did the whole process and clicked START
After a while, several minutes, it showed
"FAILED FLASHING PROCESS, FAILED FLASHING PROCESS. 5/20 REBOOT-BOOTLOADER -> NO ARRIVAL MESSAGE NOTIFICATION; PHONE DISCONNECTED"
And in the result column it shows FAILED
I made sure the battery was full before begin the process, and I haven't touched the phone at all since it started.
What do I do? It's still plugged and the screen's off (Don't sure if the phone is off). I havent touched a thing.
This is the SBF I downloaded:
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip
from here: http://sbf.droid-developers.org/edison/list.php
EDIT:
When still plugged in, I pressed the POWER button, and nothing happened, Thought it was off.
I closed the RSD and unplugged the phone from PC and tried to turn it on. NOTHING HAPPENED.
No LED light, No Moto logo, nothing.
Removed battery, tried again....nothing...at all. ¿Dead?
Is it totally screwed? Nothing to do about? PLEASE HELP ME!. Im about to die.

WaltLlanos said:
I followed the steps to flash the SBF and give my Atrix 2 the stock ICS version again.
I did the whole process and clicked START
After a while, several minutes, it showed
"FAILED FLASHING PROCESS, FAILED FLASHING PROCESS. 5/20 REBOOT-BOOTLOADER -> NO ARRIVAL MESSAGE NOTIFICATION; PHONE DISCONNECTED"
And in the result column it shows FAILED
I made sure the battery was full before begin the process, and I haven't touched the phone at all since it started.
What do I do? It's still plugged and the screen's off (Don't sure if the phone is off). I havent touched a thing.
This is the SBF I downloaded:
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip
from here: http://sbf.droid-developers.org/edison/list.php
EDIT:
When still plugged in, I pressed the POWER button, and nothing happened, Thought it was off.
I closed the RSD and unplugged the phone from PC and tried to turn it on. NOTHING HAPPENED.
No LED light, No Moto logo, nothing.
Removed battery, tried again....nothing...at all. ¿Dead?
Is it totally screwed? Nothing to do about? PLEASE HELP ME!. Im about to die.
Click to expand...
Click to collapse
If your phone is ATT version MB865, then you used the wrong SBF. The one to flash is
InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip md5=2BF9CCD528C05D26523ACC5B38AC76C6
I believe your phone is soft bricked with a dead battery. Find a way to charge your battery and try to RSD again.

Waiting4MyAndroid said:
If your phone is ATT version MB865, then you used the wrong SBF. The one to flash is
InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip md5=2BF9CCD528C05D26523ACC5B38AC76C6
I believe your phone is soft bricked with a dead battery. Find a way to charge your battery and try to RSD again.
Click to expand...
Click to collapse
Actually, I think he is, sorry to say, super-hardbricked. Take a look here, it has all the proper explanations about bricks:
http://forum.xda-developers.com/showthread.php?t=1937112
If he was on ICS and an AT&T phone and flashed a non-AT&T firmware, he is most likely screwed. We have seen this way too many times, sorry to say, but to the OP, Please read more before trying these type of things and use search and not get too antsy before attempting things. This phone even though it has a bootloader lock, you can still very easily hard brick it.
The OP, just might get lucky and be able to charge his phone with an external charger, but I am pretty sure that will not do it.
I would go on ebay or craigslist and buy a working A2 with a cracked screen (much cheaper this way), and change out the board with your screen and such, and you should be back in business.
@Waiting4MyAndroid, next time you try to help someone ask them for more information, so you/we can be of better help, this guys is obviously a noob, and if we knew which region he was from and which phone he has, we/you could have given him the EXACT link to the correct file, and then walked him through what and what not to do. I am not trying to be a jerk. I am just saying that most people do not search or read these forms, they ask in a dire need and even when you give a link to read something, they are in panic mode and still do not read, and just do what they think is the thing you just mentioned, even though it may not be the right thing. I know this has been covered so many times, but I have learned that no matter what people do not read or search no matter what you mention, that is why we see soooooooo many of these types of posts over and over.

jimbridgman said:
Actually, I think he is, sorry to say, super-hardbricked. Take a look here, it has all the proper explanations about bricks:
http://forum.xda-developers.com/showthread.php?t=1937112
If he was on ICS and an AT&T phone and flashed a non-AT&T firmware, he is most likely screwed. We have seen this way too many times, sorry to say, but to the OP, Please read more before trying these type of things and use search and not get too antsy before attempting things. This phone even though it has a bootloader lock, you can still very easily hard brick it.
The OP, just might get lucky and be able to charge his phone with an external charger, but I am pretty sure that will not do it.
I would go on ebay or craigslist and buy a working A2 with a cracked screen (much cheaper this way), and change out the board with your screen and such, and you should be back in business.
@Waiting4MyAndroid, next time you try to help someone ask them for more information, so you/we can be of better help, this guys is obviously a noob, and if we knew which region he was from and which phone he has, we/you could have given him the EXACT link to the correct file, and then walked him through what and what not to do. I am not trying to be a jerk. I am just saying that most people do not search or read these forms, they ask in a dire need and even when you give a link to read something, they are in panic mode and still do not read, and just do what they think is the thing you just mentioned, even though it may not be the right thing. I know this has been covered so many times, but I have learned that no matter what people do not read or search no matter what you mention, that is why we see soooooooo many of these types of posts over and over.
Click to expand...
Click to collapse
Jim your advice to me is well taken. Usually I do ask more questions before I offer advice. In this case the OP "seemed" knowledgeable due to the fact his phone was on CM10/MagicMod. I guess everyone should be treated as a NOOB until proven other wise! Hopefully the OP can still recover his phone with a charged battery.
Sent from my MB865 using xda app-developers app

Waiting4MyAndroid said:
Jim your advice to me is well taken. Usually I do ask more questions before I offer advice. In this case the OP "seemed" knowledgeable due to the fact his phone was on CM10/MagicMod. I guess everyone should be treated as a NOOB until proven other wise! Hopefully the OP can still recover his phone with a charged battery.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
No worries. I was going by his join date of Dec. 2012, and only having posted five times, for noting that he was a noob. I have found that a lot of people can talk the talk well in here, but have maybe used another phone that is not like the A2 and tend to easily mess it up. Especially if this is their first android.

Waiting4MyAndroid said:
Jim your advice to me is well taken. Usually I do ask more questions before I offer advice. In this case the OP "seemed" knowledgeable due to the fact his phone was on CM10/MagicMod. I guess everyone should be treated as a NOOB until proven other wise! Hopefully the OP can still recover his phone with a charged battery.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Thanks VERY MUCH for your help. And yes, this is my first Android, and first time flashing, and as you supposed, noob.
:/ I want to believe it is the battery and with a charging will revive, but I don't know. The "super-hardbrick" thing makes more sense to me.
IT WAS FULLY CHARGED, it can't drain 98% in a few minutes, can it?...
Aaaaanyways, I will see if by charging the battery and trying it will show a light.
(Will it charge the battery in this state? or I'll have to make it by other means?)
Thanks @Waiting4MyAndroid and @jimbridgman for replying.
EDIT: When I plug it in the wall, nothing happens. No LEDs, no Moto logo, just black screen. It doesn't shows life signals. Same happens when plugged to the PC.

WaltLlanos said:
Thanks VERY MUCH for your help. And yes, this is my first Android, and first time flashing, and as you supposed, noob.
:/ I want to believe it is the battery and with a charging will revive, but I don't know. The "super-hardbrick" thing makes more sense to me.
IT WAS FULLY CHARGED, it can't drain 98% in a few minutes, can it?...
Aaaaanyways, I will see if by charging the battery and trying it will show a light.
(Will it charge the battery in this state? or I'll have to make it by other means?)
Thanks @Waiting4MyAndroid and @jimbridgman for replying.
EDIT: When I plug it in the wall, nothing happens. No LEDs, no Moto logo, just black screen. It doesn't shows life signals. Same happens when plugged to the PC.
Click to expand...
Click to collapse
If that is the case then you will have to try either the Macguvyer method:
http://forum.xda-developers.com/showthread.php?t=892026
Or find someone with a similar phone that works, that will let you use their phone to charge your battery with (another A2 or a bionic).
Those are just so you can see if it is a battery issue, but at this point, I am thinking you are hardbricked.
Do you have an AT&T branded phone (there will be an at&t logo at the bottom front of the phone under the capacitive buttons)?

jimbridgman said:
If that is the case then you will have to try either the Macguvyer method:
http://forum.xda-developers.com/showthread.php?t=892026
Or find someone with a similar phone that works, that will let you use their phone to charge your battery with (another A2 or a bionic).
Those are just so you can see if it is a battery issue, but at this point, I am thinking you are hardbricked.
Do you have an AT&T branded phone (there will be an at&t logo at the bottom front of the phone under the capacitive buttons)?
Click to expand...
Click to collapse
Yes, its an AT&T device. I'll try to charge the battery.
/In the case its hardbrick, there's nothing we can do, right? AT ALL?/

WaltLlanos said:
Yes, its an AT&T device. I'll try to charge the battery.
/In the case its hardbrick, there's nothing we can do, right? AT ALL?/
Click to expand...
Click to collapse
You can try and get AT&T to exchange it for a refurb, just tell them you charged it overnight and woke and it was like this. The only thing is that you must have, had the phone less than a year to qualify for this, and you MUST be in the US.
Otherwise you can buy an A2 on ebay or craigslist with a broken screen and put your good screen on that phone and be back in action. There is a thread in the general section that is a sticky on how to exchange your screen with the phone you get that has a broken one. This will be only if you are out of the year warranty or bought this phone and use it outside the US.
http://forum.xda-developers.com/showthread.php?t=1746094

jimbridgman said:
You can try and get AT&T to exchange it for a refurb, just tell them you charged it overnight and woke and it was like this. The only thing is that you must have, had the phone less than a year to qualify for this, and you MUST be in the US.
Otherwise you can buy an A2 on ebay or craigslist with a broken screen and put your good screen on that phone and be back in action. There is a thread in the general section that is a sticky on how to exchange your screen with the phone you get that has a broken one. This will be only if you are out of the year warranty or bought this phone and use it outside the US.
http://forum.xda-developers.com/showthread.php?t=1746094
Click to expand...
Click to collapse
I'm out of US, so I guess the warranty thing won't work. (Damn, I guess if I get out of this, will NOT ever try to handle upgrades, and flashing and this stuff) I bought the Atrix 2 from e-bay..Its (was) pre-paid.
Thank you so much for everything. And well, sorry for the inconveniences.
By the way, can you explain to me, what did I do exactly to the phone? I mean, what I understand is that I took out the "software" that ran everything in the device (including powering on) and didn't replace it with the new one since the process didn't complete. So in the end, I took the "soul" out of it, leaving just the dead "body". Does it make sense?

WaltLlanos said:
I'm out of US, so I guess the warranty thing won't work. (Damn, I guess if I get out of this, will NOT ever try to handle upgrades, and flashing and this stuff) I bought the Atrix 2 from e-bay..Its (was) pre-paid.
Thank you so much for everything. And well, sorry for the inconveniences.
By the way, can you explain to me, what did I do exactly to the phone? I mean, what I understand is that I took out the "software" that ran everything in the device (including powering on) and didn't replace it with the new one since the process didn't complete. So in the end, I took the "soul" out of it, leaving just the dead "body". Does it make sense?
Click to expand...
Click to collapse
What you did was flash a non AT&T firmware to the device, which causes the phone to "hardbrick" AT&T has some checks built into the hardware that will make the phone "die" if this is done. So if you do get another one, just make sure that you ONLY flash the proper AT&T FXZ file on the SBf-droid.com site, they say which ones are AT&T.
You can flash all the "ROMS" you want, you just can not use a firmware (FXZ) that is not AT&T based, so if you bootloop or softbrick, you need to make sure you use this FXZ file for AT&T ICS:
334.7 MiB 2BF9CCD528C05D26523ACC5B38AC76C6 ATT US InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip http://sbf.droid-developers.org/edison/InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip
My guess is that you did not use this file before, and RSD lite began to flash the bootloader, then went to reboot, and the checks happened and saw that the wrong bootloader was flashed and that set off an efuse that "bricked" the phone.

warrenty
Check to see if u have warranty still with motorola. Just give some lame excuse. Dont mention anything about roooting or roms or ull be f'ed. I sent then 2 hard bricked phones so on my 3rd A2 now. Just pay for shipping and it will be back in ur hands in hopefully less than 2 weeks.
Cant enter link cause im newb but motorola com go to service look for a2 and
Its on the bottom left column just enter imei#

widekyle said:
Check to see if u have warranty still with motorola. Just give some lame excuse. Dont mention anything about roooting or roms or ull be f'ed. I sent then 2 hard bricked phones so on my 3rd A2 now. Just pay for shipping and it will be back in ur hands in hopefully less than 2 weeks.
Cant enter link cause im newb but motorola com go to service look for a2 and
Its on the bottom left column just enter imei#
Click to expand...
Click to collapse
That only works, if Motorola warranties the phone in the Country that you live in.

jimbridgman said:
That only works, if Motorola warranties the phone in the Country that you live in.
Click to expand...
Click to collapse
I live in Colombia, and I bought the device on April 2012 on ebay, had it shipped internationally with USPS.
Do you think I can claim warranty for Motorola directly? Obviously not mentioning anything about ROMs, flashing, and anything. But what can I say?

WaltLlanos said:
I live in Colombia, and I bought the device on April 2012 on ebay, had it shipped internationally with USPS.
Do you think I can claim warranty for Motorola directly? Obviously not mentioning anything about ROMs, flashing, and anything. But what can I say?
Click to expand...
Click to collapse
Nope, you can not get moto to warranty it. You are better buying another phone. I would buy one that will be warrantied in your country, just in case something like this happens.

Used RUU, screen doesn't turn on

I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.

I'm guessing you were SuperCID, and S-on? If so, sorry to say you are now bricked.
Should have read this, stickied to the top of General: http://forum.xda-developers.com/showthread.php?t=2181929

Wow. The level of suck here is amazing. Thanks. Nothing that can be done at all?

Jonathan_A said:
When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing.
Click to expand...
Click to collapse
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.

redpoint73 said:
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.
Click to expand...
Click to collapse
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.

Jonathan_A said:
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.

Everyone makes stupid mistakes once in a while. But yeah, that really sucks. If you have access to a Linux computer, you might try the JET tool in Development, or check the unbricking thread in General. But I don't think anyone has been able to come back from this after the 3.18 RUU or OTA + SuperCID.
Beyond that, you can try to find a repair shop that will JTAG the phone. It will cost you, but better than buying a new phone.

iElvis said:
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.
Click to expand...
Click to collapse
Well, it's still under warranty, and I'm hoping that since the bootloader was relocked and the RUU technically succeeded, they'll just send me a new one or something. Though I'll take a whack at the JET thing if I can find my Linux live CD... Thanks a ton, I'm feeling pretty dumb here and you guys have been really helpful.

Jonathan_A said:
I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.

redpoint73 said:
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.
Click to expand...
Click to collapse
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.

Jonathan_A said:
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.
Click to expand...
Click to collapse
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick

exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.

Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
Good luck bud!
Sent from my HTC One X using xda app-developers app

Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.

iElvis said:
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.
Click to expand...
Click to collapse
Ooh, thanks. Good to know. They'll be my next try. You all have probably just saved me ~$300

Jonathan_A said:
I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.
Click to expand...
Click to collapse
Happened to me too :c Has anyone had any luck using JET?

If the emmc partition table is still intact its feasible, but im pretty sure the ruu/ota kills it upon install. who knows why. seems to be a security "feature" since s-off seems to work fine.

Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.

I had a similar issue where my screen wouldn't turn on but it was still on and usable. I went to the AT&T store and got a replacement. Tell them you installed the AT&T update and then the screen stopped working. They probably won't be able to fix it but they'll give ya a new phone if you're under warranty. My phone was far from stock (rooted, bootloader unlocked, S-off, custom kernel and ROM), and they still gave me a new one. Make sure you go to an AT&T store though, I tried three different Best Buys and they were all noobs that had no idea what to do.
Edit: Didn't read post above so you can disregard this. But if you go to a store they can give you a new one on the spot instead of having to wait for one to be shipped to you.

Jonathan_A said:
Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.
Click to expand...
Click to collapse
Since the phone is bricked, there is really no way of them knowing (by checking the phone anyway) that you modded it. And as mentioned, AFAIK there has never been a reported case of AT&T denying warranty service due to the bootloader having been unlocked (and probably aren't even going to check). AT&T is much less strict then HTC, as its in AT&T self interest to keep you as a happy customer (paying that big old monthly bill), rather then fight over something like a single warranty exchange.
There have been some cases of the OTA randomly bricking devices that are fully stock (and probably possible with the RUU as well). Any time you mess with the hboot, if things get interrupted somehow, its possible to brick the phone. So for all AT&T knows, this is what happened in your case.
I'm normally not a big fan of making a warranty claim for your own negligence, and as a result of you modding the phone. But I suppose this is a bit of a gray area, since the RUU really shouldn't brick the phone solely due to SuperCID.
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Did HTC actually deny your warranty service due to a record of you having unlocked the bootloader? Just curious, because it would be the first I have heard of that actually happening.
Yes, as the warning state when you unlock the bootloader, it voids the warranty (at least in theory). But in actual practice, whether they honor the warranty or not after BL unlock seems to be much more of a gray area.
Its true that the carrier will be more lenient than HTC. But I know there was some discussion on the "international" (quad core) One X forum, where HTC was actually honoring the warranty if the bootloader was unlocked. But they were actually denying warranty service if any custom ROM had ever been installed on the device. Even if the device was returned to the stock ROM before sending in. So apparently, they have some way of knowing a custom ROM was previously installed (even if uninstalled). If the phone was bricked, I wonder if they would still be able to check this?
Of course, how HTC honors the warranty may also vary from region to region.

[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

My Phone turn off suddenly, help me please!!

Hey guys. I have a problem I tried to speak Spanish as forums but got HTCMania solve anything.
Before I thought it was problem of CM 11 that I turned off the phone suddenly (not restart, it shuts down) and occurred 1 time every 3 or 4 days, now increasingly occurs more often, yesterday I turned off the phone 6 times, this night while sleeping 3 times went out. It made me late for work again because the phone was turned off and the alarm did not go off ... following tips, did not solve anything. I factory reset everything I installed the stock ROM without root or anything, I installed Paranoid Android, SlimKat, Illusion ... nothing, with all the ROM I just turn off the phone. Not have more than 3 ½ months of use and this has been happening since 1 month. I gather it can be battery problem or the device itself, but it is something that has no solution for me. I live in Venezuela and bought me phone my mother and sent from Spain, along with the bootloader already unlocked, the warranty is not going to accept me or have possibility to send. I have searched a thousand Internet sites (Venezuela because the outside you can not buy anything here) and I do not find the battery moto G, to buy and to me installed in a technical service, but even on Amazon U.S. found nothing .
I fell into despair because I can not find any solution, I've calibrated the battery and also keeps shutting off, so I already was without resources, ideas and nothing to do but to stay with the phone and continuously be aware that if the phone turns off,,,, I have to turn it on again, buy an alarm clock to not be late for work again.
Continue pending if anyone can give me some solution, try anything, because nothing I lose ... buy a phone in this country is an impossible task because notice that a regular phone range Moto G (which is cheaper) costs Complete 4 months my salary.
Again thank you very much for your help and am awaiting any news that they can provide me. Hughs

I can't help you, nor I'll even bother trying.Your phone probably has some hardware fault ( too much gaming on it? ).
But what I wanted to tell you is that, you shouldn't have screwed around with your phone, if you can't afford to lose it. You should have never unlocked the bootloader in first place.
A lesson has been learned.

liveroy said:
I can't help you, nor I'll even bother trying.Your phone probably has some hardware fault ( too much gaming on it? ).
But what I wanted to tell you is that, you shouldn't have screwed around with your phone, if you can't afford to lose it. You should have never unlocked the bootloader in first place.
A lesson has been learned.
Click to expand...
Click to collapse
I unlocked the bootloader because I live far from the site where phone was bought. if phone got any problem I can't send it to warranty anytime so whats suposed I must to do? to be on stock frimware and don't root my phone? so all we must do that? then can't understand why there are lot of scene about root ROMs and all that. of course I know my rosks when I unlock my bootloader and root my phone but is my decission, if noone must unlock the bootloader then this kinds of forums would be useless.
Anytime, this community is the best for this kind of scene, root, ROMs and all around that.
I didn't play too much just played a bit, you really think that suposed hardware problem is because I rooted my phone? I bought it 3 1/2 mounth ago and I didn't have any problem, just 1 mounth ago started with this. I think is a factory problem, maybe hardware maybe battery, but not around root or ROM installed.
I was asking just because maybe someone got the same problem and can help be. I appreciate your cooperation like all kind of cooperation but need solutions, not lessons of what I souldn't do.
Thanks anytime

Replacement batteries can be found on eBay. I'd try that first.

SbM_ said:
Replacement batteries can be found on eBay. I'd try that first.
Click to expand...
Click to collapse
They can't import stuff there that easy, thats one of his main problems.Probably eBay is not an option for him.Not 100% sure about that tho.

liveroy said:
too much gaming on it? ).
You should have never unlocked the bootloader in first place.
A lesson has been learned.
Click to expand...
Click to collapse
What are you saying??? Are you kidding?!?
gaming on a phone dont destroy it :/
"a lesson has been learned" nope because he did not understand what happened

1- you should fomated all your phone ( use TWRP recovery), then flash stock Firmware.
2- after that,you turn off your phone BY YOU and plug chager for 1 day.
3- restart your phone and check.
4- it's my solutions. :thumbup: ,hope it's help.
Sent from my XT1033

agalam84 said:
I unlock my bootloader and root my phone...
Click to expand...
Click to collapse
as u wrote seems an hardware problem so not solvable itself.
u can relock the bootloader the bootloader and remove warning at boot if u want maybe motorola accept it in warranty, i havent clear if u can sent it to them...
when your problem start? after that u did something or itself, maybe something with bootloader
i hope u can solve your problem

AXD96 said:
What are you saying??? Are you kidding?!?
gaming on a phone dont destroy it :/
"a lesson has been learned" nope because he did not understand what happened
Click to expand...
Click to collapse
With that said, I don't think you'll understand even if I paint it for you.
Try reading my post again, give it a thought for a while, eventually it will come to my mind what I'm saying and why.

liveroy said:
With that said, I don't think you'll understand even if I paint it for you.
Try reading my post again, give it a thought for a while, eventually it will come to my mind what I'm saying and why.
Click to expand...
Click to collapse
sorry I do not want to be rude but he want a solution not a moralist

So I just bought this phone today anything I should do with it?

Ok more specifically I'm pretty used to the stock android experience (modded of course) but I read about that audio issue and I'm pretty terrified of it because music and calls are the main things I need a phone for. I've been out of the modded android loop since CM10 so I don't really know present day standards or processes for unlocking/rooting let alone standards for ROMs etc. Anyone got any advice?

WhenSuddenly said:
Ok more specifically I'm pretty used to the stock android experience (modded of course) but I read about that audio issue and I'm pretty terrified of it because music and calls are the main things I need a phone for. I've been out of the modded android loop since CM10 so I don't really know present day standards or processes for unlocking/rooting let alone standards for ROMs etc. Anyone got any advice?
Click to expand...
Click to collapse
just go to the guides subforum of a8 2018 and press on the thread that can help u flash twrp lol, all you gotta do is just follow the instructions word by word

WhenSuddenly said:
Ok more specifically I'm pretty used to the stock android experience (modded of course) but I read about that audio issue and I'm pretty terrified of it because music and calls are the main things I need a phone for. I've been out of the modded android loop since CM10 so I don't really know present day standards or processes for unlocking/rooting let alone standards for ROMs etc. Anyone got any advice?
Click to expand...
Click to collapse
my words of advice would be to make sure that you need root before you root it. what i mean by that is think about what you stand to gain by rooting it vs the PITA it is to root this thing. Pay close attention to the 168 hour thing as its been a thorn in many a persons side and caused many a headache. Ive had dozens of android phones and all have been rooted with the exception of the HTC Rezound, which required the OMG PITA "wire trick" to root properly. These phones run very well as stock and dont have much bloatware, so rooting them is becoming less necessary. I got mine in july '18 and have been happy with its performance overall so far. Ive reflashed the stock tar.img a few times for varying reasons, and even rooted it. But after losing SPay capability with root, i flashed back to stock as the gains werent worth the losses to me. Also, SHealth is a task to get working after you trip knox btw.

youdoofus said:
my words of advice would be to make sure that you need root before you root it. what i mean by that is think about what you stand to gain by rooting it vs the PITA it is to root this thing. Pay close attention to the 168 hour thing as its been a thorn in many a persons side and caused many a headache. Ive had dozens of android phones and all have been rooted with the exception of the HTC Rezound, which required the OMG PITA "wire trick" to root properly. These phones run very well as stock and dont have much bloatware, so rooting them is becoming less necessary. I got mine in july '18 and have been happy with its performance overall so far. Ive reflashed the stock tar.img a few times for varying reasons, and even rooted it. But after losing SPay capability with root, i flashed back to stock as the gains werent worth the losses to me. Also, SHealth is a task to get working after you trip knox btw.
Click to expand...
Click to collapse
Yeah tbh I'm ok with the interface now and aside from making the volume buttons change tracks when you hold them down the only things id need root for is clearing out bloatware etc. I think I'll take your advice and not root it for now (until something breaks) but what is this 168 hour thing?

WhenSuddenly said:
Yeah tbh I'm ok with the interface now and aside from making the volume buttons change tracks when you hold them down the only things id need root for is clearing out bloatware etc. I think I'll take your advice and not root it for now (until something breaks) but what is this 168 hour thing?
Click to expand...
Click to collapse
there has been a great deal of discussion about how to get the OEM unlock toggle to show up in the developer options, many suggest that its only obtainable by leaving the phone powered off for 168 hours and then rebooting, not connecting to any network (including cellular) and then enabling developer options and then the toggle should be there.

youdoofus said:
there has been a great deal of discussion about how to get the OEM unlock toggle to show up in the developer options, many suggest that its only obtainable by leaving the phone powered off for 168 hours and then rebooting, not connecting to any network (including cellular) and then enabling developer options and then the toggle should be there.
Click to expand...
Click to collapse
Your wrong your suppose to keep phone on for 168 hours no reboots then oem should show up again.

mchlbenner said:
Your wrong your suppose to keep phone on for 168 hours no reboots then oem should show up again.
Click to expand...
Click to collapse
youre*
and youre correct, i said it backwards.

youdoofus said:
there has been a great deal of discussion about how to get the OEM unlock toggle to show up in the developer options, many suggest that its only obtainable by leaving the phone powered off for 168 hours and then rebooting, not connecting to any network (including cellular) and then enabling developer options and then the toggle should be there.
Click to expand...
Click to collapse
So wait. My phone is showing the OEM unlock toggle and I can change it. Does that mean I can root? Or would trying to root then make me wait 168 hours? I never tried any custom stuff with it btw. Just bought and installed Lawnchair lol.

Amirk365 said:
So wait. My phone is showing the OEM unlock toggle and I can change it. Does that mean I can root? Or would trying to root then make me wait 168 hours? I never tried any custom stuff with it btw. Just bought and installed Lawnchair lol.
Click to expand...
Click to collapse
Hit the toggle and it'll ask for your pw, then you can flash a custom recovery via Odin

Amirk365 said:
So wait. My phone is showing the OEM unlock toggle and I can change it. Does that mean I can root? Or would trying to root then make me wait 168 hours? I never tried any custom stuff with it btw. Just bought and installed Lawnchair lol.
Click to expand...
Click to collapse
be careful with starting down the root rabbit hole tho. if you flash anything in download mode, youll trip the knox security counter and that is 100% irreversible without sending it to samsung. Root is cool and allows you to do stuff, but honestly ive not found too much reason to root this phone yet. Ive literally had over 20 android phones and i rooted and modded all of them (except the rezound, if you want to know why that one wasnt fully rooted, just google "rezound wire trick" and youll see) and this one just really doesnt need root IMO. Sure it would be nice to have a few root things, but its not worth the trade off of losing samsung pay so i can pay for stuff with my watch. That feature is just waaaay too valuable to me

youdoofus said:
be careful with starting down the root rabbit hole tho. if you flash anything in download mode, youll trip the knox security counter and that is 100% irreversible without sending it to samsung. Root is cool and allows you to do stuff, but honestly ive not found too much reason to root this phone yet. Ive literally had over 20 android phones and i rooted and modded all of them (except the rezound, if you want to know why that one wasnt fully rooted, just google "rezound wire trick" and youll see) and this one just really doesnt need root IMO. Sure it would be nice to have a few root things, but its not worth the trade off of losing samsung pay so i can pay for stuff with my watch. That feature is just waaaay too valuable to me
Click to expand...
Click to collapse
If his oem is showing and if he marks it and follow the directions he will be fine I have been rooted since day one of having it.
I never got locked out.

mchlbenner said:
If his oem is showing and if he marks it and follow the directions he will be fine I have been rooted since day one of having it.
I never got locked out.
Click to expand...
Click to collapse
ill never trade my SPay on my watch for root

youdoofus said:
be careful with starting down the root rabbit hole tho. if you flash anything in download mode, youll trip the knox security counter and that is 100% irreversible without sending it to samsung. Root is cool and allows you to do stuff, but honestly ive not found too much reason to root this phone yet. Ive literally had over 20 android phones and i rooted and modded all of them (except the rezound, if you want to know why that one wasnt fully rooted, just google "rezound wire trick" and youll see) and this one just really doesnt need root IMO. Sure it would be nice to have a few root things, but its not worth the trade off of losing samsung pay so i can pay for stuff with my watch. That feature is just waaaay too valuable to me
Click to expand...
Click to collapse
Thanks for the advice,but this isn't my first rodeo with Samsung lol. I messed around with the Verizon S5 alot and was lucky to have the version able to unlock it's bootloader.

Amirk365 said:
Thanks for the advice,but this isn't my first rodeo with Samsung lol. I messed around with the Verizon S5 alot and was lucky to have the version able to unlock it's bootloader.
Click to expand...
Click to collapse
np, the G900V was a major disappointment with its locked bootloader. i recall spending several hours bricking one and having to restore it with the stock tar.img file. total PITA

youdoofus said:
np, the G900V was a major disappointment with its locked bootloader. i recall spending several hours bricking one and having to restore it with the stock tar.img file. total PITA
Click to expand...
Click to collapse
Will you stop telling people that you will mess up phone if you try to root it.
If people follow directions they have nothing to worry about.
You where bootloop not bricked a brick device is usually a unfix able.
If is fine you what to keep Sam pay but your info you are telling is wrong.
I recently unroot my phone guess what Sam pay work fine.
Then root phone again no lock out and enable treble and flashed gsi image.
So their nothing wrong with rooting if you want to do that.

mchlbenner said:
Will you stop telling people that you will mess up phone if you try to root it.
If people follow directions they have nothing to worry about.
You where bootloop not bricked a brick device is usually a unfix able.
If is fine you what to keep Sam pay but your info you are telling is wrong.
I recently unroot my phone guess what Sam pay work fine.
Then root phone again no lock out and enable treble and flashed gsi image.
So their nothing wrong with rooting if you want to do that.
Click to expand...
Click to collapse
dude, i dont think youre reading what im saying right. Ive never said that rooting your phone will mess it up. the stuff about the G900V is a DIFFERENT PHONE. FFS. This isnt my first rodeo rooting and modding. Hell, i even was writing mods back in the Evo and S3 days. Im refamiliarizing myself with some of this, but i havent ever said youd mess your phone up if you follow the root instructions. Ill even go as far as saying as long as you dont Odin flash the tar.img for a completely different phone, these things are virtually impossible to hard brick. And yes, a bootloop is referred to as a soft brick. But, it is important to know that if you do root your phone, it WILL make samsung health not work as it did when stock and there is NO WAY of bringing it back without swapping the motherboard

youdoofus said:
np, the G900V was a major disappointment with its locked bootloader. i recall spending several hours bricking one and having to restore it with the stock tar.img file. total PITA
Click to expand...
Click to collapse
Unlocking the bootloader was completely dependent on the type of EMMC chip that the G900V that you had was using. I got three of those and only one was able to unlock after the Marshmallow update.

Amirk365 said:
Unlocking the bootloader was completely dependent on the type of EMMC chip that the G900V that you had was using. I got three of those and only one was able to unlock after the Marshmallow update.
Click to expand...
Click to collapse
the last tinkering i did with the G900V was several years ago and that was at the point when all hope was lost on the locked bootloader. I havent looked into it since as the G900's i had were G900P's which were FAR easier to work with. I did also root and ROM a couple G900VL's, but again was years ago

youdoofus said:
the last tinkering i did with the G900V was several years ago and that was at the point when all hope was lost on the locked bootloader. I havent looked into it since as the G900's i had were G900P's which were FAR easier to work with. I did also root and ROM a couple G900VL's, but again was years ago
Click to expand...
Click to collapse
Good times. Anyways I'm not rooting for now. Waiting for Pie and see how it goes.

Amirk365 said:
Good times. Anyways I'm not rooting for now. Waiting for Pie and see how it goes.
Click to expand...
Click to collapse
good times, yeah LOL!!! major waste of time on those friggin G900V's is more like it yeah, i wouldnt root yet, keep the stock recovery so it automagically updates to pie in a few weeks and manually check for updates every so often to force its hand. Also sammobile.com posts them too if you want to force it on via Odin and trip knox. Anyways, if you get the update in the near future, let us know!