Related
Hey everyone, been a little while, but 7.1.1 N is rolling out to you guys.
Awesome! Is this the same 108 build that went out to beta testers?
Does it include the battery optimization that was mentioned some time ago?
***
New update appears to be uncertified and Android Pay doesn't work.... any way to fix this?
ipowyourface said:
New update appears to be uncertified and Android Pay doesn't work.... any way to fix this?
Click to expand...
Click to collapse
Is your bootloader unlocked?
Nextbit_Khang said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No, I relocked it after I flashed the image and turned off the oem unlocking option after. I was previously rooted though, but the script on the image should have taken care of that right?
ipowyourface said:
No, I relocked it after I flashed the image and turned off the oem unlocking option after. I was previously rooted though, but the script on the image should have taken care of that right?
Click to expand...
Click to collapse
Yeah that's kinda weird. It should work. I'll ask around.
Nextbit_Khang said:
Yeah that's kinda weird. It should work. I'll ask around.
Click to expand...
Click to collapse
Yeah, there was another person on the Razer forums who had the same problem as well.
Just got my Nextbit today updated few times before work on 7.0 present and update pending hopefully 7.1.1 , How's the update ? any issues fixed not had it long enough to find any
Sent from my Robin using Tapatalk
Nextbit_Khang said:
Yeah that's kinda weird. It should work. I'll ask around.
Click to expand...
Click to collapse
I figured it out, I had just came from Omni Rom. For some reason, I had to flash the 6.0 image then flash the 7.1.1 image and now everything passes, and AP works.
ipowyourface said:
I figured it out, I had just came from Omni Rom. For some reason, I had to flash the 6.0 image then flash the 7.1.1 image and now everything passes, and AP works.
Click to expand...
Click to collapse
You had to re-lock your bootloader also, correct?
Is anybody having issues with sending text messages (your standard text message) with WiFi on? Not over WiFi, but just with WiFi on. I tried the default messaging app and the Google one. They both work the same. For me to get a text message out, I have to turn off WiFi.
I flashed stock N88 and still have TWRP recovery installed I got a system update that updated now stock on nextbit logo on boot , is this coz I still have TWRP recovery or just bad update would factory reset in TWRP fix ? Thanks
Sent from my MotoG3 using Tapatalk
DoobyDroid said:
I flashed stock N88 and still have TWRP recovery installed I got a system update that updated now stock on nextbit logo on boot , is this coz I still have TWRP recovery or just bad update would factory reset in TWRP fix ? Thanks
Click to expand...
Click to collapse
Why don't you flash the latest factory image?
You can't flash an OTA update via custom recovery.
Loving this new update!
However, if you want to save resources and please your customers at the same time when doing the next update -
skip the nextbit bits.
Just make the next updates (if you plan on making any more of course) stock, for all intents and purposes, except perhaps for the backup/cloud feature.
revert back to 7.0 ?
since i updated to 7.1.1, my pebble 2 would constantly disconnect.
how to revert back to plan 7.0 ?
thanks!
Any word on android 8
Franzferdinan51 said:
Any word on android 8
Click to expand...
Click to collapse
Lmao very doubtful
hey there guys i'm having this weird trouble updating to 7.1.1, i'm currently on 7.0 (Robin_Nougat_88) and i have downloaded the 7.1.1 update (560 mb) and when i hit the "reboot and install" button it say restarting in 10 ... 9... 8 blah blah then rebooting now and never get to reboot... i can't install this update is there some solution? do i have to install the N108 image like new following the razer thread? thanks in advice guys have a good day!
I'm on 8.0 after trying the beta, installing the ota, unenrolling, then wiping and starting afresh with the dev images due to lag.
Apart from battery being crap, it's all ok.
Today I just woke to the same notification for the Oreo update - the whole 987.4mb update. What!
Has anyone else had this? I can't get rid of the notification. I don't especially want to install the update as, while I'm already on it, I assume something will fcuk up and I'll have to spend hrs fixing it.
Bingley said:
I'm on 8.0 after trying the beta, installing the ota, unenrolling, then wiping and starting afresh with the dev images due to lag.
Apart from battery being crap, it's all ok.
Today I just woke to the same notification for the Oreo update - the whole 987.4mb update. What!
Has anyone else had this? I can't get rid of the notification. I don't especially want to install the update as, while I'm already on it, I assume something will fcuk up and I'll have to spend hrs fixing it.
Click to expand...
Click to collapse
I had same update for the same reason. After the update I have different build number OPR4.170623.006 with September 5 patch. So this is the latest build.
Mines telling me to update again as well.
So I updated and it came back with verification error.
Im on the 8.0.0 (OPR6.170623.013, Aug 2017) version
Trying a 2nd time but not sure if it will work.
Edit: Ok, turns out im getting this error
@/cache/recovery/block.map error: 7
Which appears to mean my device isnt in a stock state.
Will wait to see if a new update comes or if anyone else on the OPR6 version updates.
odunke01 said:
Mines telling me to update again as well.
So I updated and it came back with verification error.
Im on the 8.0.0 (OPR6.170623.013, Aug 2017) version
Trying a 2nd time but not sure if it will work.
Edit: Ok, turns out im getting this error
@/cache/recovery/block.map error: 7
Which appears to mean my device isnt in a stock state.
Will wait to see if a new update comes or if anyone else on the OPR6 version updates.
Click to expand...
Click to collapse
if you have TWRP than you have to go back to stock recovery, otherwise it will not update, unless someone creates a .zip for TWRP
I received too the update. Updated over August's Security Update (OREO). Huge update. Maybe lot of bug fixes!
odunke01 said:
Mines telling me to update again as well.
So I updated and it came back with verification error.
Im on the 8.0.0 (OPR6.170623.013, Aug 2017) version
Trying a 2nd time but not sure if it will work.
Edit: Ok, turns out im getting this error
@/cache/recovery/block.map error: 7
Which appears to mean my device isnt in a stock state.
Will wait to see if a new update comes or if anyone else on the OPR6 version updates.
Click to expand...
Click to collapse
I had OPR6 build and now after the update I am on OPR4 build with latest security patch (September 5).
I need help, please...My phone has a problem after updating Android 10....The problem is،،memory leak in android 10....My phone type is..xiaomi mi a2 lite.....It is part of the Android one project...It becomes difficult to open applications and it becomes irritating
ahmed elmansy said:
I need help, please...My phone has a problem after updating Android 10....The problem is،،memory leak in android 10....My phone type is..xiaomi mi a2 lite.....It is part of the Android one project...It becomes difficult to open applications and it becomes irritating
Click to expand...
Click to collapse
Update it to the August patch for some people the memory issue is fixed on the latest update
Aadil Gillani said:
Update it to the August patch for some people the memory issue is fixed on the latest update
Click to expand...
Click to collapse
It was updated in August and the problem is still there
ahmed elmansy said:
I need help, please...My phone has a problem after updating Android 10....The problem is،،memory leak in android 10....My phone type is..xiaomi mi a2 lite.....It is part of the Android one project...It becomes difficult to open applications and it becomes irritating
Click to expand...
Click to collapse
Flash both A and B slots with known good builds of the A10 system like 11.0.7 or 11.0.9.
Download the .zip file from the Xiaomi servers, copy to SD card.
Go to Recovery and flash update from SD card, reboot.
Wait 10-15 minutes after boot to complete the process.
Shut down, go back into recovery and flash again.
Reboot, update to August via OTA.
This worked for me, at least, the device is snappy and nice, also no data was lost.
But already updating to August may not allow you to flash older versions, and August update is not an .zip yet, so you might have to wait until september until you can try this method.
TeoXSD said:
Flash both A and B slots with known good builds of the A10 system like 11.0.7 or 11.0.9.
Download the .zip file from the Xiaomi servers, copy to SD card.
Go to Recovery and flash update from SD card, reboot.
Wait 10-15 minutes after boot to complete the process.
Shut down, go back into recovery and flash again.
Reboot, update to August via OTA.
This worked for me, at least, the device is snappy and nice, also no data was lost.
But already updating to August may not allow you to flash older versions, and August update is not an .zip yet, so you might have to wait until september until you can try this method.
Click to expand...
Click to collapse
https://bigota.d.miui.com/V11.0.10.0.QDLMIXM/miui_DAISYGlobal_V11.0.10.0.QDLMIXM_55c39d9793_10.0.zip
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
TeoXSD said:
Flash both A and B slots with known good builds of the A10 system like 11.0.7 or 11.0.9.
Download the .zip file from the Xiaomi servers, copy to SD card.
Go to Recovery and flash update from SD card, reboot.
Wait 10-15 minutes after boot to complete the process.
Shut down, go back into recovery and flash again.
Reboot, update to August via OTA.
This worked for me, at least, the device is snappy and nice, also no data was lost.
But already updating to August may not allow you to flash older versions, and August update is not an .zip yet, so you might have to wait until september until you can try this method.
Click to expand...
Click to collapse
Ok so I get what you are trying to say if one of the slot has the dirty update then the phone is bugged but I have a question if there are two good updates via OTA update doesn't the previous two builds get erased which means there are two good updates in the slots now.
Aadil Gillani said:
https://bigota.d.miui.com/V11.0.10.0.QDLMIXM/miui_DAISYGlobal_V11.0.10.0.QDLMIXM_55c39d9793_10.0.zip
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
Ok so I get what you are trying to say if one of the slot has the dirty update then the phone is bugged but I have a question if there are two good updates via OTA update doesn't the previous two builds get erased which means there are two good updates in the slots now.
Click to expand...
Click to collapse
To be honest, while it may not make much sense, it's what I get. Also from what I read from the android documentation, the new update system just applies a patch, doesn't fully rewrite, so 2 consecutive updates on the same slot just mean you're getting the new patched files from Xiaomi, not a full overwrite. That's exactly what I wrote here in more detail.
TeoXSD said:
from what I read from the android documentation, the new update system just applies a patch, doesn't fully rewrite
Click to expand...
Click to collapse
Yes, but only if the original is unmodified. That's why people run into "can't update" states.
There is no difference between a patch update and complete update. The end result has the same hash.
a1291762 said:
Yes, but only if the original is unmodified. That's why people run into "can't update" states.
There is no difference between a patch update and complete update. The end result has the same hash.
Click to expand...
Click to collapse
But Teo is saying that for him the update is snappier and better I don't know is it because he just flash the new ROM due to which there are less apps installed and you haven't used the mobile for a while while others have used for a longer time due to which they are facing the RAM management issues or is it because of the way he flash the ROM.
Aadil Gillani said:
But Teo is saying that for him the update is snappier and better I don't know is it because he just flash the new ROM due to which there are less apps installed and you haven't used the mobile for a while while others have used for a longer time due to which they are facing the RAM management issues or is it because of the way he flash the ROM.
Click to expand...
Click to collapse
August update may be better. I'd love it to be so but with only 16 hours runtime, I feel it's too early to celebrate.
How you get it installed does not matter because patch and full write gives you the same data in the end.
A clean install (wipe data) obviously makes a difference.
Some people have tolerated Android 10 better than others. I reboot weekly and I'm fine. Some people can't last a day.
I am on 11.2.4.4 (AA) and after reading about the success others were having I decided to take an incremental update, which shows up as 11.2.6.6 (unlocked/verizon). I followed the instructions found in many places, which consisted of restoring image in magisk, taking the incremental update, when finished I did not reboot, and then installed magisk to inactive slot. upon reboot my system still shows 11.2.4.4, and in the system update page it is still asking me to reboot, as if I needed to hit the system restart button in system update, which is very odd. also, I was running omega kernel, and after installing the update the kernel is back to stock, but for some reason the system has not updated and is still stuck on 11.2.4.4, and still has system reboot button on update setting screen. has anyone ran into this issue, and does anyone know how I should proceed? I am afraid if I hit reboot on the update setting screen that I will have some issue. I have also rebooted multiple times, yet the system has not updated. any help with this issue will be greatly appreciated!
When rooted you need the full update, not an incremental
You need to install 11.2.4.4 full update again in local update then the incremental will install
ryantf420 said:
You need to install 11.2.4.4 full update again in local update then the incremental will install
Click to expand...
Click to collapse
I've never heard of this method, where did you do this yourself and it worked? reinstalling a full update via local update actually forced your incremental update to take? also, how would this work when I would be installing things to different slots?
avid_droid said:
Yeah that don't work. Didn't reinstall but I wiped and tried again. Still failed. Even edited craznazn package to fix model number and still that didn't work. Back to BA and have no issues updating
Click to expand...
Click to collapse
so you are basically in the same boat as me? an incremental update is not taking? yeah thanks for reporting that, I was skeptical about that method, but I'm thinking I'll try it anyway. if not, guess I'll have to wait until AA releases a full update other than 11.2.4.4
thirtythr33 said:
so you are basically in the same boat as me? an incremental update is not taking? yeah thanks for reporting that, I was skeptical about that method, but I'm thinking I'll try it anyway. if not, guess I'll have to wait until AA releases a full update other than 11.2.4.4
Click to expand...
Click to collapse
Maybe you can download the full version of the 11 .2.4.4 from here and start over. The custom kernel combined with root may have messed it up. Happy modding!
Edit: only take full updates when rooted.
Nathan.7118391 said:
Maybe you can download the full version of the 11 .2.4.4 from here and start over. The custom kernel combined with root may have messed it up. Happy modding!
Edit: only take full updates when rooted.
Click to expand...
Click to collapse
I know the thing is up until this point I've always went for full os updates, never incremental, but after reading many posts about other members taking incremental updates successfully, (restore images in magisk - take update - don't reboot - then install magisk to inactive slot) I decided to try it myself, and I should have never bothered. I'll just wait until a new full update comes out for AA and never bother with incremental again. thing is I followed instructions to the T, yet it didn't work, so I don't know how others have been successful with this.
avid_droid said:
Yeah that don't work. Didn't reinstall but I wiped and tried again. Still failed. Even edited craznazn package to fix model number and still that didn't work. Back to BA and have no issues updating
Click to expand...
Click to collapse
Yeah it does work
Or I wouldn't have gave advice
ota 11.2.4.4 twice, and 11.2.7.7 will install....
ryantf420 said:
Yeah it does work
Or I wouldn't have gave advice
ota 11.2.4.4 twice, and 11.2.7.7 will install....
Click to expand...
Click to collapse
so since the incremental update I tried to apply is somehow "stuck" you are saying to local update 11.2.4.4 and then upon reboot 11.2.6.6 will be installed? and are you saying to ota 11.2.4.4 twice because of the slot I am on and would need to get back to that slot for the incremental update to apply? I am willing to try this but I've never heard of it, but hey if it works man then I am grateful
avid_droid said:
Don't get your panties in a bunch with that mad face haha. Just found it odd. I also wasn't rooted for the other gentlemen who said about root.was completely unrooted and fresh system update from BA to AA. Since there isn't a huge difference between 11.2.7.7 and 11.2.6.6 I'll just wait it out. Thanks guys
Click to expand...
Click to collapse
all good hdr is add to video but that's basically it. but method does work, did it on both my 9pro's
Hi, I just wanted to add that on the AA version(unlocked US version from OnePlus) the boot image have to match for the inc to install. Also I'm using props hide module and to manually select the OTA this has to be disabled (reverted). I ran into some issues at first but hopefully have it figured out.
So I decided to go to the EU version of the OS.
I did that on my 7 Pro and didn't have any issues.
So I'm on 11.2.6.6, running on Verizon with no issues.
Here is my theory on why people are failing OTA. I think maybe their A and B slots dont have matching content before they OTA. Try using the lineageOS script to duplicate the active to the inactive slots first. I'm curious if that does the trick.
dkcats3 said:
Here is my theory on why people are failing OTA. I think maybe their A and B slots dont have matching content before they OTA. Try using the lineageOS script to duplicate the active to the inactive slots first. I'm curious if that does the trick.
Click to expand...
Click to collapse
yes local update needs to be down twice...
ryantf420 said:
yes local update needs to be down twice...
Click to expand...
Click to collapse
Would I have to wipe everything if I'm already on 6.6?
ryantf420 said:
yes local update needs to be down twice...
Click to expand...
Click to collapse
I decided to take your advice bro but I'm getting update installation error. I've tried a few times now and the full 11.2.4.4 I have will not install. so I'm unable to even install the full ota, did this happen to you? thing is the 11.2.6.6 incremental ota that didn't install is no longer in system update, now 11.2.7.7 is, so I don't know what is exactly going on bc my system still reports 11.2.4.4. any help is appreciated
My device is running .036 and about a week ago the system update said there was a download. I am assuming is .037 because that is the only thing it could be...
I try to download it and it fails and it says to try again and it fails, repeat ad nauseum...
Is this ( .037 ) supposed to download ?
Ah snap, is my phone's update software broken ?
I assume this android bug will only go away with a factory reset...
Hmm...
Because fixes are cumulative, should I just wait a little bit and download December's update. I am assuming there will be a software update in December besides the security stuff.
Vote now.
Factory Reset -or- wait
You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip
miravision said:
You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip
Click to expand...
Click to collapse
Ug, ya I know, too many questions... lets try again...
Question: Is the .037 supposed to download ?
Yes
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
miravision said:
Yes
Click to expand...
Click to collapse
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?
NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Cool ! I like that idea. Will the newer update push in front of the glitched update ?
old_fart said:
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?
Click to expand...
Click to collapse
The OTA will not wipe, no flags needed. Only the full image will wipe, unless you use the flag.
I doubt your update system is broke, I suspect you just got a bad download. Next download will be fine I think. So sideload or wait for December.
NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Monthly updates usually occur on the 1st Monday of each month, which would be the 6th for December. Just curious, where did you hear this rumor that they were deviating from this process?
old_fart said:
My device is running .036 and about a week ago the system update said there was a download. I am assuming is
Click to expand...
Click to collapse
To be clear, are you rooted, or at least running a custom kernel? If yes to either one, you shouldn't attempt to take any automatic downloads. At worst they just won't update, such as you found out, or at worst it could break something, although still not catastrophic except maybe losing some data.
So, if you are rooted or at least using a custom kernel, you should turn off automatic updates in the Developer Options. And if you're not rooted and not using a custom kernel, then go with what everyone else said. Now if December's OTA failed to update your phone correctly and you're not rooted or using a custom kernel, then I would consider first just flashing the full factory image (whatever the most up to date at the time will be) while removing the -w (wipe) command from the flashall.bat.
Also, to complicate this reply even further, whether you're rooted or not, have you /or disabled verity and verification? If so, when you use the flashall.bat, you're going to want to put the disable verity and verification commands in place of the -w wipe command - otherwise you would *have* to wipe any time you go from either enabled to disabled, or from disabled to enabled.
Sorry for any confusion my reply may cause.
Do I need to root my phone before manually updating using the OTA file?
speedyx2000 said:
Do I need to root my phone before manually updating using the OTA file?
Click to expand...
Click to collapse
No
Lughnasadh said:
No
Click to expand...
Click to collapse
Thank you for your quick answer!
I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers
virtyx said:
I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers
Click to expand...
Click to collapse
It was America only apparently. Everyone else will get it in December as normal
From Orange France is 036, from Google store is 037
Fingerprint improvement patch was U.S. and Japan only, if you really want it sideload it, it works perfectly fine