Question Will OTA update wipe data? - Xiaomi Mi 11 Ultra

Hi All
I flashed EU rom and have just got an OTA update of around 4GB. Rather than install automatically, it just downloaded the zip and rebooted into TWRP.
I'm happy to install it using this method by wiping caches and using TWRP install, but would the TWRP method wipe my data so I need to back up?
Sorry for the dumb question lol.
Cheers
Steve

picitup said:
Hi All
I flashed EU rom and have just got an OTA update of around 4GB. Rather than install automatically, it just downloaded the zip and rebooted into TWRP.
I'm happy to install it using this method by wiping caches and using TWRP install, but would the TWRP method wipe my data so I need to back up?
Sorry for the dumb question lol.
Cheers
Steve
Click to expand...
Click to collapse
No it won't format. Just install ROM, wipe dalvik cache ( as presented to you after flash), then reboot system.

Hi @Sathelp
Thanks for your reply. I'll give it a bash and report back.
Cheers
Steve

All critical data should always be backed up redundantly. Otherwise you will lose data, sooner or latter.
Android crashes are very rare but can happen with little or no warning especially if you're mucking directly with the OS. That lockout is one reason stock Androids are so impervious to crashes.

Well that didn't take long! It's updated like a dream, with all my data intact.
I had a bit of fun finding the zip, as it wasn't in downloads as I expected. File Explorer showed as being in / in MIUI which of course, is /sdcard/ in TWRP. Anyway, zip loaded, flashed and now I know how to do it for the next update!
Cheers
Steve

picitup said:
Hi All
I flashed EU rom and have just got an OTA update of around 4GB. Rather than install automatically, it just downloaded the zip and rebooted into TWRP.
I'm happy to install it using this method by wiping caches and using TWRP install, but would the TWRP method wipe my data so I need to back up?
Sorry for the dumb question lol.
Cheers
Steve
Click to expand...
Click to collapse
NO, the data is only wiped when your internal storage has to be formated, like going from the stable to the weekly.

Related

'do a wipe' ? not sure what this means exactly, maybe it is what i need to do?

I have a HTC ONE m7, rooted, I have been running CM11, flashing the nightlies with great success. When CM12 came out, it 'soft bricked' my phone, continuous reboots, failing android functions. was able to reinstall Titanium backup, then restore the phone to a previous point. back running, but not without bugs. after trying this 3 times, I have given up. but I read where people say, "do a wipe" then flash the ROM....... What, specifically does this mean?
yes I have rooted my phone, but I am just knowledgable to be dangerous. if It means back to factory specs, then how do I flash the rom? I think that my phone should run CM12, and maybe I need to wipe? wipe what? dalvic cache? is that a wipe?
Anybody have some ideas or can point me to some postings that may help me. Many Thanks, very tired of operating on the last build of CM11
blairan
Do a wipe typically means wipe the data, system, cache, and dalvik cache partitions. If you are using TWRP as your recovery (I do for this phone), boot into it and then press Wipe, then Advanced Wipe. Select those four (not internal storage or USB OTG) and then Swipe to Wipe. Of course, your phone won't boot at this point, so you'll need a new ROM waiting on internal storage to be flashed.
thankyou Coal, I have been trying to install a CM12 and/or a CM12.1 ROM I can get them to boot up, but play store is not present. I can access play store via themes, and it comes up as a web page rather than an app. (is this norm for CM12?)
once I sign in to play store, I try to install titanium backup to restore all my apps. it says it is installed, I press it anyway, and it says it will be installed soon, which never happens. CM12 and CM12.1 seem to be running fine, but I can't restore any of my old phone. I can recover to a CM11, but it is a little unstable, so I would like to upgrade the system and be flashing nightlies again. what do you think?
and after watching a few videos on you tube, I figured out that I was missing the Gapps file, and the supers file. enjoying lollipop success.
thanks coal!
blairan said:
and after watching a few videos on you tube, I figured out that I was missing the Gapps file, and the supers file. enjoying lollipop success.
thanks coal!
Click to expand...
Click to collapse
I was going to suggest GAPPS, but I wasn't sure if you needed it for CM. Glad you figured it out!

