JWR66Y update for the Nexus 10? - Nexus 10 General

We got a tip and a screenshot of this for the N10, but I'm starting to suspect it was fake. Has anyone at all gotten the JWR66Y update today?
http://i.imgur.com/hIQjX2h.png

dunno about the n10, but the GN yakju update has been confirmed so it is likely i suppose.
http://android.clients.google.com/p....signed-yakju-JWR66Y-from-JWR66V.1b0ac7df.zip
edit: i got the link from this thread: http://forum.xda-developers.com/showthread.php?t=2414147

Saw that one, but I'm just looking for a confirmation on the N10.

Archon810 said:
Saw that one, but I'm just looking for a confirmation on the N10.
Click to expand...
Click to collapse
I got a very small system update last night on my N10. Not sure what the build number was on it. Can check later.

Just checked but still no updates for my N10, build JWR66V..I heard it's only a little security fix but I'm not sure about that
Inviato dal mio Nexus 10 usando Tapatalk 4

AleCai said:
Just checked but still no updates for my N10, build JWR66V..I heard it's only a little security fix but I'm not sure about that
Inviato dal mio Nexus 10 usando Tapatalk 4
Click to expand...
Click to collapse
Yes, JWR66Y is a very small update. There are no new features. It's purely a security update.

RogueWing said:
I got a very small system update last night on my N10. Not sure what the build number was on it. Can check later.
Click to expand...
Click to collapse
Just checked. That is the update I got last night.

nothing so far in my Nexus 10 or Nexus 4, but sounds like is real.. mostly bug fixes I guess.

Got it right now but installation failed because I had CWM touch recovery installed...
Now I can't get the update again...
Enviado desde mi Nexus 10 usando Tapatalk 2

Can you go into your /cache folder and get the name of the zip file?

I got it just now. Wouldn't update because I'd changed Velvet.apk now I can't get it again.
EDIT:
Ah, nice it was in cache like someone mentioned above. It is indeed JWR66Y
EDIT 2:
Copied it to the internal, flashed in TWRP. It said patching, removed root, but failed on flashing recovery.
I'll upload the file in a moment.

OK. If you guys get the update again, please look in your /cache folder and give us the filename before you try to install it. Once we have the filename, we can provide the link to the file on Google's server. That way, if you can't get it again, it won't matter because you can just download the file directly. Thanks!

Check above
---------- Post added at 09:45 PM ---------- Previous post was at 09:38 PM ----------
I couldn't sideload it using the stock recovery :/ It failed on "setperms"
I'll have to grab factory image and unpack it into a CWM zip at some point.

If anybody could make a zip for CWM thatd be awesome :good:
mine also fails at permissions - check this thread out seems to be figured out -http://forum.xda-developers.com/showthread.php?t=1745781&page=53
a line needs to be changed to #set_perm(0, 0, 0544, "/system/etc/install-recovery.sh"); because of the way the daemon is in supersu if somebody could whip up a manta zip like the ones they have were set

oldblue910 said:
OK. If you guys get the update again, please look in your /cache folder and give us the filename before you try to install...
Click to expand...
Click to collapse
I have JWR66Y downloaded from Google and haven't installed it yet on my unrooted N10. Do you need to be rooted to see the files in the /cache directory?
---------- Post added at 03:39 PM ---------- Previous post was at 03:14 PM ----------
Here's where the action is on this topic:
http://forum.xda-developers.com/showthread.php?t=2413535&page=15

So I ended up making my own zip for CWM, changed the line I mentioned above and removed the asserts. Worked fine here but flash at your own risk. Flashed supersu 1.51 after flashing the update and answered No to fixing the recovery.
**Only use if you are on Google's stock JWR66V odex hasn't been tested with other "stock" roms

NeoMagus said:
So I ended up making my own zip for CWM, changed the line I mentioned above and removed the asserts. Worked fine here but flash at your own risk. Flashed supersu 1.51 after flashing the update and answered No to fixing the recovery.
Click to expand...
Click to collapse
So, it appears that it's a small security update, it'll remove root, and I can expect to have problems with it with TWRP. Nice. Got it early this afternoon, will have to mess with getting it working later.

