Update to 4.3 if rooted? - Nexus 7 Q&A, Help & Troubleshooting

I'm on stock 4.2.2 and have TWRP and am rooted. Can I just get the wifi version of the new release and use TWRP to install it? If not what's the easiest way to go back to completely stock as if I took it out of the box so I can just do an OTA.?
Sent from my HTC One using xda app-developers app

Nope. Can't flash through TWRP.
You can use Wugfresh's tool kit to flash the new ROM.

I installed 4.3 manually through fastboot. Afterwards it only showed 6GB available instead of 27.5 so I reformatted to correct it.

So whats needed to just revert back to stock recovery and unroot it so I can just get the OTA update? Ive read a ton of posts and they are all a bit different in what they say. I have the stock ROM from google saved as well as the recovery.

Related

clean rom 2.3 android or a update

hi I have the clean rom installed with twrp custom recovery.
today when I opened my tablet it said that a system update has been downloaded and I should restart to install 4.3. I said yes and it rebooted and went normally into custom recovery but was just sitting there after that.
I have rebooted again into clear rom and nothing seems to be broken. queries :
how was the ota update downloaded on a custom rom?
where is it stored?
can I directly go to the stock system after installing it through clean rom?
is there a risk of bricking?
what's the best way to stay rooted and switch to stock 4.3?
Sent from my Nexus 10 using Tapatalk HD
msankadi said:
hi I have the clean rom installed with twrp custom recovery.
today when I opened my tablet it said that a system update has been downloaded and I should restart to install 4.3. I said yes and it rebooted and went normally into custom recovery but was just sitting there after that.
I have rebooted again into clear rom and nothing seems to be broken. queries :
how was the ota update downloaded on a custom rom?
where is it stored?
can I directly go to the stock system after installing it through clean rom?
is there a risk of bricking?
what's the best way to stay rooted and switch to stock 4.3?
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
The best way is to wait for the rom your using to update that way you can keep all your data or just flash the the 4.3 zip n the Dev thread
Sent from my Xperia Play (r800x)
Clean rom is no longer developed.

[Q] Problem with OTA 4.3

