Hi all,
I haven't really seen any information on this topic (I don't check the forum as often as I should though) but I just discovered a serious bug for us that updated to 7.0 (build NRD90M) by enrolling in the beta program to receive 7.0 prior to the OTA being release. Most of us know by now that the official OTA image which was released was NRD90U due to all the bugs which were included in NRD90M. The problem it appears is those of us who ended up with NRD90M were actually unenrolled from the normal release cycle of OTA updates for the Nexus 6P due to the fact that NRD90M was never pushed as an official build, and those of us who immediately unenrolled in the beta were also no longer eligible for any update as well. I had been concerned with the fact that I was still on August's security updates on NRD90M as of today the 15th of October. I can now verify that re-enrolling into the beta program fixes this and actually updates the phone to the latest official release of 7.0 which is build NBD90X with Octobers security patches. It does appear that any of us who jumped the gun and went through the beta to update and then left the beta program get stuck in a gray area which receives absolutely no OTA updates for official images. Just hoping this info can assist anyone who was in the same situation as i was of two month old security updates and still dealing with the battery issues on NRD90M. All of it can be easily fixed by enrolling in the beta again, installing the OTA you will receive (NBD90X) and then leaving the beta program again (unless you would like to remain in it). This resulted on zero data loss as it is installing just like a typical OTA update.
Prior to re-enrolling in the beta program
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Post update and unenrolling from the beta program again.
Hope this assists anyone who was in my situation and didn't want to deal with side loading or was afraid of losing data.
Thanks.
Sent from my Nexus 6P using XDA-Developers mobile app
Edit (10-31-2016): Since the beta program has now surpassed the NBD90X image and is now pushing out a beta of 7.1.1, you can find the factory NBD90X image link below and side load with ADB. You can still use the beta program to update to 7.1.1 and un-enroll from the beta, forcing your 6P to downgrade to NBD90X, but it will also wipe your data partition. The only way at this time to retain your personal files is to side load the image below using ADB or a similar tool.
https://dl.google.com/dl/android/aosp/angler-nbd90x-factory-4e17ed23.zip
I also enrolled in the Beta program to get Android 7.0 right away. After that, I unenrolled. Unlike you, I got the OTA updates just fine.
Sent from my Nexus 6P using Tapatalk
Yep, me too. I was enrolled in beta, then got release and I unenrolled. The phone did not erase and I eventually ended up with 90X as well via OTA.
I did just reflash (90X) from scratch to try to see if that helped my bad battery life..... sadly it didn't. It still sucks.
Are either of you sure you received NRD90M from the beta and not NRD90U. Those of us who went through beta ended up with build M and the Google developer forums are filled with similar stories of people being stuck the last two months without a OTA notification. Most people have ended up side loading. If you were a week or two late on signing up for the beta you would have received NRD90U which was the actual final release candidate which would explain why you have received updates.
Sent from my Nexus 6P using XDA-Developers mobile app
I did the exact same thing. I unenrolled though and still received the October update just fine. I actually received right on the 5th or 6th, which was nice considering I never got the monthly patches until around the 15th or so.
Sent from my Nexus 6P using XDA-Developers mobile app
Going to try and restate the fact that this post was for people on the NRD90M build and not for those who enrolled in the beta a few weeks later and likely received NRD90U. For those of us who went through the beta within a few days of 7.0 being released in the program, we received NRD90M which at the time was identified as the release candidate. Unenrolling left anyone with NRD90M stuck with no updates as the build was supposed to be part of the normal upgrade path but the actual OTA released was NRD90U. This left anyone with NRD90M no upgrade path as the official upgrade path was NRD90U to NBD90X. Without enrolling back into the beta or side loading, the phone will not update. This can be verified by numerous posts over on the official Android developers forum through Google.
Sent from my Nexus 6P using XDA-Developers mobile app
nexus 6p nougat 7.0 nethunter kernel
pls any one got the nethunter kernel for nexus 6p update of nougat 7.0 NBD90X. pls can u make a kernel pls xda developers pls.help me. i am not able to install external wifi card pls help me ony one. thank u.
I did the same thing to get to NRD90M. No OTA updates since. I re-enrolled in the preview and it wanted to load 7.1.1, so I un-enrolled. Not sure what my options are now. I don't want to unlock the bootloader and sideload (if I can figure that out) since I use Android Pay a lot. Any suggestions?
My husband and I are both stuck on NRD90M. Tried re-enrolling in the beta program tonight but got offered 7.1.1 beta instead of the stable NBD90X, so I un-enrolled again without updating. Going to try sideloading the NBD90X ota using adb tomorrow.
thehoz said:
I did the same thing to get to NRD90M. No OTA updates since. I re-enrolled in the preview and it wanted to load 7.1.1, so I un-enrolled. Not sure what my options are now. I don't want to unlock the bootloader and sideload (if I can figure that out) since I use Android Pay a lot. Any suggestions?
Click to expand...
Click to collapse
I'm no expert and I'm sure someone will correct me if I'm wrong but I thought you did not need to unlock your bootloader to sideload the full system OTAs that Google has been releasing lately i.e. not the full factory images but the large OTA images.
Link for further info:
http://www.androidpolice.com/2016/0...s-for-nexus-devices-alongside-factory-images/
npras42 said:
I'm no expert and I'm sure someone will correct me if I'm wrong but I thought you did not need to unlock your bootloader to sideload the full system OTAs that Google has been releasing lately i.e. not the full factory images but the large OTA images.
Link for further info:
http://www.androidpolice.com/2016/0...s-for-nexus-devices-alongside-factory-images/
Click to expand...
Click to collapse
Wouldn't that wipe my phone? Can I do it with the partial upgrade? And thanks.
Sideloading the OTA will not wipe the phone and does not require an unlocked bootloader.
https://developers.google.com/android/nexus/ota
thehoz said:
Wouldn't that wipe my phone? Can I do it with the partial upgrade? And thanks.
Click to expand...
Click to collapse
As kappadappa says above, it won't wipe. Not sure what you mean by partial update but if you have a phone that boots you should be able to sideload the OTA.
npras42 said:
As kappadappa says above, it won't wipe. Not sure what you mean by partial update but if you have a phone that boots you should be able to sideload the OTA.
Click to expand...
Click to collapse
BY partial I meant OTA, sorry for my confusion. Anyway, I gave it a try. I seem to be unable to install the usb drivers. The nexus 6p doesn't show up in my Device Manager to update drivers. It does show up under Portable Devices, with some drives, but it won't let me update the driver. adb does not see my phone, which is why I think I need this step. Any thoughts? Thanks.
thehoz said:
BY partial I meant OTA, sorry for my confusion. Anyway, I gave it a try. I seem to be unable to install the usb drivers. The nexus 6p doesn't show up in my Device Manager to update drivers. It does show up under Portable Devices, with some drives, but it won't let me update the driver. adb does not see my phone, which is why I think I need this step. Any thoughts? Thanks.
Click to expand...
Click to collapse
Make sure you have switched on USB debugging in Settings > Developer options. To get the developer options menu in Settings go to About phone and press on Build number multiple times until it tells you that Developer options are now available.
Another way to make things a little bit easier if you don't really know how all this works is to just google search for and install a program called Wug's Nexus Toolkit. It walks you through installing USB drivers etc and allows you to sideload the OTA from the link above.
npras42 said:
Make sure you have switched on USB debugging in Settings > Developer options. To get the developer options menu in Settings go to About phone and press on Build number multiple times until it tells you that Developer options are now available.
Another way to make things a little bit easier if you don't really know how all this works is to just google search for and install a program called Wug's Nexus Toolkit. It walks you through installing USB drivers etc and allows you to sideload the OTA from the link above.
Click to expand...
Click to collapse
The driver's did install, apparently. Win 10 recognizes the 6p and when running normally, the phone is recognized in adb. However, when I go into recovery and it says it's waiting for the adb sideload, adb does not see the phone. I'll try Wug's. And thanks!
I'm still running NRD90M rooted. I wiped and flashed the OTA once it was out. I haven't had any of the battery issues that are plaguing so many people. It's smooth and perfect. I'm too lazy to flash security updates all the time, plus I'm a little afraid of getting battery issues. I'm waiting for stable 7.1.1 to flash again.
thehoz said:
...when I go into recovery and it says it's waiting for the adb sideload, adb does not see the phone...
Click to expand...
Click to collapse
I had the same issue. What worked for me was: once in recovery, on the 6p select "Apply update from ADB" and then unplug and re-plug the 6p into the computer. Windows 10 will then recognize the 6p with a different driver.
Then, in ADB type the command "adb kill-server" and then "adb devices" and the device should show up ready for sideloading.
Hope that helps
Hi, I had updated my phone with the Beta Program and got the latest build at the time NRD90M. However, I've not be receiving any OTA after this. I'm in India and with Indian Carriers. I tried re-enrolling into the Beta Program, however, I'm now being offered 7.1.1 (NPF10C) build. How do I get the latest 7.0 build without side loading. Any ideas ?
Also, if at all I go for side loading will it screw up future OTAs or will everything return to normal with future updates ?
I was assisting someone on the google developers forum with this same issue as it does appear entering the beta now offers 7.1.1 beta instead of NBD90X. He was able to enroll in the beta, update to 7.1.1, leave the beta and downgrade to NBD90X without data loss. I can't verify this first hand as this was in a forum but it may be worth researching to save the hassle of ADB / Sideloading for those that haven't done it before.
Related
I have the LTE version on Boost, its already on 5.1 but there is obviously an update for it, I get the prompt to download update but when I go to install it, the install fails. The notification gets annoying b/c it seems to come up while i'm trying to use the phone. How can I force the update? Or disable the notification for the update entirely....I like the phone as it is right now
is it fully stock ?
once you tinker with it you may lose ability to get OTA updates i think right.
and that update could be a "Stagefright" update.
update failure is due to modified recovery/system
Dvdxploitr said:
I have the LTE version on Boost, its already on 5.1 but there is obviously an update for it, I get the prompt to download update but when I go to install it, the install fails. The notification gets annoying b/c it seems to come up while i'm trying to use the phone. How can I force the update? Or disable the notification for the update entirely....I like the phone as it is right now
Click to expand...
Click to collapse
now to verify if ur system is modified then do one thing, reboot into ur bootloader and there will be displayed some text in yellow that device connected via USB or something like that above this text is : system status: official/modified(depending upon ur device ). And my guess here is that ur system status is modified and hence u might not recieve updates. Don't worry bro! it doesnt matter, anyways we wont recieve updates for android v6.0. As for 5.1 use any custom rom like CM12.1 or PACMAN.
I bought the phone off eBay and its already rooted, so obviously it has been modified, i clicked on "Disable" on the moto udpate thing and it seems to not be bothering me with the updates. I think its crazy that it downloads the updates and then tells me to install it, but it won't actually install....i'll just leave it as it is for right now. The phone is only used for PerkTV apps, so its not even used for service
i searched this sub-forum for update failed and pretty much every single topic showed up LOL
it seems i too am getting this update prompt too.
i tried letting it update and it always fails then eventually i get into a loop.
my phone keeps restarting to recovery automatically.
but it stopped when i re-flashed my Squid kernel.
But i do want to install the update though.. the update details said it was a stagefright fix.
i figured out what was going on by reading the logs.
the update for me downloads and tries to install.. it asks you to restart to apply the update.
when it restarts it fails with an error mentioning "Keys" and the versions found / needed.
i am thinking i *might be able to adb side load the update with TWRP but i have not used that before yet.
i also think forcing the update may be a bad idea.. i don't want to brick it LOL
so i don't know..
edit:
I guess it's common for these to fail.
something set test Keys on my phone prob SuperSU
It got detected and then the update failed.
i found some side loading info and possible TWRP flashable version info for another phone.
But they say flash to a stock firmware and i have done that a lot lately and can't be bothered right now.
So it seems if i want the OTA update installed it's gonna be some work/waiting.
Going to keep an eye out for a TWRP ready flashable.zip though
I have the same issue as xpmule, when phone restarts to install the update it boots into recovery (TWRP) so the update fails. I restored a backup and now I am waiting for an update that I can flash using TWRP, stagefright is serious business.
I have an euro XT1524, rooted, Stock 5.1 US ROM flashed and squid kernel r10f.
I have a Canadian XT1527, rooted, Stock 5.1 US ROM flashed and squid kernel r10f.
And i still have not had much time to research more but i think the problem lies
with the singing keys..
i can see WHY it failed when you open the TWRP log (middle button)
my log said it failed to execute the update script because of bad keys..
It mentions i have test/keys and it expects to see Retail/Keys
When i looked on the web i see that could be because of SuperSU (being signed with TestKeys)
Or i thought maybe even Squids Kernel i am running.
If anyone seen a topic on this or what ever then let us know
i will prob keep poking around and see what i can do.
Problem is i am being VERY cautious i don't want to brick my phone.
Official OTAs tend not to flash on rooted or modified devices. Specifically with custom recoveries. The zips script verifies partitions and if something doesn't match it'll fail. Usually to get the ota you'll have to go back to completely stock unrooted firmware with the stock recovery.
After growing tired of seeing the update popup each time the phone decided to switch networks I did this:
Full TWRP Backup (just in case)
Flashed XT1527_SURNIA_RETUS_5.1_LPI23.29-18.9_cid9_subsidy-DEFAULT_CFC.xml.zip from here
I flashed back TWRP (well, just replaced the recovery.img from the stock rom, did the same with the logo)
Restored data backup
Reinstalled squid's kernel
Reinstalled SuperSU
Had some minor quirks, like losing the swiftkey language (just enter the config and download again, didn't lose predictions) and having to open apps that needed root and reapply SuperSU permissions, but all of those sound normal. Everything seems to be working correctly, there's no annoying popup nor Stagefright vulnerability.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ya i was thinking of doing similar pretty quick..
was waiting to hear back from people if that included stage fright fixes.
people are slow to reply here lol
thanks for the info.. i was not sure what parts of the back up i was going to restore.
also i use Swift Keyboard to.. i just wish the Lollipop UI had the Holo Theme or some dark theme.
but ya me too that prompt was getting a bit irritating lol
I have a virgin mobile xt1526 running 5.0.2 rooted but i need to update to 5.1, if i flash the ret_us update will it correctly identify my phone as VM? Boost users, did android correctly identify your phone as boost when you flashed the ret_us 5.1 update?
Sent from my XT1526 using Tapatalk
Sands207 said:
I have a virgin mobile xt1526 running 5.0.2 rooted but i need to update to 5.1, if i flash the ret_us update will it correctly identify my phone as VM? Boost users, did android correctly identify your phone as boost when you flashed the ret_us 5.1 update?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
The update is for people on 5.1 already.
There is a different update for the 5.0.2 versions.
The retail update will look for the right version to update or it will fail.
And it is VERY picky at what it expects to see too !
Your going to need the newest full firmware package (easiest way)
that is a whole new can of worms to open LOL
@direi
i did the same thing now..
i seem to be up running ok and not vulnerable using the same Stage Fright Test tool as you.
Although i had to let it fire up once after flashing then turn it off so i could get the partition restored.
Reinstalled squid kernel with twrp and problem solved. Then froze motorolaOTA. Working fine so far.
Google Now provide full block level OTA images, so they can be sideloaded onto your device no matter what version your on.
https://developers.google.com/android/nexus/ota
Instructions for sideloading the OTA images.
Use the latest OTA image from the above link instead of using Android N OTA.
Marshmallow OTA hose your Nexus device? Just flash the N dev preview.
Posting this in a new thread so more people see it.
Get the Android N Preview OTA from here.
Google has updated the OTA zips again for nexus 9.
We've updated the OTA packages on https://developer.android.com/preview/download-ota.html. This should fix the issue with adb sideload failing at 47%. Please try again with the new packages.
Click to expand...
Click to collapse
Quote taken from here
Note: Removed Marshmallow from the tittle because it has been report to work for lollipop brick as well.
Try this if sideloading a marshmallow OTA doesn't work. See here. (Also see this link for instructions on sideloading.)
My Nexus 9 that I purchased when the device was originally put up for sale, got an OTA to 6.0.1 a few weeks back. I had not activated OEM Unlock in settings, no developer mode so I also hadn't activated USB Debugging. Well, that legit OTA ended up soft bricking my device. From that moment on, all it would ever do was show the booting screen until the battery died.
I tried manually sideloading Google's official update to 6.0.1 to the device, no go. It kept failing during the process.
I tried (knowing it likely wouldn't work) playing around with Nexus Root Toolkit to see if maybe there was some magic in there that would work, no go.
After two straight weeks of trying, I could not get an update pushed to the device and last night had resigned myself to sending it into HTC for repair... something that they weren't sure yet whether or not would incur a cost FOR ME to repair, even though in a completely stock and pristine device, the OTA update is what hosed it.
This morning, I heard that Google released sideloadable Android N images for all supported Nexus devices that some were saying would work in this scenario. (https://plus.google.com/u/0/+ArtemRussakovskii/posts/K4oUnQymMqG)
And what do you know, that totally worked. It sideloaded to my Nexus 9 and its working again.
tl;dr If you got an OTA for your Nexus and it ruined the device, and nothing else works, try to update it to N. Worked for me.
Thanks to Artem and Lenny Fudenna for the heads up.
Click to expand...
Click to collapse
dweissinger said:
I wanted to thank you for posting this solution!! I was able to flash N onto my nexus 9 and it is working once again. I was going to post this onto a main thread so that more people can see this but i did not want to seem as if i was taking credit for finding this. You should post this there so that you can help others. Once again, I would like to thank you. I am now trying to get into the usb debugging menu to unlock the bootloader so this does not happen again but i cannot find it in this version of android.
MANY THANKS!!!
Click to expand...
Click to collapse
Thanks pal. You saved my Nexus 9 LTE after 4 months of soft brick.
This is because the N OTA is a full-block/full image OTA zip that doesn't check the system partition of it's current state. It will just blindly flash. This kind of OTA image is perfect for recovering locked bootloader devices because it is signed by Google, unlike their factory images which are not signed and gets flashed like any other custom ROM.
I hope Google will provide full-block OTAs for major version releases in the future to resolve instances like this. With the requirement of enabling OEM unlocking in the new Nexus devices, full-image OTAs like these would be required to recover from failed standard OTA updates. I imagine this can happen with the monthly security update OTAs like it did with you. For those who never had an OTA fail, they never knew they were dodging bullets all those times.
For those concerned that stolen devices can be re-purposed this way, fear not. Even with a factory reset (no more user data), after flashing this OTA to get my Nexus 9 working again, it asked me to authenticate with the last owner's credentials before letting me in. So this should still deter thieves if they get a hold of a full-image-OTA thinking they can just flash a factory image with a locked bootloader. Much safer than leaving the bootloader unlocked or keeping OEM unlocking enabled.
Another reason why it's a good idea vs the old Full Factory Image method: will not delete user data.
I seriously hope the Google Android team consider releasing full-image OTAs in the future as standard practice - at least for major Android releases (no need to do this for all the minor updates - kind of like reinstalling Windows and getting all the security updates).
Creating a full-image OTA shouldn't add much to their workflow. The OTA for Lollipop to Marshmallow, for example, would have to be a full-image OTA anyways. The only thing the Android team needs to do is to disable version checking so it can be side loaded no matter what state the system partition is in.
Also, if a user wants to keep their data partition intact, a full-image OTA for the major release is important. If Google only released a single full-image OTA for the original OS the device released with (example: Lollipop), and someone needs to recover from a bad OTA update when they're already in Marshmallow, the original Lollipop build may not work with the new data partition schema.
Of course you'd be thinking "I'll just be happy the device is not bricked", but if you can also solve the "I'm glad I didn't lose any data" dilemma without much effort, why wouldn't you?
Well, I have discovered an exception to this solution .
Yesterday I set my Nexus 9 to update to the Android N Preview but when I returned I had the robot with the exclamation mark and my machine would not boot . I went through all the processes to try and get a factory image of 6.0.1 installed but had not preset my bootloader to allow an unlock.
I eventually found this article and duly downloaded the Android N developer preview factory image and then tried to ADB sideload but the process failed.
And I knew why it failed. It failed because it told me that the factory image I had downloaded from the correct URL was older than the version that had failed the OTA process.
Google does not give a version date for their Android N developer images so I had concluded that they must be up-to-date.
I now realise that their image was not up-to-date so I will now have to wait for Google to publish a newer version of their Developer N factory image that is the same age or newer than the failed OTA update from yesterday so that I can successfully ADB sideload the image without getting this error .
Just as well that I have some technical knowledge or I'd be sending my Nexus 9 back to HTC for something that was not my fault.
Overall - not impressed.
Herbiv4 said:
I eventually found this article and duly downloaded the Android N developer preview factory image and then tried to ADB sideload but the process failed.
Click to expand...
Click to collapse
You don't sideload a factory image, you sideload an "OTA zip" linked in the OP or again here
corkiejp said:
You don't sideload a factory image, you sideload an "OTA.zip" linked in the OP or again here
Click to expand...
Click to collapse
Just to clarify - I was up until 3:30am this morning having been through factory images, OTA zip files, the SDK for Android, the Wugfresh Nexus Root Kit, installing Linux Mint to try and get fastboot working when my Windows PC didn't seem to want to recognise my Nexus 9. I eventually sorted out the drivers included with the SDK because the Wugfresh drivers did not play nicely with my Nexus 9. Then I realised that as my bootloader was locked I could get nowhere with restoring 6.0.1. MMB29R.
After more googling I found this webpage and the link to the OTA .zip file plus the instructions of how to force the upgrade to the developer preview of Android N. Fantastic I thought.
I did in fact download the OTA .zip file from the right URL posted above and tried to sideload that file but it failed because the download was older than the files that Google sent to my Nexus 9 OTA earlier the previous afternoon.
So, as I said before, I now have to wait until Google to update their OTA .zip file to a version equal to or newer than the failed OTA file from yesterday.
As Google don't give publication dates to these files I will have to regularly check that web page until new files appear when they send out a further update .zip package.
So apologies for using the wrong phrase - it wasn't a factory image - it was an OTA .zip file and my tablet did try to send over the .zip file but it failed owing to it's age relative to the files already on my Nexus 9.
Hope that this clarifies everything.
The bottom line is - sideloading an OTA.zip file isn't as simple as it has been made out to be.
Herbiv4 said:
I did in fact download the OTA .zip file from the right URL and tried to sideload that file but it failed because the download was older than the files that Google sent to my Nexus 9 OTA.
Click to expand...
Click to collapse
Thanks for clarifying, Google must have sent you an Android N OTA which included the latest patch. Hopefully they will provide new OTA zips with Preview 2 in April. Which should hopefully resolve your problem. As i haven't seen a link for the latest patch OTA yet.
Herbiv4 said:
As Google don't give publication dates to these files I will have to regularly check that web page until new files appear when they send out a further update .zip package.
Click to expand...
Click to collapse
You could setup a change detection on that page. I use it on the factory images page all the time.
Herbiv4 said:
The bottom line is - sideloading an OTA.zip file isn't as simple as it has been made out to be.
Click to expand...
Click to collapse
I remind you of the title of this thread "Marshmallow OTA update bricked ..." which should make this process still valid for those devices. Your findings are worth posting on the Android N thread.
my tablet is bricked at "6.0/MPA44I/217251", and I have bootloader locked, OS-n/a, tried to adb sideload the zip, and It doesn't work
Can anyone help me?
ignaciouy said:
my tablet is bricked at "6.0/MPA44I/217251", and I have bootloader locked, OS-n/a, tried to adb sideload the zip, and It doesn't work
Can anyone help me?
Click to expand...
Click to collapse
MPA44I is Marshmallow Developer Preview. Is your device bricked that long? You should have RMA'd that while in Warranty.
Please check stock recovery to see if your device reports a different build version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
corkiejp said:
MPA44I is Marshmallow Developer Preview. Is your device bricked that long? You should have RMA'd that while in Warranty.
Please check stock recovery to see if your device reports a different build version.
Click to expand...
Click to collapse
You mean this?
That long because I tried everything, and nothing worked
I can't RMA because this was a gift in USA, and I live in Uruguay. So I can't send it to usa and get another back, I think I can't do that. + I can't afford it :/
ignaciouy said:
my tablet is bricked at "6.0/MPA44I/217251", and I have bootloader locked, OS-n/a, tried to adb sideload the zip, and It doesn't work
Can anyone help me?
Click to expand...
Click to collapse
ignaciouy said:
That long because I tried everything, and nothing worked
I can't RMA because this was a gift in USA, and I live in Uruguay. So I can't send it to usa and get another back, I think I can't do that. + I can't afford it :/
Click to expand...
Click to collapse
What error did you get when trying to sideload the Android N zip?
corkiejp said:
What error did you get when trying to sideload the Android N zip?
Click to expand...
Click to collapse
First of all, thanks for replying, this is what I get
I checked the md5 of the file and it's the same of the google download page
ignaciouy said:
First of all, thanks for replying, this is what I get
I checked the md5 of the file and it's the same of the google download page
Click to expand...
Click to collapse
You maybe looking to perform a miracle here.
Other things to check: -
Your Cable
Versions of adb and fastboot on your PC (have you got the latest).
People have reported errors when using a faulty cable.
The stock recovery on your device maybe to old to apply the Android N OTA.
I tried 3 cables, and the same with all of them.
192:volantis-npc56x ignacio$ adb version
Android Debug Bridge version 1.0.32
Revision 09a0d98bebce-android
192:volantis-npc56x ignacio$
Isn't that the last one?
The stock recovery on your device maybe to old to apply the Android N OTA.
Click to expand...
Click to collapse
And what can I do? :-|||
Herbiv4 said:
So, as I said before, I now have to wait until Google to update their OTA .zip file to a version equal to or newer than the failed OTA file from yesterday.
As Google don't give publication dates to these files I will have to regularly check that web page until new files appear when they send out a further update .zip package.
Click to expand...
Click to collapse
corkiejp said:
You could setup a change detection on that page. I use it on the factory images page all the time.
Click to expand...
Click to collapse
I setup a change detection on the page and google has update the OTA zip for Nexus 9.
Nexus 9
"volantis" volantis-ota-NPC56X-2785955f.zip
MD5: 36d813350fd660ab751a434782f5523f
SHA-1: 2785955fd77310106d2fa9f02f93b595d77b8e72
Nexus 9G
"volantisg" volantisg-ota-NPC56X-d93e161c.zip
MD5: 1fb7d83cd065a962dbed49e72db97dc4
SHA-1: d93e161c15503dc641b654f6ef4c1611222bc9fd
Click to expand...
Click to collapse
corkiejp said:
I setup a change detection on the page and google has update the OTA zip for Nexus 9.
Click to expand...
Click to collapse
Hello there Corkiejp, thanks very much for doing this. I downloaded this new OTA .zip file last night and used adb sideload as instructed. The transfer got to 47% on the PC side and on the Nexus 9 side the installation started briefly before suddenly rebooting so the install fails. When booting to recovery it shows the very latest version has registered but as the install has failed it cannot boot. I have done a factory reset and tried the process again but got the same result.
I'll have to wait for the next update and I'll try process again.
Otherwise, I'll have to ask HTC to fix this for me.
Herbiv4 said:
Hello there Corkiejp, thanks very much for doing this. I downloaded this new OTA .zip file last night and used adb sideload as instructed. The transfer got to 47% on the PC side and on the Nexus 9 side the installation started briefly before suddenly rebooting so the install fails. When booting to recovery it shows the very latest version has registered but as the install has failed it cannot boot. I have done a factory reset and tried the process again but got the same result.
I'll have to wait for the next update and I'll try process again.
Otherwise, I'll have to ask HTC to fix this for me.
Click to expand...
Click to collapse
Get the recovery logs to see where it failed and post the results in this thread.
Hello, good evening I'm having the same Issue that herbiV4; it gets till 47% then reboot and shows the android in its back and *ningun comando" (No commands) if I try to reboot, it send me once again to the recovery menu like... It doesn't have a OS? Even when it "updated" the recovery menu I really REALLY need help, I already contacted with HTC and the told me to send it but I'm from Venezuela so that's absolutely impossible for me, the Nexus has been bricked for 4 months ;---;
This is what the ADB shows me in the pc.
And this is what the tablet shows exactly after it reboot post "No error" from adb
This is the Last log, I truly dont get the "error" thingy :/
Help :crying:
If your getting error's from this process, it maybe helpful to google, to report your recovery logs to this thread.
If your device is in this state we would really appreciate logs from more devices.
1) Power off your tablet.
2) Press and hold the Volume Down button. Then, while holding Volume Down, also press and hold the Power button until the tablet turns on. (Fastboot mode)
3) Press the Volume Down button once to highlight "Recovery." Press the Power button to start in recovery mode. You'll see an image of an Android robot with a red exclamation mark. (Recover mode)
4) Press and hold down the Power button. Then, while holding Power, press and release the Volume Up button once.
5) Use the Volume Up and Volume Down buttons to navigate to "View recovery logs", and press the Power button to select.
6) There might be multiple log files. Start from "/cache/recovery/last_log" to view the log contents. Look for lines like "Finding update package...", "Opening update package...", etc. These lines indicate that the log file is for the OTA.
7) Navigate towards the end of the log using the volume buttons and look for any errors.
We are specifically interested in knowing if the bricked devices show "fsync failed: I/O error". We are exploring options to recover devices with locked bootloaders that are bricked. We'll post an update here.
Click to expand...
Click to collapse
This process has been reported to work on a bricked lollipop device.
This process has been reported to work on a bricked lollipop device.
defmetal96 said:
Hi I know this is a long shot but do you know how to fix this ^^ abort error?
Currently stuck on LRX22L but it is not booting as the OTA update to LRX22L failed for no apparent reason, foolishly my bootloader is still locked and the OEM unlock option is not checked.
is there any salvation?
Click to expand...
Click to collapse
defmetal96 said:
Sideloaded the N preview and that finally did the trick.
For anyone else with this issue I think the N preview is the only escape at present if your tablet is locked and refusing OTA updates
Click to expand...
Click to collapse
UPDATE: Axon 7 A2017U Build 29 (MR3)
New OTA update is arriving and looking forward for what bring to the table.
aerospaceman Employee Oct 30, 2016 6:01 PM
Over the next 24 to 72 hours, you can expect our 3rd software update (MR3) to the Axon 7 (A2017U). This update will bring your device to the latest build, B29. This update comes less than one and a half months from the previous one, but the more exciting news is that we're in parallel paths to deploy Nougat as quickly as possible.
Here are the latest updates you will see on B29 (coming from the previous build, B27):
Notification bell is now optional (hooray!)
New application management policy to enhance battery life
Optimized video camera focus on moving objects
Resolved .FLAC file playback issue
Visual Voicemail optimized for dual SIM
Updated fix for Mute Call issue
Other general enhancements
Note: This is an over-the-air (OTA) update. To check availability of an update, click on "Settings -> Updates."
Aside from this update, you can bet on our R&D team being hard at work on Android N. Early tests from your Mod Squad have been very positive and we trust that many of you will also not sleep for the first several days after upgrading. Setting Nougat aside, we remain heads down prioritizing fixes and enhancements for our community. Your constant feedback, both positive and negative, continue to motivate our R&D team. So please don't let up on your interactions with us and each other about the Axon 7. Until the next update, please drop a comment below to add further motivation for your R&D team!
Click to expand...
Click to collapse
-------------------------------------------------------------------------
UPDATE: Axon 7 A2017U Build 29 (MR3) Announcement Link
-------------------------------------------------------------------------
TWRP Flashable Files can be found here : TWRP_A2017U.B29_Bootstack_StockSystem_Files
What's does the " Parallel paths" mean....
S8ntsHaz3 said:
What's does the " Parallel paths" mean....
Click to expand...
Click to collapse
Ha! I was thinking the same thing. It sounds like more vague crap from ZTE like normal.
jonathan3579 said:
Ha! I was thinking the same thing. It sounds like more vague crap from ZTE like normal.
Click to expand...
Click to collapse
I'm wondering if it means that it's at a parallel in development as far as time between updates... Like b27>b29 was 1 and 1/2 months and that's what they're lookin at for a time frame?
S8ntsHaz3 said:
What's does the " Parallel paths" mean....
Click to expand...
Click to collapse
jonathan3579 said:
Ha! I was thinking the same thing. It sounds like more vague crap from ZTE like normal.
Click to expand...
Click to collapse
S8ntsHaz3 said:
I'm wondering if it means that it's at a parallel in development as far as time between updates... Like b27>b29 was 1 and 1/2 months and that's what they're lookin at for a time frame?
Click to expand...
Click to collapse
my guess is " performing of multiple operations simultaneously " meaning getting MR's OTA and working Naugat (Android 7) at the same time???
well i'm just assuming so , and i assume next Update will be N release., you know B3x
DrakenFX said:
my guess is " performing of multiple operations simultaneously " meaning getting MR's OTA and working Naugat (Android 7) at the same time???
well i'm just assuming so , and i assume next Update will be N release., you know B3x
Click to expand...
Click to collapse
Oh how I hope your right!!!!
Now to wait for the download link
xtermmin said:
Now to wait for the download link
Click to expand...
Click to collapse
It's here!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ZTE A2017U using Tapatalk
toyanucci said:
It's here!
Click to expand...
Click to collapse
How'd you get the embedded battery percentage?! I sorely miss that from my Nexus 6P.
jonathan3579 said:
How'd you get the embedded battery percentage?! I sorely miss that from my Nexus 6P.
Click to expand...
Click to collapse
There's an app in play store to enable it in any device!
Sent from my ZTE A2017U using Tapatalk
toyanucci said:
There's an app in play store to enable it in any device!
Click to expand...
Click to collapse
Oh sweet, thanks. I think I tried it before but it didn't stick after rebooting. Has it changed since then? If so, I'm definitely gonna have to search for it again.
I have the option for the update as well. Waiting as I'm rooted.
Here is the download link if anyone wants to play with it.
update_P996A01_B27_to_B29.up
I'll be looking into it and try to create a flashable zip for us TWRP users
DrakenFX said:
Here is the download link if anyone wants to play with it.
update_P996A01_B27_to_B29.up
I'll be looking into it and try to create a flashable zip for us TWRP users
Click to expand...
Click to collapse
Thanks for looking into a twrp version!
Sent from my ZTE A2017U using Tapatalk
Parallel paths does indeed mean they are simultaneously working on updates and the long awaited Nougaaaattttt update. ZTE has done a good job updating and listening to their customers in the z-forum. Lets hope this plus Official CM and unlock bootloader without breaking warranty will help ZTE be known as a developer friendly Own.
How do we install if we are unlocked bootloader and rooted??
Do we have any idea if flashing U roms on G device works? Would love to get rid of the bell
Here over in europe, i just received for my A2017G an 703mb big B05 Update.(previous B03)
Strange that ours is 703mb big (hope they fix the youtube freeze Problem) and also supports optional notification bell (no info for that in the change log)
Take a look:
DrakenFX said:
Here is the download link if anyone wants to play with it.
update_P996A01_B27_to_B29.up
I'll be looking into it and try to create a flashable zip for us TWRP users
Click to expand...
Click to collapse
Here is an Mega Mirror for the B29 update. Just in case.
I have simply copied it from its location "data/data/com.zte.zdm/files" where the updater places its OTA files.
https://mega.nz/#!K050XAqT!6EBTgtX13VTdAOiUjiYqeE6jemeOJ2mN8smrrreai6o
MD5: 9a7f45caf459a21a905de0c543748309
If you place the file into that directory. You should be good to go using the inbuild updater.
Dewaynelives said:
How do we install if we are unlocked bootloader and rooted??
Click to expand...
Click to collapse
I was on B27, unlocked bootloader, TWRP recovery, rooted, with changes to /system, and have successfully upgraded to B29 (w/ same modifications). Since I made changes to /system (AdAway, Titanium Backup, AFWall) and wanted a clean slate for everything, I wiped my A7.
If you don't want to factory reset your device and didn't make any changes to /system, you might only have to unroot, restore stock boot.img and stock recovery.img via TWRP (from rczrider's topic linked below), install B29.zip in stock recovery, flash TWRP, then flash root, but I didn't do it personally, so no guarantees.
Anyway, this is what I did. Some of these steps might not have been needed, and probably could have been done differently, but it's what worked for me, and yes I like rebooting:
1. Download the B29 update, DrakenFX's B27 StockSystem zip for TWRP (which also flashes stock boot.img), stock B27 recovery.img from rczrider, and SuperSU 2.65. Put all on microSD.
2. Booted into TWRP and did a factory reset, rebooted back into TWRP and flashed DrakenFX's B27 StockSystem ZIP, rebooted back into TWRP and flashed stock B27 recovery.img, rebooted device.
3. Powered on the device and made sure it booted into OS fine and was still reporting the correct amount of internal storage space. Rebooted into stock recovery and flashed the B29 update.zip from my microSD card. Installed fine, rebooted into OS to made sure it still worked.
4. Rebooted into fastboot, connected to my computer and flashed Unjustified Dev's TWRP via Minimal ADB & Fastboot, booted into TWRP and flashed SuperSU 2.65 from my microSD, let the device reboot itself a couple of times.
I now have B29 with unlocked bootloader, TWRP, and root.
NOTE: Something I noticed when I was going through and disabling system apps: WeShare can't be disabled from the Settings > Apps menu, but can be disabled by opening the app drawer, pressing and holding on it, and dragging it up to "Disable" at the top of the screen.
However, it would probably be easier to just wait for DrakenFX to create custom TWRP install zips for B29.
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.***
From the Pixel Images page:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This applies to ALL Tensor devices, regardless of whether or not you're rooted!
What this means: Once Android 13 Stable boots, it updates an anti-rollback counter in the device hardware to prevent rolling back the bootloader. This will prevent previous versions of the bootloader from starting.
Why this is a problem: The OTA only updates one slot, then reboots into that slot. It does not update both slots at once. If there is a boot failure after updating to Android 13, the device may attempt to "recycle" back to the old slot. If this other slot has a previous version of the bootloader, the bootloader will not start, rendering the device a brick.
How do I make sure this doesn't happen to me? If you updated via OTA, simply sideload the OTA again. Since you are currently on the Android 13 slot, this will overwrite your old Android 12 slot with the new bootloader.
If you have an unlocked bootloader and prefer to update using the factory image, you can flash the bootloader to both slots:
fastboot flash bootloader --slot=all <bootloader image> It's highly recommended you do this BEFORE updating, but if you didn't, do it as soon as possible.
I've updated several times since the August 2022 update, am I still at risk?
If you've updated via OTA at least once the initial Android 13 update, you should be fine. Instructions to check bootloader versions are further down this post.
The initial Android 13 release bootloader version is slider-1.2-8739948. As long as your bootloader is equal to or higher than this, you should be fine.
What if I was on the Android 13 Beta? Same as above - the beta did not incorporate the anti-rollback, and the beta bootloaders are still considered "old".
Will the new bootloader prevent me from flashing and running Android 12? The short answer is YES, for now. Contrary to what the warning above says, you CAN flash Android 12 on the Android 13 bootloader, and though it will boot, it will not run properly. See this post.
How do I check my current bootloader version?
Spoiler: Use these commands in an ADB command line:
Code:
adb reboot bootloader #Reboots device to bootloader.
fastboot getvar current-slot #Outputs current slot, should also be visible on the device screen: "Boot slot"
fastboot getvar version-bootloader #Outputs current slot's bootloader version, should also be visible on device screen "Bootloader version"
fastboot --set-active=a or b #Use this to switch to the inactive slot - if current slot is A, set to B or vice versa.
fastboot getvar current-slot
fastboot getvar version-bootloader
fastboot --set-active=b or a (set to original slot) #Set active slot back to what it was before. If you started on slot A, make sure you switch back to slot A.
fastboot getvar current-slot
fastboot continue #Commands device to resume boot, same function as selecting "Start" in the bootloader menu.
#So as an example:
fastboot getvar current-sot
>current-slot: a
fastboot getvar version-bootloader
>version-bootloader: slider-1.2-8739948
fastboot --set-active=b
>Setting current slot to 'b'
fastboot getvar version-bootloader
>version-bootloader: slider-1.2-8739948
fastboot --set-active=a
>Setting current slot to 'a'
fastboot continue
I updated with OTA and later sideloaded the update, but my bootloader is unlocked. I'm screwed?
AlphaSteam said:
I updated with OTA and later sideloaded the update, but my bootloader is unlocked. I'm screwed?
Click to expand...
Click to collapse
No. That's is the recommended method according to Google.
"To avoid hitting this state, if you are flashing a Pixel 6, Pixel 6a, or Pixel 6 Pro device with an Android 13 build for the first time, please flash the bootloader partition to the inactive slot after successfully updating and booting into Android 13 at least once. This can be done by following these steps:
Option 1 (recommended): After a successful boot into Android 13 for the first time, sideload the full OTA image corresponding to that build and reboot the device to ensure that both slots have a bootable image."
Can we run A13 system on an A12 bootloader?
Is there any way / anyone / any research on the bootloader code to stop the "fuse" trigger?
Does it break any law in any country that software update secretly activates a hardware trigger that stops the user from using any good old systems?
kylechen said:
Can we run A13 system on an A12 bootloader?
Click to expand...
Click to collapse
Hasn't been tested yet. If you want, you can try by using the same --force argument; just be aware that if it doesn't work, you may need to wipe data.
kylechen said:
Is there any way / anyone / any research on the bootloader code to stop the "fuse" trigger?
Click to expand...
Click to collapse
Don't know, doubt it.
kylechen said:
Does it break any law in any country that software update secretly activates a hardware trigger that stops the user from using any good old systems?
Click to expand...
Click to collapse
This seems like something you could research yourself. I highly doubt it - many OEMs implement some form of anti-rollback on their devices to prevent downgrading to previous firmwares. Samsung is especially notorious for this.
No, and you shouldn't. It has a vulnerability in the Android 12 bootloader.
Android is open source, and that means it is potentially vulnerable to "downgrade attacks." Essentially, an attacker downgrades the software to an older version that has known exploits. This is particularly dangerous in open source software like Android because the act of fixing an exploit reveals it to everyone.
Click to expand...
Click to collapse
I see no reason to downgrade the bootloader, you still can run A12 with the newer bootloader.
Cheers
tom1807 said:
No, and you shouldn't. It has a vulnerability in the Android 12 bootloader.
I see no reason to downgrade the bootloader, you still can run A12 with the newer bootloader.
Cheers
Click to expand...
Click to collapse
Not as a daily driver.
V0latyle said:
Not as a daily driver.
Click to expand...
Click to collapse
Can't comment on this, no idea what would be the side effects.
My active slot is A and has Android 13, I only updated the ootloader to the latest one on slot B but there should be still A12.
Cheers
Tom
tom1807 said:
Can't comment on this, no idea what would be the side effects.
My active slot is A and has Android 13, I only updated the ootloader to the latest one on slot B but there should be still A12.
Cheers
Tom
Click to expand...
Click to collapse
The whole point of this thread is that if only one slot is updated and the device switches/is switched to the Android 12 slot after updating and running Android 13, it will brick.
The side effects of running 12 on the 13 bootloader have been established. See the OP. WebView and DRM Apex constantly crash.
tom1807 said:
Can't comment on this, no idea what would be the side effects.
My active slot is A and has Android 13, I only updated the ootloader to the latest one on slot B but there should be still A12.
Cheers
Tom
Click to expand...
Click to collapse
But if you flash back to A12 using the A13 bootloader you'll have a bunch of apps, webview, browers, etc. crashing.
Which actually makes me wonder about something...
@roirraW "edor" ehT When you were on A12 and flashed the A13 bootloader, did you experience apps crashing or other negative side effects? I don't remember you mentioning so which makes me curious if there is a difference in how well the OS runs when you are on A13 and flash back to A12 with the A13 bootloader vs. being on A12 and flashing the A13 bootloader???
Lughnasadh said:
But if you flash back to A12 using the A13 bootloader you'll have a bunch of apps, webview, browers, etc. crashing.
Which actually makes me wonder about something...
@roirraW "edor" ehT When you were on A12 and flashed the A13 bootloader, did you experience apps crashing or other negative side effects? I don't remember you mentioning so which makes me curious if there is a difference in how well the OS runs when you are on A13 and flash back to A12 with the A13 bootloader vs. being on A12 and flashing the A13 bootloader???
Click to expand...
Click to collapse
I didn't, but I didn't even both trying to launch anything, that I recall. I merely unlocked the phone - I might have swiped right to display "Google Discover" aka whatever it's called now via Nova Companion, and I might've swiped up to check out the app drawer, and swiped down to check out the notifications.
I didn't test texting, chatting, phone calls, web browsing, watching videos, harassing my fellow moderators LOL!, or anything when I had only upgraded the bootloader and still running my original, never upgraded Android 12 (first) July "global" update - 12.1.0 (SQ3A.220705.003, Jul 2022).
roirraW edor ehT said:
harassing my fellow moderators LOL!,
Click to expand...
Click to collapse
Beat you to it bet you won't find the Easter egg
roirraW edor ehT said:
I didn't, but I didn't even both trying to launch anything, that I recall. I merely unlocked the phone - I might have swiped right to display "Google Discover" aka whatever it's called now via Nova Companion, and I might've swiped up to check out the app drawer, and swiped down to check out the notifications.
I didn't test texting, chatting, phone calls, web browsing, watching videos, harassing my fellow moderators LOL!, or anything when I had only upgraded the bootloader and still running my original, never upgraded Android 12 (first) July "global" update - 12.1.0 (SQ3A.220705.003, Jul 2022).
Click to expand...
Click to collapse
Ah, ok. Makes sense now. I had thought you stayed on it for a while and used it. Thanks...
Updating via google pixel flashing website flashes both slots ? Or should i do it manually
Nightf0x_007 said:
Updating via google pixel flashing website flashes both slots ? Or should i do it manually
Click to expand...
Click to collapse
Do you mean Android Flash Tool? If so, no, it doesn't flash to both slots. However, the latest version of the Pixel Flasher does.
Can someone list steps to manually update Google pixel 6?
My phones bootloader is locked.
EDIT : I was just worrying, did manual update VIA sideloading OTA, worked well, now I need to figure out how to update the bootloader.
eagledipesh said:
Can someone list steps to manually update Google pixel 6?
My phones bootloader is locked.
EDIT : I was just worrying, did manual update VIA sideloading OTA, worked well, now I need to figure out how to update the bootloader.
Click to expand...
Click to collapse
Sideload the OTA again. It always installs to the inactive slot.
I've updated by using the factory image (batch-installation), overloaded unblocked.
Can I flash the bootloader to both slots manually again without any issues?
Sui77 said:
I've updated by using the factory image (batch-installation), overloaded unblocked.
Can I flash the bootloader to both slots manually again without any issues?
Click to expand...
Click to collapse
Should be able to, yes.
Thanks for posting this. I manually flashed the OTA update from Google' site and there is no warning listed there (I just double checked to see if it was added since I flashed). I knew you wouldn't be able to roll back to the old bootloader, but I had no idea the recommendation was to flash both bootloaders.
EDIT - actually after looking at the warning on the factory image page (and not seeing it on the OTA image page), I have to wonder if the OTA image flashing process actually flashed both bootloaders. I would think Google would add the same warning to the OTA image site if this was a potential problem.
Hi All,
I am now on the latest India Android 13 Beta that was just released.
Here is how I flashed while keeping root and unlocked bootloader.
Global to Full EU A08 - Install magisk to inactive slot before rebooting
EU A08 to Full India A10 - Install magisk to inactive slot before rebooting
India A10 to Full India latest Android 13 beta(CPH2413_11_C.10) - Install magisk to inactive slot before rebooting
If I didn't goto the EU rom, I would have just went to the latest India and then to the India Android 13 Beta.
After you flash using local storage while booted into your current Android, BEFORE YOU REBOOT, you have to then goto Magisk app and install Magisk to the "Inactive Slot"
I did not need to do a factory reset either. I read somewhere that if you are going to a newer version when flashing cross regions, you won't have to factory reset. I haven't tried flashing the same full version of a different region, but I don't see why I would need a factory reset in that instance either as long as I am doing the "Full". Though that is yet to be determined.
Also you have to always do the "Full" update when you download it from Oneplus Updater app if you have an unlocked bootloader. It's probably also required if you are just going to be jumping around different region roms...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does doing this method keep your data? Even with doing full update from oxygen updater? Thanks in advance! I will keep a backup either way but I'd like to know.
JPower123 said:
Does doing this method keep your data? Even with doing full update from oxygen updater? Thanks in advance! I will keep a backup either way but I'd like to know.
Click to expand...
Click to collapse
Yes, it kept all my data. No need for a factory reset if you follow what I did.
maamdroid said:
Yes, it kept all my data. No need for a factory reset if you follow what I did.
Click to expand...
Click to collapse
Hey, thank you so much for the reply, however it seems I have gotten myself into a pickle lmao... After downloading the indian A10 firmware from oxygen updater, I went into software update in settings and clicked local update etc... It then said extracting for a while, and after that, it simply said install. I clicked on install, and it restarted my phone to proceed with the update, this caused me to lose root. That is fine with me as I can simply root again before updating to A13, however, is there a way to install without rebooting for next time? or do I install magisk to inactive slot before clicking "install" in settings? Other than this the first update went fine, and my data is perfectly intact.
JPower123 said:
Hey, thank you so much for the reply, however it seems I have gotten myself into a pickle lmao... After downloading the indian A10 firmware from oxygen updater, I went into software update in settings and clicked local update etc... It then said extracting for a while, and after that, it simply said install. I clicked on install, and it restarted my phone to proceed with the update, this caused me to lose root. That is fine with me as I can simply root again before updating to A13, however, is there a way to install without rebooting for next time? or do I install magisk to inactive slot before clicking "install" in settings? Other than this the first update went fine, and my data is perfectly intact.
Click to expand...
Click to collapse
I am using one of the apks to do the local install. I did not have local install in my normal settings. As noted in the OnePlus updater app, below are the links. I used the android 12 one below.
This does the install them tells you to reboot. You ignore that and then do the magisk flash before rebooting. I'm surprised you have local install in your normal settings...see my screenshot below for what I am using.
OnePlus:
• https://oxygenos.oneplus.net/OPLocalUpdate_For_Android.apk
• https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
• https://oxygenos.oneplus.net/OnePlus_tools.apk
• https://oxygenos.oneplus.net/English_20220225101104.apk
• https://oxygenos.oneplus.net/outputbTGjgm62UO_20220218143830.apk
maamdroid said:
I am using one of the apks to do the local install. I did not have local install in my normal settings. As noted in the OnePlus updater app, below are the links. I used the android 12 one below.
This does the install them tells you to reboot. You ignore that and then do the magisk flash before rebooting. I'm surprised you have local install in your normal settings...see my screenshot below for what I am using.
OnePlus:
• https://oxygenos.oneplus.net/OPLocalUpdate_For_Android.apk
• https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
• https://oxygenos.oneplus.net/OnePlus_tools.apk
• https://oxygenos.oneplus.net/English_20220225101104.apk
• https://oxygenos.oneplus.net/outputbTGjgm62UO_20220218143830.apk
View attachment 5744509
Click to expand...
Click to collapse
Yeah honestly I was kind of surprised too lmao, Im pretty sure that I screwed up a few months ago when trying different roms and ended back up on Indian oxygenos A08. Then after toggling developer options, local update option was there. Anyways I am on android 13 now and it looks amazing! Thanks so much for the help, and I'll be sure to use these apks in the future.
JPower123 said:
Yeah honestly I was kind of surprised too lmao, Im pretty sure that I screwed up a few months ago when trying different roms and ended back up on Indian oxygenos A08. Then after toggling developer options, local update option was there. Anyways I am on android 13 now and it looks amazing! Thanks so much for the help, and I'll be sure to use these apks in the future.
Click to expand...
Click to collapse
Awesome! Glad to have another person on it. You and me are probably at this moment the only two on it that aren't on an India model!
So far, I'm liking it alot!
maamdroid said:
Awesome! Glad to have another person on it. You and me are probably at this moment the only two on it that aren't on an India model!
So far, I'm liking it alot!
Click to expand...
Click to collapse
Yeah i agree, its super smooth, and there have been few bugs. I do notice that swiping away notifications takes a lot of swipe if that makes sense. Also for future reference, I was able to install magisk by booting from the A0.8 patched image, even though it was for android 12, it worked like a charm (direct install), and I am once again rooted on Android 13!
JPower123 said:
Yeah i agree, its super smooth, and there have been few bugs. I do notice that swiping away notifications takes a lot of swipe if that makes sense. Also for future reference, I was able to install magisk by booting from the A0.8 patched image, even though it was for android 12, it worked like a charm (direct install), and I am once again rooted on Android 13!
Click to expand...
Click to collapse
Nice on the root! Glad that worked fine still.
I haven't noticed any issues with swiping away notifications yet. I'll have to pay closer attention.
The search issue when searching for an app and your search not clearing when you come back is quite annoying.
maamdroid said:
Nice on the root! Glad that worked fine still.
I haven't noticed any issues with swiping away notifications yet. I'll have to pay closer attention.
The search issue when searching for an app and your search not clearing when you come back is quite annoying.
Click to expand...
Click to collapse
Yeah the search issue was really annoying, but you can disable "smart search in app drawer" to go back to old search/fix the bug. Also have you had any issues with fingerprint? I cant tell if it got slower, or if I am just trippen... Also I realized the notifications just need an extra swipe/tap to clear all the way.
JPower123 said:
Yeah the search issue was really annoying, but you can disable "smart search in app drawer" to go back to old search/fix the bug. Also have you had any issues with fingerprint? I cant tell if it got slower, or if I am just trippen... Also I realized the notifications just need an extra swipe/tap to clear all the way.
Click to expand...
Click to collapse
Finger print seems fine for me.
Good call on the search, I have now disabled the smart search.
You're right on the notifications, sometimes it seems to need a little extra. Not always though, so maybe it's certain types of notifications...
OxygenOs13 open beta for eu is now live
does fps drop in pubg fixed ?
abdouyakuzataleb said:
does fps drop in pubg fixed ?
Click to expand...
Click to collapse
When do they exactly drop? I have it installed but I don't ever play it. If you give me more specifics I can let you know how it runs on the 13 beta.
try to play on smooth 60 fps and land on bootcamp sanhok
check if fps drops or stable 6
abdouyakuzataleb said:
try to play on smooth 60 fps and land on bootcamp sanhok
check if fps drops or stable 6
Click to expand...
Click to collapse
Hey sorry. I already flashed back to EU android 12 A08 now.
i did qntutu with and without performance mode