Jackietreehorn said:
So, it appears that it's a small security update, it'll remove root, and I can expect to have problems with it with TWRP. Nice. Got it early this afternoon, will have to mess with getting it working later.
Click to expand...
Click to collapse
Dude, every OTA ever in history removes root and reflashes stock recovery. This isn't news. Just flash and then re-root. It's a Nexus. You can do that.
Sent from my Xoom using Tapatalk 4

The 1.8MB OTA has arrived in UK:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

NeoMagus said:
So I ended up making my own zip for CWM, changed the line I mentioned above and removed the asserts. Worked fine here but flash at your own risk. Flashed supersu 1.51 after flashing the update and answered No to fixing the recovery.
Click to expand...
Click to collapse
Will it work with twrp as well?
Sent from my Nexus 10 using xda app-developers app

Related

Need a quick tester!

I need someone to test a PA build I have built. I posted a build for the Sprint GNote 2 already and just need someone to test this before I post. Please lmk if you can help.
Once I get confirmation it boots and everything seems to be working I can post http://d-h.st/TcW and flash these gapps with it http://d-h.st/X4a
Downloading now.
Sent from my SCH-I605 using Tapatalk 2
---------- Post added at 10:51 PM ---------- Previous post was at 10:35 PM ----------
flashing fails with TWRP recovery. Gapps flash and rom doesn't
---------- Post added at 10:52 PM ---------- Previous post was at 10:51 PM ----------
flashing fails with TWRP.
Gapps flash okay.
Rom fails.
What does it say exactly? Can you check md5?
Just shows failed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SCH-I605 using Tapatalk 2
Its gotta say a bit more. I appreciate all the feedback youve given me this far though.
I tried with and without the forcing of md5
Sent from my Nexus 7 using Tapatalk 2
Just to be clear, you do have a VZW GNote 2 running a VZW rom right?
Yes. Verizon gnote 2 running beans v2 with twrp recovery.
Wiped system, data, cache. Tried flashing PA a few times and gave me errors... then tried gapps for the heck of it and flashed fine.
Sent from my Nexus 7 using Tapatalk 2
Hmm ok then. I dont see why its not flashing. Ill have another build to try in the morning. Thanks for helping so far!
EDIT: If you can or whoever else, try this one http://d-h.st/TcW md5sum didnt match with first one when it got uploaded. Hoping thats why it wouldnt flash. LMK!
just throwing this out there but i bet it needs to be flashed with cwm recovery just like sbrissens cm10 build...ill give it a go!
flashed fine with CWM recovery and booted up...
droidstyle said:
just throwing this out there but i bet it needs to be flashed with cwm recovery just like sbrissens cm10 build...ill give it a go!
Click to expand...
Click to collapse
Ya, twrp does not play nice with cm builds... On top of that we don't even have the "official" twrp recovery. We are using a Sprint version and I have tried to flash the official build but it takes me back to stock recovery. I am sure you already knew that though my friend, judging by your infinite wisdom! I would definitely like to see PA on the N2 though! :good: It's too bad cause I can't stand any other recovery besides twrp...
shojus said:
Ya, twrp does not play nice with cm builds... On top of that we don't even have the "official" twrp recovery. We are using a Sprint version and I have tried to flash the official build but it takes me back to stock recovery. I am sure you already knew that though my friend, judging by infinite wisdom! I would definitely like to see PA on the N2 though! :good: It's too bad cause I can't stand any other recovery besides twrp...
Click to expand...
Click to collapse
this PA build is running damn smooth for a test!
droidstyle said:
this PA build is running damn smooth for a test!
Click to expand...
Click to collapse
OH YA!!
Alright thank you guys for testing! I'll post it up in a bit
Sent from my SPH-L900 using Tapatalk 2
Just so people know, the assert issues with TWRP are not isolated to our device, as I have seen similar issues when trying to flash CM on other devices. Not sure why.
imnuts said:
Just so people know, the assert issues with TWRP are not isolated to our device, as I have seen similar issues when trying to flash CM on other devices. Not sure why.
Click to expand...
Click to collapse
yes I ran into this on the S3 aswell...thank you for bringing us CWM!!!
So to say the least we should flash the unofficial cwm recovery if we plan on flashing CM roms at some point?
Sent from my Unlocked & Loaded Beast!
pschatz12 said:
So to say the least we should flash the unofficial cwm recovery if we plan on flashing CM roms at some point?
Sent from my Unlocked & Loaded Beast!
Click to expand...
Click to collapse
I would say any ROM that has device asserts in it. At least until TWRP can be fixed to process them properly. And truthfully, anything that gets flashed via recovery should have asserts to make sure you're flashing on the proper device, but many rarely include them if not built from source (myself included).
GPS working on this build???
Imnuts you post all over and are extremely knowledgeable! !!! Are you a developer? !
Sent from my Unlocked & Loaded Beast!