Hey guys, got a problem here.
My nexus 4 is rooted running team win recovery. running 4.2.2
just got the notification about OTA update 4.3, really excited about it and clicked install.
phone rebooted, went to teamwin, and it looked to me trying to flash something. left it there and suddenly when back to the team win recovery home page. clicked reboot to system and don't know why i'm still in 4.2.2. checked for updates but says system is up to date.
can anyone help me with the solution?
thanks a lot
You need the stock recovery, as said in a thousand other threads. If u want 4.3 flash the system image and re-root
Sent from my Nexus 4 using xda premium
EddyOS said:
You need the stock recovery, as said in a thousand other threads. If u want 4.3 flash the system image and re-root
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Or he could just get any 4.3 ROM and flash it through TWRP.
Sent from my Nexus 4 using xda app-developers app
Aaaaand i am still waiting for my update :/
My two friends with Samsung GNex got the Update, but ME with the Latest Nexus 4 still using 4.2.2 and on stock how beautiful the feeling is haha
Thibaultvw said:
Or he could just get any 4.3 ROM and flash it through TWRP.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Or CWM
If you want it that bad. Just download the factory image from Google devs and flash it.
Then you also have stock ROM running.
Send from my Nexus 4
EddyOS said:
Or CWM
Click to expand...
Click to collapse
He uses TWRP.
Sent from my Nexus 4 using xda app-developers app
Is there any way to revert back to stock recovery in order to get the update?
Further more, is there an option to do so without re-flashing stock all together?
wizardwiz said:
Is there any way to revert back to stock recovery in order to get the update?
Further more, is there an option to do so without re-flashing stock all together?
Click to expand...
Click to collapse
You can extract the stock recovery from the factory image and flash through fastboot.
Hit thanks if I helped.
Sent from my Nexus 4 using xda app-developers app
You can get the stock 4.2.2 recovery from the 4.2.2 factory image. I did have it but as I only keep the current factory image I only have the 4.3 recovery to hand
EddyOS said:
You can get the stock 4.2.2 recovery from the 4.2.2 factory image. I did have it but as I only keep the current factory image I only have the 4.3 recovery to hand
Click to expand...
Click to collapse
OK, did some further investigations and here are my findings
1. If you have it, you can use Wugfresh's toolkit (V1.6.4 for now) and it has a utility that can simply restore stock recovery and if you want it, stock kernel as well.
2. The Toolkit will download all necessary files and prompted you before each step.
3. It will revert back permissions for the stock recovery as well
I'll give it a try later on at home.
Thanks guys
Ziv
I am a bit confused. According to the “Nexus OTA Help-Desk” thread, the way to do this is as follows:
Scenario #2
You are stock, with root. Custom Recovery without any modifications or deletions.
Continue to Section B
Section B: Flashing in a custom recovery
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery
3) Flash the OTA
4) Flash Su.zip: (SU is being updated often so check Chainfire's G+ for the latest) https://plus.google.com/+Chainfire/posts
NOTE: Root on 4.3 is not stable. Your mileage may vary.
5) Reboot
So, what is different about using this method to install the OTA and just running the OTA from the notification, and is this the incorrect method?
Is returning to the stock recovery the preferred and more or less foolproof method?
I'm not sure why there's people saying otherwise, but from my experience you don't need stock recovery to take on an OTA...
I've updated my N7 several times now from when I first bought it to 4.3 currently, all the time with a custom recovery. Unless you've changed some other files which causes an error during the OTA update, I don't believe there is a need to re-flash stock recovery at all.
@mlj11, lots of people have the OTA failing on them, even if they are on rooted factory image 4.2.2.
Why the OTA fails on rooted 4.2.2 is still unclear.
My N4 with rooted factory image 4.2.2 also updated like it should without error.
Maybe the unlocked bootloader is the issue letting the 4.3 OTA fail.
Send from my Nexus 4
@DecypherT
I'm not saying that rooted users will have no problems updating. My post was in response to people on this thread saying that a custom recovery will stop the OTA. This is false.
It can't be the unlocked bootloader (and it has never been) causing the problem otherwise you or I wouldn't have been able to take the OTA, for example. More likely it's something else.
If any of a user's system files have been altered, there's a good chance the OTA will fail. In the past that happened to me because the Stickmount app changed one of the system files. Once I replaced it though, I could update without any problems.
Ok, good points you're proving here.
Still, it looks like the (OTA) android 4.3 is very unstable.
I'm on rooted 4.3 and experience no big bugs or flaws though.
I do see a very large decrease of battery life when using the phone (screen on) and a big increase when in deep sleep. When the phone is off I almost use no battery.
Send from my Nexus 4

[Q] Updating from 4.2.2 to 4.3 failing repeatedly.

