My Nexus 7 wifi has the 4.4.3 update that has been prompting me to update. I tried doing the update which fails.
I do have TWRP installed, MultiROM, and a customer kernel. I tried flashing a custom kernel which did not resolve the issue.
I currently swap between stock and CM depending on what I would like to play with.
pctechdroid said:
My Nexus 7 wifi has the 4.4.3 update that has been prompting me to update. I tried doing the update which fails.
I do have TWRP installed, MultiROM, and a customer kernel. I tried flashing a custom kernel which did not resolve the issue.
I currently swap between stock and CM depending on what I would like to play with.
Click to expand...
Click to collapse
I'd do a nandroid before doing anything.
It might help if you state what the exact contents of the error is, my guess is that you have changed something in /system (unexpected contents error), and flashing a custom kernel won't fix it, in fact you would want to flash a stock 4.4.2 system.img and stock 4.4.2 boot.img if you want to use the OTA method, else you can just skip using the OTA and try and flash a 4.4.3 system.img and 4.4.3 boot.img, either way make sure you clear dalvik and cache before booting up after the system flashes.
You cannot install official updates if your device is modified!
Since you mentioned that you are familiar with CM, why don't you update to the latest CM ROM?
mediumsteak said:
You cannot install official updates if your device is modified!
Since you mentioned that you are familiar with CM, why don't you update to the latest CM ROM?
Click to expand...
Click to collapse
I play with it every once in awhile but I don't know why I enjoy stock but I do. Maybe I will go back to CM.
Related
Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
niaoRen said:
Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
Click to expand...
Click to collapse
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
True, I've experienced this before, I would recommend go with Official Factory image if not sure your device is running completely stock before apply OTA...
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
fux0r99 said:
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
Click to expand...
Click to collapse
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Zepius said:
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Click to expand...
Click to collapse
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
niaoRen said:
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
Click to expand...
Click to collapse
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
cupfulloflol said:
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
Click to expand...
Click to collapse
alright. Will try to revert to stock kernel and try the official OTA. Will revert back here after i've attempted it. Thanks a bunch you all
I just found a easier way to do things.
Just flash this 4.3 stock ROM over my current 4.2 rom. Works like a charm and hassle free.
Okay, I am in the same boat as many others here. I am running a rooted stock 4.4 with the Elemental 2.3 kernel, along with the two dalvik/bionic hacks and naturally xposed with all sorts of modules. My recovery is TWRP 2.6.1.0., and my device is a 2013 N7 wi-fi model. I think I used Wug's toolkit to root.
I have the OTA 4.4 > 4.4.2 .zip file. What is the easiest way to go about updating to this, and then getting back root and everything else? I have seen reports of people actually flashing the OTA using TWRP, but then some people have problems. Does a person have to force an unroot first, and then go through ADB sideloading from pc/console? Is there a way to flash this with either TWRP or one of the Phil/touch recovery setups?
I know that the kernel is untouched with this OTA, and that I will have to re-root and then re-install xposed. I also know that AppOps is broken with the 4.4.2 release, hopefully something they will sort out. Does it make sense to redo the two hacks for dalvik and bionic?
Anyone have a tried and tested way to update and get back to full root as easily as possible?
I'm in the same situation too, but would installing a custom Rom with 4.2.2 on not solve it if you were happy to flash custom?
..
BigPickle80 said:
I'm in the same situation too, but would installing a custom Rom with 4.2.2 on not solve it if you were happy to flash custom?
Click to expand...
Click to collapse
The beauty of the Nexus 7 is that you can stick with the stock rom and nowadays still get all the goodies you want with xposed and other tweaks that accomplish the same thing as most hotrod roms. I want HDMI out, which I have lost on other devices after going to a CM based build.
I had my phone rooted before the update, but then I thought I'd try going without root once the update came out. But now I am rooted once again and running the "T999L 4.3 deodexed, Knox Free". But when I try to install cm (I tried 11 and 10.2), I either get the executing updater binary error, status 7 error, and when I removed the asserts, it just aborted installation. Any help or suggestions are greatly appreciated
Update your Recovery to the latest version.
Perseus71 said:
Update your Recovery to the latest version.
Click to expand...
Click to collapse
I did that, tried both CWM and TWRP and it's still aborting the flash. It seems like the only rom it's letting me install is the deodexed 4.3
Actually I had a issue a few days where I accidentally wiped my internal memory and that is why I installed te deodexed 4.3, could that be a reason why nothing is working properly (I'm able to make backups but not restore them and what I mentioned before in my fist post)? Should I install the original 4.3 (with knox and everything) to get my phone on the correct thing and then use the knox remover from the forum before trying again?
wanderingghost said:
I had my phone rooted before the update, but then I thought I'd try going without root once the update came out. But now I am rooted once again and running the "T999L 4.3 deodexed, Knox Free". But when I try to install cm (I tried 11 and 10.2), I either get the executing updater binary error, status 7 error, and when I removed the asserts, it just aborted installation. Any help or suggestions are greatly appreciated
Click to expand...
Click to collapse
Why dont you try this:
S3Rx 3.0
http://forum.xda-developers.com/showthread.php?t=2326763
Its basically the same thing, except its debloated with a few mods..
Just be sure you have the MK4 Modem..
if you have not updated the bootloader (DONT) It will trip your warranty counter..
Just be sure you flashed the MK4 Modem, then flash the 4.3 rom..
Also be sure to Flash the T999L Connectivity patch on top
with the Insecure Kernel.. If you dont flash the Kernel you will lose wifi connectivity..
Zaphodspeaks said:
Why dont you try this:
S3Rx 3.0
http://forum.xda-developers.com/showthread.php?t=2326763
Its basically the same thing, except its debloated with a few mods..
Just be sure you have the MK4 Modem..
if you have not updated the bootloader (DONT) It will trip your warranty counter..
Just be sure you flashed the MK4 Modem, then flash the 4.3 rom..
Also be sure to Flash the T999L Connectivity patch on top
with the Insecure Kernel.. If you dont flash the Kernel you will lose wifi connectivity..
Click to expand...
Click to collapse
Do I also flash the MD5 file that's right above the t999l data connectivity patch? On the download link it says t999 so I'm not sure
wanderingghost said:
Do I also flash the MD5 file that's right above the t999l data connectivity patch? On the download link it says t999 so I'm not sure
Click to expand...
Click to collapse
Yes.. Flash that (Its the ROM), then flash the Connectivity patch (its the T999L patch), then flash the insecure Kernel..
Zaphodspeaks said:
Yes.. Flash that (Its the ROM), then flash the Connectivity patch (its the T999L patch), then flash the insecure Kernel..
Click to expand...
Click to collapse
Oops, I somehow missed realizing that that was the rom and was downloading an older version of it that was lower down on the post. I got this rom to work, but I am still unable to install other custom roms. I really liked the CM11 (4.4) rom, but after updating to 4.3 (unrooted), I am unable to install anything but 4.3 roms so it seems. I did update to the latest version of twrp and I also tried cwm, but I'm still getting failure messages, any idea on how to fix that? Thanks for your help so far
wanderingghost said:
Oops, I somehow missed realizing that that was the rom and was downloading an older version of it that was lower down on the post. I got this rom to work, but I am still unable to install other custom roms. I really liked the CM11 (4.4) rom, but after updating to 4.3 (unrooted), I am unable to install anything but 4.3 roms so it seems. I did update to the latest version of twrp and I also tried cwm, but I'm still getting failure messages, any idea on how to fix that? Thanks for your help so far
Click to expand...
Click to collapse
To be honest there isnt much difference between 4.4 and 4.3.. other than ART..
I much rather stay on 4.3 because it has App Ops, where 4.4 had it removed..
I much rather have an AOSP rom rather than Touchwiz, but no other ROM i have found that is non Touch Wiz
that has Wifi Calling
Zaphodspeaks said:
To be honest there isnt much difference between 4.4 and 4.3.. other than ART..
I much rather stay on 4.3 because it has App Ops, where 4.4 had it removed..
I much rather have an AOSP rom rather than Touchwiz, but no other ROM i have found that is non Touch Wiz
that has Wifi Calling
Click to expand...
Click to collapse
True, but I guess my issue is that I can't install any of the CM roms, not even 10.2 which is based on 4.3. I just like CM because of the customization and the rom you linked me to has some of them, but not all. I've already tried unrooting and re-rooting, but that still did not help. Is there a different way you're supposed to root after the 4.3 update? I've always followed the instructions on DocHoliday's T999L/T999N thread and before 4.3, I was able to use twrp to flash t999 roms without removing asserts, but now even removing the asserts, I can't install any custom roms
wanderingghost said:
True, but I guess my issue is that I can't install any of the CM roms, not even 10.2 which is based on 4.3. I just like CM because of the customization and the rom you linked me to has some of them, but not all. I've already tried unrooting and re-rooting, but that still did not help. Is there a different way you're supposed to root after the 4.3 update? I've always followed the instructions on DocHoliday's T999L/T999N thread and before 4.3, I was able to use twrp to flash t999 roms without removing asserts, but now even removing the asserts, I can't install any custom roms
Click to expand...
Click to collapse
I have been able to install a couple of CM 10.2 Roms.. Not sure what ones I flashed, because I couldnt connect my phone to my PC via USB..
the phone started to act a bit bazaar.. So I reverted to something I knew..
Zaphodspeaks said:
I have been able to install a couple of CM 10.2 Roms.. Not sure what ones I flashed, because I couldn't connect my phone to my PC via USB..
the phone started to act a bit bazaar.. So I reverted to something I knew..
Click to expand...
Click to collapse
Different CM 10.2 roms as in stable, rc, nightly? I tried the stable version earlier and still no luck. I'm kind of starting to give up on it because I'm just getting frustrated lol
wanderingghost said:
Different CM 10.2 roms as in stable, rc, nightly? I tried the stable version earlier and still no luck. I'm kind of starting to give up on it because I'm just getting frustrated lol
Click to expand...
Click to collapse
Im pretty new to this area myself.. I've had a few trial and error issues..
Flashing Nexus devices is far to easy compared to this.. But since they have no Micro SDcard reader..
I'll never own a Nexus phone..
This is the first phone I've rooted, I didn't have problems until after 4.3. But would you happen to know where I can find instructions on how to unroot this device? I was going to try to find an 100% 4.3 stock rom, unroot, and then try this (http://forum.xda-developers.com/showthread.php?t=2563955) to see if it would work and if it didn't, then I'll just leave my phone unrooted. But I can't find any instructions anywhere, the only one's I can find are DocHoliday's but that's to return to stock 4.1.2
Never mind, I figured out
my work requires encryption. i was on slimkatv22 at the time and had to encrypt. as encryption kept failing, i went back to stock. way back to stock.
so i'm running
JZO54K.I317UCAMH3 ROM
TEAMWIN Recovery
I317UCUCNE5 Bootloader
with Root and Busybox installed.
everytime i try to update via device update, it downloads, reboots and runs TWRP, I decrypt using password, reboots and the update fails with "Update Interrupted" message.
Is there a way to update ROM and keep encryption?
You can't OTA stock ROMs without stock recovery.
xBkKx said:
You can't OTA stock ROMs without stock recovery.
Click to expand...
Click to collapse
Thanks for your response. I tried updating ROM via ODIN and was not successful. Always got stuck in boot logo after i flashed new ROM.
Is there a stock recovery I should flash over TWRP to try?
Thanks for your help.
I have never used encryption so I can't really help if there are specifics around that. What exactly are you trying to install through Odin? If it's the firmware such as THIS it should overwrite the custom recovery with the stock one. If the stock ROM isn't booting you might have to boot into recovery and factory reset/wipe dalvik cache. This is my first Samsung phone so if nothing helps someone else who'd like to offer their assistance would probably be more knowledgeable.
I was going back to stock, which I guess, was mostly successful. however, I've not been able to install new ROM, namely 4.4.2 I317UCUCNE5. so if I install from your link, that should overwrite custom recovery and allow me to upgrade to 4.4.2 ROM either OTA or via Odin?
Maybe? Using the OTA always tells me there isn't an update (cause I'm on T-Mobile I guess?) and I haven't seen any files to update to Kitkat firmware through Odin
http://forum.xda-developers.com/showthread.php?t=2618447
i'm going to try this.
thanks,
miserly said:
http://forum.xda-developers.com/showthread.php?t=2618447
i'm going to try this.
thanks,
Click to expand...
Click to collapse
haven't had time to try. tbutbut i noticed that foxfi doesn't work even though i'm rooted. i searched for tether and doesn't seem to be a working solution for a free app.
SOLVED
finally got around to following the directions from dicksteele and voila! i'm on 4.4.2!
thanks all!
m
I'm trying to install the latest update to cm13 but it errors out. I'm only running stock CM with no custom kernel. I've also tried a full wipe and reinstall but get the same error message. Any help is appreciated.
Which rom are you running now? If it's lollipop based then you need to flash marshmallow to then flash cm13 over the top of it.
If you are s-on you have to use an ruu or an ota. If you are s-off there are plenty of zips around you can flash.
The principle is, you need a base rom to flash the "incomplete" cm13.
Sent from my HTC One M9 using Tapatalk
You need to update your firmware to the latest version and then you will be able to flash the new ROM.