Updating system after root - Nexus 6P Q&A, Help & Troubleshooting

Can I just not wipe data and flash system to update after root? Like when new otas come through.
Also how do you know when bootloader changes to know if I'll need to flash that also... Or radio.

Yes. You can flash all of those with fastboot (system, vendor, bootloader, boot, radio, recovery) without wiping data.

bongostl said:
Yes. You can flash all of those with fastboot (system, vendor, bootloader, boot, radio, recovery) without wiping data.
Click to expand...
Click to collapse
Just have to re-root after right? And add back any system apps if I had any?
Thanks

Related

if i factory reset my phone, will it remove the root

will the root be gone if i factory reset my mytouch 4g?
Yes. Everything Will be wipe, superuser too.
Wrong. Actually, no. Not at all.
Factory reset wipes the /data partition, which holds user data.
Superuser resides on /system partition, which isn't wiped, and the fresh system after wipe will retain root access. Superuser app might be installed on /data, but the actual SU file will be on /system.
To remove root, you need to unroot - or flash non-rooted stock ROM.
Right, "factory" reset is a bit of a misnomer on Android.
There is no backup of the factory firmware if you have modified your system partition.
But if you flash a full RUU or PD15IMG.zip of the stock ROM, then yes you will lose root. However if you still have Radio S-OFF, you will still be able to flash unsigned images through the bootloader.
syedquadri said:
will the root be gone if i factory reset my mytouch 4g?
Click to expand...
Click to collapse
What ROM do you have? This all depends on the current ROM you have. If you did not update your ROM, then you will lose root. If you only updated your ROM and did NOT update your recovery, you could ruin your device potentially by selecting that option from within the phone or the stock recovery.
However, if you have a custom (probably rooted already) ROM and you have a recovery like clockworkmod recovery installed, then go ahead and wipe away. You can also clear just your cache, dalvik and many other stuff, the menu has a lot of options.

Blisspop: updating without wiping data

Hi,
I've recently done a succesful flash of Blisspop after a full wipe.
Now I want to update, but I don't want to do a full wipe. Simply installing the zip on-top gives a permanent booting screen. Can you update without starting from scratch?
Did you wipe cache & dalvik after flashing updated zip?
I did not. Is that the only required extra step? And will I lose data if I do so?
Kalenden said:
I did not. Is that the only required extra step? And will I lose data if I do so?
Click to expand...
Click to collapse
No, you only lose data when you wipe the data partition
In recovery, you'll see different named partitions, cache, dalvik cache, system, data, etc etc
If you wipe System, you wipe the ROM
If you wipe Data, you wipe your user data
Caches are just temp partitions, safe to wipe any time, only side effect is a longer first boot as Android needs to re-cache everything
But yes, you do need to wipe the caches when updating to a newer version of the same ROM/Droid version, and no you won't lose your data
Here's how I do it:
Wipe System
Wipe Caches
Flash new ROM
Flash new Gapps
Flash SuperSU if needed
Wipe Caches again
Reboot
Result = New ROM with no loss of data
That's a clean flash, a dirty flash is how you did it without wiping System
If you are moving to a newer version of android, or a different ROM, wiping data becomes more necessary, especially if the move is to an older version of droid
Thanks. I'll try it out.

How to (re) encrypt?

I had some complex issues flashing some roms and ended up having to format userdata. Now I am unencrypted and I have not been able to get the stock rom (from the official OTA zip) to boot. I was able to get all 3 of the custom OOS roms in the development section to boot, however when i go into settings and start encryption the green android logo flashes on the screen and the device does a hot reboot without starting encryption. I have tried countless things to boot the stock rom and/or get encryption to work including flashing the stock recovery on a custom rom, and the stock recovery asks for a pattern and mine doesn't work. I am totally out of ideas so if anyone has any please help.
solved: i previously did fastboot format userdata and it didn't work. I just did fastboot format userdata, system, and cache and the full ota zip installed, the security settings say it's encrypted, and i was able to decrypt with the stock recovery. Time to flash twrp and break more stuff!
Encryption
I believe the phone encrypts when you put a screen lock on.
I put a pin on mine booted in to recovery and it was encrypted, rebooted phone, removed pin, rebooted recovery everything back to normal.
hibby50 said:
solved: i previously did fastboot format userdata and it didn't work. I just did fastboot format userdata, system, and cache and the full ota zip installed, the security settings say it's encrypted, and i was able to decrypt with the stock recovery. Time to flash twrp and break more stuff!
Click to expand...
Click to collapse
Flashing stock boot.img in bootloader mode should encrypt the phone too.
gee2012 said:
Flashing stock boot.img in bootloader mode should encrypt the phone too.
Click to expand...
Click to collapse
Where or how can one extract/get the stock boot.img?
going to twrp wipe Then format data and typing yes will re-encrypt the device
Watch this
hibby50 said:
solved: i previously did fastboot format userdata and it didn't work. I just did fastboot format userdata, system, and cache and the full ota zip installed, the security settings say it's encrypted, and i was able to decrypt with the stock recovery. Time to flash twrp and break more stuff!
Click to expand...
Click to collapse
Thanks for sharing your solution. I found myself in this precarious position today. Solved with fastboot format... Thanks!