Hi everyone, I'm having a hell of a time trying to update my phone from 4.2.2 to 4.3 (stock rom). I have searched the forums (or tried to) and have done general Google searches, but nothing with my problems came up. I rooted my phone a while back, lost root when my phone updated to 4.2.2, then used wugfresh's Nexus Root Toolkit to get it back. Ever since 4.3 came out, I have been unable to update. I was using TWRP, and when updating through the phone it would simply dump me back there and not continue. I was then instructed to manually flash through TWRP, which I tried to do, but halfway through the flash it simply stops. I believe it said "signature verification failed". Someone had me try using the NRT to push the update as well, but that hasnt worked either. It just fails.
After asking around some more, I was instructed to flash the stock recovery, which I have now done. Now when I try to update (through the phone), it takes me to stock recovery, starts installing the update, and (yet again) halfway through the android guy just has an X on it and it says "failed". With Kit Kat supposedly coming out in two days, I really want to be ready to get the update asap. Could anybody help me out?
Also, if possible I would like there to be a way to do so without losing the data on my phone. But its not necessary.
I am sorry if this same problem has come up before. I tried going through other threads and the ones suggested after typing in the thread title.
Why don't you just use the toolkit to bring you back to stock and unroot? Once that is done you will get the update OTA
I am on stock, and I am getting the update OTA. It is just failing to install every time I try to install the update.
Your did something wrong when going back to stock. Did you unroot and relock the boot loader?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Or you can just flash all the .img file of the 4.3 using adb.
To blankit, no I did not unroot or relock the bootloader. I simply re-flashed the stock recovery. Relocking my bootloader would cause me to lose all my data, and by all accounts has nothing to do with installing updates. I will try disabling root access.
To arffrhn, flashing the .img through adb is what I have done through different toolkits. No matter how I have gone about trying to manually flash the 4.3img or install through the OTA update, it is failing.
To blankit, no I did not unroot or relock the bootloader. I simply re-flashed the stock recovery. Relocking my bootloader would cause me to lose all my data, and by all accounts has nothing to do with installing updates. I will try disabling root access.
To arffrhn, flashing the .img through adb is what I have done through different toolkits. No matter how I have gone about trying to manually flash the 4.3img or install through the OTA update, it is failing.
I did same thing without any problems after I unrooted and installed stock kernel.
Just use Wug toolkit and factory 4.3 image.
Now open image and extract radio, bootloader and system img.
Now use Wug and flash only these img.
Then reroot and start flashing custom kernel or roms.
Sent from my NookColor using Tapatalk 4
If everything else fail, do it manually.. Seek this thread.. http://forum.xda-developers.com/showthread.php?t=2010312.
Never do anything using toolkits.. Manual way is always the best.
this tool may help you:
Have you ever get into a situation where you have a custom recovery on a stock rom and then get a OTA update then you find out that you need to flash the stock recovery to flash?, well this Nexus 4 Stock Recovery Flasher will sort it all out.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2413550

Nexus 4 no command but phone working please help

Hello. I have a nexus 4 that until recently i was running on 4.3 with a custom kernel from faux123 and paranoid android rom and twrp custom recovery.
Finally i decided to update it to stock 4.4 for which i restored a nandroid i had made back when the phone had stock 4.3 on it. Also, the nandroid had happened to have stock rom but custom kernel (same faux123 one). Also, before restoring nandroid i made ti backup for my apps which i successfully restored after nandroid restore.
So now i decided to flash the default 4.3 kernel which i did successfully. Now i thought i was ready for the ota update since i had everything stock except recovery so i went ahead and checked for updates.
First up was jwr66y(before that i was on 66v) which successfully downloaded and installed. Then came the 240 mb 4.4 update which downloaded but while installing after reboot gave me the dead android with 'error' message.
I then rebooted the phone which works ok but shows 4.3 as my version and also tells me im already up to date on checking for updates. So now i decided to flash ota manually using zip. However now on booting in recovery, it doesnt take me to the TWRP screen but simply shows dead android with no command message.
Also, root seems to be gone. However rest of the phone works alright. How do i fix this and successfully install 4.4 kitkat? Please help. Also can anybody shed light on why it might have happened so i can prevent it in the future.
Sent from my Nexus 4 using xda app-developers app
Tinfoil Hat Tom said:
Hello. I have a nexus 4 that until recently i was running on 4.3 with a custom kernel from faux123 and paranoid android rom and twrp custom recovery.
Finally i decided to update it to stock 4.4 for which i restored a nandroid i had made back when the phone had stock 4.3 on it. Also, the nandroid had happened to have stock rom but custom kernel (same faux123 one). Also, before restoring nandroid i made ti backup for my apps which i successfully restored after nandroid restore.
So now i decided to flash the default 4.3 kernel which i did successfully. Now i thought i was ready for the ota update since i had everything stock except recovery so i went ahead and checked for updates.
First up was jwr66y(before that i was on 66v) which successfully downloaded and installed. Then came the 240 mb 4.4 update which downloaded but while installing after reboot gave me the dead android with 'error' message.
I then rebooted the phone which works ok but shows 4.3 as my version and also tells me im already up to date on checking for updates. So now i decided to flash ota manually using zip. However now on booting in recovery, it doesnt take me to the TWRP screen but simply shows dead android with no command message.
Also, root seems to be gone. However rest of the phone works alright. How do i fix this and successfully install 4.4 kitkat? Please help. Also can anybody shed light on why it might have happened so i can prevent it in the future.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Flash the complete 4.4 KRT16S factory image. Download from here and extract the zip to your adb/platform tools directory. Make sure your drivers are working properly. If you don't want your data wiped, edit flash-all.bat and remove -w. Connect your phone and boot into the bootloader (you can do this by opening cmd in adb directory and entering "adb reboot bootloader"). Now simply run the flash-all script and wait for it to complete. You are now on KitKat 4.4
Flash TWRP and anything else you want to flash. Download and flash the 4.4.2 update if you want.
Thanks a lot for the quick reply. I managed to get root and twrp back using wugfresh's kit. It seems to me that twrp is not good with OTAs(there is a page on their site re. this) which might be the reason for this mess.
So now instead of flashing the zip using adb, can i do it with twrp? I dont have much experience with adb since i have always used twrp. (I am not averse to using cmd but the 480 mb download for the sdk just to get adb and stuff puts me off).
Do I necessarily need to wipe my data to install the kitkat update?
Sent from my Nexus 4 using xda app-developers app

