My Nexus 6P is rooted and running Android Marshmallow (6.0.1) (supposed to be systemless but not sure anymore)
I have unlocked the bootloader and have twrp as my recovery.
I have exposed framework with some modules installed and working (notification bar clock now shows the seconds and stuff like that....)
So I recently got my Nexus 6p and the first thing I did was root and install twrp via adb and fast boot so I could use exposed framework. I would like to know what my options are in receiving ota updates? I have the Android security patch from January 1, 2016 and I just got an Android system update notification that includes a newer security patch from February and I'm not sure if I can get a specific ota that is flashable through twrp or if I'll need to back up my stuff and flash stock or if there's an easier way to do this because I'd prefer to not have to set up everything all over again.
If you need me to provide any further information about my device just tell me.
---
I'm currently on build MMB29P and I have checked the Google dev page on Factory Images for Nexus Devices
And apparently MHC19I is the newest.
use flashfire
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
fireeyeeian said:
My Nexus 6P is rooted and running Android Marshmallow (6.0.1) (supposed to be systemless but not sure anymore)
I have unlocked the bootloader and have twrp as my recovery.
I have exposed framework with some modules installed and working (notification bar clock now shows the seconds and stuff like that....)
So I recently got my Nexus 6p and the first thing I did was root and install twrp via adb and fast boot so I could use exposed framework. I would like to know what my options are in receiving ota updates? I have the Android security patch from January 1, 2016 and I just got an Android system update notification that includes a newer security patch from February and I'm not sure if I can get a specific ota that is flashable through twrp or if I'll need to back up my stuff and flash stock or if there's an easier way to do this because I'd prefer to not have to set up everything all over again.
If you need me to provide any further information about my device just tell me.
---
I'm currently on build MMB29P and I have checked the Google dev page on Factory Images for Nexus Devices
And apparently MHC19I is the newest.
Click to expand...
Click to collapse
I have all the OTA zips listen in my index. As previously mentioned you can use Flashfire to flash them without having to undo your modifications.
But with flashfire you will still lose all of your modifications like xposed apps? You have to redo it all? Anyone have a direct link to the new feb security update?
Heisenberg said:
I have all the OTA zips listen in my index. As previously mentioned you can use Flashfire to flash them without having to undo your modifications.
Click to expand...
Click to collapse
I've used flash fire back on my s4 so this is good but
Should I disable my exposed modules before I flash with flash fire as i can also reinstall exposed along with the ota? It's my First time using exposed because my s4 has a locked bootloader.
squall458 said:
But with flashfire you will still lose all of your modifications like xposed apps? You have to redo it all? Anyone have a direct link to the new feb security update?
Click to expand...
Click to collapse
Downloaded modules should stay intact. However, I am not sure if the OTA update has library changes, that may affect Xposed installation. Anyhow, simply flashing the Xposed Installer zip will suffice.
DJBhardwaj said:
Downloaded modules should stay intact. However, I am not sure if the OTA update has library changes, that may affect Xposed installation. Anyhow, simply flashing the Xposed Installer zip will suffice.
Click to expand...
Click to collapse
Thanked you!
Will the latest google image for the 6p already have the security patch in it? I dont see a changelog or a timestamp so I cant tell if its just the old image.
squall458 said:
Thanked you!
Will the latest google image for the 6p already have the security patch in it? I dont see a changelog or a timestamp so I cant tell if its just the old image.
Click to expand...
Click to collapse
No need to thank, just add this to your knowledge for future reference. That will be more than enough for me.
Which security patch are you talking about, specifically? The latest Google factory image as of now, contains the March security update. You can read a more detailed article here: https://source.android.com/security/bulletin/2016-03-01.html
DJBhardwaj said:
No need to thank, just add this to your knowledge for future reference. That will be more than enough for me.
Which security patch are you talking about, specifically? The latest Google factory image as of now, contains the March security update. You can read a more detailed article here: https://source.android.com/security/bulletin/2016-03-01.html
Click to expand...
Click to collapse
Ok i just used flashfire to update with the image file. Made sure to follow the instructions and even got it to flash xposed for me after.
It all went smoothly. But upon reboot it looked like it was doing an android app update but it stopped and everything seems like it was before. The security update didnt work. Still says january.
squall458 said:
Ok i just used flashfire to update with the image file. Made sure to follow the instructions and even got it to flash xposed for me after.
It all went smoothly. But upon reboot it looked like it was doing an android app update but it stopped and everything seems like it was before. The security update didnt work. Still says january.
Click to expand...
Click to collapse
What did you flash, image files or OTA zip?
DJBhardwaj said:
What did you flash, image files or OTA zip?
Click to expand...
Click to collapse
The system image file. Not the ota one. I got it from the google developer site with my matching build.
squall458 said:
The system image file. Not the ota one. I got it from the google developer site with my matching build.
Click to expand...
Click to collapse
Well then you just flash the system partition only. I would say, flash the OTA zip.
Wait! "with my matching build" ? Which build did you download?
DJBhardwaj said:
Well then you just flash the system partition only. I would say, flash the OTA zip.
Wait! "with my matching build" ? Which build did you download?
Click to expand...
Click to collapse
My build is MMB29P. I got the 6.0.1 matching my build. Did I pick the wrong one?
squall458 said:
My build is MMB29P. I got the 6.0.1 matching my build. Did I pick the wrong one?
Click to expand...
Click to collapse
Yes. You will need to pick MHC19I factory image, and extract the system.img from it. Flash it, and also the vendor.img too.
Every thing worked out I had downloaded the most recent build and exposed installer flashed through flash fire everything seems good so far.
DJBhardwaj said:
Yes. You will need to pick MHC19I factory image, and extract the system.img from it. Flash it, and also the vendor.img too.
Click to expand...
Click to collapse
Ohhh ic! I dont pick my matching build? I just pick the last one which is the latest update?
squall458 said:
Ohhh ic! I dont pick my matching build? I just pick the last one which is the latest update?
Click to expand...
Click to collapse
Picking the current build is simply reflashing it. To update, you will need to flash the system.img from the latest factory image.
---------- Post added at 09:17 PM ---------- Previous post was at 08:59 PM ----------
fireeyeeian said:
Every thing worked out I had downloaded the most recent build and exposed installer flashed through flash fire everything seems good so far.
Click to expand...
Click to collapse
Great.
DJBhardwaj said:
Picking the current build is simply reflashing it. To update, you will need to flash the system.img from the latest factory image.
---------- Post added at 09:17 PM ---------- Previous post was at 08:59 PM ----------
Great.
Click to expand...
Click to collapse
It worked! You are the best. Ppl like you make xda such an awesome forum! Bless you
squall458 said:
It worked! You are the best. Ppl like you make xda such an awesome forum! Bless you
Click to expand...
Click to collapse
People like all of us, you, me, and everyone else, make this a better community. Belonging to different countries and cultures, and we still understand each other very well. :highfive:
Related
Hello,
I've found a link to the supposedly OTA, but it didn't work with the same method for the 5.0.2, I mean copying to the memory of the phone and trying to update from the settings. I don't know if it is really the 5.1 OTA but feel free to give it a try. I've found it on a comment in a brasilian site: http://www.androidpit.com.br/moto-x-android-update. If any of you guys know how to update please let me know.
Link: https://mega.co.nz/#!48E0VZBR!lphA3SijKt1yhbvUGuSi535yXNinoNamFoIw3dDOjtc
pd.: sorry for my bad english, and sorry if I'm not supposed to post links this way.
ECassinelli said:
Hello,
I've found a link to the supposedly OTA, but it didn't work with the same method for the 5.0.2, I mean copying to the memory of the phone and trying to update from the settings. I don't know if it is really the 5.1 OTA but feel free to give it a try. I've found it on a comment in a brasilian site: http://www.androidpit.com.br/moto-x-android-update. If any of you guys know how to update please let me know.
Link: https://mega.co.nz/#!48E0VZBR!lphA3SijKt1yhbvUGuSi535yXNinoNamFoIw3dDOjtc
pd.: sorry for my bad english, and sorry if I'm not supposed to post links this way.
Click to expand...
Click to collapse
Can I use this on my device. I am on us cellular XT1055?
cdiamond said:
Can I use this on my device. I am on us cellular XT1055?
Click to expand...
Click to collapse
I don't know, it is the brazilian firmware so I think it deppends if you have updated the to 5.0.2 brazilian firmware previously.
cdiamond said:
Can I use this on my device. I am on us cellular XT1055?
Click to expand...
Click to collapse
Goto the Confirmed Android 5.1 thread, around page 16, there is a mega link of a nadroid backup of 5.1 Brazil for twrp. Download it, extract it to the TWRP/backup folder, boot to recovery, backup your present ROM. Then restore the downloaded nandroid, wipe data, cache, and davlik cache only, reboot into system, profit. This way gpt and boot partitions remained in touched, and no need to revert to Brazilian KitKat, then to 5.0.2, then to 5.1 painful process.
flipm00de said:
Goto the Confirmed Android 5.1 thread, around page 16, there is a mega link of a nadroid backup of 5.1 Brazil for twrp. Download it, extract it to the TWRP/backup folder, boot to recovery, backup your present ROM. Then restore the downloaded nandroid, wipe data, cache, and davlik cache only, reboot into system, profit. This way gpt and boot partitions remained in touched, and no need to revert to Brazilian KitKat, then to 5.0.2, then to 5.1 painful process.
Click to expand...
Click to collapse
Ok will do thank you
cdiamond said:
Ok will do thank you
Click to expand...
Click to collapse
In running it right now, and it is nice thus far
flipm00de said:
Goto the Confirmed Android 5.1 thread, around page 16, there is a mega link of a nadroid backup of 5.1 Brazil for twrp. Download it, extract it to the TWRP/backup folder, boot to recovery, backup your present ROM. Then restore the downloaded nandroid, wipe data, cache, and davlik cache only, reboot into system, profit. This way gpt and boot partitions remained in touched, and no need to revert to Brazilian KitKat, then to 5.0.2, then to 5.1 painful process.
Click to expand...
Click to collapse
Do you know how can I update without being root? I'm in the brazilian 5.0.2.
flipm00de said:
In running it right now, and it is nice thus far
Click to expand...
Click to collapse
What carrier are u on?
ECassinelli said:
Do you know how can I update without being root? I'm in the brazilian 5.0.2.
Click to expand...
Click to collapse
cdiamond said:
What carrier are u on?
Click to expand...
Click to collapse
I'm in united States using cricket wireless.
You do not need to be rooted for this. You must have unlocked boot loader though because you need twrp
Oh I'm rooted matter of fact I'm on the N5X based ROM and its really Good..and I will extract and put inside the backup folder
flipm00de said:
I'm in united States using cricket wireless.
You do not need to be rooted for this. You must have unlocked boot loader though because you need twrp
Click to expand...
Click to collapse
Is there any other way? I dont have twrp, I updated to 5.0.2 just copying the ota zip on my phone.
flipm00de said:
In running it right now, and it is nice thus far
Click to expand...
Click to collapse
Ok could I flash back to stock 4.4.2 if I don't want to be on 5.1 anymore?
cdiamond said:
Ok could I flash back to stock 4.4.2 if I don't want to be on 5.1 anymore?
Click to expand...
Click to collapse
I was wondering the same thing
Tested on my XT1058, worked like a charm! No need to mess with bootloader, fastboot nor any other tool... Download, add to memory, install, be happy!
Just as other OTA zips...
Ah, remember to install 5.0.2 OTA before this, link can be found on other threads...
---------- Post added at 11:56 AM ---------- Previous post was at 11:52 AM ----------
truelove_shinn said:
I was wondering the same thing
Click to expand...
Click to collapse
Please don't! Many people bricked the device when trying to roll back from 5.X... If you install the soak test, it is better to wait for the final OTA update...
How to update
Yesterday I found out why in some cases when you place the file in the internal memory it doesn't work, you need to follow the updates sequence to make it work.
So from 4.4.4 you update to 5.0.2 (AKA .31):
Blur_Version.221.41.31.ghost_row.Brasil.en.BR
Then you apply this small patch that still 5.0.2 (AKA .38):
Blur_Version.221.41.38.ghost_row.Brasil.en.BR
And finally you apply the update to 5.1 (AKA .2)
Blur_Version.222.21.2.ghost_row.Brasil.en.BR
Happy flashing.
Kind regards,
Johnny
JohNNyum said:
Yesterday I found out why in some cases when you place the file in the internal memory it doesn't work, you need to follow the updates sequence to make it work.
Click to expand...
Click to collapse
Yes. All OTA's have been incremental so far, and have a pre-flash validation check to ensure your phone is on the correct level, and if your phone isn't, it wont flash.
It doesn't surprise me that this follows that pattern especially based on its size
KidJoe said:
Yes. All OTA's have been incremental so far, and have a pre-flash validation check to ensure your phone is on the correct level, and if your phone isn't, it wont flash.
It doesn't surprise me that this follows that pattern especially based on its size
Click to expand...
Click to collapse
What will happen with the official 5.1 release then? They never released an official 5.0.2, so how can they expect people to be upgrading from 5.0.2?
joaoBeno said:
Tested on my XT1058, worked like a charm! No need to mess with bootloader, fastboot nor any other tool... Download, add to memory, install, be happy!
Just as other OTA zips...
Ah, remember to install 5.0.2 OTA before this, link can be found on other threads...
---------- Post added at 11:56 AM ---------- Previous post was at 11:52 AM ----------
Please don't! Many people bricked the device when trying to roll back from 5.X... If you install the soak test, it is better to wait for the final OTA update...
Click to expand...
Click to collapse
Thanks a lot for the kind warning. After posting this comment I went through many other posts, especially the one by KidJoe. Chances are quite real that one can hard-brick his device by downgrading then upgrading through OTA again.
justaway2 said:
What will happen with the official 5.1 release then? They never released an official 5.0.2, so how can they expect people to be upgrading from 5.0.2?
Click to expand...
Click to collapse
For those were invited to the MFN Test or Soak, Moto has their IMEI, knows what is on their phone, and will push them the appropriate update to 5.1 final, hence this file's preflash check looking for a particular 5.02. Since we know of two different 5.02 versions (one for the Brazil xt1058 and one for the XT1053), there will be at least two different 5.1 versions that Moto will push to those on the MFN test/soak list.
For the those NOT invited, as in the past Moto will likely compile and push a 4.4.4 -> 5.1 OTA zip for each carrier/model which will have a preflash check looking for the 4.4.4 for the particular carrier/model.
For those that manually applied the 5.x leaks because they were NOT invited to the MFN test/soak, Moto will NOT have their IMEI to push a special version, they will be off stock 4.4.4, and so any 5.1 push from the carrier/moto will fail to install due to the preflash check. They'll either need to revert to 4.4.4 (where GPT.BIN/Motoboot.img have been the cause of many bricks in the past when downgrading, so its expected to continue to be risky going forward), or wait for a leak of the OTA zip they need, or wait for a leak of the 5.1 SBF for their carrier/model.
That is why some suggested if you're not part of the MFN invites, you should wait on installing the 5.x leaks.
Credits mega link for me haha
http://www.motoforum.com.br/topic/33-ota-android-51-lollipop-moto-x/?page=1
Google released the Android 7.1 Developer preview for the Nexus 5X device.
Android Developers
You can enroll your eligible device in the Android beta program to get it on the developer preview or grab the system images here and flash them manually.
So far seems really really smooth, loving the transition animations during setup.
mykenyc said:
So far seems really really smooth, loving the transition animations during setup.
Click to expand...
Click to collapse
Can you post some screenshots ?
karthik432 said:
Can you post some screenshots ?
Click to expand...
Click to collapse
check out this article:
http://www.androidpolice.com/2016/1...view-now-available-nexus-5x-nexus-6p-pixel-c/
How's the camera for all of you?
Having problems here with the auto ISO on the camera, running ElementalX kernel.
Edit: Yep, confirmed, 7.0 custom kernels cause camera problems on 7.1.1
Has anybody testeed root methods or twrp on 7.1 yet? Figured I would ask before I tried it.
Sent from my Nexus 5X using Tapatalk
pbailey212 said:
Has anybody testeed root methods or twrp on 7.1 yet? Figured I would ask before I tried it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I did and everything was working just fine until I tried flashing a tweak to make the nav bar look like the pixel. it sucks because now I will have to go back and redo everything I just did. installing twrp worked, rooting worked, installing the pixel launcher worked, changing the build prop to enable google assistant worked just not the mod to change the nav bar.
Just so everyone knows NexusRootToolkit by Wugfresh works like a charm
Has anyone tried altering your build.prop to get Assistant working?
erikcave said:
Has anyone tried altering your build.prop to get Assistant working?
Click to expand...
Click to collapse
Yes it worksjist like it did on 7.0. I used the flashable zip method.
Another quick question,
I downloaded from here:
https://developer.android.com/preview/download.html#top
to get a .zip file. Do in install this in TWRP? I was expecting to have to use NRT.
erikcave said:
Another quick question,
I downloaded from here:
https://developer.android.com/preview/download.html#top
to get a .zip file. Do in install this in TWRP? I was expecting to have to use NRT.
Click to expand...
Click to collapse
Yes u can use it. But device may reboot while installing. If it rebooted: Don't do any wipes, just re-run installation!
---------- Post added at 10:03 AM ---------- Previous post was at 10:02 AM ----------
Wow. Camera stock app now similar to Pixel's
erikcave said:
Has anyone tried altering your build.prop to get Assistant working?
Click to expand...
Click to collapse
erikcave said:
Another quick question,
I downloaded from here:
https://developer.android.com/preview/download.html#top
to get a .zip file. Do in install this in TWRP? I was expecting to have to use NRT.
Click to expand...
Click to collapse
No you download it on your PC and put your phone in fastboot then run the flash all.bat file and it does everything for you
I am stock rooted on 7.0. I am guessing I can't install the OTA ?
I can't get twrp to work. It keeps wanting to decrypt and it still won't read my storage if I am decrypted. I tried 3.0.2.1, 2.2, and 2.3
Sent from my Nexus 5X using Tapatalk
I'm on PureNexus, can I flash the ota over custom rom and custom kernel?
tauio111 said:
How's the camera for all of you?
Having problems here with the auto ISO on the camera, running ElementalX kernel.
Click to expand...
Click to collapse
I read on Flash kernel thread that that's a bug with 7.0 kernels on 7.1.
Sent from my Nexus 5X using XDA Labs
i try OTA update on Stock + after a Factory reset who delete the SuperSu ....... Downloading i'm waitting for ready to reboot and applying 7.1 update
Just installed. Now, storage is taking more space than earlier
axiel7 said:
I'm on PureNexus, can I flash the ota over custom rom and custom kernel?
Click to expand...
Click to collapse
No, Clean flash Stock then 7.1 OTA.
Just received a notice that a new Beta version NPG47I is being pushed currently. 328.9MB in size.
Just wanted to give everyone a heads up!
First thing I notice is on start-up there is now a "Powered by Android" at the bottom.
March 5th Security updates.
Thanks​ for the heads up! Having a problem installing. It downloads fine and then fails installing shortly after the installation starts. Probably because I am rooted, but I was rooted when I installed the beta to begin with and it worked fine.
OTA for NPG47I from NPG05E (330MB download)
https://ota.googlezip.net/packages/.../890d20b59c4edeeef494b2bd8ae7830b14fe7df4.zip
Code:
ota-required-cache=0
ota-type=AB
post-build=google/marlin/marlin:7.1.2/NPG47I/3795619:user/release-keys
post-build-incremental=3795619
post-timestamp=1489011460
pre-build=google/marlin/marlin:7.1.2/NPG05E/3638325:user/release-keys
pre-build-incremental=3638325
pre-device=marlin
Verizon?
I decided to load this up from my Verizon version to see what happens. It's a 841.7 MB update (from whatever the latest version was pushed out, I had already missed the boat on first the system update that locked the BL).
What are my options if I'm able to unlock the bootloader while in this beta?
It seems if I un-enroll from the beta, I'll get wiped?
I mainly just want to be able to run a rom and edit my build.prop.
Yes. It will wipe the entire device if you unenroll. I would wait to see if someone builds a custom ROM based off of the new build if your intent is to modify.
se7endust1 said:
I decided to load this up from my Verizon version to see what happens. It's a 841.7 MB update (from whatever the latest version was pushed out, I had already missed the boat on first the system update that locked the BL).
What are my options if I'm able to unlock the bootloader while in this beta?
It seems if I un-enroll from the beta, I'll get wiped?
I mainly just want to be able to run a rom and edit my build.prop.
Click to expand...
Click to collapse
iceman4357 said:
Yes. It will wipe the entire device if you unenroll. I would wait to see if someone builds a custom ROM based off of the new build if your intent is to modify.
Click to expand...
Click to collapse
Well, I'll have to wait for more experienced people to mess with this, if there's anything to do with it. The toggle in my dev options for unlock is still greyed out.
If you un enroll in the beta and accept the OTA to the latest stable then it will wipe your device. If you un enroll then flash the latest stable it should keep your files as long as you take out the -w in the .bat file.
wow nice
If I delete SuperSu, do you guys think I will be able to take the OTA successfully? Its weird because I was rooted when I installed the beta to begin with and had no issues. Just had to root again afterwards.
Does it have the same old Google camera or anything newer?
CZ Eddie said:
Does it have the same old Google camera or anything newer?
Click to expand...
Click to collapse
Same. It actually contains an older build that is updatable via the play store to the current 4.3.016
Couldn't update. I was rooted, did full unroot, but still couldn't update. Anyone have a flashable .zip?
335Deezl said:
Couldn't update. I was rooted, did full unroot, but still couldn't update. Anyone have a flashable .zip?
Click to expand...
Click to collapse
Yeah same here, full unroot and flashed back system boot/recovery and still no go.
Can't do OTA or sideload with ADB
So this image won't be available on Google's server separately? And the stable 7.1.2 is supposedly coming on 3rd April?
Rollback OTA (will wipe the device) for NOF27B from NPG47I
https://ota.googlezip.net/packages/.../33bbd87269a4e7babcd165d2ccbf28136138a6ac.zip
Code:
ota-downgrade=yes
ota-required-cache=0
ota-type=AB
ota-wipe=yes
post-build=google/marlin/marlin:7.1.1/NOF27B/3687361:user/release-keys
post-build-incremental=3687361
pre-build=google/marlin/marlin:7.1.2/NPG47I/3795619:user/release-ke
s
pre-build-incremental=3795619
pre-device=marlin
danw_oz said:
Yeah same here, full unroot and flashed back system boot/recovery and still no go.
Can't do OTA or sideload with ADB
Click to expand...
Click to collapse
I reflashed the factory image of the first 7.1.2 beta from last month and then was able to sideload the ota. no problem.
---------- Post added at 06:18 PM ---------- Previous post was at 06:14 PM ----------
xdatastic said:
Rollback OTA (will wipe the device) for NOF27B from NPG47I
https://ota.googlezip.net/packages/.../33bbd87269a4e7babcd165d2ccbf28136138a6ac.zip
Code:
ota-downgrade=yes
ota-required-cache=0
ota-type=AB
ota-wipe=yes
post-build=google/marlin/marlin:7.1.1/NOF27B/3687361:user/release-keys
post-build-incremental=3687361
pre-build=google/marlin/marlin:7.1.2/NPG47I/3795619:user/release-ke
s
pre-build-incremental=3795619
pre-device=marlin
Click to expand...
Click to collapse
You can manually flash the 7.1.1 factory image without wiping the device.
Factory images are up. Release notes.
---------- Post added at 10:52 AM ---------- Previous post was at 10:48 AM ----------
Well, Android O developer preview images are up as well.
Kisakuku said:
Factory images are up. Release notes.
---------- Post added at 10:52 AM ---------- Previous post was at 10:48 AM ----------
Well, Android O developer preview images are up as well.
Click to expand...
Click to collapse
Am I able to flash this without wiping? I am currently on the first 7.1.2 beta. Can't take the OTA due to being rooted, but unrooting doesn't seem to help either.
Frankie1588 said:
Am I able to flash this without wiping? I am currently on the first 7.1.2 beta. Can't take the OTA due to being rooted, but unrooting doesn't seem to help either.
Click to expand...
Click to collapse
Yes, just remove the '-w' in flash-all.bat.
ok so i flashed just the radio from the latest beta, radio-marlin-8996-012901-1702171013.img, and no signal and baseband unknown when booted in to the O.S. had to update the bootloader to the Beta2 bootloader in order to flash the radio back at all. does anyone have the beta1 image? i loved the radio in it it worked great.
On Google developers site. Both factory images and OTA.
PLEASE fix bluetooth lol
EDIT: How do I know if I need OTA build E or J?
"J" is for Deutsche Telekom
Flashed here. All good so far.
TonikJDK said:
Flashed here. All good so far.
Click to expand...
Click to collapse
Does systemless root work on this new build? I don't want to flash it if root hasn't been sorted out yet.
anuraj1 said:
Does systemless root work on this new build? I don't want to flash it if root hasn't been sorted out yet.
Click to expand...
Click to collapse
I flashed SU 2.79 SR3 no problem. All my root apps work fine. I do not install TWRP, I only boot to it via Fastboot to install SU. So I can't give any insight on how that is working.
The.Yield said:
PLEASE fix bluetooth lol
EDIT: How do I know if I need OTA build E or J?
Click to expand...
Click to collapse
J is just for Deutsche Telekom
A quick heads up that there is a bug with the lates version of adb 25.0.4 wich mean your unable to sidload larger files, you need to roll backk to adb version 25.0.3 to sidload this OTA. See this bug report here:
https://code.google.com/p/android/i... Priority Owner Summary Stars Reporter Opened
anuraj1 said:
J is just for Deutsche Telekom
Click to expand...
Click to collapse
Which build should US T-Mobile use?
So I have root (March update, 7.1.1). I can install the factory image of 7.1.2 without losing data right? (by deleting -w from the bat file ie)
And will I be able to root it again using the boot to root.img process, right? Thanks to anyone who knows and can help.
Which is better? Flash ota through twrp or factory??
TheAnarchist1 said:
Which build should US T-Mobile use?
Click to expand...
Click to collapse
Flash E.
---------- Post added at 21:09 ---------- Previous post was at 21:09 ----------
lucky_strike33 said:
Which is better? Flash ota through twrp or factory??
Click to expand...
Click to collapse
flash through stock recovery
TheAnarchist1 said:
Which build should US T-Mobile use?
Click to expand...
Click to collapse
"J" is for Deutchtelecom.
"E" is for everyone else.
zaydenQ said:
So I have root (March update, 7.1.1). I can install the factory image of 7.1.2 without losing data right? (by deleting -w from the bat file ie)
And will I be able to root it again using the boot to root.img process, right? Thanks to anyone who knows and can help.
Click to expand...
Click to collapse
Yeah, do full unroot, flash ota, re-root.
@IIIIkoolaidIIII
Thanks for the heads up! I figured such. You never know, though. T-Mobile and DT are technically the same thing after all'ish. Better to confirm with the community before doing something stupid!
IIIIkoolaidIIII said:
Flash E.
---------- Post added at 21:09 ---------- Previous post was at 21:09 ----------
flash through stock recovery
Click to expand...
Click to collapse
zaydenQ said:
So I have root (March update, 7.1.1). I can install the factory image of 7.1.2 without losing data right? (by deleting -w from the bat file ie)
And will I be able to root it again using the boot to root.img process, right? Thanks to anyone who knows and can help.
Click to expand...
Click to collapse
Yes, remove the -w to save data and apps.
Boot to root was for 7.1. 7.1.1 and 7.1.2 are different. See my post in the thread below. Second to the last post has it all for you.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
IIIIkoolaidIIII said:
A quick heads up that there is a bug with the lates version of adb 25.0.4 wich mean your unable to sidload larger files, you need to roll backk to adb version 25.0.3 to sidload this OTA. See this bug report here:
https://code.google.com/p/android/i... Priority Owner Summary Stars Reporter Opened
Click to expand...
Click to collapse
Where did those ADB versions come from? I fastboot install of sideload, and I haven't installed this update yet, but I haven't had any problems.
This is what mine from platform tools says:
>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
flashed all images via fastboot manually, and working fine.
JimSmith94 said:
Where did those ADB versions come from? I fastboot install of sideload, and I haven't installed this update yet, but I haven't had any problems.
This is what mine from platform tools says:
>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
Click to expand...
Click to collapse
Directly from Google. Here > https://developer.android.com/studio/releases/platform-tools.html#revisions
cam30era said:
Directly from Google. Here > https://developer.android.com/studio/releases/platform-tools.html#revisions
Click to expand...
Click to collapse
I don't use the full SDK, so maybe that's the difference. I use the minimal ADB and fastboot from Google as linked by Android Police here: http://www.androidpolice.com/2017/0...ble-without-full-sdk-android-studio-download/.
It was last updated on March 13, but ADB hasn't changed since last December. That doesn't explain the huge version difference, unless that is the SDK version itself.
Haven't installed it yet. Anyone have?
622 MB??? Wth can be in there?
tolymatev said:
Wth can be in there?
Click to expand...
Click to collapse
It's in your print
Still doesn't allow me to update Hiya.
tolymatev said:
Wth can be in there?
Click to expand...
Click to collapse
Lol. Look at the screenshot you posted...
On a more serious note, hopefully DrakenFX is able to whip up a flashable zip for us rooted folks.
Luhccas-X10 said:
It's in your print
Click to expand...
Click to collapse
Bolandk said:
Lol. Look at the screenshot you posted...
On a more serious note, hopefully DrakenFX is able to whip up a flashable zip for us rooted folks.
Click to expand...
Click to collapse
Im talking about the size of the download. Usually these minor updates are 200 MB.
Btw, this doesn't even include April security patch.
Just received B25 OTA but when I ask it to install, phone reboots into TWRP and I can't install from TWRP. Later I get a notification that update failed. I tried FlashFire, it detects the B25 OTA but will not install gives message "Unencrypted ....".
TheBoozer said:
Just received B25 OTA but when I ask it to install, phone reboots into TWRP and I can't install from TWRP. Later I get a notification that update failed. I tried FlashFire, it detects the B25 OTA but will not install gives message "Unencrypted ....".
Click to expand...
Click to collapse
To get the stock OTA to work , you need the stock recovery (TWRP won't work).
Not sure about Flashfire?
tele_jas said:
To get the stock OTA to work , you need the stock recovery (TWRP won't work).
Not sure about Flashfire?
Click to expand...
Click to collapse
Thank you. Can direct me on how to get the stock recovery? I am somewhat a noobe!
tolymatev said:
Im talking about the size of the download. Usually these minor updates are 200 MB.
Btw, this doesn't even include April security patch.
Click to expand...
Click to collapse
It is 7.1.1 and is the March 2017 security updates. It does add night light and is supposed to fix the DND issues. It also has a modem patch.
TeutonJon78 said:
It is 7.1.1 and is the March 2017 security updates. It does add night light and is supposed to fix the DND issues. It also has a modem patch.
Click to expand...
Click to collapse
Currently I am on 7.1.1 latest update and I am unlocked and rooted. Should I flash the 7.1.1 again?
TheBoozer said:
Currently I am on 7.1.1 latest update and I am unlocked and rooted. Should I flash the 7.1.1 again?
Click to expand...
Click to collapse
Not much has changed for me from B19 to B25.
TheBoozer said:
Thank you. Can direct me on how to get the stock recovery? I am somewhat a noobe!
Click to expand...
Click to collapse
Everything you need to know is in this thread: https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Make a backup first, it (should) completely wipe your data.
tele_jas said:
Everything you need to know is in this thread: https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Make a backup first, it (should) completely wipe your data.
Click to expand...
Click to collapse
Thank you, very much appreciate it.
DAC is still screwed up. Standard/Super sound reversed compared to pre Nougat.
bhazard451 said:
DAC is still screwed up. Standard/Super sound reversed compared to pre Nougat.
Click to expand...
Click to collapse
Can you prove this?
Problem that I have found was with the Fingerprint sensor. Before I could unlock my phone easy. Now I have to stick my tongue out, while standing on my head, one leg horizontal, and he the other leg vertical. Wiping cache helps a little but not a lot. I removed fingerprints and re-added them. Helps a little.
TheBoozer said:
Currently I am on 7.1.1 latest update and I am unlocked and rooted. Should I flash the 7.1.1 again?
Click to expand...
Click to collapse
I don't understand the question. If you're on B25, there is no need. If you're on B19 and want the B25 update, you'll either need to be stock or wait for a flash package before updating, since you've modified some partitions.
The OTA files only work directly on fully stock phones.
bhazard451 said:
DAC is still screwed up. Standard/Super sound reversed compared to pre Nougat.
Click to expand...
Click to collapse
Try high end high ohm headphones, you will be surprised to see that they work correctly.
TeutonJon78 said:
I don't understand the question. If you're on B25, there is no need. If you're on B19 and want the B25 update, you'll either need to be stock or wait for a flash package before updating, since you've modified some partitions.
The OTA files only work directly on fully stock phones.
Click to expand...
Click to collapse
Sorry if I weren't clear, currently I have Nougat 7.1.1 and my version is 0B19 and I want to install the 0B25 that was pushed OTA yesterday. I thought I was running B19 stock. I am Unlocked, TWRP and Rooted. If there is something that has been modified in my system then as you stated, I guess I have to wait for a B25 ZIP to flash.
Thank you for your help.
TeutonJon78 said:
I don't understand the question. If you're on B25, there is no need. If you're on B19 and want the B25 update, you'll either need to be stock or wait for a flash package before updating, since you've modified some partitions.
The OTA files only work directly on fully stock phones.
Click to expand...
Click to collapse
Not true... I installed the OTA to my setup using TWRP just needed to delete a few lines from the updater-script to make it possible