What to wipe before manual update - ONE Q&A, Help & Troubleshooting

Bought a chinese oneplus. Unlocked bootloader and installed root and install cyanogen 11s through C4tech's guide by flashing the XN22R bacon signed.zip in recovery.
Now cannot update to latest cyanogen via system updates.
Installed update 25R manually but am experiencing a battery drain, not really a battery drain but noticed a significantly increased battery depletion rate.
I wondered if its due to the fact that i did not wipe data before updating.
I simply typed the unlocked bootloader command before manual flashing. (The flastboot flash radio stuff...)
Should i wipe date wipe cache wipe system?

Related

How to install 5.1.1 without losing data...

Hey Guys,
My N5 is currently running android 5.1 and I want to upgrade to 5.1.1. My phone also shows that the OTA update is available but I am currently rooted and running TWRP. A quick google research showed me that I canĀ“t install an OTA update while being on TWRP. Is there any other way to update my phone to 5.1.1 without losing my data?
Greets
I have this exact same question. I was going to try and use fastboot with the system image and recovery and then take the ota update. Not sure if that will work.
I got impatient, so i downloaded the factory image from the web for the version of my phone (lmy47d). I extracted the system.img and recovery.img and flashed them with fastboot as stated here -> http://forum.xda-developers.com/goo...orial-applying-ota-update-stock-root-t2976556
Rebooted the phone and then applied the OTA update. Phone is updating the apps after boot. So far seems ok.
Thank you I will try it out later
You don't lose data by default? At least not for me

Can't update with OTA zip.

I'm on the XT1540 and I got my OTA notification and went back to stock recovery (still rooted and unlocked bootloader) but it fails halfway through flashing everytime. I reflashed TWRP and captured the OTA into a zip but get an error about updating binary or something when flashing it. Is there something I need to delete from the OTA zip to allow it to flash in twrp?
Sent from my MotoG3 using xda premium
You cannot update your systems software using the OTA update if you are rooted and have modified the system in any way as there are checks of original system during the auto update over the OTA. This means having the original recovery too. Wont work on TWRP or CWM. So no root and no custom recovery for OTA. Unlocked bootloader is okay.
In case you want to try the OTA update then what I have noticed on my XT1550 dual sim APAC version is that even unrooting it using the SuperSu unroot option is not going to help. In my case I could download the OTA and waited till it replaced the system software but got stuck midway of the boot animation.
I had to flash the 23.72-33 version of the stock ROM and opt for the OTA update. This time though I was successful.
Hope this info helps.
Yes, what arunhebbare says. you need to back up al your data and restore your stock firmware and than update via ota.
that is the best way of doing it
HelpMeruth said:
Yes, what arunhebbare says. you need to back up al your data and restore your stock firmware and than update via ota.
that is the best way of doing it
Click to expand...
Click to collapse
This...do a full factory image restore, then adb sideload the ota file. It's signed. TWRP can't install it.
Just use fastboot to flash the factory image for the version you want ... screw wiping your user partition like the above recommends.
nikon120 said:
Just use fastboot to flash the factory image for the version you want ... screw wiping your user partition like the above recommends.
Click to expand...
Click to collapse
This...I can't understand, for the life of me, why everyone is wiping userdata with fastboot....that wipes your android data, and internal storage in one shot. Cache erasing is another totally unnecessary step. All that's necessary, at the most, is a factory reset with TWRP to wipe the android data and both caches....but even that shouldn't technically be necessary for an update like this. It's not like this is the marshmallow update!!
arunhebbare said:
You cannot update your systems software using the OTA update if you are rooted and have modified the system in any way as there are checks of original system during the auto update over the OTA. This means having the original recovery too. Wont work on TWRP or CWM. So no root and no custom recovery for OTA. Unlocked bootloader is okay.
In case you want to try the OTA update then what I have noticed on my XT1550 dual sim APAC version is that even unrooting it using the SuperSu unroot option is not going to help. In my case I could download the OTA and waited till it replaced the system software but got stuck midway of the boot animation.
I had to flash the 23.72-33 version of the stock ROM and opt for the OTA update. This time though I was successful.
Hope this info helps.
Click to expand...
Click to collapse
@arunhebbare I've got the APAC version of the G3 as well, which ROMs are you flashing? I could only find images of the India version, did you use those?

B394 update advise