New Software Update for Verizon GS4

I hooked my 16GB GS4 up to my computer a few hours ago to do some backup because I am replacing it with the 32GB S4 (arriving Wednesday). The Verizon Software Upgrade Assistant did an update first, then it showed I had an update available for the phone itself. It took about an 1 1/2 - 2 hours (ridiculous I know) and it is finally done. Looking for changes, biggest I see is ability to move apps to SD Card. Can't remember what my storage was before, but maybe this is the update to give that little bit of extra space too? I assume those went hand in hand as 1 update. Any one else got this yet? Any other changes you see?
I just read last night that there is some fear that Vnz patched the boot loader. My 32gb arrives today and hope I have a chance to opt out so I can root. What's the new version number?
Go to about phone and screen shot us the info plz
Sent from my SCH-I545 using xda premium
Count me as one very interested in this. Mine is scheduled to arrive tomorrow and want to preserve the root option if I can.
I just downloaded the update via the installer as well but did not install. Where does this get saved on my phone?
Sent from my SCH-I545 using xda premium
From what I can tell there is nothing that will stop someone from making this device able to root. It'll just take some time. I'd there's a will there's an XDA.
Sent from my SCH-I545 using xda app-developers app
Deleted...
My S4 comes tomorrow. Hopefully someone will let us know if the current root exploits work on the OTA.
Ryno77 said:
I just downloaded the update via the installer as well but did not install. Where does this get saved on my phone?
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
It should be in the /cache partition. You'll need root access to get at it if I'm not mistaken.
Per kies...
Current firmware version: PDA:MDK / PHONE:MDK / CSC:MDK (VZW)
Latest firmware version: PDA:ME7 / PHONE: ME7 / CSC:ME7 (VZW)
Edit: there is a tmpD385.tmp on my PC which had appeared when kies started "downloading file for firmware upgrade" and is now at 971,207KB in size. Progress bar shows 41%
EDIT2: I now have a I545VRUAME7_I545VZWAME7_I545VRUAME7_HOME.tar.md5 which is being flashed.
Just got my 32gig S4 yesterday. fired it up and rooted it with no issues..
However didnt see any notice for an update. Even if they have one, you have to accept the OTA.. just dont.
vacaloca said:
It should be in the /cache partition. You'll need root access to get at it if I'm not mistaken.
Click to expand...
Click to collapse
Not rooted and I don't dare install without knowing if you can Odin back after install.
Sent from my SCH-I545 using xda premium
KidJoe said:
Per kies...
Current firmware version: PDA:MDK / PHONE:MDK / CSC:MDK (VZW)
Latest firmware version: PDA:ME7 / PHONE: ME7 / CSC:ME7 (VZW)
Edit: there is a tmpD385.tmp on my PC which had appeared when kies started "downloading file for firmware upgrade" and is now at 971,207KB in size. Progress bar shows 41%
Click to expand...
Click to collapse
And there is already a Kernel out for ME7 which would make me believe that root is already possible on the new update. This update is obtainable with a custom recovery installed, correct?
(sorry for the picture size)
Before...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After update...
and I'm uploading I545VRUAME7_I545VZWAME7_I545VRUAME7_HOME.tar.md5.zip to mega. I'll post link as soon as it completes. (approx 45 min)
KidJoe said:
I'm uploading I545VRUAME7_I545VZWAME7_I545VRUAME7_HOME.tar.md5.zip to mega. I'll post link as soon as it completes. (approx 45 min)
Click to expand...
Click to collapse
I found a file named SCH-I545_VZW_1_20130613175748_jy2r2k5mdm.zip.enc2 in the IE cache directory, 1.74 GB. How do I extract the contents?
vacaloca said:
I found a file named SCH-I545_VZW_1_20130613175748_jy2r2k5mdm.zip.enc2 in the IE cache directory, 1.74 GB. How do I extract the contents?
Click to expand...
Click to collapse
because its extension is ENC2 I would think that is the encoded copy... you might not be able to extract.
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
Just got it loaded, and I'm working, so I haven't had time to really do anything with it yet.. One thing I did notice... see the "Secure boot status" in the AFTER picture? that wasn't there before the upgrade. Could this be the KNOX update?
KidJoe said:
because its extension is ENC2 I would think that is the encoded copy... you might not be able to extract.
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
Just got it loaded, and I'm working, so I haven't had time to really do anything with it yet.. One thing I did notice... see the "Secure boot status" in the AFTER picture? that wasn't there before the upgrade. Could this be the KNOX update?
Click to expand...
Click to collapse
Yes, I'm aware, I tried CheckFusDownloader_v2.1, but perhaps I'm entering the wrong settings. Where did the file get stored when it got downloaded to the phone, in /cache?
vacaloca said:
....Where did the file get stored when it got downloaded to the phone, in /cache?
Click to expand...
Click to collapse
I don't have a SIM in my S4 right now, so I used Kies on my PC to update via USB, rather than OTA.
Also, this update does include Apps 2 SD
KidJoe said:
I don't have a SIM in my S4 right now, so I used Kies on my PC to update via USB, rather than OTA.
Also, this update does include Apps 2 SD
Click to expand...
Click to collapse
lol, so did I, I was wondering where in your computer or phone you got the un-encrypted copy from.
root
lost root after the update and voodoo ota root protector doesn't seem to be able to restore it.

