Related
I bought this nexus one used from someone on craigslist. It came with android 2.2. on it. frf 50 build and 4.04 radio. The video camera doe not work and I've researched and learned its due to the out dated radio. I received the ota frf91 update today but it didn't work. I have no idea how to fast-boot, update or upgrade my nexus one. i just want my video camera working and the lasted frf build, can someone please advise?
Is you bootloader unlocked?
Sent from my Nexus One using XDA App
yes my bootloader is unlocked
anyone? i have no clue how and all the how to's i come across are a bit confusing
Do a full wipe and install a full rooted FRF91 build. You can Google instructions. Having the bootloader unlocked is part way there. You probably just need to install the SDK on your PC, flash AmonRA and get busy.
Sent from my Nexus One using XDA App
Still haven't received it but it looks like a junk update.
NRD90M.G935VVRU4BQC5
This software update provides the latest enhancements for Enterprise customers.
One Talk℠ from Verizon:
The Galaxy S7 edge now supports One Talk, connecting your office and mobile devices with one number.
App update:
Amazon Shopping (version 8.1.1)
https://www.verizonwireless.com/support/samsung-galaxy-s7-edge-update/
Edit: I received it and it updated Android security patch level to April
Are you sure that the OTA Firmware isn't actually a 7.0+ Nougat Build? The QC builds that I've seen so far have all been at least base 7.0 Nougat.
I don't have a S7 vzw. Yet. Probably within a few days.
Sent from my Galaxy Note5 using XDA Labs
I got this pushed to me too, updating now.
I just checked system updates. There is a new one for me, it include Verizon One Talk and some security updates. Don't k ow if it's QC5. I'm downloading now.
Sent from my SM-G935V using Tapatalk
Does anyone know where to find a odin-flashable version of this?
ArcticSpyder said:
Does anyone know where to find a odin-flashable version of this?
Click to expand...
Click to collapse
There isn't one yet.
Delgoth said:
Are you sure that the OTA Firmware isn't actually a 7.0+ Nougat Build? The QC builds that I've seen so far have all been at least base 7.0 Nougat.
I don't have a S7 vzw. Yet. Probably within a few days.
Click to expand...
Click to collapse
It is based on 7.0 and only added Verizon One Talk and updated Amazon Shopping app and android security patch to April.
Is it me or is the speaker louder?
gunnyman said:
Is it me or is the speaker louder?
Click to expand...
Click to collapse
I hope its not just you haha
Update downloaded, install failed. Guessing because I'm rooted.. anyone else??
They just now only included One Talk? That's been on the S6 and S5 for a long time now.
drt054 said:
Update downloaded, install failed. Guessing because I'm rooted.. anyone else??
Click to expand...
Click to collapse
Yep. You can return to stock and keep some directory changes you made by using their desktop Verizon Software Recovery utility for Samsung. You'd lose root but the phone will get and install OTA updates.
Sent from my SM-G935V using Tapatalk
Installed and used it for a couple of days. Found, that security changes made all calendar notifications on locked screen to be hidden - "some hidden event" & "some hidden time"
I know we will lose root if we take this update but is the update still rootable? I'm rooted on QA4 still and refused to take this update yet as I just received the notification today(Tuesday 5/2/17). I like being rooted with dual speaker mod,and V4A installed. Can anybody confirm if this version is rootable using the Nougat root method? How can I disable the uodates?
Sent from my SM-G935V using XDA-Developers Legacy app
DMon04 said:
I know we will lose root if we take this update but is the update still rootable? I'm rooted on QA4 still and refused to take this update yet as I just received the notification today(Tuesday 5/2/17). I like being rooted with dual speaker mod,and V4A installed. Can anybody confirm if this version is rootable using the Nougat root method? How can I disable the uodates?
Sent from my SM-G935V using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm wondering the same.. Anyone try it yet?
Sent from my SM-G935V using Tapatalk
Any updates on rootability on this FW update? I still haven't taken it and it's been on my screen for a week lmao
Sent from my SM-G935V using XDA-Developers Legacy app
DMon04 said:
Any updates on rootability on this FW update? I still haven't taken it and it's been on my screen for a week lmao
Click to expand...
Click to collapse
If you go to @jrkruse "root for nougat" thread and follow his guide, you'll be able to root the qc5firmware.
https://forum.xda-developers.com/verizon-s7-edge/how-to/root-method-nougat-t3566978/post71275316
I am already on BQC5 and just this morning I got a new system software update downloaded, ready to install message. Odd thing is in the past, prior to BQC5 the notification showed the build number, date and what was changing. Now it doesn't show me anything. It just says there is an update do you want to install now or later.....
Anyone have info on this "unknown" system update?
Looks like this
Software Update G930VVRS4BQC9 for Samsung Galaxy S7 and G935VVRS4BQC9 Galaxy S7 Edge
Android May security update.
Device Stability improvements, bug fixes.
Further improvements to performance.
http://sihmar.com/software-update-g930vvrs4bqc9-galaxy-s7-edge/
Should say further improvements to guaranteeing random lag.
I just received a notification in my status bar for an update. The thing is, I've already applied the January update earlier this month. Anybody else getting this? Just curious why my phone thinks it needs to update...? I'm bootloader unlocked, twrp installed, Magisk 15.3 rooted and have the latest Flash kernel installed.
Yup. I just got the same thing. Any idea what it is?
JAYNO20 said:
Yup. I just got the same thing. Any idea what it is?
Click to expand...
Click to collapse
Nope. Hopefully someone smarter than me can chime in lol
jascolli said:
Nope. Hopefully someone smarter than me can chime in lol
Click to expand...
Click to collapse
Did you buy yours from Verizon?
I've got the notification too. Verizon model. Maybe this is the bootloader unlock fix!
JRJ442 said:
Did you buy yours from Verizon?
Click to expand...
Click to collapse
No from the Google store.
jascolli said:
No from the Google store.
Click to expand...
Click to collapse
I bought mine from Verizon and got it today too. I flashed stock back to take the OTA but it failed a few times. I was thinking it was a patched bootloader since they didn't do that with the January update. But apparently not if yours is from Google. There were some random lockscreen touch issues reported. It could possibly be a fix for that.
Sure hope it's not to lock the bootloader. My Verizon pixel 2 comes tomorrow and I want to unlock and root. I doubt it's preloaded already. Can anyone confirm you can unlock the bootloader with the new update?
I don't think it has anything to do with Verizon. I'm on T-mobile and got the 2nd update today as well.
rukawa2k said:
I don't think it has anything to do with Verizon. I'm on T-mobile and got the 2nd update today as well.
Click to expand...
Click to collapse
Verizon doesn't push the updates. It is linked to your IMEI and pushed by Google.
Just got notified myself... Google phone on Verizon
Got it installed, new build number OPM2.171019.016. Maybe a bug fix release. I'm at work or I'd check it out more. It installed just fine though on non-Verizon Pixel 2.
just got the notification and thought I was going crazy since I just sideloaded jan 5th update yestreday
My wife's phone got it, however mine has not. Both are Google play store phone, on Verizon.
i don't see anything on google's website for sideloads.
It's probably for Spectre/meltdown patches/fixes.
Sent from my walleye using XDA Labs
dobbs3x said:
It's probably for Spectre/meltdown patches/fixes.
Click to expand...
Click to collapse
I thought that initially as well. Went out and seen those issues were addressed already...at least according to BigRed
https://www.verizonwireless.com/support/google-pixel-update/
https://www.verizonwireless.com/support/google-pixel-2-update/
mikeprius said:
i don't see anything on google's website for sideloads.
Click to expand...
Click to collapse
I know. I've been keeping an eye out too.
b00ster23 said:
I thought that initially as well. Went out and seen those issues were addressed already...at least according to BigRed
https://www.verizonwireless.com/support/google-pixel-update/
https://www.verizonwireless.com/support/google-pixel-2-update/
Click to expand...
Click to collapse
Ya but these could be fixes to the last one. They rushed it out so probably some fixes.
Sent from my walleye using XDA Labs
FYI.....
https://9to5google.com/2018/01/18/google-pixel-2-receiving-new-out-of-cycle-android-8-1-ota-update/
I was trying to downgrade my Pixel back to Oreo because of mostly app incompatibility (I should've taken that into account before I upgraded it, my bad) but everytime I tried to flash back to Oreo, I'm unable to do it because of the locked bootloader, I've been using recovery mode and adb sideload to try it, but I had a feeling it wouldn't work, can anyone recommend me any solutions to downgrade?
Edit: Well, I realized after looking for some answers on reddit, that I'm basically screwed for a while until DP2 comes out, so I'm still just hoping I can downgrade it but I might as well start accepting my fate.
+1. App compatibility in P makes my phone almost unusable, which is 100% my fault. Take note Verizon users. The changes in P aren't worth half your apps, including Google apps, not working.
Sent from my Pixel using Tapatalk
I've had no problems. Only one app hasn't worked so far.
tember1214 said:
I've had no problems. Only one app hasn't worked so far.
Click to expand...
Click to collapse
Gmail? Google?
Sent from my Pixel using Tapatalk
Jazznax said:
Gmail? Google?
Click to expand...
Click to collapse
They both work. Try a factory reset
Jazznax said:
Gmail? Google?
Click to expand...
Click to collapse
Sounds like your gapps broke, factory reset
It did take me a factory reset to fix my problems, but data for games and such are gone as a result. The apps that wouldn't work for me are apps like Amazon Prime Video, Youtube, and xda feeds.
So is it worth upgrading my Verizon XL to P or should I stay on Oreo? If so, is there a thread describing how to do this?
rdegamer said:
So is it worth upgrading my Verizon XL to P or should I stay on Oreo? If so, is there a thread describing how to do this?
Click to expand...
Click to collapse
If your bootloader isn't unlocked stay on oreo. Android P is still in beta and there are potential problems to occur and if your bootloader isn't unlocked you will be stuck in the beta from what I've heard
Hello,
have received the pixel 6a today. Wanted to install Android 13 beta, but that does not work. Is not supported. The pixel 4a and 5a is. I do not understand this. Is this coming in the next few days, does anyone know anything?
Greetings Mike
Have a bit of patience. You'll get the non-beta android 13 when its ready.
Pixel 6a gets day one update, global/unlocked build now available [U]
With the Pixel 6a officially hitting store shelves today, Google is releasing a day one update, while Android 13 Beta support...
9to5google.com
Hell, there are not even images available for the Pixel 6a unless you are on Verizon or in Japan. Absolutely ridiculous on Google's part.
It's coming later this week they confirmed
I'd love to see A13 for the P6a tomorrow. Then regular release date for the rest. We desperately need some immediate fixes tomorrow so why not give us the whole shebang?
A quick google says...they are working on it.
Pixel 6a gets day one update, global/unlocked build now available [U]
With the Pixel 6a officially hitting store shelves today, Google is releasing a day one update, while Android 13 Beta support...
9to5google.com
bobby janow said:
I'd love to see A13 for the P6a tomorrow. Then regular release date for the rest. We desperately need some immediate fixes tomorrow so why not give us the whole shebang?
Click to expand...
Click to collapse
Google claims they released fixes last week but AFAIK nobody that has a 6A that is not a Verizon or Japanese variant has received the allegedly released update. It's also not posted on Google's list of factory images. I hope but am not particularly confident that Google will make things right later today.
Beta enrollment is now live
bartolo5 said:
Beta enrollment is now live
Click to expand...
Click to collapse
I enroll and when I look for an update it shows nothing. Is anyone else experiencing this?
Geo411m said:
I enroll and when I look for an update it shows nothing. Is anyone else experiencing this?
Click to expand...
Click to collapse
Yes, I also successfully enrolled in the beta but no update showing.
Edit: Just took a few minutes after updating to June ASB. Its showing now and updating as I type.
I unlocked the bootloader and clean flashed the June AT&T/T-Mobile image. I then signed up for the 13 beta and installed. Did a wipe after installation. Fingerprint scanner is not working at all.
greatgoogly said:
I unlocked the bootloader and clean flashed the June AT&T/T-Mobile image. I then signed up for the 13 beta and installed. Did a wipe after installation. Fingerprint scanner is not working at all.
Click to expand...
Click to collapse
I thought the same. Turned out I had to push my finger down harder to register the print.
bobby janow said:
I'd love to see A13 for the P6a tomorrow. Then regular release date for the rest. We desperately need some immediate fixes tomorrow so why not give us the whole shebang
Click to expand...
Click to collapse
The beta is live
greatgoogly said:
I unlocked the bootloader and clean flashed the June AT&T/T-Mobile image. I then signed up for the 13 beta and installed. Did a wipe after installation. Fingerprint scanner is not working at all.
Click to expand...
Click to collapse
How did you unlock? Mine is grey'd out and I have the unlocked variant not VZW
seangeezy12 said:
How did you unlock? Mine is grey'd out and I have the unlocked variant not VZW
Click to expand...
Click to collapse
You have to factory reset after installing either A13 Beta or A12 June update. After setting up again you should be able to unlock.
ctfrommn said:
You have to factory reset after installing either A13 Beta or A12 June update. After setting up again you should be able to unlock.
Click to expand...
Click to collapse
Damn so I'm on beta now. I have to do a full factory reset!?!? Then I'll be able to do it.
Unfortunately, yes. As another mentioned earlier unlocking wipes everything anyway.