Ok, since there seems to be a lot of people not successfully updating to 4.0.4 using the stock Google file I decided to do this poll, to shine some light on the reasons. I got the idea because it has been said that the update file is only for i9023 so here goes.
Have you successfully updated you Nexus S using the incremental OTA update file hR7QFEtn.zip?
Yes, in an i9023
No, in an i9023
Yes, in an i9020
No, in an i9020
Of course, for keeping the poll real, it would be best if the update was attempted in a stock 4.0.3 Nexus S.
Preliminary report shows that it's a matter of luck...
Nice poll!
Since it seems more like a matter of which recovery (stock or cwm) you are using to flash the update, it would be nice to add these category though, I can understand, it would made the poll a bit complicated or that ONLY full stock (locked bootloader, stock recovery) users vote.
mELIANTE said:
Of course, for keeping the poll real, it would be best if the update was attempted in a stock 4.0.3 Nexus S.
Click to expand...
Click to collapse
Its not luck, you just have to do things in the proper order. I tried updating a few different ways where I got the same errors as everyone else. I also tried another way that works, and I did it three times to prove it wasn't just luck. 1st I flashed a backup of 2.3.6 when it was complete I wiped everything, data, cache, dalvik. Then I flashed the 4.0.3 update, again wiping everything after it completed. Then I flashed the 4.0.4 update and again wipe everything. Then if you want root, flash superuser zip and reboot.
9020t stock w/root unlocked boot loader cwm recovery.
Success using cwm recovery
Sent from my Nexus S using xda premium
dls5375 said:
Its not luck, you just have to do things in the proper order. I tried updating a few different ways where I got the same errors as everyone else. I also tried another way that works, and I did it three times to prove it wasn't just luck. 1st I flashed a backup of 2.3.6 when it was complete I wiped everything, data, cache, dalvik. Then I flashed the 4.0.3 update, again wiping everything after it completed. Then I flashed the 4.0.4 update and again wipe everything. Then if you want root, flash superuser zip and reboot.
9020t stock w/root unlocked boot loader cwm recovery.
Click to expand...
Click to collapse
Did you use 2.3.6 recovery to flash 4.0.4 over 4.0.3 or did you reboot between these two steps because appart from cwm recovery, 2.3.6 recovery is reported by some as working to apply the 4.0.4 update.
Because I did every same steps as you with a reboot between each steps you describe and got the error still.
EDIT (in answer to your editing) :
dls5375 said:
9020t stock w/root unlocked boot loader cwm recovery.
Click to expand...
Click to collapse
...so the recovery seems to be the trick.
Browsing quickly (maybe too quickly...?!) the threads about 4.0.4, I was not able to find out anyone who could succesfully update to 4.0.4 with stock 4.0.3 recovery. I didn't found either someone updating OTA so at this point I'm not able to find out if the update seems to work this way.
I was on stock 4.0.3 + Matr1x, restored to 4.0.3 stock, but my SystemUI.apk seemed to be off (update rejected it). Copied SystemUI.apk from the 4.0.3 full rom and replaced the one on my phone, set permissions and the update went fine. Everything's working great. (i9023, using CWM)
csrxds said:
Since it seems more like a matter of which recovery (stock or cwm) you are using to flash the update, it would be nice to add these category though, I can understand, it would made the poll a bit complicated or that ONLY full stock (locked bootloader, stock recovery) users vote.
Click to expand...
Click to collapse
With this poll I was trying to determine if the update was i9023 specific or not.
From the looks of it, some i9020 were updated too so that isn't it.
I, for one, did the update on an unlocked i9023 with CWM and all went smooth. Granted, I had the stock 4.0.3 from Google, later rooted.
From what I've been reading, the reason some are having issues is because the update is only for phones with a IMM76D build.
I have a i9020T, unlocked bootloader but otherwise bone stock running ICS 4.0.3, Build IML74K and mine would not accept the upgrade.
I bet if you look into this a little more carefully, you find that this is the reason so many of the updates are failing.
BartmanJax said:
From what I've been reading, the reason some are having issues is because the update is only for phones with a IMM76D build.
I have a i9020T, unlocked bootloader but otherwise bone stock running ICS 4.0.3, Build IML74K and mine would not accept the upgrade.
I bet if you look into this a little more carefully, you find that this is the reason so many of the updates are failing.
Click to expand...
Click to collapse
An IMM76D build is 4.0.4.
Any working solutions that don't involve losing app data? Unrooted phone.
BartmanJax said:
From what I've been reading, the reason some are having issues is because the update is only for phones with a IMM76D build.
I have a i9020T, unlocked bootloader but otherwise bone stock running ICS 4.0.3, Build IML74K and mine would not accept the upgrade.
I bet if you look into this a little more carefully, you find that this is the reason so many of the updates are failing.
Click to expand...
Click to collapse
yes, my phone is IML74K and with error 7 during upgrade to 4.04. but i don't know why Google do nothing on this issue. wish they could resolve it soon
Sent from my Nexus S using XDA
Tried with 4.0.3 stock recovery. status 7 error.
Flashed CWM and flashed. Done.
4.0.3 Stock without root.
Solution to error 7 in stock recovery!
evil89 said:
Tried with 4.0.3 stock recovery. status 7 error.
Flashed CWM and flashed. Done.
4.0.3 Stock without root.
Click to expand...
Click to collapse
Yep, it worked the same for me! Here is how to fix it! I just reflashed a clean 2.3.6, updated to 4.0.3 and tried to update via the (broken) ICS recovery (to see what's written, use a strong light, the issue is just that the backlight is not working). It didn't work!
So, since I had not relocked my bootloader, but just unrooted, I flashed CWM and booted directly to it (if you reboot in between, it will go away). In CWM I flashed the update, rebooted and then rebooted again, so that stock recovery image would flash itself over the custom one. Done!
And what about all of us who didnt root or unlock the bootloader? Are we talking about the biggest, epic FAIL in the history of Android????
Because if we get it right, in order to apply the OFFICIAL, I repeat, THE OFFICIAL update, you have to flash a custom recovery??????
Simply ridiculous...
Works just fine on 9020t if u all would remember correctly that was the first person who reported getting the OTA in this forum, stop the false claims...
Sent from my Nexus S using XDA App
Not working for me and I have a un rooted i9020a nexus s
Sent from my Nexus S using XDA
Updated from stock 4.0.3 with ClockworkMod 5.0.2.0 without problems. System is unlocked and rooted. Hopefully the occasional freezes are now history.
9020a
axellink said:
Not working for me and I have a un rooted i9020a nexus s
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Do you already have 4.0.3 installed?
I got it to work on my i9020a using CWM recovery. If you've made any system file tweaks it will fail. Mine was giving me an error on the Music2.apk file since I had actually deleted it since I had installed CM Music app as my default music player. I just used a copy of the full 4.0.3 zip file, dug through it to find the Music2.apk file and put it back under /system/apps/ and set it's permissions accordingly. Then I was able to run this patch without any issues.
I'm no expert, but if you need more help, just ask!
An interesting question to the poll would have been, for those who could install, did you use the stock recovery?
Related
Got the Nexus One OTA for Android v2.3.6 GRK39F this morning.
"This OTA update will upgrade your device to Gingerbread 2.3.6. IT contains important bug fixes and security patches."
Attached the d323ca384aaa.signed-passion-GRK39F-from-GRJ22.d323ca38.zip update file.
Guess this should have gone into the development forum, but I am not allowed to post there yet.
any idea what changes this brings?
I have not used the nexus one in quite some time but have not ran stock in even longer but here are some things I noticed.
During the update it says it is replacing recovery. So I assume there is a new stock recovery. It looks the same and the version is 3e. Again not sure what it was prior.
Some apps are installed in the rom that I do not recall being there prior. Facebook/twitter.
Kernel is 2.6.35-59465.
Clean install of stock rom (passing.img) ota to 2.3.4 then flashed the update in this post to 2.3.6
Is there a difference in free space after updating?
Sent from my Nexus One using xda premium
I cannot install it after playing with my 2.3.4 (removing some stock apps, moving some system apps to user apps and to sdcard) ?
Maybe someone can prepare 2.3.6 revision with root permissions and without hash checks?
I love Google's changelogs, if they ever published one...
Well they just say that it contains some security patches and bug fixes.....!thats what is expected to be in it....!
Has anyone checked if this breaks USB and wifi tethering like the Nexus S 4G update did?
Tethering is there. 178mb free on clean install
I've used passim.img method and now see the 2.3.6 ota but can't download it (the download fail eveery time )... any solution?
albundy2010 said:
I have not used the nexus one in quite some time but have not ran stock in even longer but here are some things I noticed.
During the update it says it is replacing recovery. So I assume there is a new stock recovery. It looks the same and the version is 3e. Again not sure what it was prior.
Some apps are installed in the rom that I do not recall being there prior. Facebook/twitter.
[snip]
Click to expand...
Click to collapse
Every OTA update replaces the recovery.
Facebook and Twitter have always been included in the stock ROM
Sent from my Nexus One using Tapatalk
I don't think the ota's in the past have replaced the recovery. I know the recovery always gets overwritten when you actually boot up the os. This ota updated, or at least it said its updating the recovery from the flash itself.
If this happened with all the other otas in the past then people would not have been able to flash the ota on a rooted stock rom with cwm then flash su.zip prior to booting the os and having the recovery script in the ota wipe it back to stock.
This update replaced the stock recovery while the phone was in recovery installing the ota, not while booting.
I am tempted to passimg back to froyo, get the ota up to 2.3.4, put the ota.zip on the SD card, flash cmw via fastboot. Boot into it and flash the ota. Then see if cwm is still there prior to booting the os.
albundy2010 said:
I am tempted to passimg back to froyo, get the ota up to 2.3.4, put the ota.zip on the SD card, flash cmw via fastboot. Boot into it and flash the ota. Then see if cwm is still there prior to booting the os.
Click to expand...
Click to collapse
I just placed the updated on my sdcard, booted into recovery, flashed the update then flashed su.
Sent from my Nexus One using Tapatalk
I lost pinch to zoom capabilities in the picture gallery after the update. Pinch to zoom still works in the browser and maps though. Anyone else notice this?
Sent from my Nexus One using XDA App
Hwaiting said:
I lost pinch to zoom capabilities in the picture gallery after the update. Pinch to zoom still works in the browser and maps though. Anyone else notice this?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Pinch and zoom doesn't work on the native gallery for me either. I use Quickpic and it works just fine on that app.
Can someone do me a favor and post the nandroid backup of this 2.3.6 build? I don't need your data partition, just the boot.img and the system.img. I need it to get the proprietaries to try to make a ROM.
BuglessPete said:
Can someone do me a favor and post the nandroid backup of this 2.3.6 build? I don't need your data partition, just the boot.img and the system.img. I need it to get the proprietaries to try to make a ROM.
Click to expand...
Click to collapse
You are building for the N1 now? Sweet! Let me unroot and install a stock rom and then get the update and get you it. My bootloader is unlocked would that matter?
I put it up in the other thread. And some1 posted it in development as well.
Ok so I can't use the Passimg Method to downgrade then update. I am having a heck of a time trying to find a Stock Untouched GRJ22 2.3.4 ROM to flash so I can get this update. Any one got a link to a Stock GRJ22 ROM? Is there a direct link from Google for the Full GRJ22 ROM?
hi. i'm pretty new to all this. a few months ago, i unlocked the bootloader on my atrix 4g and also rooted it. i then flashed the ICS CM7 rom using cwm. after a few days of playing with the new rom, i decided to go back to 2.3.4 by flashing the 2.3.4 fruitcake. i see now that 2.3.6 ota update is available when i check for updates from my phone. if i install this ota update, will i brick my phone? i still have the unlocked bootloader but no longer have root.
Applying the 2.3.6 OTA on a fruitcake 2.3.4 may cause a soft brick/boot loop. IMO wait until others respond with more definitive results. Don't be the first guinea pig . I had a stock, locked and rooted 2.3.4 prior to the 2.3.6 update.
nvd425 said:
hi. i'm pretty new to all this. a few months ago, i unlocked the bootloader on my atrix 4g and also rooted it. i then flashed the ICS CM7 rom using cwm. after a few days of playing with the new rom, i decided to go back to 2.3.4 by flashing the 2.3.4 fruitcake. i see now that 2.3.6 ota update is available when i check for updates from my phone. if i install this ota update, will i brick my phone? i still have the unlocked bootloader but no longer have root.
Click to expand...
Click to collapse
Don't quote me on this, but if you flashed back to 2.3.4 using RSD and then applied the update you should be okay. Caveat emptor, as always, and do it at your own risk.
There may be some unknown consequences, though. Maybe flashing back to 2.3.4 after applying the update will brick your phone, like the 2.3.4 update did with 1.8.3. You will definitely lose root, and from what I hear some of the old rooting methods don't work anymore.
If you are rooted and unlocked and had modified systems flashing worth RSD lite to get back to stock is the way to go before the update. Flashing back to .91 after installing the update WILL brick the phone for sure so don't.
Sent From Rob's ATRIX.
If you are using fruitcake 2.3.4, the OTA update to 2.3.6 will work, as the difference between a fruitcake 2.3.4 and the official one is that it does not touch the recovery and boot. As your phone was running official 2.3.4 before cm7, the changes to boot and recovery are already in place. The only possible downside is that you will not be able to roll back to "official" 2.3.4. You will have to flash CWM and flash fruitcake 2.3.4 to roll back.
This isn't stock ICS is it?
No, it is the latest gingerbread update.
Dogie52 said:
This isn't stock ICS is it?
Click to expand...
Click to collapse
Miguelyl said:
No, it is the latest gingerbread update.
Click to expand...
Click to collapse
Alright thanks
Miguelyl said:
If you are using fruitcake 2.3.4, the OTA update to 2.3.6 will work, as the difference between a fruitcake 2.3.4 and the official one is that it does not touch the recovery and boot. As your phone was running official 2.3.4 before cm7, the changes to boot and recovery are already in place. The only possible downside is that you will not be able to roll back to "official" 2.3.4. You will have to flash CWM and flash fruitcake 2.3.4 to roll back.
Click to expand...
Click to collapse
I think I get it...almost .
Could you verify #2 and fill in #3?
1) locked, stock 2.3.4: recovery and boot are stock
2) unlocked, flash CM7 or other ROMS: recovery and boot are NOT stock...applying the 2.3.6 OTA at this point can semi-fubar your phone with a bootloop and/or softbrick
3) fruitcake 2.3.x : recovery and boot are ???...applying the OTA = ???
I searched xda and could not find anything stating that applying future OTAs over a fruitcake 2.3.x will be successful. My search skillz could be lacking, so apologies ahead of time .
2) You cannot OTA update from those roms, there is no way to do it. I doubt anyone will even try to update.zip the OTA over CM7 or any other custom rom.
3) Recovery is non stock, boot is stock (as last official update installed). After the update, stock recovery will be installed, boot will change to 2.3.6 so it will prevent downgrade. Will have to flash CWM again to have access to custom roms and fruitcakes.
This is as I understand it. If anyone has more info you are welcome to share.
gnahc79 said:
I think I get it...almost .
Could you verify #2 and fill in #3?
1) locked, stock 2.3.4: recovery and boot are stock
2) unlocked, flash CM7 or other ROMS: recovery and boot are NOT stock...applying the 2.3.6 OTA at this point can semi-fubar your phone with a bootloop and/or softbrick
3) fruitcake 2.3.x : recovery and boot are ???...applying the OTA = ???
I searched xda and could not find anything stating that applying future OTAs over a fruitcake 2.3.x will be successful. My search skillz could be lacking, so apologies ahead of time .
Click to expand...
Click to collapse
Update on this. DO NOT UPDATE ON AN UNLOCKED BOOTLOADER!!! FRUITCAKE OR ANY OTHER CUSTOM ROM. YOU WILL BRICK. WAIT FOR FRUITCAKE.
Miguelyl said:
2) You cannot OTA update from those roms, there is no way to do it. I doubt anyone will even try to update.zip the OTA over CM7 or any other custom rom.
3) Recovery is non stock, boot is stock (as last official update installed). After the update, stock recovery will be installed, boot will change to 2.3.6 so it will prevent downgrade. Will have to flash CWM again to have access to custom roms and fruitcakes.
This is as I understand it. If anyone has more info you are welcome to share.
Click to expand...
Click to collapse
Well, crap. Wish I had seen this beforehand. My phone is currently stuck with 3 green Chinese characters on the screen with the goapk website subtitle.
Have unlocked bootloader, upgraded to previous firmware OTA (didn't flash pudding), no ROMs.
Any suggestions would be much appreciated.
Miguelyl said:
Update on this. DO NOT UPDATE ON AN UNLOCKED BOOTLOADER!!! FRUITCAKE OR ANY OTHER CUSTOM ROM. YOU WILL BRICK. WAIT FOR FRUITCAKE.
Click to expand...
Click to collapse
thanks for the update. that's what I thought...once you unlock you can never apply any future OTA updates. After unlocking you can get 'stock' only through fruitcake.
You are stuck on recovery. Goapk is tenfar cwm recovery. Fastboot wipe and then flash 2.3.4 fruitcake.
Eionai said:
Well, crap. Wish I had seen this beforehand. My phone is currently stuck with 3 green Chinese characters on the screen with the goapk website subtitle.
Have unlocked bootloader, upgraded to previous firmware OTA (didn't flash pudding), no ROMs.
Any suggestions would be much appreciated.
Click to expand...
Click to collapse
---------- Post added at 10:31 PM ---------- Previous post was at 10:24 PM ----------
You can normally rsd lite to 4.5.91 but there are reports that after doing that, updating
to 4.5.141 results in a brick. Some have succeeded, some don't.
So the safe route is to wait for fruitcake.
gnahc79 said:
thanks for the update. that's what I thought...once you unlock you can never apply any future OTA updates. After unlocking you can get 'stock' only through fruitcake.
Click to expand...
Click to collapse
For those afraid of losing root
It is true you will lose root after updating and the current root methods no longer work. However, there is one method that still does; the fastboot method. Instructions and files can be found here:
http://www.atrixforums.com/forum/mo...ons-including-stock-locked-2-3-4-2-3-6-a.html
(Note: Instructions are right after Pete's Root Tools Method)
In order for this to work you will need to make sure that all traces of root has been removed from you phone or it will fail to write su to the correct directory due to not enough memory being available. There are a few ways to remove all traces of root. One way is to flash the sbf file of the current version you are on. After flashing just uninstall superuser like you would uninstall any other app.
Another method of completely removing all traces of root is through the preinstall root method. It can be found at the same link from above under How to Un-root after using the /preinstall root method (I think this will only work if you used the fastboot method to gain root, I have not tried it myself).
You could also use the Motorola Software Update Tool to flash the update which should remove all traces of root. It can be found here:
http://direct.motorola.com/hellomot...SoftwareUpdateforATTATRIX4Gversion.4.5.91.pdf
As of right now the fastboot method seems to be the only way to root this version of the software. I actually tried all the current methods including the recent Motofail method that was discovered by Dan Rosenburg, but all have failed.
As a side note, those that are waiting for an official ICS rom will be getting one in the 3Q. Check it out on Motorola's Software Upgrade News page.
https://forums.motorola.com/pages/00add97d6c
Miguelyl said:
Update on this. DO NOT UPDATE ON AN UNLOCKED BOOTLOADER!!! FRUITCAKE OR ANY OTHER CUSTOM ROM. YOU WILL BRICK. WAIT FOR FRUITCAKE.
Click to expand...
Click to collapse
Not sure if this helps anyone, but I had...
1) Stock 2.3.4
2) unlocked bootloader
3) rooted via fastboot (never flashed custom recovery)
4) used Voodoo OTA bootkeeper
5) followed bootkeeper instructions
6) updated to 2.3.6
7) re-rooted
8) currently i have no unlocked bootloader
I am unlocked, and RSD'd back to stock .91 and then applied the update and got a soft-brick - I did discover that I was able to flash the 2.3.6 sbf and it worked fine.... The preinstall method gave me root access back... I would not recommend trying to downgrade back to 4.5.91 after upgrading to 4.5.141 until we have more info about it....
Okay so if I used the pudding method(2.3.4/4.5.91):
1)am I unlocked, or just rooted?
2)what method should I use to install the 2.3.6 update?
OTA obviously isn't working, and I'm thinking I can just flash back to another rom, then OTA update ..any suggestions?
Sent from my MB860 using XDA App
How is the overall feedback of this OTA update? Ya I have seen the change logs but real world feedback from users is always important.
Sent from my MB860 using Tapatalk
Excause me guys but what languages are inclueded in this new firmware?
Can you please help me answer how to install OTA updated with CWM installed. I get this error saying the installation aborted .. it boots into CWM
is there any step by step method to get the new update on nexus 4
Thanks
you need stock rom, no modifications made, and stock kernel for it to work
Download and extract the original 4.2 and fastboot flash system system.img and it'll restore all missing apps.. I had to do it earlier to allow the system to install the update
Sent from my Nexus 4 using xda app-developers app
I reflashed stock recovery but now the update isn't available. Any ideas?
billybennett said:
I reflashed stock recovery but now the update isn't available. Any ideas?
Click to expand...
Click to collapse
update manually.
So I got my update but it keeps failing during install. I'm rooted and every time the update starts it kicks over to CWM recovery and stops with a message something like, "do you want to install this untrusted zip file" I say yes but it still fails. I have even tried to manually install the update through CWM but that fails too. My N7 is rooted but otherwise stock, I have not removed any stock apps or flashed roms or kernels so WTF must I do???
Did you not read the posts above yours? CWM recovery is not stock.
Sent from Arkham
zelendel said:
Did you not read the posts above yours? CWM recovery is not stock.
Sent from Arkham
Click to expand...
Click to collapse
I don't know where, but I saw a few posts about working updates to 4.2.1 with CWM recovery.
However, I'm not getting it to work.
How do I get rid of the recovery without loosing the root?
If you are on Windows I find the Nexus 4 Toolkit to be super easy to use. I flashed a stock recovery so I could get the update. Unfortunately, I forgot I had made changes to the stock weather widget so I can't apply the update anymore because of a missing geniewidget.odex file.
You will need to be fully stock to get the update to take as posted earlier in this thread. This is a well known requirement when doing OTA
Sent from Arkham
4.2.1 update getting installation aborted
Hey, can some please post the stock Nexus 4 v4.2 build.prop file? I can't seem to install the v4.2.1 update without it...
Thanks...
zelendel said:
You will need to be fully stock to get the update to take as posted earlier in this thread. This is a well known requirement when doing OTA
Sent from Arkham
Click to expand...
Click to collapse
Successfully installed OTA here while rooted with CWM recovery, though everything else is stock.
billybennett said:
If you are on Windows I find the Nexus 4 Toolkit to be super easy to use. I flashed a stock recovery so I could get the update. Unfortunately, I forgot I had made changes to the stock weather widget so I can't apply the update anymore because of a missing geniewidget.odex file.
Click to expand...
Click to collapse
Hey,
got an Error over here with stock recovery and root.
However, tengen says he made it with CWM and root - maybe it's because I'm using stuff like Busybox or the Pimp my Rom APK?
EDIT: I think its because of the %-BatteryMod I'm using. I'll try to flash the custom rom.
Greetings
Hello. I searched the forums and came up empty.
I have a stock 4.2 ROM I rooted. When the system says its updating and rebooting. It kicks me into recovery screen and does not up date.
Do I have to unroot and re lock the boot loader?
I know I'm probably just missing something stupid.
Thanks for any help.
If you were on a custom rom before then your recovery is probably messed up and not the stock recovery. Otherwise I do not know what it is that can be doing it because every time I would flash back to stock 4.2 I would get prompted to update to 4.2.1 and as well to note I have an unlocked bootloader and from what I have read before being rooted shouldnt make a difference.
Perhaps you could grab the toolkit and flash the stock recovery that is in it to your N7 and see if that helps you out.
jonnyg1097 said:
If you were on a custom rom before then your recovery is probably messed up and not the stock recovery. Otherwise I do not know what it is that can be doing it because every time I would flash back to stock 4.2 I would get prompted to update to 4.2.1 and as well to note I have an unlocked bootloader and from what I have read before being rooted shouldnt make a difference.
Perhaps you could grab the toolkit and flash the stock recovery that is in it to your N7 and see if that helps you out.
Click to expand...
Click to collapse
Crap. I was hoping I didn't have to reflash. I dont have a custom ROM never have. I just unlocked this and rooted.
I'm going to try the toolkit when I get home revert from stock to stock, see if the update takes then.
Thanks for you help.
Edit. Looks like I have twrp recovery. This is my issue I assume. Is there a zip I can just flash to update
I have removed twrp back to stock recovery. Now when system reboots to install update, it stats the update then gives me a error. No error code just error. I really dont want to wipe my device as I have it setup for my liking.
I'm using wug's toolkit
I think (...and may be wrong...), but if you modified anything in /system (deleted any of the stock apps and/or updated them) it won't update either.
RMarkwald said:
I think (...and may be wrong...), but if you modified anything in /system (deleted any of the stock apps and/or updated them) it won't update either.
Click to expand...
Click to collapse
I owe u a beer. I did add browser.apk to my system dir. I removed it and now I'm fully updated.
Thank you so much.
root keeper and I'm back in business.
I am not seeing any stock rooted 4.2.2 roms anywhere which is how I have usually updated in the past with my phones. So unless I missed a thread with a stock rooted 4.2.2, which would be nice, what would be the easiest method for me that preferably doesn't involve a computer or wiping my data but keeping root? I am currently on 4.2.1 stock rooted.
I think I tried using ota root keeper when the ota first hit but the update failed for some reason so I deleted it out of the cache folder and haven't been notified of it again. I have read this is probably because I don't have the stock recovery installed.
Thanks
Evo_Shift said:
I am not seeing any stock rooted 4.2.2 roms anywhere which is how I have usually updated in the past with my phones. So unless I missed a thread with a stock rooted 4.2.2, which would be nice, what would be the easiest method for me that preferably doesn't involve a computer or wiping my data but keeping root? I am currently on 4.2.1 stock rooted.
I think I tried using ota root keeper when the ota first hit but the update failed for some reason so I deleted it out of the cache folder and haven't been notified of it again. I have read this is probably because I don't have the stock recovery installed.
Thanks
Click to expand...
Click to collapse
I think you can flash the update form here. Than get the
Flashable SuperSU update and flash it after upadting, You need a custom recovery to do that as you may know already.
N.B: Please keep a backup first just to be safe.
Evo_Shift said:
I am not seeing any stock rooted 4.2.2 roms anywhere which is how I have usually updated in the past with my phones. So unless I missed a thread with a stock rooted 4.2.2, which would be nice, what would be the easiest method for me that preferably doesn't involve a computer or wiping my data but keeping root? I am currently on 4.2.1 stock rooted.
I think I tried using ota root keeper when the ota first hit but the update failed for some reason so I deleted it out of the cache folder and haven't been notified of it again. I have read this is probably because I don't have the stock recovery installed.
Thanks
Click to expand...
Click to collapse
Here's what I used, its in the android development section:
Nexus 7 (WiFi)
http://forum.xda-developers.com/showthread.php?t=2148337
Sent from my HTC Sensation XE with Beats Audio using xda app-developers app