Database Users

If I root

Right just a quick question if I root my nexus 7 just to use stick mount and a OTG cable and add removal. Will I still get the OTA updates from the big G.
I'm a compulsive ROM changer and I have never owed a full Nexus device and would just like to keep it pure Nexus so to speak but with Root.
Sent from Galaxy SIII using Tapatalk

Yes.
Yes, you'll still get OTA updates, but you'll lose root (I know 'cause my old Galaxy tab lost it when it got ICS), so if you want to keep root, use the Root Keeper app in the Play Store. I thing there are ways or apps that do this too, but I don't know.

You will get them but they wont update your nexus 7 because of a custom recovery
Sent from my Nexus 7 using Tapatalk 2

E_Goldstein said:
You will get them but they wont update your nexus 7 because of a custom recovery
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Ahhh that's what I thought
Sent from Galaxy SIII using Tapatalk

Ignore last poster.
You can still get your ota if you keep the stock recovery
You can still use a custom recovery for gaining root by doing fastboot boot recovery.img instead of fastboot flash recovery recovery.img
Doing it this way will give you a single boot into custom recovery while Leaving the actual recovery on your tab stock
Sent from my Nexus 7

E_Goldstein said:
You will get them but they wont update your nexus 7 because of a custom recovery
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
That's not true. You can root and still have stock recovery. In fact you'll have stock recovery unless you flash one manually. edit: or unless your root tool flashes the recovery.
And to the OP, yes, you sure can have root, and still have updates [but apparently not upgrades], I recommend that over unrooted stock, but I would definitely recommend a custom rom like Paranoid Android [CM10 based]. It lets you choose the layout [tablet and phablet] of any app.

Yes, you will keep root if here is an upgrade. You might not keep it going from 4.1 to 4.2 on the OTA because like then other guy said, he lost root after a big update. If you go from 4.1 to 4.1.1 you should be fine.
Sent from my SGH-T989 using xda premium

Then if this is true, that they will flash why for the past 2 weeks when people have asked the same question has everyone else said the same as i did??
You cant get a straight answer on this site now a days i wish it go back to 5 years ago. It was nice t be on here then
Sent from my Nexus 7 using Tapatalk 2

E_Goldstein said:
Then if this is true, that they will flash why for the past 2 weeks when people have asked the same question has everyone else said the same as i did??
You cant get a straight answer on this site now a days i wish it go back to 5 years ago. It was nice t be on here then
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
OK let me give you the full breakdown which should hopefully make things easier to understand for everyone
[RECOVERIES AND OTA UPDATES]
in order to flash a manufacturer OTA update you must have the stock recovery on your devices Recovery Partition
you can still use a custom recovery via fastboot boot recovery.img as this doesnt touch your physical recovery partition
by doing fastboot boot clockworkrecovery.img you can then install your su binaries to get root
[OTA UPDATES AND KEEPING ROOT]
there are 2 different types of OTA updates
Incremental and Full System Updates
[INCREMENTAL UPDATES]
an incremental update will just update files on your system partition, as a stock rom doesnt have SU binaries, a incremental update will never
touch them and thus root will not be affected
[Full System Updates]
a full system update will erase and flash a completely new system partition, as such all data on the system partition is replaced including SU binaries so with this type of update Root will be lost
even after a full system update it is easy enough to just fastboot boot clockworkrecovery.img and reflash the su binaries again afterwards so nothing is ever truly lost
hope this is slightly educational for some of you

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

[Q] OTA update to 4.2.2 problems

My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?

rsipson said:
My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
Click to expand...
Click to collapse
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip

You have to restore everything except relocking bootloader ... To be able to update ...when u finish ..just re-root
Sent from my Nexus 7 using xda premium

Same thing happened to me, I had to unroot and then root again after update.
Sent from my HTC Desire S using xda app-developers app

heat361 said:
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
Click to expand...
Click to collapse
Thanks for your post. I tried this using Clockwork and got a very long error message. I will quote part of it.
assert failed_apply_patch_check("/system/bin/debuggerd", "a2323a0c8 and a lot more
This is followed by error in file
I saw something about busybox changing some system files.
Any ideas??

How do I unroot without whipping all data?
Sent from my Nexus 7 using xda app-developers app

Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.

bftb0 said:
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
Click to expand...
Click to collapse
Sorry for being a numpty... can someone put the above into a mini step by step guide for me.. I'm stuggling with the terminology.
I rooted my Nexus and have since forgotten anything techie regarding it. I have StickMount and cannot update to 4.2.2..
How do i flash boot.img and system.img via fastboot, where do i get these files from, what versions etc do i need? And over flash SuperSU root kit?
What is OTA?
Basically, I think i need a newbie guide. I am techie enough to achieve most things normally.. i just don't know the android system at all, and what i did know to be able to root it i have completely forgotten!
Any guidance would be very much appreciated. Cheers.

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.

Nexus 7 2012 stuck in safe mode

When I restart Nexus 7 it always boot up to safe mode. Tablet first shows bootloader menu and when I choose to start, it boot in to safe mode. It looks like volume down button is always pressed on but it don't work - does nothing in bootloader menu, and in safe mode.
I don't use it for some days. I don't remember the tablet being flooded or hit. It just appears. First I thought that it was caused by some bug in LineageOS. I made factory reset, and when it does nothing I set u Android 5.1 again but that also didn't work.
Do you have any idea why this is happening?

You mean you are always booting into recovery when starting up the device? This may happen if there is no valid boot.img / system.img installed. How did you install the current system on your device? Do you have an unlocked bootloader? Do you have the latest bootloader (4.23) installed on your device?

AndDiSa said:
You mean you are always booting into recovery when starting up the device? This may happen if there is no valid boot.img / system.img installed. How did you install the current system on your device? Do you have an unlocked bootloader? Do you have the latest bootloader (4.23) installed on your device?
Click to expand...
Click to collapse
Last thing I did is option Flash Stock + Unroot in Nexus Root Toolkit.
Yes I have bootloader 4.23.

Sorry, but I don't know what the toolkit is doing and whether everything went as expected .. that's the disadvantage of using toolkits.
Best would be to learn how to install and to use fastboot and after that you can decide either to flash stock factory image again or to upgrade to one of the custom ROMs available for the Nexus 7.
Sent from my Nexus 7 using XDA Labs

AndDiSa said:
Sorry, but I don't know what the toolkit is doing and whether everything went as expected .. that's the disadvantage of using toolkits.
Best would be to learn how to install and to use fastboot and after that you can decide either to flash stock factory image again or to upgrade to one of the custom ROMs available for the Nexus 7.
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
I think you don't understand me. Nexus Root Toolkit have nothing to do with this. It works 3 years with my Nexus 4 and 1 year with Nexus 7. This problem appeared long after installation of LineageOS.
Ok, I installed Android 5.0 manually and I still have this problem.

Did you notice any error messages while flashing the stock image? Did you do a factory reset after returning to stock?
I am still thinking that your bootloader is closed and you are not really flashing / changing the ROM, but flashing fails and you are remaining in the same state as before. Just as an idea ...
Sent from my Nexus 7 using XDA Labs

I would do one step at a time assuming fastboot and adb work. Search for adb minimal. Download stock zip to same directory. Run fastboot oem unlock. Unzip stock zip and try running flash-all.bat it flashes compatible bootloader and stock zip. If that doesn't work img files are inside stock zip and can be flashed separately.
Sent from my Nexus 6 using Tapatalk

Sorry for leaving you like that.
I took the risk and ordered flex cables with volume buttons. Now the tablet works fine. I'm sorry for the trouble.