Stagefright Fix

I have pulled the appropriate libs from the OH1 update and put them in a flashable zip for those of you who want a fix for the stagefright Vulnerability, but don't want to update. I am currently on the OC5 build and I flashed the zip and the vulnerability has been fixed.
IMPORTANT: I have only tested this on the stock deodexed OC5, I can not speak on if it will work for anything else. If you're not on the OC5 build flash at your own risk!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not responsible for anything that may or may not happen to your device, I am just telling you my experience. I recommend having a backup as always.
DOWNLOAD:
https://www.androidfilehost.com/?fid=24052804347798028
Sent from my note 3 running Beast Mode rom
Awesome work man..... nice job!!
Hello,
Can I use this on MJ4?
Thanks!
Sent from my SM-N900P using Tapatalk
Was this designed to be installed in recovery?
BHurst said:
Hello,
Can I use this on MJ4?
Thanks!
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Make a backup and try but since it was for lollipop base it may not.... try it and let us know.
Thanks,
Chaz187
---------- Post added at 11:22 AM ---------- Previous post was at 11:22 AM ----------
dcwashington said:
Was this designed to be installed in recovery?
Click to expand...
Click to collapse
Yes flash in recovery
Thank you @Chaz187
Sent from my note 3 running Beast Mode rom
Thank you for this JB
Hey JoHnNYBlaZE716, the binary-script removes the calendar and stuff since the script was from another package. I am not that familiar with Stagefright but I assume only the library files are needed since they seem to be the only thing in the system path.
Code:
delete("/system/app/Calendar.apk");
delete("/system/app/GoogleCalendar.apk");
delete_recursive("/system/app/GoogleCalendar");
delete_recursive("/system/app/CalendarGoogle");
delete_recursive("/system/app/Calendar");
Sorry I took a zip I had laying around, I'll fix that asap
Sent from my note 3 running Beast Mode rom
I have posted a new link for the stage fright fix that doesn't have the delete calendar script in the updater script. Thanks @dyehya for bringing to my attention and for making the new zip. I am currently without a pc at the moment so you were a great deal of help.
Sent from my note 3 running Beast Mode rom
The new fix did not work for me.
The checker still shows me as vulnerable.
TrofeoSC said:
The new fix did not work for me.
The checker still shows me as vulnerable.
Click to expand...
Click to collapse
One of the 2 apps will show as vulnerable still due to Google not catching the issue all the way. It is something on googles end that's all I know. There will most likely be another update fixing it completely. The app you're using should only show one of them in red correct?
You can read more in the article I have linked below
http://www.securityweek.com/android-stagefright-vulnerability-not-patched-properly-google
Sent from my note 3 running Beast Mode rom
Yes, only the top one in the list.
Thanks
JoHnNYBlaZE716 said:
One of the 2 apps will show as vulnerable still due to Google not catching the issue all the way. It is something on googles end that's all I know. There will most likely be another update fixing it completely. The app you're using should only show one of them in red correct?
You can read more in the article I have linked below
http://www.securityweek.com/android-stagefright-vulnerability-not-patched-properly-google
Sent from my note 3 running Beast Mode rom
Click to expand...
Click to collapse
Dude it's been a while u had shown ur OC5 custom rom on tx_dbs_tx's thread.
i guess that's what u r using right now. are you planning to release it?
Will I b able to keep stock root if I do the full update?
Sent from my SM-N900P using XDA Free mobile app
Yes i plqn on releasing my rom it should be about done soon, just touching up a few things. Amd if you take the update for the OH1 then yes you will lose root and go back to stock. You can just flash this zip for the stagefright fix if you want.
JoHnNYBlaZE716 said:
Yes i plqn on releasing my rom it should be about done soon, just touching up a few things. Amd if you take the update for the OH1 then yes you will lose root and go back to stock. You can just flash this zip for the stagefright fix if you want.
Click to expand...
Click to collapse
That's what I keep saying about my theme until I find something else that needs themed, lol.
Sent from my Galaxy Note 3 using AnaKonda Tapatalk
AnaKonda Theme
eREDicate Theme
JoHnNYBlaZE716 said:
Yes i plqn on releasing my rom it should be about done soon, just touching up a few things.
Click to expand...
Click to collapse
Man that answer hasnt changed since july end...hehe !!
I guess you are busy with ur stuff. Btw do release if u get time or else the device is as good as dead.
and any major difference betn OC5 and OH1?
and hopefully u release fix 2 soon too mate....:highfive:
I am using fre3 4.4.4 KitKat ROM and I am on OC5, flashing your zip just makes my phone get stuck on the Samsung logo. Anything special I need to do? Clearing Davik and Cache doesn't fix it.
joelstitch said:
I am using fre3 4.4.4 KitKat ROM and I am on OC5, flashing your zip just makes my phone get stuck on the Samsung logo. Anything special I need to do? Clearing Davik and Cache doesn't fix it.
Click to expand...
Click to collapse
I honestly can't answer your question, I've personally only flashed it being on a stock oc5 rom. No one has reported any issues so I don't know why it wouldn't work. The files were pulled from the oh1 update for the sprint note 3
Sent from my SM-N920P using Tapatalk

