Database Users

New Nexus 7 User needing Unlocking/Root advice

Hey XDA
Iv had my Nexus 7 for a day now and am dying to root and mabe install CM10
i currently have a Samsung Galaxy S3 with CM10 on it...thot its extremly buggy sadly... anyways i have been looking up on how to root the nexus 7 but i need to know if i can instead of using toolkit can i instead just use odin to flash stock rom and cwm and so on instead of having to unlock the device?
i am used to using odin for flashing and cwm but here the nexus is close to the same with htc one x in the way it has that fastboot thing and from what iv heard the nexus 7 requires unlock before it can be rooted, also is the tookit the best way to unlock and root the device?
also does unlocking break the warrenty and if i ever decide to return to stock unroot how do i flash stock rom back onto the device? am not sure where i would find the stock roms for it and also can odin be used to flash it...:S
i hate sounding like a noob lol

ok iv used the toolkit 2.0 and its worked great so far...im stuck at not being able to boot into cwm recovery
it installed fine thru the toolkit but whenever i try to hold up and power i cant get it to boot into cwm recovery...
i tryed to reinstall again but still cant get it to boot into cwm am i doing something wrong?

Doing the following won't cause you to loose warranty:
- Unlocking the bootloader
- Rooting
- Flashing custom ROM's and Kernels (however, if you flash a custom kernel that causes your device to explode... I'm somewhat certain this won't be covered)
However, if you are doing anything like that, and have to send the device in for warranty, you "should" factory restore it. Google provides Factory Images for the Nexus 7, which can be restored to your device with semi-ease.
I use this guide to factory restore: http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html Some filenames might need changed though since I think that guide is based off an older factory image (instructions are the same though).
There is a good chance a toolkit also has an easy method for factory restoring, but I don't recommend this at all.

Stop using toolkits.
Sent from my Nexus 7 using Xparent White Tapatalk 2

ÜBER™ said:
Stop using toolkits.
Click to expand...
Click to collapse
Amen, +1. http://forum.xda-developers.com/showthread.php?t=1830108

encryptioncsta said:
ok iv used the toolkit 2.0 and its worked great so far...im stuck at not being able to boot into cwm recovery
it installed fine thru the toolkit but whenever i try to hold up and power i cant get it to boot into cwm recovery...
i tryed to reinstall again but still cant get it to boot into cwm am i doing something wrong?
Click to expand...
Click to collapse
I've never used a toolkit before (until this issue had me stuck). I'm unable to get the Nexus 7 to book into recovery (CWM) after flashing it via fastboot. After giving up, I rooted it using the toolkit.. scariest thing I've ever done.. it did work.. but I'd like to get to the bottom of why a number of people like me seem to be having issues flashing and booting CWM on the Nexus 7.

Did you rename the original system/recovery to .bak first?

Travisdroidx2 said:
Did you rename the original system/recovery to .bak first?
Click to expand...
Click to collapse
No, I flashed it as I normally do.. using the .img file. In this case, CWM.. recovery-clockwork-6.0.1.0-grouper.img
Why would renaming it to .bak be needed?

xyzulu said:
No, I flashed it as I normally do.. using the .img file. In this case, CWM.. recovery-clockwork-6.0.1.0-grouper.img
Why would renaming it to .bak be needed?
Click to expand...
Click to collapse
Its not actually.
Sent from my Nexus 7 using Xparent White Tapatalk 2

I had to rename the stock recovery under system to .bak before I could get twrp to work. Or else when I went into recovery it would get stuck on the android.
But I see you are using fast boot it should write over it.

Travisdroidx2 said:
I had to rename the stock recovery under system to .bak before I could get twrp to work. Or else when I went into recovery it would get stuck on the android.
But I see you are using fast boot it should write over it.
Click to expand...
Click to collapse
I didn't have to. Flashed twrp and forgot to put a ROM on it and went back into recovery and it was twrp still.
Sent from my Nexus 7 using Xparent White Tapatalk 2

I should of just flashed the image file and flashed it myself but I was in a hurry and used goo im and it bit me in the ass. Lesson learned.

Any Guide available For Flashing 4.2.2 on Custom kernel without Loosing Data