Hi guys
I really need some assistance, just because I received a notification for update my honor 8 L09 from B389 to B394.
I'm not sure because the device has the bootloader unlocked and it is rooted now, so i'm really afraid to mess it up!
Should i do the update?
Thanks for the help in advance.
Crake said:
Hi guys
I really need some assistance, just because I received a notification for update my honor 8 L09 from B389 to B394.
I'm not sure because the device has the bootloader unlocked and it is rooted now, so i'm really afraid to mess it up!
Should i do the update?
Thanks for the help in advance.
Click to expand...
Click to collapse
Well I'll tell you how I updated my Honor 8 L09 from B389 to B394 and you decide if you wish to proceed. What you get with update is probably new security patch (you are currently on May I assume? And get updated to August 5th) and some minor changes.
So I updated same way as I did the update before (B381 to B389). I was rooted and bootloader unlocked same way as you currently are now, stock EMUI. First what you must do is a full TWRP backup because there is a high chance your bootloader will relock and you will have to restore data partition on your updated device, or at least that's how I had to do it.
To update you need to extract stock recovery.img from B389 and flash it via fastboot. After that you download full update image via
Settings > Update Device and confirm that you want to update. After that device will reboot and you'll be booted to recovery where update will take place. Once that finishes your device should reboot and if you encounter the same scenario as I did you will find yourself with fully locked bootloader. You won't encounter the "Your device is unlocked and bla bla black screen", you will go straight to the system and your device will be unrooted.
What I did after that is go to the fastboot to confirm that my bootloader is locked and indeed it was. I was unable to flash my TWRP recovery again. So my only solution to rooting and having TWRP again was to unlock the bootloader once again. You know the drill for that... Enter "fastboot oem unlock xxxxxxxx" and confirm the dialog. Get full factory reset, and reenter the fastboot to finally reflash TWRP. So assuming that you made the backup now all that has to be done is restore only DATA partition. And not to forget flash latest SuperSU zip. Of course I recommend you wiping dalvik cache or not restoring the data partition at all and starting from the beginning on your new system just so you have a clean start and no unexpected bugs even if I have none personally.
That's it. Some people reported different scenarios while doing this update. This is only how it went for me and your situation might be different so ALWAYS do backups.
NatusVincere said:
Well I'll tell you how I updated my Honor 8 L09 from B389 to B394 and you decide if you wish to proceed. What you get with update is probably new security patch (you are currently on May I assume? And get updated to August 5th) and some minor changes.
So I updated same way as I did the update before (B381 to B389). I was rooted and bootloader unlocked same way as you currently are now, stock EMUI. First what you must do is a full TWRP backup because there is a high chance your bootloader will relock and you will have to restore data partition on your updated device, or at least that's how I had to do it.
To update you need to extract stock recovery.img from B389 and flash it via fastboot. After that you download full update image via
Settings > Update Device and confirm that you want to update. After that device will reboot and you'll be booted to recovery where update will take place. Once that finishes your device should reboot and if you encounter the same scenario as I did you will find yourself with fully locked bootloader. You won't encounter the "Your device is unlocked and bla bla black screen", you will go straight to the system and your device will be unrooted.
What I did after that is go to the fastboot to confirm that my bootloader is locked and indeed it was. I was unable to flash my TWRP recovery again. So my only solution to rooting and having TWRP again was to unlock the bootloader once again. You know the drill for that... Enter "fastboot oem unlock xxxxxxxx" and confirm the dialog. Get full factory reset, and reenter the fastboot to finally reflash TWRP. So assuming that you made the backup now all that has to be done is restore only DATA partition. And not to forget flash latest SuperSU zip. Of course I recommend you wiping dalvik cache or not restoring the data partition at all and starting from the beginning on your new system just so you have a clean start and no unexpected bugs even if I have none personally.
That's it. Some people reported different scenarios while doing this update. This is only how it went for me and your situation might be different so ALWAYS do backups.
Click to expand...
Click to collapse
First of all thanks very much.
I'm really confident that is too much work for so few improvements.
I guess i will wait for Oreo update and the corresponding Emui version, and at that time i will get my hands busy!
I updated from B392SP02 super-easily via ota without losing root or my bootloader0unlock but beforehand I flashed the modified recovery that doesn't verify update files. (available in one of the threads here) Give that a try.

Xiaomi.eu OTA update

Hi guys,
I'm on xiaomi.eu 9.1.24 and today I've received a notification to install 9.2.15. Is it possible to normally update my phone rather than following this method "https://xiaomi.eu/community/threads/9-2-14-15.49206/" that would wipe my data?
I was thinking about flashing stock recovery and run the update.
If you are on Xiaomi.eu, how do you update your phone?
Off-topic: for me it's impossible to flash staff via twrp from internal storage because it shows numerous "weird" folders instead of showing the right ones.
(It seems to me it is (like) encrypted)
I just flashed it in twrp, no need to wipe.

Unable to update Arrow OS latest updates from May manually in TWRP

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

Categories

Resources