I had the notification for 4.2 update yesterday morning and after pondering for the day I decided to initiate the upgrade which for some reason or another the update failed.
Is there anyway of finding out why the update failed and since the failure I've had no further notifications of the update so how can I try the update again?
Thanks
Jon
Update just failed for me too, which having read up, looked like it might have been because of having an alternate recovery installed.
So I removed the recovery .................UPDATE FAILED
Removed root.....................................UPDATE FAILED
Locked Bootloader..............................UPDATE FAILED
Full system wipe.................................UPDATE FAILED
You can force a retry by going to App,------All-------Google Services Framework and stopping the process and wiping the data
Then checking for update manually.
Some folks say you can have problems with Play and push notification after the framework wipe, but as I had gone the route of restoring to default, I wasn't bothered as I will just do the same again.
I wonder if there is a deeper issue however, than just my tablet.
Phil
jonchill said:
I had the notification for 4.2 update yesterday morning and after pondering for the day I decided to initiate the upgrade which for some reason or another the update failed.
Is there anyway of finding out why the update failed and since the failure I've had no further notifications of the update so how can I try the update again?
Thanks
Jon
Click to expand...
Click to collapse
did you guys did anything or change anything from system, like change the proxyprovider.apk for flash support? Mine failed through OTA and even via manual update but then I changed back the those apks and things went well and now I am on 4.2. Just sharing my experience and hope it can help you guys. somewhat.
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
My tablet updated just fine and it is both rooted and unlocked. My galaxy nexus which is the same (both rooted and unlocked) for some reason fails on the 4.2 update.
I had the exact same problem over the past two days, I don't have a custom recovery, just unlocked bootloaded and root.
just lou said:
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
Click to expand...
Click to collapse
OOOOOH! I froze then deleted the KOREAN IME app, because why the heck do I need a Korean app on my tablet? Hmm, so what are my options? Can I just redownload the Korean IME off the play store and OTA will work then?
Was there any other forced IME like Chinese that's 'baked in' to the Google ROM? I forgot if I may have deleted any others, but I think it was only Korean.
just lou said:
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
Click to expand...
Click to collapse
That explains it then I've deleted and frozen stock apps.
Thanks
I'm the same, i deleted system apps.
Is the only way to fix this to use a pc and adb the 4.1.2 zip and gapps?
Is there any way to fix it from the device itself?
(I've tried flashing the 4.1, 4.1.2 and 4.2 via CWM)
Would reflashing the 4.1 gapps help?
Sent from my Nexus 7 using xda premium
I had the same problem. Used titanium backup and the "integrate system apps updates into ROM" option and then couldn't update to 4.2.
Tried several things I read in this forum but nothing worked.
Had to erase everything and flash the stock ROM I downloaded from Google. They have a 4.2 stock ROM too so didn't need to update afterwards.
Then restore all your apps from backup and you are set.
Sent from my Nexus 7 using Tapatalk 2
Wow, all because a damn Korean IME app? Geez, what a pain, Google. :|
Chocoburger said:
Wow, all because a damn Korean IME app? Geez, what a pain, Google. :|
Click to expand...
Click to collapse
The alternative is that you restore your system folder to its original state (i.e. get hold of that Korean IME app, stick it back in /system/app and set the correct permissions). I had to do this with Google Wallet but it can be done if you know exactly what you've changed and avoids flashing a factory image and setting your device up again (albeit that Titanium makes this relatively painless now).
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
CFRTim said:
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
Click to expand...
Click to collapse
Me too. Also a 32gb N7. I owned it less than a week. Multiple factory resets didn't correct the issue either. I returned it to the store for a refund. Didn't want to keep a device that would never install updates.
I have 32 gigabyte Nexus 7 and it came with Android 4.2 out of the box so I guess no problems with the updates
Sent from my Nexus 7 using XDA Premium HD app
CFRTim said:
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
Click to expand...
Click to collapse
So your saying you opened it, turned it on, signed in.....then your status bar should show system update available, click it, accept, let it do its thing and it just failed?
Sent from my Nexus 7 using Tapatalk HD
If you search the forums this has been addressed and solved. You need to reflash the os - you don't need root. Use wugs toolkit. Its a problem on googles end where the nexus was formatted incorrectly, and a reflash fixes it.
Sent from my Nexus 7 using Tapatalk HD
Yep. Got the Android robot on his back, with the triangle/exclamation point on top of him, after downloading, restarting and almost complete install. I've tried multiple times and miserably failed each time, at the same point. Eventually, I was able to manually update it using Wug's Nexus Toolkit, since all other methods failed. Thank you Wug
Sent from my Nexus 7 using Tapatalk 2
Related
Got the firmware today.. when it loaded it ran the entire progress bar and later said that it failed.. however in the settings it say jh7 and additional attempts to update says no updates available. Also.. after the update the superuser app is still installed and appears that root is still there. Any thoughts?
Sent from my SAMSUNG-SGH-I897 using XDA App
trumsey2005 said:
Got the firmware today.. when it loaded it ran the entire progress bar and later said that it failed.. however in the settings it say jh7 and additional attempts to update says no updates available. Also.. after the update the superuser app is still installed and appears that root is still there. Any thoughts?
Sent from my SAMSUNG-SGH-I897 using XDA App[/QUOTE
I take it back.. after changing clock and checking again the update is available again...
Click to expand...
Click to collapse
You have to unroot before you can do a ota upgrade. Rooting is suppose to block ota upgrades because a ota upgrade would remove superuser.
I read somewhere that people have had to flash back to complete original. I've rooted and removed AT&T crapware. Also, being new to the Android platform I need some guidance on how to go back to factory orig. I've heard of odin.. but base on my limited research I haven't seen if it is available to mac. I am familiar with Unix/Linux.. they are my primary OS'.. but messing with a phone OS is just a different animal altogether.
I had to redo the phone but the update never showed up.. So what I did was just flash the update from samfirmware and it is working even though I have to redo everything...
HTH,
Charlie
evil5826 said:
You have to unroot before you can do a ota upgrade. Rooting is suppose to block ota upgrades because a ota upgrade would remove superuser.
Click to expand...
Click to collapse
My phone is rooted and I updated without issue.
Well i just tred to update mine this morning, i finally got past the communication errors. The download went fine, but when it was installing it went from 0 to 50% percent in about a second and then said update failed and rebooted.
I'm on the stock JF6 rom, however i used odin to get there.
My Sim card and sd were left in, however my sd is blank
And i don't know what any other info i can post to be helpful
2.1 update
just did the update with one click root loaded.went though with no problems phone is faster with less lag.also i can still use as wi fi hot spot. new Quikoffice,Media hub,Mobile Video and you tube. well this may mean no 2.2?
I also did the ota update with root installed, allowed 3rd apps, with wireless tethering, and it went through fine for me but I still have poor gps, did not seem to do anything for the gps except removed the option to enter lbs test mode. Anyone know how to get to the lbs test mode after update?
Samsung Mini-Kies Updater
If anyone is having troubles with Mini Kies (I had the problem where the application crashed, using Win 7 x64), I'd recommend using the regular Samsung Kies application. I was unable to do the JH7 update even after restoring to complete stock with Odin (50% update failed error). This was easy, and now I am fully in JH7, and so far the GPS lock is much, much faster.
So I just got a notification from ATT saying that there is a software update available. Has anyone else gotten this and installed it? Is it jelly bean or a minor update? I haven't tried it myself because I am rooted.
Sent from my HTC PH39100 using xda app-developers app
Bigluc said:
So I just got a notification from ATT saying that there is a software update available. Has anyone else gotten this and installed it? Is it jelly bean or a minor update? I haven't tried it myself because I am rooted.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Yes just got it I'm Rooted & S-OFF
it won't be jelly bean since the ONE X series doesn't have it yet haha just a minor I bet
Can someone detail this update?
*Edit* Called AT&T the Update was released October 9th it an 13mb update so yea Minor the girl
on the phone was talking to fast for me to listen what it offers
Got it last night. Android version did not change. Couldn't tell for sure if any other numbers updated. It wouldn't kill AT&T to send out an e-mail or text message telling us what the update was for.
got the same thing i have no idea what is the update
Update has my phone stuck in a darn boot loop..any idea what it is?
Sorry bludiamond.
Since my phone is rooted, I did not want to install this update. It's quite upsetting that AT&T forces the update unconditionally.
Anyway, I had let the download to complete, but did not let it to install. The update did prompt me, whether I want it to install now, or later. I had opted for later.
Then, after some Googling, I had deleted the download (from /sdcard/Download), and had un-installed the following services: com.htc.demoflopackageinstaller and com.smithmicro.dm.
Then, I've rebooted the phone. Afterwards, the phone still had a notification, that there's an update ready to be installed. When, selecting the notification, updater did realize that the downloaded file is gone, and had prompted me whether or not I'd like to download the update again, on which, I had responded no. The notification is gone, and AT&T did not prompt me to download and install the update again, at least not yet.
My phone seems to be OK.
I was hoping for a new Radio/RIL. That's not what this is...
New Kernel & Recovery. If you are rooted and on a custom rom Do Not run the update. I'm sure the developer of the rom you are on will work to add anything useful to future updates.
The dates on these files is 7/27/12 so it took At$t over to months to test & release.
To delete it look in /cache/fota/OTAPkg.zip
Once gone you shouldn't be bothered by it anymore.
Have anyone successfuly downloaded and installed it?
What's new? Bluetooth bugs fixes? Usable Voice Dialer? Better battery life?
Sense 4.0?
Please comment.
Sent from my HTC PH39100 using xda app-developers app
gattech said:
Have anyone successfuly downloaded and installed it?
What's new? Bluetooth bugs fixes? Usable Voice Dialer? Better battery life?
Sense 4.0?
Please comment.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Think the majority of users on here are rooted and running custom roms so they wouldnt' be installing this.
I forgot I was unlocked and rooted. Now I am really stuck. How do I get out of the dead Android loop?
I googled the update, and found this on the ATT Support website.
Beginning on October 9, 2012, AT&T and HTC have released an additional software update for the HTC Vivid that will be available via firmware over-the-air (FOTA). This 13MB software package updates the firmware version to 3.26.502.56_R23 and improves sensor performance.
NOTE: Customers must have a data SOC in order to obtain any FOTA updates. Customers who have a data opt-out SOC are not able to receive FOTA updates.
strose09 said:
Think the majority of users on here are rooted and running custom roms so they wouldnt' be installing this.
Click to expand...
Click to collapse
Hmmm....
Sent from my HTC PH39100 using Tapatalk 2
For the users in boot loop I just recovered from it. Boot into cwm and clear the cache a couple of times and reboot.
Sent from my HTC PH39100 using xda app-developers app
kos26 said:
For the users in boot loop I just recovered from it. Boot into cwm and clear the cache a couple of times and reboot.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
This Fix works. My phone no longer boot loops
3f62011 said:
Sorry bludiamond.
Since my phone is rooted, I did not want to install this update. It's quite upsetting that AT&T forces the update unconditionally.
Anyway, I had let the download to complete, but did not let it to install. The update did prompt me, whether I want it to install now, or later. I had opted for later.
Then, after some Googling, I had deleted the download (from /sdcard/Download), and had un-installed the following services: com.htc.demoflopackageinstaller and com.smithmicro.dm.
Then, I've rebooted the phone. Afterwards, the phone still had a notification, that there's an update ready to be installed. When, selecting the notification, updater did realize that the downloaded file is gone, and had prompted me whether or not I'd like to download the update again, on which, I had responded no. The notification is gone, and AT&T did not prompt me to download and install the update again, at least not yet.
My phone seems to be OK.
Click to expand...
Click to collapse
After getting my phone out of the boot loop I tried this and am no longer prompted to update. Thank you for the help
Apatche69 said:
This Fix works. My phone no longer boot loops
After getting my phone out of the boot loop I tried this and am no longer prompted to update. Thank you for the help
Click to expand...
Click to collapse
I had the looping issue too. I cleared the cache once and rebooted. Received a message that there was a problem with the update and to wait for the next update. Phone seems to be okay since.
I'm unlocked s/on..no custom rom..it was so early, I must have hit the wrong button, so I'm stuck in the loop and can't seem to get into recovery either..ugh
I'm stock - not rooted. I did do the download without any problems, although you do have to manually reboot after the update.
It supposedly improves the sensor. Not sure what that means, but that's what the ATT website says. Other than it changing my default ringtone, I don't see any difference.
Could not get it out of the loop. Took it to the service center and neither could they..they ended up replacing it under warranty..thank goodness. Said that another lady came in with the same issue as well.
AT&T Upgrade to Nowhere
I'm running stock on the HTC Vivid and got this upgrade pushed out by AT&T. This is the second AT&T upgrade I've done on this phone (the first was to ICS not long after I got the phone).
I ran the update yesterday, which force rebooted my phone and I watched as the upgrade downloaded and installed, then came back up.
NOTHING has changed. I don't know what AT&T supposedly upgraded, but it's certainly nothing noticeable.
I didn't even get the "3.26.502.56_R23" software designation that the AT&T help article says I was supposed to see.
It was literally an upgrade to nowhere. Not sure why I wasted time off the grid and battery power on it.
As usual-- AT&T fail.
At least no harm was done.
I was rooted, stock ROM, and got the notification yesterday. I postponed as much as I could but it finally wouldn't let me anymore and I let it try to update.
Of course, went into a boot loop. I did eventually get the boot looping to stop by reflashing the wxc recovery image and CWM-root, but then my wifi wouldn't work. I suspected some difference in the kernel version or some other borking of the update.
Long story short, I had to re-lock, go back to stock, and re-unlock and root again. Then spend the time (ongoing) to get my environment back. Thank goodness for Titanium backup pro and Dropbox. LOL.
Wish I could bill AT&T for the 18 hours I've spent. And if they push it to me again, I'll be irritated.
I'm reading the threads and seeing a consistent pattern (and experienced it myself). Referring at least to 4.1.2 -> 4.2 and 4.2 -> 4.2.1, it seems that you can do the OTA update if you if you have CWM but not TWRP. If you accept the OTA and have CWM, it will reboot into CWM, apply the update, ask if you want to preserve recovery and su, and reboot you into the new version.
If you have TWRP, though, it seems people get stuck at error 7 or similar.
When a larger version comes out in the future though I suspect we'll have to flash by hand as the OTA could blow away custom recovery; but for the two mentioned above at least, it wont kill CWM and installs fine with it in place.
I've loved TWRP in the past, but in this case it looks like CWM is handling the OTAs more gracefully. It's just a random chance that I have the latest CWM on my N7 instead of TWRP.
I have never used twrp, but I have done the last updates through cwm recovery and kept recovery and kept root. Definitely recommend cwm recovery.
I just got the OTA here, on TWRP 2.3.2.1, Nexus 7 no 3G. No errors, just worked.
Yeah just got the new update and I'm still rooted
-Google
iGoogleNexus said:
Yeah just got the new update and I'm still rooted
-Google
Click to expand...
Click to collapse
And you are using which recovery?
Both work. If they don't something else is going on.
Sent from Tapatalk XDA Premium
<><><><><><><><><><><><>
Nexus 7
Clean ROM 3.0 - Leankernel 0.8.x
jb0ne said:
And you are using which recovery?
Click to expand...
Click to collapse
CWM ...
-Google
Worked for me using TWRP
Sent from my SAMSUNG-SGH-T989 using xda premium
Just took the 4.2.1 update im still rooted using TWRP...
Status 7 is usually a security thing regarding the signature I think. If anything CWM has signature verification off by default.
Sent from my Nexus 7 using XDA Premium HD app
I really don't understand why people are having such a hard time understanding what is wrong when they receive an error message with the OTA update.
It's not complicated people. You don't need to be a friggin' brain surgeon or a senior level developer. The error message TELLS YOU what the issue is.
Verifying current system...assert failed: apply_patch_check("/system/SOMEFILE")
Guess what? Something is wrong with SOMEFILE. You either modified it, deleted it, "froze" it in TiBu, or did something else that is causing the update to break.
If you look at the updater-script, you can see everything thing the OTA does. It's just a long batch script basically.
The ONLY way this 4.2.1 OTA update is going to fail due to recovery is if you are using the wrong recovery for your device (ie: grouper on talapia, etc.).
I hear what you are saying but....my N7 is stock, untouched, unlocked & rooted, yet I had problems with CWM & TWRP with the OTA and flashing the update manually.
I had to go back to stock recovery for both updates.
But I can see in this thread some have the OTA update working fine, one thing we all have in common is the N7, yet varied results.
jersonf said:
I hear what you are saying but....my N7 is stock, untouched, unlocked & rooted, yet I had problems with CWM & TWRP with the OTA and flashing the update manually.
I had to go back to stock recovery for both updates.
But I can see in this thread some have the OTA update working fine, one thing we all have in common is the N7, yet varied results.
Click to expand...
Click to collapse
Was your unit a 3G or Wi-Fi only model?
OTA?
I hate to be the hater, but why would anyone here take an OTA? The reason this site exists is specifically to help people to not use the stock software. If cwm survives OTAs it is probably an accident, lol.
Sent from my Nexus 7 using xda premium
brizey said:
OTA?
I hate to be the hater, but why would anyone here take an OTA? The reason this site exists is specifically to help people to not use the stock software. If cwm survives OTAs it is probably an accident, lol.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
What are you talking about?
XDA is in no way a site dedicated exclusively to "help people not use the stock software". It's a place where people can discuss their hardware/software including stock/custom/etc. usage and modifications. So not only is your comment 100% incorrect, but it's also contrary to this thread in particular. The thread title clear talks about using a CUSTOM recovery with an update to the stock software. So even if you were right (you aren't), your point is counter-intuitive.
There are many people here that are either mostly or completely stock. That's their personal preference and it's completely fine and acceptable. And it most certainly doesn't mean they don't deserve help or assistance here.
---------- Post added at 03:17 PM ---------- Previous post was at 03:13 PM ----------
Also, while OTA updates are written in such a way to remove suid root on the su binary and reinstall the stock recovery image, most new custom recoveries have a work around in place to prevent this. Not to mention it's trivial to restore them back after the update.
brizey said:
OTA?
I hate to be the hater, but why would anyone here take an OTA? The reason this site exists is specifically to help people to not use the stock software. If cwm survives OTAs it is probably an accident, lol.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
No accident ... I updated my N7 from 4.1 to 4.2 still rooted.. And I just updated again to 4.2.1 ... Don't know about you but I love these kind of updates
Also I like my devices stock, rooted and a few tweaks here and there along with rooted applications... I'm sure there are many of me out there.
-Google
I prefer to never actually flash the recoveries.. just adb boot them as required - that means my system is always stock for the updates and I can pick a recovery at random should I want them (although generally I only use them to get a root shell to install su when I get a new phone).
I am rooted stock with cwm touch and the ota fails staus 7. I'm pretty sure I didn't do anything to "break" the update for myself. It's kind of funny the clockwork stops and asks about flashing an untrusted rom and then doesn't allow it. I would rather sit out of this whole 4.2 bs anyway.
I was rooted and stupidly just clicked the update to 4.2.1 without thinking, it didn't even occur to me to take any measures to keep root or custom recovery. So I lost both. It only took a few minutes with Wugs' toolkit to fix though.
I've taken three OTAs with TWRP and had no problems with any of them.
Sent from my Nexus 7 using Tapatalk HD
So finally Android 4.3 has arrived and our Beloved Nexus 7 is Upgradable Now.....
here is the link to the download of factory Image:
https://developers.google.com/android/nexus/images#nakasijwr66v
Follow this Method and flash the New Android OS...
[GUIDE] Flashing a Factory Image with fastboot / return to stock Thanks @comminus for a great Guide...
Report Back with screenShots and new featuers as well as Bugs because new pudates bring New Bugs.....
The update brought a new bootloader version...android 4.2.2 had 4.18 and 4.3 has 4.23.....
hassam_tariq2003 said:
The update brought a new bootloader version...android 4.2.2 had 4.18 and 4.3 has 4.23.....
Click to expand...
Click to collapse
Did you lose boot loader unlock or root when you installed 4.3? I'm assuming you used fastboot to install not OTA? Just curious...I'll be playing tonight when I get home.
tbonezx11 said:
Did you lose boot loader unlock or root when you installed 4.3? I'm assuming you used fastboot to install not OTA? Just curious...I'll be playing tonight when I get home.
Click to expand...
Click to collapse
You lose root but your bootloader remains unlocked.
Has anyone been able to root 4.3? Tried to root and flash custom recovery with the Nexus 7 toolkit, but I don't think it's working.
mhl12 said:
You lose root but your bootloader remains unlocked.
Has anyone been able to root 4.3? Tried to root and flash custom recovery with the Nexus 7 toolkit, but I don't think it's working.
Click to expand...
Click to collapse
haven't tried it (I'm yet to receive the update) but someone referenced this link: https://plus.google.com/u/0/+Chainfire/posts/WqS2E9kkN1L
he is right.....You loose root but bootloader remains unlocked...
i have heard people say that you do not loose root if you use the OTA Method and your bootloader also remains unlocked....So its your choice its either Fastboot or OTA...
Just use OTA Rootkeeper, you'll be fine.
Just remember kids.
You cannot use an OTA if your ROM is modified in ANY WAY.
Yeah OTA wont work for most people, seeing as they probably have a modified ROM. In any sense, chainfire has a root method that works. I can confirm it working, because I installed it using TWRP
khaytsus said:
Just use OTA Rootkeeper, you'll be fine.
Just remember kids.
You cannot use an OTA if your ROM is modified in ANY WAY.
Click to expand...
Click to collapse
When 4.2.2 came out I had problems updating because my ROM was modified. But someone modified OTA not to check for changes in ROM and it worked.
no OpenGL ES 3.0 for us?
according to http://developer.android.com/:
"OpenGL ES 3.0 is an optional feature that depends on underlying graphics hardware. Support is already available on Nexus 7 (2013), Nexus 4, and Nexus 10 devices."
I am running 4.3 unlocked but I did the one click method for root using nexus tool kit and for some reason it did not work, I have to try again tonight.
Want a single click ADB setup? Go to my thread I've made a Tool for that. No need to download the whole SDK it's just 2MB
http://forum.xda-developers.com/showthread.php?t=2374071
What to know how to easily pull ota link with ADB follow my thread.
http://forum.xda-developers.com/showthread.php?t=2270429
For official nexus 7 windows 7 - 8 driver download them from ASUS site. No trickery needed.
Sent from my SPH-L710 using Tapatalk HD
Team SXTP
So, I played around a bit,
First of all, I did a "clean, unrooted and even locked bootloader install".
So I'm 1000% stock, just to avoid stuff like "maybe root caused it"..
(I locked it because I wanted to go 100% stock, just FYI, I know it's normally not necessary...)
The welcome screen was a bit weird... I got asked 2 times to tick or untick boxes for saving passwords and all that stuff.. (I think they mixed up the new and the old "first boot setup"?)
The Apps and widgets in the drawer were kinda confused, took 2 reboots for them to settle... (Icons disappeared and reappeared.. The widget tab in the drawer threw some widgets in and out, and the previews were mixed up, so dots and a weird sign was the result (as a preview of the widget)...
The initial setup was pretty laggy, but after setting stuff up, until now, yes I can say the performance of the nexus 7 is improved..
First I was like "OH HELL NO" but after the setup and the reboot everything was smooth...
Oh, and the back button was destroyed 1 time, blinked up but didn't go back... I pressed the home button and it worked then.
Edit: And sadly, no new wallpapers in stock... ):
Sent from my Nexus 7 using xda premium
I booted it up, restored my Google Play stuff (flashed a factory image, completely wiped everything from it, so it's clean, I think).
It lagged a lot, so I rebooted it and it still isn't 4.2.2 smooth. Maybe it's just me, I'll see.
Is it just me, or does it feel like the only thing that changed for us is the number in settings menu besides Google Apps?
OpenGL ES as it was already said, doesn't appear to be here for us, not to mention the fact that Miracast had never actually worked on N7 until recently when someone had it ported over.
Has anyone managed to find the link for the OTA yet?
SO I flashed the stock 4.3 kernel on a 4.2.2 rom and discovered that the stock android 4.3 kernel breaks wifi and gps on 4.2.2...
Eregoth said:
Has anyone managed to find the link for the OTA yet?
Click to expand...
Click to collapse
I have literally hours working on that.
Flashed the stock image using fastboot, took like 2 minutes to do, flashed the chainfire root patch and rebooted and restored apps, so far everything is pretty smooth no disappearing apps or icons or buttons, the kernel seems to be quicker, opening websites was quite a bit quicker, one thing I noticed while trying out different browsers was ads opening up new tabs automatically, that's something that's never happened before.
ffaiz.m said:
no OpenGL ES 3.0 for us?
according to http://developer.android.com/:
"OpenGL ES 3.0 is an optional feature that depends on underlying graphics hardware. Support is already available on Nexus 7 (2013), Nexus 4, and Nexus 10 devices."
Click to expand...
Click to collapse
Tegra 3 does not support GLES3. Even Tegra 4 won't, because nvidia are still using their old gpu architecture.
What's the performance like? Better than 4.2 or 4.1?
Sent from my GT-I9300 using xda premium
Hey all,
Thought I'd let those of you that have an AT&T Tab S 8.4 know that Lollipop has been released today. Happened to be on the AT&T Software update page here: http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB425812&cv=820 and noticed it listed the update.
Manually checked for updates on my tablet, it's downloading now. My 8.4 on AT&T is totally stock.
Downloading now... 1.1GB
manually checking shows nothing for me
Mine wasn't too laggy after the upgrade. But as I know from places like XDA usually a very good idea to do a full system wipe which I did.
What I am most thankful for is there is now an option to remove that Samsung screen that has those Samsung widgets that go full page. Can't recall what it is called. Yeah I know could have got rid of that using a 3rd party launcher in 4.4 but so happy Samsung put option there to disable it finally. To get rid of it, long press blank space like you were going to add a widget, then click Home Screen Settings, then uncheck "Content Home Screen".
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Russ77 said:
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Click to expand...
Click to collapse
Not sure it will work.
Maybe try to adapt the method given by ashyx here: http://forum.xda-developers.com/galaxy-tab-s/general/guide-how-to-root-tripping-knox-kitkat-t3129484
It worked successfully for me on the T800
Russ77 said:
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Click to expand...
Click to collapse
I'm rooted with Kingroot and it's currently downloading the update. If you load Xposed Framework and Wanam Xposed, under Security hacks there's a setting for Fake System Status that allows you to set it to Original.
I'll follow up when the download finishes.
Update: The download completed but the install failed and then got stuck in a boot loop. Ended up having to go to the Samsung place at Best Buy to have them re-flash KitKat. Now the tab is telling me I have to wait 24 hours to check for updates. I'm sure everything will be good now that I'm back on a factory image.
fleabeard said:
I'm rooted with Kingroot and it's currently downloading the update. If you load Xposed Framework and Wanam Xposed, under Security hacks there's a setting for Fake System Status that allows you to set it to Original.
I'll follow up when the download finishes.
Update: The download completed but the install failed and then got stuck in a boot loop. Ended up having to go to the Samsung place at Best Buy to have them re-flash KitKat. Now the tab is telling me I have to wait 24 hours to check for updates. I'm sure everything will be good now that I'm back on a factory image.
Click to expand...
Click to collapse
Turn off automatic date and time and manually advance it by a day, and try again.
When they re-flashed KitKat did it wipe your tablet? The OTA failed me when rooted, failed me after un-installing adaway and un-rooting and removing KingUser. I cannot do a firmware upgrade via Kies 3 as it's not available. I cannot do an emergency firmware recover via Kies 3 as it's not soft bricked. I can't find either the KitKat or the Lollipop firmwares online anywhere... Currently I have a tablet, works fine, I did a factory reset (in the back of my mind knew this wouldn't work) that has a custom status and won't take the OTA.
If anyone knows where I can find the KitKat firmware, or the OTA, please let me know.
Or maybe someone could grab the OTA off their tablet after downloading prior to updating and share the wealth with the community???
Has any kingroot user tried triangle away, unroot via kinguser, and take the OTA?
Also just realized that if I can fail the OTA, I can obviously download it... Where do I grab it from if I wanted to flash it with odin or sideload?
Russ77 said:
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Click to expand...
Click to collapse
Russ77 said:
Turn off automatic date and time and manually advance it by a day, and try again.
When they re-flashed KitKat did it wipe your tablet? The OTA failed me when rooted, failed me after un-installing adaway and un-rooting and removing KingUser. I cannot do a firmware upgrade via Kies 3 as it's not available. I cannot do an emergency firmware recover via Kies 3 as it's not soft bricked. I can't find either the KitKat or the Lollipop firmwares online anywhere... Currently I have a tablet, works fine, I did a factory reset (in the back of my mind knew this wouldn't work) that has a custom status and won't take the OTA.
If anyone knows where I can find the KitKat firmware, or the OTA, please let me know.
Or maybe someone could grab the OTA off their tablet after downloading prior to updating and share the wealth with the community???
Click to expand...
Click to collapse
OTA came down successfully while not rooted. The reflash at Best Buy didn't wipe it.
As far as I know, the factory images for the AT&T versions aren't available anywhere, or at least I've been unable to find them. They obviously exist because I'm pretty sure the guy at Best Buy used Kies to flash with an image that's available to him from Samsung.
I re-rooted last night in the attempt of using triangle away to clear customs status, then un-rooting. This was odd because device status still shows custom but download mode shows official and Knox is 0.
While I was briefly rooted again I downloaded the OTA in the hopes of copying it to my PC and updating via ADB Sideload... Couldn't find it. If anyone knows where Samsung puts these I'll grab it and post it to share.
im not rooted, performed a factory reset, and my device still doesn't see any updates. Can somebody provide a link to the ROM?
Same situation here - no root, no mods, no available update
Sent from my SM-G925V using XDA Premium HD app
Same Thing Here Also
bshaw100 said:
Same situation here - no root, no mods, no available update
Sent from my SM-G925V using XDA Premium HD app
Click to expand...
Click to collapse
I've got the same thing: no root, no mods, no update available! Darn!!!!
I've got the same thing: no root, no mods, no update available!
Russ77 said:
I re-rooted last night in the attempt of using triangle away to clear customs status, then un-rooting. This was odd because device status still shows custom but download mode shows official and Knox is 0.
While I was briefly rooted again I downloaded the OTA in the hopes of copying it to my PC and updating via ADB Sideload... Couldn't find it. If anyone knows where Samsung puts these I'll grab it and post it to share.
Click to expand...
Click to collapse
The OTA gets downloaded to /cache. If you are rooted you can see it. But the OTA is not a complete ROM, just a differential to the ROM you have.
Sent from my SM-T707V using XDA Premium HD app
still nothing
gshaw_nash said:
I've got the same thing: no root, no mods, no update available! Darn!!!!
Click to expand...
Click to collapse
gshaw1967 said:
I've got the same thing: no root, no mods, no update available!
Click to expand...
Click to collapse
I've reset several time and cannot download the update. I get "Connecting to DM Server" and then update interrupted. Has anyone gotten around this?
---------- Post added at 08:58 AM ---------- Previous post was at 08:11 AM ----------
gshaw1967 said:
I've reset several time and cannot download the update. I get "Connecting to DM Server" and then update interrupted. Has anyone gotten around this?
Click to expand...
Click to collapse
Turns out there is a imei problem with the tablet that is preventing the download. My imei number is paired with a IPhone 4. Anyway will take a few day to fix then the upgrade should work.
I get the same. I wiped my device hoping for a different outcome, and still no update.
I found this in the thread below.
It is an old tread but I'll comment anyway. SM-T807 is the 3G version while SM-T805 is the LTE version. Both Hardware (CPU/GPU) and comms modules are different. So 805 LTE (which has Lollipop) firmware won't work for 807 (no Lollipop is currently available nor Samsung plans to release soon).
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-s/help/sm-t805-sm-t807a-t2961117
John.
After not being able to take the OTA after rooting, even after un rooting, not being able to find the OTA and sideload (not in /cache), and not able use Kies or Odin I finally took it to the Samsung kiosk at my bestbuy.
They reflashed 4.4.2, didn't wipe anything, and immediately downloaded and successfully installed the lollipop update after getting home and on WiFi.
Just don't mention that you rooted ;')