Hello, If I erase my system image via adb will I loose root? If I won't loose root, will I lose the recovery image. The problem is that I can not reclaim about 30 in internal storage. I deleted all my apps and still Im missing 30. I don't know where it is.
Yes erasing system will loose androids access to root and to boot,
No it will not impact your recovery that is in the recovery partition not system, so if you have a custom recovery it will still have root, to rebuild your now missing os.
It also won't touch the spl bootloader, so if you have an engineering one you will still have fastboot (this is very low level access to the device but isn't anything to do with root in linux)
Fyi if you are talking about 30mb of data its on /data And will also not change by destroying /system.. also the data is the dalvik cache and uaerdata for the built in applications in addition to ones you install.
One important thing to note:
If you have an engineering bootloader, then having root DOESN'T MATTER, since it is trivial to get back with fastboot.
Related
Ok, I come from the Apple world where you have to restore the iPhone / iPad first to update to the latest iOS then re-jailbreak.
With the N7, if I wanted to upgrade to a newer version of Android (currently on 4.2.2, so whatever comes next), would I have to re-flash the N7 to stock 4.2.2 then re-unlock and re-root it?
What if I just want to do a factory reset to start over? Do I have to re-flash stock 4.2.2 then re-unlock and re-root in that case too?
Synomenon said:
Ok, I come from the Apple world where you have to restore the iPhone / iPad first to update to the latest iOS then re-jailbreak.
With the N7, if I wanted to upgrade to a newer version of Android (currently on 4.2.2, so whatever comes next), would I have to re-flash the N7 to stock 4.2.2 then re-unlock and re-root it?
What if I just want to do a factory reset to start over? Do I have to re-flash stock 4.2.2 then re-unlock and re-root in that case too?
Click to expand...
Click to collapse
To do an official ota yes. There are stock odexed/deodexed ROMs you can flash in the dev forums without having to go through that though.
Sent from my Paranoid 3.0 Nexus7 running M-Kernel mr1
Locking/unlocking of the boot loader is completely independent from other "rooting" activity. Under normal circumstances, it is only unlocked once and then left that way.
In Android, there are 5 principal partitions: recovery, boot, system, data, and cache. In pure stock devices, it is intended that recovery, boot, and the system partition are always used in a read-only fashion by the end user. All user changes, customizations, settings, and data are recorded into the data (sometimes also called "userdata") partition. (The cache partition is used for temporary/transient stuff)
So, the Android "factory reset" is not precisely what you are thinking of - it is a procedure which erases only the cache and data partitions. IT RESTORES NOTHING - IT ONLY DELETES.
So, if a device "rooter" comes along and alters the boot/recovery/system partition, those changes stay on the tablet/phone even when a "factory reset" procedure is performed. THOSE CHANGES CAN BREAK THE SUCCESSFUL INSTALL OF AN OTA BUNDLE, so, yes - it is generally cleaner to install a pure stock ROM for the purposes of performing an OTA upgrade... at which point you need to re-root and re-customize ( not including the boot loader unlock step).
One more thing, too: because the Nexus 7 has no physical SD card, it has an "emulated" SD card which is stored in the /data (userdata) partition. When the "stock recovery" performs a "factory reset", it erases EVERYTHING in /data - including this psuedo SD card! The newer versions of the CWM or TWRP custom recoveries define "factory reset" a little differently - they erase everything except what is stored in the /data/media/ folder - the location of the emulated SD card (usually /data/media/0). This is important to understand, as your backups will be stored in there.
HTH
PS There is no need for you to "hurry up and install an OTA" if you are using a well supported custom ROM - generally after a few weeks a ROM dev will rebase their ROM onto the new release, and you can simply "dirty flash" the replacement ROM over the top of the existing ROM. That will save you some effort if you just wait a little.
So I just unlocked and rooted my N7 last night.
Since it is unlocked and rooted, do I have to do anything different if I want or have to perform a factory reset (using the hardware buttons to go into recovery mode and use the "wipe data/factory reset" option)?
If I do this factory reset, it stays unlocked right? Does it stay rooted too?
Synomenon said:
If I do this factory reset, it stays unlocked right? Does it stay rooted too?
Click to expand...
Click to collapse
Yes and Yes.
PS. The most important skill set you can develop right now is making backups using the custom recovery. You should be 100% comfortable using the backup/restore menus of the custom recovery ... and almost as important knowing where they are stored so you can get copies of them off the tablet for safe keeping.
Thank You!
bftb0 said:
Locking/unlocking of the boot loader is completely independent from other "rooting" activity. Under normal circumstances, it is only unlocked once and then left that way.
In Android, there are 5 principal partitions: recovery, boot, system, data, and cache. In pure stock devices, it is intended that recovery, boot, and the system partition are always used in a read-only fashion by the end user. All user changes, customizations, settings, and data are recorded into the data (sometimes also called "userdata") partition. (The cache partition is used for temporary/transient stuff)
So, the Android "factory reset" is not precisely what you are thinking of - it is a procedure which erases only the cache and data partitions. IT RESTORES NOTHING - IT ONLY DELETES.
So, if a device "rooter" comes along and alters the boot/recovery/system partition, those changes stay on the tablet/phone even when a "factory reset" procedure is performed. THOSE CHANGES CAN BREAK THE SUCCESSFUL INSTALL OF AN OTA BUNDLE, so, yes - it is generally cleaner to install a pure stock ROM for the purposes of performing an OTA upgrade... at which point you need to re-root and re-customize ( not including the boot loader unlock step).
One more thing, too: because the Nexus 7 has no physical SD card, it has an "emulated" SD card which is stored in the /data (userdata) partition. When the "stock recovery" performs a "factory reset", it erases EVERYTHING in /data - including this psuedo SD card! The newer versions of the CWM or TWRP custom recoveries define "factory reset" a little differently - they erase everything except what is stored in the /data/media/ folder - the location of the emulated SD card (usually /data/media/0). This is important to understand, as your backups will be stored in there.
HTH
PS There is no need for you to "hurry up and install an OTA" if you are using a well supported custom ROM - generally after a few weeks a ROM dev will rebase their ROM onto the new release, and you can simply "dirty flash" the replacement ROM over the top of the existing ROM. That will save you some effort if you just wait a little.
Click to expand...
Click to collapse
Thank you bftb0:good::good:
I was playing around with kernels in fastboot the other day, and somehow my SD storage partition got all messed up. It's supposed to be 16GB, but it's only showing 5.8GB.
I ran the fastboot erase commands for boot, userdata, system, and cache, then flashed the jdq39 factory image. When I rebooted, the partition was only 5.8GB, and there were no files left on it.
I've tried formatting it in cwm recovery, but it just stays the same size. It's not showing any extra storage partition, but it almost feels like that's what happened somehow, and I just can't access the other partition. I'm also thinking that maybe the other partition I can't access possibly still contains my missing files, which I would love to recover, if possible, since I do have a nandroid on there I'd love to be able to restore!
I'm running UBUNTU and do not have windows, so if I need to do any terminal work I'm game...but I'm also a n00b, so please explain well
hp420 said:
I was playing around with kernels in fastboot the other day, and somehow my SD storage partition got all messed up. It's supposed to be 16GB, but it's only showing 5.8GB.
I ran the fastboot erase commands for boot, userdata, system, and cache, then flashed the jdq39 factory image. When I rebooted, the partition was only 5.8GB, and there were no files left on it.
I've tried formatting it in cwm recovery, but it just stays the same size. It's not showing any extra storage partition, but it almost feels like that's what happened somehow, and I just can't access the other partition. I'm also thinking that maybe the other partition I can't access possibly still contains my missing files, which I would love to recover, if possible, since I do have a nandroid on there I'd love to be able to restore!
I'm running UBUNTU and do not have windows, so if I need to do any terminal work I'm game...but I'm also a n00b, so please explain well
Click to expand...
Click to collapse
you might have to flash the stock system img via fastboot to fix it.
I've done a FULL flash...bootloader, radio, boot, system, userdata
http://forum.xda-developers.com/showthread.php?t=2033692
You'll either follow the steps in the OP or flash stock recovery and factory reset and clear cache.
Sent from my Nexus 4 using xda premium
OMG thank you!! This is exactly what I was looking for I knew there had to be one!
Hi all,
I have a nexus 7 running Android 4.1.2 stock w/ root. Some months ago, I disabled the OTA update notification - but I can't seem to remember how!
I want to now re-enable OTA updates so that I can update to the latest android version, and not lose my installed apps.
I've searched the device for FOTAKill.apk inside /system/app, and its not found
I've also searched for frozen / hidden apps using Titanium Backup Pro... nothing
When I enter Settings -> About Tablet -> System Updates... it says I'm up to date... but I'm not, considering I'm running 4.1.2.
Any help or pointers in re-enabling OTA is appreciated!!
- make a full nandroid backup.
- using fastboot, flash the system.img file from the 4.2.2 factory image to the system partition.
- using your custom recovery, reflash a SuperSU root kit bundle.
- using the custom recovery, wipe cache and dalvik-cache.
If you don't like the result, restore the nandroid backup and proceed in a different fashion. It will probably break things like stickmount and any other changes that you caused in /system.
Note the above method is for use by lazy and sloppy users. A better approach is to make TiBu backups of only your market apps, bite the bullet, and start from scratch with a flash & (new) configuration of a pure stock ROM. In any case, every conceivable procedure should start with making a full nandroid backup and getting it copied to a safe place off the tablet.
I will also say that unless odd problems crop up, the portions of the factory install procedure (using fastboot) that deal with erasure or flashing of the userdata partition should be skipped, as these steps completely wipe your /data storage - including your /sdcard area in /data/media/0 and any CWM/TWRP nandroid backups!
It's not really clear why these steps would be needed unless the /data ext4 filesystem in the userdata partition got corrupted somehow. A more sly approach would be to use the custom recovery's "factory reset" procedure to clean up /data - either before or after flashing the factory ROM - and completely skip anything that touches the userdata partition in the factory install instructions.
good luck
hi guys,
please i have some questions i really need there answers:
1- (rooted phone) if i do a factory data reset will the root gone and the TWRP also ?
2- (rooted phone) is there a way to install an update if i got it ( like update security patches "monthly" ) on rooted phone without wipe data or loosing the root or TWRP?
3- (rooted phone) if i reinstall the factory image full,the root and TWRP will have gone or not ?
thanks a lot !
1. If you use systemless root a factory reset will remove it. If you use a root method that modifies the system partition a factory reset won't remove root. Factory resets will not remove TWRP.
2. Installing monthly security updates and keeping TWRP, root, and data can be done by manually installing the update using fastboot and doing the following:
-Systemless root method: flash everything EXCEPT the recovery, boot, and userdata images.
-System based root method: install everything EXCEPT the recovery and userdata images. You will have to reflash Superuser/SuperSU (whichever you prefer) in TWRP since flashing the system image will remove root. There's no way around this.
3. If you use fastboot to install everything included in a factory image you will lose root, data, and TWRP.
Face_Plant said:
1. If you use systemless root a factory reset will remove it. If you use a root method that modifies the system partition a factory reset won't remove root. Factory resets will not remove TWRP.
2. Installing monthly security updates and keeping TWRP, root, and data can be done by manually installing the update using fastboot and doing the following:
-Systemless root method: flash everything EXCEPT the recovery, boot, and userdata images.
-System based root method: install everything EXCEPT the recovery and userdata images. You will have to reflash Superuser/SuperSU (whichever you prefer) in TWRP since flashing the system image will remove root. There's no way around this.
3. If you use fastboot to install everything included in a factory image you will lose root, data, and TWRP.
Click to expand...
Click to collapse
Could you explain me what are the difference between systemless root method and system based root method, in order to get know what is it the method that I used
Chouiyekh said:
Could you explain me what are the difference between systemless root method and system based root method, in order to get know what is it the method that I used
Click to expand...
Click to collapse
If you are running Marshmallow or Nouget and used a version of SuperSU that is a year or less old it does system less root by default.
You can flash OTA updates on a rooted device with FlashFire without using a computer.
You can also flash an OTA image in TWRP and then simply flash root after, before you boot the phone. If the phone boots without root, out will wipe TWRP and leave you with stock recovery.
But honestly, from the questions being asked, you might not want to try this stuff until you understand it better. Losing root and TWRP is not a big deal. You can flash them again in about 1min and 30 seconds, so it's not worth worrying about.
Sent from my Nexus 6P using Tapatalk
Why would factory reset remove systemless root? I expect factory reset to only reset what you're supposed to have changed since factory image. That is /data.
Systemless must be in /data if it's not in /system, right? I don't really know much about systemless, because I don't use Android pay, Snapchat or play children's games haha.
But my guess is that if it's not touching system, then it must be in data, so wiping data would remove it. But I'm just guessing.
Sent from my Nexus 6P using Tapatalk
HikingMoose said:
You can also flash an OTA image in TWRP and then simply flash root after, before you boot the phone. If the phone boots without root, out will wipe TWRP and leave you with stock recovery.
But honestly, from the questions being asked, you might not want to try this stuff until you understand it better. Losing root and TWRP is not a big deal. You can flash them again in about 1min and 30 seconds, so it's not worth worrying about.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
thank you, i got it easily because i'm not a beginner i have some experience
HikingMoose said:
Systemless must be in /data if it's not in /system, right?
But my guess is that if it's not touching system, then it must be in data, so wiping data would remove it. But I'm just guessing.
Click to expand...
Click to collapse
You guessed right. Never thought of that, thought it was actually all done from boot partition.
Quoting Chainfire:
As the binaries should still be updatable, and we don't know the space we have available in the boot image itself, we're mounting a (writable) ext4 image with /su as mount point from /data, and modifying PATH accordingly. Interestingly, for reasons yet unknown to me, if the image is mounted r/o by init, later remounting it r/w causes a bunch of issues. So we're keeping it r/w (for root) for now.
So I've seen with installing custom ROMs that there are steps that basically say, "Do not wipe system" in TWRP. I have noticed in doing things the dumb way that I can wipe every partition but the only way it becomes unrecoverable is if system is wiped, this is even if I install a custom ROM in its place. Can someone help me understand what has changed with A/B partition or OnePlus security settings where OOS system partition must be intact to allow one to run a custom ROM?
The reason I ask is that unless it is a byte for byte overwrite then we leave OOS files on parts of the custom ROM storage partition and if it is bit for bit write why would erasing the partition matter?
What seems more important for custom ROM is to not wipe data before rebooting in TWRP to flash magisk. So a clean flash is now flashing the ROM, flashing TWRP then reboot in TWRP and then only wiping data and art. Then flashing magisk. This is important to keep decryption working. That means not using factory reset feature either, always wiping with manually selected partitions.
Anyway wiping system is useless as the flashing script wipes it anyway.