Related
I had my nexus 7 rooted on 4.1 and then got the ota update pushed to me. Being my first root I accepted the update not knowing I would lose root. When I tried to reroot it using nexus root toolkit it keeps saying fastboot device not found. I reinstalled all the drivers (PDAnet) and tried it many times but it still wont find the fastboot. My nexus is unlocked.
Any ideas?
You need the right drivers or it will not work.
BTW...I updated and didn't lose root at all...
Yeah, always keep ota root keeper around, and I kept root after update with that.
To atop the random reboot issue, I flashed the 4.2 image using wugs toolkit and had no problems. I even managed to root with only one nexus logo loop. -Ara
Sent from my Nexus 7 using xda app-developers app
I also accidentally accepted the ota update and lost my root. So all I need to do is to root my N7 again like the first time, is that correct? And will it wipe out all my data?
Hi There,
I have rooted my Nexus 4 Few Days ago and Still I didn't got my Android 4.3 Update. I want to know after rooting is my device getting automatically update or do I need to install it manually after downloading image from Google ?
Thanks
http://forum.xda-developers.com/showthread.php?t=2378413
Sent from my Nexus 4 using Tapatalk 4 Beta
konfidential said:
http://forum.xda-developers.com/showthread.php?t=2378413
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I know I can install it manually. I need to know whether I will get Automatic Push Up Update or Not
You're rooted... So no
Sent from my Nexus 4 using Tapatalk 4 Beta
konfidential said:
You're rooted... So no
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks Buddy.So after I Installed Image from Google Developers is it unroot again ?
Yes.. You'll lose root
Sent from my Nexus 4 using Tapatalk 4 Beta
konfidential said:
You're rooted... So no
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Actually, if your device is rooted but still running stock, you can still receive OTA updates.
AnjulaMalshan said:
Thanks Buddy.So after I Installed Image from Google Developers is it unroot again ?
Click to expand...
Click to collapse
Yes, you'll need to re-root your device.
Sent from my Nexus 4
Hi,
My Nexus 4 is rooted running stock, but with the faux kernel. Will I still get 4.3 pushed to my phone?
Either way once I install 4.3, will I have to unlock the bootloader again in order to root the phone?
Thanks, I'm new to all this business
Theonew said:
Actually, if your device is rooted but still running stock, you can still receive OTA updates.
Yes, you'll need to re-root your device.
Sent from my Nexus 4
Click to expand...
Click to collapse
I received update notification, my Nexus 4 is rooted and running stock. So if I update would I lose root? and when I root again would I lose my data unless I backup and restore it later?
Thank you.
kannaiah said:
I received update notification, my Nexus 4 is rooted and running stock. So if I update would I lose root? and when I root again would I lose my data unless I backup and restore it later?
Thank you.
Click to expand...
Click to collapse
You will lose root. once you re-root it you will not lose any data. just to be safe create a backup before upgrading to 4.3
I received my Nexus 4 on March 2 2013.
It was running Jelly Bean 4.2 out of the box but, soon after I connected to my wifi, the phone automatically downloaded 4.2.2 and was ready to install. I upgraded to 4.2.2 without making any modifications or added any apps to the phone.
I then rooted my phone using Nexus Root Toolkit v1.6.3 by Wug. It used SuperSU and BusyBox Free, and installed the TWRP custom recovery.
A week later I installed the faux123 kernel. I have not installed any custom ROM at all.
On July 31 2013 I noticed the 4.3 update had been automatically downloaded and ready to install (there was a persistent notification in the status bar as well as a "Restart & Install" message in About phone -> System updates).
Just now (yes I know it has been a week but I had been rather busy so I did my backups in parts) I tried to install the 4.3 update. After the restart I was dumped into TWRP's recovery screen. Not knowing what to do I chose Reboot -> System. The phone started up as normal, but once the boot has completed, I found that I am still on 4.2.2, still rooted, and still running the faux123 kernel. But now - even after reboots and rechecks - About phone -> System updates tells me that "Your system is up to date"!?!?
STRANGE...
xdakewie said:
I received my Nexus 4 on March 2 2013.
It was running Jelly Bean 4.2 out of the box but, soon after I connected to my wifi, the phone automatically downloaded 4.2.2 and was ready to install. I upgraded to 4.2.2 without making any modifications or added any apps to the phone.
I then rooted my phone using Nexus Root Toolkit v1.6.3 by Wug. It used SuperSU and BusyBox Free, and installed the TWRP custom recovery.
A week later I installed the faux123 kernel. I have not installed any custom ROM at all.
On July 31 2013 I noticed the 4.3 update had been automatically downloaded and ready to install (there was a persistent notification in the status bar as well as a "Restart & Install" message in About phone -> System updates).
Just now (yes I know it has been a week but I had been rather busy so I did my backups in parts) I tried to install the 4.3 update. After the restart I was dumped into TWRP's recovery screen. Not knowing what to do I chose Reboot -> System. The phone started up as normal, but once the boot has completed, I found that I am still on 4.2.2, still rooted, and still running the faux123 kernel. But now - even after reboots and rechecks - About phone -> System updates tells me that "Your system is up to date"!?!?
STRANGE...
Click to expand...
Click to collapse
I also get the same thing. I rooted my official jellybean 4.2.2 to with nexus 4 tool kit. I have teamwin recovery mode . I get on my phn there is an update 4.3 when i press restart and install its restarting to teamwin recovery mode and nothings updated when i boot back to system still get 4.2.2 ver. How do I update the official firmware?
crashzonecz said:
I also get the same thing. I rooted my official jellybean 4.2.2 to with nexus 4 tool kit. I have teamwin recovery mode . I get on my phn there is an update 4.3 when i press restart and install its restarting to teamwin recovery mode and nothings updated when i boot back to system still get 4.2.2 ver. How do I update the official firmware?
Click to expand...
Click to collapse
hi there!
after 3-4 days of telling me my "system is up to date", i got another auto-download and prompt to update yesterday. this time i tried to look for the downloaded update file on my emulated SD card when in TWRP but i couldn't find it; so i chose Restart->System like i did before and again (naturally) nothing was updated (and thank goodness at least nothing broke as far as i could see).
from what i've read i believe we will all get such OTA update notices. however, to successfully update using the downloaded file, we would need our phones to be in stock condition (no root, no custom ROM or kernel, etc.). now this 4.3 update as compared to 4.2.2 isn't all that appealing to me, so i think i will wait for a few months to see there are no bugs before attempting to update again.
if you would like to update now, i suggest you read this thread http://forum.xda-developers.com/showthread.php?t=2390127 in which a member advised on using TWRP to handle the updating and not having to re-root your phone after that. hope it helps, and good luck to you!
just do it manually! It's soo simple..
follow these great instructions:
http://forum.xda-developers.com/showthread.php?t=2145848
Look out with flashing userdata userdata.img, dependent on the instructions you choose you have to remove/skip this one because it will erase all your data!
If you want root, install the latest SuperSU 1.5 after you're done.
I also would make a nandroid (full backup) with CWM/TWRP before you start.. if something goes wrong you can always revert all steps.
hi,
apologies if this has been asked before but my searches have not found a clear answer. i have a 2012 nexus 7 Rooted and running JB 4.2.2.
the OTA update to JB 4.3 fails everytime. it gets so far and then shows the android logo with a red triangle exclamation and just "error"
it reboots back to home screen after a minute or two.
my device was rooted using WUGS toolkit and TWRP recovery. i just did the basic rooting so i could use stickmount and have done nothing funny with the device since.
i have seen many guides about flashing 4.3 update that will wipe the device which i really want to avoid.
will it work if i just un-root and re-lock the device with the toolkit and then run the OTA update or is it more complicated than that.
Lemegeton300 said:
hi,
apologies if this has been asked before but my searches have not found a clear answer. i have a 2012 nexus 7 Rooted and running JB 4.2.2.
the OTA update to JB 4.3 fails everytime. it gets so far and then shows the android logo with a red triangle exclamation and just "error"
it reboots back to home screen after a minute or two.
my device was rooted using WUGS toolkit and TWRP recovery. i just did the basic rooting so i could use stickmount and have done nothing funny with the device since.
i have seen many guides about flashing 4.3 update that will wipe the device which i really want to avoid.
will it work if i just un-root and re-lock the device with the toolkit and then run the OTA update or is it more complicated than that.
Click to expand...
Click to collapse
Same Here!, I had TWRP recovery and I'm rooted, so Just Flashed stock recovery and I though I can update easily. But now I can't!
-By the way, I did not change any system file.
Since you have Stickmount did your error message reference a bad file check on 'debuggerd' in the /system/bin folder? It seems Stickmount may replace or alter that file and you have to put back an original for 4.2.2 to successfully flash the update with TWRP. After replacing 'debuggerd', the update flashed just fine for me. Are you sure you didn't get any text other than 'Error'? Are you sure you didn't freeze or delete any system apps?
It also happened to my nexus 4, they recommended to use this way: (It won't erase the data)
http://forum.xda-developers.com/showthread.php?t=2377307
hey, the error has no message or info. it literally says the word "error" with red exclamation and thats it. i have not touched any of the system apps or done anything that could upset the system files.
i will try the suggestion from alipashang77, thanks
sorry but those instructions are for the samsung galaxy nexus phone.
does not apply to my nexus 7 tablet.
any suggestions
Lemegeton300 said:
sorry but those instructions are for the samsung galaxy nexus phone.
does not apply to my nexus 7 tablet.
any suggestions
Click to expand...
Click to collapse
There's tonnes of older posts with all the info you'll need. Gotta just search more.
Ota will erase everything except your internal/external sd cards. Plus ota wont work if anything system wise had been altered. You'd have to Odin stock 4.2.2 then do ota.
No reason why you can't just flash a 4.3 rom like anything else tho.
And in all cases, wiping your data and apps is best. You gotta back it up. Restore after. Apps and their data anyway. Restoring system app data is never ever a good idea.
Sent from my cellular telephone
Device won't update via OTA with a custom recovery. And 4.3 OTA will fail if you're rooted. So in order to get OTA make sure you have stock recovery and unroot, then as long as you haven't modified anything system wise it should update successfully. And no, OTA updates will not wipe any data.
Sent from my Nexus 7 using xda premium
thanks everyone. its finally updated to 4.3. i backed up my data and then flashed the stock 4.3 image and that failed and the device would not boot. i thought it was bricked but it let me flash the 4.2.2. image and then the 4.3 OTA update worked.
:good::good::good::good::good:
hi guys i know that the previous reply was that flashing to the 4.2.2 worked then the OTA worked, however i have an explaination for people that were stuck like me
i JUST managed to upgrade my nexus 7 to 4.3 (JWR66Y)
i found a helpful link to upgrade from http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
after following all the steps, my i wasnt able to flash the bootloader (bootloader-grouper-4.23.img).
after doing some googling today, i found that it is the bootloader in the 4.3 update that is different (according to http://forum.xda-developers.com/showthread.php?t=2417097&page=2) and that you need the JWR66V bootloader img file (which is also the bootloader-grouper-4.23.img) they explain it in the link above, and have a download link for it there.
so in order to do the update, what you need to do is follow the steps from the 1st link (extract all the files etc in place), but before flashing, copy the bootloader from the 2nd link into your platform-tools folder, then follow the steps to flash.
as long as you follow the steps, and skip step 10, you will keep your data also
hope that helped
95Z28 said:
Device won't update via OTA with a custom recovery. And 4.3 OTA will fail if you're rooted. So in order to get OTA make sure you have stock recovery and unroot, then as long as you haven't modified anything system wise it should update successfully. And no, OTA updates will not wipe any data.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Per WugFresh's advice, if you're rooted and using stock reovery, you still can OTA update.
Link: http://www.wugfresh.com/nrt/faqs/
vndnguyen said:
Per WugFresh's advice, if you're rooted and using stock reovery, you still can OTA update.
Link: http://www.wugfresh.com/nrt/faqs/
Click to expand...
Click to collapse
Past OTAs would be successful when rooted, you would usually just lose root access. But the 4.3 OTA won't work while rooted, you'll just keep getting the failed message.
Sent from my Galaxy Nexus using xda premium
95Z28 said:
Past OTAs would be successful when rooted, you would usually just lose root access. But the 4.3 OTA won't work while rooted, you'll just keep getting the failed message.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
ok thanks. I'm on 4.3 and only root with stock recovery. So if the 4.4 available I will unroot and then OTA. Thanks!
Today I received the ota for 4.4 on my Nexus 4 and when I pressed "restart and install" it went to my custom recovery (which was flickering BTW Idk why never seen it do that before) and when I restarted it I wasn't running 4.4. I found the download location for the OTA would it be OK for me to boot into twrp and simply flash it like I would any other custom rom? Just wanted to ask before I did it.
Sent from my Nexus 4 using xda app-developers app
tsmith9191 said:
Today I received the ota for 4.4 on my Nexus 4 and when I pressed "restart and install" it went to my custom recovery (which was flickering BTW Idk why never seen it do that before) and when I restarted it I wasn't running 4.4. I found the download location for the OTA would it be OK for me to boot into twrp and simply flash it like I would any other custom rom? Just wanted to ask before I did it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hi, What format is it in? Unless it's in a zip format (which I doubt) then flagging it through recovery won't work I think .. I'll have a poke about and see what I can find ..
K
Sent from my Nexus 4 using Tapatalk 2
Hi can you tell me where you found the ota folder I am looking for it but can't locate it.I had the same problem as you.I think we need to be on stock recovery for it to install.
Sent from my Nexus 4 using xda app-developers app
Usually a root browser go to root and it is under the cache folder.
Sent from my Nexus 4 using xda app-developers app
krrunch said:
Hi, What format is it in? Unless it's in a zip format (which I doubt) then flagging it through recovery won't work I think .. I'll have a poke about and see what I can find ..
K
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
OK and yes it is in a zip format
Sent from my Nexus 4 using xda app-developers app
tsmith9191 said:
Today I received the ota for 4.4 on my Nexus 4 and when I pressed "restart and install" it went to my custom recovery (which was flickering BTW Idk why never seen it do that before) and when I restarted it I wasn't running 4.4. I found the download location for the OTA would it be OK for me to boot into twrp and simply flash it like I would any other custom rom? Just wanted to ask before I did it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Depending on how the ota image is packaged you may want to take a look at this thread here
http://forum.xda-developers.com/showthread.php?t=2010312
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
Hth
K
--------
:: Nexus 4 :: SlimKat :: Faux mainline ::
---------- Post added at 10:13 PM ---------- Previous post was at 10:08 PM ----------
tsmith9191 said:
OK and yes it is in a zip format
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Then I see no reason why you can't give it a go Make sure you have a backup of everything though before you go ahead .. I'm assuming you already have an unlocked bootloader ..
--------------------------------------------------------------
:: Nexus 4 :: SlimKat :: Faux mainline ::
Yes I do have an unlocked bootloader
Sent from my Nexus 4 using xda app-developers app
guys you can't flash the OTA while running custom recovery or roms. If you want to be on kitkat why not just download one of the many stock rooted roms out there? Make your life simple and for future reference like I said custom recovery will not flash OTA unless its been manipulated by someone
I tested flashing OTA using latest TWRP successfully on a 100% unmodified stock rom with no root. CWM on the other hand is not compatible for flashing OTA.
I do not recommend doing this, modifications to your /systems partition or root can cause it to fail and softbrick. I have heard people hardbricking their device too due to the bootloader getting corrupted in the process.
Make a backup before you flash.
I have installed franco kernel but I backed up the stock kernel and restored it. I have also used xposed but I uninstalled that as well as disabled and uninstalled the only module I was running which was gravity box.
Sent from my Nexus 4 using xda app-developers app
eksasol said:
I tested flashing OTA using latest TWRP successfully on a 100% unmodified stock rom with no root. CWM on the other hand is not compatible for flashing OTA.
I do not recommend doing this, modifications to your /systems partition or root can cause it to fail and softbrick. I have heard people hardbricking their device too due to the bootloader getting corrupted in the process.
Make a backup before you flash.
Click to expand...
Click to collapse
What do you recommend I do to receive the 4.4 update without losing data?
Sent from my Nexus 4 using xda app-developers app
tsmith9191 said:
What do you recommend I do to receive the 4.4 update without losing data?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Backup your data partition first, then follow either of the two guide links in my signature to flash 4.4 factory image without wiping data.
I had the same problem yesterday where the OTA made absolutely no changes (This method worked fine when I went from 4.2 to 4.3 under the same conditions; TWRP, unlocked bootloader, and stock ROM). It may be related to a new conflict with TWRP. I also had a hybrid radio installed, but I put the stock radio back in before I tried the OTA; however there were a couple changes associated with this such as build prop changes and LTE activation that I did not revert. Who knows. After searching this forum I came across a fix in the "Nexus 4 OTA Help-Desk" thread...fancy that. If you have the Android SDK installed, this is a really quick and easy fix.
1) Under "Factory Images "occam" for Nexus 4" I downloaded "4.4 (KRT16S)".
https://developers.google.com/android/nexus/images#occamkrt16s
2) I then followed these directions (WARNING: Note the instructions to remove the "-w" from the flash-all.bat file before you run it. This will retain all your existing data, apps, settings, etc.).
http://forum.xda-developers.com/showthread.php?t=2527142
3) I then installed the latest versions of TWRP (for recovery) and superuser (for root).
Now I have a fully functioning 4.4 install with no loss of data. I am holding off on the new hybrid radio until things stabilize a bit with that.
pjc123 said:
I had the same problem yesterday where the OTA made absolutely no changes (This method worked fine when I went from 4.2 to 4.3 under the same conditions; TWRP, unlocked bootloader, and stock ROM). It may be related to a new conflict with TWRP. I also had a hybrid radio installed, but I put the stock radio back in before I tried the OTA; however there were a couple changes associated with this such as build prop changes and LTE activation that I did not revert. Who knows. After searching this forum I came across a fix in the "Nexus 4 OTA Help-Desk" thread...fancy that. If you have the Android SDK installed, this is a really quick and easy fix.
1) Under "Factory Images "occam" for Nexus 4" I downloaded "4.4 (KRT16S)".
https://developers.google.com/android/nexus/images#occamkrt16s
2) I then followed these directions (WARNING: Note the instructions to remove the "-w" from the flash-all.bat file before you run it. This will retain all your existing data, apps, settings, etc.).
http://forum.xda-developers.com/showthread.php?t=2527142
3) I then installed the latest versions of TWRP (for recovery) and superuser (for root).
Now I have a fully functioning 4.4 install with no loss of data. I am holding off on the new hybrid radio until things stabilize a bit with that.
Click to expand...
Click to collapse
Hybrid radios are fine I have been running 4.4 and .27/84 with no issues for weeks... No need to flash the 97 if you have a hybrid radio that was already working fine. sometimes just cuz its new dont make it better...
playya said:
Hybrid radios are fine I have been running 4.4 and .27/84 with no issues for weeks... No need to flash the 97 if you have a hybrid radio that was already working fine. sometimes just cuz its new dont make it better...
Click to expand...
Click to collapse
Good to know. By the way, the 27/84 hybrid radio is the only one that would work for me (quick GPS lock). I don't have LTE in my immediate area anyway (Straight Talk AT&T), so I am in no rush, and will see how the .27/97 works out for users.
pjc123 said:
I had the same problem yesterday where the OTA made absolutely no changes (This method worked fine when I went from 4.2 to 4.3 under the same conditions; TWRP, unlocked bootloader, and stock ROM). It may be related to a new conflict with TWRP. I also had a hybrid radio installed, but I put the stock radio back in before I tried the OTA; however there were a couple changes associated with this such as build prop changes and LTE activation that I did not revert. Who knows. After searching this forum I came across a fix in the "Nexus 4 OTA Help-Desk" thread...fancy that. If you have the Android SDK installed, this is a really quick and easy fix.
1) Under "Factory Images "occam" for Nexus 4" I downloaded "4.4 (KRT16S)".
https://developers.google.com/android/nexus/images#occamkrt16s
2) I then followed these directions (WARNING: Note the instructions to remove the "-w" from the flash-all.bat file before you run it. This will retain all your existing data, apps, settings, etc.).
http://forum.xda-developers.com/showthread.php?t=2527142
3) I then installed the latest versions of TWRP (for recovery) and superuser (for root).
Now I have a fully functioning 4.4 install with no loss of data. I am holding off on the new hybrid radio until things stabilize a bit with that.
Click to expand...
Click to collapse
So the directions you have listed are the ones you found at the help desk?
tsmith9191 said:
So the directions you have listed are the ones you found at the help desk?
Click to expand...
Click to collapse
Yes, and since then in other forums, and since then in eksasol's post above.
I was in the same boat as you. Flashed stock 4.4 (entire image, not just the ota) and never lost data. I did have to reroot though.
Sent from my Nexus 4, while driving in my Evo9.
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