I could swear over the last decade+ I read a number of times that the Android OS check for update function currently located under System -> System Update was improved or fixed to actually check for and initiate the latest update. Here I am in 2023 on a Pixel, it's been a week since the Jan updates were released and published on Google's Factory Images pages and still, nothing. No OTA found. What is the point of this function? Had it EVER worked? Why isn't it seeing the update that plainly exists?
I understand the logic of *pushing* the OTA in waves, but if a user is manually hitting the check, they're more of a power user and let them have at it. Annoyed I have to ADB manually push updates cuz the built in function has never worked in a timely manner.
Yes it does work. No, I don't know why it didn't this time. Agreed that applying the update via ADB is annoying, especially when you have to patch boot.img with Magisk beforehand.
deusfaux said:
I could swear over the last decade+ I read a number of times that the Android OS check for update function currently located under System -> System Update was improved or fixed to actually check for and initiate the latest update. Here I am in 2023 on a Pixel, it's been a week since the Jan updates were released and published on Google's Factory Images pages and still, nothing. No OTA found. What is the point of this function? Had it EVER worked? Why isn't it seeing the update that plainly exists?
Click to expand...
Click to collapse
Someone confirm or deny, but in the USA at least doesn't the carrier control when the OTA is actually pushed to the customer?
Likely there is nothing wrong with the System update function of the phone, your carrier or Google just hasn't pinged your phone yet. At least there is an easy way to sideload if you get impatient, unlike some other phones.
poit said:
Someone confirm or deny, but in the USA at least doesn't the carrier control when the OTA is actually pushed to the customer?
Likely there is nothing wrong with the System update function of the phone, your carrier or Google just hasn't pinged your phone yet. At least there is an easy way to sideload if you get impatient, unlike some other phones.
Click to expand...
Click to collapse
That's not really a thing anymore and hasn't been for years. Google sells unlocked phones, updates can be downloaded from Wifi, the carrier isn't involved in most cases.
deusfaux said:
That's not really a thing anymore and hasn't been for years. Google sells unlocked phones, updates can be downloaded from Wifi, the carrier isn't involved in most cases.
Click to expand...
Click to collapse
This article posted today seems to infer that carriers still have the final say before pushing out OTA updates to users. It suggests that in the USA T-Mobile is delaying the January update due to unstated compatibility issues.
From the article:
The folks over at Droid-Life unearthed a Reddit comment from a T-Mobile employee who cites an unspecified issue that is causing T-Mobile to hold back these recent updates, but the comment has since been deleted.
Click to expand...
Click to collapse
Like I said, probably not an issue with your phone.
9to5Google: Latest Google Pixel updates have been delayed on T-Mobile and Google Fi for many
I don't even understand what's going on with that news story. Is the suggestion that google purchased pixels read which carrier the phone is on at that moment, compare to a list maintained by Google and decide whether to get the universal/generic OTA or not?
Anyways, yeah I'm not on any of those carriers anyhow.
There's been speculation that the phone validates the boot partition (where Magisk lives) and if it doesn't match the expected hash, it remembers that mismatch for some time even if Magisk is uninstalled and won't update - but I don't know if that's just speculation or if it's been proven. In the meantime, there's PixelFlasher - obviously downloading the file manually is less convenient, and I think the bootloader needs to be unlocked, but it works, and badabing2003 has made the rest of the process as quick and easy for us as possible. Or there's sideloading, which might not need an unlocked bootloader? (There are USB issues with that for some, but there's a fix for that.)
Jaitsu said:
There's been speculation that the phone validates the boot partition (where Magisk lives) and if it doesn't match the expected hash, it remembers that mismatch for some time even if Magisk is uninstalled and won't update - but I don't know if that's just speculation or if it's been proven. In the meantime, there's PixelFlasher - obviously downloading the file manually is less convenient, and I think the bootloader needs to be unlocked, but it works, and badabing2003 has made the rest of the process as quick and easy for us as possible. Or there's sideloading, which might not need an unlocked bootloader? (There are USB issues with that for some, but there's a fix for that.)
Click to expand...
Click to collapse
The fix : using a usb-a to usb-c cable cconnected on a USB 2.0 port
dexlemaffo said:
The fix : using a usb-a to usb-c cable cconnected on a USB 2.0 port
Click to expand...
Click to collapse
There's another, actually! I found this one in an obscure forum post a while ago and I've been spreading it around ever since - no more screwing around with USB 2.0 hubs/ports and slow speeds. Details here: https://forum.xda-developers.com/t/...ith-android-flash-tool.4525811/#post-87865327
Jaitsu said:
There's been speculation that the phone validates the boot partition (where Magisk lives) and if it doesn't match the expected hash, it remembers that mismatch for some time even if Magisk is uninstalled and won't update - but I don't know if that's just speculation or if it's been proven. In the meantime, there's PixelFlasher - obviously downloading the file manually is less convenient, and I think the bootloader needs to be unlocked, but it works, and badabing2003 has made the rest of the process as quick and easy for us as possible. Or there's sideloading, which might not need an unlocked bootloader? (There are USB issues with that for some, but there's a fix for that.)
Click to expand...
Click to collapse
This might explain why after the October OTA (I'm rooted) google bombarded me with update notifications and even there annoying white popup modal begging me to update until... The notification AND the updates vanished completely. I'd go to check for updates manually all the way up to a few days ago and it would tell me I'm already on the latest version. After the January 5th update came out I just gave up on the OTA and used pixel flasher. Great experience, easy to use, fast and worked flawlessly. I even used pixel flasher on Linux and it worked exactly as advertised (for some reason it wouldn't pick up my device after it entered fastboot on windows).
Thanx for the usb fix Jaitsu! Will keep it just in case...
Related
Hello,
I own the kindle fire HDX 8.9 3rd generation. Yesterday i rerolled my version back to 3.2.4, everything seemed to be working just fine.
But after i closed my case and reopened it after half an hour my device was shutted down (the battery was 80%). Since i've been trying to turn it on with no succes. I've also contacted amazon support who were willing to give me an "huge" sale on my next purchase (20$) since they don't think it will ever work again.
On my pc in device manager my kindle does show up, but when i try to install adb drivers i get an error 10.
I'm hoping to get some help here.
HybridLion said:
Hello,
I own the kindle fire HDX 8.9 3rd generation. Yesterday i rerolled my version back to 3.2.4, everything seemed to be working just fine.
But after i closed my case and reopened it after half an hour my device was shutted down (the battery was 80%). Since i've been trying to turn it on with no succes. I've also contacted amazon support who were willing to give me an "huge" sale on my next purchase (20$) since they don't think it will ever work again.
On my pc in device manager my kindle does show up, but when i try to install adb drivers i get an error 10.
I'm hoping to get some help here.
Click to expand...
Click to collapse
Did you block OTA and/or disable WiFi after rolling back to 3.2.8? If not you likely received an update from Amazon which often leads to a hard brick (no recovery).
What version were you on before and did you directly edit build prop?
Try holding the power button for up to 60 sec. Any response?
Davey126 said:
Did you block OTA and/or disable WiFi after rolling back to 3.2.8? If not you likely received an update from Amazon which often leads to a hard brick (no recovery).
What version were you on before and did you directly edit build prop?
Try holding the power button for up to 60 sec. Any response?
Click to expand...
Click to collapse
No i didn't block the OTA, i wasn't even planning on rooting and stuff, i downloaded the 3.2.4 from amazons site.
I downgraded from the newest versien 4.?.? (it didn't work with my vpn)
I have absolutely no response when pressing it for 60 seconds
HybridLion said:
No i didn't block the OTA, i wasn't even planning on rooting and stuff, i downloaded the 3.2.4 from amazons site.
I downgraded from the newest versien 4.?.? (it didn't work with my vpn)
I have absolutely no response when pressing it for 60 seconds
Click to expand...
Click to collapse
You can't go from 4.x to anything below 3.2.8. Amazon incorporated anti-rollback protection after 3.2.6. If you try to install an earlier version it will permanently disable the device. Also known as an 'efuse'. Sorry mate, there is no recovery.
Davey126 said:
You can't go from 4.x to anything below 3.2.8. Amazon incorporated anti-rollback protection after 3.2.6. If you try to install an earlier version it will permanently disable the device. Also known as an 'efuse'. Sorry mate, there is no recovery.
Click to expand...
Click to collapse
What the ****...
Why the fuc*k* do they offer a download of 3.2.5 on their website?
So there is seriously no way to recover it? Well good by all my brithday money:good:
**** you amazon
HybridLion said:
What the ****...
Why do they offer a download of 3.2.5 on their website?
So there is seriously no way to recover it? Well good by all my brithday money:good:
**** you amazon
Click to expand...
Click to collapse
Really sorry this happened. For future reference system images are supplied to repair or upgrade a device. Downgrades are always risky and rarely supported regardless of mfg. In this case a little knowledge (likely gained through these forums) met a loaded gun. Unfortunately, there is no known fix to an efuse brick.
Davey126 said:
Really sorry this happened. For future reference system images are supplied to repair or upgrade a device. Downgrades are always risky and rarely supported regardless of mfg. In this case a little knowledge (likely gained through these forums) met a loaded gun. Unfortunately, there is no known fix to an efuse brick.
Click to expand...
Click to collapse
Yeah i feel like a huge turd...
Well thanks anyway... F#king amazon :c
Have you looked at some of the possible techniques around from last year? There were reports of holding the power button down for over a minute to try and get to Fastboot or something... have a look around and you may find something, hope isn't always lost.
You can get into fastboot by holding the minus button while booting, but I am not sure how much it will help with a locked boot loader. Technically, it should flash a factory image, but I am not sure anyone has gotten that to work on the hdx. Note, if you try this, the windows drivers are a pain and there is a special way to run commands for the hdx. Check out the boot unlock op for the commands, the rest of the thread for the drivers, and know you are in uncharted territory.
Good luck,
Leko
From my understanding, blowing an eFuse is physical and thus irreversible unless you replace the actual chip.
I messed mine up, too I believe. I tried flashing the new safestrap ROM with the older safestrap. And now only the gray kindle fire logo stays on. I tried holding down the power button a minute, but just turns the gray logo off and on. I'm assuming there is no way out of this, correct?
manymarius73 said:
I messed mine up, too I believe. I tried flashing the new safestrap ROM with the older safestrap. And now only the gray kindle fire logo stays on. I tried holding down the power button a minute, but just turns the gray logo off and on. I'm assuming there is no way out of this, correct?
Click to expand...
Click to collapse
Correct (sorry).
Yeah.. I gambled. Guess I lost this round.
what kind of douchebag company keeps a version of an os on their website that will brick their device without warning ? if i were you i would never buy one of their products and since the same thing happened to me i will do the same :/
Jasonbrody14 said:
what kind of douchebag company keeps a version of an os on their website that will brick their device without warning ? if i were you i would never buy one of their products and since the same thing happened to me i will do the same :/
Click to expand...
Click to collapse
While I appreciate your frustration this is not Amazon's fault. The actions you and others took are not recommended by Amazon nor most other device manufacturers. The 3.2.8 rollback file that you used was silently captured w/o Amazon's permission and was intended for devices that would never received an OTA update. A few clever individuals figured out how to exploit that file to facilitate 4.5.4 -> 4.5.2 rollbacks (also not supported by Amazon). There are warnings everywhere that wifi must be kept off (or the device placed in 'airplane mode') when using this rollback technique. I am very sorry you lost your device but ultimately the risks and responsibility for bad outcomes are borne by the owner.
Davey126 said:
While I appreciate your frustration this is not Amazon's fault. The actions you and others took are not recommended by Amazon nor most other device manufacturers. The 3.2.8 rollback file that you used was silently captured w/o Amazon's permission and was intended for devices that would never received an OTA update. A few clever individuals figured out how to exploit that file to facilitate 4.5.4 -> 4.5.2 rollbacks (also not supported by Amazon). There are warnings everywhere that wifi must be kept off (or the device placed in 'airplane mode') when using this rollback technique. I am very sorry you lost your device but ultimately the risks and responsibility for bad outcomes are borne by the owner.
Click to expand...
Click to collapse
yeah its my fault for installing an old update i admit that but they host several other versions on their website that arnt 3.2.8 that also brick the device. i just wonder why they would even do that at least instead of permanently killing the device it would just soft brick it :/
Jasonbrody14 said:
yeah its my fault for installing an old update i admit that but they host several other versions on their website that arnt 3.2.8 that also brick the device. i just wonder why they would even do that at least instead of permanently killing the device it would just soft brick it :/
Click to expand...
Click to collapse
Amazon updates don't brick unless: 1) the device is rooted (which means you can get around all protections); or 2) something goes wrong with the update (as occasionally happens to all devices regardless of make). The stock updater will reject attempts to rollback or install an incompatible update. My local auto parts store carries lots of engine elixirs that can work wonders if used correctly. Go off-label and one can 'brick' a $4K engine in minutes.
I'm not ragging on you; what's done is done. Hopefully this post will help someone else contemplating rolling back their device. Tinkers beware: the road to the candy store is laced with land mines.
I have found out that the new update will break the current root method.
There currently does not seem to be a way to downgrade if your devices is updated.
If you want to root, do not update.
This is aggravating because I only ever use root for ad blockers nowadays. Oh well.
Maybe with some luck the bootloader will be unlocked.
Luigiman765 said:
I have found out that the new update will break the current root method.
There currently does not seem to be a way to downgrade if your devices is updated.
If you want to root, do not update.
This is aggravating because I only ever use root for ad blockers nowadays. Oh well.
Maybe with some luck the bootloader will be unlocked.
Click to expand...
Click to collapse
I use NetGuard to block adds. I purchased the IP filtering and it works awesome. Load in your favorite host table and let it go. It does keep an active VPN but haven't noticed any drain on it.
Here is the app thread http://forum.xda-developers.com/android/apps-games/app-netguard-root-firewall-t3233012/page332#post68312768 Developer is super awesome with replying to questions and helping.
Yup!
http://forum.xda-developers.com/showpost.php?p=68791345&postcount=9
on a good note (no pun intended) the device almost doesnt even need root. you have Good Lock to adjust Notifications and colors, and a Theme Store as well. As OP said, blocking ads is about all one really needs root for on this device. Sure with xposed you can have a circle battery icon, and a few other neat tricks. But these can all be lived without. I am currently staring at my 2 replacement Note7's I just picked up a few minutes ago. Ive got Software Updates disabled, but cant pull the trigger to start the root process, lol.
Luigiman765 said:
I have found out that the new update will break the current root method.
There currently does not seem to be a way to downgrade if your devices is updated.
If you want to root, do not update.
This is aggravating because I only ever use root for ad blockers nowadays. Oh well.
Maybe with some luck the bootloader will be unlocked.
Click to expand...
Click to collapse
I woke up this morning and saw my Note7 auto-updated overnight!
If I reset my phone to factory settings would I be set back to the original firmware, or will I still be on the "Green Battery" update?
TimeshiftR said:
I woke up this morning and saw my Note7 auto-updated overnight!
If I reset my phone to factory settings would I be set back to the original firmware, or will I still be on the "Green Battery" update?
Click to expand...
Click to collapse
Unfortunately, factor resestting won't affect the software, and you'll still be on the same update. I even tried flashing the original firmware files via Odin but that did not work either.
i concur, i bricked my Note 7 trying to root it after i got my replacement yesterday 9/21.
i got an internal usc email in regards to the phe update which states it will only let you postpone it 4 times before it will automatically install.
unfortunately the dbag in the store activated my phone on the wrong line and for some reason thought a firmware update would correct it smh so i didnteven have a chance to root since he already installed my screen protector as well.
elliwigy said:
i got an internal usc email in regards to the phe update which states it will only let you postpone it 4 times before it will automatically install.
unfortunately the dbag in the store activated my phone on the wrong line and for some reason thought a firmware update would correct it smh so i didnteven have a chance to root since he already installed my screen protector as well.
Click to expand...
Click to collapse
that blows! never trust them guys, i took my note7's in without the sim cards, said they were active in other phones right now. the rep looking to avoid work, gladly let me take my replacements home without even opening the boxes
cordell12 said:
that blows! never trust them guys, i took my note7's in without the sim cards, said they were active in other phones right now. the rep looking to avoid work, gladly let me take my replacements home without even opening the boxes
Click to expand...
Click to collapse
awsome! good thinking-
We can use 'Package Enabler' app available in Playstore and disable the Software updates (which is what i did).
Ready, set, ask me anything!
I have a couple questions..
1. Is there any kind of ETA? I'm as patient as the next guy, but it's always nice to know! No worries if you don't have one though : )
2. Is there any proof of the K10 root working on the V10?
(not really a question but)
3. I know it's a very long time off, but in October of this year I will no longer be with Verizon and I'm willing to test anything around that time.
supermansbrother said:
I have a couple questions..
1. Is there any kind of ETA? I'm as patient as the next guy, but it's always nice to know! No worries if you don't have one though : )
2. Is there any proof of the K10 root working on the V10?
(not really a question but)
3. I know it's a very long time off, but in October of this year I will no longer be with Verizon and I'm willing to test anything around that time.
Click to expand...
Click to collapse
1. Sadly I have no ETA, right now I have an init and a new sepolicy. I'm able to dirtycow the sepolicy but I can't find any way to get the init across without the phone rebooting before it finishes. I need a way to like freeze the init in a way to make it available for transfer. So there's that and the other guy we are working with is gone right now and idk yet when he'll be back and ready.
2. Well, he is helping me out but he had the same issue with the init sadly. So stuck again
3. I have a question for you.. what version of Android are you on currently?
Currently running a V10 from Verizon, Android version is 6.0.
After recent updates (a few months ago) from Verizon, I noticed my call blocking software was no longer working. I had the software set to block any numbers not in my contacts.
I poked around in the phone app settings and the Android settings, all settings allowing me to block callers from mt phone had been removed.
Verizon's "solution" to be able to block up to 5 numbers free for 90 days (then you have to reblock them) simply does not meet my needs. Paying extra for their service to block numbers is just rude to me. I'd go to another carrier first.
Is there any way to get those settings back on my phone so I can block numbers from my phone again?
artcarney said:
Currently running a V10 from Verizon, Android version is 6.0.
After recent updates (a few months ago) from Verizon, I noticed my call blocking software was no longer working. I had the software set to block any numbers not in my contacts.
I poked around in the phone app settings and the Android settings, all settings allowing me to block callers from mt phone had been removed.
Verizon's "solution" to be able to block up to 5 numbers free for 90 days (then you have to reblock them) simply does not meet my needs. Paying extra for their service to block numbers is just rude to me. I'd go to another carrier first.
Is there any way to get those settings back on my phone so I can block numbers from my phone again?
Click to expand...
Click to collapse
All those settings to block calls from verizon are a verizon thing, once it's changed it's changed. Verizon's contract with us says they technically own the phone and we are just borrowing it. So my first guess would be no you can't get that software back. I could look, depends on what you were using. My suggestion though would check out an app on the play store to see what you get. Once we get root you can probably find a good software for it.
Do you expect roms to be available including nougat roms if/when root is achieved?
snapz54 said:
Do you expect roms to be available including nougat roms if/when root is achieved?
Click to expand...
Click to collapse
Maybe I'll start a project for one but it's a big maybe, I'm going to try to also push out the updates to be flashed over twrp.
artcarney said:
Currently running a V10 from Verizon, Android version is 6.0.
After recent updates (a few months ago) from Verizon, I noticed my call blocking software was no longer working. I had the software set to block any numbers not in my contacts.
I poked around in the phone app settings and the Android settings, all settings allowing me to block callers from mt phone had been removed.
Verizon's "solution" to be able to block up to 5 numbers free for 90 days (then you have to reblock them) simply does not meet my needs. Paying extra for their service to block numbers is just rude to me. I'd go to another carrier first.
Is there any way to get those settings back on my phone so I can block numbers from my phone again?
Click to expand...
Click to collapse
Actually, I've been using contacts+ and dialer+ from the play store on my last several phones and I no longer have to back up my contacts , call log, or texts! And, it has call blocking that does have the block everything not in your contacts. It has made rooting and breaking phones hurt a little less and/or be less of a pain in the @$$. I swear I have nothing to do with them, lol. I'm just a guy who likes to fiddle with this stuff who stumbled on this app purely by trial and error. If I can make one complaint, it's different than other dialers/contacts, and I don't think it's the prettiest app, but once you fiddle with it a while, it gets better. I wish I could skin it though, lol. Sorry for rambling, I just stumbled here and had to comment.
Root for LG V10 VS990 with MM
abine45 said:
Ready, set, ask me anything!
Click to expand...
Click to collapse
I was wondering if you could point me in the right direction?
I need to find a reliable, safe, proven way to root a LG V10 VS990 running MM.
Please, please, please help quickly.
Thank you so much!
~CM
cmccrar said:
I was wondering if you could point me in the right direction?
I need to find a reliable, safe, proven way to root a LG V10 VS990 running MM.
Please, please, please help quickly.
Thank you so much!
~CM
Click to expand...
Click to collapse
Sorry, I personally can't help. Be advised if you root an Android device now, Netflix won't work.
See: https://www.engadget.com/2017/05/14/netflix-no-longer-available-for-rooted-android-phones/
Not worried a/b Netflix, thanks though
artcarney said:
Sorry, I personally can't help. Be advised if you root an Android device now, Netflix won't work.
Not worried a/b Netflix, thanks though!
Click to expand...
Click to collapse
need help here. just bought my V10 refurb unit. they said its H900 at&t unit. its on lollipop with root out of the box so i cannot use any banking app. so i try to diry flash latest H900 firmware via LGUP. phone bootup but i cannot use due to force closed app. so i clean reflash it. now it booting as normal. but i cannot setup any fingerprint as it will force closed. so i came out a solution trying to clear cache and data . phone bootup still same. then suddenly its blank. only black screen with backlit on. so pull out the battery, now phone cannot turn on. only qdloader9008. so its hardbrick. try dismantle mainboard and its turn out im getting verizon vs990 mainboard with at&t firmware in it. now had no idea how to fix it. try those SDCARD using h901 system dumb as i cannot find any vs990 system dumb to work with. no luck, cannot enter download [email protected] fastboot mode. any help will be appreciated.
p/s : now im still not sleeping since yesterday trying to figure it out and my head feel like to exploded.
My parents both have the VS990 and recently their Wi-Fi calling has stopped receiving calls- calls can still be made (outgoing) but they go straight to VM incoming. My Verizon s7e on the same plan works just fine, leading me to rule out Network and Verizon. What is left is LG and Android (since I'm on N and they're still on MM). It seems that it occurred after the recent vzm upgrade from 27a to 28a. Nobody on Reddit responded to my thread, Verizon has been 0 help (they told my parents it was a SIM issue, swapped their SIM, "tested them" without putting the phones on airplane mode and sent them on the way telling them it was fixed..... thanks guys). I can't find any documentation or bug reports of this happening to anyone else- but, I'm not sure how many ppl depend on wireless calling like we do (satellite is our only method of telecom out here- no phone lines run, no dsl, no cell service.. we're in the middle of nowhere). I've tried resetting the Advanced Calling features. I've restarted the phones. I haven't done a factory reset.
A) Anything I've missed?
B) I found an img for 27a on here, is LGUP a feasible means still of downgrading/rolling-back?
Nothing going on
So my v10 wont charge, wont turn on, there's no charging notification light or anything. the only thing that gives me hope is that when I plug it into my laptop, my computer detects it because I can hear the sound. I cant get it into any of the modes, download..recovery..ect. any suggestions?
Hey could you please help me figure out something. I have an LG V10 H901 (purchased from China) its supposedly the T-Mobile version but was manufactured in Korea. Its WIFI and bluetooth weren't working so I tried to update its firmware using LGUP. However, after the update it was hardbricked. I have managed to get to the LG logo using H90021w Unbrick Qfil files. Afterwards I tried to flash stock firmware H90130d_00_0611 using lgup. However, I got a message about partition changes and hardbrick once again. I have also tried KDZ files related to F600L, h90021w and many others. Can you please suggest based on my details:
-Correct QFIL files
-Correct Firmware or KDZ
Phone Details:
IMEI:354017070602111
Model:LGH901BK
Suffix:ATMOOP
Buyer:TMO
Software Verison:H90130D_00
OS Version:N
File Name:H90130d_00_0611.kdz
KDZ File size:1975399272
No Luck
abine45 said:
Ready, set, ask me anything!
Click to expand...
Click to collapse
So my Lgv10. Doesn't show that its charging, doesn't turn on, doesn't do anything at all. It does however connect to the computer in the whole qualcomm hs-usb qdloader9008 mode thing. ive been doing the qfil thing because that seems to be the only thing that detects my phone but nothing is working. are there any other options? oh it says its the lgh900. but the motherboard is the vs990. does that make a difference? I have files for both
Been a while since I've touched a LG device but i'll respond to everyone tonight.
Shiah said:
So my v10 wont charge, wont turn on, there's no charging notification light or anything. the only thing that gives me hope is that when I plug it into my laptop, my computer detects it because I can hear the sound. I cant get it into any of the modes, download..recovery..ect. any suggestions?
Click to expand...
Click to collapse
Uh, check in device manager, see if you are in a qualcomm mode
nabilsp said:
Hey could you please help me figure out something. I have an LG V10 H901 (purchased from China) its supposedly the T-Mobile version but was manufactured in Korea. Its WIFI and bluetooth weren't working so I tried to update its firmware using LGUP. However, after the update it was hardbricked. I have managed to get to the LG logo using H90021w Unbrick Qfil files. Afterwards I tried to flash stock firmware H90130d_00_0611 using lgup. However, I got a message about partition changes and hardbrick once again. I have also tried KDZ files related to F600L, h90021w and many others. Can you please suggest based on my details:
-Correct QFIL files
-Correct Firmware or KDZ
Phone Details:
IMEI:354017070602111
Model:LGH901BK
Suffix:ATMOOP
Buyer:TMO
Software Verison:H90130D_00
OS Version:N
File Name:H90130d_00_0611.kdz
KDZ File size:1975399272
Click to expand...
Click to collapse
In device manager what is your phone coming up as?
thetestis said:
My parents both have the VS990 and recently their Wi-Fi calling has stopped receiving calls- calls can still be made (outgoing) but they go straight to VM incoming. My Verizon s7e on the same plan works just fine, leading me to rule out Network and Verizon. What is left is LG and Android (since I'm on N and they're still on MM). It seems that it occurred after the recent vzm upgrade from 27a to 28a. Nobody on Reddit responded to my thread, Verizon has been 0 help (they told my parents it was a SIM issue, swapped their SIM, "tested them" without putting the phones on airplane mode and sent them on the way telling them it was fixed..... thanks guys). I can't find any documentation or bug reports of this happening to anyone else- but, I'm not sure how many ppl depend on wireless calling like we do (satellite is our only method of telecom out here- no phone lines run, no dsl, no cell service.. we're in the middle of nowhere). I've tried resetting the Advanced Calling features. I've restarted the phones. I haven't done a factory reset.
A) Anything I've missed?
B) I found an img for 27a on here, is LGUP a feasible means still of downgrading/rolling-back?
Click to expand...
Click to collapse
I would update to the latest version. and I would factory data reset. I would also say that wifi calling is brutal and something that I wouldn't use all that much personally. any more questions you can ask
"An update with the November security patch arrived for the majority of Pixel 6 and 6 Pro owners at the end of October. Google is now releasing updated builds for both phones, with global and Verizon variants.
Update 11/17: According to Verizon, this mid-cycle update “improves the performance of your device’s fingerprint sensor.” Early anecdotes of the 14.56MB OTA are bearing that out. However, “Check for update” does not currently trigger the download for all users."
Click to expand...
Click to collapse
Pixel 6 Pro – SD1A.210817.037 – all – Factory Image – OTA
Pixel 6 Pro – SD1A.210817.037.A1 – Verizon – Factory Image – OTA
Click to expand...
Click to collapse
Pixel 6 and 6 Pro get out-of-cycle November update to improve the fingerprint sensor [U]
An update with the November security patch arrived for the majority of Pixel 6 and 6 Pro owners at the end of October. Google is now....
9to5google.com
Wow! Just wow. This is the way it should be. Banking, apps, unlocking nearly instantaneous..
How long did this update take to finish for other people? My Pixel 6 is spending forever "Optimizng apps".
Also, my fingerprint sensor seemed quick and responsive to me (coming from a LG G8X). I wonder if this update will change anything.
Ive not received it yet. UK based.
Don't have the tech know how to side load so I'm checking for updates via settings ]] system ]] system update.
utnick said:
How long did this update take to finish for other people? My Pixel 6 is spending forever "Optimizng apps".
Also, my fingerprint sensor seemed quick and responsive to me (coming from a LG G8X). I wonder if this update will change anything.
Click to expand...
Click to collapse
Optimizing apps is like watching paint dry. Put the phone aside and come back in a half hour.
bobby janow said:
Optimizing apps is like watching paint dry. Put the phone aside and come back in a half hour.
Click to expand...
Click to collapse
I let it be and just came back to it to find it was ready for the phone to be restarted. So I don't know when it actually finished, but it was a while. Now to test the fingerprint sensor performance.
Edit:
Performance feels the same or just a fraction of a second longer. Perhaps it also addressed accuracy? Should be noted that I never felt my fingerprint sensor was slow.
phupton said:
Ive not received it yet. UK based.
Don't have the tech know how to side load so I'm checking for updates via settings ]] system ]] system update.
Click to expand...
Click to collapse
I hope you get it soon in the UK. If not, take a look at the instructions given here. One of the most important things is downloading the sdk-platform tools and making sure your phone is recognized. The download is the second of 2 November OTAs. Once you do it you'll see how easy it is. But I do understand being a little trepidatious.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
definitely a tick faster for me. I think this also prevents it from misreading the FP when moving it while holding down. Faster sometimes can also be more accurate.
cheers
Nothing here yet. Pixel is not officially sold in my country but i think that the one i have is initially bought from UK. Hope that it will make fingerprint reader better when i receive it.
Optimizing apps took a really long time.
Way faster unlock within apps. (I use smart unlock so I can't comment on unlocking the phone_
Everytime I try to flash, it just fails on (remote: partition (system) not found)
Tried most things, full reset, adb wont update on sideload.
Although it did fail on bootloader, but it did eventually update the bootloader to the required, but it jsut will not update to the 037 update, its really damn annoying.
Using flash all or sideload, it wont update, bizarre.
If you are rooted already and want to update: @gururoop has an execellent step by step for Pixel6 Pro that can be used on the Pixel6 (assuming flashing proper images etc) https://forum.xda-developers.com/t/...thout-wiping-data-and-retaining-root.4356065/
chaimav said:
Optimizing apps took a really long time.
Way faster unlock within apps. (I use smart unlock so I can't comment on unlocking the phone_
Click to expand...
Click to collapse
I also had on smart unlock but with this update I turned it off. I've yet to get a FP deny with the update. And with the location of the onscreen thumb reader it's even faster than my P5 with the rear sensor where you need to adjust in order to get your finger on it. (that's not what she said either. ;-)
This update has made the phone so much better, imo. I also saw that it corrected some overheating issues so we'll see if it helps battery life too.
Google must have been reading our XDA fingerprint threads!
Just need it to arrive OTA in the UK. Pretty please.
galaxys said:
Google must have been reading our XDA fingerprint threads!
Click to expand...
Click to collapse
I was thinking the exact same thing. And Reddit too. They are uncensored so things got really vicious there. At least there is some semblance of normalcy and decorum here which might have even made it more readable for Google.
mbonus said:
If you are rooted already and want to update: @gururoop has an execellent step by step for Pixel6 Pro that can be used on the Pixel6 (assuming flashing proper images etc) https://forum.xda-developers.com/t/...thout-wiping-data-and-retaining-root.4356065/
Click to expand...
Click to collapse
Was this directed at me?
Shouldn't need root to update stock to 037, it just fails on partition error.
NHNXDA said:
Everytime I try to flash, it just fails on (remote: partition (system) not found)
Tried most things, full reset, adb wont update on sideload.
Although it did fail on bootloader, but it did eventually update the bootloader to the required, but it jsut will not update to the 037 update, its really damn annoying.
Using flash all or sideload, it wont update, bizarre.
Click to expand...
Click to collapse
It seems google have been messing with files via the firmware page as 1 minute it didnt work, flash tool showed raven download for the pixel 6 which is wrong, anyway finally got it done via flash all on many downloads later, god knows how but alas.
NHNXDA said:
Was this directed at me?
Shouldn't need root to update stock to 037, it just fails on partition error.
Click to expand...
Click to collapse
No sorry mate - I was just making a general suggestion for anyone who is already rooted and doesn't want to wipe
No worries, sorted our 6 & pro now, google playing games with me & firmware
Pretty much as the title says. I'm stock and unrooted, but the idea of an update that blows a physical fuse and can't be undone gives me the shakes. So I held off since it came out. We're about a month into deployment of the update, so I'm now considering applying it. Has anything in terms of major bugs/performance problems come out that should factor into my decision? I've read various threads here and not seen much major stuff.
Thoughts and input? Thanks in advance.
One reason for not going to Android 13 would be that It can mess up the wireless charging function . Mine has not worked properly since I updtaed , even after the patch ( which was supposed to fix it ) it still doesnt work .
Thanks. I've never used wireless charging but I appreciate this caveat to the A13 update.
Other than that all seems good , bit annoying for me as I use wireless charging a lot , have one in my car and this was a major factor in me buying a Pixel 6 . Had high hopes when they rolled out a patch pretty quick but nothing seemd to of changed .
Sad to hear it broke.
I'm afraid to accept major updates after the very final update ever for my OnePlus 6T broke several key functionalities I relied on. That led me to the Pixel 6, which I don't love but it is working "fine" and I hope A13 won't nuke me. I will likely update this weekend unless I hear something widespread and impactful to how I use the phone.
accessibility service not possible in non-store apps
miss said:
accessibility service not possible in non-store apps
Click to expand...
Click to collapse
WHAT... That's horrible... ACR won't work ) :
miss said:
accessibility service not possible in non-store apps
Click to expand...
Click to collapse
Just go to app info, click on 3 dot menu to bypass restriction.
I updated and I'm pretty happy. IIRC there's now a "developer" Android 12 build that works on the Android 13 bootloader if it ends up not being for you for any reason. I haven't seen any significant issues, though now I see people mentioning wireless charging I did notice it kept popping up the little "100%" screen every 5 or 6 minutes like I'd just put it on the charger when I was using the one in my car, after it hit full, but not the one in my room that provides a higher wattage. Either way, not a big issue to me.
Just be sure to read the other threads about updating to 13 and sideload the OTA after you update if you want to be certain you won't accidentally brick booting the un-updated partition after updating. It gave me a hassle sideloading from both of my PCs, but if you use USB 2.0 it'll go through, just... reeeeeally... sloooowly - so you could let it go overnight.
Jaitsu said:
I updated and I'm pretty happy. IIRC there's now a "developer" Android 12 build that works on the Android 13 bootloader if it ends up not being for you for any reason. I haven't seen any significant issues, though now I see people mentioning wireless charging I did notice it kept popping up the little "100%" screen every 5 or 6 minutes like I'd just put it on the charger when I was using the one in my car, after it hit full, but not the one in my room that provides a higher wattage. Either way, not a big issue to me.
Just be sure to read the other threads about updating to 13 and sideload the OTA after you update if you want to be certain you won't accidentally brick booting the un-updated partition after updating. It gave me a hassle sideloading from both of my PCs, but if you use USB 2.0 it'll go through, just... reeeeeally... sloooowly - so you could let it go overnight.
Click to expand...
Click to collapse
So, even unrooted and stock I have to fuss with the side load update thing?
Frankenscript said:
So, even unrooted and stock I have to fuss with the side load update thing?
Click to expand...
Click to collapse
You don't have to, it's just eliminating an unlikely risk. It'll work fine after just updating. Even if the update somehow failed you'd be safe as it would just roll back; the risk only lies in if you update, successfully boot, and then something causes Android to fail to boot, which should never happen if you're not rooted and tinkering with things.
Basically:
* Your phone has two "system" slots.
* Either taking an OTA from an automatic system update, or manually sideloading it, updates the slot you're not on, then switches to it.
* When you update to 13 and it successfully boots, a flag is set that permanently prevents booting with an older bootloader. (This is a one-time thing and shouldn't happen again with future updates.)
* At this point, if something caused Android to fail to boot, it might try to boot into the un-updated system slot. Because that flag is set and it still has the old bootloader, it wouldn't boot and would be bricked.
* Sideloading the OTA again (or even getting another automatic update, but that won't happen immediately) ensures this won't happen by updating the other slot.
Personally I'd just do it because I'm paranoid (and moreso because I personally do root and tinker with things I shouldn't all the time ).
Lughnasadh said:
Just go to app info, click on 3 dot menu to bypass restriction.
Click to expand...
Click to collapse
with any apk file, any application?
I use many that are not from any official store, such as motomedialink, which needs to have accessibility permission to work
miss said:
with any apk file, any application?
I use many that are not from any official store, such as motomedialink, which needs to have accessibility permission to work
Click to expand...
Click to collapse
As long as the accessibility permission has been restricted for that app because of the new policy (applies to Notification Access permission as well), it should work.
So far the update to A13 seems to have gone smoothly. I honestly haven't noticed anything different yet.
For what it's worth, one benefit I've noticed so far is that certain applications don't get shut down so aggressively as under A12. Despite all the tweaks I made previously, Angry Birds 2 would get shut down pretty much as soon as I did anything else on the phone, and Sound Profile would shut down randomly. Both of these seem fixed under A13.
Haven't noticed a downside yet in terms of how I use the phone.
I've been on A13 for two weeks now and everything seems to run smoothly, definitely dropped phone temperatures. I don't use wireless charging so can't tell about that. I'm on 13.0.0 (TP1A.220624.021.A1, Aug 2022) rooted. Tried loading 13.0.0 (TP1A.220905.004.A2, Sep 2022) but it won't boot, I'm getting "your device is corrupt it can't be trusted and may not work properly" error, had to revert back to previous one. Shame as I'm struggling with biometrics and this new update was suppose to fix the issue. Might try to flash_all with -w option this weekend to see if it makes any difference, can't be asked to be setting up my phone from scratch after three days of festival