Hi, no issue here in fact I am loving the ROM. One curious thing. If I update via system update, the size of the nightly is 279mb whereas if I download from dl.omnirom.org, the size is around 180mb.
Can any one account for the discrepancy ?
Thanks A|C
I'd like to know, too. Just noticed it this morning.
Sent from my Nexus 4 using Tapatalk
I guess that's because of another compression of the file so the updater can better compare the changes of the new build.
Anyone else having problems with twrp don't finding the update zips!?
It worked fine at the first builds, but with the last two nightlys it doesn't work anymore!?
Twrp stops with error message saying that the file is not found, but it's located in the right directory!?
Is there any solution?
Gesendet von meinem C6603 mit Tapatalk
Hmm, I had no problem this morning with the 12/10 update. TWRP 2.6.3.3 found Franco, LTE enabler, GAPPS, SuperSU without any problem.
Sent from my Nexus 4 using Tapatalk
bruce7373 said:
Hmm, I had no problem this morning with the 12/10 update. TWRP 2.6.3.3 found Franco, LTE enabler, GAPPS, SuperSU without any problem.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I think it is somehow related to the external sdcard.
In filemanagers it sometimes shows as "emulated/0" and sometime as "sdcard1"
Strange thing, above all it worked before and now it doesn`t anymore!?
@Chainfire
FlashAfterInstall seems to be broken
Related
As you can see my dates are a bit off. Ive done some searching and found others who have had the same issue. No definite solutions or explanations have been provided. This is super frustrating. Not sure why its happening or how to fix it. Im running the latest twrp, before that I was running cwm with the same results. I just did a backup about an hour ago and i couldnt tell you which one it is. Any help would be much appreciated.
Idk it was like this on the sprint gs3 also with twrp. So I just name the backups myself with the date I backed up.
Sent from my SPH-L720 using Tapatalk 4 Beta
The TWRP source is messed up and no one cares to dig in and fix it. Just manually name your backups.
I'm using philztouch and have not noticed the problem. Also a cool feature of that recovery is that it says what rom it is in the title, so even if the date happens to be off, the file name will give away what backup it is.
Sent from my SPH-L720 using xda premium
That has been an issue for over a year I believe. All CWM and TWRP versions that I am aware of have it. One of the Android updates broke the date function from what I recall. Might have been Jellybean. Since you can just rename the backups to whatever you want I guess the priority is at the very bottom of the list.
Sent from my SPH-L720 using Tapatalk 4 Beta
I use twrp 2.5.0.2 on this device and do all my nands to external and name them what they are.
Sent from my SPH-L720 using xda premium
Much appreciated fellas!
Sent from my Nexus 7 using Tapatalk HD
try this
BiffTirkle said:
As you can see my dates are a bit off. Ive done some searching and found others who have had the same issue. No definite solutions or explanations have been provided. This is super frustrating. Not sure why its happening or how to fix it. Im running the latest twrp, before that I was running cwm with the same results. I just did a backup about an hour ago and i couldnt tell you which one it is. Any help would be much appreciated.
Click to expand...
Click to collapse
Try Dream TWRP I installed it and my BU dates have been correct.
Yeah. Some have said there's a setting that you can change to fix that. I've yet to find it.
this is my first time making an account/posting on xda after being a long time reader and user. just need some help with my nexus 7 32gb WiFi (Australian model) i have loved this tablet and I have never had a problem with it, its unrooted and has never been dropped or anything like that, i updated it to 4.3 ota last night and almost instantly after that I have noticed it keeps rebooting itself like so many other people have problems with on earlyr versions like 4.2, please tell me what I can do to fix this, I can't find any straight help, my location is off and always has been, but I have noticed every now and again I would notice (on earlyr version) fused location would always stop working and ask me to force close randomly, that now doesn't happen but instead it retstarts, so do u think this could be the problem? any help would be awesome, thanks.
If you're having a problem with 4.3 you can try two things.
1. Revert back to 4.2.2
2. Try a rooted official stock ROM.
Sent from my SGH-T999 using Tapatalk 4 Beta
fixed it!!
TheLastSidekick said:
If you're having a problem with 4.3 you can try two things.
1. Revert back to 4.2.2
2. Try a rooted official stock ROM.
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I fixed the proble,m, I found a site that finally gave me a good option to try besides rooting as I don't want to root my nexus 7, turns out HD widgets was cashing the issue, but the issue only showed up after this update, thanks for ur help though.
adex9 said:
I fixed the proble,m, I found a site that finally gave me a good option to try besides rooting as I don't want to root my nexus 7, turns out HD widgets was cashing the issue, but the issue only showed up after this update, thanks for ur help though.
Click to expand...
Click to collapse
Ah good note. Thanks that's helpful for future knowledge. Glad all is well for you.
Sent from my Nexus 7 using Tapatalk 4 Beta
I've had random reboots on 4.2.2 and one since updating to 4.3. Usually happens when I am mounting or unmounting a USB drive, but sometimes it's for no apparent reason.
Sent from my SGH-I747M using xda app-developers app
I have the latest flash apk installed, flash settings shows up in my drawer, I have uninstalled and reinstalled, but still no luck getting flash to work with any browser (boat, firefox, dolphin beta). It runs fine on my Nexus 7 (2013). I even tried fix permissions on a lark. Running stock rooted image 4.3. Anybody have any suggestions on what to try?
Sharkeyd said:
I have the latest flash apk installed, flash settings shows up in my drawer, I have uninstalled and reinstalled, but still no luck getting flash to work with any browser (boat, firefox, dolphin beta). It runs fine on my Nexus 7 (2013). I even tried fix permissions on a lark. Running stock rooted image 4.3. Anybody have any suggestions on what to try?
Click to expand...
Click to collapse
11.1.115.69 works nice here with aosp-browser and firefox (sine update from august the 6th brfore firefox was crashing). Stock 4.3 from factory image. Sometimes when reading of this different experience with 4.3 I can't stand the feeling factory image, ota and flashable zip all have slightly different issue...
I went back to full factory image with no root, got flash working then manually rooted. Everything works now.
Sent from my Nexus 7 using Tapatalk 2
Sharkeyd said:
I went back to full factory image with no root, got flash working then manually rooted. Everything works now.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Incredible!!! I was using, after updating to 4.3 the Flash 11.111.29 and for a few days it worked fine, both with Firefox and aosp-browser. Then stopped suddendly!!!
Now I've downloaded the 11.115.69 as you suggested but in the fullscreen it crashes both firefox and aosp. Does it work in full screen to you??
Yeah works great in full screen. I prefer boat browser, just make sure to enable flash in settings. How did you achieve root? Did you flash a prerooted image, or stock then rooted that?
Sent from my Nexus 7 using Tapatalk 2
Sharkeyd said:
Yeah works great in full screen. I prefer boat browser, just make sure to enable flash in settings. How did you achieve root? Did you flash a prerooted image, or stock then rooted that?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
My device is stock and then rooted, does it make difference???
To me makes crashes or lagging, both firefox and aosp. Which browser do you use?? Are you runnibg 4.3???
Inviato dal mio GT-I9100 con Tapatalk 2
Dodazza said:
My device is stock and then rooted, does it make difference???
To me makes crashes or lagging, both firefox and aosp. Which browser do you use?? Are you runnibg 4.3???
Inviato dal mio GT-I9100 con Tapatalk 2
Click to expand...
Click to collapse
Yes I'm on 4.3. I had read about flash and issues with prerooted images, so I hoped that was your problem. I use boat browser, like I said before just make sure you allow flash in the settings. If you still can't get it to work, I recommend going back to unrooted stock and starting over. First download flash player, then flash the latest superuser. That's what got me fixed.
Sent from my Nexus 7 using Tapatalk 2
Hi all - I just received a notice on my Nexus 7 that there is a system update to install. I already installed 4.3 build JWR66V a couple weeks ago. Anyone know what this update is? I can't seem to find any information anywhere. My device is unlocked and rooted, running stock.
Yeah, google has released a newer version, so if you're on stock, why not update?
Sent from my Nexus 7 using Tapatalk 4
It's an update from build JWR66V to JWR66Y, still Android 4.3.
If it's an OTA update, always install it.
It fixes a couple of issues after the 4.3 update
Sent from my Nexus 7(2012) that has zero issues.
Is it possible to update via ota when the device is unlocked and rooted? I updated it but it still says JWR66V, not Y. But when I look for an update it says up to date.
Gesendet von meinem Nexus 7 mit Tapatalk 4
Got the same issue as dakoookie
Sent from my Nexus 7 using Tapatalk 4
Will this update unroot it?
Yes you'll still recieve the update it just hasnt been pushed to you yet if it says up to date. Factory images for it are already up waiting on someone to make a zip for CWM
nikola1970 said:
Will this update unroot it?
Click to expand...
Click to collapse
OTA's always remove root
Apparently not. I updated but I still have root
Sent from my Nexus 7 using Tapatalk 4
Me too, but gives error when installing =(
Rooter and bootloader unlock
Had an error at then end of the installation but looks like it succeed to update it coz when i started my device it said that my applications are optimizating for the new version or something like that.
Build is JWR66V now, there is no any system updates now. Root is still there.
nikola1970 said:
Had an error at then end of the installation but looks like it succeed to update it coz when i started my device it said that my applications are optimizating for the new version or something like that.
Build is JWR66V now, there is no any system updates now. Root is still there.
Click to expand...
Click to collapse
Then the update failed the new OTA is JWR66Y
Lol the same questions.
Every.
Single.
Time.
FYI, I lost root.
Lost root also
NeoMagus said:
OTA's always remove root
Click to expand...
Click to collapse
Guess nobody believed me :silly:
Anybody working on a zip yet for the update??
If you lost root and it put you back on stock recovery just reflash your recovery then supersu
For the folks that are having "error" during the update, restart your n7 then clear cache and data from framework services and check for updates again and it should come up. Also make sure you at least have 80% battery level:good:
It's supposed to fix the phantom screen touch problem and a few other things I'm sure someone will come up with root G.B.Y.
Sent from my Nexus 7
There's an OTA .zip for build JWR66Y here... but there appears to be a problem with symlink permisssions.
But there is also a solution here http://forum.xda-developers.com/showthread.php?t=1745781&page=53 and a modified version of the OTA that fixes the permissions. Worked for me flashing via TRWP.
Incidentally, I also lost root after upgrading... not sure why... but not a big problem, as I reflashed SuperSU v1.51 in TWRP.
-----------------------------
Not quite sure what this very minor upgrade is supposed to accomplish, given 4.3 was only rolled out 4 weeks or so, ago.... but I suspect it has a lot to do with a minor screwup on Googles part, the details of which can be found here... http://forum.xda-developers.com/showthread.php?t=2382880.
I think (and I could be wrong), build JWR66Y is {AOSP JSS15J + Gapps}... in other words, JSS15J, released as Factory Stock instead of AOSP.
And the full factory image of JWR66Y is already available on the Google Developer website here and it's immediate predecessor, JWR66V has been 'pulled' and is no longer available for download.
Anyway, take a look at the above link, and you should see what I'm getting at.
Rgrds,
Ged.
grouper zip that was linked worked great here. No issues here now
The latest Android 7 Nougat firmware for SM-T817w, a Canadian version of the Tab S2, is out.
I did an OTA yesterday morning and it is now on firmware T817WVLU3CQDA. There was an update right after and now it is on NRD90M.T817WVLU3CQDA.DM.
I odined the TWRP (twrp_3.1.0-1_sm-t810_13317.tar) and twrp flashed the SuperSU (SuperSU-2.79-201612051815.aip) right after. It has TRWP recovery and root without even a glitch.
It probably takes a few week before Sammobile posts this official firmware.
Is this compatible with the T817T T-Mobile version?
I don't think so. You have to wait till that for t817t is released.
Hey man can you post a nandroid backup so us other users can try to go this route until the OTA is posted?
thanks
Sure, here it is, a link to the nandroid backup for those who need it. Restore it with TWRP.
https://drive.google.com/drive/folders/0B5aAz5mBnQAaczRVcXdtS3JPX3M?usp=sharing
Thank you man!!!
Thanks, running good n sexy
Sent from my SM-T817W using XDA Premium HD app
How does one install this?
I have TWRP, Rooted - installed rom manager, nandroid manager, busy box, all the dependencies - booted into recovery and when I click on restore, regardless of where it is (internal sd, external sd, external usb) no files are shown.. i've unzipped it to a folder etc..
Do I have to wipe out twrp and install clockwork mod instead?
myeepad said:
The latest Android 7 Nougat firmware for SM-T817w, a Canadian version of the Tab S2, is out.
I did an OTA yesterday morning and it is now on firmware T817WVLU3CQDA. There was an update right after and now it is on NRD90M.T817WVLU3CQDA.DM.
I odined the TWRP (twrp_3.1.0-1_sm-t810_13317.tar) and twrp flashed the SuperSU (SuperSU-2.79-201612051815.aip) right after. It has TRWP recovery and root without even a glitch.
It probably takes a few week before Sammobile posts this official firmware.
Click to expand...
Click to collapse
Just extract the directory and restore from TWRP.
MastahOnetrack said:
How does one install this?
I have TWRP, Rooted - installed rom manager, nandroid manager, busy box, all the dependencies - booted into recovery and when I click on restore, regardless of where it is (internal sd, external sd, external usb) no files are shown.. i've unzipped it to a folder etc..
Do I have to wipe out twrp and install clockwork mod instead?
Click to expand...
Click to collapse
Do this if you have room and time. This way you will know what to put where and how:
Do a backup in TWRP then look at the folder it created and you will have an epiphany
Sent from my SM-T817W using XDA Premium HD app
iggut said:
Do this if you have room and time. This way you will know what to put where and how:
Do a backup in TWRP then look at the folder it created and you will have an epiphany
Sent from my SM-T817W using XDA Premium HD app
Click to expand...
Click to collapse
Lol thanks.. yes.. makes a bit of sense which is better than no sense.. who knew it had to be in TWRP/[long string of random numbers]/Backups
Its working now, except for a few things - I cannot transfer any files to the tablet via USB, there doesn't seem to be a developers option anywhere, I've lost the unified storage (damnit samsung..) and seems to have lost root.
Other than that, we're all good.
I flashed Magisk to root and you get dev option the same way... Just tap build 5 times. It is in a sub menu this time... Thank Samsung
myeepad said:
The latest Android 7 Nougat firmware for SM-T817w, a Canadian version of the Tab S2, is out.
I did an OTA yesterday morning and it is now on firmware T817WVLU3CQDA. There was an update right after and now it is on NRD90M.T817WVLU3CQDA.DM.
Click to expand...
Click to collapse
Really! I also have a T-817w (here in Canada)... and I still haven't got the update. I'm full stock / never rooted, eh.
Any idea why I'm not seeing it, even when manually checking for the update? (Sammobile still doesn't have the update either.)
On Rogers still no Nougat as of today
jgoedhard said:
On Rogers still no Nougat as of today
Click to expand...
Click to collapse
Hmmm. I'm wondering where in the world the OP found this ROM update. I haven't seen it posted anywhere.
Got the ota this morning build is now NRD90M.T817WYLU3CQE4
Sent from my SM-T817W using XDA-Developers Legacy app
DAE1964 said:
Got the ota this morning build is now NRD90M.T817WYLU3CQE4
Sent from my SM-T817W using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for the info. Now I have to unroot and get this OTA all over again.
DAE1964 said:
Got the ota this morning build is now NRD90M.T817WYLU3CQE4
Sent from my SM-T817W using XDA-Developers Legacy app
Click to expand...
Click to collapse
I gave it a day and battery life is similar to MM during sleep. Screen on is more demanding though. No noticeable lag. So far so good.
Sent from my SM-T817W using XDA-Developers Legacy app
Anyone noticied a bug in brightness and auto brightness?
Edit:Bug fixed After a reflash with smart switch
Yorgo1982 said:
Anyone noticied a bug in brightness and auto brightness?
Click to expand...
Click to collapse
Screen seems good but I set it to reading mode.
Sent from my SM-T817W using XDA-Developers Legacy app