Hi to all,
Android 10 Final is now available (for Pixel phones)
https://developers.google.com/android/images#blueline
JC
0.19 and 0.20... what's the difference ?
is there a difference between the two versions? I'm guessing verizon vs non-verizon like a lot of the other ones, but which is which?
Looks like there are 2 versions. For a new version is the side load OTA technique still how it is done ? This would be the first time I would be loading a new version on Android non OTA/locked bootloader.
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
Based on previous versions of android, the specific ones are typically the secondary versions and the standard unlock are the first copy. Edit: see below comments.
My Pixel 3 on Fi is updating now. I'll come back and edit this post to let you all know which sub-version gets installed.
Edit:
So Google P3 on Fi pulled the .019 version. Hope that helps.
mikeprius said:
Looks like there are 2 versions. For a new version is the side load OTA technique still how it is done ? This would be the first time I would be loading a new version on Android non OTA/locked bootloader.
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
Based on previous versions of android, the specific ones are typically the secondary versions and the standard unlock are the first copy. So probably the .019 is the one for everyone and the 0.20 is the version for Verizon.
Click to expand...
Click to collapse
i've sideloaded the newest of the 2 versions to my non verizon phone and it worked fine- only "issue" - i can see the build number at to top bar when i pull it down. Thats strange
robjective said:
My Pixel 3 on Fi is updating now. I'll come back and edit this post to let you all know which sub-version gets installed.
Click to expand...
Click to collapse
I'm on the P3 with Verizon but Google device. Updating now as well 1337.4 Mb d/l.
just wanted to sideload the other version but its getting canceled imediatelly ....
OTA
Just finished installing the OTA update and for my factory unlocked (non Verizon) pixel 3 its .20
Installed 10 on my wife's P3 (my 3 XL is on Havoc OS, and I am not ready for a factory reset) using flash-all (without -w). Root went fine. Had to put AdAway into systemless, but otherwise no real issues yet. I did notice during the flash that it beings up a screen that looks like it is going to fail and force you into recovery (and ultimately a factory reset), but it just kept chugging along in command prompt and rebooted like that screen was meant to be. Only thing post install that is odd is that clearing recent apps (half flip up and swipe to the right and clear all) leaves a shell of the app that says it is not available if you click on it and goes away completely with a lock and unlock.
Just updated to 10 with flash-all and without -w. Procedure worked fine. This is my first experience with 10. And honestly Google like wtf, these gestures are horrible, unbelievable. How is it possible Apple does this million times better. So back on the good old 3 button layout.
Another thing: 10 feels even more laggy on the P3 than Pie. Anybody else experiencing this? Maybe I should try a new clean install... I am a die-hard Android fan but the experience on the 3 besides taking pictures with the great camera has just been disappointing from day 1 until now. Problem is, I don't see an alternative that keeps this form factor... The 7 pro is just to big.
Just Ota. Mine says 0.19
Bought from Google store unlocked
Force 2D GPU rendering
Force 2D GPU acceleration is gone from developer options. On .20 OTA. But there is now a game driver preferences menu.
...
Cris7ianO said:
Just updated to 10 with flash-all and without -w. Procedure worked fine. This is my first experience with 10. And honestly Google like wtf, these gestures are horrible, unbelievable. How is it possible Apple does this million times better. So back on the good old 3 button layout.
Another thing: 10 feels even more laggy on the P3 than Pie. Anybody else experiencing this? Maybe I should try a new clean install... I am a die-hard Android fan but the experience on the 3 besides taking pictures with the great camera has just been disappointing from day 1 until now. Problem is, I don't see an alternative that keeps this form factor... The 7 pro is just to big.
Click to expand...
Click to collapse
Sweet! Just to make it crystal clear, you say this procedure works (credits to xda member Phil_Chambers) : (with magisk canary for now, I guess)
1-Download the 9.0.0 (PQ1A.181205.006, Dec 2018) file from https://developers.google.com/android/images
2-Unzip the contents of the zip into your ADB/Fasboot folder (I just leave my ADB folder on the desktop, windows 7). This is assuming you downloaded ADB/Fastboot program for Windows.
3-Right click and open the flash-all.bat file with a free program called Notepad++ and remove the last part of the text that says "-w" and SAVE FILE.
4-Remove the Edge sense module from Magisk on your phone if installed.
5-Make sure the phone has USB debugging enabled and USB cable plugged in with FILE TRANSFER mode turned on.
6-Run command in ADB/Fastboot:
adb reboot bootloader
click on adb flash-all.bat [now that its modified with -w removed. If -w was not removed, the phone will be WIPED CLEAN!]
(phone will restart) Go back into ADB/Fasboot:
adb reboot bootloader
adb fastboot boot <insert_name_of_TWRP_image_here>.img
7-Once in TWRP, FLASH your TWRP.ZIP and restart into Recovery.
8-Flash Magisk, other stuff etc at this point.
There is no need to remove Magisk or Unzip the secondary file inside the OTA. I've done it without those steps and nothing was changed.
I did re-install the latest version of Edge sense in Magisk as he put out a new version that works with the latest DEC update.
Click to expand...
Click to collapse
gatharot said:
Sweet! Just to make it crystal clear, you say this procedure works (credits to xda member Phil_Chambers) : (with magisk canary for now, I guess)
Click to expand...
Click to collapse
Yes, can confirm. Worked for me. As I am not pleased with the performance I will do a clean one just to be sure.
Cris7ianO said:
Just updated to 10 with flash-all and without -w. Procedure worked fine. This is my first experience with 10. And honestly Google like wtf, these gestures are horrible, unbelievable. How is it possible Apple does this million times better. So back on the good old 3 button layout.
Another thing: 10 feels even more laggy on the P3 than Pie. Anybody else experiencing this? Maybe I should try a new clean install... I am a die-hard Android fan but the experience on the 3 besides taking pictures with the great camera has just been disappointing from day 1 until now. Problem is, I don't see an alternative that keeps this form factor... The 7 pro is just to big.
Click to expand...
Click to collapse
I did a clean install with the factory ota images on a brand new P3. Super smooth! Plus, there's an option in 10 to go back to two- or three-button navigation instead of gestures
Been using for 24 hrs. The gestures are a bit choppy. Also it will not work with 3rd party launchers for the time being which sucks. The gestures don't really feel that smooth. When I use the back gesture and side menu they can get mixed up at times.
Bingley said:
I did a clean install with the factory ota images on a brand new P3. Super smooth! Plus, there's an option in 10 to go back to two- or three-button navigation instead of gestures
Click to expand...
Click to collapse
The 3 button navigation under accessibility options removes the ability for screen rotation by button
I just tried using flash.bat from the factory image (after removing the "-w") and now my phone is stuck in a bootloop....what on earth. I updated to the newest version every single time using that method but now it's screwed up....
For reference, previously the only thing I did was root with Magisk using TEMPORARY TWRP with Adaway. Nothing else. I have no idea why it isn't working. May need to go back to the August update...
Now it's saying in fastboot mode "no valid slot to boot". In terms of SDK Platform Tools, I'm using the newest ones that were from July 2019 (got it straight from their site yesterday).
EDIT: Flashed the August update back on my phone. Gonna stick with that for now since it's working fine anyways. Not in a rush to update to Android 10 or in general anyways.
Related
[Dead Thread about Preview]
See this thread for discussing rooting 7.1.1 : -
Root Android Nougat 7.1.1 -- [NMF26F] -- SuperSU v2.78 SR5
Factory Image!
Successfully used flashfire to flash above factory image, along with SuperSU v2.78 SR4 ( instead of everroot) and ElementalX 5.05
Flashed with Flashfire. Root intact. Haven't looked at anything else yet.
Tapatalk on Nexus 9
ritchea said:
Flashed with Flashfire. Root intact. Haven't looked at anything else yet.
Click to expand...
Click to collapse
Did you use everroot option of flashfire? Which is still using su v2.78 SR1? I thought we would have needed SR4 for 7.1.
I need to make some backups and probably will flash this version on Thursday!
Made backups today (23/11) and successfully flash it! OP update with links!
Yes.
Tapatalk on Nexus 9
I flashed it a few minutes ago over stock 7.0 without wiping data and it seems to be the fastes and smoothest experience I ever had with this device. Can't say much more and didn't try to root, but I switched a few times between my two users und it's still fast and smooth. After switching between my users for two times with 7.0 a reboot was much needed! :fingers-crossed:
Mine is stuck at booting animation. No idea why first time this has happened to me before. Or does it just take like 20 minutes on first boot or what?
I flashed it manually through fastboot like normal.
jaju123 said:
Mine is stuck at booting animation. No idea why first time this has happened to me before. Or does it just take like 20 minutes on first boot or what?
I flashed it manually through fastboot like normal.
Click to expand...
Click to collapse
20 minutes is too long. Have you tried to just power off then on? Sometimes, that's all it takes. It's happened to me but not for this flash.
Tapatalk on Nexus 9
seems way faster than 7.0 so far.... I just did a full reset on 7.0 a week ago and experience immediate lag after I installed my apps. I flashed the 7.1 dev image today and went through the same process. So far so good. I'll report back after a couple of weeks of usage.
Did anyone enrolled in the beta program get the OTA yet ?
Previously I got it the same day an announcement was made. Nothing received yet. As a matter of fact, I didn't even receive the November security update this month.. Never rooted, never modified.
Had to post. Clean flashed new preview , temp boot of twrp to flash latest SU (SR4) for root and set up as new device. Best google effort yet! No problems adjusting build prop to enable assistant and both Pixel and Nova Launchers are go as is new systemless option adaway. Couldn't help notice how responsive UI is and chrome is stable for me 4-5 tabs in using sites like fark.com and no/very few redraws after pushing the tablet with moderate demands. Looking forward to the December release, noticed USB charging was still fairly slow still, hopefully the batt life is ok too. Go Google, they might just catch up to Craig's AOSP version/kernel performance if they're not careful !
Completed clean flash this preview
Rootless with supersu 2.78 sr4
Disable some app not use, very smooth
the.teejster said:
Did anyone enrolled in the beta program get the OTA yet ?
Previously I got it the same day an announcement was made. Nothing received yet. As a matter of fact, I didn't even receive the November security update this month.. Never rooted, never modified.
Click to expand...
Click to collapse
Same here. My device is enrolled but no update. I had to manually flash the November update. I did wonder if it was anything to do with flashing custom Roms. I am on full stock Google image but no update yet.
I never flashed a custom rom on my N9 nor has it ever been rooted. Still haven't received Nov update nor the Beta program update.
If you flash a factory image then you are fully stock and you should receive all updates from google.
Gold Ribbed said:
Same here. My device is enrolled but no update. I had to manually flash the November update. I did wonder if it was anything to do with flashing custom Roms. I am on full stock Google image but no update yet.
Click to expand...
Click to collapse
Has anyone received the ota yet? Or is google only doing a factory image this time for some reason?
Just manually flashed the stock preview. Much better than the stock 7.0 which is virtually unusable . This preview is solid and stable..
One of the main benefits of enrolling in the beta program was to be able to get OTA updates and not lose your data. Other devices in the program have received the OTA. Disappointing that the N9 hasn't to this date.
Gold Ribbed said:
Just manually flashed the stock preview. Much better than the stock 7.0 which is virtually unusable . This preview is solid and stable..
Click to expand...
Click to collapse
the.teejster said:
One of the main benefits of enrolling in the beta program was to be able to get OTA updates and not lose your data. Other devices in the program have received the OTA. Disappointing that the N9 hasn't to this date.
Click to expand...
Click to collapse
You can flash factory images without affecting your data partition. It is called "dirty flashing" for a reason.
My device has been through loads of updates, + the previous Preview images, by that method!
Checkout "Flashfire" app!
Flashfire
Click to expand...
Click to collapse
is the most advanced on-device firmware flasher available for rooted Android devices.
Click to expand...
Click to collapse
I realize this is the wrong thread for this discussion but to conclude. I'm not rooted and choose not to go down that path. My last comment still stands.
corkiejp said:
You can flash factory images without affecting your data partition. It is called "dirty flashing" for a reason.
My device has been through loads of updates, + the previous Preview images, by that method!
Checkout "Flashfire" app!
Click to expand...
Click to collapse
the.teejster said:
I realize this is the wrong thread for this discussion but to conclude. I'm not rooted and choose not to go down that path. My last comment still stands.
Click to expand...
Click to collapse
It is also possible to flash factory images with fastboot without wiping data.
Flashfire is just a convenient app for doing it (with needing a computer) for people who are rooted.
I've been waiting for a custom ROM, haven't quite learned to make one myself. I've tried finding a compatible Xposed with no luck. The only things I have been able to do are debloat and add Viper/Dolby sound mods that added volume boosts. Please feel free to add any trials and errors you guys have had trying to mod this phone here.
packydavis said:
I've been waiting for a custom ROM, haven't quite learned to make one myself. I've tried finding a compatible Xposed with no luck. The only things I have been able to do are debloat and add Viper/Dolby sound mods that added volume boosts. Please feel free to add any trials and errors you guys have had trying to mod this phone here.
Click to expand...
Click to collapse
There are plenty of tutorials for making your own rom and kerenel. There are plenty in xda university and an excellent one by my colleague jackeagle, if you want something device specific then it maybe better to add the phone title in your op rather than just adding a tag
Regards
Sawdoctor
LG Aristo
No ROMs, no real mods and the only progress we have towards a kernel is KyleBryant's work delivering us the kernel source itself.
JustLee said:
Dang Any tips for editing the power button on the back of the phone
Click to expand...
Click to collapse
What do you mean by editing the power button? Like how it functions or it's response upon being held down?
Substratum
Hey, just so you guys know, Substratum works once you're rooted. Just go to the Play Store and download the Substratum app along with a theme of your liking. I'll post some screenshots of my Aristo all theme translucent.
mustangtim49 said:
Hey, just so you guys know, Substratum works once you're rooted. Just go to the Play Store and download the Substratum app along with a theme of your liking. I'll post some screenshots of my Aristo all theme translucent.
Click to expand...
Click to collapse
I'd recommend against using it with certain themes.
I ended up breaking my status bar so now when I hit the settings button from the pull down, it activated gps instead.
MODS
Changed BootAnimation .zip to Cyanogenmod version
Added Viper4Divine FX + DivineEQ + Dolby Atmos
Apps Added into system:
AdAway
Camera FV-5
ES File Explorer
EvolveSMS
FlySo
GhostKik
Instagram
Kik
NovaLauncher
PowerManager
Pulsar+
Removed from system:
All LG Home Apps (FIRST replace with Launcher of your choice E.G. Nova or ADW)
Lookout
All Google but Play Store, Play Services, Play Games, Gmail, YouTube, Maps, and Drive.
All LG apps but SmartWorld (yes including Messaging)
And removed more but they were minor and cant remember...
DivineEQ is blank when loaded so far.
ES File Explorer clears its "history" every time i exit the app. But major settings stick.
I know its nothing major. If I knew Android Developing, I would create a custom rom.
https://forum.xda-developers.com/android/development/rom-ipioneer-stock-10i-v1-t3637393
xtremelora said:
https://forum.xda-developers.com/android/development/rom-ipioneer-stock-10i-v1-t3637393
Click to expand...
Click to collapse
Good look, but the is for the lv3. I've already tried and it won't work due to twrp doing a check on model version and build version sadly.
ninjasinabag said:
Good look, but the is for the lv3. I've already tried and it won't work due to twrp doing a check on model version and build version sadly.
Click to expand...
Click to collapse
As I said on the OP of that thread, check the specifications at the end.
Of course, it is for the MetroPCS version, I make it clear where it says:
Carrier: MetroPCS
And I also mention the twrp limitations and the fix.
Besides that, I am going to start building an slim version (very slim) and at the same time if anyone can provide me a T-mobile/Other Carrier Nandroid I can build slim versions of that for you guys.
xtremelora said:
As I said on the OP of that thread, check the specifications at the end.
Of course, it is for the MetroPCS version, I make it clear where it says:
Carrier: MetroPCS
And I also mention the twrp limitations and the fix.
Besides that, I am going to start building an slim version (very slim) and at the same time if anyone can provide me a T-mobile/Other Carrier Nandroid I can build slim versions of that for you guys.
Click to expand...
Click to collapse
Ooh sh#t, my bad homie.
Well now that I've made a fool of myself, I'mma back up and give this a test.
ninjasinabag said:
I'd recommend against using it with certain themes.
I ended up breaking my status bar so now when I hit the settings button from the pull down, it activated gps instead.
Click to expand...
Click to collapse
That's when you boot into recovery and flash the Substratum.rescue zip and all good, plus, you should have a good nandroid to restore also. So nobody should be afraid to use Substratum, it's perfectly safe if you know your back up plans. Anyone has questions, just reply in this thread and I'll do my best to help anyone.
mustangtim49 said:
That's when you boot into recovery and flash the Substratum.rescue zip and all good, plus, you should have a good nandroid to restore also. So nobody should be afraid to use Substratum, it's perfectly safe if you know your back up plans. Anyone has questions, just reply in this thread and I'll do my best to help anyone.
Click to expand...
Click to collapse
Yeah, I already had that panned out. My comment was a simple heads up about one of the possibilities.
snafu
starting over from scratch currently. everything was correct and working when i first rooted and progressively i messed up. i have no idea how it got so bad or why Ive put up with it for weeks now. i have several nandroid back-ups if anyone wants a headache. but i think my problem is deeper than just the ROM.
Laptop recognizes my LGMS210 as a LGMS550 when in recovery. Code 10 -broken drivers.... *re-flashed the recovery from fastboot [ADB version 1.0.32 Revision eac51f2bb6a8-android] and laptop gave me access to internal and SD but only seeing 9.95g available (6g for sys? is that right)
Google play is broke af. Nothing will install (error -504) even after cleaning data/data. data/apps .. even after dalvik/cache wipe.... even after praying. Not even apps Ive never installed before. LG smart world ie themes,fonts,whatever gives install error.
cant even install apks i have on SD (error-package seems corrupt)
Magisk wont update from ver 2.*.* to ver 16. begins to work but alas error -1 ?
I still have root tho lol
no super su present
and i have xposed framework API 26 installed but i think when using magisk and xposed modules this whole cluster nut began.
android Easter egg wont even work. its stuck with a fish selected, cant change the food offering. and NO cat has ever came.
Boot-loops 3-4 times if not shutdown properly... ie rebooter app or terminal reboot. i changed the default MPCS boot animation so i can see if its looping or chooching. gets thermo-nuclear hot and eventually boots after 4-5 minutes.
i'm gonna go ahead and re-flash stock FW.
*on a side note i keep confusing my PC software like fastboot and adb for my gf's galaxy tab A. Caught a security error brick when i accidentally used its fastboot for something like to unlock bootloader.... i have way too many devices being worked on at once. eh, never a dull moment.
₥ike_grips said:
starting over from scratch currently. everything was correct and working when i first rooted and progressively i messed up. i have no idea how it got so bad or why Ive put up with it for weeks now. i have several nandroid back-ups if anyone wants a headache. but i think my problem is deeper than just the ROM.
Laptop recognizes my LGMS210 as a LGMS550 when in recovery. Code 10 -broken drivers.... *re-flashed the recovery from fastboot [ADB version 1.0.32 Revision eac51f2bb6a8-android] and laptop gave me access to internal and SD but only seeing 9.95g available (6g for sys? is that right)
Google play is broke af. Nothing will install (error -504) even after cleaning data/data. data/apps .. even after dalvik/cache wipe.... even after praying. Not even apps Ive never installed before. LG smart world ie themes,fonts,whatever gives install error.
cant even install apks i have on SD (error-package seems corrupt)
Magisk wont update from ver 2.*.* to ver 16. begins to work but alas error -1 ?
I still have root tho lol
no super su present
and i have xposed framework API 26 installed but i think when using magisk and xposed modules this whole cluster nut began.
android Easter egg wont even work. its stuck with a fish selected, cant change the food offering. and NO cat has ever came.
Boot-loops 3-4 times if not shutdown properly... ie rebooter app or terminal reboot. i changed the default MPCS boot animation so i can see if its looping or chooching. gets thermo-nuclear hot and eventually boots after 4-5 minutes.
i'm gonna go ahead and re-flash stock FW.
*on a side note i keep confusing my PC software like fastboot and adb for my gf's galaxy tab A. Caught a security error brick when i accidentally used its fastboot for something like to unlock bootloader.... i have way too many devices being worked on at once. eh, never a dull moment.
Click to expand...
Click to collapse
You're using the wrong recovery if it's still showing the ms550.
Drivers are universal inside of company devices. (LG for LG, Samsung for Samsung) so they don't conflict.
Adb and fastboot are both universal drivers and shouldn't matter for your device. (I'm using the same fastboot I installed for my Galaxy note 4 that I am for my aristo, my V10, my htc desire 610, and my uncle's v20)
Just do what you said and start fresh.
Unlock the bootloader.
Install the proper twrp and remove encryption.
Flash the stock boot partition and wipe data (this is sneakily pertinent if you're gonna use magisk)
Do not install system mods before using magisk.
After that, use twrp's file explorer to remove and stock apps that you won't need.
https://developers.google.com/android/images
picked it up via OTA. They seem to be doing a better job getting OTAs ready right away. $10 says the screen flash is still there.
It supposedly fixes sound in video recordings, so that will be interesting to see. I don't record much video, but when I do, I want it to sound decent.
I just wish they'd fix the Google Assistant to start responding to the Hey Google hotword again. It's super frustrating when a key feature doesn't work.
PuffDaddy_d said:
I just wish they'd fix the Google Assistant to start responding to the Hey Google hotword again. It's super frustrating when a key feature doesn't work.
Click to expand...
Click to collapse
I use "Hey Google" almost daily. I haven't seen reports of the hot phrase not working. Do many people have this problem?
- Pixel 3XL
Has anyone had any issues with Magisk on this January update? I just updated and tried installing Magisk v18 and started bootlooping. I may try v17.3. Ill report back
EDIT: v17.3 installed just fine
It appears I am $10 rich. I screen flash still there.
No worries. Just wait till the February update boys.
JJT211 said:
Has anyone had any issues with Magisk on this January update? I just updated and tried installing Magisk v18 and started bootlooping. I may try v17.3. Ill report back
EDIT: v17.3 installed just fine
Click to expand...
Click to collapse
Installed v18 on both a P3 and P3XL (from the TWRP .img). No problem with either.
l2tp bug is also still present! wtf Google. fix this!
sliding_billy said:
Installed v18 on both a P3 and P3XL (from the TWRP .img). No problem with either.
Click to expand...
Click to collapse
What was your process?
acidspider said:
What was your process?
Click to expand...
Click to collapse
1. Magisk saved to the phone (Just to be sure, I would confirm you have the one that Topjohn posted with the same version very shortly after originally posting V18 originally since there was an issue installing kernels after his 1st V18. The one on the main Magisk thread is the right/current one)
2. flash-all (without -w)
3. Once system boots back up, shut down, boot back to fastboot with key combo (I do all of my boots to fastboot from full shutdown and with key combo not ADB) and fastboot boot the current (different versions for my two phones) TWRP .img
4. Install Magisk V18
5. Reboot system from TWRP
6. Verify root and SafetyNet
7. Install ElementalX from EX application
8. After kernel forces reboot, just normal maintenance stuff like definitions for AdAway, checking modules, reinstalling BusyBox, installing native tethering prop
mikeprius said:
It appears I am $10 rich. I screen flash still there.
No worries. Just wait till the February update boys.
Click to expand...
Click to collapse
It's probably at the bottom of Google's list of priorities. It is hard to replicate, occurs rarely, and doesn't affect performance in any way. I wouldn't hold my breath waiting for a fix any time soon.
Installed v18 on both a P3 and P3XL (from the TWRP .img). No problem with either.
Click to expand...
Click to collapse
Yea I just installed v17.3 and upgraded to v18 through manager. Weird, must've been a bad download.
JJT211 said:
Has anyone had any issues with Magisk on this January update? I just updated and tried installing Magisk v18 and started bootlooping. I may try v17.3. Ill report back
EDIT: v17.3 installed just fine
Click to expand...
Click to collapse
I'm on canary 18.1 and it installed just fine.
I have been using the flash-all ( without -w) each month since I got the phone. I just installed the Jan update. However, the "Security patch level: September 5, 2018" still shows. Are you guys getting this too?
SmokinCharger said:
I have been using the flash-all ( without -w) each month since I got the phone. I just installed the Jan update. However, the "Security patch level: September 5, 2018" still shows. Are you guys getting this too?
Click to expand...
Click to collapse
It should say Jan 5. Something went wrong, redo it and make sure you redownload the Jan update. Feels like maybe you didn't clean up or grabbed the wrong image.
Strangely, since January update,I try to modify my host file again but it stay there only for a few minutes and get erase back to the original... Anybody know why?
Why does it matter if you reboot-bootloader or using the "key combo"? It shouldn't matter.
ShadowJP88 said:
Strangely, since January update,I try to modify my host file again but it stay there only for a few minutes and get erase back to the original... Anybody know why?
Click to expand...
Click to collapse
It seems like system write privileges aren't sticking with the January update. Check my magisk thread below for updates.
https://forum.xda-developers.com/pixel-3/how-to/magisk-pixel-3-t3853445
Cares said:
Why does it matter if you reboot-bootloader or using the "key combo"? It shouldn't matter.
Click to expand...
Click to collapse
I don't know, but I know there was some wonky behavior in TWRP a couple of months ago that only showed if you used ADB reboot or TWRP reboot. My only guess is that something gets cleared from memory during a full power down and that it simply looks like the difference is in the electronic vs. key combo method when it is actually in the power down function.
I think you are right. I talked about this on another thread because I have placed a LatineIME folder in my system/app folder, changed permissions, rebooted and used AOSP keyboard fine with every other update until Jan. Now, I place the folder in my system/app, change permissions, reboot and it is gone. I have tested this on three different phones, og pixel, Pixel 3, and Moto G5 Plus running custom Pie rom with Jan update. All three have the same problem.
PuffDaddy_d said:
It seems like system write privileges aren't sticking with the January update. Check my magisk thread below for updates.
https://forum.xda-developers.com/pixel-3/how-to/magisk-pixel-3-t3853445
Click to expand...
Click to collapse
TESTED IN INDIAN AND BRAZILIAN DEVICES
https://motoota.lolinet.com/index.p...&carrier=retbr&sn=SERIAL_NUMBER_NOT_AVAILABLE
FOR MEXICAN USERS
https://motoota.lolinet.com/index.p...&carrier=amxmx&sn=SERIAL_NUMBER_NOT_AVAILABLE
Pre-requisites:
1. Battery 50+%
2. Locked bootloader
How to install ?
Step 1: Place the downloaded zip in internal storage and rename it.
( Indian / Brazilian: Blur_Version.29.11.30.albus.retail.en.US.zip or Mexican: Blur_Version.29.11.31.albus.retail.en.US.zip)
Step 2: Go to settings -> apps -> show system apps
and then give storage permission for Motorola update services.
Step 3: Reboot the phone and then check for update in settings app.
#Youtube video tutorial by Rocha Tech
https://youtu.be/xJO31p4GLmU
(Just watch the video without sound if you understand the language )
#FAQ
1. What about my data after i install this update?
Ans: Your data is safe after installing the update. For more safety, you can backup your data as an additional safety measure.
2. Will this work on my bootloader unlocked device ?
Ans: No, it will not work with bootloader unlocked. You need to flash the Oreo stock rom to be able to flash this on your device.
3. Why my country name is not mentioned for updates ?
Ans: You may try Indian update zip file and if it doesn't work then try the Mexican one.
Credits:
Helton Vezzoni @erfanoabdi
Any info about the build, software channel, etc?
XBrav said:
Any info about the build, software channel, etc?
Click to expand...
Click to collapse
Load it up and tell us.
kewlzter said:
Load it up and tell us.
Click to expand...
Click to collapse
Definitely trying. Stock recovery was not spawning ADB, so I'm trying to boot TWRP live. It's been a while, and it's hanging on the TWRP page.
XBrav said:
Definitely trying. Stock recovery was not spawning ADB, so I'm trying to boot TWRP live. It's been a while, and it's hanging on the TWRP page.
Click to expand...
Click to collapse
I tried TWRP (installed) didn't work.
I'll try returning to stock and sideloading tomorrow after work.
Ok, trying the stock way:
1) Reboot into bootloader (Power + Vol Down)
2) Select boot into Recovery.
3) At "No Command" Screen, hold down Power and press Vol Up.
4) Load from SD card, or live dangerously like me and sideload via ADB (Minimal ADB and Fastboot seems to work for me)
Will update once the push is complete.
I just downloaded.
Gave "Motorola Update Services" storage permission.
Copied the file from the computer to the phone's internal storage.
Checked for updates
And voilá, there was the update.
I'm already running Pie.
Up and running here. Didn't like my original image, but after flushing data, it booted fine. It did say I no longer qualify for updates which seems to be a new thing with Motorola and Pie, but common across other devices too. Either way, it all seems to be working.
victorhbm15 said:
I just downloaded.
Gave "Motorola Update Services" storage permission.
Copied the file from the computer to the phone's internal storage.
Checked for updates
And voilá, there was the update.
I'm already running Pie.
Click to expand...
Click to collapse
Did it work really..??
Do we need unlocked bootloader or will it work for all..
Currently running Stock Oreo Firmware locked Bootloader.
Trying to sideload via ADB, will post results after completion of process.
Hello!
Is there an .xml file for this update?
OR
Any proper guide for sideload method?
Thanks
OK! I found a guide for Oreo OTA sideload install.
https://forum.xda-developers.com/z2-play/how-to/official-oreo-z2-play-t3784660
I guess for Pie it is the same.
Tried.
Didn't work.
Can anybody guess what I did wrong?
OldUncle said:
Tried.
Didn't work.
Can anybody guess what I did wrong?
Click to expand...
Click to collapse
Did you follow the steps I posted earlier? What does the phone show for errors?
For those of you who were curious:
1) Software channel remained the same.
2) Dual sim in XT1710-09 seems to be working fine so far (haven't tested a second sim, but the sim statuses are showing for both card slots).
3) No issues with mods so far (Tried the battery pack and gamepad. Hasselblad, projector and speaker are not with me).
4) Build number is PPS29.133-30, Patch Level September 1, 2019.
My phone is in Canada, and the modem patch included works fine as far as I've seen. I haven't fully tested the bluetooth stability yet to see if it's working better than before. Android Auto is working great though.
My smartphone Model name is XT-1710-10, Dual SIM.
I was successfully able to sideload the Update, with the command
"adb sideload Blur_Version.29.11.30.albus.retail.en.US.zip".
It took around 15 to 18 mins for the sideload process to complete, later the phone restarted and showed the usual Moto loading screen for another 12mins or so, for a moment i thought it was stuck, but no, it successfully completed the update process.
Everything is functioning as usual, i noticed that the placement of signal bar, wifi icons, and battery icons on the top right corner of the screen seem to be not proper.
Same is the case with the arrangement of signal and wifi icons on top right portion inside notification drop down menu, seems to be too close to the screen edge.
Additional features I saw after the update are, 3 finger screenshot, Screenshot editor, Media controls provision inside 'Moto Actions'; Attentive display inside 'Moto display'.
Also the addition of "Digital Wellbeing" inside settings Menu.
---------- Post added at 01:33 PM ---------- Previous post was at 01:17 PM ----------
OldUncle said:
Hello!
Is there an .xml file for this update?
OR
Any proper guide for sideload method?
Thanks
OK! I found a guide for Oreo OTA sideload install.
https://forum.xda-developers.com/z2-play/how-to/official-oreo-z2-play-t3784660
I guess for Pie it is the same.
Tried.
Didn't work.
Can anybody guess what I did wrong?
Click to expand...
Click to collapse
It took around 3hrs for me to solve the problem, I am still not clear, what was I doing wrong.
What worked for me somehow was... I properly uninstalled the old ADB installations first vis control panel and then downloaded the latest version of adb i.e adb-setup-1.4.6.exe, and repeated the normal procedure of adb sideload, this time it worked.
I couldn't find an option to enable Android Pie navigation gestures, even in System>Gestures, there is no option.
Do existing TWRP and Magisk root work?
Thanks to everyone who replied with advices :good:
It is my first try to Sidload OTA.
I found out that, I needed the latest OPS27.76-12-25-22/23 stock firmware and I was using OPS27.76-12-25-13.
I fastbooted to the latest but, it didn't work again and I think the reason is that my device is XT1710-11 (Chinese), though I have fastbooted it to RETEU version (Modems preserved) and works fine.
If my guess is correct, that means I need to wait for the fastboot version for Pie
snuk182 said:
Do existing TWRP and Magisk root work?
Click to expand...
Click to collapse
its working great
I get error while sideloading.. i need OPS27.76-12-25-22/23 firmware and I am using OPS27.76-12-42-13/16. On bell canada.
Any advise?
saurav112214 said:
I get error while sideloading.. i need OPS27.76-12-25-22/23 firmware and I am using OPS27.76-12-42-13/16. On bell canada.
Any advise?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/albus/official/
Get the firmware you need from that link and then fastboot flash it to your device.
But make sure if this OTA Pie is for your device.
XBrav said:
Did you follow the steps I posted earlier? What does the phone show for errors?
For those of you who were curious:
1) Software channel remained the same.
2) Dual sim in XT1710-09 seems to be working fine so far (haven't tested a second sim, but the sim statuses are showing for both card slots).
3) No issues with mods so far (Tried the battery pack and gamepad. Hasselblad, projector and speaker are not with me).
4) Build number is PPS29.133-30, Patch Level September 1, 2019.
My phone is in Canada, and the modem patch included works fine as far as I've seen. I haven't fully tested the bluetooth stability yet to see if it's working better than before. Android Auto is working great though.
Click to expand...
Click to collapse
I too have an XT1710-09 (Europe, RETEU software channel). Any idea if this firmware will work for me? Thanks!
Hi
Quite bored of Oneplus updates for my Nord 2 5G that transforms more and more the phone in publicity support for OnePlus CEO messages, and adding features I don't care at all, I'm looking to flash it with an alternative ROM.
What is most stable and operational ROM for that device currently ? The version of the device I have is DN2103 (bought in Switzerland).
Thanks for your advices,
Vincèn
Tried them all. Evolution X is the most often updated and works the best for me.
Hey there!
I also need some much needed insight in how to continue with this device (DN2103 bought in NL, Europe; just updated from 11.A.14 to 11.A.21). I suspect I will probably need the same answer as OP is looking for.
This is my second OnePlus, I was using a OnePlus X before running my first and only ROM, Lineage OS, to be able to move on to Android 10. Then screen broke for the second time after I had already fixed up the whole phone myself before that using brand new parts (Screen, frame, backplate) except for the motherboard still original. So I decided it was time for a new device.
Really love the DN2103 itself, except for the whole rooting / OTA update process, although it was a good training in getting to know all the technicalities. I had been running rooted 11.A.14 since it came out till yesterday, because I was avoiding dealing with the whole process again.
Anyway I kicked myself under my butt and got myself to 11.A.21 now. I was planning to just continue updating OOS till the latest 11.C.10 / 11.C.13, because after all this effort, I'm too curious to not check out the new Android.
But I just happened to read some thread where people were saying that somewhere after 11.C.4 it's not possible anymore to get into fastboot / BROM mode and thus no means to get TWRP?? That sounds horrible, one mistake rooting and it would be a big mess, having to downgrade to OOS 11 again and bla bla bla, why the f...?
So, I just need to hear this from someone, is this correct? I'm too tired to investigate now myself after a 20h OTA/rooting session behind me and just 3h sleep.
And how is everyone dealing with it that wants root? Has everyone moved on to other ROMs for Android 12 / 13, because of this?
In the update process yesterday for some reason my phone did a complete wipe without asking / warning. So I really need to get to a stage in this update process where I can restore all my ****. I've been at this for 24h right now and was happy to do so as I was making steps. but now I suddenly got hit in the face by this news.
tl;dr PLEASE confirm/deny this news (underlined part above) and help me decide if the only comfortable way is to ditch OOS for a custom ROM to get Android 12 / 13 with root & TWRP. I've thrown 24 hours into OTA updating OOS 11, now got to 11.A.21, but phone somehow got wiped in process, so now I really need to finish upgrading and restore data, because I'm without all the apps / accounts etc. I depend on for daily life.
I do really enjoy the road but now I HATE being lost along the way. Show me the light and, if ROM, same question as OP
Sorry if a bit off-topic + long post...
Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.
wuttehhell said:
Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.
Click to expand...
Click to collapse
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.
Btw, u dont need root to change rom, only if you want. I personally dont use root and works great.
wuttehhell said:
Tried them all. Evolution X is the most often updated and works the best for me.
Click to expand...
Click to collapse
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/
wuttehhell said:
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.
Click to expand...
Click to collapse
Thanks a lot for confirming! I'd already read the thread and indeed Evolution looks like the best option, so that's decided then. Wish me luck flashing the ROM
And about root, I really have some essential mods that need root. For example Advanced Charge Controller (I use it with the GUI app ACCA for convenience, else it's only terminal). I limit my charging by default to 80%, which translates in about a 4x increase in lifetime of the battery. On normal days I don't need any more than that, and it always has the option to charge to 100% if you know you're gonna have a long day without charging capabilities.
vincebay said:
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/
Click to expand...
Click to collapse
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!
Releece said:
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!
Click to expand...
Click to collapse
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks
vincebay said:
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks
Click to expand...
Click to collapse
Yep that should do it, looks like you did your research and understand the process.
I had the same question earlier. Strangely I found that the Nord 2 does not have A / B partitioning. I can only detect an A-partition with apps designed to test it. I didn't have to do anything extra / another way while rooting with Magisk, OTA updates or flashing ROM. I thought A/B was enforced on all phones since Android 10 or sth, but apparently not all.
I would add one extra step, after you reboot into TWRP (before flashing the ROM) make a backup of all the individual partitions one by one (so you can restore any single partition in the future), even the tiniest ones.
Some contain calibration data for e.g. Bluetooth and fingerprint sensor that are specific to your device. Now this whole process should leave them untouched, but if anything ever happens to them, the only way to get your phone working again is to send your phone to a service centre, so it's a good idea to have everything backed up.
They will be stored in the TWRP folder in /sdcard/, which is the folder you can see on your PC. So after backing them all up, you can just copy them to your PC.
I successfully flashed Evolution yesterday, and all went well Initially the new Android 13 UI was a bit of a shock from what I was used to, but I'm starting to like it already, especially after going over the settings. And it works smooooth like butter. The only thing that annoyed me was the haptic feedback, which feels very mushy instead of snappy. But putting vibration strength to low helps a lot. Maybe I can find a way to modify it later.
I had one little hickup: Evolution install instructions say this for TWRP before flashing ROM:
"3. Tap [Wipe] , then [Format data]. type "yes" and Enter"
But when I did this, it removed the media folder at /data/media/ instead of just emptying it. I remember it gave me a pop-up saying something like, for /data/media/ to get populated I would probably need to boot to system. But if I would've done that stock would overwrite recovery.
I don't have a lot of knowledge about this, but this folder gets mounted to /sdcard/ and is where your internal storage is mounted to. So after the wipe I wanted to copy the ROM .zip to my phone using the file manager. Windows did recognize my phone as having internal storage, and I could open it, but it didn't see any file/folder/free space and I couldn't copy anything to it.
I solved it by renaming ROM to sth simple like evolution.zip, placing it inside platform-tools folder, and then using ADB push command, so it looked like:
ADB push C:/platform-tools/evolution.zip /data/
It doesn't give any feedback while copying and I didn't even see much disk usage on Windows task manager, so I was about to get nervous and close the terminal, but then it suddenly completed successfully and I could see the evolution.zip in TWRP file manager. After that flashing took just a few minutes and everything went perfect.
Now I don't know if it's maybe a typo in the instructions or if TWRP had a bug, but I don't think so as it specifically gave me a prompt about it. I think it's better to just tap [Wipe] and then do the usual factory reset slider, with data, dalvik and cache selected. Think I'll make a post later in the Evolution thread to ask.
Good luck!
Hi, I don´t like the colors on Oxygen OS. I don't know if it's cause by our screen or is something related with the ROM. In Samsung or Xiaomi colors are more brilliant and saturated. In Evolution ROM, can you modify this issue?
So I have been able to dowgrade my DN2103 to 11_A20 running Android 11 but I'm stuck there !
Each time I try to flash twrp or load it in device I get that:
[email protected]:~/Bureau$ fastboot boot twrp.img
Sending 'boot.img' (131072 KB) OKAY [ 3.310s]
Booting FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
[email protected]:~/Bureau$ fastboot flash recovery twrp.img
Sending 'recovery' (131072 KB) OKAY [ 3.371s]
Writing 'recovery' FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
I have unlocked OEM protection into it and allow USB debug. Any ideas what's the problem ?
damn was a long time I had not done Android flashing so was a little more complicated but made it (well it looks to be so far Will see if it boots after initial setup and now hanging on the Phone initial preparation but should go very soon I think
Thanks