As the Topic Suggest is there any guide someone made for noobs like me
who wanna upgrade there NEXUS 7 to 4.2.2 having Custom kernel without loosing data ?

You don't need a guide in your case.
Click here:
http://forum.xda-developers.com/showthread.php?t=2148337
There are two STOCK 4.2.2 roms in this thread. One is DEODEXED and the other is ODEXED.
I recommend downloading the DEODEXED STOCK 4.2.2 rom.
Here's the link to the DEODEXED STOCK ROM:
http://goo.im/devs/teshxx/Nexus7Wifi/Grouper-JDQ39_4.2.2-Deodex_Rooted-02-14-13-teshxx.zip
Download it, put it in your N7 and flash it via recovery. You won't lose any data and you don't have to wipe anything. Just flash and go!

scream4cheese said:
You don't need a guide in your case.
Click here:
http://forum.xda-developers.com/showthread.php?t=2148337
There are two STOCK 4.2.2 roms in this thread. One is DEODEXED and the other is ODEXED.
I recommend downloading the DEODEXED STOCK 4.2.2 rom.
Here's the link to the DEODEXED STOCK ROM:
http://goo.im/devs/teshxx/Nexus7Wifi/Grouper-JDQ39_4.2.2-Deodex_Rooted-02-14-13-teshxx.zip
Download it, put it in your N7 and flash it via recovery. You won't lose any data and you won't have to wipe anything. Just flash and go!
Click to expand...
Click to collapse
I won't get error 7 ?
For installing this ?
And its not ota update how come it wont wipe data?
Sent from my Nexus 7 using Tapatalk HD

1) make a full nandroid (cwm/twrp) backup
2) flash a 4.2.2 stock-derived ROM on top of existing ROM - no wipe
2.5) flash a minimal root kit (SuperSU or Superuser) if not in ROM in step 2 - no wipe
3) flash the same kernel you used previously - no wipe
4) profit!
No workie? Restore backup from step # 1 and try something else.

pleasant said:
I won't get error 7 ?
For installing this ?
And its not ota update how come it wont wipe data?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2

scream4cheese said:
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
For safety I made a full online nandroid backup as above suggested now the issue is I am trying to copy the backup on PC
But when I plug nexus 7 on PC
In clockworkmod folder the backup folder doesn't show up but in
File manager at tablet shows it :/
Sent from my Nexus 7 using Tapatalk HD

pleasant said:
For safety I made a full online nandroid backup as above suggested now the issue is I am trying to copy the backup on PC
But when I plug nexus 7 on PC
In clockworkmod folder the backup folder doesn't show up but in
File manager at tablet shows it :/
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
There's no need to do that. But in spite of it, I can tell you that you can just create the nandroid backup and leave it in your device. Don't pull it out. Just flash the download in my previous post and if anything goes wrong. Enter recovery mode and restore your system. Even if you did pull the nandriod backup file from the N7 and the device fails to boot up, you cant just put the file back in to restore it that way. It won't mount so you can access the internal storage system.
P.S i don't know how to make the backup show up but i think there are a few thread here that some people have found a solution to it.

scream4cheese said:
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
DA FAAK this thing worked :good:
i am finally upgraded to 4.2.2
tell me why this one didnt gave "7" error ?
Where this Guide was Hiding i have been looking for easiest method and this is what it is

pleasant said:
For safety I made a full online nandroid backup as above suggested now the issue is I am trying to copy the backup on PC
But when I plug nexus 7 on PC
In clockworkmod folder the backup folder doesn't show up but in
File manager at tablet shows it :/
Click to expand...
Click to collapse
I have had TWRP behave the same way - sometimes it will put backups in
/data/media/TWRP/...
and sometimes in
/data/media/0/TWRP/...
It is a bit of a mystery what causes this to happen. Strangely, when there is a folder in the first location, TWRP (2.4.1.0) will not find the second one. But, if I manually move the files from the first location (/data/media/TWRP) to the second location (/data/media/0/TWRP) using a file manager, then TWRP will find the backups no problem.
well, the "sdcard" mount point ( == /data/media/0/ ) is the thing that shows up on the PC via MTP mode, so I would just move the files to the second location. I'm not sure if CWM behaves the same way, but you will certainly be able to copy them from the N7 to the PC at that point.
good luck.