Stuck on bootloop, stock recovery, want to recover files.

So I decided to try out Ivan's Marshmallow ROM, knowing it would be a bad idea... I backed everything but the photos which were 2.5GBs and was too lazy to copy over. I wiped cache, but not user data, copied ROM to phone, rename to update.zip and updated through recovery(stock). Now it's stuck on booting and want to know if there is any way to recover my photos.
Keep in mind there is a functional MIUI ROM inside but it is named differently than update.zip so I don't know how to flash it. It turns on, boots on fastboot and recovery but can't do much... I could wipe it, but I need the photos....
Thanks in advance.
eXtrimist said:
So I decided to try out Ivan's Marshmallow ROM, knowing it would be a bad idea... I backed everything but the photos which were 2.5GBs and was too lazy to copy over. I wiped cache, but not user data, copied ROM to phone, rename to update.zip and updated through recovery(stock). Now it's stuck on booting and want to know if there is any way to recover my photos.
Keep in mind there is a functional MIUI ROM inside but it is named differently than update.zip so I don't know how to flash it. It turns on, boots on fastboot and recovery but can't do much... I could wipe it, but I need the photos....
Thanks in advance.
Click to expand...
Click to collapse
Assuming that you haven't yet extended partitions, stock phone has 2 system partitions. So if you're using system 1, boot using system 2 and vice versa. AFAIK, if you flash stock miui using MiTools, it wouldn't erase the storage on the phone.
The second partition seems unable to boot as well...
Anyway, if found out I could install twpr through fastboot, from where I could mount the sdcard.
As far as MiTools are concerned, last time I tried it, I think it erased everything.
The thread can be closed. Thanks!
eXtrimist said:
The second partition seems unable to boot as well...
Anyway, if found out I could install twpr through fastboot, from where I could mount the sdcard.
As far as MiTools are concerned, last time I tried it, I think it erased everything.
The thread can be closed. Thanks!
Click to expand...
Click to collapse
Glad you could work it out. Don't be lazy next time

Question about 3T Stock Recovery

Well my 3T after days of "Pending Shipment" is on the way and luckily, Stable Nougat is out!
So I had some questions about recovery in preparation.
1. In OnePlus's stock recovery, is there a way to mount storage? I ask because basically, while I'm still waiting for my phone to arrive, I'd download the Nougat Rom and as soon as I receive the phone, boot into recovery, mount storage, get the file and then flash the Update to have a completely clean install.
2. If it's not possible to mount storage in recovery and I have to setup the phone, I'd just put the Update on the phone's storage after setup and would then, be able to do a clean install from the stock recovery right?
Just wanted some clarification as I think just having the update ready to go would save me time of actually downloading the update.
Thank You and Happy New Year
The internal storage is mounted automatically in stock recovery.
Apart from that, if you want to reinstall your system, download the full rom. The ota will only work when your system partition is untouched.
Also, why do you want to re-setup your phone? If you do not want to redownload your update, do not do a factory reset.
Jo_Jo_2000 said:
The internal storage is mounted automatically in stock recovery.
Apart from that, if you want to reinstall your system, download the full rom. The ota will only work when your system partition is untouched.
Also, why do you want to re-setup your phone? If you do not want to redownload your update, do not do a factory reset.
Click to expand...
Click to collapse
I think you misunderstood, I don't have it yet it's on the way.
I have the 1.4gb Nougat rom and what I'm saying is that instead of setting up the phone and then waiting for Nougat to download and etc,
as soon as I get, boot into recovery and just install Nougat to save myself time while doing a clean install at the same time and moving from there.
But you answered my question about storage being mounted in recovery, thanks.
star4oelife said:
I think you misunderstood, I don't have it yet it's on the way.
I have the 1.4gb Nougat rom and what I'm saying is that instead of setting up the phone and then waiting for Nougat to download and etc,
as soon as I get, boot into recovery and just install Nougat to save myself time while doing a clean install at the same time and moving from there.
But you answered my question about storage being mounted in recovery, thanks.
Click to expand...
Click to collapse
I think it would be best if you would just sideload the ota package

