Database Info

[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

[Q] Bricked Nexus 5 doesn't boot + no access adb/fastboot/recovery (corup. bootload)

Hey there,
I received my Nexus 5 some days ago, I rooted it with the CF-AutoRoot, it worked fine, but since today, it is bricked. By the magic operation of Jesus maybe, who knows.
It don't boot, I don't see anything on the screen, I don't know if it is turned on or off… It just won't reply. To anything, fastboot, adb or whatever else. I can't boot in recovery or something else.
I think I have a splendid bricked late-2013 phone… I followed some tutorials to unbrick phones, the power + trick, but nothing.
The only thing I have on a windows computer is a "tadam" when I plug the USB, but that's it, no fastboot or adb, no screen, nada. But this sound of a plugged USB device. Knuh…
What the hell can I do ?
Shall I call Google tomorrow for RMA ?
ps: i saw some threads like me, i followed replies, but after a 4 hours searching, I don't wake up my phone

Have you given this a try? http://forum.xda-developers.com/showthread.php?t=2513937

esskayy said:
Have you given this a try? http://forum.xda-developers.com/showthread.php?t=2513937
Click to expand...
Click to collapse
yap, but no more results…
I think I tried all solutions on xda, no one worked :s

Flayks said:
yap, but no more results…
I think I tried all solutions on xda, no one worked :s
Click to expand...
Click to collapse
Hmmm... sounds like your bootloader is corrupt dude Weird, you are like the third today who has bricked the Nexus. All you can do now is RMA it and hope for the best.

esskayy said:
Hmmm... sounds like your bootloader is corrupt dude Weird, you are like the third today who has bricked the Nexus. All you can do now is RMA it and hope for the best.
Click to expand...
Click to collapse
Damned… why
Please, Google, don't be cruel with me

Flayks said:
Damned… why
Please, Google, don't be cruel with me
Click to expand...
Click to collapse
If the phone is truly bricked, and it seems like it is, then Google won't be able to boot up the phone so they won't know you've unlocked the bootloader

esskayy said:
If the phone is truly bricked, and it seems like it is, then Google won't be able to boot up the phone so they won't know you've unlocked the bootloader
Click to expand...
Click to collapse
That's what I think too, but how to explain that like someone don't know what is about… "helow my phone won't boot, it is black, I can't do anything… send me another one, please"? :cyclops:

doesn't boot*
*grammar police*

Flayks said:
That's what I think too, but how to explain that like someone don't know what is about… "helow my phone won't boot, it is black, I can't do anything… send me another one, please"? :cyclops:
Click to expand...
Click to collapse
Yh, that will work There are legitimate cases of phones not booting up so they may think you are one of them. Also I doubt the Google representative will care much for the reason. Their job is just to arrange the RMA

Flayks said:
That's what I think too, but how to explain that like someone don't know what is about… "helow my phone won't boot, it is black, I can't do anything… send me another one, please"? :cyclops:
Click to expand...
Click to collapse
That would work. Just don't say "send me another" ask "what do I do now"

apristel said:
doesn't boot*
*grammar police*
Click to expand...
Click to collapse
ups, thx.
esskayy said:
Yh, that will work There are legitimate cases of phones not booting up so they may think you are one of them. Also I doubt the Google representative will care much for the reason. Their job is just to arrange the RMA
Click to expand...
Click to collapse
Yep, I will call the support…
jd1639 said:
That would work. Just don't say "send me another" ask "what do I do now"
Click to expand...
Click to collapse
I would like to…
Thankz!

" I messed up my phone, even though it was completely fine when I bought it, I'll accuse google of producing a bad / faulty phone. "
Sounds legit.
If you CANNOT afford the risk that comes with modding, DONT do it. You/others who do this are very disgusting. GOOGLE did nothing wrong. YOUR phone was fine when you got it. Don't be a chump. You have to PAY to play.
MODS I'd close this thread due to FRAUD.. I HATE threads like this, People f/up their phones and expect everyone else to pay.

apristel said:
" I messed up my phone, even though it was completely fine when I bought it, I'll accuse google of producing a bad / faulty phone. "
Sounds legit.
If you CANNOT afford the risk that comes with modding, DONT do it. You/others who do this are very disgusting. GOOGLE did nothing wrong. YOUR phone was fine when you got it. Don't be a chump. You have to PAY to play.
MODS I'd close this thread due to FRAUD.. I HATE threads like this, People f/up their phones and expect everyone else to pay.
Click to expand...
Click to collapse
How do you know the phone isn't booting due to his bootloader being unlocked? He even said it was fine and it was not booting today....
Sent from my Nexus 5 using XDA Premium 4 mobile app

Because it booted afterwards. Thats how. .
I received my Nexus 5 some days ago, I rooted it with the CF-AutoRoot, it worked fine, but since today, it is bricked.
Click to expand...
Click to collapse

apristel said:
Because it booted afterwards. Thats how.
Quote:
I received my Nexus 5 some days ago, I rooted it with the CF-AutoRoot, it worked fine, but since today, it is bricked.
Click to expand...
Click to collapse
Maybe I was not clear in my first message but I rooted it, yes, but it worked! Since 3 days it works. But today, I really don't know why, I don't update or something else like changing rom (I'm on stock rom etc), it doesn't boot anymore.
That's it…

Flayks said:
Maybe I was not clear in my first message but I rooted it, yes, but it worked! Since 3 days it works. But today, I really don't know why, I don't update or something else like changing rom (I'm on stock rom etc), it doesn't boot anymore.
That's it…
Click to expand...
Click to collapse
I feel for you that your phone isn't working. Fraud isnt the answer. do you HONESTLY feel you'd get the same answer from Google if you told them that you rooted/unlocked and now your phone isn't working?
just saying that those who f up and make everyone pay for it are wrong. I personally like paying 400 for the 32gb device. I'd rather not pay 500 because of people who mess up and now make the cost/device go up due to rma's that are not legit.
Code:
The issuance of an RMA/RGA is a key gatekeeping moment in the reverse logistics cycle, providing the vendor with a final opportunity to diagnose and correct the customer's problem with the product (such as improper installation or configuration) before it is returned. As returns are costly for the vendor and inconvenient for the customer, any return that can be prevented benefits both parties.

Dude you need to chill a little. Unlocking your bootloader does not completely null warranty. If you brick your phone via software then you are responsible.
By the sounds of what is happening with the op, he has not changed anything to end up in this predicament. As with the other purple with similar problems (unlocking bootloader resulting in brick) can hardly be pointed at them.
Clearly something is happening which is out of user control which is causing these bricks.
If the ROM fails to boot it will throw you back to the bootloader.
If the bootloader fails you have a brick (not 100% true but not going into that now)
The facts are that the op has unlocked the bootloader which is a legitimate task and has for unknown reasons ended up with a corrupt bootloader.
This should still be covered as the op has not fine anything to solicit what had happened.
Sent from my Nexus 4 using xda app-developers app

apristel said:
I feel for you that your phone isn't working. Fraud isnt the answer. do you HONESTLY feel you'd get the same answer from Google if you told them that you rooted/unlocked and now your phone isn't working?
just saying that those who f up and make everyone pay for it are wrong. I personally like paying 400 for the 32gb device. I'd rather not pay 500 because of people who mess up and now make the cost/device go up due to rma's that are not legit.
Code:
The issuance of an RMA/RGA is a key gatekeeping moment in the reverse logistics cycle, providing the vendor with a final opportunity to diagnose and correct the customer's problem with the product (such as improper installation or configuration) before it is returned. As returns are costly for the vendor and inconvenient for the customer, any return that can be prevented benefits both parties.
Click to expand...
Click to collapse
Personally from my own experience, as the disclaimer on the bootloader unlock screen states 'This MAY void your warranty', telling Google the truth would be his best bet. Call Google, advise that the bootloader was unlocked and worked for 3 days and then it suddenly stopped booting.
If you bought a Nexus 5 and don't plan to do anything to it then that's up to you. However some of us buy Nexus devices because of the ease of development on them. Google facilitate this with the ability to unlock the bootloader and have no justifiable reason to refuse an RMA when all the OP has done is unlock said bootloader.
Why don't YOU stop being a **** and get off this thread. Please.

Anyone else bricked their phone like this? Managed to un-brick mine from an identical situation, if anyone is still stuck like I was I'll try and make a little "guide" to help others

daniel.kusy said:
Anyone else bricked their phone like this? Managed to un-brick mine from an identical situation, if anyone is still stuck like I was I'll try and make a little "guide" to help others
Click to expand...
Click to collapse
Apparently yes, I'm not the only one. It would be great if you try to explain your solution!

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!

[Need for help] Is there any way to remove bootloader unlocked screen?

This question has bothered me for a long time. As you guys know, when the bootloader is unlocked, everytime when you boot the device, the warning screen will show up
That screen is quite annoying...
Therefore I use a lot of time searching on Google, many people said it is impossible to remove it...
However, I saw them successfully replaced it on Moto and LG V20 (V20 Guide XDA link)
or something like this V30 Discuss XDA thread
I think maybe we can use the HEX tool to replace the warning screen with original logo sceen...?
But unfortunately, I'm not a developer and still couldn't find out the solution...
Can anyone please help research in how to remove or replaced that annoying screen...? Really appreciate!

UP. I'm also interested to know if it's possible.

AFAIK, there's no way around it. Think of it as a badge of honor.

I hear there's meds that will take away the pain.

Hitting the resume button makes the warning screen go away quicker.

swieder711 said:
Hitting the resume button makes the warning screen go away quicker.
Click to expand...
Click to collapse
Yeah but that's still quite annoying... So I'm thinking if there's a way to get rid of that

MyStyle0714 said:
Yeah but that's still quite annoying... So I'm thinking if there's a way to get rid of that
Click to expand...
Click to collapse
First for a little background on unlocked bootloader warnings. It used to be that the actual graphics files for the initial splash screen were located in their own partition and after you unlocked the bootloader you could flash a new image to that partition of any correctly formated graphic file to display whatever you wanted. Starting with the original Pixels Google moved them into the bootloader itself and I am not aware of any Dev that has or is willing to experiment with altering the bootloader since any error in doing so will hard brick the phone.

Why does it bother you so much? Its not like you need to hide it from the FBI. You should be PROUD...

Bootloader weirdness

I couldn't find absolutely any information about this anywhere so heck, I'm gonna just post this hoping someone has a clue about it. There was only one other person asking about it in September last year for another pixel phone, but he didn't get an answer either.
So the issue. After using the online flashing tool provided by Google for flashing AOSP builds, the bootloader shows 2 additional lines at the bottom. I've never seen them before and now even after factory resetting, either via flashing the factory image or sideloading the OTA, switching slots and flashing to factory image on both slots, locking back the bootloader, those 2 options are still there. No negative effects on the usage of the phone as I'm using it as I've been doing since I got it, but those 2 friggin options are still there and it's bugging the hell out of me.
If someone has a clue, please do share. I'd really appreciate it.
[ picture taken with potato phone ]

dragos281993 said:
I couldn't find absolutely any information about this anywhere so heck, I'm gonna just post this hoping someone has a clue about it. There was only one other person asking about it in September last year for another pixel phone, but he didn't get an answer either.
So the issue. After using the online flashing tool provided by Google for flashing AOSP builds, the bootloader shows 2 additional lines at the bottom. I've never seen them before and now even after factory resetting, either via flashing the factory image or sideloading the OTA, switching slots and flashing to factory image on both slots, locking back the bootloader, those 2 options are still there. No negative effects on the usage of the phone as I'm using it as I've been doing since I got it, but those 2 friggin options are still there and it's bugging the hell out of me.
If someone has a clue, please do share. I'd really appreciate it.
[ picture taken with potato phone ]
Click to expand...
Click to collapse
I remember seeing that post. I've never used the flash method, always downloaded the link and used fastboot. This has to have happened to more than the two of you. I wonder if it's isolated to the Pixel 5?

Tulsadiver said:
I remember seeing that post. I've never used the flash method, always downloaded the link and used fastboot. This has to have happened to more than the two of you. I wonder if it's isolated to the Pixel 5?
Click to expand...
Click to collapse
I actually saw the same thing on a Pixel 4's bootloader. It's really weird. It seems to be hardcoded or something cause not going away no matter the flashing method, slot switching and so on.

Strangely my P5 doesn't have those two additional options. For the first time ever I used the online flash tool to wipe and fresh install last month's update (Feb 2021), this past Saturday. But yeah my screen looks the same as always.
Hopefully those two options that some are seeing don't mean something ominous going forward, like Google taking away our options for unlocked bootloaders.
Thought I'd add my experience, I'm glad to know about this.