[ROM][5.1.1][Project Fi] LVY48F, Stock, Rooted, Decrypted kernel

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the new Project Fi LVY48F 5.1.1 stock ROM. The rom has simply been rooted and made flashable by @jermaine151. This is based on @Stephen's prior work. So is this thread OP. lol
Rom Features
-Stock Android 5.1.1 Project Fi LVY48F base
-Rooted
-Busybox
-No force encrypt kernel
-Persistent ADB enabled
-Custom DPI set at 460
Flash instructions
1. Download ROM from link below
2. Backup current ROM
3. Flash ROM using TWRP*
4. Profit?
*For best results clean wipe but may not be needed if coming from a previous build.
Disclaimer
We are not responsible for any damage done to your device, either hardware or software. You use this ROM at your own risk. We will try to help resolve any issues you have, but we make no guarantees in doing so.
Download
LVY48F_Odxed_Stock.zip
Custom DPI
LVY48F_Odxed_Stock.zip
Mirror
MD5: 5a7a592b210cd17d7b18810b719bc9ac
Radios, Bootloaders, and More:
[FXZ][OTA] Nexus 6 Recovery Flashable Fastboot Files (Unlocked Bootloader Only)
Scroll down to "LVY48F (5.1.1 Project Fi bugfix update 20150910)" and "Click to Show Content." These can be flashed in custom recoveries.
Suggested Mods:
Xposed
GravityBox
Nexus 6 Double-Tap to Wake
Lightflow Lite or Lightflow Full*
*Lightflow Tutorial
If anyone has other mods to suggest, feel free. These are the ones I use and they work great with this ROM.
Thanks @GuyInDogSuit!!
@GuyInDogSuit yes, I changed my DPI. Sorry about that.
Cheers, I will close my thread off now, as this is newer. Thanks for hosting.
jermaine151 said:
Thanks @GuyInDogSuit!!
@GuyInDogSuit yes, I changed my DPI. Sorry about that.
Click to expand...
Click to collapse
Is it set to 460? That's what ROM Toolbox is telling me.
Just flashed this and everything looks to be working great. Thanks again for doing this, the upgrade prompts were driving me bonkers. I did notice the dpi change and I like it. Much cleaner.
Sent from my Nexus 6 using Tapatalk
Anyone get Android Pay working on this?
can you have one with the Stock DPI please appreciate it and thx
Sent from my Nexus 6 using Tapatalk
davemlinux said:
can you have one with the Stock DPI please appreciate it and thx
Click to expand...
Click to collapse
I don't know how to change it other than with an app once it's flashed.
apristel said:
Anyone get Android Pay working on this?
Click to expand...
Click to collapse
I have Android Pay working on the official LVY48F image, but I'm pretty sure the DPI change that was done with this will not work with it. Also had to hold off on rooting until after it was set up.
Sorry guys. I didn't mean to change it in the rom. I just wanted it set to 460 on my phone. I can give you a different build.prop file or correct it and upload again. Give me a second and I'll upload a correct build and a 2nd flashable zip to correct dpi only.
EDIT: Attached is the flashable zip to set the density to 560 which is stock. I am uploading the full ROM with it corrected and I will post the link here when it's done.
P.S. If someone tries the attached zip, please post and confirm that it fixed your DPI. Thanks!
Here's the link to the same build with the stock 560 DPI: http://d-h.st/K2Ee
thx boss the way o wanted appreciate it
Sent from my Nexus 6 using Tapatalk
I'm getting a system update notification. Go ahead, or ignore?
whiskeymcirish said:
I'm getting a system update notification. Go ahead, or ignore?
Click to expand...
Click to collapse
You shouldn't be receiving an update message is you're running this build. Check your settings about and make sure that your build number is LVY48F. The update will fail if you try to accept it.
I got the update notification when I first booted but have not seen it since.
Was running the wrong version, 48C, my bad. Thanks guys.
whiskeymcirish said:
I'm getting a system update notification. Go ahead, or ignore?
Click to expand...
Click to collapse
If you ever get another one, don't update. It'll fail if you have a custom recovery. Even if you had stock recovery, you'll then lose root and be encrypted again. Wait for a ROM update.
^^ what he said, learned that the hard way
Sent from my Nexus 6 using Tapatalk
GuyInDogSuit said:
If you ever get another one, don't update. It'll fail if you have a custom recovery. Even if you had stock recovery, you'll then lose root and be encrypted again. Wait for a ROM update.
Click to expand...
Click to collapse
I think it'll fail even if you're so much as rooted.
#WhiteUIsMustDie, #EndDarkAppOppression
Hello everyone,
I'm running into an issue here, I flashed this ROM so I could activate my Project Fi invite. Unfortunately, I am getting the same message as I've gotten on every other ROM. First, I will get error T301 and cannot do anything I'm the app. Eventually I get around it by attempting to choose network operators in the settings but get stuck at the part where I am trying to transfer my number. After typing in all the account info and selecting next, I get a notification at the bottom of the screen that reads "something went wrong".
I've been wondering, do I need to flash any of the radios, base (baseband?), or any other of the things that are linked in the OP? If so, which ones?
P.S. I have never flashed a different radio or bootloader etc. on this phone since I purchased in May.
If that's not the case does anyone have any idea what could be the issue? Any help is highly appreciated and I thank you in advance!
Sent from my Nexus 6 using Tapatalk