pleasant said:
DA FAAK this thing worked :good:
i am finally upgraded to 4.2.2
tell me why this one didnt gave "7" error ?
Where this Guide was Hiding i have been looking for easiest method and this is what it is
Click to expand...
Click to collapse
LOL. I told you it works.
There's one thing that you're missing from that update. And that is the bootloader version, the bootloader version that you're currently using is 4.13. The newest version is 4.18. You don't have to update it if you don't want to.
I'll include this link for you to flash the latest bootloader via command prompt.
http://forum.xda-developers.com/showthread.php?t=2150251
I hope you know how to use adb/fastboot.

scream4cheese said:
LOL. I told you it works.
There's one thing that you're missing from that update. And that is the bootloader version, the bootloader version that you're currently using is 4.13. The newest version is 4.18. You don't have to update it if you don't want to.
I'll include this link for you to flash the latest bootloader via command prompt.
http://forum.xda-developers.com/showthread.php?t=2150251
I hope you know how to use adb/fastboot.
Click to expand...
Click to collapse
first tell me does updating bootloader wipes data ?
and secondly what does bootloader do and advantage of updating bootloader ?
u mean to say sideload command ?

pleasant said:
first tell me does updating bootloader wipes data ?
and secondly what does bootloader do and advantage of updating bootloader ?
u mean to say sideload command ?
Click to expand...
Click to collapse
Updating bootloader does not wipe anything. It simply replaces and updates the one you already have on.
Definition of a bootloader:
http://m.androidcentral.com/what-is-android-bootloader
Sideload? I think so.

boot(basically kernel) and system are usually what people mean 'custom ROM'. So if you just manually flash these two things(and usually need to be done together), none of your 'data' would be lost.
So just find these two images (usually .img) in whatever custom ROM you want and flash it.
This is the unix convention for a long long while and android is just linux

scream4cheese said:
Updating bootloader does not wipe anything. It simply replaces and updates the one you already have on.
Definition of a bootloader:
http://m.androidcentral.com/what-is-android-bootloader
Sideload? I think so.
Click to expand...
Click to collapse
So if there is a flashable zip available that would be great
Sent from my Nexus 7 using Tapatalk HD

you don't really need to flash bootloader

chimpanzeexda said:
you don't really need to flash bootloader
Click to expand...
Click to collapse
Yeah, I told him that.
Sent from my Nexus 7 using Tapatalk HD

scream4cheese said:
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Hi bro can you provide me the similar flashable zip for android 4.3 for nexus 7 wifi
Sent from my Nexus 7 using Tapatalk HD

Recovery won't flash

I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4

Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.

SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4

T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps

Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4

T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.

Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4

T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.

OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.

Back to Factory with no computer access.

I everyone!
I just tried to connect my Nexus 4 to my windows 8.1 laptop and the phone is not recognised by the PC. It gives me Code 43 error, I tried everything, form fresh driver install to cable change. I also tried on another W7 laptop and nothing pops up there. The phone charges but in Device Manager it is not listed under Google ADB devices but appears with an exclamation mark under USB controllers saying Device Descriptor Request Failed. I fear it is an hardware problem and RMA is the only option left. However, my phone is Rooted, Stock but with modified build.prop, with TW touch recovery and unlocked. Since I have no access to ADB I cannot use the Android SDK tools or anything to flash the factory img. Is there any way in which I could flash back the sock image and lock the bootloader via recovery only?
Thanks everyone :crying::crying:

you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.

Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was what I was thinking, however, the main issue would be locking the bootloader again
simms22 said:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Click to expand...
Click to collapse
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time

c0sk said:
This was what I was thinking, however, the main issue would be locking the bootloader again
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
Click to expand...
Click to collapse
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.

mrhiab said:
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
Click to expand...
Click to collapse
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?

c0sk said:
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
Click to expand...
Click to collapse
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.

efrant said:
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
Click to expand...
Click to collapse
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??

c0sk said:
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
Click to expand...
Click to collapse
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2

efrant said:
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset

c0sk said:
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
Click to expand...
Click to collapse
The way you removed SuperSU must have not worked properly. (I've never tried doing it from the SuperSU settings.) In any case, there's nothing more you can do now, so might as well send it in for RMA.

noob here, lost at rooting

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