As a desktop user, I always do a clean install when upgrading to a new version of an OS (ex. Windows 7 - Windows 8) since the update process can cause a few kinks in performance and compatibility and a clean install will keep the system operating optimally. I do this by formatting my drive and reinstalling a fresh new version of the OS. With the upcoming Android L update, I was wondering if there was a way for owners of Nexus, GPE, or Motorola devices to do something equivalent to a clean install since they will most likely be getting the update first. Does an Android OTA update run as a Delta update or does it essentially reinstall the entire OS? Would simply running the OTA update and doing a factory reset be equivalent to a clean install?
A true clean install would involve flashing the stock image through fastboot, which would erase all partitions, including your SD card also I believe. Android OTA's work as delta updates, replacing only files that need to be erased. Installing the OTA and then doing a factory reset is as clean of an install as you can get without a custom recovery and completely wiping all your partitions through fastboot (The cleanest install you can get).
Sent from my Nexus 4 using XDA Free mobile app
Related
i tried to install update 68, the shield reboots get me to the screen with the android on its back, select the update install, then it errors out?
is the device being rooted causing the issue o the bootloader.
also if this or any small update installed correctly would i lose my root access,
if i lose root, will i always have to start from a factory rest and lose all my information to root it again.
thanks
An unlocked bootloader is not the problem. If you somehow modified the system image ( like rooted/removed apps, integrated updates into ROM, installed custom recovery or something else) the update process will fail because of it. That might have to do with the fact its an incremental update which checks if it is modified/rooted and/or will update apps which aren´t there anymore.
One way to solve this is to backup your apps and data. Then flash stock recovery and stock image via fastboot and install all updates from the beginning.
The other way is to go to Nvidias Support Page for the Shield. Then download the latest Update for it. It´s an sh package which needs to be extracted under Ubuntu or special tool for windows. Then you can flash the newest image and recovery directly with fastboot. Didn´t try that.
Hope i was able to help you.
I have a Moto g3 (osprey) with Android 6.0.1 and CyanogenMod version 13.0-20160927-NIGHTLY-osprey.
Obviously previous owner did not keep up to date installing the received updates.
When I attempt to install the oldest update it does not complete successfully. I get the Android character with red in stomach
.Upon rebooting it does so to current version.
What would be the best way with fewest steps to bring this phone's cyanogenMod up to date?
Thanks in advance
Jerry
That version is almost a year old... and it sounds like you don't have TWRP installed.
Install TWRP via fastboot, download latest LOS ROM and gapps, start TWRP, wipe system and caches, flash ROM and gapps.
Be aware that such a large jump might require a clean install, meaning you need to wipe all your data and installed applications.
Recently updated to 10.3.4 but having an issue with one of my games. I've tried everything I can think of to fixing it, including resetting the device and starting fresh. Only thing left for me to do would be to downgrade to the previous update.
I am rooted, with xXx and Renovice ICE running, would like to continue using them.
Would the easiest way to downgrade be to download 10.3.3 full OTA, wipe everything in TWRP, flash the OTA, then flash magisk?
If going to an older security patch you might need to format /data and start over.
Hello community!
Hope you are doing awesome, I am trying to install specifically the update from the 18 th of May (latest while doing this post) so when I downloaded it I go to TWRP and this is what I done
1)Place my pin and decrypt the device
2) Perform a format Data > Yes
3) Wipe cache, dalvik, internal
4) Restart to Recovery
5) Install the update all seems to be fine and reboot to system
The Phone boots to Poco screen and then vibrates and then gets me back to TWRP. I manage one time to get it worked and got in the config page from the customer rom a UI unresponsive message and is unable to connect to my Wifi so I have to use the Data 4G to make it work and I rolledback to April version of Arrow OS that seems to be the one working now.
The Miui stock that I am using to install the customer Rom is surya_global_images_V12.0.8.0.QJGMIXM_20210222.0000.00_10.0_global
Could you please provide some hints and tips what I am doing wrong so I can get this updates up to date? Because I love the Arrow OS Rom and I want to keep the firmware updated correclty on my side.
Thank you!
I am very interested, too. Got the same problem. After latest OTA-Update I'm stuck in a recovery bootloop as well.
Sadly even the attempt to flash back an older version or a MIUI Stock rom is failing for me now. Always recovery bootloop, even after a successfull flash without errors (and format data of course) .
Is the stock rom or an older arrow os version working for you, after the 18th May update?
@koelbche I was able to make a stock based on the stock fw shown on my post. then I installed old version of arrow OS April update and it was restarting bootloop.
I had to delete data, factory reset and select de wipe options so super clean flash and manage to boot it up.
I am waiting for any updates from others that manage to install the updates because I was not able to do it.
Flash ArrowOS custom recovery for ota update to work. After update you can flash recovery back to TWRP for root and backup, your choice.
I was able to make it worked in another post.
All I have to do was to update the version of the stock with Oss vendor (I think) and then all worked like a charm!.
Thanks for the replies though
Hello! I've been rooting and installing custom ROMs for years but it's been a long while since I last did it, I got a oneplus 8 global (IN2015) late last year, unlocked the bootloader as soon as I got it out of the box since I knew eventually I would want to flash some stuff. but I have kept it stock this long. Running latest Oxygen 11 android 11
Since I want to start flashing some kernels or roms I wanted to ask about making a backup since I've never had a phone without sd card slot where I would usually store backups.
Can I still use titanium backup to keep all of my apps/data/photos/videos and the state they are in, store it in my pc , then go about flashing a custom Rom and then bring my titanium backup back into the phone and restore everything?
since I'll be installing custom roms based on android 11 I believe it will be fine with no conflicts? or does it matter that my apps were installed in Oxygen OS?
that's what I used to do with older phones anyway. is there a way to flash a rom while having the titanium backup still in storage since most roms require full whipe when clean installing them?
Recently twrp added official support for OP8 and when I open the official app it recognizes my phone as instant noodle but when I click search for phone it says it can't connect to the server? should I flash official twrp from the app or via fastboot? which I'm also quite rusty with.
any tips for a step by step would be appreciated
Hello, I was in the same boat as you since I came to the OP 8 from a Galaxy S4. Titanium backup should work for what you want to do, as long as the custom rom is also based on A11 (disclaimer: I haven't tried it; I'm running rooted stock OOS 11 with a custom kernel). If the rom you want to install requires a data partition format, you can't keep the backups there during the flashing process. If it only needs a data wipe / factory reset, everything in the sdcard directory (also known as /data/media) should be preserved.
I'd say just flash TWRP in fastboot. Flash it to both recovery slots, and read up on how flashing works with A/B slot devices if you aren't familiar, since you'll need to know about it when flashing roms also. It's a big difference from what I was used to with older devices.
Thanks for the reply, yeah I was thinking of just going with a custom kernel since I have so much stuff going on the phone I find it really a chore to backup, but still might want to try it.
What kernel are you using and how are you liking it ?