Related
Below are a list of all known Nexus 5 OTA updates. Each time there is a new OTA update, the links will be posted here as they become available. If you get an OTA notification that we don't have a link for, please pull the filename out of logcat for us before applying the OTA and post it here. Once you post it, I'll update this post and mirror the file on my website, http://randomphantasmagoria.com, in case Google pulls it down in the future.
OTA Updates - hammerhead
Current firmware: Android Android 6.0, Build MRA58N
MRA58N from MRA58K - https://android.googleapis.com/pack...74e.signed-hammerhead-MRA58N-from-MRA58K1.zip
------------------------------------------------
MRA58K from LMY48M - https://android.googleapis.com/pack...402b.signed-hammerhead-MRA58K-from-LMY48M.zip
------------------------------------------------
LMY48M from LMY48I - https://android.googleapis.com/pack...ed-hammerhead-LMY48M-from-LMY48I.79fa6114.zip
------------------------------------------------
LMY48I from LMY48B - https://android.googleapis.com/pack...ed-hammerhead-LMY48I-from-LMY48B.1207c77d.zip
------------------------------------------------
LMY48B from LMY47D - https://android.googleapis.com/pack...rhead-LMY48B-from-LMY47D-restricted-radio.zip
LMY48B from LMY47D - https://android.googleapis.com/pack...d-hammerhead-LMY48B-from-LMY47D-fullradio.zip (Use this if the one above won't flash)
LMY48B from LMY47I - https://android.googleapis.com/pack...rhead-LMY48B-from-LMY47I-restricted-radio.zip
-------------------------------------------------
LMY47I from LRX21O - http://android.clients.google.com/p...d-ota-LMY47I-from-LRX21O-radio-restricted.zip
LMY47I from LRX21O - http://android.clients.google.com/p...mmerhead-ota-LMY47I-from-LRX21O-fullradio.zip (Use this if the one above won't flash)
LMY47I from LRX22C - http://android.clients.google.com/p...d-ota-LMY47I-from-LRX22C-radio-restricted.zip
LMY47I from LRX22C - http://android.clients.google.com/p...mmerhead-ota-LMY47I-from-LRX22C-fullradio.zip (Use this if the one above won't flash)
-------------------------------------------------
LMY47D from LRX21O - http://android.clients.google.com/p...d-ota-LMY47D-from-LRX21O-radio-restricted.zip
LMY47D from LRX22C - http://android.clients.google.com/p...d-ota-LMY47D-from-LRX22C-radio-restricted.zip
-------------------------------------------------
LRX22C from KTU84P - http://android.clients.google.com/p...ed-hammerhead-LRX22C-from-KTU84P.6dadaf47.zip
LRX22C from KTU84Q - http://android.clients.google.com/p...ed-hammerhead-LRX22C-from-KTU84Q.a7e2eebf.zip
LRX22C from LRX21O - http://android.clients.google.com/p...ed-hammerhead-LRX22C-from-LRX21O.785a2f7a.zip (Original, may not flash for most people)
LRX22C from LRX21O - http://android.clients.google.com/p...rhead-LRX22C-from-LRX21O.radio-restricted.zip (Attempt to fix #1, may or may not flash.)
LRX22C from LRX21O - http://android.clients.google.com/p...d-hammerhead-LRX22C-from-LRX21O-fullradio.zip (This should flash for everyone)
-------------------------------------------------
LRX21O from KTU84P - http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip
LRX21O from KTU84Q - http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84Q.67fdc56d.zip
-------------------------------------------------
KTU84Q from KOT49H - http://android.clients.google.com/p...ed-hammerhead-KTU84Q-from-KOT49H.9cad7d26.zip
KTU84Q from KTU84M - http://android.clients.google.com/p...ed-hammerhead-KTU84Q-from-KTU84M.21e068a8.zip
KTU84Q from KTU84P - http://android.clients.google.com/p...ed-hammerhead-KTU84Q-from-KTU84P.a32b2f45.zip
-------------------------------------------------
KTU84P from KTU84M - http://android.clients.google.com/p...ed-hammerhead-KTU84P-from-KTU84M.c08cce45.zip
-------------------------------------------------
KTU84M from KOT49H - http://android.clients.google.com/p...ed-hammerhead-KTU84M-from-KOT49H.d173d546.zip
-----------------------------------------------
KOT49H from KFS78N - http://android.clients.google.com/p...ed-hammerhead-KOT49H-from-KFS78N.2a79b8f6.zip
KOT49H from KQS81M - http://android.clients.google.com/p...ed-hammerhead-KOT49H-from-KQS81M.f3dc7925.zip
KOT49H from KRT16M - http://android.clients.google.com/p...ed-hammerhead-KOT49H-from-KRT16M.b3d1f307.zip
KOT49H from KOT49E - http://android.clients.google.com/p...ed-hammerhead-KOT49H-from-KOT49E.537367d5.zip
----------------------------------------------
KOT49E from KFS78N - http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KFS78N.777bedc5.zip
KOT49E from KQS81M - http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KQS81M.79448efe.zip
KOT49E from KRT16M - http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
----------------------------------------------
KRT16M from KFS78N - http://android.clients.google.com/p...ed-hammerhead-KRT16M-from-KFS78N.c6defefd.zip
KRT16M from KQS81M - http://android.clients.google.com/p...ed-hammerhead-KRT16M-from-KQS81M.ea9d0ad5.zip
SPECIAL THANKS
Nevvty
fevan
El Daddy
TheManii
switch85
xdatastic
GabrielGPP
emuneee
kvidli
EthanFirst
HackerWolf
mazsuper
msinkovich
zero_x3
oldblue910 said:
As with so many Nexus devices in the past, I'm going to be tracking OTA update URLs for the Nexus 5 both in this thread and on randomphantasmagoria.com. The first post will be updated with each OTA and if you get an OTA update on your Nexus 5 that I don't have listed here, please get the URL and post it here for the community!
VERY IMPORTANT
When the Nexus 5 launches, it will most likely have an immediate OTA update available the first time you turn it on. Please DO NOT accept this OTA update without getting some information for me first! Too often, people get excited when they turn on their device for the first time and see an update. They accept the update and before we know it, we end up losing all data on the firmware that the device ships with.
When you get your Nexus 5 and turn it on for the first time, please gather the following info before applying that out-of-the-box OTA update:
1. The values of ro.build.fingerprint and ro.build.date.utc from /system/build.prop.
2. The baseband version (can be found in Settings | About Phone)
3. The bootloader version (can be found by booting into fastboot mode, the bootloader version will be displayed on screen).
4. The filename for the out-of-the-box OTA ZIP file (if any). This file can be found in /cache or you can check logcat for the full URL. Either one works.
If you need help with any of this, I'll be more than happy to assist! After we have this information locked down, feel free to apply the OTA update out of the box and enjoy your new device!!
Click to expand...
Click to collapse
Thank you, added you to the index.
subscribing. nice to see oldblue here as well
oldblue910 said:
As with so many Nexus devices in the past, I'm going to be tracking OTA update URLs for the Nexus 5 both in this thread and on randomphantasmagoria.com. The first post will be updated with each OTA and if you get an OTA update on your Nexus 5 that I don't have listed here, please get the URL and post it here for the community!
VERY IMPORTANT
When the Nexus 5 launches, it will most likely have an immediate OTA update available the first time you turn it on. Please DO NOT accept this OTA update without getting some information for me first! Too often, people get excited when they turn on their device for the first time and see an update. They accept the update and before we know it, we end up losing all data on the firmware that the device ships with.
When you get your Nexus 5 and turn it on for the first time, please gather the following info before applying that out-of-the-box OTA update:
1. The values of ro.build.fingerprint and ro.build.date.utc from /system/build.prop.
2. The baseband version (can be found in Settings | About Phone)
3. The bootloader version (can be found by booting into fastboot mode, the bootloader version will be displayed on screen).
4. The filename for the out-of-the-box OTA ZIP file (if any). This file can be found in /cache or you can check logcat for the full URL. Either one works.
If you need help with any of this, I'll be more than happy to assist! After we have this information locked down, feel free to apply the OTA update out of the box and enjoy your new device!!
Click to expand...
Click to collapse
Any reason your not just requesting a system dump of the out of the box firmware?
Sent from my XT1080 using XDA Premium 4 mobile app
TheWhiteChallenger said:
Any reason your not just requesting a system dump of the out of the box firmware?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Good question. Basically it comes down to the fact that system dumps aren't official and you can never be guaranteed that what you're getting is pure and unmodified. Because of that, they're pretty much useless for me.
For a shipping firmware that just gets updated upon first boot, I just want the info. It's much faster for someone to just type out the info I need rather than dumping the system, zipping it, uploading it, downloading it and hitting a hex editor to get the bootloader and baseband versions from the dumps.
I'm sure someone will post a system dump, but unless it's an OTA or a set of official fastboot images from Google, I don't really have any use for them.
Sent from my GT-I9505G using Tapatalk
Gotcha
Sent from my XT1080 using XDA Premium 4 mobile app
Alright guys, the Nexus 5 order pages are live. If anyone buys one, PLEASE get the info I need (listed in the first post) before applying the out-of-the-box OTA update. Thank you!!
oldblue910 said:
Alright guys, the Nexus 5 order pages are live. If anyone buys one, PLEASE get the info I need (listed in the first post) before applying the out-of-the-box OTA update. Thank you!!
Click to expand...
Click to collapse
Will do. Just ordered my white 32GB with 2 day shipping. I live in WV and know from the N4 release that they have a facility in Lexington, KY where it will most likely ship from.
*subscribing*
wvcadle said:
Will do. Just ordered my white 32GB with 2 day shipping. I live in WV and know from the N4 release that they have a facility in Lexington, KY where it will most likely ship from.
*subscribing*
Click to expand...
Click to collapse
Thank you very much. Much appreciated. Also, once you get that info, apply the out-of-the-box OTA update and then get the same info for the updated firmware as well, please!
oldblue910 said:
Thank you very much. Much appreciated. Also, once you get that info, apply the out-of-the-box OTA update and then get the same info for the updated firmware as well, please!
Click to expand...
Click to collapse
Will do.
wvcadle said:
Will do.
Click to expand...
Click to collapse
You're the man. Thanks, dude!
https://support.google.com/nexus/answer/3507867?hl=en&ref_topic=3415518 said:
The new Nexus 5 comes with Android 4.4 pre-installed. Note that you will be prompted to install a small update when you set up your device.
Click to expand...
Click to collapse
We can more or less expect that the initial rom wont ever be dumped, as SETTING UP THE DEVICE WILL FORCE AN OTA.
This is what happened for the 2013 N7 and for the GE S4.
If you are willing to try and get the initial ota, you will likely need wireshark/fiddler/<your preferred network sniffer> to get the url.
TheManii said:
We can more or less expect that the initial rom wont ever be dumped, as SETTING UP THE DEVICE WILL FORCE AN OTA.
This is what happened for the 2013 N7 and for the GE S4.
If you are willing to try and get the initial ota, you will likely need wireshark/fiddler/<your preferred network sniffer> to get the url.
Click to expand...
Click to collapse
Unless you are like me, who doesn't boot into Android the first time until after I unlock the bootloader, dump all the partitions and get root...
efrant said:
Unless you are like me, who doesn't boot into Android the first time until after I unlock the bootloader, dump all the partitions and get root...
Click to expand...
Click to collapse
Same here
Sent from my Nexus 10 using Tapatalk 4
efrant said:
Unless you are like me, who doesn't boot into Android the first time until after I unlock the bootloader, dump all the partitions and get root...
Click to expand...
Click to collapse
Well that would require waiting a custom rec to be released first, generally people here are so impatient they'll flash a rom and when they realize it's a dos 4.0 image they'll just come and complain because no factory images are available
---------- Post added at 04:09 PM ---------- Previous post was at 03:36 PM ----------
https://groups.google.com/forum/?fromgroups#!topic/android-building/JVLaFRoJxFk said:
the kitkat release build (KRT16M) for the Nexus 5--which will be tagged with android-4.4_r1
Click to expand...
Click to collapse
Whatever the initial rom is, it will likely OTA to KRT16M
TheManii said:
We can more or less expect that the initial rom wont ever be dumped, as SETTING UP THE DEVICE WILL FORCE AN OTA.
This is what happened for the 2013 N7 and for the GE S4.
If you are willing to try and get the initial ota, you will likely need wireshark/fiddler/<your preferred network sniffer> to get the url.
Click to expand...
Click to collapse
Is it possible to set up the device with no network connection and avoid any initial OTA update?
I'm thinking not, first post states it could be pre-downloaded and in the cache folder...
koriflame said:
Is it possible to set up the device with no network connection and avoid any initial OTA update?
Click to expand...
Click to collapse
Possibly...you can definitely try. :good:
Sent from my Galaxy S4 Google Play Edition using Tapatalk
My N5 will be showing up Monday afternoon. I'll pull the OTA link if it hasn't been posted by then.
El Daddy said:
My N5 will be showing up Monday afternoon. I'll pull the OTA link if it hasn't been posted by then.
Click to expand...
Click to collapse
And all the info on the shipping firmware!! Keep in mind that, like the N7 2013 WiFi, there may be two OTAs out of the box. The first one will be forced during the setup screen. That one will convert the ROM from dev-keys to release-keys, then once that one is in and you set up your device, it'll probably get a normal OTA to KRT16M.
I hope there's a custom recovery available by Monday. Otherwise we may lose that initial devkeys->releasekeys OTA because it's forced.
If there is a custom recovery, make sure you don't boot the system normally the first time. Instead, the first time you turn it on, boot it into fastboot mode (power + volume down). Note the bootloader and baseband versions on screen. At that point, unlock the bootloader, boot the custom recovery (use fastboot boot recovery.img so you don't overwrite the stock recovery), and do a nandroid. Provide that Nandroid backup, please!
Once that's done, stay in the custom recovery and do an adb shell. Dump the radio if you can. I can help you with that if you don't know how.
After that, boot her up normally, accept the forced OTA and after it applies, DO NOT let it boot up again. Once it reboots, hold down volume down as it reboots so it'll go back into fastboot mode. Note if the bootloader version changed. Boot your custom recovery again (use fastboot boot) and this time do an adb pull on the log files in /cache/recovery. The devkeys->release keys OTA filename should be in there. Post that.
After that, boot her up, set her up, and get the OTA link to the KRT16M OTA, and then tell us the new baseband and bootloader versions for KRT16M. Thanks everyone for offering to help. If there is a custom recovery by Monday that'll be awesome. If not, we may lose the devkeys->releasekeys OTA file. :/
Sent from my Galaxy S4 Google Play Edition using Tapatalk
oldblue910 said:
And all the info on the shipping firmware!! Keep in mind that, like the N7 2013 WiFi, there may be two OTAs out of the box. The first one will be forced during the setup screen. That one will convert the ROM from dev-keys to release-keys, then once that one is in and you set up your device, it'll probably get a normal OTA to KRT16M.
I hope there's a custom recovery available by Monday. Otherwise we may lose that initial devkeys->releasekeys OTA because it's forced.
If there is a custom recovery, make sure you don't boot the system normally the first time. Instead, the first time you turn it on, boot it into fastboot mode (power + volume down). Note the bootloader and baseband versions on screen. At that point, unlock the bootloader, boot the custom recovery (use fastboot boot recovery.img so you don't overwrite the stock recovery), and do a nandroid. Provide that Nandroid backup, please!
Once that's done, stay in the custom recovery and do an adb shell. Dump the radio if you can. I can help you with that if you don't know how.
After that, boot her up normally, accept the forced OTA and after it applies, DO NOT let it boot up again. Once it reboots, hold down volume down as it reboots so it'll go back into fastboot mode. Note if the bootloader version changed. Boot your custom recovery again (use fastboot boot) and this time do an adb pull on the log files in /cache/recovery. The devkeys->release keys OTA filename should be in there. Post that.
After that, boot her up, set her up, and get the OTA link to the KRT16M OTA, and then tell us the new baseband and bootloader versions for KRT16M. Thanks everyone for offering to help. If there is a custom recovery by Monday that'll be awesome. If not, we may lose the devkeys->releasekeys OTA file. :/
Sent from my Galaxy S4 Google Play Edition using Tapatalk
Click to expand...
Click to collapse
Hmm, I didn't know about the forced OTA during setup. Does it reboot the device or somehow just switch the keys?
Anyway, I'll do what I can. Hopefully, I can keep my excitement in check and remember to do all these things!
Afternoon all, just wondering if anyone could help on a quick problem - my Nexus 6 keeps prompting me to update but when I do it hangs after the reboot with what I assume is the recovery error message (red exclamation mark). I'm already on build LMY48I on 5.1.1, which I was under the impression was the September 2015 security patch. I'm fully stock, not rooted or any other mods. I am abroad currently, which I wouldn't imagine has any effect?
Could anyone offer any help on this or steer me in the right direction for further information.
Thanks in advance.
Latest build is LMY48M. OTA may fail because of corrupted download.
You may wanna update your signature.
Yeah, OK, thanks, not been around these parts for awhile.
Would you mind letting me know how I would go about getting a fresh download of the update using OTA?
Thank for the reply.
Still booting normally? Bootloader locked?
When you get to error with Android logo with tummy open press Power then VolumeUp this will show more details about the error. Write everything down.
Hi, sorry for for delay in replying. Bootloader is locked, boots normally when not trying to apply this update.
Next time I try to update I'll log the error messages and revert back here, thanks for your help.
gardy09 said:
Hi, sorry for for delay in replying. Bootloader is locked, boots normally when not trying to apply this update.
Next time I try to update I'll log the error messages and revert back here, thanks for your help.
Click to expand...
Click to collapse
If you're overseas you may be getting an incorrect build, not quite sure how that works
Strangely I thought it might have something towards do with being in Spain. I'll factory reset when I get home and see if that works.
Me too
Sorry to bump an old thread but the OP describes the EXACT problem I am having. Repeat system update update notifications. It says its downloaded but it goes to error when apply the update. I first got the notification in Qatar. I am unlocked and rootwd nexus 6 but running stock 5.1.1.
How can I get rid of the incorrect build?
soccerguy243 said:
Sorry to bump an old thread but the OP describes the EXACT problem I am having. Repeat system update update notifications. It says its downloaded but it goes to error when apply the update. I first got the notification in Qatar. I am unlocked and rootwd nexus 6 but running stock 5.1.1.
How can I get rid of the incorrect build?
Click to expand...
Click to collapse
two way.. update to the latest, or long press the update then oresspress the white circle that appears in the right, then press disable notifications. but i thing updating to the is most important.
simms22 said:
two way.. update to the latest, or long press the update then oresspress the white circle that appears in the right, then press disable notifications. but i thing updating to the is most important.
Click to expand...
Click to collapse
When I go to settings, about phone, it shows I àm running 5.1.1 which is the latest version. But ht I still get the notification.
soccerguy243 said:
When I go to settings, about phone, it shows I àm running 5.1.1 which is the latest version. But ht I still get the notification.
Click to expand...
Click to collapse
There have been serveral updates with version number 5.1.1. What you need to check is the build number.
The latest are LMY48M (most people), LYZ28K (T-Mobile) or LVY48F (Project Fi).
---------- Post added at 10:03 ---------- Previous post was at 10:01 ----------
soccerguy243 said:
Sorry to bump an old thread but the OP describes the EXACT problem I am having. Repeat system update update notifications. It says its downloaded but it goes to error when apply the update. I first got the notification in Qatar. I am unlocked and rootwd nexus 6 but running stock 5.1.1.
How can I get rid of the incorrect build?
Click to expand...
Click to collapse
Ah, just re-read your first post. You can't take an OTA-update, since you're rooted. You need to flash a factory image (or relevant parts of one).
Check the stickies for instructions...
Didgeridoohan said:
There have been serveral updates with version number 5.1.1. What you need to check is the build number.
The latest are LMY48M (most people), LYZ28K (T-Mobile) or LVY48F (Project Fi).
---------- Post added at 10:03 ---------- Previous post was at 10:01 ----------
Ah, just re-read your first post. You can't take an OTA-update, since you're rooted. You need to flash a factory image (or relevant parts of one).
Check the stickies for instructions...
Click to expand...
Click to collapse
I have 47Z installed. I'll use nexus root toolkit to get the latest. Thanks SO MUCH!
Evening all and sorry for delayed response. I've called Google today and they were no help whatsoever, the person I spoke to didn't even know the difference between Android versions and build numbers, I had to explain it to her. Is there any way of checking or finding out what build is being pushed to my phone? Also, will I be able to update to 6.0 when it arrives if I haven't sorted this problem ie how to clear this potentially corrupted download? Am I correct in thinking that I need to be on LMY48M and not on LMY48I - thanks in advance.
gardy09 said:
Evening all and sorry for delayed response. I've called Google today and they were no help whatsoever, the person I spoke to didn't even know the difference between Android versions and build numbers, I had to explain it to her. Is there any way of checking or finding out what build is being pushed to my phone? Also, will I be able to update to 6.0 when it arrives if I haven't sorted this problem ie how to clear this potentially corrupted download? Am I correct in thinking that I need to be on LMY48M and not on LMY48I - thanks in advance.
Click to expand...
Click to collapse
Have you ever found out more details about update error? Press Power then Volume Up on error screen.
Will do it now, hang on...
This is the error message I get...
gardy09 said:
This is the error message I get...
Click to expand...
Click to collapse
At this point you have few choices.
File bug report and wait for resolution.
Try Factory Reset. Using PC try fastboot format userdata and format cache.
Unlock bootloader and flash factory image. Might just well go straight to 6.0 MRA58K. You will loose all your private data either way. Backup all your private stuff.
So have downloaded the MRA58K build of 6.0, attempting to sideload via ADB, device seen, reboot bootloader, into recovery, use ./adb sideload 'file.zip' but getting a footer and signature error. Any help would be greatly appreciated.
And how the hell does one update a 5 year old signature on XDA!?
Edit - so just reading around and there are two issues I've noted 1) that I'm going from LMY48I straight to MRA58K and missing out LMY48M or 2) that the factory images can't be sideloaded, they need to use the fastboot scripts. Any ideas what could be causing my errors?
gardy09 said:
So have downloaded the MRA58K build of 6.0, attempting to sideload via ADB, device seen, reboot bootloader, into recovery, use ./adb sideload 'file.zip' but getting a footer and signature error. Any help would be greatly appreciated.
And how the hell does one update a 5 year old signature on XDA!?
Edit - so just reading around and there are two issues I've noted 1) that I'm going from LMY48I straight to MRA58K and missing out LMY48M or 2) that the factory images can't be sideloaded, they need to use the fastboot scripts. Any ideas what could be causing my errors?
Click to expand...
Click to collapse
Here is guide how to flash factory images http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
gardy09 said:
So have downloaded the MRA58K build of 6.0, attempting to sideload via ADB, device seen, reboot bootloader, into recovery, use ./adb sideload 'file.zip' but getting a footer and signature error. Any help would be greatly appreciated.
And how the hell does one update a 5 year old signature on XDA!?
Edit - so just reading around and there are two issues I've noted 1) that I'm going from LMY48I straight to MRA58K and missing out LMY48M or 2) that the factory images can't be sideloaded, they need to use the fastboot scripts. Any ideas what could be causing my errors?
Click to expand...
Click to collapse
You'll have to find the update from ur current version to the new version. You'll probably have to get LMY48M, didn't see one from I
Sent from my Nexus 6 using Tapatalk
Straight to the content, new mirrors appreciated. I will update this thread as soon as a new update comes out.
Links to Odin are from sammobile, and the ADB drivers are on Github. All links are clean and untouched.
Odin 3.11.1
ADB for Windows
===========================
Untouched side loadable update zips downloaded from xdmd.sl.attcompute.com (sideload using ADB):
7.0 branch:
2017 Mar security level Android 7.0 (G920AUCU5EQB8 to G920AUCU6EQC9)
2017 Mar security level Android 7.0 (G920AUCU5DQB3 to G920AUCU6EQC9)
2017 Feb security level Android 7.0 (G920AUCU5EQA8 to G920AUCU5EQB8)
2017 Feb security level Android 7.0 (G920AUCU5DQB3 to G920AUCU5EQB8)
2017 Jan security level Android 7.0 (G920AUCS5DPK5 to G920AUCU5EQA8) | Credit goes to Mohit0144
6.0 branch:
2017 Feb security level Android 6.0.1 (G920AUCS5DPK5 to G920AUCU5DQB3)
2017 Feb secruity level Android 6.0.1 (G920AUCS5DPK3 to G920AUCU5DQB3)
2017 Jan security level Android 6.0.1 (G920AUCS5DPK3 to G920AUCS5DPK5)
2016 Dec security level Android 6.0.1 (G920AUCS5DPK1 to G920AUCS5DPK3)
2016 Nov security level Android 6.0.1 (G920AUCS5DPJ1 to G920AUCS5DPK1)
===========================
Official complete Odin images (flash using Odin):
2016 Oct security level Android 6.0.1 (G920AUCS5DPJ1)
Current update path to most current build:
G920AUCS5DPJ1 (odin flash) -> G920AUCS5DPK1 (sideload) -> G920AUCS5DPK3 (sideload) -> G920AUCS5DPK5 (sideload) -> pre-release G920AUCU5EQA8 (sideload) -> pre-release G920AUCU5EQB8 -> pre-release G920AUCU6EQC9
If you are on a version more recent than DPJ1, you can start from a later sideload update.
Disclaimer: You are responsible for what you do to your phone
How to flash using Odin (will wipe phone):
1. Extract complete firmware
2. Extract Odin software
3. Shutdown phone
4. Press BL, AP, CP, and CSC buttons in-order in Odin and load files, Odin may freeze during this, just wait it out. Don't touch other options
5. Press Volume down, home, and power together to go into download mode
6. Plug in phone to laptop, and press start to flash
How to sideload using ADB (will wipe phone):
1. Install ADB, reboot
2. Using cmd, cd into the folder of the sideload update zip
3. Shutdown phone, press Volume up, home, and power together to go into download mode
4. Select "apply update from adb", use power button to confirm
5. Using the command "adb devices", verify that the phone is detected after plugging in, if it is detected, proceed
6. Type in command "adb sideload SIDELOADZIPNAME"
7. Wait, it takes a bit for the update to work, and the phone may appear frozen during this process.
If confused, see this thread: http://forum.xda-developers.com/att...ating-to-android-6-0-1-g920aucu3cpd6-t3371884
did exactly what u said with the odin and i keep getting a fail...
Billfromnj05 said:
did exactly what u said with the odin and i keep getting a fail...
Click to expand...
Click to collapse
Well, the file is the exact same as that from this thread. And it is working for those people, so not sure why this is happening to you without more details.
Thank you for these updates.
would this fix the reboot issue? clearing cache doesnt help with previous update (oct)
drek_67045 said:
would this fix the reboot issue? clearing cache doesnt help with previous update
(oct)
Click to expand...
Click to collapse
I have absolutely no idea about why your phone is crashing.
Installing an update may fix it, just by virtue of clearing the /data partition and resetting it to stock in the process. But personally I doubt it (unless google fixed a denial of service bug that you were somehow triggering?).
Not really a diagnosis thread, so do you mind creating a new post with USB debugging turned on and logcat output so the community can help?
See here: http://android.wonderhowto.com/how-...ture-logcat-for-detailed-bug-reports-0167774/
drek_67045 said:
would this fix the reboot issue? clearing cache doesnt help with previous update (oct)
Click to expand...
Click to collapse
Not sure as to specifics of your reboot issue, but I had an S6 that started giving me multiple random reboots per day. Luckily I was inside warranty by a couple weeks - it was a hardware issue. Ended up with a new main board, plus a new display since the tech broke the original somehow changing the board.
That's funny. I never got Dec update for my AT&T S6 variant over OTA. I guessing, it's time to sideload it again.
supersmilers said:
That's funny. I never got Dec update for my AT&T S6 variant over OTA. I guessing, it's time to sideload it again.
Click to expand...
Click to collapse
This has not been officially released yet. But it has been sitting on AT&T servers for quite a bit (along with DPK2). The kernel has a build date of Dec 14. My guess is that AT&T is waiting after the holidays to officially release this. It's a fairly small update coming in at 17MB.
Edit: I should note that I am running DPK3 without issue.
sand_bit said:
This has not been officially released yet. But it has been sitting on AT&T servers for quite a bit (along with DPK2). The kernel has a build date of Dec 14. My guess is that AT&T is waiting after the holidays to officially release this. It's a fairly small update coming in at 17MB.
Edit: I should note that I am running DPK3 without issue.
Click to expand...
Click to collapse
Man can you tell me, how do you flash in adb sideload the latest firmwares?, my s6 send me an error
E: Error in /sideload/package.zip
(status 7)
sand_bit said:
This has not been officially released yet. But it has been sitting on AT&T servers for quite a bit (along with DPK2). The kernel has a build date of Dec 14. My guess is that AT&T is waiting after the holidays to officially release this. It's a fairly small update coming in at 17MB.
Edit: I should note that I am running DPK3 without issue.
Click to expand...
Click to collapse
December update has been pushed out OTA. Is PK3.
Sent from my SAMSUNG-SM-G920A using Tapatalk
GilbertoXDA17 said:
Man can you tell me, how do you flash in adb sideload the latest firmwares?, my s6 send me an error
E: Error in /sideload/package.zip
(status 7)
Click to expand...
Click to collapse
Not sure, but probably need to flash this with Odin
worked fine, note of caution.
my att gs6 was on oj9. flashed went through fine initially then an error came up "can't open the serial(com)port" and FAIL in red above the blue part.
however, the phone progress meter kept going and eventually the flash was successful.
My g920a is stuck at g920aucs5dpi1 and on ota it says my software is up to date. I don't know what's happening or is it because I am not using at&t sim? But it's already unlocked.
wiltaf said:
My g920a is stuck at g920aucs5dpi1 and on ota it says my software is up to date. I don't know what's happening or is it because I am not using at&t sim? But it's already unlocked.
Click to expand...
Click to collapse
I would bet that it's because you're not on an AT&T sim. I don't think they feel responsible to update the phone if it's not on their network. Not sure if you can throw someone's sim in there to update it or if you just ODIN flash it to update it.
Edit: You can also try to use Smart Switch to see if it'll pull the update, or try a Samsung Experience at a BestBuy to see if they can push the update.
Thanks. Now my phone is up to date.
This is the only way I can apply updates. For some reason I never get the OTA updates.
Thanks my phone updated to latest.
will my unlocked galaxy s6 become locked if i update using this?
Could someone tell me if the encryption menu items are available on your GS6, and what build you are on?
I encrypted my phone about 2 builds back, and after the December update, upon reboot it no longer asks for my PIN/PW and encryption is no where to be seen in the settings, or at least I (and search) can't find it. I don't want to factory reset to see if it reappears...yet.
If AT$T removed encryption from the device in the next update, I'm going to be real pissed.
Also, I think (at the moment) my battery life is worse on the latest build, but I have been using my phone a little more lately. But last night I went from 100% at 7:05pm to 5% at 11:30pm. 4.5 hours is not way to quick for a battery to die. Wakelock Detector (no root) didn't give much info, and the system menu for battery gave 3 of the top 4 to Android OS, Google Play services, Android System.
TIA
Is this for phones already with root access?
Hey guys,
I'm on a stock Samsung Galaxy S6, SM-G920A, Android Version 6.0.1, Security Patch Level December 1, 2016, Build Number: MMB29K.G920AUCS5DPK3. I have an AT&T Go-Phone account (pre-paid). Do I have to root my phone before following this procedure? I have never tried to root this phone before. I have been researching the topic for a long time and just wanted to make sure I understand everything thoroughly before I pull the trigger. Don't want to trip KNOX or brick my phone. Any help would be much appreciated. Thanks fellas.
Matt
---------- Post added at 11:42 AM ---------- Previous post was at 11:31 AM ----------
Zero4 said:
Could someone tell me if the encryption menu items are available on your GS6, and what build you are on?
I encrypted my phone about 2 builds back, and after the December update, upon reboot it no longer asks for my PIN/PW and encryption is no where to be seen in the settings, or at least I (and search) can't find it. I don't want to factory reset to see if it reappears...yet.
If AT$T removed encryption from the device in the next update, I'm going to be real pissed.
Also, I think (at the moment) my battery life is worse on the latest build, but I have been using my phone a little more lately. But last night I went from 100% at 7:05pm to 5% at 11:30pm. 4.5 hours is not way to quick for a battery to die. Wakelock Detector (no root) didn't give much info, and the system menu for battery gave 3 of the top 4 to Android OS, Google Play services, Android System.
TIA
Click to expand...
Click to collapse
I'm on AT&T Galaxy S6, SM-G920A, Android Version 6.0.1, Build #: MMB29K.G920AUCS5DPK3. My phone is stock, no root. I have the encryption settings and am currently using them. Everything seems to be working fine.
---------- Post added at 06:22 PM ---------- Previous post was at 05:42 PM ----------
mjr4281 said:
Hey guys,
I'm on a stock Samsung Galaxy S6, SM-G920A, Android Version 6.0.1, Security Patch Level December 1, 2016, Build Number: MMB29K.G920AUCS5DPK3. I have an AT&T Go-Phone account (pre-paid). Do I have to root my phone before following this procedure? I have never tried to root this phone before. I have been researching the topic for a long time and just wanted to make sure I understand everything thoroughly before I pull the trigger. Don't want to trip KNOX or brick my phone. Any help would be much appreciated. Thanks fellas.
Matt
---------- Post added at 11:42 AM ---------- Previous post was at 11:31 AM ----------
I'm on AT&T Galaxy S6, SM-G920A, Android Version 6.0.1, Build #: MMB29K.G920AUCS5DPK3. My phone is stock, no root. I have the encryption settings and am currently using them. Everything seems to be working fine.
Click to expand...
Click to collapse
They did change it up though. Whatever you choose as your screen lock i.e., pattern, pin, password, is what will be used for unencryption at start-up. The one thing that doesn't make sense to me is that they now give you an option to use one of these methods or none at all during start-up. I don't see the point in using encryption if you can't password protect it, but I haven't fully researched all the options yet.
https://developers.google.com/android/ota
I've update via adb.
Swiping via Soli seems much improved for me when using the music player.
What is the best way to do the OTA with Magisk root and custom kernel installed? It has been a very long time since I have rooted a phone and did any OTA.
ExcuseTheN00b said:
What is the best way to do the OTA with Magisk root and custom kernel installed? It has been a very long time since I have rooted a phone and did any OTA.
Click to expand...
Click to collapse
I followed the below steps. This is assuming you are already rooted on October patch level and want to maintain root.
1) Downloaded the factory images for the Nov update (https://developers.google.com/android/images) to the PC.
2) Extracted the zip file (make sure to extract the zip file inside the first one. That zip contains the .img file which we will need in step 4 ).
3) Edited the flash_all.bat file to remove '-w' parameter so that the data is not wiped.
4) Copied the 'boot.img' to the phone and used magisk manager to patch the boot file (https://topjohnwu.github.io/Magisk/install.html#boot-image-patching).
Copied the patched 'magisk_patched.img' from the phone to the PC.
NOTE: I also disabled all magisk modules before the next steps. This is just to ensure that custom module don't mess up the update (have seen this with the Oneplus 7 PRO android 10 update when i had that device)
5) Reboot phone into bootloder and connect to PC
6) Flashed the update by running the flash_all.bat file (make sure to remove the '-w' parameter before flashing so that DATA is not wiped). I did run into issue where the vendor.img failed at flashing but a change of USB cable fixed that (I have seen this issue before. some cables just don't work in fastboot/adb).
7) Once the flashing completes the phone reboots and does some update after booting up.
8) Again reboot into bootloader. Flash the boot with the 'magisk_patched.img' that was copied in step 4.
Code:
fastboot flash boot magisk_patched.img
I always flash it on both the a & b partitions by using below command.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
9) Reboot the phone. At this point you have ROOT with Magisk and your custom kernel would be gone since stock/patched boot.img would have replaced it. You can re-flash your kernel (make sure the kernel has been updated for the November security update). Also at this point you can enable any modules that you may have disabled before the update.
I got november update now from ota..
Does anyone know why the Pixel 4 has 3 update files? Is there a specific version need for a specific carrier or something?
These are all Nov 2019 Factory/OTA update files for the Pixel 4.
QD1A.190821.007.A3
QD1A.190821.014
QD1A.190821.014.C2
---------- Post added at 09:23 AM ---------- Previous post was at 09:21 AM ----------
meek2100 said:
Does anyone know why the Pixel 4 has 3 update files? Is there a specific version need for a specific carrier or something?
These are all Nov 2019 Factory/OTA update files for the Pixel 4.
QD1A.190821.007.A3
QD1A.190821.014
QD1A.190821.014.C2
Click to expand...
Click to collapse
Actually I just found the answer here: https://support.google.com/pixelphone/thread/18553639?hl=en
Pixel 4 (XL):
US (ATT & Verizon): QD1A.190821.014.C2
US (TMobile, Sprint, Google Fi) & UK carriers: QD1A.190821.014
All other carriers (AU/JP/CA/TW/US): QD1A.190821.007.A3
ExcuseTheN00b said:
What is the best way to do the OTA with Magisk root and custom kernel installed? It has been a very long time since I have rooted a phone and did any OTA.
Click to expand...
Click to collapse
The post above (post #3) that says to use the factory image isn't wrong, but it isn't the easiest method either.
You can side-load the OTA image. You can do this on a phone with a locked or unlocked bootloader and you don't need to modify any files to prevent it from wiping the phone. It's just like the OTA update and will not wipe the phone.
You can find the files and directions directly from Google. https://developers.google.com/android/ota
Once the update is done, you will need to reroot the phone using the standard modified boot image method and then reflash your custom kernel (after making sure it has been updated to the latest OTA version). Just be aware that while the actual flashing time is much shorter than taking the OTA normally, it may have to optimize all of the apps during the initial boot. Unfortunately it doesn't give you any indication this is going on (unlike during a normal OTA update) and therefore people tend to get impatient and reboot during the initial boot. Don't do this. Just be patient and let the phone do it's thing. My phone took about 20 minutes to boot initially after side-loading the Nov update because I have a decent number of apps that it had to optimize.
Oops, nevermind. fixed
How do I get into bootloader mode? I can get into fastboot mode fine. But when I execute the command 'fastboot flashing unlock' the command prompt just shows waiting for device.
Spookymyo said:
How do I get into bootloader mode? I can get into fastboot mode fine. But when I execute the command 'fastboot flashing unlock' the command prompt just shows waiting for device.
Click to expand...
Click to collapse
Instructions here
https://developers.google.com/android/ota
Anyone experiencing "improved camera quality" that was listed in the change log? What are we looking for specifically?
xxaarraa said:
Anyone experiencing "improved camera quality" that was listed in the change log? What are we looking for specifically?
Click to expand...
Click to collapse
Pure speculation on my part, but I wonder if Google didn't tweak the auto-white balance due to the complaints about how the phone handled white balance in pictures with a predominantly red color.
Apparently Google killed the manual update your phone function again. At least on my pixel 4. Seemed to happen to me all the time on the pixel 3 too. Anyone else have the same issues?
Sent from my Pixel 4 using Tapatalk
BubbaGumprc said:
Apparently Google killed the manual update your phone function again. At least on my pixel 4. Seemed to happen to me all the time on the pixel 3 too. Anyone else have the same issues?
Click to expand...
Click to collapse
I had the same issue, the check update function did not work on my P4. It was working great on my P3.
Ugh! I got antsy and manually flashed the November factory image and now my face unlock is completely broken. I've tried rebooting, deleting face data + creating a new one in different lighting environments 5+ times now. No matter what I do the phone will not recognize my face anymore. It was working flawlessly on the October patch.
Now I'm afraid broken face unlock is one of the reasons Google delayed the role out of the November patch. Not a happy camper right now.
EDIT: I had to revert back to the October patch (full wipe) to get face unlock working again.
sn0warmy said:
Ugh! I got antsy and manually flashed the November factory image and now my face unlock is completely broken. I've tried rebooting, deleting face data + creating a new one in different lighting environments 5+ times now. No matter what I do the phone will not recognize my face anymore. It was working flawlessly on the October patch.
Now I'm afraid broken face unlock is one of the reasons Google delayed the role out of the November patch. Not a happy camper right now.
EDIT: I had to revert back to the October patch (full wipe) to get face unlock working again.
Click to expand...
Click to collapse
that's, odd, i updated to november, and my phone is spot on, I've yet to face an issue, or if i have i havent even noticed
sn0warmy said:
Ugh! I got antsy and manually flashed the November factory image and now my face unlock is completely broken. I've tried rebooting, deleting face data + creating a new one in different lighting environments 5+ times now. No matter what I do the phone will not recognize my face anymore. It was working flawlessly on the October patch.
Now I'm afraid broken face unlock is one of the reasons Google delayed the role out of the November patch. Not a happy camper right now.
EDIT: I had to revert back to the October patch (full wipe) to get face unlock working again.
Click to expand...
Click to collapse
Make sure you picked the correct image for your phone variant.
My phone came with build 007, installed a different one and it broke the face unlock. Installing back 007 restored it.
Im on November and face unlock works just fine
Does this undo the tweak to get Google pay to work with magisk? Or will we have to re do it?
ahsank128 said:
that's, odd, i updated to november, and my phone is spot on, I've yet to face an issue, or if i have i havent even noticed
Click to expand...
Click to collapse
hm... When I flashed the November image I did full wipe. Mybe this time I'll try without wipe and see if it retains proper face unlock from the October image.
thehartk said:
Make sure you picked the correct image for your phone variant.
My phone came with build 007, installed a different one and it broke the face unlock. Installing back 007 restored it.
Im on November and face unlock works just fine
Click to expand...
Click to collapse
Yeah, I was on 10.0.0 (QD1A.190821.007, Oct 2019) before clean flashing 10.0.0 (QD1A.190821.014, Nov 2019). I'm now back on 10.0.0 (QD1A.190821.007, Oct 2019) to get face unlock working again.
I wonder if I should be flashing 10.0.0 (QD1A.190821.007.A3, Nov 2019), instead? That ".A3" is giving me pause though.
Google really needs to label/identify these factory images better like they used to with (unlocked US) or (verizon) etc.. This is confusing.
sn0warmy said:
Google really needs to label/identify these factory images better like they used to with (unlocked US) or (verizon) etc.. This is confusing.
Click to expand...
Click to collapse
Look here: https://support.google.com/pixelphone/thread/18742521?hl=en
sn0warmy said:
hm... When I flashed the November image I did full wipe. Mybe this time I'll try without wipe and see if it retains proper face unlock from the October image.
Yeah, I was on 10.0.0 (QD1A.190821.007, Oct 2019) before clean flashing 10.0.0 (QD1A.190821.014, Nov 2019). I'm now back on 10.0.0 (QD1A.190821.007, Oct 2019) to get face unlock working again.
I wonder if I should be flashing 10.0.0 (QD1A.190821.007.A3, Nov 2019), instead? That ".A3" is giving me pause though.
Google really needs to label/identify these factory images better like they used to with (unlocked US) or (verizon) etc.. This is confusing.
Click to expand...
Click to collapse
Yes flash the .007.A3 if you were on the .007 before. I went through the same problems with the .014 too but .007.A3 fixed it.
I went to check for system updates today and my pixel initially started to download the latest patch and then after a couple of seconds went straight to telling me that there is no update available. Anyone else have this issue and/or successfully update to the March 2020 OTA via the process below?
Updating Phone Once Rooted:
- Check for device updates, when found:
- Tap uninstall in 'Magisk Manager'
- Tap restore images
- install OTA (do not reboot)
- Back to magisk, tap install > select install to inactive slot
- When magisk installed, press the reboot button in it. It'll force to the other slot AND you'll be updated AND rooted
I assume I should be able to go under 'System' -> 'Advanced' and get the OTA under 'System Update'. I've already disabled 'Automatic system updates' under 'Developer Options'. Just making sure google is somehow not blocking the update on rooted devices and that the above steps are correct. Thank you in advance!
Found similar thing on reddit here.
It's very common for unlocked and rooted Pixel phones to not "find" or complete the monthly OTA updates. There must be some sort of check in the OTA process that fails on rooted phones.
You should get familiar with the "sideloading" process of manually flashing OTA images.
Here is a set of instructions that I wrote in my Pixel 3a rooting guide. The process is exactly the same for the Pixel 4 series.
Taking an OTA update should be as easy as the above instructions. However there is another option available to install an OTA update called sideloading. Sometimes the update doesn't appear on the phone in a timely manner and you may want to manually install the update. Other times the OTA update seems to fail for some reason. In the end, you may decide to sideload the OTA instead of trying get it via the update feature on the phone. Surprisingly, it's actually faster to install the update via sideloading than it will be to take the OTA normally. I'll walk through the sideloading steps.....
Optional Step 1 - Uninstall Magisk (so that it restores the stock boot.img). If you find yourself unable to boot into recovery, you will have to restore the stock boot.img. I've run into this issue on some Android 10 images, but not all.
Step 2 - Download to your computer the correct OTA image from here
Step 3 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 4 - Boot your phone into recovery (type the command "adb reboot recovery").
Step 5 - The phone will have a green android robot with a red sign over it's open access panel. Press the power button and then the volume up button while still holding down the power button.
Step 6 - Select "Apply update from ADB" using the volume buttons to highlight the choice and the power button to select it to enter the sideload mode.
Step 7 - Using your computer, type "adb sideload ota_file.zip" where ota_file.zip is the name of the OTA file you downloaded in step 2.
Step 8 - Once the update finishes, reboot the phone to complete the update process. (See note below about initial boot times).
Step 9 - To obtain root again, please use one of the two root methods listed above
Please note, the initial boot may take quite a while. I've seen the process take upwards of 20 minutes and longer. I think part of the reason it can take so long is that it optimizes the apps during this boot process. The more apps you have, the longer the process may take. When you take a regular OTA update, the phone will change to a screen where is specifically tells you it is optimizing the apps and counts up as the apps are optimized to give you status updates. When you use the the side-load method, it all happens with just the regular boot animation running and without any status updates. Because of this, it is easy to assume something has gone wrong with the boot process while in fact the phone is working through the process normally. If it isn't boot looping (showing the initial power screen before moving back to the boot animation), everything is fine and you just be patient and let the phone complete the process.
Click to expand...
Click to collapse
sic0048 said:
It's very common for unlocked and rooted Pixel phones to not "find" or complete the monthly OTA updates. There must be some sort of check in the OTA process that fails on rooted phones.
You should get familiar with the "sideloading" process of manually flashing OTA images.
Here is a set of instructions that I wrote in my Pixel 3a rooting guide. The process is exactly the same for the Pixel 4 series.
Click to expand...
Click to collapse
Thanks for the reply! I'm very used to sideloading/dirty flashing the updates, was hoping to use the Magisk method . Seems like google is getting smarter with their updates. I am guessing the current inability to see the OTA is due to the updates with google pay and google wanting to ensure banks it is safe.
I just finished sideloading March's OTA and patching the boot.img and everything seems to work, just a bit more effort than leveraging Magisk.
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
I experienced same exact thing. Looks like it saw the update at first then after a few seconds reverted to No updates available. About to try uninstalling Magisk, if no bueno, then gonna just sideload.
Spookymyo said:
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
Click to expand...
Click to collapse
Did you disable 'Automatic system updates' on the phone? That should still allow the download to occur just not the install. It seems like google got smarter with this update to detect rooted phones.
Gooch4130 said:
Did you disable 'Automatic system updates' on the phone? That should still allow the download to occur just not the install. It seems like google got smarter with this update to detect rooted phones.
Click to expand...
Click to collapse
Yes I disabled automatic updates. It didn't do it automatically, I clicked the check for update button. Normally when I do that it says there's a download available and then I know to check online for the flash file. This time it updated without stopping.
FAILED (remote: Failed to write to partition Not Found)
what i am doing wrong ????
---------- Post added at 12:21 PM ---------- Previous post was at 12:17 PM ----------
Boot loader is unlocked...
10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)
this version i did ota update
i am from germany.
okay, i found a way to root, but how is it with safety net fix ???
anyone an idea ???
Deleted
Spookymyo said:
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
Click to expand...
Click to collapse
It installed the OTA for me too, now I'm afraid to restart my phone.
mattcoz said:
It installed the OTA for me too, now I'm afraid to restart my phone.
Click to expand...
Click to collapse
I would flash Magisk again before you restart.
I still can't get my phone rooted. I'm not sure what's going on. I wonder if other people have been able to successfully root the March update.
I successfully rooted the March update, using the boot.img method.
Spookymyo said:
I would flash Magisk again before you restart.
I still can't get my phone rooted. I'm not sure what's going on. I wonder if other people have been able to successfully root the March update.
Click to expand...
Click to collapse
I rooted with boot.img method, as well
sruel3216 said:
I rooted with boot.img method, as well[/QUOTE
I ended up following this
https://www.youtube.com/watch?v=kZY8qiz2SZ0
Click to expand...
Click to collapse
I got it rooted. It ended up taking a factory reset. It must have been some file interfering with the process. Once I reset my phone the rooting process went without incident.
As I'm searching for a more Phone based update wy, I'm thinking about to use maybe the Implemented OTA Process, but download the OTA-File manually... But for that We must know,how the OTA process is working. Did someone know:
- Where the update stores the download fine (I found a OTA and a OTA_Packge directory in the /Data/ folder)
- is there maybe a setting or information which must be injected somewhere (maybe a txt file)
- after that the ota update could then maybe started by hand
Has someone informations on that? If maybe someone where the ota still works and stil has root could check the files and places?
Chris.C said:
sruel3216 said:
I rooted with boot.img method, as well[/QUOTE
I ended up following this
https://www.youtube.com/watch?v=kZY8qiz2SZ0
Click to expand...
Click to collapse
Worked like charm!! Thanks!! :good:
Click to expand...
Click to collapse
I unlocked the bootloader, sideloaded the August 2020 OTA and flashed the patched boot image. Kept bootlooping, then I restored to the original, booted in, installed Magisk Manager and then flashed the patched image again. Just leaving this here in case it helps someone.