Nexus 7 2013 Android Update 4.3 to 4.4.2

Do you have problems updating Nexus 7 from Jelly Bean to Kitkat? Well I did, since the day got my hands of N7 device, it was unlocked and rooted.
Somewhere is Sep the News of Kitkat has been rolling out. In Oct my N7 device notified on the new Kit Kat upgrade. I have been trying using OTA update but each time came to "FAILED" installation and so decided to give up the idea since JB 4.3 was working fine.
Now Kit Kat rolled out 4.4.2 version and still I had the same problem, did some researched on XDA forum and tried each of their suggestion but still did not work out. I was always stuck with "KoreanIME.apk" error on recovery, perhaps something I deleted earlier on.
Using Nexus Root Toolkit Ver 1.8
Finally decided to use the Nexus Root Toolkit (NRT). The last time used it was rooting the brand new N7. Run NRT and it started gathered information and upgraded to latest NRT ver 1.8.
With the new NRT version I decided to Flash Stock + Unroot, hoping I can do the update by going back to stock. To my surprise NRT found the latest Kitkat 4.4.2 and installed on Nexus 7. Most of the data was lost but had earlier done a backup. After which just like a brand new device, log in my account and immediately all the previous Apps started to download back to the device.
Once that was done, Root the device using NRT included Custom Recovery check, the rest just follow NRT instructions to install BusyBox and all is Done!!
Apps like Watsapp had to be installed manually since it does not support tablet version. Other data were also done manually.
I would not recommend this method unless you are prepared to wipe everything clean, so do a backup first. There were no other options and this was the only method.
Hope this helps and if anyone can point out the mistake I have done, do share for others.
OTA update doesn't work with custom recovery if I'm not mistaken
OTA can work with custom recovery, I've done it several times, though the custom recovery was overwritten by the update.
Sent from my SGH-I747M using xda app-developers app
Yes, OTA in the form of .zip file can be flashed via custom recovery.
But it seems that OP's problem occurs when he's trying to update from official OTA notification, from my understanding if you try to update from official OTA notification with custom recovery installed it will fail.
Please correct me if I'm wrong since mine was done through adb sideload
I did it through the official OTA (not a zip file) with a custom recovery. There seems to be a myth out there that it's not possible, but I can say from experience that it is possible.
Sent from my SGH-I747M using xda app-developers app
clienttrace said:
Yes, OTA in the form of .zip file can be flashed via custom recovery.
But it seems that OP's problem occurs when he's trying to update from official OTA notification, from my understanding if you try to update from official OTA notification with custom recovery installed it will fail.
Please correct me if I'm wrong since mine was done through adb sideload
Click to expand...
Click to collapse
Just for clarification, besides using auto OTA update, I did tried it manually using razor and SuperSu zip files. Also as you mentioned ADB sideload. It did not work out.
Somehow using NRT was much easier, just sit back and let NRT do all the job. The only setback were the missing data. Not a big issue, anyway was nice to see the file structure cleaned up.
gc84245 said:
I did it through the official OTA (not a zip file) with a custom recovery. There seems to be a myth out there that it's not possible, but I can say from experience that it is possible.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
thanks, that's clear it up for me

Categories

Resources