October OTA and factory Images are available

https://developers.google.com/android/images#angler
WTH ?!?
No one stranges that there is a regression in build number from the October update?!?
September OPR6.170623.019
October OPR5.170623.007
October update was supposedly built around the same date that September update (?!?), it's from an earlier branch code (OPR5) opposed the September update (OPR6).
Can't understand this...
How to install the build on the rooted Nexus 6P
Actually it is the same brunch, 17063 , maybe earlier revision.
akashkyh said:
How to install the build on the rooted Nexus 6P
Click to expand...
Click to collapse
I simply downloaded the full factory image, unzipped. Edited the flash-all.bat file and removed the "-W"
Then run the file and just before it rebooted , went to bootloader, flashed TWRP, booted to recovery, flashed root and ElementalX 5.0.4 and I am done.
Can anyone provide a flashable OTA for twrp?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My Pixel?
pezzku said:
View attachment 4291034View attachment 4291035
My Pixel?
Click to expand...
Click to collapse
it's only a text typo.The update is for the 6P.
akashkyh said:
Can anyone provide a flashable OTA for twrp?
Click to expand...
Click to collapse
hmm?? Just grab the full ota and you can flash it via TWRP
onesolo said:
it's only a text typo.The update is for the 6P.
hmm?? Just grab the full ota and you can flash it via TWRP
Click to expand...
Click to collapse
Can I flash flash the official OTA in twrp?
akashkyh said:
Can I flash flash the official OTA in twrp?
Click to expand...
Click to collapse
Again?!?!
Yes u can!!!! You can flash the full OTA in TWRP with no problems!!! It will flash unconditionally the system partition and won't delete any thing from internal storage!!! You will loose any modification that you'll have on system, except TWRP.
Im getting error 7 while installing OTA via TWRP... any help??
akashkyh said:
Im getting error 7 while installing OTA via TWRP... any help??
Click to expand...
Click to collapse
First make sure you're installing the OTA for the 6P and not for another device, also confirm your checksum is correct. Also you could check this video https://www.youtube.com/watch?v=h5Kp_jybnjQ
The OP posted the link directly to the SHAMU (Motorola Nexus 6) section .. not ANGLER (Huawei Nexus 6P) so be careful.
The correct direct link is https://developers.google.com/android/images#angler
wattsja said:
The OP posted the link directly to the SHAMU (Motorola Nexus 6) section .. not ANGLER (Huawei Nexus 6P) so be careful.
The correct direct link is https://developers.google.com/android/images#angler
Click to expand...
Click to collapse
Thanks for spotting my mistake
Fixed it in the main page.
I am confused because of the build number. Does "OPR" mean Oreo Pre-Release?
Sent from my Nexus 6P using Tapatalk
akashkyh said:
Im getting error 7 while installing OTA via TWRP... any help??
Click to expand...
Click to collapse
The same here. Don't know why. I already use this method previously on previous OTAs and never had this error!! Any ideas guys?!
Sent from my Nexus 6P using Tapatalk
I didn't use the OTA.
Modified the flash-all.bat and then re-installed root/elementalX and twrp
akashkyh said:
Im getting error 7 while installing OTA via TWRP... any help??
Click to expand...
Click to collapse
Try using the OTA image, not the factory image linked in the OP.
https://developers.google.com/android/ota#angler
placebo_domingo said:
Try using the OTA image, not the factory image linked in the OP.
https://developers.google.com/android/ota#angler
Click to expand...
Click to collapse
wth?? did you read my post?? I was using the full ota image!!!
I discovered, in the TWRP thread, that it's a bug that TWRP has with Oreo OTAs!!! Have to edit the updater script file and remove the first two lines.
onesolo said:
wth?? did you read my post?? I was using the full ota image!!!
I discovered, in the TWRP thread, that it's a bug that TWRP has with Oreo OTAs!!! Have to edit the updater script file and remove the first two lines.
Click to expand...
Click to collapse
In this case It would be easier to simply download the full factory image and flash manually the separate images.

Categories

Resources