I have a verizon model SM-G965U (Snapdragon). A few weeks ago, I was able to follow this upgrade sequence to get Pie:
G965USQU3BRI9 to G965USQU3BRJ5
G965USQU3BRJ5 to G965USQU3ZRJ8
So now I am currently stuck on G965USQU3ZRJ8. I am attempting to upgrade it to the latest Pie release which is G965USQU3CRKD (November 19 2008). However, when I try to update the firmware via download mode / adb sideload update.zip, it fails because it expects the BRJ5 model.
So, my only option it seems to sideload the update is to first downgrade back down to BRJ5. How can I downgrade this firmware, or would it be easier to flash the latest updates via odin another way? I am clueless, please help a disgruntled user stuck in the wrong version of Pie.
cmcjacob said:
I have a verizon model SM-G965U (Snapdragon). A few weeks ago, I was able to follow this upgrade sequence to get Pie:
G965USQU3BRI9 to G965USQU3BRJ5
G965USQU3BRJ5 to G965USQU3ZRJ8
So now I am currently stuck on G965USQU3ZRJ8. I am attempting to upgrade it to the latest Pie release which is G965USQU3CRKD (November 19 2008). However, when I try to update the firmware via download mode / adb sideload update.zip, it fails because it expects the BRJ5 model.
So, my only option it seems to sideload the update is to first downgrade back down to BRJ5. How can I downgrade this firmware, or would it be easier to flash the latest updates via odin another way? I am clueless, please help a disgruntled user stuck in the wrong version of Pie.
Click to expand...
Click to collapse
You may install the required Android Oreo build first, and then update using ADB sideload to Pie.
This may help you - Download Galaxy S9 Pie.
itskapil said:
You may install the required Android Oreo build first, and then update using ADB sideload to Pie.
This may help you - Download Galaxy S9 Pie.
Click to expand...
Click to collapse
That does not help at all. It simply repeats the steps I have already taken. If it were as easy as reversing these steps I would not post this topic. It was easy to upgrade, but downgrading is not as simple.
I already have Pie, I don't want vague upgrade instructions. I specifically want to go back to Oreo.
Use Odin to downgrade to Oreo. It's been covered many times in the beta thread. There should be a link in there for a lower version then you'll need to patch to BRJ5 and then the latest Beta.
https://forum.xda-developers.com/showpost.php?p=77970099&postcount=121
Related
I'm wanting to manually install the April 2016 update to my Nexus 5X (currently running February 2016) but due to being rooted (with SuperSU BETA 2.67) and having TWRP as my recovery. I've looked for ways of doing it and trying to be a cautious as I can (when I tried to root las time, I soft-bricked my phone for a few hours). So far the best way I've found is simply through the Google Developers page (link below) with instructions and all the files I need.
Before I go through with it however, I'm wanting to know whether TWRP will prevent the install, if there's a better method, and do I install the latest image, or the one currently installed on my device, then update? Let me know if you need more details too.
Google page:
developers.google.com/android/nexus/images#instructions
Just follow the directions on Google's page, then redo twrp and root all over again.
zelendel said:
Just follow the directions on Google's page, then redo twrp and root all over again.
Click to expand...
Click to collapse
So just to be clear, manually updating will get rid of TWRP too?
sebowow said:
I'm wanting to manually install the April 2016 update to my Nexus 5X (currently running February 2016) but due to being rooted (with SuperSU BETA 2.67) and having TWRP as my recovery. I've looked for ways of doing it and trying to be a cautious as I can (when I tried to root las time, I soft-bricked my phone for a few hours). So far the best way I've found is simply through the Google Developers page (link below) with instructions and all the files I need.
Before I go through with it however, I'm wanting to know whether TWRP will prevent the install, if there's a better method, and do I install the latest image, or the one currently installed on my device, then update? Let me know if you need more details too.
Google page:
developers.google.com/android/nexus/images#instructions
Click to expand...
Click to collapse
Look at this very good guide. It helped me very much.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Dont be afraid to brick it. As long as you are carefully flashing the bootloader, nothing really bad can happen. It is a Nexus.
Bad news is, March brought a new bootloader. So if you dont want to fool around with the bootloader, I would recommend flashing System, recovery and boot of Febraury and then update via OTA. Have fun
Hello,
I currently have a AT&T factory unlocked G965U build R16NW.G965USQU3ARG7 on T-Mobile and I want to update to Pie. Yesterday I popped an activated AT&T SIM card to update the device to Pie and had no OTA luck. Can I download the latest version PPR1.180610.011.G965USQU3CSAB and install it via ODIN or do I need to do an incremental upgrade. I also tried updated to R16NW.G965USQS3ARG8 via SD card sideload and got an “error 7”, I do not care about the data on the phone. Should I only use ODIN or ADB? Also I can't seem to locate AT&T's version of Pie. If someone can guide me in the right path it would be great-full.
tennyson24 said:
Hello,
I currently have a AT&T factory unlocked G965U build R16NW.G965USQU3ARG7 on T-Mobile and I want to update to Pie. Yesterday I popped an activated AT&T SIM card to update the device to Pie and had no OTA luck. Can I download the latest version PPR1.180610.011.G965USQU3CSAB and install it via ODIN or do I need to do an incremental upgrade. I also tried updated to R16NW.G965USQS3ARG8 via SD card sideload and got an “error 7”, I do not care about the data on the phone. Should I only use ODIN or ADB? Also I can't seem to locate AT&T's version of Pie. If someone can guide me in the right path it would be great-full.
Click to expand...
Click to collapse
What I did for my ATT device, is changed the date to 22 Feb 2019 or a few weeks out, and then ran the OTA checker on the device and then it started downloading to update to pie. Either way, good luck and thread moved here...
I just purchased a used AT&T SM-G965U. My carrier is Google Fi. It's running Android 8.0 and Samsung Experience 9.0. Build number is G965USQU3BRK1. Last security patch was November 1, 2018. When I try to update OTA or with Smart Switch both claim my phone is up to date.
I started looking into how I might manually update the phone and found some instructional pages for updating via ODIN, but was not able to find the correct firmware to update to Pie using that method. I did however find a thread on the XDA forums with a download link for an SM-G965U Pie build. Someone posted in that thread that it is possible to update the phone with a micro SD in recovery mode. Even with that being the case the firmware.science page linked in the thread specifically says that the firmware will update my phone from version G965USQS3BRK2 to version G965USQU3CSAB. This seems like a problem since my phone is running G965USQU3BRK1 which I assume is an older build based on the BRK1 designation. Will this update method even work with my phone? Do I need to update to BRK2 before I use the firmware linked in the thread? If so is the BRK2 firmware available for download anywhere? Or failing that is there an ODIN firmware update available?
Update: I tried updating via micro SD in recovery mode using a firmware update downloaded from firmware.science that is supposed to update my SM-G965U from version G965USQU3BRK1
to version G965USQU3CSA5. The update was aborted due to "unexpected contents". I transcribed the error at the bottom of this post. Not sure what else I can do if I can't find an ODIN firmware. If I used the modifed ODIN to flash my phone with U1 firmware would that enable updates through normal (OTA/Smart Switch) channels?
E3005: "EMMC://dev/block/bootdevice/by-name/modem:83300864:2d921fc2a30290a4f894ef4e5528ab83263913ec:84005376: 12c0577b202561c4a0732793bdbaf3a04eca67f0" has unexpected contents.
E:Error in /sideload/package.zip (Status 7)
Installation Aborted.#1
Update 2: I managed to find the ODIN firmware update files and successfully flashed my phone with a Pie build. Disregard this post.
I'm having the identical problem, only with Verizon SM-G965U. Android 8.0.0, last security update Nov 2018. Can someone guide me to the solution?
Thanks
DIncLover said:
I'm having the identical problem, only with Verizon SM-G965U. Android 8.0.0, last security update Nov 2018. Can someone guide me to the solution?
Thanks
Click to expand...
Click to collapse
What firmware are you currently on?
I've done a bit of research since I first posted this and think I know what's going on. This phone was supposedly new, unlocked. Then I found out SM-G965U is actually locked. It booted up with Verizon logo and worked on Verizon network, so I was ok with that. When I checked the firmware version, it was ....BRK1 (I don't have the phone in front of me), which I looked up to be Sprint firmware! This would explain why it doesn't get updates on Verizon's network, wouldn't it? How this came to be, I don't know, but I think I can proceed by getting a later Oreo or maybe Pie version for VZW and flashing it with Odin.
Comments, if any, are welcome.
If memory serves correctly if your firmware is a certain amount of revisions behind what is currently released then the OTA update and samsung switch will say your firmware is up to date. Even though it obviously is not up to date, it has something to do with how far behind in updates the phone is.
In which case you should be able to update your phone using the patched ODIN and the firmware files found on sammobile or via samfirm app. Thee files from sammobile or samfirm are not ones you can flash via SD card in the recovery menu, the OTA files and what are offered on sammobile or samfirm app (and from here unless otherwise specified) are two different things.
I would note that you might have to factory data reset your phone after flashing the new firmware. It's one possible result of flashing a newer firmware to a phone that has an older firmware like that installed.
Hi,
I have a Mate 10 ALP-L29 8.0.0.132 (C636), unlocked bootloader, rooted with magisk. I would like to update the phone to Android 9.
After reading lots of posts, I think following procedure may give what I want.
0. downloading current stock firmware from here:
https://pro-teammt.ru/en/online-firmware-database/?firmware_model=alp-l29c636b132&firmware_page=0
1. downloading Android 9 official stock firmware from here:
https://pro-teammt.ru/en/online-fir..._model=ALP-L29C636E2R1P12B159&firmware_page=0
2. flashing back stock RAMDISK.img and RECOVERY_RAMDIS.img from stock 8.0.0.132 firmware
https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733
3. Simply waiting for OTA or Using SD card method to update Mate 10 to Android 9.
see: https://huaweiadvices.com/flash-stock-firmware-huawei-honor-phones/
I would appreciate it if someone answer/confirm my following questions:
Will the procedure work?
Is step 2 really necessary?
Will my user data be erased? I don't really mind if I have to re-install my apps.
root will be lost after updating. Is it right?
Thanks.
zagzzig said:
Hi,
I have a Mate 10 ALP-L29 8.0.0.132 (C636), unlocked bootloader, rooted with magisk. I would like to update the phone to Android 9.
After reading lots of posts, I think following procedure may give what I want.
0. downloading current stock firmware from here:
https://pro-teammt.ru/en/online-firmware-database/?firmware_model=alp-l29c636b132&firmware_page=0
1. downloading Android 9 official stock firmware from here:
https://pro-teammt.ru/en/online-fir..._model=ALP-L29C636E2R1P12B159&firmware_page=0
2. flashing back stock RAMDISK.img and RECOVERY_RAMDIS.img from stock 8.0.0.132 firmware
https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733
3. Simply waiting for OTA or Using SD card method to update Mate 10 to Android 9.
see: https://huaweiadvices.com/flash-stock-firmware-huawei-honor-phones/
I would appreciate it if someone answer/confirm my following questions:
Will the procedure work?
Is step 2 really necessary?
Will my user data be erased? I don't really mind if I have to re-install my apps.
root will be lost after updating. Is it right?
Thanks.
Click to expand...
Click to collapse
With EMUI 8 i think that flashing the stock ramdisk would be enough, but it won't hurt flashing the recovery_ramdisk too (in case you have twrp installed).
After that you should receive several OTAs, i don't think it will update directly to EMUI 9.
In case you don't receive any OTA, try with Hisuite on PC.
P. S. Installing the official OTAs is the safest way.
Pretoriano80 said:
With EMUI 8 i think that flashing the stock ramdisk would be enough, but it won't hurt flashing the recovery_ramdisk too (in case you have twrp installed).
After that you should receive several OTAs, i don't think it will update directly to EMUI 9.
In case you don't receive any OTA, try with Hisuite on PC.
P. S. Installing the official OTAs is the safest way.
Click to expand...
Click to collapse
Hi Pretoriano80,
Thanks for your reply. cheers.
Pretoriano80 said:
With EMUI 8 i think that flashing the stock ramdisk would be enough, but it won't hurt flashing the recovery_ramdisk too (in case you have twrp installed).
After that you should receive several OTAs, i don't think it will update directly to EMUI 9.
In case you don't receive any OTA, try with Hisuite on PC.
P. S. Installing the official OTAs is the safest way.
Click to expand...
Click to collapse
Just to update my progress so far.
above procedure worked
all my date remain unchanged.
I lost my root.
however, I got EMUI 9 though OTA!. I kept getting OTA updates after flashed back stock RAMDISK.img and RECOVERY_RAMDIS.img. Here is the list of OTA update I have got.
OTA 8.0.0.143 1.08G, Google Security path Aug, Sept, Oct.
OTA 9.0.0.159 3.88G, ALP-L29 9.0.0.159(C636E2R1P12).
OTA 9.0.0.159(C636E2R1P12patch01), a small 3.8M update on NFC
OTA 9.1.0.300(C636E2R1P12), 3.83G EROFS and GPU turbo 3.0; Security path July 2019
OTA 9.1.0.321(C636E5R1P13), 4.01G Security path Oct 2019
PS. I am in Australia.
I heard the good news that EMUI 10 has been rolled out :fingers-crossed:. Let's just wait...
OK so, I don't even know where to start. I got this phone in November and I did the unlocking and rooting following https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509 that guide. Since then I wasn't able to install any of the OTA updates.
Yesterday I updated to March Security Update using the latest global version I found on this https://forum.xda-developers.com/mi-a3/how-to/rom-xiaomi-mi-a3-laurelsprout-t3962489 thread and while I had lots of issues I though I did it right? Now the WI-FI isn't working (doesn't turn on) and I don't know what to do. PLEASE HELP ME
Reflash whole rom, if you're using patched boot image with Magisk, make sure that it's the very same version as your ROM. The best way is to patch boot.img yourself, don't use ready made images.