Hello all. I am in need of some assistance. I had bought the wifi nexus 7 (2012) rooted for my son... it had aokp rom booted on it.. my other son has a stock nexus 7 and received the update.. can someone please help me and guide me know how to update his nexus to 4.4 stock rom.. I'm not a stranger to rooting and such. He currently has the newest version of twrp recovery and bootloader 4.13.
Thank you in advance.
Sent from my SM-N900V using xda app-developers app
jjdicecco said:
Hello all. I am in need of some assistance. I had bought the wifi nexus 7 (2012) rooted for my son... it had aokp rom booted on it.. my other son has a stock nexus 7 and received the update.. can someone please help me and guide me know how to update his nexus to 4.4 stock rom.. I'm not a stranger to rooting and such. He currently has the newest version of twrp recovery and bootloader 4.13.
Thank you in advance.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Hi, jjdicecco...
If you have a Nexus 7 with a Custom ROM (such as AOKP) installed on it, you won't be able to update it to stock Android 4.4 KitKat via the normal process of OTA updates.
Googles OTA updates do not work with Custom ROMs - only with Unmodified Stock
The reason why, is because OTA's aren't full ROMs - they consist of a collection of 'patches' that are applied (during the update process) to the system files in the preexisting version of official stock Android. But before those 'patches' can be applied, the OTA runs a checksum on all system files to ensure they haven't been modified... and a Custom ROM such as AOKP, represents a very significant modification of stock Android... so, in short, the OTA will abort with no changes made.
The only way to bring your AOKP Nexus 7 up to date with KitKat, is to forget about OTA's and flash the full factory image for Android 4.4 KitKat, available here. Essentially, you need to re-install the entire Android OS from scratch.
It's important you download the correct factory image for your specific Nexus 7... so if your Nexus 7 is WiFi only, you'll need the 'nakasi' image... if it's the WiFi & 3G model, then the 'nakasig' image is required.
Although there are toolkits that will get the job done (so to speak), I've never used them myself... and IMHO, you'd be better of using the fastboot tool that Google themselves provide.
There is an excellent tutorial available here on how to use fastboot to flash a factory image on the Nexus 7.
It looks a little daunting, but if, as you say, you're no stranger to rooting or flashing recoveries such as TWRP, then you shouldn't have much problem following it - it's actually quite straightforward.
Hope this helps... and good luck.
Rgrds,
Ged.
Thank you very much.. can I just flash a whole rom from development
Sent from my SM-N900V using xda app-developers app
jjdicecco said:
Thank you very much.. can I just flash a whole rom from development
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Yes, you can.
If you have TWRP installed, just download the ROM .zip of your choice directly to the Nexus 7... boot into TWRP, go to WIPE>ADVANCED WIPE and clear Dalvik Cache, System, Cache and Data... BUT UNDER NO CIRCUMSTANCES, WIPE INTERNAL STORAGE... or you'll lose the Custom ROM you just downloaded. You'll have no bootable OS, and no easy means of installing one... without resort to either ADB or fastboot.
After this, use the INSTALL button in TWRP to flash that ROM. (You'll need to navigate to where it downloaded to - usually the /download folder on the Nexus 7's internal storage).
It's a good idea, though, before doing any of this, to perform a NANDROID backup of your current AOKP system using the BACKUP button in TWRP... just in case anything goes wrong with your ROM flash, or if the ROM you flashed isn't what you expected it be.
You'll then have an easy way of getting back to your current setup.
Rgrds,
Ged.
Related
I apologize for the noob question but I've never found myself in this particular situation...
I've decided to stick with the 4.3 JWR66V factory image while I wait for a working rooted version to be released or even an updated SuperSU or Superuser zip (that doesn't drain the battery or lose root with certain apps).
I used the factory image found HERE and followed the detailed instructions found HERE. I followed the instructions under section "D" vigorously which meant that I installed the stock recovery image as well. Everything is running as it should. However, I was curious if it was safe to flash TWRP 2.6.0.0 recovery through fastboot with my current setup. I'd like to use that recovery to wipe cache/dalvik and possibly fix permissions. However, I'm not sure if this will break something so I am hesitant to try it.
I have made sure the bootloader is unlocked. But I am curious if it's safe to flash and use TWRP while I am not rooted.
You can install recovery with no problem, root has nothing to do with it. however i think upon a reboot your recovery will be replaced with factory.
Interesting. I wonder why/how the system would flash back to stock recovery if I've pushed the TWRP recovery image over the factory image?
I flashed twrp from fastboot and it's still there. Just waiting on root
Sent from my Nexus 4 using xda app-developers app
otariq said:
I flashed twrp from fastboot and it's still there. Just waiting on root
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Without root would there be any functionality within TWRP that I shouldn't touch? Or does recovery functionality have no dependency on root?
What is there you wanna do? I just replaced stock with twrp so I can just flash the su zip when its out because I don't always have access to a PC. Also, Franco released his initial 4.3 kernel which I'm thinking about flashing.
When rebooting from twrp it'll ask if you wanna flash the su.apk because you don't have root I chose no because it wouldn't do anything for us right now without the binaries
Sent from my Nexus 4 using xda app-developers app
Good point. As of right now I guess I don't have a huge need for it. I'll just leave everything as is until a proper SuperSU is released. At which point I'll install the latest TWRP and root.
Just a question, wasn't nexus root toolkit supposed to be able to revert to stock?
I did it in previous android versions.
now I am running slim rom with CWM and "reverting to stock 4.3" using NRT doesn't work, the process finishes but nothing is done.
skinniezinho said:
Just a question, wasn't nexus root toolkit supposed to be able to revert to stock?
I did it in previous android versions.
now I am running slim rom with CWM and "reverting to stock 4.3" using NRT doesn't work, the process finishes but nothing is done.
Click to expand...
Click to collapse
No idea. I use a Mac and flash back to stock via Fastboot. You should just learn to do that anyway so you have a better sense of exactly what is going on and if something fails you'll know exactly which step is failing in order to correct it. Relying on a toolkit is like never taking the training wheels off your bike.
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
Does anyone know where I can get a flashable OTA file that will keep root for the Wifi OG Nexus 7? I have seen it posted for the Nexus 4 and new Nexus 7, but cannot find it anywhere for Grouper.
VAVA Mk2 said:
Does anyone know where I can get a flashable OTA file that will keep root for the Wifi OG Nexus 7? I have seen it posted for the Nexus 4 and new Nexus 7, but cannot find it anywhere for Grouper.
Click to expand...
Click to collapse
There is a flashable ota at the link below. You may need to flash superuser 1.51 after to get root back.
http://forum.xda-developers.com/showthread.php?t=1745781
Sent from my GT-I9505 using xda app-developers app
gsmyth said:
There is a flashable ota at the link below. You may need to flash superuser 1.51 after to get root back.
http://forum.xda-developers.com/showthread.php?t=1745781
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
OK I tried that but I got a Status 7 error message and it aborted install. I have everything stock that I can think of. No custom kernel. No nothing. Any suggestions other than flashing back to stock completely via Wug's toolkit then doing the OTA through the tablet itself and then restoring everything with Titanium Backup?
VAVA Mk2 said:
OK I tried that but I got a Status 7 error message and it aborted install. I have everything stock that I can think of. No custom kernel. No nothing. Any suggestions other than flashing back to stock completely via Wug's toolkit then doing the OTA through the tablet itself and then restoring everything with Titanium Backup?
Click to expand...
Click to collapse
If you check that thread I linked to above, there a few people with the status 7 error and a few different fixes, worth a try before wiping anything, hope it helps.
Sent from my GT-I9505 using xda app-developers app
gsmyth said:
If you check that thread I linked to above, there a few people with the status 7 error and a few different fixes, worth a try before wiping anything, hope it helps.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Thanks I appreciate it!
VAVA Mk2 said:
OK I tried that but I got a Status 7 error message and it aborted install. I have everything stock that I can think of. No custom kernel. No nothing. Any suggestions other than flashing back to stock completely via Wug's toolkit then doing the OTA through the tablet itself and then restoring everything with Titanium Backup?
Click to expand...
Click to collapse
You don't need to flash the stock image and lose your data, but even if you are on stock 4.3 you still need two things: stock recovery (if you don't already have it installed) AND you need to unroot! Being rooted will throw the Status 7 error.
Here's what I did:
First flash the stock recovery for JWR66V in fastboot.
Then use the "Full unroot" option inside SuperSU.
Apply the JWR66Y update using ADB sideload.
Then reinstall TWRP and install UPDATE-SuperSU-v1.51.zip using TWRP.
After rebooting you may be surprised to see that the SuperSU app needs to be installed again (seems to be a quirk a lot of us are having). Just head over to Google play and after that all should be good.
Sent from my Nexus 7 using xda app-developers app
CatThief said:
You don't need to flash the stock image and lose your data, but even if you are on stock 4.3 you still need two things: stock recovery (if you don't already have it installed) AND you need to unroot! Being rooted will throw the Status 7 error.
Here's what I did:
First flash the stock recovery for JWR66V in fastboot.
Then use the "Full unroot" option inside SuperSU.
Apply the JWR66Y update using ADB sideload.
Then reinstall TWRP and install UPDATE-SuperSU-v1.51.zip using TWRP.
After rebooting you may be surprised to see that the SuperSU app needs to be installed again (seems to be a quirk a lot of us are having). Just head over to Google play and after that all should be good.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi, I'm looking forward to doing this step since I really want to get that OTA installed in my device. Mine is on stock ROM, rooted via wugfresh toolkit. My concern is, after doing this step, will I lose all data? Also could you please explain how to do the first step- "First flash the stock recovery for JWR66V in fastboot."? I'm still a bit new to all these things, so please bare with me.
Thanks!
http://forum.xda-developers.com/showthread.php?t=1745781&page=53
Check out this thread. I flashed the Grouper.zip file, which is the OTA modified by commenting out the validation check that results in the Status 7 error. I copied it to /sdcard along with the Supersu 1.51 zip. The ota flashed perfectly using TWRP recovery. After booting and going back into TWRP, I flashed the supersu1.51 and regained root. You do not need to unroot or flash stock recovery to get this update. No data loss. I'm stock rom & kernel, rooted with TWRP recovery.
choybel said:
Hi, I'm looking forward to doing this step since I really want to get that OTA installed in my device. Mine is on stock ROM, rooted via wugfresh toolkit. My concern is, after doing this step, will I lose all data? Also could you please explain how to do the first step- "First flash the stock recovery for JWR66V in fastboot."? I'm still a bit new to all these things, so please bare with me.
Thanks!
Click to expand...
Click to collapse
You won't lose data if you repeat the steps I took. However since you are asking how to flash a recovery in fastboot I would seriously be careful and do a bit of homework on how fastboot works. All the instructions you'll ever need can be found by searching xda. It really isn't as daunting as it sounds but you definitely need to understand how it works before trying it.
Or you could try the link that Groid posted if you aren't concerned about skipping the validation check. The process is definitely is simpler if you're "new to all these things".
I'm not opposed to using WugFresh's toolkit, he's a brilliant developer, but it's never a bad idea to learn about what happens in the background and see it with your own eyes.
Sent from my rooted GSM Galaxy Nexus
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.
hey all,
I'm a complete noob when it comes to rooting
I've been searching online on how to root a nexus 4 using a mac.. every single guide is different, some skip the unlocking bootloader part, some skip other parts, and most guides are just outdated.
I'm running on absolute stock, 4.4.2.
What's the best (and most current) guide out there? I'm interested in rooting my phone mainly so I can get LTE access.. do no care too much for non stock ROMS (not yet at least)
I think this is the easiest for noobs: http://forum.xda-developers.com/showthread.php?t=1999065 . It's a tool that will do all the work for you.
Sent from my Nexus 4 using Tapatalk
update:
I set up adb on my mac and unlocked bootloader, that was easy.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2018179
so now I'm confused about the whole Rom part.. which one do I download? There's a ROMs column, a stock recovery, and stock touch recovery. What are those?
You don't have to install another ROM. You can just download the recovery (CMW for mako touch or non touch) in the post. Also download the su zip tot get root acces.
Sent from my Nexus 4 using Tapatalk
Yuoko5 said:
You don't have to install another ROM. You can just download the recovery (CMW for mako touch or non touch) in the post. Also download the su zip tot get root acces.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ah, so the touch column is all the 'stock' roms. how do I know that it's the latest 4.4.2 stock rom? will be able to do OTA updates after I flash the mako touch?
If you're device is rooted I think you won't be able to install OTA updates from google anymore. But, you can flash these stock roms easily. I'm sure people make flashable zips of every new version of Android. About the columns: ROMs=you can download custom roms (you don't need that); Recovery and recovery touch is basically the same thing. The difference is one recovery can be controlled with the touchscreen and the over with the volume and power button. It's just what you like best.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
beegbear said:
ah, so the touch column is all the 'stock' roms. how do I know that it's the latest 4.4.2 stock rom? will be able to do OTA updates after I flash the mako touch?
Click to expand...
Click to collapse
Get it?
Sent from my Nexus 4 using Tapatalk
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
beegbear said:
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
Click to expand...
Click to collapse
Cwm(clockworkmod recovery) is a side load which helps u to flash different ROMs and zip files. It also helps u to wipe battery stats, partition sd card(not with case of n4)
Factory image is the stock ROM that Google provide that u r having in your nexus 4
Sent from my Nexus 4 using xda app-developers app
beegbear said:
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
Click to expand...
Click to collapse
And regarding your previous question of OTA updates, You'll have to flash the stock recovery if you're on CWM or TWRP (Team Win Recovery Project - Many people recommend this one, I use it myself) and you shouldn't have made any changes to the system files of your stock ROM.
You will receive the OTA if you have modified anything in system, you just won't be able to flash it. And you can also flash the OTA with TWRP instead of stock recovery. Root does not matter, although it will be lost after you update. Before updating, also make sure you're not using a custom kernel. Kernel: The "thing" that android runs on. It's the heart of the OS, you could say. No kernel, no boot.
Lt.Win said:
And regarding your previous question of OTA updates, You'll have to flash the stock recovery if you're on CWM or TWRP (Team Win Recovery Project - Many people recommend this one, I use it myself) and you shouldn't have made any changes to the system files of your stock ROM.
You will receive the OTA if you have modified anything in system, you just won't be able to flash it. And you can also flash the OTA with TWRP instead of stock recovery. Root does not matter, although it will be lost after you update. Before updating, also make sure you're not using a custom kernel. Kernel: The "thing" that android runs on. It's the heart of the OS, you could say. No kernel, no boot.
Click to expand...
Click to collapse
So let me make sure I'm following this..(sorry, I'm sure you saw such questions countless times before)
CWM (or TWRP) is a custom recovery instead of the stock 'recovery' option that's found in the bootloader. If I choose to go with either CWM or TWRP, how much of an issue is it to flash back to stock recovery? would it be done through ADB the same way the custom recovery was flashed in the first place?
As I understand.. the first thing I should do after unlocking the bootloader (already done) and flashing a custom recovery (not done yet) is to create a backup through the custom recovery. Does that back up the radios as well? If I decide to flash the all in one LTE zip and it doesn't work or what not.. will using that recovery flash back the old radios?
Now to the actual rooting..
so flashing super su is what actually does the root? How would I go about returning to complete stock if I ever need to? (stock recovery, remove root, lock bootloader)
When flashing a different ROM, how come I need to make a backup of my apps? what if I want to start completely fresh? Would I not be able to go to the playstore after flashing a custom rom and downloading everything I need? or there is not going to be a play store after flashing? (that's why GAPPS are needed?)
so I rooted and flashed the hybrid radio, works like charm!
I answered most of my own questions in the post above just by going through the process.
What happens if I decide to factory reset through settings? will CWM stay? will the root stay? will the lte fix stay?
Yes...yes...yes.....you really should take advantage of the countless guides people have written explaining all of your questions.
Sent from my Nexus 4 using XDA Premium 4 mobile app