Random names TWRP

Hi, I'm from Nougat 4.5.14 and these are the steps I made:
1. Flash codeworx then reboot to twrp
2. Wipe cache and dalvik
3. Install OS 5.0.2
4. Install magisk
5. Wipe cache dalvik
6. Reboot to system
However after rebooting to system it started bootlooping so I decided to reflash OS and wipe data as recommended. So I power off the phone then hold volume down + power to boot to recovery. However when I boot to recovery, file folders started to become random names like its encrypted. Luckily I backed up my internal storage and data so I'm okay to flash everything but can someone help me how to fix the twrp random file names and the steps for reflashing the OS?
EDIT: I rebooted to recovery, wiped dalvik, cache, and data. flashed OS 5.0.2, wipe dalvik cache, flashed magisk, wipe dalvik, reboot to system and it does not proceed to circling dots. So what I did is just, wipe dalvik, cache, data, flashed OS, wipe again dalvik cache, boot to system and it proceeds to circling dots however it takes so long that I can consider this as bootloop. I'm very tempted to wipe everything (data, system, internal storage, cache, dalvik) then just flash again the OS but I don't know if it would work so I hope someone could give me some steps how to fix this
Edit 2: This is solved now: What I did is just after trying the flash OS with no magisk, I booted to system. However, i just dont boot at all so I decided to boot to recovery again, but this time the recovery is the stock one. I wipe everything I could including cache, system reset, and data (music pics etc) and it booted to the system in no time but everythings lost.
You have to format data... Not just wipe it. From TWRP go to format data, write yes, and let it format everything. Then transfer over to the phone all the fil a you need (ROM, kernel, no verity zip) and flash them as per the instructions of your rom thread. You should be fine.
panooos said:
You have to format data... Not just wipe it. From TWRP go to format data, write yes, and let it format everything. Then transfer over to the phone all the fil a you need (ROM, kernel, no verity zip) and flash them as per the instructions of your rom thread. You should be fine.
Click to expand...
Click to collapse
What I did is just after trying the flash OS with no magisk, I booted to system. However, i just dont boot at all so I decided to boot to recovery again, but this time the recovery is the stock one. I wipe everything I could including cache, system reset, and data (music pics etc) and it booted to the system in no time but everythings lost.
Edit: nvm you've solved it
Peshyy said:
Edit: nvm you've solved it
Click to expand...
Click to collapse
You can still show other solutions as others may need it sometime

Vendor Partition is missing in Wipe menu in TWRP

I flashed TWRP recovery I used last week, to install SparkOS and I do remember following a tutorial that said wipe Dalvik, Cache, Data, System and Vendor, which I did successfully and installed the custom rom. I didn't last much and reverted to Stock Rom.
Cut to yesterday I flashed the same recovery as last time, and when I went to wipe the partitions I didn't find Vendor. Checked Mount menu clicked on Vendor it didn't show up under Wipe.
Should I ignore this and continue with installing my custom rom after wiping (Dalvik, Cache, Data and system only) or this is a problem and I am not able to install any custom rom until I wipe Vendor Partition?
It may cause problem or maybe not. Try Orange Fox recovery or any other recovery which supports to wipe vendor data and then flash your Custom Rom correctly as in tutorial.
ai.Sanaul said:
It may cause problem or maybe not. Try Orange Fox recovery or any other recovery which supports to wipe vendor data and then flash your Custom Rom correctly as in tutorial.
Click to expand...
Click to collapse
I followed it step by step, but I'm gonna try different versions and see if shows up. Otherwise I'll revert back to stock and hang my hat.
ai.Sanaul said:
It may cause problem or maybe not. Try Orange Fox recovery or any other recovery which supports to wipe vendor data and then flash your Custom Rom correctly as in tutorial.
Click to expand...
Click to collapse
Updating the TWRP version from 3.3.1 to 3.6 fixed the problem. Thank you for the help.
Ikarisdruig said:
Updating the TWRP version from 3.3.1 to 3.6 fixed the problem. Thank you for the help.
Click to expand...
Click to collapse
welcome

Categories

Resources