Just came off of having to put up with using Razr M's for the last two years. I bought two used G3's this week and am now attempting to figure out which way to go.
These are our first LG products since flip days. The specs of the G3 really grabbed my attention when I read up on it.
I've spent the last (7) hours crawling around this forum and am now somewhat burned-out, overwhelmed, confused, ETC. (and the beer supply ran out...)
The two (new to me) phones are in great shape. One is @24B and the other is @10B
The 24B unit pulled down the 35B update today and is waiting/holding to update.
The 10B unit when I select 'Check for Updates' is pulling down a 110MB update, however when I select 'Install', it reboots, attempts upgrade and then returns a error #0x1111004. I got a feeling that the PO didn't execute something quite right when he wiped it before selling it.
Since these units are at a stage where I can wipe and flash at will, I'm trying to determine if I should go custom or just accept the 35B.
I'm leaning towards Jasmine 9 or Xdabbeb. Once I get these setup & configured I'll most likely stay with it. I'll tinker but that's about it.
I want stability and reliability and won't be flashing just to try out the latest. (i may have to get ahold of another for that )
One feature that caught my eye that I would truly, dearly like to have is 'Record Call'. (if possible)
So if I may ask for some opinions on which way to go I would appreciate it.
Thanks in Advance,
_Dan
middle_road said:
Since these units are at a stage where I can wipe and flash at will, I'm trying to determine if I should go custom or just accept the 35B.
I'm leaning towards Jasmine 9 or Xdabbeb. Once I get these setup & configured I'll most likely stay with it. I'll tinker but that's about it.
I want stability and reliability and won't be flashing just to try out the latest. (i may have to get ahold of another for that [emoji14])
One feature that caught my eye that I would truly, dearly like to have is 'Record Call'. (if possible)
Click to expand...
Click to collapse
Hi and welcome! First, any used phone who knows what state they left the phone in so I would use LG Flash Tool 2014 with the 10B KDZ in Windows PC after having installed the Verizon LG drivers, which are different than the drivers for the other G3s, and then rebooted the PC.
Look for the return to stock thread in the Verizon G3 General section. It might mention the TOT method too, I prefer the KDZ method because it's easier.
Then root with the Stump app, install TWRP v2.8.7.0 with the TWRP Manager app and flash the custom ROM you want.
I'm using @xdabbeb 's and my personal opinion is that it's awesome. Very, very debloated. Runs cooler, battery lasts even longer.
Be warned that on this phone sometimes when you reboot it will go to a black screen and not actually boot up.
Sometimes you can just hold the power button in for up a while (not sure on the count, maybe 30 seconds or so) and that will shut it off and it you held it long enough it will power back on, too.
Once you have your ROM set up, if you decide to try another stock ROM, use the built in LG Backup (in settings). It's faster, easier and more reliable than Titanium Backup in my opinion and in the opinion of some others on here, although there are some users who have had trouble with LG Backup working for them.
I use it with every new updated stock ROM.
One caveat of LG Backup is that when you make a backup, it stops a bunch of things like the clock app for the alarm and they stay stopped until you run them once again, just like right after you restore apps with either Titanium Backup or LG Backup.
@xdabbeb 's ROM includes call recording although any stock ROM (not sure about Cyanogenmod) can use Xposed and the G3TweakBox app to give that functionality too.
If you ever do go straight stock and get to the 35B update, once you take it the ONLY way so far of downgrading so you can reroot is the TOT method with a different, new .DLL than what is referenced in the TOT instructions.
You can get everything I referenced by using Google to search XDA such as:
Code:
XDA VS985 10B KDZ
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
roirraW "edor" ehT said:
Hi and welcome!
Click to expand...
Click to collapse
- Thanks!
roirraW "edor" ehT said:
First, any used phone who knows what state they left the phone in so I would use LG Flash Tool 2014 with the 10B KDZ in Windows PC after having installed the Verizon LG drivers, which are different than the drivers for the other G3s, and then rebooted the PC.
Click to expand...
Click to collapse
- Isn't that the truth?! The one that's on 10B is acting a bit funky.
I've got a laptop with a fresh install of Win7 sitting here just awaiting setup for the G3 specific drivers.
Did not want to mess around with one that has all sorts of drivers on it going back (4) years. From HTC to Samsung to HPTP items.
Also have a 'Nix with ADB installed, JIC I really mess up. Altough it seems like it's a quite a bit more straight forward than years past...
roirraW "edor" ehT said:
Look for the return to stock thread in the Verizon G3 General section. It might mention the TOT method too, I prefer the KDZ method because it's easier.
Then root with the Stump app, install TWRP v2.8.7.0 and flash the custom ROM you want.
I'm using @xdabbeb 's and my personal opinion is that it's awesome. Very, very debloated. Runs cooler, battery lasts even longer.
Click to expand...
Click to collapse
- More thanks. I had not seen any mention of 'Stump' and also was unsure which version of 'TWRP' to use.
roirraW "edor" ehT said:
Be warned that on this phone sometimes when you reboot it will go to a black screen and not actually boot up.
Sometimes you can just hold the power button in for up a while (not sure on the count, maybe 30 seconds or so) and that will shut it off and it you held it long enough it will power back on, too.
Click to expand...
Click to collapse
- And I hadn't seen any mention at all on this little 'feature'. That would have worried me big time if it happen(s)(ed).
Thanks again for the advice and recommendations, I owe you a brew.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm gonna go grab a fresh cup of coffee and get to it.
_Dan
middle_road said:
- Thanks!
- Isn't that the truth?! The one that's on 10B is acting a bit funky.
I've got a laptop with a fresh install of Win7 sitting here just awaiting setup for the G3 specific drivers.
Did not want to mess around with one that has all sorts of drivers on it going back (4) years. From HTC to Samsung to HPTP items.
Also have a 'Nix with ADB installed, JIC I really mess up. Altough it seems like it's a quite a bit more straight forward than years past...
- More thanks. I had not seen any mention of 'Stump' and also was unsure which version of 'TWRP' to use.
- And I hadn't seen any mention at all on this little 'feature'. That would have worried me big time if it happen(s)(ed).
Thanks again for the advice and recommendations, I owe you a brew.
I'm gonna go grab a fresh cup of coffee and get to it.
_Dan
Click to expand...
Click to collapse
You're welcome! Stump only works pre-12B (from what I remember) so that's why I recommended the 10B KDZ. Also will warn you that although LG Flash Tool 2014 might display misleading dialogs such as "server not found" etc, whatever you do, do NOT bother touching those dialogs, selecting any buttons in them. Just move them out of your way and ignore them. 99% of the time despite these seemingly catastrophic errors, on the G3 within 10 minutes the device will have been flashed, and it will be obvious when it has.
Also note that flashing KDZs/TOTs erases your internal storage so save anything you want to keep from there.
On older LG G3 stock ROMs, you can use TWRP Manager or Flashify to flash the latest TWRP. You can't do that successfully with newer stock G3 ROMs - another reason I recommend a pre-Lollipop KDZ.
Boy that was easy -- on the 2nd phone. Nice and lean, looks very fine at first glance.
(6) hours later... Typical windows drivers problems, even on a fresh/clean laptop install. Of course it's been that way with
windoz for the last 20+ years that I've been dealing with it.
I've got a few questions, ( I did do some searching, however I'm beat and tired.)
- I couldn't get ADB to work on either 'Nix or Windows.
- GApps? is there one? I can't 'push' from the Play store on the PC to the handset. Should I just add the apps?
- The Better Half wanted me to ask if GPS is fully functional. (She's a tad concerned I'm flashing them...)
- That's more but my brain has turned to mush...
Thanks for all the guidance Warrior! Tis Appreciated.
_Dan
middle_road said:
Boy that was easy -- on the 2nd phone. Nice and lean, looks very fine at first glance.
(6) hours later... Typical windows drivers problems, even on a fresh/clean laptop install. Of course it's been that way with
windoz for the last 20+ years that I've been dealing with it.
I've got a few questions, ( I did do some searching, however I'm beat and tired.)
- I couldn't get ADB to work on either 'Nix or Windows.
- GApps? is there one? I can't 'push' from the Play store on the PC to the handset. Should I just add the apps?
- The Better Half wanted me to ask if GPS is fully functional. (She's a tad concerned I'm flashing them...)
- That's more but my brain has turned to mush...
Thanks for all the guidance Warrior! Tis Appreciated.
_Dan
Click to expand...
Click to collapse
Do you have USB Debugging turned on, on the phone? Go to Settings/About device/Software and press the Build # string about 10 times reasonably quickly and that'll put the Developer options menu in the main Settings. From there turn on USB Debugging. The first time you try to access an Android device from a new operating system installation (possibly for different USB ports, too), a pop-up will appear on the screen asking for you to give either temporary or permanent authorization to the PC for adb access.
All stock OEM ROMs come with GApps, and you can't just flash a different/newer GApps over top of it, you just have to update the apps you want to from the Play Store. Personally, I remove all Google apps from the stock ROM's system except for the necessary Play Store, Play Services, and maybe also Google TTS. Since the apps are updated occasionally or frequently, depending on the app, I like to only keep one copy of them in user apps instead of having the system copy and then the updated version still reside in user apps.
You can tell the Play Store on the PC to install such-and-such app to such-and-such of your device in the drop down and it'll install, although I usually find that manually launching the Play Store app from the device gets it started installing faster after doing so.
GPS works great for me, and I use it often.
You're welcome!
---------- Post added at 10:42 AM ---------- Previous post was at 10:35 AM ----------
Another tip: Definitely make a backup of your IMEI on each phone, and keep a backup of your backup in a safe place! Sometimes flashing KDZs, TOTs and even ROMs has caused people with this phone to get their IMEI reset to all zeros. Hasn't happened to me in all my flashing over the past ten months, but it's happened to some others.
In TWRP there's an odd partition listed - I forget what it's called, just back up only that and keep a copy of that on your phone and on your wife's in a safe place like Google Drive, so you can restore them if you ever need to.
How to engage Debugging was one of the first things I searched on when the phones arrived -hehe.
Love how 'cryptic' it is now. Following your suggestions, I tried out 'Run as Administrator' and lo & behold
after a bunch of bleeps & booruuups, ADB showed a device attached. Gotta love Windoz...
'Nix laptop still isn't seeing though. Going to mess with that later.
Pushing from the Play store from a PC was only working on the Wife's early this morning before I packed it in.
Now trying mine it's working. That makes it easier to load apps.
IMEI Partition - is this the one you're talking about- The 'EFS' one? :-
Need to go and search on DPI settings now. The 'Home' row buttons are too small for my fat fingers.
You hit 50 and your fingers get mushy and touches aren't precise.
Also need to punch up the text a tad for the eyes. hehe.
Thanks, _Dan
middle_road said:
How to engage Debugging was one of the first things I searched on when the phones arrived -hehe.
Need to go and search on DPI settings now. The 'Home' row buttons are too small for my fat fingers.
You hit 50 and your fingers get mushy and touches aren't precise.
Also need to punch up the text a tad for the eyes. hehe.
Thanks, _Dan
Click to expand...
Click to collapse
Yes! EFS, exactly. texdroider is what I used to change DPI recently. 640 is stock.
You may or may not have not seen you can change the font size in the Display settings.
Almost "fity" myself.
Pretty snappy ROM thus far. I'm liking it and this G3. I actually like where the power and vol buttons are. Doesn't mess anything up when
pulling it out of your pocket.
Grabbed Texdroider but haven't played with it yet.
Got a feeling I'm going to have to mess around with framework a bit or find a mod. Need some things to be more visible w/o glasses.
Figured if I do I'll call it 'Old Goats GUI'. Fat thumbs and aged eyesight.
Google trashed my contacts. Tons of entries from where I used email to send txts. That's going to take a while to clean up.
It is nice though have a clean slate. It's just like wiping your computer and starting fresh.
(Of course there is always a great deal of pain that goes with that.)
A friend called today and she just got a G4 and is getting rid of her G2, and it's got the touchscreen problem.
Hopefully it's just a software fix and I'll have another phone to add to the stable.
They didn't transfer all her stuff so I'll be taking that on this weekend. gives me a chance to get my hands dirty with all three models.
Thanks again, _Dan
Have fun! You're welcome. Changing the DPI, and that font size setting should solve most of any issue you have. I use Nova Launcher Prime which is highly configurable - if you don't use a custom launcher you might want to look into it. You can make everything whatever size you want. Icons, text, how many icons fit on the screen in both portrait and landscape, etc.
Oh, oh. Having problems this afternoon. (should I maybe post this in the ROM forum?)
We're at home today and the phones are dropping off network. They're talking to us saying 'No Carrier'...
I just noticed (using Signal Check Pro) that there is no EV-DO. and watching the phone the last several minutes
it is not shifting into 3G. Usually with the RAZR M's previously, they would drop to 3G depending on where one
was at in the house or out in the yard. I don't see 3G at all on the G3.
Did I mess something up flashing? Figures doesn't it? - (2) days after flashing the devil out of them....
And of course I'm waiting on a very important phone call today...
Thanks,
_Dan
I doubt if you messed anything up in flashing otherwise the ROM wouldn't have worked. Maybe Verizon has an issue in your area.
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
Gave Tech Support a call last evening, and all they could (or would) say was that there were problems in TN.
Usually they are a bit more specific. Then again I only called them twice over the last few years.
And of course this had to happen two days after I switched our plan to pre-paid and went to two different phones and
flashed a non-OEM ROM and was waiting on a call.
It was only happening on my phone - the wife's didn't do it. I did notice that it finally showed 3G when I was on the backside
of the house, so I'm hoping it's just tower issues.
I'm going to go dink around with Nova Launcher and Texdroider now and wait for the cases to arrive in the mail today...
middle_road said:
Gave Tech Support a call last evening, and all they could (or would) say was that there were problems in TN.
Usually they are a bit more specific. Then again I only called them twice over the last few years.
And of course this had to happen two days after I switched our plan to pre-paid and went to two different phones and
flashed a non-OEM ROM and was waiting on a call.
It was only happening on my phone - the wife's didn't do it. I did notice that it finally showed 3G when I was on the backside
of the house, so I'm hoping it's just tower issues.
I'm going to go dink around with Nova Launcher and Texdroider now and wait for the cases to arrive in the mail today...
Click to expand...
Click to collapse
When my wife and I were on Sprint with two Galaxy S3's, I noticed we would both get different signal/data strength in different areas, including our home. I had gone to a Sprint store where they said that was expected, that two of the same phones in the same place might favor different towers, or something like that. They said were able to change some technical setting in the phone that would hopefully give me a better or at least different tower when I was at home. From what I recall it did definitely make a noticeable difference.
Only mention it as a demonstration that it can be normal to get different service on two of the same phone and ROM at the same location.
That was the first and only time I had pursued a fix of that kind so no idea what Verizon is willing to do or capable of doing. Normally I don't expect much from the carrier stores, technically speaking.
roirraW "edor" ehT said:
When my wife and I were on Sprint with two Galaxy S3's, I noticed we would both get different signal/data strength in different areas, including our home. I had gone to a Sprint store where they said that was expected, that two of the same phones in the same place might favor different towers, or something like that. They said were able to change some technical setting in the phone that would hopefully give me a better or at least different tower when I was at home. From what I recall it did definitely make a noticeable difference.
Only mention it as a demonstration that it can be normal to get different service on two of the same phone and ROM at the same location.
That was the first and only time I had pursued a fix of that kind so no idea what Verizon is willing to do or capable of doing. Normally I don't expect much from the carrier stores, technically speaking.
Click to expand...
Click to collapse
OUI! The S3 with the great antenna design....
A good tech is hard to find. Even more rare are the knowledgeable ones.
(10) years ago I had contacts with engineers at Sprint, US Cell & Verizon. Wish that I had maintained them or that two of them had stayed... hehe.
I've determined that the towers around us appear to be leased as far as I can tell.
USCC, Sprint & Verizon are hanging their birds off of them and I'm getting the impression that maintenance it minimal.
I left USCC two years ago because on the tower closest to us the bird was pointing downwards and the signal likewise.
Over two years now and it still hasn't been re-positioned.
I was at home all day and didn't hear the phone say 'No Carrier' so hopefully it was an infrastructure problem.
I was just nervous with the timing and all.
Better Half was out all day and no problems and actually came home with 90% on her battery.
I'm liking that!
middle_road said:
I was at home all day and didn't hear the phone say 'No Carrier' so hopefully it was an infrastructure problem.
I was just nervous with the timing and all.
Better Half was out all day and no problems and actually came home with 90% on her battery.
I'm liking that!
Click to expand...
Click to collapse
Hopefully you don't get a scare like that again soon. I plan on putting that ROM on my wife's phone sooner or later, too.
Rainy day here so I'm finally attempting to try Nova Launcher and Texdroider.
Backup first - as recommended. Battery was @80%, TWRP finished up and rebooted the system and when
it came back up battery was @60%. A backup operation lasting a few minutes wouldn't use up 20% - would it?
(oh and yeah, I did have on my glasses )
middle_road said:
Rainy day here so I'm finally attempting to try Nova Launcher and Texdroider.
Backup first - as recommended. Battery was %, TWRP finished up and rebooted the system and when
it came back up battery was @60%. A backup operation lasting a few minutes wouldn't use up 20% - would it?
(oh and yeah, I did have on my glasses )
Click to expand...
Click to collapse
I wouldn't expect it to and I don't recall recent backups biting that much out of the battery. Did you backup to internal storage or external? I'm about to do another backup before performing a modification so I'll see what happens for me today.
Texdroider was just what was needed for my ol' eyes. Much better. It came up showing 541 DPI, I took it to 480 first try
just for grins. Boy that messes up the icons. Set it to 640 after that and I can actually see items without glasses on.
Thanks for that suggestion!
Two odd things still going on with the handsets. Just sitting here with it on the desk she'll tell me 'Lost of Service'.
Check the phone and Signal Pro is saying it's fine.
On the Wife's - her's is going into Roaming mode around the house, same vicinity as mine.
Related
This morning I woke up and my phone was running Entropy's 12/1 DD kernel with unnamed ROM. AT&T seemed to be having tower issues, and it that appeared to have caused my battery to drain a little quicker than normal. Happily, my Galaxy SII uses a standard micro-USB connector for power instead of some proprietary (and likely patented) connector. So, I plugged it into the cable I usually use to charge my wireless mouse. It just worked.
After I had a full charge on the battery, I was feeling like I wanted to play around with a different phone, so I rebooted into "recovery", did a backup, and flashed my latest compile of the cyanogen mod 7 code. This is truley a tinkerer's environment, with settings for nearly anything. I also really like the "rings" lock screen in cyanogenMod. It's also nice that I can play with the source code and change pretty much anything I desire. After setting this up and tinkering for a while, I decided that I needed to go back to my "daily driver" phone. I tend to get slightly worse battery performance when using cyanogenMod.
So, a quick reboot back into recovery, another backup, and then restored my previous kernel/ROM/settings. Everything is just the way I left it. The next time I decide I want to tinker more with cyanogenMod, it's a trivial matter to reboot, backup the current state of my phone, and restore cyanogenMod to the exact state it was in earlier.
Perhaps tomorrow I'll play with one of the concept ICS ports that were put in the wild a few weeks ago. Why not? It's fun to think different. Or, perhaps I'll put in a completely stock ROM and kernel... I can do that, too.
I know that whichever ROM and kernel I use, it'll be easy to back up and restore things. I know my email will work, I'll get my text messages, and my voice mail will function. Best of all, it'll do those things my way, not the way some self-proclaimed dictator decided for me.
There's been a huge uproar lately about some software by a company called "Carrier IQ" and phone companies essentially spying on their customers. Apparently, this involves all kinds of phones and wireless companies here in the United States. Some companies are saying they do it, some say they don't, and others say that the users can opt-out by turning off an option. None of them have mentioned if they use something other than "carrier iq" to spy on their users, however. They probably do. None of them have offered ANY proof whatsoever to back up any of their claims. I'm glad I'm able to check the logs on my phone directly, see what processes are running internal, and determine for my self what might be going on.
In the meantime, I've plugged my headphones into my phone and I'll sit back and enjoy my music. Perhaps I'll change around my playlists while listening to them on my phone. It's good to be able to do that without requiring a computer.
Thank you, Google.
--
Take care
Gary
All you need now is a hammock and a beverage of your choice.
Red5 said:
All you need now is a hammock and a beverage of your choice.
Click to expand...
Click to collapse
Well, android does come with a form of 'java'.
Is there a new OTA update for v21B going out?
Anyone have a rooted back up of v21B?
_________________________________________
edited 5/31
Here is a rooted V21B CWM back up file from Kid_Ding. Thank him in the post right below.
Rooted_CWM_BACKUP_P769_V21B_by_kid_ding.zip (569.1 MB)
https://mega.co.nz/#!sodg1K5A!G_4sbQXZouNUb3GZWpuvNi-lbStKBNDSIEs0owQ-DKQ
Before changing over to the Wind V21B from Tmobile V20D, make a back up copy of APN and then re-install it after the change over. Otherwise, there will be no data service. (Look for 'APN Backup & Restore' app in Google Play).
No noticeable functional difference between the two versions. The battery usage seems about the same.
csrow said:
Is there a new OTA update for v21B going out?
Anyone have a rooted back up of v21B?
Click to expand...
Click to collapse
flashing it now. i'll upload the backup when its all done.
also you can grab the kdz and hex edited bin from here if you dont want to wait for me.
http://forum.xda-developers.com/showthread.php?t=2284446
"New" in what sense, exactly...? Something released just today?
br0adband said:
"New" in what sense, exactly...? Something released just today?
Click to expand...
Click to collapse
latest radio and a lot less bloatware. its wind mobile canada. works great on the tmobile p769.
Would anyone know if flashing a backup of this would lock the bootloader?
Sent from my LG-P760 using Tapatalk 2
Kid_Ding said:
latest radio and a lot less bloatware. its wind mobile canada. works great on the tmobile p769.
Click to expand...
Click to collapse
Ok, but then the question becomes: is it fraught with the same problems the T-Mobile V20D update has that prompted T-Mobile to kill the update and go back to the drawing board, so to speak, or is this an even better build that has the issues fixed (Wi-Fi battery drain, connectivity issues, and some others that I've read about)?
br0adband said:
Ok, but then the question becomes: is it fraught with the same problems the T-Mobile V20D update has that prompted T-Mobile to kill the update and go back to the drawing board, so to speak, or is this an even better build that has the issues fixed (Wi-Fi battery drain, connectivity issues, and some others that I've read about)?
Click to expand...
Click to collapse
The wifi drain is still there (see screenshot)
Also Note: the wind version will obviously not have wifi calling.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-P769 using xda app-developers app
So then the final question (since I know things are just going off the rails at this point): is it worth the trouble of doing all this rather complicated effort to get the Wind version installed on this relatively new P769 of mine? I mean, I've used some complex devices over the decades, and I've been mucking around with ROMs on devices for a long long time as well but this L9 seems to have the most singularly complex methods of rooting and ROM flashing that I've ever encountered in my experience.
I know it's a great phone (so far in my usage, at least), and I was just outside a few minutes ago on the balcony of my apartment building and rather pleased to note that - at least on full brightness - the 4.5" display is rather easy to read even when I was holding the phone in direct sunlight, so that's a big plus considering summer is almost upon us here in Sin City.
But I'm still not seeing any major positives to pushing a JB update on this device even though it's obviously more than capable of the update overall.
Should I, shouldn't I, that eternal question always lingers...
ps
Wi-Fi calling is a gimmick in my opinion, and since I use the $30/plan with 100 minutes of talk time, it won't do any good for me at all either - I use Google Voice + Talkatone for VoIP duties and rarely ever touch the 100 minutes, actually.
br0adband said:
So then the final question (since I know things are just going off the rails at this point): is it worth the trouble of doing all this rather complicated effort to get the Wind version installed on this relatively new P769 of mine? I mean, I've used some complex devices over the decades, and I've been mucking around with ROMs on devices for a long long time as well but this L9 seems to have the most singularly complex methods of rooting and ROM flashing that I've ever encountered in my experience.
I know it's a great phone (so far in my usage, at least), and I was just outside a few minutes ago on the balcony of my apartment building and rather pleased to note that - at least on full brightness - the 4.5" display is rather easy to read even when I was holding the phone in direct sunlight, so that's a big plus considering summer is almost upon us here in Sin City.
But I'm still not seeing any major positives to pushing a JB update on this device even though it's obviously more than capable of the update overall.
Should I, shouldn't I, that eternal question always lingers...
ps
Wi-Fi calling is a gimmick in my opinion, and since I use the $30/plan with 100 minutes of talk time, it won't do any good for me at all either - I use Google Voice + Talkatone for VoIP duties and rarely ever touch the 100 minutes, actually.
Click to expand...
Click to collapse
I use Wi-Fi calling due to the fact that coverage isn't all that great when I go to a friends house, I could and here and their do use Talkatone but its not as clear on voice calls compared to regular.. not sure if my settings are messed up or what..
Trust me, flash this rom if you don't need wifi calling or are not with tmobile.
It's better, also includes apps to sd card.
http://forum.xda-developers.com/showthread.php?t=2287404
Sent from my LG-P769 using xda app-developers app
I don't really need WiFi calling. My signal is like, always strong in my city.
Sent from my LG-P760 using Tapatalk 2
I decided to chance it and flashed this Wind ROM (V21B) with the instructions from the "Offline Flashing" thread and was successful, but it's not reading the T-Mobile microSIM so it's basically stuck in the water, so to speak. Decided to redo it using the available T-Mobile V20D Jelly Bean ROM and even in spite of following the instructions in that Offline Flashing thread to a T - I'd just done the same thing to get the Wind ROM on it so I know the instructions are valid - now I can't get the T-Mobile ROM flashed because the update tool can't see the phone for some reason.
Rechecked everything, redid the steps twice, reset the phone, pulled the battery, did everything pretty much exactly the same (checked to make sure the debugging and unknown sources are checked, unchecked them both and rechecked them to make sure), restarted the phone a 3rd time and still the update tool can't see the phone. It shows up in Device Manager as required (LG modem and LG composite device), etc.
Am I not able to reflash or back up? Hrmmm... will keep trying I suppose, may just drop back to ICS and be done with it (assuming of course I can get this working again, that is).
br0adband said:
I decided to chance it and flashed this Wind ROM (V21B) with the instructions from the "Offline Flashing" thread and was successful, but it's not reading the T-Mobile microSIM so it's basically stuck in the water, so to speak. Decided to redo it using the available T-Mobile V20D Jelly Bean ROM and even in spite of following the instructions in that Offline Flashing thread to a T - I'd just done the same thing to get the Wind ROM on it so I know the instructions are valid - now I can't get the T-Mobile ROM flashed because the update tool can't see the phone for some reason.
Rechecked everything, redid the steps twice, reset the phone, pulled the battery, did everything pretty much exactly the same (checked to make sure the debugging and unknown sources are checked, unchecked them both and rechecked them to make sure), restarted the phone a 3rd time and still the update tool can't see the phone. It shows up in Device Manager as required (LG modem and LG composite device), etc.
Am I not able to reflash or back up? Hrmmm... will keep trying I suppose, may just drop back to ICS and be done with it (assuming of course I can get this working again, that is).
Click to expand...
Click to collapse
Did you try a factory reset?
Turn off and press volume down +home and power to initiate
I've done most everything at least 3 times so far (and tried 3 different USB cables, 3 different USB ports, etc) - the update tool is simply not seeing the phone anymore. It's listed in Device Manager as required (as stated, LG modem and LG USB composite device), then I'll restart the shttps server (with a freshly extracted copy), restart the update tool (also a freshly extracted copy) and even in spite of being able to see the device with Explorer, etc, the update tool simply can't find it anymore; the resulting codes are supposed to be:
0 = no device
1 = Normal connect
2 = Emergency connect
and each time it's 0, so I'm stumped now as to how to proceed. I'm able to use the P769 with T-Mobile and calling, but there's no data connection whatsoever which seems a bit odd considering I have data service and was using it an hour ago. I've used the hidden menu to ensure I'm set for automatic network setup, but the APNs under Mobile Networks aren't there - that screen is totally blank which is most likely why I'm not getting any data. I mean the page is completely blank when I select that option, it is as white as a blank sheet of paper with no info whatsoever.
I'm a bit baffled at this point, guess I should have just been patient and waited for T-Mobile to get around to dropping a proper fixed JB update.
Edit: will try to manually input the T-Mobile APN info and see what happens but at this point I'd just prefer to flash the V20D and see what that's doing, if I'm not happy with that because of the bugs then back to V10G if possible.
Second edit: well that didn't work either, it won't actually save the APN data I input (got it from a T-Mobile support page) so... it's broke-dead for data presently, geez.
Try entering the apn correctly and see if it saves. If not, it's most likely data corruption stemming from your previous T-Mobile rom
I have tmobile version of the p769 and the wind jb works perfectly for me. I did do a factory reset before the initial boot of the wind ROM by unplugging the battery right after the completion of flash and doing a hard reset.
Sent from my LG-P769 using xda app-developers app
I can comprehend a little data left over since no, I didn't do a full blown factory reset before the initial flash, but what I can't comprehend now is the update tool not seeing the phone anymore when all the PC connectivity appears to be functional across the board. I suppose I'll just wipe everything clean from the PC, get rid of all the software installed, all the LG drivers, and restart this and hope I can drop back to V10G, I've had enough with JB at this point - obviously a properly working phone (without that Wi-Fi battery life issue) is more valuable than a smoother running but somewhat janky device.
Let's hope this whole clean start thing works...
Edit:
And no, this is pretty much dead in the water now. APN data will not save, the LG update tool doesn't see the phone anymore (the status is always 0 even in spite of the device plainly being attached, showing up as required in Device Manager, other modes of operation like typical USB connectivity work just fine, can copy files to the device without issue from the PC). Did the full clean start of everything, using the latest 3.8.1 USB drivers, and so on.
Dammit...
Can this be flashed on a locked t-mobile P769. If so can some1 point me in the right direction?
br0adband said:
I can comprehend a little data left over since no, I didn't do a full blown factory reset before the initial flash, but what I can't comprehend now is the update tool not seeing the phone anymore when all the PC connectivity appears to be functional across the board. I suppose I'll just wipe everything clean from the PC, get rid of all the software installed, all the LG drivers, and restart this and hope I can drop back to V10G, I've had enough with JB at this point - obviously a properly working phone (without that Wi-Fi battery life issue) is more valuable than a smoother running but somewhat janky device.
Let's hope this whole clean start thing works...
Edit:
And no, this is pretty much dead in the water now. APN data will not save, the LG update tool doesn't see the phone anymore (the status is always 0 even in spite of the device plainly being attached, showing up as required in Device Manager, other modes of operation like typical USB connectivity work just fine, can copy files to the device without issue from the PC). Did the full clean start of everything, using the latest 3.8.1 USB drivers, and so on.
Dammit...
Click to expand...
Click to collapse
Are you using menu>save APN? Back button discards any settings. Also if epic.tmobile.com does not get you connected try fast.tmobile.com
Sent from my LG-P769 using xda app-developers app
---------- Post added at 04:44 PM ---------- Previous post was at 04:43 PM ----------
Kid_Ding said:
Are you using menu>save APN? Back button discards any settings. Also if epic.tmobile.com does not get you connected try fast.tmobile.com
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
epc.tmobile.com not epic lol
Sent from my LG-P769 using xda app-developers app
---------- Post added at 04:46 PM ---------- Previous post was at 04:44 PM ----------
sm_x said:
Can this be flashed on a locked t-mobile P769. If so can some1 point me in the right direction?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2173465
Sent from my LG-P769 using xda app-developers app
Yes, it was not saving the APN data by using Menu -> Save. Anywhooo...
After a somewhat even more convoluted process requiring me to muck around with fastboot in the omap4fastboot thread, I got the device recognized so it could be "seen" by the updater and then flashed V20D on it, presently doing a factory reset since it left some data from the Wind ROM around.
Now that I finally have the JB ROM on it I'll do some testing and see how it goes, I'm sure the Wi-Fi battery/power thing didn't just magically skip over me so I'll keep an eye on it. But at least now I can get to flashing again. Odd why that happened but, sometimes things do.
I've found that sometimes it's just a matter of restarting my computer to get the device recognized. It would suck if that was the reason.
Good luck on the tmobile rom and never stop trying
Sent from my LG-P769 using xda app-developers app
I am currently fully rooted, running the latest jasmineRom. I liked the stock based kernal, had some nice features like tap to turn on, etc, and haven't dabbled in other roms such as CMMod, LiquidSmooth etc on the G3. Honestly I don't know if they have some of the features for waking the screen by tapping it that make the G3 usable without any front buttons, and changing roms and recustomizing / installing everything is a bit of a bear, so I haven't experimented with it.
My phone has the 5.1.1 update downloaded, keeps wanting to schedule it. (It actually tried to install itself, but I think TWRP prevented it from working). So now I am faced with the question of, what to do?
Do I let 5.1.1 install, and thereby gain Android Pay, which I did like, but lose root, which I enjoy for letting me debloat my phone? (Also G3 tweeksbox) Those are really the only things I've used root for. Do I experiment with other roms? (And then, how do I return to stock? Does TWRP prevent me from doing so, or would it get taken out in the update? I honestly don't know and have yet to find that information). I have read the Flash back to Stock using the KDZ method, which is actually how I rooted my phone to begin with, but it seems that is under the assumption I am running a stock rom / bootloader to begin with.
Just trying to get some input from people far more familier with this than I. If there is a way back to stock, including bootloader, what ROM would you recommend I try?
Thanks in advance!
Hi! Questions go in Q&A.
Be aware that if you take 5.1.1 that so far you *can't* root even if you want to, and you also can't currently downgrade.
If you're looking to return to completely stock including the recovery, so that you can take OTAs in the future, then flash the 24B KDZ with LG Flash Tool 2014. If you want to be rooted but be able to turn root off and on, you can do that with any, although I think Pay only works with stock. Another user on here just found out that merely temporarily deactivating root allowed him to use Pay just fine. Probably have to reboot in between turning it on and off - not sure.
Here are my thoughts on the subject: http://forum.xda-developers.com/showpost.php?p=63191071&postcount=135
Personally, I like rooting and twrp b/c of nandoid backups, debloating, removing ads and using titanium backup. I would feel truly lost without these options (and, to be perfectly honest, I love tinkering with electronics). If you decide to pass on the update for now, freeze system update using titanium backup, then wipe cache and that should remove the downloaded update in memory prior to installation . It's really a personal choice, but for me, I will likely stay where I am now rather than give up root.
The only reason I really rooted this phone was to get rid of bloat and fix the weak notification volume. I've never been one to jump aboard new updates as soon as they're released. Gonna wait it out and see if something happens with the root situation.
Decided I might as well try a custom rom, never used a custom rom on a phone, only tablets. Titanium backup and custom recovery are valuable tools, and decided it was worth the risk.
Went with Liquid Smooth, which I think has auto-updates ala CM Mod. So I get the benefits of 5.1.1, without the hassle of Verizon. Going to see what I think.
Thanks for the replies!
The update deactivates wireless charging. That was the deal breaker for me.
Edit: Turns out my wife and I both had a bad update. I used repair assistant and wireless charging is working again.
a2597 said:
Decided I might as well try a custom rom, never used a custom rom on a phone, only tablets. Titanium backup and custom recovery are valuable tools, and decided it was worth the risk.
Went with Liquid Smooth, which I think has auto-updates ala CM Mod. So I get the benefits of 5.1.1, without the hassle of Verizon. Going to see what I think.
Thanks for the replies!
Click to expand...
Click to collapse
Ive been running a CM12 based ROM for months now, it fixes almost everything wrong with the 5.0.2 update and with this update blocking root and downgrading, it seems CM12 based ROMS are the best choice for now.
timboger said:
The update deactivates wireless charging. That was the deal breaker for me.
Click to expand...
Click to collapse
Where did you hear that? A web search shows inconsistent functionality starting with v5.0 with various carriers, including one report of someone who tried everything to get it to work and couldn't, so he reassembled his phone and tossed it on the charger, and it started working.
DeanGibson said:
Where did you hear that? A web search shows inconsistent functionality starting with v5.0 with various carriers, including one report of someone who tried everything to get it to work and couldn't, so he reassembled his phone and tossed it on the charger, and it started working.
Click to expand...
Click to collapse
Sorry, I should of been clearer. The update to 35b, 5.1.1, will render wireless charging useless. It can not be rooted. If you decide to update then you will loose root until the devs can figure it out. That will have to wait until the kdz is available. I have been wireless charging since I got the phone and bought the new back from ebay. It has worked without fail until the latest update.
Clarification requested
timboger said:
Sorry, I should of been clearer.
Click to expand...
Click to collapse
I should have been clearer as well. I take it that you are saying that wireless charging stopped working on your VS985 phones when you upgraded to v5.1.1. That's distinct from saying that wireless charging no longer works when anyone upgrades the LG G3 to v5.1.1.
Certainly your one two data points are significant, but I'd like to know if it's confirmed that it won't work on other VS985 phones that upgrade to v5.1.1 (35B).
I'm tempted to go buy one of the charging backs and pads. Where did you get yours? I seriously considered it a year ago when I bought the phone, but the lack of a nice belt clip deterred me. How are you carrying the phone (eg, belt clip or what)?
Edit: I was told that the charging back made the phone thicker. However, a little research seems to suggest that's only true for Verizon's "Circle case" (eg, a combined front and back), which I don't need. Someone even reported that they just cut off the front case, and then it fit their belt clip holder. Also, another reporter said that it charged much slower. Comments on all of this?
DeanGibson said:
I should have been clearer as well. I take it that you are saying that wireless charging stopped working on your VS985 phones when you upgraded to v5.1.1. That's distinct from saying that wireless charging no longer works when anyone upgrades the LG G3 to v5.1.1.
Certainly your one two data points are significant, but I'd like to know if it's confirmed that it won't work on other VS985 phones that upgrade.
I'm tempted to go buy one of the charging backs and pads. Where did you get yours? I seriously considered it a year ago when I bought the phone, but the lack of a nice belt clip deterred me. How are you carrying the phone (eg, belt clip or what)?
Edit: I was told that the charging back made the phone thicker. However, a little research seems to suggest that's only true for Verizon's "Circle case" (eg, a combined front and back), which I don't need. Someone even reported that they just cut off the front case, and then it fit their belt clip holder. Also, another reporter said that it charged much slower. Comments on all of this?
Click to expand...
Click to collapse
I have the vs985 on verizon, purchased about 1 week after it's release. It is rooted since stump and I have run either Jasmine or skydragon (currently sd5.0/4.2 kernel) . I purchased the charging sticker (available on ebay at the time). I was able to put the sticker onto the original back of the phone and wirelessly charge it both with a circle case (US lgg3) and without. I also bought a Korean circle case that had a charging sticker built into it. I removed the european charging sticker and replaced that one with one of the ones that I purchased on ebay (again, for US, wireless charging) and that worked as well (did not need the original oem back in this situation as the circle case back served as phone back, again this worked on a US wireless charger perfectly (I have a tylt). Never used a belt clip, but hope that this provides you with some useful information. Charging was complete and never slow.
a2597 said:
I am currently fully rooted, running the latest jasmineRom. I liked the stock based kernal, had some nice features like tap to turn on, etc, and haven't dabbled in other roms such as CMMod, LiquidSmooth etc on the G3. Honestly I don't know if they have some of the features for waking the screen by tapping it that make the G3 usable without any front buttons, and changing roms and recustomizing / installing everything is a bit of a bear, so I haven't experimented with it.
My phone has the 5.1.1 update downloaded, keeps wanting to schedule it. (It actually tried to install itself, but I think TWRP prevented it from working). So now I am faced with the question of, what to do?
Do I let 5.1.1 install, and thereby gain Android Pay, which I did like, but lose root, which I enjoy for letting me debloat my phone? (Also G3 tweeksbox) Those are really the only things I've used root for. Do I experiment with other roms? (And then, how do I return to stock? Does TWRP prevent me from doing so, or would it get taken out in the update? I honestly don't know and have yet to find that information). I have read the Flash back to Stock using the KDZ method, which is actually how I rooted my phone to begin with, but it seems that is under the assumption I am running a stock rom / bootloader to begin with.
Just trying to get some input from people far more familier with this than I. If there is a way back to stock, including bootloader, what ROM would you recommend I try?
Thanks in advance!
Click to expand...
Click to collapse
I don't understand the issue.
I have an LG G3 with TWRP, Xposed and root; I can use Android Pay.
I had to jump through hoops but I can use it. Adding cards is a pain, but I can do that too.
To get it working you have to temp-unroot.
Install and configure Pay.
Re-enable root.
You will need to install Xposed and the module that provides cloaking for root, for Pay called -> No Device Check http://repo.xposed.info/module/com.pyler.nodevicecheck
Now you should be able to use Android Pay.
Jasmine 9.0 is out. I'd try that out. Its 5.1.1 with root
xdabbeb has the 35b bootstack that can be flashed to get advanced calling features working. Read about it.
I was having sms issues on cm13, and it was suggested that I flash the TOT again.
Not sure what happened the first time I tried to flash the TOT, but I was following directions as always and just assumed it would work flawlessly as it has done in the past. It failed somewhere along the line but I wasn't paying too much attention .
Now the phone automatically boots into DL mode (after LG screen, unusual), and anytime I try to flash a TOT now the flash tool goes from "Waiting for Connection" to showing a PID and showing my IMEI as null (all 0's). After some googling around I realize that this is not good in the slightest. The flash tool will timeout after ~20s and try again, but just keeps timing out endlessy after 20s.
This looks to me like a brick but I don't have enough experience or knowledge to say for sure. If anyone has suggestions I would greatly appreciate it.
Try the 10B KDZ just for the hell of it. I'm sorry to hear you're having so much trouble. Don't do anything rash, we'll see what we can do.
I hope you have a TWRP backup of the EFS (IMEI) in a safe place or once you get the phone working you'll have to use QPST or some such to manually type in your IMEI.
roirraW "edor" ehT said:
Try the 10B KDZ just for the hell of it. I'm sorry to hear you're having so much trouble. Don't do anything rash, we'll see what we can do.
I hope you have a TWRP backup of the EFS (IMEI) in a safe place or once you get the phone working you'll have to use QPST or some such to manually type in your IMEI.
Click to expand...
Click to collapse
I tried flashing that kdz already, as well as the 47a. Both get up to that 4% like I had problems with before. Now the phone doesn't seem to want to boot into dl mode : ^) I can get into the system recovery but any of the options just take me to the LG boot screen.
And nope, no backups. I got this phone 4 days ago as a refurb to last me until the (supposedly) htc nexus phones in the fall. Never really got anywhere so didn't think to back anything up, especially not the imei. Never had a device be this finicky in my years rooting android devices.
Thanks for all your help man, but I may just have to chalk this one up as sunken costs and go back to my m7
Go with what roirraW "edor" ehT tells you first and foremost. What I'm posting is another option at last resort. If you dont have a backup of your imei, you will need an IMEI editor and use the IMEI that is printed inside your phone or on the box it came with.
I had the same problem. It's nerve racking but can be easily fixed. I'll look for the program I used and post it once I find it. Just so it's said, changing your IMEI is highly illegal. Make sure you restore your original that came with the device and not someone elses.
inexplicability said:
I tried flashing that kdz already, as well as the 47a. Both get up to that 4% like I had problems with before. Now the phone doesn't seem to want to boot into dl mode : ^) I can get into the system recovery but any of the options just take me to the LG boot screen.
And nope, no backups. I got this phone 4 days ago as a refurb to last me until the (supposedly) htc nexus phones in the fall. Never really got anywhere so didn't think to back anything up, especially not the imei. Never had a device be this finicky in my years rooting android devices.
Thanks for all your help man, but I may just have to chalk this one up as sunken costs and go back to my m7
Click to expand...
Click to collapse
I know it may seem useless, but take the battery out and leave it out for an hour or more, then try to put it into Download mode again. When you try to put it in Download mode now, what happens exactly? Are you checking in Windows' Device Manager to see if the phone shows up in the Modem and Port sections? Does it ever show up?
Was it a warranty (LG or Verizon) refurb and do you have the option to try to exchange it for another?
Sure - I just wish I could do more.
What @thebigindian said reminded me - you may have to restore the IMEI before you can flash the TOT (assuming you can get into Download mode or at least QHSUSB_BULK 9008 mode). I have no idea how to go about that, though, as I've never had to - I just know there are threads in these sections on how to do it.
thebigindian said:
Go with what roirraW "edor" ehT tells you first and foremost. What I'm posting is another option at last resort. If you dont have a backup of your imei, you will need an IMEI editor and use the IMEI that is printed inside your phone or on the box it came with.
I had the same problem. It's nerve racking but can be easily fixed. I'll look for the program I used and post it once I find it. Just so it's said, changing your IMEI is highly illegal. Make sure you restore your original that came with the device and not someone elses.
Click to expand...
Click to collapse
I've looked into restoring the imei, and have found that some users had success using a method for the lg g2, but most of these methods require some sort of booting. I am unable to boot to anything but the lg screen. I'll try why Rode says about leaving the battery out and see what happens from there.
roirraW "edor" ehT said:
I know it may seem useless, but take the battery out and leave it out for an hour or more, then try to put it into Download mode again. When you try to put it in Download mode now, what happens exactly? Are you checking in Windows' Device Manager to see if the phone shows up in the Modem and Port sections? Does it ever show up?
Was it a warranty (LG or Verizon) refurb and do you have the option to try to exchange it for another?
Sure - I just wish I could do more.
What @thebigindian said reminded me - you may have to restore the IMEI before you can flash the TOT (assuming you can get into Download mode or at least QHSUSB_BULK 9008 mode). I have no idea how to go about that, though, as I've never had to - I just know there are threads in these sections on how to do it.
Click to expand...
Click to collapse
I'll get back to you in a bit after the battery has been out for awhile.
I picked this up off of amazon as a refurb device. The first 2 devices I received were defective out of the box (first one had bent pins in usb port, second would bootloop and i didnt know as much about dl/recovery as i do now, it was probably fixable looking back) so that should have kept me away lol. I know I could probably get away with sending it back saying the device is defective or something, but it really is my fault (I believe) and wouldn't exactly feel good about doing that. Then again I don't exactly feel good about having a $120 brick lol.
inexplicability said:
I've looked into restoring the imei, and have found that some users had success using a method for the lg g2, but most of these methods require some sort of booting. I am unable to boot to anything but the lg screen. I'll try why Rode says about leaving the battery out and see what happens from there.
I'll get back to you in a bit after the battery has been out for awhile.
I picked this up off of amazon as a refurb device. The first 2 devices I received were defective out of the box (first one had bent pins in usb port, second would bootloop and i didnt know as much about dl/recovery as i do now, it was probably fixable looking back) so that should have kept me away lol. I know I could probably get away with sending it back saying the device is defective or something, but it really is my fault (I believe) and wouldn't exactly feel good about doing that. Then again I don't exactly feel good about having a $120 brick lol.
Click to expand...
Click to collapse
I was afraid of that (can't put the IMEI back in without booting). I understand what you're saying but I honestly wouldn't be surprised if there was something wrong with the device anyway and that is the cause of why it bricked so easily. I don't trust refurbs.
I had a good experience selling on Swappa once but I haven't bought any through there so no idea if the experience would be better. I wouldn't buy any refurbed one. There's a black one on there that says Mint condition for $150. It's funny, some of them say 16 GB - as far as I'm aware there's no 16 GB version of the VS985.
roirraW "edor" ehT said:
I was afraid of that (can't put the IMEI back in without booting). I understand what you're saying but I honestly wouldn't be surprised if there was something wrong with the device anyway and that is the cause of why it bricked so easily. I don't trust refurbs.
I had a good experience selling on Swappa once but I haven't bought any through there so no idea if the experience would be better. I wouldn't buy any refurbed one. There's a black one on there that says Mint condition for $150. It's funny, some of them say 16 GB - as far as I'm aware there's no 16 GB version of the VS985.
Click to expand...
Click to collapse
Yeah now I don't trust refurbs either haha. It was worth a shot though. But yeah I noticed that about the 16gb device too when I was looking for a device to purchase.
I only picked up the g3 because a friend of mine asked about rooting his g3, wondering if he could get some more life out of it as his was becoming sluggish with all the bloat and whatnot. Figured I need a new phone now anyway and I would be able to get a g3, figure it out, then help him. That worked out great, didn't it?
UPDATE:
@roirraW "edor" ehT just thought I'd give you an update. I plugged in the device to power and it stayed at the charging screen with the loading icon for awhile, then I came back and it was in download mode!! Plugged into my pc and let windows install the drivers (took like 20 min, unusually long time) and was able to flash the 10b tot. IMEI is still 0, but at least there are ways to change that. Thanks again for your advice!
UPDATE 2:
Restored IMEI using this method: http://forum.xda-developers.com/showthread.php?t=2701861
Confirmed that mobile data / sms / mms are in working order... Going to try flashing cm13 again if that doesn't work I'll go back to stock and debloat as recommended
inexplicability said:
UPDATE:
@roirraW "edor" ehT just thought I'd give you an update. I plugged in the device to power and it stayed at the charging screen with the loading icon for awhile, then I came back and it was in download mode!! Plugged into my pc and let windows install the drivers (took like 20 min, unusually long time) and was able to flash the 10b tot. IMEI is still 0, but at least there are ways to change that. Thanks again for your advice!
UPDATE 2:
Restored IMEI using this method: http://forum.xda-developers.com/showthread.php?t=2701861
Confirmed that mobile data / sms / mms are in working order... Going to try flashing cm13 again if that doesn't work I'll go back to stock and debloat as recommended
Click to expand...
Click to collapse
Wow. I'm always surprised when things actually turn around so well.
Do that IMEI (EFS) backup in TWRP although it must not have been too tough after all. You're welcome! It's helped me on various phones including this one from time to time.
roirraW "edor" ehT said:
Wow. I'm always surprised when things actually turn around so well.
Do that IMEI (EFS) backup in TWRP although it must not have been too tough after all. You're welcome! It's helped me on various phones including this one from time to time.
Click to expand...
Click to collapse
I'll do an imei and nandroid backup once i get everything up and running. Tried using dirty unicorn, but google play services was failing. Tried cm13 but ran into sms issues again. Reluctantly installed stock 47a w/ debloat and it seems to be working ok.
Going to go off of your recommendations and use the xposed modules mentioned in the 47a thread until a more stable aosp based rom is available.
You may have actually helped me with my thread/issue, unwittingly.
Your symptoms are similar to what happened when I flashed anything lower than 46A bootloader wise... it would get a black screen (this is different than yours but keep reading), register as a device in download mode without any keypresses, and then refuse to flash the same way with all 0's IMEI.
It never occured to me to pull the battery for an hour. Maybe I should try that?
EDIT: ...And nope, that did not work either. I guess I just have to wait until marshmellow bootloader is exploited somehow...
Hi,
I, like many others, got forced onto Android 11. I have a lot of problems with it. With or without root. The most annoying of which is the wifi aggressively dropping/changing. Bluetooth failures. Volume drops that don't return to normal, forcing a reboot to fix. Clock and background/screen saver problems. System UI crashing. Keyboard freezing and lagging on certain sites with textareas. I used my phone without root for a couple days after the forced upgrade and all of these issues were present with or without magisk modules.
I'm interested in going back to Android 10 and blocking the a11 OTA in Hosts.
I'd like to get some help with a couple things. I'd like to make a FULL flashable backup of my current device as is. Just in case I mess something up, I can get back to this current state as worst case, very easily. Do I use the MSM tool and copy something? Do I boot twrp and push something over? Please advise the safe and smart way to get right back to a 1:1 of current install. I want to be very sure about this part.
After I know which way I can safely get back to current state, can I use the MSM tool to wipe and flash an older build of Android 10? Or is it a problem after being on 11 because of some restrictions (partitions, RO, twrp no mount) somewhere?
If I can get back to an older build of Android 10, I have a couple options (grayhat and httpcanary) to monitor the traffic to see what we need to block in Hosts for sure.
I'm open to other suggestions also. Someone in the root thread said they proactively tried to disable some services around update and it was still forced on them.
OnePlus 7T Pro 5G McLaren TMobile
Android 11.0.1.2HD61B
(Carrier unlocked, bootloader unlocked, magisk root)
Thanks for any help
Disable the T-mobile update app or ask them to disable it on their end, they can.
Backup all critical data by direct file transfer and verify... just in case.
There's no way to do a full nandroid backup, e.g. restoring things exactly back to how they are now. Best you can do is use the app Swift Backup to backup app data/settings along with Google's backup and OP's backup app.
As for OOS11, have you tried resetting back to stock (factory reset while running OOS11)? Chances are you just have some leftover things from OOS10 that didn't play well with the upgrade. So before you abandon OOS11, try that first (factory reset from stock recovery). Make sure you've copied any backups to your PC first. If the issues come back after restoring your backup from Swift Backup or from Google or OP, then you need to find out exactly what app(s) are causing issue or just start from scratch.
As for the MSM Tool, it will restore you back to OOS10 just fine on its own.
Lastly, the OTA updates are downloaded from https://android.googleapis.com
For example, the url for the latest OTA to go from latest version of OOS10 (10.0.43) to first version of OOS11 (11.0.1.2) was
https://android.googleapis.com/packages/ota-api/package/45ba72b0b2f7c643a09d2d0875459cd01b8db998.zip
I pulled that from the update log. So blocking
https://android.googleapis.com/packages/ota-api/*/
in AdBlock or other hosts file app should do the trick. It may still see an update available, but it will definitely continue to fail when trying to download it.
But try OOS11 clean (after a factory reset). I bet all your problems will go away. I have exact same phone, not a single issue on OOS11, bootloader unlocked, latest version of Magisk.
starcms said:
There's no way to do a full nandroid backup, e.g. restoring things exactly back to how they are now. Best you can do is use the app Swift Backup to backup app data/settings along with Google's backup and OP's backup app.
As for OOS11, have you tried resetting back to stock (factory reset while running OOS11)? Chances are you just have some leftover things from OOS10 that didn't play well with the upgrade. So before you abandon OOS11, try that first (factory reset from stock recovery). Make sure you've copied any backups to your PC first. If the issues come back after restoring your backup from Swift Backup or from Google or OP, then you need to find out exactly what app(s) are causing issue or just start from scratch.
As for the MSM Tool, it will restore you back to OOS10 just fine on its own.
Lastly, the OTA updates are downloaded from https://android.googleapis.com
For example, the url for the latest OTA to go from latest version of OOS10 (10.0.43) to first version of OOS11 (11.0.1.2) was
https://android.googleapis.com/packages/ota-api/package/45ba72b0b2f7c643a09d2d0875459cd01b8db998.zip
I pulled that from the update log. So blocking
https://android.googleapis.com/packages/ota-api/*/
in AdBlock or other hosts file app should do the trick. It may still see an update available, but it will definitely continue to fail when trying to download it.
But try OOS11 clean (after a factory reset). I bet all your problems will go away. I have exact same phone, not a single issue on OOS11, bootloader unlocked, latest version of Magisk.
Click to expand...
Click to collapse
Thanks so much for the detailed reply.
My main reason for rooting my phone is to have full speed tethering. If that worked, I would try a reset. Since it doesn't, it's a good excuse to go back to 10 on its own for me.
No simple method for a full nandroid backup is going to slow me down. I need to go thru my apps and make sure I don't forget about anything important for a reset or a downgrade.
Do you have any hypothesis on why they forced Android 11 so hard?
During the time I wrote this message, my wifi switched networks a half dozen times. When this first started after the force to a11, I thought it was strange because I wasn't rooted and any modules shouldn't have been affecting anything. They're only added props (for the tethering module anyway). I don't have the Qualcomm crash others are reporting but maybe something in the new settings are related and causing both problems, theirs and mine.
Do you have multiple APs within reach of your phone? I've tried to disable/enable different connection options in the wifi settings and handoff settings. Nothing seems to help. It wants to drop me off my AP to any closer AP, constantly. Which is particularly annoying because I'm constantly in ssh sessions and that closes them. I can avoid that somewhat by forgetting the other APs near me so it tries to stay connected to just one but I shouldn't have to do that. I never had an issue before the update. In fact, I was actually really happy with how stable Android 10 was for our device.
Appreciative said:
Thanks so much for the detailed reply.
My main reason for rooting my phone is to have full speed tethering. If that worked, I would try a reset. Since it doesn't, it's a good excuse to go back to 10 on its own for me.
No simple method for a full nandroid backup is going to slow me down. I need to go thru my apps and make sure I don't forget about anything important for a reset or a downgrade.
Do you have any hypothesis on why they forced Android 11 so hard?
During the time I wrote this message, my wifi switched networks a half dozen times. When this first started after the force to a11, I thought it was strange because I wasn't rooted and any modules shouldn't have been affecting anything. They're only added props (for the tethering module anyway). I don't have the Qualcomm crash others are reporting but maybe something in the new settings are related and causing both problems, theirs and mine.
Do you have multiple APs within reach of your phone? I've tried to disable/enable different connection options in the wifi settings and handoff settings. Nothing seems to help. It wants to drop me off my AP to any closer AP, constantly. Which is particularly annoying because I'm constantly in ssh sessions and that closes them. I can avoid that somewhat by forgetting the other APs near me so it tries to stay connected to just one but I shouldn't have to do that. I never had an issue before the update. In fact, I was actually really happy with how stable Android 10 was for our device.
Click to expand...
Click to collapse
Honestly I can't help. OOS11 made my phone even better than it ever has been. No exaggeration. And not a single bug or even issue. They probably saw the same results on their test phones and pushed it really hard because they knew people had been waiting a very long time for it.
That's why I really think you have some trash left behind from your OOS10 install that made the upgrade to OOS11 go crazy. Once you get your backups done, please try a factory reset on OOS11 and don't restore any Google or other backups and just see if you have any issues. It could all be due simply to needing a "fresh install"
Edit: As for high speed tethering, is that accomplished with a Magisk module? If so, it probably needs the tiniest change in directory names/path to be compatible with OOS11, just like the boot and shutdown animation modules
Edit2: And yes, my phone can see at least 15 APs while at home. Never have any trouble connecting via 802.11ac on 2.4 or 5ghz at home, and never had any trouble with other random hotspots.
You've got some OOS10 settings/junk/leftovers interfering with OOS11. Not trying to sound like an idiot TMobile tech, but in this case you do need to factory reset and I bet all issues go away.
starcms said:
Honestly I can't help. OOS11 made my phone even better than it ever has been. No exaggeration. And not a single bug or even issue. They probably saw the same results on their test phones and pushed it really hard because they knew people had been waiting a very long time for it.
That's why I really think you have some trash left behind from your OOS10 install that made the upgrade to OOS11 go crazy. Once you get your backups done, please try a factory reset on OOS11 and don't restore any Google or other backups and just see if you have any issues. It could all be due simply to needing a "fresh install"
Edit: As for high speed tethering, is that accomplished with a Magisk module? If so, it probably needs the tiniest change in directory names/path to be compatible with OOS11, just like the boot and shutdown animation modules
Edit2: And yes, my phone can see at least 15 APs while at home. Never have any trouble connecting via 802.11ac on 2.4 or 5ghz at home, and never had any trouble with other random hotspots.
You've got some OOS10 settings/junk/leftovers interfering with OOS11. Not trying to sound like an idiot TMobile tech, but in this case you do need to factory reset and I bet all issues go away.
Click to expand...
Click to collapse
I believe you. I don't think you sound like the robot techs either. Yes, it can be accomplished with a magisk module. Which I first tried to edit like the animation modules. When that was unsuccessful, I did it manually by creating/editing props. The tethering provision and dun props. I even tried them in combination with another apn using only ipv4.
Some other phones report the module still working in Android 11 so I was hopeful it was just a path adjustment or that manual would work. It's still likely it could be done but I have to balance how long someone with more experience to bring a solution might take, with how long I can get by with this 600kbps throttle. I have kids and having internet (capable of YouTube, 600kbps doesn't cut it, especially on multiple devices) available for long car rides is really helpful after they're tired of playing Eye-Spy
Appreciative said:
I believe you. I don't think you sound like the robot techs either. Yes, it can be accomplished with a magisk module. Which I first tried to edit like the animation modules. When that was unsuccessful, I did it manually by creating/editing props. The tethering provision and dun props. I even tried them in combination with another apn using only ipv4.
Some other phones report the module still working in Android 11 so I was hopeful it was just a path adjustment or that manual would work. It's still likely it could be done but I have to balance how long someone with more experience to bring a solution might take, with how long I can get by with this 600kbps throttle. I have kids and having internet (capable of YouTube, 600kbps doesn't cut it, especially on multiple devices) available for long car rides is really helpful after they're tired of playing Eye-Spy
Click to expand...
Click to collapse
Post the Magisk module for high-speed tethering and I'll take a look at it. It'll either be really simple to get it working on OOS11...or not lol.
All credit to the authors and yadda yadda.
There's another one floating around.
In this one, I changed it to be /product/ but didn't have success.
If you do have success on a11 with it, that'd be cool. I can find out if a reset will clear up these other issues I have or not
Hello everyone, I'm in a similar situation though I was wondering if it might be a different problem.
So I bought a 7TPro Mclaren off Ebay and for the last year, it's worked fine. the phone came factory unlocked, with zero issues connecting to Telus (my Canadian provider). Last month my phone force-updated itself to android 11, and nothing but bad things have happened since. screen frame-rate tanks randomly, apps are slow, battery's tanked, the works.
After resetting the cache 3 or 4 times and still having issues, I reset the phone to factory, stock settings, but the phone still performs poorly Maybe because I re-added all my apps and pictures via Oneplus backup? either way, I'm very fed up with how the phone has been especially the battery, so I've been looking into downgrading back to Android 10, but it seems that the Tmobile variant has trouble doing that (i.e. no simple menu option).
Should I try downgrading to Android 10 again and not bothering with a backup? I don't have too much to lose as of right now so I don't mind resetting it again, but if restoring all my pictures via backup is what's causing the issue I'm willing to do that. Should I make another Oneplus backup before I do this, or should I back up the data to my PC first? I find it very irritating that T-mobile forced this update so I will try and block the upgrade in my hosts but I'm worried that won't work because I don't plan to root my phone and block the hosts files.
Any tips or help would be appreciated!
DhoomLard said:
Hello everyone, I'm in a similar situation though I was wondering if it might be a different problem.
So I bought a 7TPro Mclaren off Ebay and for the last year, it's worked fine. the phone came factory unlocked, with zero issues connecting to Telus (my Canadian provider). Last month my phone force-updated itself to android 11, and nothing but bad things have happened since. screen frame-rate tanks randomly, apps are slow, battery's tanked, the works.
After resetting the cache 3 or 4 times and still having issues, I reset the phone to factory, stock settings, but the phone still performs poorly Maybe because I re-added all my apps and pictures via Oneplus backup? either way, I'm very fed up with how the phone has been especially the battery, so I've been looking into downgrading back to Android 10, but it seems that the Tmobile variant has trouble doing that (i.e. no simple menu option).
Should I try downgrading to Android 10 again and not bothering with a backup? I don't have too much to lose as of right now so I don't mind resetting it again, but if restoring all my pictures via backup is what's causing the issue I'm willing to do that. Should I make another Oneplus backup before I do this, or should I back up the data to my PC first? I find it very irritating that T-mobile forced this update so I will try and block the upgrade in my hosts but I'm worried that won't work because I don't plan to root my phone and block the hosts files.
Any tips or help would be appreciated!
Click to expand...
Click to collapse
Sorry to hear that.
Do fresh installs for the apps.
Do direct file transfers to/from the PC for all other critical data. "Restore it all" apps can fail miserably and are hard to verify the data they supposedly stored.
11 is a mess but this might help... or not.
DhoomLard said:
Hello everyone, I'm in a similar situation though I was wondering if it might be a different problem.
So I bought a 7TPro Mclaren off Ebay and for the last year, it's worked fine. the phone came factory unlocked, with zero issues connecting to Telus (my Canadian provider). Last month my phone force-updated itself to android 11, and nothing but bad things have happened since. screen frame-rate tanks randomly, apps are slow, battery's tanked, the works.
After resetting the cache 3 or 4 times and still having issues, I reset the phone to factory, stock settings, but the phone still performs poorly Maybe because I re-added all my apps and pictures via Oneplus backup? either way, I'm very fed up with how the phone has been especially the battery, so I've been looking into downgrading back to Android 10, but it seems that the Tmobile variant has trouble doing that (i.e. no simple menu option).
Should I try downgrading to Android 10 again and not bothering with a backup? I don't have too much to lose as of right now so I don't mind resetting it again, but if restoring all my pictures via backup is what's causing the issue I'm willing to do that. Should I make another Oneplus backup before I do this, or should I back up the data to my PC first? I find it very irritating that T-mobile forced this update so I will try and block the upgrade in my hosts but I'm worried that won't work because I don't plan to root my phone and block the hosts files.
Any tips or help would be appreciated!
Click to expand...
Click to collapse
Try another factory reset on OOS11 but don't restore any backups including Google app backups and see if problem still persists. Don't even bother logging in with your Google account at first. Just see if issues are fixed.
Morning b4 coffee rant:. I'm so tired of hearing this, TMobile/OnePlus didn't "force update" anyone's phones any more so than Google or any other manufacturer. This is my first OnePlus phone, probably will be the last because of all the serious quirks in rooting and just horrible software engineering by OnePlus and I want to throw it thru the window sometimes, but that's half from me screwing with it lol. Anyway, so I'm not OnePlus's biggest fan, but they didn't do crazy by releasing OOS11. That's how updates work...People had been (rightfully) been expecting it for a long time. And I don't have a single issue with it.
My battery life is much worse also. I blame it on the constant/aggressive wifi changes.
starcms said:
Try another factory reset on OOS11 but don't restore any backups including Google app backups and see if problem still persists. Don't even bother logging in with your Google account at first. Just see if issues are fixed.
Morning b4 coffee rant:. I'm so tired of hearing this, TMobile/OnePlus didn't "force update" anyone's phones any more so than Google or any other manufacturer. This is my first OnePlus phone, probably will be the last because of all the serious quirks in rooting and just horrible software engineering by OnePlus and I want to throw it thru the window sometimes, but that's half from me screwing with it lol. Anyway, so I'm not OnePlus's biggest fan, but they didn't do crazy by releasing OOS11. That's how updates work...People had been (rightfully) been expecting it for a long time. And I don't have a single issue with it.
Click to expand...
Click to collapse
They did force the update. There was no further postponement available. It's not cool that we have to jump thru hoops to take an OTA but the full version upgrade ignores root woes and forces itself to install. I don't mind jumping the hoops, so long as it's consistent.
I've never had this force update issue on any previous device. I've been able to ignore it indefinitely, and if rooted, need to do a manual intervention to take the OTA. I was in the middle of doing something when my phone shut down and installed a11.
This isn't my first OnePlus device. It is my first carrier tied/coupled OnePlus device. And will definitely be my last carrier coupled phone. I want to give OnePlus another chance. I had the 8 Pro and it was lackluster to say the least. I found a great medium with this device. It offered similar specs, 5G, good build quality at a reasonable price.
It may be true that other manufacturers force updates on some devices but it wasn't true for me with the Nexus or Pixel phones I had. Or my previous OnePlus device (5T/8P).
A lot of us are intentionally choosing OnePlus for the root and ubl friendliness with good specs.
I don't think anyone is saying A11 shouldn't be offered, it should be of course. It just shouldn't be forced and the safety net we thought we had to prevent that, was also swallowed up.
Give OnePlus another chance, this phone is not the typical OnePlus experience I've come to love. Or maybe this is the new OnePlus... I'm gonna give them another shot.
As a side note to this, my wife wanted the Samsung s21, coming from a OnePlus device. She is very disappointed with the s21 in just about every aspect other than the picture quality. Oppo and OnePlus are merging, I'm not even sure where to go after OnePlus
Appreciative said:
My battery life is much worse also. I blame it on the constant/aggressive wifi changes.
They did force the update. There was no further postponement available. It's not cool that we have to jump thru hoops to take an OTA but the full version upgrade ignores root woes and forces itself to install. I don't mind jumping the hoops, so long as it's consistent.
I've never had this force update issue on any previous device. I've been able to ignore it indefinitely, and if rooted, need to do a manual intervention to take the OTA. I was in the middle of doing something when my phone shut down and installed a11.
This isn't my first OnePlus device. It is my first carrier tied/coupled OnePlus device. And will definitely be my last carrier coupled phone. I want to give OnePlus another chance. I had the 8 Pro and it was lackluster to say the least. I found a great medium with this device. It offered similar specs, 5G, good build quality at a reasonable price.
It may be true that other manufacturers force updates on some devices but it wasn't true for me with the Nexus or Pixel phones I had. Or my previous OnePlus device (5T/8P).
A lot of us are intentionally choosing OnePlus for the root and ubl friendliness with good specs.
I don't think anyone is saying A11 shouldn't be offered, it should be of course. It just shouldn't be forced and the safety net we thought we had to prevent that, was also swallowed up.
Give OnePlus another chance, this phone is not the typical OnePlus experience I've come to love. Or maybe this is the new OnePlus... I'm gonna give them another shot.
As a side note to this, my wife wanted the Samsung s21, coming from a OnePlus device. She is very disappointed with the s21 in just about every aspect other than the picture quality. Oppo and OnePlus are merging, I'm not even sure where to go after OnePlus
Click to expand...
Click to collapse
You can block OTA a couple different ways. I've done it for over 5 years with AT&T, no root needed.
My 10+ is still running happily on Pie.
Appreciative said:
A lot of us are intentionally choosing OnePlus for the root and ubl friendliness with good specs.
Oppo and OnePlus are merging, I'm not even sure where to go after OnePlus
Click to expand...
Click to collapse
Xiaomi/Redmi/Poco meets the root and ubl friendliness. In some countries, they still have warranty coverage after unlock bootloader.
Good specs or not is vague between different phones.
Check XDA Xiaomi category and see the reply and thread count. It's to some point a sign of better price to the specs.
Use GSMarena to compare the spec.
Appreciative said:
Give OnePlus another chance, this phone is not the typical OnePlus experience I've come to love. Or maybe this is the new OnePlus... I'm gonna give them another shot.
Click to expand...
Click to collapse
Sadly, OnePlus hasn't been typical OnePlus in well over a year. Look how slow updates are now even for their latest non-carrier flagships beginning around 7T time (and can start to be seen as early as the 6T).
Appreciative said:
As a side note to this, my wife wanted the Samsung s21, coming from a OnePlus device. She is very disappointed with the s21 in just about every aspect other than the picture quality. Oppo and OnePlus are merging, I'm not even sure where to go after OnePlus
Click to expand...
Click to collapse
Oppo and OnePlus are merging, like you said, so won't they still continue producing flagship phones at a manic rate, like Samsung? At least Samsung has gotten much better with the speed of OTA updates, while OnePlus has tanked.
We're guaranteed Android 12 for our phones. Let's see how long it takes for us to get it, probably more than a year after I make this post. The 6T is still waiting for OOS11.
To be honest, receiving the 8 Pro was disappointing. I had the pixel 2xl and it's the only thing I've returned in a decade. I got the 5T for half the price and couldn't believe how amazing that phone was. It's still alive and crack free. I put it through a lot.
Getting the 8 Pro, I knew it was $1k but I expected a lot. I was disappointed. I liked it but not $1k-liked-it. And I realized then, that maybe OnePlus had already ended their founding principles. I was most disappointed that nothing about the 8P was pushing the envelope. The 5T was breaking the envelope and the 6 was doing big moves with giant storage and ufs3 speed. After that, partially because of how well the 5T was made, I didn't follow what they were doing. I didn't need to. Now we are at OP9 and you may be right that 'that oneplus' isn't here anymore.
I did look at some oppo devices. I knew that's the parent/sister company to OnePlus and would find similar features. It just worked out that the 7T Pro 5G dropped right after I got the 8P and I traded back.
I guess I got spoiled
Appreciative said:
To be honest, receiving the 8 Pro was disappointing. I had the pixel 2xl and it's the only thing I've returned in a decade. I got the 5T for half the price and couldn't believe how amazing that phone was. It's still alive and crack free. I put it through a lot.
Getting the 8 Pro, I knew it was $1k but I expected a lot. I was disappointed. I liked it but not $1k-liked-it. And I realized then, that maybe OnePlus had already ended their founding principles. I was most disappointed that nothing about the 8P was pushing the envelope. The 5T was breaking the envelope and the 6 was doing big moves with giant storage and ufs3 speed. After that, partially because of how well the 5T was made, I didn't follow what they were doing. I didn't need to. Now we are at OP9 and you may be right that 'that oneplus' isn't here anymore.
I did look at some oppo devices. I knew that's the parent/sister company to OnePlus and would find similar features. It just worked out that the 7T Pro 5G dropped right after I got the 8P and I traded back.
I guess I got spoiled
Click to expand...
Click to collapse
That's one reason I got this phone, OnePlus's prices are thru the roof. And no, I don't want any Nord crap. I want a flagship phone at a reasonable price. Got my 7T Pro 5G Mclaren for $500 brand new from eBay the day after the OP8/Pro launched. I just couldn't justify spending $1000 on a phone and I never will.