Been busy, still have not unlocked/rooted my 6P.
I've got the OTA for N 7.0 waiting to install - is there anything that will screw me up from fastboot flashing back to a previous image if I take the OTA to 7.0 and then do the fastboot flashing unlock and unlock the phone while on 7.0.
I'm guessing it should be like all Nexus devices still where you can always go back, but I have noticed some people having issues when trying to downgrade. If it trips anything up I'll wait, but if I can take the OTA and then unlock, rooting, downgrade, upgrade, ROM, etc as usual, I'll give N a go first.
Sent from my Nexus 6P using Tapatalk
You should be able to do everything you said in your post. I've done the same things multiple times with no problems whatsoever. That's the beauty of a Nexus device.
10-4. Previous Nexus experience with the n7 2013 was that way, just had seen some people having brick issues while trying to downgrade
Sent from my Nexus 6P using Tapatalk
Norcalz71 said:
10-4. Previous Nexus experience with the n7 2013 was that way, just had seen some people having brick issues while trying to downgrade
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
That was due to TWRP 3.0.2-1 having a bug restoring EFS partitions. If you are fastboot flashing a factory MM image, you should be fine.
Sent from my Nexus 6P using Tapatalk
Since you're stock, locked and unrooted... YMMV
On multiple forums, it was suggested that right vendor.img should work for downgrade
I installed Android 7 Nougat by flashing WETA 8 ROM on unlocked bootloader
To revert to Marshmallow, I was able flash the vendor.img along with radio.img and bootloader.img and then MM ROM from https://androidfilehost.com/?w=files&flid=88221
aviralmsharma said:
Since you're stock, locked and unrooted... YMMV
On multiple forums, it was suggested that right vendor.img should work for downgrade
I installed Android 7 Nougat by flashing WETA 8 ROM on unlocked bootloader
To revert to Marshmallow, I was able flash the vendor.img along with radio.img and bootloader.img and then MM ROM from https://androidfilehost.com/?w=files&flid=88221
Click to expand...
Click to collapse
in my past experience with fastboot flashes, I never messed with any vendor.img. Is this a new thing?
My thought was to hop to 7.0, give it a run, and if necessary I would factory reset and fastboot flash myself back to 6.0.1. All stock, then go from there.
Norcalz71 said:
in my past experience with fastboot flashes, I never messed with any vendor.img. Is this a new thing?
My thought was to hop to 7.0, give it a run, and if necessary I would factory reset and fastboot flash myself back to 6.0.1. All stock, then go from there.
Click to expand...
Click to collapse
I too learnt about the vendor.img recently
The dev for WETA ROM included this in change log : "WETA V5.0 *reflashing vendor.img is essential for this update"
Since you are on stock ROM, would this for you?
http://www.gsmarena.com/heres_how_t...n_to_marshmallow_on_your_nexus-blog-17197.php
aviralmsharma said:
I too learnt about the vendor.img recently
The dev for WETA ROM included this in change log : "WETA V5.0 *reflashing vendor.img is essential for this update"
Since you are on stock ROM, would this for you?
http://www.gsmarena.com/heres_how_t...n_to_marshmallow_on_your_nexus-blog-17197.php
Click to expand...
Click to collapse
Vendor has been a thing all through MM, too. It includes binaries that allow Android to run and is updated with each new build. So, every ROM or monthly security update requires a matching vendor to work.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
Vendor has been a thing all through MM, too. It includes binaries that allow Android to run and is updated with each new build. So, every ROM or monthly security update requires a matching vendor to work.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Good to know! Thanks ultyrunner
ultyrunner said:
Vendor has been a thing all through MM, too. It includes binaries that allow Android to run and is updated with each new build. So, every ROM or monthly security update requires a matching vendor to work.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
10-4, but it just accompanies all the other images with each build stack? I DL'd 6.0.1 and looks like it's in there.
Big problems if you mismatch vendor.img and other img builds?
Sent from my Nexus 6P using Tapatalk
Norcalz71 said:
10-4, but it just accompanies all the other images with each build stack? I DL'd 6.0.1 and looks like it's in there.
Big problems if you mismatch vendor.img and other img builds?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yes, vendor is in each build of factory image. Many on here can't be bothered flashing from bootloader so they wait for someone to make a zip. If you have a mismatched vendor, you will get an error message on boot and your phone will likely exhibit anything from FCs of apps to bootloops to whatever.
Sent from my Nexus 6P using Tapatalk
Related
For whatever reason can't get the update to flash. I'm stock jwr66y except I have twrp and root. Is there a straight stock rooted rom for grouper yet or an I Sol?
Sent from my Nexus 4 using Tapatalk
Anyone?
Sent from my Nexus 4 using Tapatalk
You can't flash the OTA if you're rooted I believe. Try to unroot. If that doesn't work, maybe flashing the system.img from the extracted JWR66Y factory image might work.
If you want 4.4 asap, go back to stock 4.3.
Custom 4.4 roms will be available after Google releases the stock images.
Eregoth said:
You can't flash the OTA if you're rooted I believe. Try to unroot. If that doesn't work, maybe flashing the system.img from the extracted JWR66Y factory image might work.
Click to expand...
Click to collapse
You can flash it if you are rooted, you will only loose root. But it is so easy to root afterwards, just flash SU from recovery....
I couldn't get it to flash over the top of a rooted stock 4.3 rom.
In the end I used wug's toolkit to flash an unrooted stock 4.3 image (the toolkit does all the work for you, even downloading the stock image), then flashed the 4.4 zip over the top, again using wug's toolkit.
to be honest its a bit disappointing as there's no option to enable ART in developer options and no translucent notification bar/nav bar.
looks and feels exactly the same as it did with 4.3 (it's showing as 4.4. under 'about tablet').
Cor-master said:
For whatever reason can't get the update to flash. I'm stock jwr66y except I have twrp and root. Is there a straight stock rooted rom for grouper yet or an I Sol?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I couldn't flash it with twrp, either. Switch to the latest cwm and try again. Worked for me.
My install failed at the end, while setting permissions, if I remember well. You could try to flash boot.img and system.img from the jwr66y factory image, just to be sure.
where is the ota. everyones talking about it,but, it aint even released on googles site???FRAUDS.
podagee said:
where is the ota. everyones talking about it,but, it aint even released on googles site???FRAUDS.
Click to expand...
Click to collapse
right here .... bold lettered
http://forum.xda-developers.com/showthread.php?t=1745781
bonzer2u said:
right here .... bold lettered
http://forum.xda-developers.com/showthread.php?t=1745781
Click to expand...
Click to collapse
I want the official through Google. Anyone know when it will post the full factory image?
dalanik said:
You can flash it if you are rooted, you will only loose root. But it is so easy to root afterwards, just flash SU from recovery....
Click to expand...
Click to collapse
What I meant was if one is not using stock recovery and rom, will not get the official OTA update.
podagee said:
I want the official through Google. Anyone know when it will post the full factory image?
Click to expand...
Click to collapse
Thats 100% official. If you check the link, its straight from Google's OTA server.
Erovia said:
What I meant was if one is not using stock recovery and rom, will not get the official OTA update.
Thats 100% official. If you check the link, its straight from Google's OTA server.
Click to expand...
Click to collapse
That's not a full factory image, just the OTA image. I'm not in a hurry for any of this anyway. I'd rather just wait for a full stock rooted 4.4 ROM, whenever that's cobbled together. If it's not broken, don't attempt to fix.
LordLugard said:
That's not a full factory image, just the OTA image. I'm not in a hurry for any of this anyway. I'd rather just wait for a full stock rooted 4.4 ROM, whenever that's cobbled together. If it's not broken, don't attempt to fix.
Click to expand...
Click to collapse
Its here.... On the factory image website a bunch got it. I can't wait to get home to update my nexus 7 and my phone(nexus 4).
Finally ! Straight from Google DEVS
"razor" for Nexus 7 [2013] (Wi-Fi) 5.1.1 (LMY47V)
Thank You
Just flashed it. I wasn't having any issues, but I hope it fixes problems for others.
just lou said:
Just flashed it. I wasn't having any issues, but I hope it fixes problems for others.
Click to expand...
Click to collapse
Can you check if the bootloader is still 04.05 or it changed?
I heard, it is the same
idCyber said:
Can you check if the bootloader is still 04.05 or it changed?
Click to expand...
Click to collapse
Its 4.05 bootloader still. Somehow in the zip its called bootloader-flo-flo-04.05.img
There's a new kernel, some changes in the source. Its compiled March 21
Not much else changed
Has any one got the ota yet ?
@Vkk187
ofc not.
Flash the stock image with NRT and check "dirty flash" and that will not delete your apps and data.
Yet to unlock my BL ...I know it's simple . Will do it some day [emoji18]
AonI updated to 5.1 rooted stock via TWRP a couple weeks ago.
Today I just got this update notification for 5.1
Is today's notification for 5.1.1? Because it only says 5.1
Do we have a rooted stock file we can flash in TWRP?
ymDroid said:
Do we have a rooted stock file we can flash in TWRP?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nex...my47v-root-t3098137/post60479181#post60479181
I just got the 5.1 update. It shows 5.1.1 as the Android version.
Sent from my BN Nook HD using XDA Free mobile app
I just completely flash-all every time a new build comes out as I do not know how to side load using NRT or TWRP (am I wasting my time on doing it this way). If someone could please explain to me how to side load I would be forever grateful. I have searched and cannot find clear instructions or walk through on side loading
Having read wugfresh page,it says Since lollipop,its hard to sideload OTA now. I myself try it last night with my rooted stock recovery,it fails to install the OTA from google,even if file has been downloaded automatically. Its harder to get OTA install smoothly nowadays especially if you on lollipop. No choice had full flash without wipe. And reroot again.
Sent from my Nexus 7
ksloh1 said:
Having read wugfresh page,it says Since lollipop,its hard to sideload OTA now. I myself try it last night with my rooted stock recovery,it fails to install the OTA from google,even if file has been downloaded automatically. Its harder to get OTA install smoothly nowadays especially if you on lollipop. No choice had full flash without wipe. And reroot again.
Sent from my Nexus 7
Click to expand...
Click to collapse
Actually, it's just as easy sideloading as it's always been. The difference is that you can't sideload an OTA (or receive one in any way) if you've done any kind of alterations to the system. This includes rooting and/or flashing custom recoveries and kernels. Even if you unroot there are still residue alterations in your system, meaning you'll have to do a full system flash anyway.
It's worth mentioning that unlocking your bootloader does not prevent installing an OTA.
How is this version running compare to the 5.0?
Jaylex31 said:
How is this version running compare to the 5.0?
Click to expand...
Click to collapse
Any versions of Android on the Nexus 7 2013 ran fine for me.
I'm sure I overlooked something but I'll ask anyway. Is it possible to update without losing root and having to reinstall modified TWRP 2.7.01?
Sent from my Nexus 6
Anyone have a flashable TWRP for it yet? That would be NICE
Sent from my Nexus 6
Which device?
VK810
Probably only one still on kk
713brianp27 said:
VK810
Click to expand...
Click to collapse
713brianp27 said:
Probably only one still on kk
Click to expand...
Click to collapse
rfarrah said:
Took the OTA. Lost root. Trying to decide whether I need to root again.......
Click to expand...
Click to collapse
713brianp27 said:
There's an official lollipop update for 8.3 VZW? Missed that
Sent from my Nexus 6
Click to expand...
Click to collapse
I have managed to root the device but TWRP is not working on aboot 5.0.2. You can see the post links below.
It is merely few commands on 5.0.2 to run recovery by downgrading your aboot to 4.2.2 but then, Lollipop wouldn't start and you will need to reflash aboot 5.0.2.
So basically it is a choice between Lollipop rooted without recovery or Kitkat with root & recovery. I think we are not flashing anything as yet so it would not be much of a problem actually to not have a recovery. When we do need however, we can downgrade our aboot and flash twrp using loki and then flash the rom we want to.
Look into my guides for more details
http://forum.xda-developers.com/lg-g-pad-83/general/vk810-altev-complete-root-recovery-t3108260
http://forum.xda-developers.com/lg-g-pad-83/general/vk810-downgrade-required-t3116336
Yeah I recall rooting it first time. Pain. All the Loki this Loki that.. Asking bc I upgraded my KLTEVZW by way of a flashable zip (4.4.4-5.0). Thought it may be possible on G Pad?
How about you root and make a twrp backup. Win, win
713brianp27 said:
I'm sure I overlooked something but I'll ask anyway. Is it possible to update without losing root and having to reinstall modified TWRP 2.7.01?
Sent from my Nexus 6
Click to expand...
Click to collapse
Check my ROM in my signature below, just flash the new official VK810 altev LG G Pad 8.3 35A_08 5.0.2 ROM from TWRP.
Also, questions should go in Q&A, not in General.
Hnk1 said:
I have managed to root the device but TWRP is not working on aboot 5.0.2. You can see the post links below.
It is merely few commands on 5.0.2 to run recovery by downgrading your aboot to 4.2.2 but then, Lollipop wouldn't start and you will need to reflash aboot 5.0.2.
So basically it is a choice between Lollipop rooted without recovery or Kitkat with root & recovery. I think we are not flashing anything as yet so it would not be much of a problem actually to not have a recovery. When we do need however, we can downgrade our aboot and flash twrp using loki and then flash the rom we want to.
Look into my guides for more details
http://forum.xda-developers.com/lg-g-pad-83/general/vk810-altev-complete-root-recovery-t3108260
http://forum.xda-developers.com/lg-g-pad-83/general/vk810-downgrade-required-t3116336
Click to expand...
Click to collapse
Have you tried CWM? Rumor is there's a new TWRP that hasn't been released yet, for what ever reason.
No twrp to flash, yet?
713brianp27 said:
Have you tried CWM? Rumor is there's a new TWRP that hasn't been released yet, for what ever reason.
Click to expand...
Click to collapse
It's not a rumour. It definitely exists. It won't matter what recovery you use or what version as to whether you need to swap aboot.img versions temporarily if you're running stock LG Lollipop, if that's what you're wondering. 4.2.2 aboot.img lets the custom recovery boot, anything newer doesn't. And stock LG Lollipop won't boot on the 4.2.2 aboot.img, so you have to swap the new 35A_08 5.0.2 aboot.img in to get the ROM to boot.
I'm guessing the dev who made the newest TWRP for the VK810.4G is waiting to release it to the public until/if he gets CM 12.1 completely straightened out for our device. He'll probably release both at the same time.
713brianp27 said:
No twrp to flash, yet?
Click to expand...
Click to collapse
I'm not sure what you're asking here. 2.7.0.1, 2.7.0.2 and 2.7.1.0 are all publicly available for us.
Sent from my VK810 4G
Idk. Some guy was bragging about using 2.8.6 saying it "wasn't publicly available yet" not to long ago. Only reason I said rumor was I had no proof.
Honestly I could care less what version he has. BL still locked. No mr , just felt he was name dropping or bragging. " I got it and you don't " sorry
Hello, I want to flash the 7.0 update yet I'm uncertain as to which build I'm supposed to use. I'm currently on MTC19T but don't know which I'm supposed to use from the factory images " 7.0.0 (NRD90T)" or "7.0.0 (NRD90U) ".
I'm currently on PureNexus ROM with ElementalX kernel.
This is about the Nexus 6P.
Use the latest (NRD90U).
I was wondering if you're on a custom 6.0.1 ROM (DU for example) if you can just clean flash up to a 7.0 ROM? Or do you need to first do a flash-all.bat of the NRD90U from google or something like that? Idk how simple moving up to nougat is.
whispertwig said:
I was wondering if you're on a custom 6.0.1 ROM (DU for example) if you can just clean flash up to a 7.0 ROM? Or do you need to first do a flash-all.bat of the NRD90U from google or something like that? Idk how simple moving up to nougat is.
Click to expand...
Click to collapse
You can clean flash a 7.0 rom, however you need to flash the matching 7.0 vendor.omg as well.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You can clean flash a 7.0 rom, however you need to flash the matching 7.0 vendor.omg as well.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you!
I have a US XT1687 on LineageOS (2017-09-19 build), and I would like to flash the latest stock firmware (which I believe is the April NPNS25.137-93-10 update), while also continuing to receive future OTA updates
The fastboot stock firmware thread was closed.
I found these files https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ but I don't see the 93-10 update.
Can I flash the 93-4 update from that site via fastboot and then get the 93-10 update via OTA?
Thanks!
I believe it depends on what bootloader version you were on before. If you were on 93-4 or earlier, then theoretically you should be fine. If you were on the 93-10 version of the bootloader and attempted to flash to the 93-4 stock rom, and then take an OTA from there, you are very likely going to hard-brick your device.
There are a lot of active threads about flashing back to stock and losing IMEI and enhanced LTE, so I wouldn't risk it. Out of curiosity why would you want to flash back to stock Nougat? IMO the camera is worse and you're rolling back to an older OS.
dunderball said:
I believe it depends on what bootloader version you were on before. If you were on 93-4 or earlier, then theoretically you should be fine. If you were on the 93-10 version of the bootloader and attempted to flash to the 93-4 stock rom, and then take an OTA from there, you are very likely going to hard-brick your device.
There are a lot of active threads about flashing back to stock and losing IMEI and enhanced LTE, so I wouldn't risk it. Out of curiosity why would you want to flash back to stock Nougat? IMO the camera is worse and you're rolling back to an older OS.
Click to expand...
Click to collapse
I'm actually still on Nougat. The last time I flashed a new ROM was back in September (the LineageOS build I'm using is from 2017-09-19). So my bootloader is likely whatever the latest one was around that time.
From what I read, it seemed like people were losing their IMEI and VoLTE after flashing 8.1 custom ROMs, which I haven't done, so I figured I was safe. Maybe I'm misunderstanding?
Yousie642 said:
I'm actually still on Nougat. The last time I flashed a new ROM was back in September (the LineageOS build I'm using is from 2017-09-19). So my bootloader is likely whatever the latest one was around that time.
From what I read, it seemed like people were losing their IMEI and VoLTE after flashing 8.1 custom ROMs, which I haven't done, so I figured I was safe. Maybe I'm misunderstanding?
Click to expand...
Click to collapse
Ah I wasn't aware that you were on a nougat version of LOS. I would still back up all partitions just in case.
dunderball said:
Ah I wasn't aware that you were on a nougat version of LOS. I would still back up all partitions just in case.
Click to expand...
Click to collapse
Is that different from doing a NAND backup in TWRP?
Yousie642 said:
Is that different from doing a NAND backup in TWRP?
Click to expand...
Click to collapse
Nope it's the same.
Yousie642 said:
I have a US XT1687 on LineageOS (2017-09-19 build), and I would like to flash the latest stock firmware (which I believe is the April NPNS25.137-93-10 update), while also continuing to receive future OTA updates
The fastboot stock firmware thread was closed.
I found these files https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ but I don't see the 93-10 update.
Can I flash the 93-4 update from that site via fastboot and then get the 93-10 update via OTA?
Thanks!
Click to expand...
Click to collapse
Here's a mirror of the 93-10 firmware, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud but not everyone was able to download it from there.
If you changed to a custom rom in September 2017 you should have been on August security patch which is the firmware NPNS25.137-33-11.
But you should be good to go with 93-10.
As written above make sure to have a full nandroid, especially of EFS.
Sent from my Moto G5 Plus using XDA Labs
dunderball said:
Nope it's the same.
Click to expand...
Click to collapse
Wolfcity said:
Here's a mirror of the 93-10 firmware, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud but not everyone was able to download it from there.
If you changed to a custom rom in September 2017 you should have been on August security patch which is the firmware NPNS25.137-33-11.
But you should be good to go with 93-10.
As written above make sure to have a full nandroid, especially of EFS.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Thanks dudes! I actually found my old adb folder and saw I had the files for NPN25.137-83 extracted there, so I'm pretty sure that's what I'm on. Seems like it still won't be an issue though.
What I am worried about now is losing VoLTE if I ever decide to go back to a custom ROM. Though, from what I understand, as long as I have an EFS backup, I can fix it. Is that right?
Yep you should be fine. I didn't have issues when going from stock to custom. Still -- I'd try out an Oreo rom before jumping back to stock.
dunderball said:
Yep you should be fine. I didn't have issues when going from stock to custom. Still -- I'd try out an Oreo rom before jumping back to stock.
Click to expand...
Click to collapse
Y'know, it didn't actually occur to me, and this may be a silly question, but now I'm wondering if there's actually any need to run a stock firmware update before going to newer custom ROMs? The reason I ask is because this was a thing with my Nexus 5x. Newer LineageOS builds sometimes needed a bootloader and radio update.