Is it possible that there will be no wipe update 5.1 ZIP with no encryption? Works like OTA.
I'd like to update from 5.0.1 (no force encryption) to 5.1 without loosing my data. The best for me is zip for TWRP
Well if backup everything in twrp to an external flash drive then it shouldn't be an issue. I know people have side loaded the OTA via ADB but it hasn't been working for everyone. You obviously can't take a normal OTA if you are rooted so you could try that. Alternatively I would download Parcel if you have root and backup all of your apps and data for each one that you don't want to lose then transfer it to an external drive so you don't lose it when flashing the updated images. From here you can install 5.1 and then simply restore all of your missing apps and data using Parcel. It works really well and much better than TiBu for restoring data in apps. I use both TiBu and Parcel for different things. The above is only if you can't find any alternative ways to get it loaded in TWRP
There's a stock based ROM in dev forum. Flash that followed immediately (without booting) a kernel with no force encryption such as elementalx and you'll be good.
Or just fastboot flash a system image followed by immediately boot into recovery, flash kernel and SuperSU
rootSU said:
Or just fastboot flash a system image followed by immediately boot into recovery, flash kernel and SuperSU
Click to expand...
Click to collapse
So what if we wanted to, coming from encrypted, decrypt without a wipe?
drinfernoo said:
So what if we wanted to, coming from encrypted, decrypt without a wipe?
Click to expand...
Click to collapse
nope. your internal storage meeds to be reformatted. save on a computer anything you would need.
Related
My N6 is rooted, SuperSU and TWRP. On build LYZ28J and want to update to LYZ28K.
It seems I have 3 ways to do this:
1. Use settings in SuperSU to fully unroot, AND flash the LYZ28J recovery.img to replace TWRP. Then I can take the OTA. After that I can rerun the Chainfire Autoroot script and flash TWRP. So i'm updated with no data loss.
2. Flash the factory image. No need to unroot or remove TWRP, but all data is lost. And I still need to reroot and reflash TWRP. Correct ?
3. sideload the ota zip. Just run adb sideload <ota.zip> . No need to unroot . My problem here is that the only place I found with the ota zip is on Droid Life, not a google url. I like Droid Life, read it all the time, but still... Does anyone have a google url link to the OTA ?
Is there another method?
How are others upgrading? Is #3 as easy as I described ?
sean
1. no. to fully unroot, you need to flash a factory image. if you just remove root, itll still think tour rooted because system files have changed. so, wont work.
2. you can, but why? you gave extra time that you want to burn?
3. nope, cant flash an ots while rooted ir havd chsnged system files.
4. just flash the system.img of a factory image ehen it vomes out, and you will not lose data, but will upgrade.
I've used this thread (http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158) to update within Lollipop through several versions. It is always best to wipe data when going from one version to the next (Lollipop to Marshmallow) but as long as you are staying within Lollipop this should work fine.
Check this out, http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
IMO, easiest way. DL zips to internal storage, wipe, and flash. READ the "Read Me" in the first post. When you update it will get rid of SU. Once you boot with update the first time, you can go back and root with TWRP.
Chose to use this. Did not flash the new recovery image. Updated fine, BUT locked and no root, no TWRP. I'll need to run oem unlock again, wiping all the data.
Sigh.
Wrote too soon. SuperSU and TWRP were gone (even though I did not flash recovery.img). Developer Options was gone. So I needed run CF-Autoroot and still need to flash TWRP. But all apps and data remained.
This is great news, especially if we're going to get monthly updates.
So what's the best way to flash a update and not lose data? If it's just a security update and not an actual version difference, what's the best way to do this and not lose data? Keep in mind, my device is unencrypted. I was thinking flashing everything except userdata, and then booting into TWRP straight away and flashing a kernel before first boot, would this work?
H4X0R46 said:
So what's the best way to flash a update and not lose data? If it's just a security update and not an actual version difference, what's the best way to do this and not lose data? Keep in mind, my device is unencrypted. I was thinking flashing everything except userdata, and then booting into TWRP straight away and flashing a kernel before first boot, would this work?
Click to expand...
Click to collapse
This is how I do it:
Copy/download new zip with prerooted lite stock rom of Danvdh to internal storage.
Boot Twrp-recovery.
Wipe system partition and caches
Flash new rom (zip)
Twrp file manager - restore layers from back up.
Reboot
NLBeev said:
This is how I do it:
Copy/download new zip with prerooted lite stock rom of Danvdh to internal storage.
Boot Twrp-recovery.
Wipe system partition and caches
Flash new rom (zip)
Twrp file manager - restore layers from back up.
Reboot
Click to expand...
Click to collapse
So it's easier to just use the zip rather than flash with fastboot?
H4X0R46 said:
So it's easier to just use the zip rather than flash with fastboot?
Click to expand...
Click to collapse
Yes, and I only backup the data partition and recovery on the phone.
Till now I think the method is comfortable and faster for the monthly updates. Everything that's needed is on the phone.
When there is a complete new Android, like N,
it could be different. Especially when kernel, bootloader and radio are new. We need a modded kernel that does not forces encryption.
Has anyone noticed how TWRP doesn't persist with the latest N dev preview?
I'm not talking about systemless install, either.
I verified that TWRP renames "recovery-from-boot.p" to "recovery-from-boot.bak" before first boot, but on next boot into recovery, it's back to stock.
I even manually renamed "/system/bin/install-recovery.sh" to "system/bin/install-recovery.bak", and "/system/etc/recovery-resource.dat" to "/system/etc/recovery-resource.bak".
Then I deleted all three files; TWRP still gets overwritten with stock recovery.
AFAIK these are all the files associated with creating stock recovery from the boot image, so not sure what else to try.
As it stands, the only way to use TWRP is to fastboot it from pc every time you want to use it.
Btw, I know I can just use a custom rom instead, so please don't provide that as a "solution" lol.
*Edit*
It seems that after deleting these three files and then reflashing TWRP solves the problem.
SuperSU still disappears after a data wipe, but with persistent TWRP, at least it can be reflashed without pc...
Q9Nap said:
Has anyone noticed how TWRP doesn't persist with the latest N dev preview?
I'm not talking about systemless install, either.
I verified that TWRP renames "recovery-from-boot.p" to "recovery-from-boot.bak" before first boot, but on next boot into recovery, it's back to stock.
I even manually renamed "/system/bin/install-recovery.sh" to "system/bin/install-recovery.bak", and "/system/etc/recovery-resource.dat" to "/system/etc/recovery-resource.bak".
Then I deleted all three files; TWRP still gets overwritten with stock recovery.
AFAIK these are all the files associated with creating stock recovery from the boot image, so not sure what else to try.
As it stands, the only way to use TWRP is to fastboot it from pc every time you want to use it.
Btw, I know I can just use a custom rom instead, so please don't provide that as a "solution" lol.
*Edit*
It seems that after deleting these three files and then reflashing TWRP solves the problem.
SuperSU still disappears after a data wipe, but with persistent TWRP, at least it can be reflashed without pc...
Click to expand...
Click to collapse
supersu will always disappear after a data wipe, unless you set it as a system app. and flashing twrp, then deleting that one file upon boot will fix twrp being deleted. and its been that way for years.
simms22 said:
supersu will always disappear after a data wipe, unless you set it as a system app. and flashing twrp, then deleting that one file upon boot will fix twrp being deleted. and its been that way for years.
Click to expand...
Click to collapse
I flash the supersu zip package with twrp rather than downloading from the play store, so supersu is a system app automatically and hasn't historically been erased during a data wipe.
I understand what you're saying though.
The approach you described would be necessary coming from an unrooted device with a stock recovery and no access to a pc, assuming the bootloader was already unlocked.
Hi all,
What happens if you take a stock 3T, upgrade it all the way to Nougat the normal way, then proceed to unlock the bootloader, flash TWRP and supersu?
Does the TWRP 3.0.3.0 build have an issue with decrypting and mouting the sdcard? Is that even a problem in the sense of waiting until a fixed version of TWRP is released? The point is to just flash supersu for the moment. No other need to access that partition from recovery, is there? Or does it directly impact my ability to upgrade TWRP in the future?
And another question: would decrypting the phone after the stock to Nougat update, and only then flashing TWRP&root be of any use? Is this even possible at the moment? I can hold on without encryption until there's a proper version of TWRP, kernel sources are released etc.
I don't seem to find any info on these scenarios. Has anyone tried any of this?
Thank you!
Good questions.
Does the TWRP 3.0.3.0 build have an issue with decrypting and mouting the sdcard?
Click to expand...
Click to collapse
I can confirm 3.0.3.0 has problems with decrypting and mounting sdcard. A new version of TWRP should fix this.
No other need to access that partition from recovery, is there?
Click to expand...
Click to collapse
Well, the need to access partition from recovery depends. You won't be able to flash anything from TWRP. I could sideload different recoveries without decrypting but had to decrypt (with the format userdata command from cmd prompt) to revert to 3.5.4 from TWRP. In the end I mostly downgraded due to bluetooth issues.
I am having the same decryption issue... TWRP shows 0MB as the storage
What should be done now..?
you can get past encryption by formating data in twrp, though that deletes all your data, back ups and everything, but with that you have the phone completely rooted and then you can download or transfer data via mtp to storage, flash super su and verity.
Amar97 said:
you can get past encryption by formating data in twrp, though that deletes all your data, back ups and everything, but with that you have the phone completely rooted and then you can download or transfer data via mtp to storage, flash super su and verity.
Click to expand...
Click to collapse
Did that already but did not work.. Even tried the setting up of pattern method.. that too did not work...
Also force decrypted with Toolkit but still the same
just to make sure. flash twrp via fastboot( I flashed the 3.0.2.0 version) then when booting to twrp you get get the screen where it asks you for a password, skip that , just swipe to continue then go to wipe, then format data, type "yes" to confirm, the at the next booting it shouldn't ask you for the password anymore. That did it for me. Maybe you should try adb sideload to flash verity.img and supersu
Amar97 said:
just to make sure. flash twrp via fastboot( I flashed the 3.0.2.0 version) then when booting to twrp you get get the screen where it asks you for a password, skip that , just swipe to continue then go to wipe, then format data, type "yes" to confirm, the at the next booting it shouldn't ask you for the password anymore. That did it for me. Maybe you should try adb sideload to flash verity.img and supersu
Click to expand...
Click to collapse
why not use 3.0.3.0?
Solnir said:
why not use 3.0.3.0?
Click to expand...
Click to collapse
Don't really know, probably tried solving the problem by trying with the older version and then didn't feel like upgrading to the newer 3.0 after fixing the problem.
I have a UK XT1072 which:-
has an unlocked bootloader
is rooted (with SuperSU v2.78)
has a custom recovery (TWP v3.1.0.0) and
is on stock MM (v6.0)
.
I want to revert to Lollipop.
I have d/loaded a stock 5.0.2 LL rom (RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml.zip) but am unsure how to install it successfully.
I'm unsure if I should either:-
get into TWRP recovery, do a full factory reset including a wipe of internal storage and then install the stock LL ROM zip using TWRP, or
get into TWRP recovery, do a full factory reset (but no wipe of internal storage) and then install the stock LL ROM zip using TWRP, or
connect the phone to a PC, get into TWRP recovery, do a full factory reset including a wipe of internal storage, stay in recovery and then use ADB command set on the PC to install the unzipped components of the stock LL ROM? (if it's this option, please someone tell me what the command sequence is)
Note: I assume I will have to re-root the phone once I've done this but unsure how to do this on LL - same as on MM (ie use TWRP to install SuperSU zip) or different for LL?
Can anyone please let me know which, if any of these options is the best/easiest/safest? Or, if it's none of them , tell me what I should be be doing!
Many thanks to anyone who can help
First option - assuming you have a SD card not formatted as internal and your LL zip is there and accessible (check your card and files through TWRP before deleting anything).
You will lose root if SuperSU is no longer present - so add the flashable SuperSU on the card and flash it before first reboot.
I can't think of any reason you would want to go back to Lollipop other then the annoying Android 6 security restrictions, but you can bypass them by using the right custom ROMs. Those usually come with root managers included. I'd recommend this one - it is for Titan, not ours, but, with some tweaks, it can be installed on Thea and it works Lollipop-style in regard to permissions - not to mention your root is taken care of automatically, as it has SuperSU included in the installation package.