I installed the June '23 update but I don't see the matching factory images I need to extract the boot image in order to root. Anyone seen it anywhere?
I think I may have downloaded a beta by mistake. Is it possible to root a beta version?
June update AFAIK hasn't been released. Rooting beta versions is possible however.
Double check the version/security update level you're on. In my experience, carriers apparently can sneak in their OTAs even if you're on Google's version of the software.
I didn't realize the June was being withheld. I saw June updates on Android Flash Tool and figured second Monday but that doesn't mean much anymore. I hope June is made available as I'm having some issues with no screen response when clicking links using Chrome and Facebook.
Related
I have several Moto Z Plays here; two are retus and one is reteu. The reteu one is running 7.1.1 (official version, not a soak test, NPN26.118-22) because I downloaded the official update and sideloaded it yesterday. It has the July security patch. I was never a soak tester, either. The retuses are still on 7.0, May security patch (NPN25.137-24.4).
Here's the issue. When I sideload NPN26.118-22 (7.1.1. official) on a retus, I get an error saying "E3002: Package expects build thumbprint of 7.1.1/NPN26.118-22/21:user/release-keys or 7.0/NPN25.137-24.3/4:user/release-keys; this device has 7.0/NPN25137-24.4/5:user/release-keys," and it fails. (This also happened on reteu, but I happened to have the package it wanted to see, so I installed it first. See below.)
So, my next move is to replicate what worked on reteu, which was to flash the other package I have first, but I get another error saying "E3002: Package expects build thumbprint of 7.0/NPN25.137-24.3/4:user/release-keys or 7.0/NPNS25.137-24-1-9/10:user/release-keys; this device has 7.0/NPN25.137-24.4/5:user/release-keys."
I'm sort of at a loss from here of what to do, since the May security update for retus does seem to prevent compatibility with flashing any new package. The reason this wasn't an issue on the reteu one was, I'm assuming, because it was on the April security update, and I was able to install the second package, and then finally official 7.1.1 to get it current.
Anyone have any ideas? I can't be the only one running this freaking NPN25.137-24.4 (May) update on the retus Z Play that is preventing me from sideloading official 7.1.1. Thanks in advance!
Let me ask again (not you, in general). Why do you so desperately want 7.1.1? And risk hard bricking flashing images?
Mine Play is also retus and got May security patch last week. I'm not noticing any bugs. 7.1.1 is not bringing something revolutionary. It's still 7.x after all. I'm even thinking to not accept update. Don't fix it if is not broken.
Zeljko1234 said:
Let me ask again (not you, in general). Why do you so desperately want 7.1.1? And risk hard bricking flashing images?
Mine Play is also retus and got May security patch last week. I'm not noticing any bugs. 7.1.1 is not bringing something revolutionary. It's still 7.x after all. I'm even thinking to not accept update. Don't fix it if is not broken.
Click to expand...
Click to collapse
I appreciate your reply, but this isn't really relevant to my question at all. I acknowledge there are risks with flashing, but I did it successfully on one of my devices and it's really not the scariest thing I've ever done on ADB.
If you're content to wait, that's fine; what I want to know is the reason why I can't seem to do it on 2/3 of my devices. I'd appreciate responses that are relevant to my question.
I replied to your post on reddit, but I'll share it here too. Someone may even correct me here on XDA if I've got any info wrong.
The 7.1.1 that was released to most of us (retbr, retca, etc) require the build number NPN25.137-24.3 (May 2017 security patch) to be installed.
The May security patch on retus has the build number of NPN25.137-24.4 (I guess there was a change that warranted the .4 over .3). All retus phones will have this build number if they've installed the May patch.
This is why you were getting errors when trying to sideload 7.1.1 onto the retus phones (trying to install an update not meant for the device). retus will likely get a different install package for Android 7.1.1
How do you sideload using stock recovery? I tried adb devices and my device is not listed. I want to sideload Google stuff to stock ROM, any idea how to do that? Tried to install the APK files manually but I got force closed after that. Thank you.
I've got an AT&T S9 and it's still got the February 1 security patch and says no updates are pending. AT&T's website indicates that the latest security patch they've released is July and that there was also a June update. https://www.att.com/devicehowto/tut...9?make=Samsung&model=SamsungG965U&gsi=uArWqmI
Is it possible the June update got pulled (and not removed from the AT&T website) and that for some reason the July update hasn't been released for my device yet? Can anyone shed some light on this for me? I searched and couldn't find anything regarding this.
Thanks
Idk. I got an unlocked s9 on metro pcs. I didn't get an update since June patch. Used odin updated myself. Give it a try.
I just got the August first update today I'm also on AT&T using an S9 from AT&T
Check it out
tlopez1973 said:
Check it out
Click to expand...
Click to collapse
tlopez1973 said:
I just got the August first update today I'm also on AT&T using an S9 from AT&T
Click to expand...
Click to collapse
Thanks. Did either of you get the June update? I'm still on February and whenever I check no new update is available.
jollywhitefoot said:
Thanks. Did either of you get the June update? I'm still on February and whenever I check no new update is available.
Click to expand...
Click to collapse
Thanks for the replies everyone, but I've got an update downloading now. Here's what I did...
Background and symptoms:
- I was what I believe was the original out of the box firmware (G960USQU1ARB7 - February 2018 security patch)
- When I would check for updates i would immediately get a message that no updates were available (like it wouldn't even check really)
- I tried doing a factory reset which didn't help
Resolution:
- Used FirmwareScience to find and download the next update (G960USQU1ARBI here is the direct link)
- Followed the instructions there to install the update (placed the update.zip file on SDCard, reboot to recovery, select update from zip)
- After the update, I went back into settings to see if the next update would download and it did...it's installing now.
Void Warranty
jollywhitefoot said:
Thanks for the replies everyone, but I've got an update downloading now. Here's what I did...
Background and symptoms:
- I was what I believe was the original out of the box firmware (G960USQU1ARB7 - February 2018 security patch)
- When I would check for updates i would immediately get a message that no updates were available (like it wouldn't even check really)
- I tried doing a factory reset which didn't help
Resolution:
- Used ="https://samsung.firmware.science"]FirmwareScience to find and download the next update (G960USQU1ARBI https://samsung.firmware.science/download?url=52758/1488/SS-G960USQU1ARB7-to-U1ARBI-UP"]here is the direct link)
- Followed the instructions there to install the update (placed the update.zip file on SDCard, reboot to recovery, select update from zip)
- After the update, I went back into settings to see if the next update would download and it did...it's installing now.
Click to expand...
Click to collapse
Will it void warranty?
in download mode there is void warranty: 0x0 will it switch to 0x1? is that case working as OTA update I dont want to slow down my device, thank you
I've been using the lazy method of rooting my 3XL from an arriving OTA.
https://topjohnwu.github.io/Magisk/tutorials.html
It works great, the problem is the OTA arriving. As was well publicized the December one never arrived, but the January one did. However, I never got the February so I'm still on January. I don't know if that was widespread. Finally, its now March 8 and I haven't gotten the March OTA., which is available on the factory image site. If I didn't get February automatically (and I do poll) I have to wonder if I will get March.
Is there a way to get the phone to treat a manually downloaded OTA the same way as one that was auto distributed? I know about the other ways to update and patch, but I like the OTA method.
kmandel said:
I've been using the lazy method of rooting my 3XL from an arriving OTA.
https://topjohnwu.github.io/Magisk/tutorials.html
It works great, the problem is the OTA arriving. As was well publicized the December one never arrived, but the January one did. However, I never got the February so I'm still on January. I don't know if that was widespread. Finally, its now March 8 and I haven't gotten the March OTA., which is available on the factory image site. If I didn't get February automatically (and I do poll) I have to wonder if I will get March.
Is there a way to get the phone to treat a manually downloaded OTA the same way as one that was auto distributed? I know about the other ways to update and patch, but I like the OTA method.
Click to expand...
Click to collapse
Your phone won't apply the OTA with a modified boot image (magisk modifies it).
If you want to get updates you'll need to manually flash the full system image with the -w removed from the bat file. Head over to the guides portion of the forum for instructions.
ffchampmt said:
Your phone won't apply the OTA with a modified boot image (magisk modifies it).
If you want to get updates you'll need to manually flash the full system image with the -w removed from the bat file. Head over to the guides portion of the forum for instructions.
Click to expand...
Click to collapse
If you look at the url at the top of the thread you will see that first you do is "Magisk Manager → Uninstall → Restore Images" before triggering the OTA install.
It does work fine, I've done it twice. The problem is that Google didn't download the OTA in December or February, and so far in March (though its early).
kmandel said:
If you look at the url at the top of the thread you will see that first you do is "Magisk Manager → Uninstall → Restore Images" before triggering the OTA install.
It does work fine, I've done it twice. The problem is that Google didn't download the OTA in December or February, and so far in March (though its early).
Click to expand...
Click to collapse
I did the Jan OTA update with Magisk and it worked great. I got tired of waiting for the Feb and Mar OTA's so I flashed the full Mar image yesterday. There's another thread with others having the same issue of not getting the OTA https://forum.xda-developers.com/pixel-3-xl/help/preparing-update-t4060613
This is happening to a lot of us. If you time it right you will see it say Preparing to update.....if you manually check before it has tried.
The preparing goes away and then it is stuck on you are up to date. Google found a way to pre check for root I think.
I'm rooted and sideload OTA's every 3-4 months. I've done this several times since the phone was released with no issues. Today, was going to be May - August updates. May went through with no problem. However, when I went to install the June OTA, it failed with the following error:
Update package is older than the current build, expected a build newer than timestamp 1586927258 but package has timestamp 1586827774 and downgrade not allowed.
Do you folks have any suggestions? I tried re-downloading, but that didn't work. I checked the SHA-256 Checksum and they're all correct per the Google Developer site. I could move on to the July OTA, but I've never skipped an OTA before and am not sure of the consequences. I'd rather not install factory image and have to set things up again if I can avoid it.
Quick and easy
Fastboot boot the latest TWRP 3.4.0-1 img and flash the August OTA
Skipping June & July OTAs isn't an issue?
Edmontonchef said:
Quick and easy
Fastboot boot the latest TWRP 3.4.0-1 img and flash the August OTA
Click to expand...
Click to collapse
jaybird779 said:
Skipping June & July OTAs isn't an issue?
Click to expand...
Click to collapse
Never had a problem, you could flash and boot those the same way first if it makes you feel better.
Are you sticking to stock or are you running a custom ROM?
This is a known problem with the June update. Notified Google, posted about it on Android Police, problem never fixed. Only way to get the June update was OTA.
Skip June, sideload July or August. Why not just sideload most up to date anyway? Curious. Running August no problem.
A new version of Platform Tools has been released since June.....you may want to download newest Platform Tools and give June another try before loading July or August.
Read Comments: https://www.androidpolice.com/2020/...ogle-pixels-are-here-with-plenty-of-bugfixes/
Hey, I'm on 210817.036 (Nov. 2021) on an unlocked Pixel 6 Pro.
I was finally able to unlock it today from AT&T and wondering if I should update to the latest Android update before rooting.
Thanks for any advice!
I wouldn't bother, because OTAs take longer than flashing full firmware. i.e. As part of the rooting process, I would go ahead and flash the latest full firmware instead.
SDK Platform Tools
Get the Google USB Driver
Official Google Android Flash Tool
Oh OK! I didn't realize I could flash the full image of a higher version directly over an older version as part of this process. Thank you!
Oh and also I didn't know if patches above Nov. 2021 made things worse or not.
DevanteWeary said:
Oh OK! I didn't realize I could flash the full image of a higher version directly over an older version as part of this process. Thank you!
Oh and also I didn't know if patches above Nov. 2021 made things worse or not.
Click to expand...
Click to collapse
You're welcome!
I never had any issues at all, even with the fingerprint reader, from the end of October when I received mine through the second February patch. Hopefully, yours will be the same way.
At worst, once you unlock the bootloader if you have any issues with how things run, you can always flash any firmware you like. Be careful. You can also accidentally flash the wrong firmware. Coincidentally, I accidentally gave you a link to the official flashing site, which is good for staying stock unrooted, but if you're going to be rooted, I actually recommend the Pixel 6 Pro Factory Images. Just only ever use images that have Raven in the name as flashing the wrong thing can make it so that your phone would be unrecoverable.
Forgive me if I'm repeating anything you already know.