upgrading to Nougat, trouble replacing old kernel

Apologies for duplicating this post but the original forum was apparently the wrong spot for this.
I need either some pointers or a reference to a how-to, if you please.
My Nexus 6 is currently running Pure Nexus 6.0.1-2060821-official, security patch 8/5/2016 with ElementalX kernel 3.10.40-ElementalX-N6-3-20.
I've updated Pure Nexus before through TWRP and all went well, but those efforts never involved updating the kernel too. I've attempted to flash the new kernel, the rom and the google apps, but the phone goes into a never ending boot effort and it's a tussle getting back to recovery mode as it tends to boot loop. The flashes are preceded by clearing Delvik and cache and cleared again after the flash.
Is the order of flashing off or perhaps not enough clearing of other items such as system? Or is a factory reset needed?
Kind of lost on this one and can't seem to string together enough search terms to find help specific to the problem.
Any help would be appreciated.
The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.
zelendel said:
The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.
Click to expand...
Click to collapse
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?
jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?
Click to expand...
Click to collapse
You are doing a full wipe right? Wiping system and data before flashing?
Also encryption could be an issue. If your device in encrypted or the kernel did not remove the force encryption flag. That could take awhile as well.
jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215
Click to expand...
Click to collapse
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?
Pkt_Lnt said:
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?
Click to expand...
Click to collapse
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.
Needs Nougat bootloader and latest radio--flash in TWRP. This allows flashing N ROMs while will still work with all MM or even 5.1 ROMs
http://batakang.com/ftp/devs/mhous33/shamu/bootloaders/shamu_bootloader_moto-apq8084-72.01.zip
http://batakang.com/ftp/devs/mhous33/shamu/7.1.1/shamu_baseband_D4.01-9625-05.44+FSG-9625-02.115.zip
jlfesslerkc said:
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.
Click to expand...
Click to collapse
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.
Try reverting to stock
Install stock firmware using adb
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
Hi... Save your internal storage before processing. Just in case... TWRP 2.8.5.0 is pre nougat and incompatible.
jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
You should really update the bootloader/radio to the latest once you update the TWRP. Updating the bootloader/radio will not affect your internal storage.
Pkt_Lnt said:
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.
Click to expand...
Click to collapse
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?
jlfesslerkc said:
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?
Click to expand...
Click to collapse
yup
Item 1.8 and 1.9 here
Pkt_Lnt said:
yup
Item 1.8 and 1.9 here
Click to expand...
Click to collapse
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?
jlfesslerkc said:
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?
Click to expand...
Click to collapse
That is what Titanium Backup (and Restore) does, yes.

General Flash / Rooting Question S10e (970F)

Hi guys
Hope you are well, just wanted to find out, i rooted my phone using the patching method (Magisk). Thereafter i installed TWRP (Placing TWRP / VBMETA file in one archive) Flashed it, and it worked, i was able to log into recovery, i then formatted data, rebooted and wiped Dalvik etc etc. (Note i did not install the Multidisabler (The instructions i followed did not mention anything about it) I then installed LOS with GAPPS,
I know would like to try and either install Beyond ROM, or if need be back to complete stock (CTF3) as im missing DEX.
Can i just log back into TWRP - WIPE and installed Beyond ROM? (As we used to do in the old days - jumping between ROMS) Or should reflash MAGISK TWRP process everytime? If this is the case i would want to rather move back to stock...
Can i just flash back in ODIN and all will be good? Or is there any risks? (Ie in bricking the device etc)
Have you checked out this thread?
https://forum.xda-developers.com/galaxy-s10/how-to/proper-to-root-s10-device-twrp-s10-10e-t4015813
StoneyJSG said:
Have you checked out this thread?
https://forum.xda-developers.com/galaxy-s10/how-to/proper-to-root-s10-device-twrp-s10-10e-t4015813
Click to expand...
Click to collapse
Hi there! Thank you very much, this is a fantastic guide. Exactly what i was looking for

Categories

Resources