Hey All, I got the OTA (I have it in /cache in my phone so no need to download anything) in my Stock 33R with root, franco 23R and TWRP. When trying to install the OTA, I'm getting a "Can't install this package on top of incompatible data. Please try another package or run a factory reset" error. I've followed Franco's post on how to install this OTA (https://plus.google.com/106873500108976028532/posts/ByvTAonR6mH) and I have even flashed the backed-up kernel and still same issue. One more thing I did was remove supersu.apk from /system/apps/ just to make sure that was not the case. I've read about the modified OTA, however not sure why I would need any modified so I want to see if this can be done with the unmodified 38R
Anyone can help?
UPDATE: I was able to make it work, see comment #12
You need to go back to being completely stock. Perform a full wipe (system/data/cache/dalvik cache) and flash the recovery flashable version of 33R from here, Then you can flash the update.
Transmitted via Bacon
timmaaa said:
You need to go back to being completely stock. Perform a full wipe (system/data/cache/dalvik cache) and flash the recovery flashable version of 33R from here, Then you can flash the update.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, but there has to be other way that would not require wiping data... that is not acceptable
rhaces said:
Thanks, but there has to be other way that would not require wiping data... that is not acceptable
Click to expand...
Click to collapse
I'm not talking about user data, I'm talking about your system data partition.
Transmitted via Bacon
timmaaa said:
I'm not talking about user data, I'm talking about your system data partition.
Transmitted via Bacon
Click to expand...
Click to collapse
In your original post you mention "Perform a full wipe (system/data/cache/dalvik cache)", that will factory reset my phone (except /sdcard), that is what I want to avoid.
rhaces said:
In your original post you mention "Perform a full wipe (system/data/cache/dalvik cache)", that will factory reset my phone (except /sdcard), that is what I want to avoid.
Click to expand...
Click to collapse
You don't really have a choice. Why is it an issue? Just use Titanium to backup your apps and restore them again once you've updated. The only thing you'll have to do again is your system settings.
Transmitted via Bacon
timmaaa said:
You don't really have a choice. Why is it an issue? Just use Titanium to backup your apps and restore them again once you've updated. The only thing you'll have to do again is your system settings.
Transmitted via Bacon
Click to expand...
Click to collapse
I've had plenty of issues throughout the years with Titanium, which makes me not to trust it fully, it will consume a lot of time to fully backup and fully restore, and, most important, I really hate that I need to wipe and re-flash stock if I'm in stock (with a few modifications which can be all undone)
rhaces said:
I've had plenty of issues throughout the years with Titanium, which makes me not to trust it fully, it will consume a lot of time to fully backup and fully restore, and, most important, I really hate that I need to wipe and re-flash stock if I'm in stock (with a few modifications which can be all undone)
Click to expand...
Click to collapse
Follow vomer's guide here. It just bring your rom back to stock and leaves user data untouched. http://forum.xda-developers.com/showpost.php?p=55882576&postcount=229
rhaces said:
I've had plenty of issues throughout the years with Titanium, which makes me not to trust it fully, it will consume a lot of time to fully backup and fully restore, and, most important, I really hate that I need to wipe and re-flash stock if I'm in stock (with a few modifications which can be all undone)
Click to expand...
Click to collapse
There's nothing wrong with Titanium if you know how to use it. Unless you're restoring system data (which you shouldn't be) it's perfectly solid. And the thing is, you're not stock, those modifications you've made mean that you're not stock, so it's completely normal that you'd have issues with updating. You can moan about it all you like but it doesn't change the fact that you need to wipe.
Transmitted via Bacon
What he said.
You can't apply an OTA update if u have a custom kernel installed.
Just go back stock and apply updates until the latest version. If u use titanium properly you will not have any issue, just backup user apps without system settings.
Any other turnaround can cause havoc.
rhaces said:
Hey All, I got the OTA (I have it in /cache in my phone so no need to download anything) in my Stock 33R with root, franco 23R and TWRP. When trying to install the OTA, I'm getting a "Can't install this package on top of incompatible data. Please try another package or run a factory reset" error. I've followed Franco's post on how to install this OTA (https://plus.google.com/106873500108976028532/posts/ByvTAonR6mH) and I have even flashed the backed-up kernel and still same issue. One more thing I did was remove supersu.apk from /system/apps/ just to make sure that was not the case. I've read about the modified OTA, however not sure why I would need any modified so I want to see if this can be done with the unmodified 38R
Anyone can help?
Click to expand...
Click to collapse
Please check http://forum.xda-developers.com/showpost.php?p=55948892&postcount=16
@rhaces, just curious, could you PM me your /data/system/packages.xml file?
Well, It looks like you really don't need to wipe data (see, I told you it was ludicrous), I tried following both this and this, but did not helped (however both gave me ideas), here's what I did:
Fastboot flash boot system and recovery from 33R, boot into system, apply the OTA from the system (I'm now in an unrooted-unmodified stock 33R) and now that worked. Booted into newly installed 38R and everything worked ok, so went back to fastboot, flashed TWRP, went into TWRP and installed supersu and franco 24r and now things seem to be ok.
Thanks for all the help
Just don't complain when you start getting problems. Which you most likely will.
Transmitted via Bacon
Related
I have root, s-off, using TWRP recovery. I backed up everything on my external SD card with TWRP, ran (what I think is) RUU to get a clean install and was able to update to 4.4.3. After update, I put TWRP back on, and restored all my apps, still have s-off and root. A couple of things didn't restore (like Tasker), but I chalked that up to them probably being on the internal storage and then erased.
Everything else seemed to be working fine, but my WiFi will not turn on, and the default Sense camera opens to a completely black screen.
Any suggestions?
Thanks,
Ian
istrasci said:
I have root, s-off, using TWRP recovery. I backed up everything on my external SD card with TWRP, ran (what I think is) RUU to get a clean install and was able to update to 4.4.3. After update, I put TWRP back on, and restored all my apps, still have s-off and root. A couple of things didn't restore (like Tasker), but I chalked that up to them probably being on the internal storage and then erased.
Everything else seemed to be working fine, but my WiFi will not turn on, and the default Sense camera opens to a completely black screen.
Any suggestions?
Thanks,
Ian
Click to expand...
Click to collapse
To be correct, you are running a 4.4.3 ROM with 4.4.3 firmware right? Also when you try to enable wifi from the status bar does it simply endlessly show its trying to turn it on?
Perhaps a viable option would be to try a factory reset via TWRP, I sometimes encounter issues when doing that after a firmware update. Actually my 4.4.3 was so messed up because of restoring apps that I was forced to go back to my 4.4.2 ROM. Soo as I said, since you have a backup I'd just at least give factory reset a try and if it doesn't fix it then you can restore your backup again.
Try another kernel, I had the same issues
Enviado desde mi unknown mediante Tapatalk
bighleo114312 said:
Try another kernel, I had the same issues
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
I'm kinda new to all this flashing/recovery stuff. How exactly do I use another kernel?
istrasci said:
I have root, s-off, using TWRP recovery. I backed up everything on my external SD card with TWRP, ran (what I think is) RUU to get a clean install and was able to update to 4.4.3. After update, I put TWRP back on, and restored all my apps, still have s-off and root. A couple of things didn't restore (like Tasker), but I chalked that up to them probably being on the internal storage and then erased.
Everything else seemed to be working fine, but my WiFi will not turn on, and the default Sense camera opens to a completely black screen.
Any suggestions?
Thanks,
Ian
Click to expand...
Click to collapse
How did you restore your apps?
jsaxon2 said:
How did you restore your apps?
Click to expand...
Click to collapse
Through TWRP. I put it back on after the update and restored the apps and data (not the system) from the backup I'd made previously.
You could try and flash the stock rom from http://forum.xda-developers.com/showthread.php?t=2874699 through twrp and see if it works for you. Don't wipe anything, just try flashing on top of what you have. Might work.
jsaxon2 said:
You could try and flash the stock rom from http://forum.xda-developers.com/showthread.php?t=2874699 through twrp and see if it works for you. Don't wipe anything, just try flashing on top of what you have. Might work.
Click to expand...
Click to collapse
Do I do that through TWRP or through the bootloader?. Sorry, again I'm still new at this.
istrasci said:
Do I do that through TWRP or through the bootloader?. Sorry, again I'm still new at this.
Click to expand...
Click to collapse
Your posts didn't really make clear what exactly you did: From which rom you took the TWRP nandroid, which rom you restored it back to, what you mean by "you think you ran a RUU", what exactly from the nandroid you restored in TWRP....
Did you restore all of /data? If you did, you restored way more than just your apps and may have compatability issues.
Restoring /data IMHO is not a good idea after doing a firmware upgrade and flashing a corresponding rom.
A better strategy would be to backup just your apps and their data in TiBu and only restore those after you flashed the new firmware and the new rom.
Here's what I would do:
Factory reset in TWRP
Reflash the rom
Reinstall your apps (this time from scratch, next time you'll have a TiBu backup).
Hi all!
First off, I apologize in advance if this is a dumb question. But basically, I'm running a rooted One and I've been waiting for the official nightly builds for CM12, but now that they're finally here, I can't seem to flash them. I keep getting random errors when I try. I'm currently running on the latest 11s update that was OTA with TWRP, and I've unlocked my bootloader and everything. Anyone have any input? I've read in some places that you can't update to the CM12 nightly from 11s, and if that's the case, what's the best way to go from 11s to 11 without losing any data?
Thanks in advance!
There's no reason why you couldn't flash CM12 while coming from CM11 or CM11S. Are you making sure to wipe before flashing? I's very important to do that when switching ROMs, and even more so when you're flashing an entirely different Android version. You need to perform a full wipe (system, data, cache, and dalvik cache) before flashing the ROM, this will not affect your personal data on the internal storage (the virtual sd card). It will wipe your apps though obviously so just make sure you back them up with Titanium Backup beforehand, and you can restore them after the new ROM boots up and you install TiBu again (just don't backup/restore any system apps or settings, that'll cause problems).
timmaaa said:
There's no reason why you couldn't flash CM12 while coming from CM11 or CM11S. Are you making sure to wipe before flashing? I's very important to do that when switching ROMs, and even more so when you're flashing an entirely different Android version. You need to perform a full wipe (system, data, cache, and dalvik cache) before flashing the ROM, this will not affect your personal data on the internal storage (the virtual sd card). It will wipe your apps though obviously so just make sure you back them up with Titanium Backup beforehand, and you can restore them after the new ROM boots up and you install TiBu again (just don't backup/restore any system apps or settings, that'll cause problems).
Click to expand...
Click to collapse
Do I absolutely have to wipe? It says on the blog post from Cyanogen that there's no need to wipe. I'd like to circumvent that if possible, I just like having my sms logs and homescreen and such.
CaptainBlackbeard said:
Do I absolutely have to wipe? It says on the blog post from Cyanogen that there's no need to wipe. I'd like to circumvent that if possible, I just like having my sms logs and homescreen and such.
Click to expand...
Click to collapse
You need to wipe. Every time you flash a ROM you must wipe. There are plenty of apps that can backup your SMS for you, and your homescreen should be easy to set up again.
timmaaa said:
You need to wipe. Every time you flash a ROM you must wipe. There are plenty of apps that can backup your SMS for you, and your homescreen should be easy to set up again.
Click to expand...
Click to collapse
According to CM blog...
CM11>CM12 no need to wipe btw, unless you want to downgrade. But CM11s>CM12 DOES need to wipe. An S makes a huge difference.
soralz said:
According to CM blog...
CM11>CM12 no need to wipe btw, unless you want to downgrade. But CM11s>CM12 DOES need to wipe. An S makes a huge difference.
Click to expand...
Click to collapse
I'd wipe even going from CM11 to CM12.
Transmitted via Bacon
soralz said:
According to CM blog...
CM11>CM12 no need to wipe btw, unless you want to downgrade. But CM11s>CM12 DOES need to wipe. An S makes a huge difference.
Click to expand...
Click to collapse
Ah, gotcha. I guess as a workaround, is there any way I can go from CM11s to CM11 without wiping, and then from there from to CM12?
CaptainBlackbeard said:
Ah, gotcha. I guess as a workaround, is there any way I can go from CM11s to CM11 without wiping, and then from there from to CM12?
Click to expand...
Click to collapse
No, can't, unless you wait for CM12s. But I guess you can backup everything with Ti Backup then restore it back, No harm doing that though.
CaptainBlackbeard said:
Ah, gotcha. I guess as a workaround, is there any way I can go from CM11s to CM11 without wiping, and then from there from to CM12?
Click to expand...
Click to collapse
Why the big fear of wiping? Don't you want to do it the right way? Trying to cut corners like that is what causes bugs.
Transmitted via Bacon
dirty flash
i have dirtys flashing my self is there an app for dirty flashing, i have found app like cyandelta but isnt support many roms only CM12.
dd2 said:
i have dirtys flashing my self is there an app for dirty flashing, i have found app like cyandelta but isnt support many roms only CM12.
Click to expand...
Click to collapse
Why on earth would you want to use an app to flash a ROM? They're notoriously unreliable, and renowned for causing problems. Couple that with dirty flashing and you're asking for trouble. Just flash the way you're supposed to, in recovery.
Transmitted via Bacon
timmaaa said:
Why on earth would you want to use an app to flash a ROM? They're notoriously unreliable, and renowned for causing problems. Couple that with dirty flashing and you're asking for trouble. Just flash the way you're supposed to, in recovery.
Transmitted via Bacon
Click to expand...
Click to collapse
ok, thank you but can i dirty flash through recovery or is always better to fresh flash everytime.
dd2 said:
ok, thank you but can i dirty flash through recovery or is always better to fresh flash everytime.
Click to expand...
Click to collapse
If you're just updating the same ROM (flashing a newer build of the exact same ROM) you can usually dirty flash. Any other time you must clean flash.
timmaaa said:
Why the big fear of wiping? Don't you want to do it the right way? Trying to cut corners like that is what causes bugs.
Transmitted via Bacon
Click to expand...
Click to collapse
Well, I went ahead and did the wipe, but now I can't get SuperSU to work and I'm getting the "There is no SU binary installed, and Super SU cannot install it." error, and as a result Titanium isn't going to work correctly, and so now I get to redownload everything manually. So I guess that's why I don't like wiping.
CaptainBlackbeard said:
Well, I went ahead and did the wipe, but now I can't get SuperSU to work and I'm getting the "There is no SU binary installed, and Super SU cannot install it." error, and as a result Titanium isn't going to work correctly, and so now I get to redownload everything manually. So I guess that's why I don't like wiping.
Click to expand...
Click to collapse
Don't give up so easily, or maybe custom ROMs (and particularly early builds) aren't for you if you can't deal with small issues like this, it's part and parcel of all this.
You just need to work out SuperSU. Which version did you flash on which ROM?
Transmitted via Bacon
timmaaa said:
Don't give up so easily, or maybe custom ROMs (and particularly early builds) aren't for you if you can't deal with small issues like this, it's part and parcel of all this.
You just need to work out SuperSU. Which version did you flash on which ROM?
Transmitted via Bacon
Click to expand...
Click to collapse
I flashed the version the Oneplus One toolbox had and then updated it on the latest nightly.
CaptainBlackbeard said:
I flashed the version the Oneplus One toolbox had and then updated it on the latest nightly.
Click to expand...
Click to collapse
Well there's your problem. Stop using the toolbox, because it's most likely flashed an old and incompatible version of SuperSU. Just delete the toolbox altogether, it really isn't needed for this phone, plus it seriously stunts your learning.
You need to download the latest beta version and flash that instead.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Transmitted via Bacon
---------- Post added at 10:26 AM ---------- Previous post was at 10:10 AM ----------
Actually, come to think of it I don't think you need to flash SuperSU on CM12, I'm pretty sure they've built root access into Privacy Guard for CM12. So by flashing SuperSU you've probably borked it. Clean flash again but this time only flash ROM and gapps, then install Titanium and you should be prompted to grant root access when you open it.
Transmitted via Bacon
timmaaa said:
Well there's your problem. Stop using the toolbox, because it's most likely flashed an old and incompatible version of SuperSU. Just delete the toolbox altogether, it really isn't needed for this phone, plus it seriously stunts your learning.
You need to download the latest beta version and flash that instead.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Transmitted via Bacon
---------- Post added at 10:26 AM ---------- Previous post was at 10:10 AM ----------
Actually, come to think of it I don't think you need to flash SuperSU on CM12, I'm pretty sure they've built root access into Privacy Guard for CM12. So by flashing SuperSU you've probably borked it. Clean flash again but this time only flash ROM and gapps, then install Titanium and you should be prompted to grant root access when you open it.
Transmitted via Bacon
Click to expand...
Click to collapse
Alrighty, I'm trying the new version now. As for the installing Titanium before anything else, that's what I had done originally and it didn't work :/
CaptainBlackbeard said:
Alrighty, I'm trying the new version now. As for the installing Titanium before anything else, that's what I had done originally and it didn't work :/
Click to expand...
Click to collapse
Did you read the second part of my post??
timmaaa said:
Well there's your problem. Stop using the toolbox, because it's most likely flashed an old and incompatible version of SuperSU. Just delete the toolbox altogether, it really isn't needed for this phone, plus it seriously stunts your learning.
You need to download the latest beta version and flash that instead.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Transmitted via Bacon
---------- Post added at 10:26 AM ---------- Previous post was at 10:10 AM ----------
Actually, come to think of it I don't think you need to flash SuperSU on CM12, I'm pretty sure they've built root access into Privacy Guard for CM12. So by flashing SuperSU you've probably borked it. Clean flash again but this time only flash ROM and gapps, then install Titanium and you should be prompted to grant root access when you open it.
Transmitted via Bacon
Click to expand...
Click to collapse
The new version you linked worked!
Now I'm attempting a restore through TItanium. How long does it usually take? It's been sitting at 0% on the first app for a little while now.
Like everyone else I got the 5Q update the other day. Something in the update was causing my battery to drain much faster than before and since there are no new features in 5Q that I care about I tried rolling back to 44s.
I used the flash-able version of 44s from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Now I am basically stuck in a boot loop. Android boots up but I keep getting com.android. phone has stopped working over and over.
Anyone know how to fix this?
I didn't back anything up thinking this would be a quick roll back to 44S so I want to avoid having to do a full factory reset.
If worst comes to worst, can I use fastboot to reflash 44S without losing pics/texts/files ect?
Edit: I jumped back to 5Q and I no longer get the continuous errors. So I guess the question becomes now how should I go about rolling back to 44S and avoid getting the errors I was getting?
Thanks!
skyliner99 said:
Like everyone else I got the 5Q update the other day. Something in the update was causing my battery to drain much faster than before and since there are no new features in 5Q that I care about I tried rolling back to 44s.
I used the flash-able version of 44s from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Now I am basically stuck in a boot loop. Android boots up but I keep getting com.android. phone has stopped working over and over.
Anyone know how to fix this?
I didn't back anything up thinking this would be a quick roll back to 44S so I want to avoid having to do a full factory reset.
If worst comes to worst, can I use fastboot to reflash 44S without losing pics/texts/files ect?
Edit: I jumped back to 5Q and I no longer get the continuous errors. So I guess the question becomes now how should I go about rolling back to 44S and avoid getting the errors I was getting?
Thanks!
Click to expand...
Click to collapse
When you went back to 44S did you clean flash or dirty flash? The errors suggest that you dirty flashed, which you shouldn't do when going backwards. So what you need to do is perform a full wipe (system/data/cache/dalvik cache) and then flash 44S. Backup your user apps (not system apps or settings though) with Titanium Backup first, then you can restore them after 44S boots up again.
Transmitted via Bacon
The easiest method to go back would be to back up using Titanium Backup (And nandroid if you want to revert to old ROM if any problems occur) and then Wipe data/cache and flash the signed zip you downloaded. The issues must be with additions to dialer app I guess.
But just one question, have you checked why there is battery drain in 5Q? I would suggest you to install 'Better Battery Stats' or WakeLock Detector and find out what is draining your battery.
Usually this is the main culprit,http://forum.xda-developers.com/oneplus-one/general/guide-google-play-services-battery-t2832525/page3 .
You can also rely on Calkulin's Stock ROM's to enjoy stock+root. http://forum.xda-developers.com/oneplus-one/development/rom-calkulins-oneplus-one-v1-0-t2810365.
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
timmaaa said:
When you went back to 44S did you clean flash or dirty flash? The errors suggest that you dirty flashed, which you shouldn't do when going backwards. So what you need to do is perform a full wipe (system/data/cache/dalvik cache) and then flash 44S. Backup your user apps (not system apps or settings though) with Titanium Backup first, then you can restore them after 44S boots up again.
Transmitted via Bacon
Click to expand...
Click to collapse
@timmaaa, you really are the fastest to help anyone in distress. Thank you. :good::laugh:
tr.supradeep said:
The easiest method to go back would be to back up using Titanium Backup (And nandroid if you want to revert to old ROM if any problems occur) and then Wipe data/cache and flash the signed zip you downloaded. The issues must be with additions to dialer app I guess.
Click to expand...
Click to collapse
System must be wiped too. Otherwise there's really no point in wiping anything.
Transmitted via Bacon
You are right, I missed that part, though I do it always. Always while changing ROMs and Downgrading. Upgrading using dirty flash has never caused me a problem.
Edited the build.prop file by adding 1 line, restarted phone and now I keep getting System UI has stopped message.
Any way I can edit the file to fix my phone?
Have you tried to clear the cache in recovery? If that doesn't work, try a full factory reset.
If the phone is running a stock rom, try flashing just the system.img file in fastboot.
Before doing any of this, make sure you backup your data.
audit13 said:
Have you tried to clear the cache in recovery? If that doesn't work, try a full factory reset.
If the phone is running a stock rom, try flashing just the system.img file in fastboot.
Before doing any of this, make sure you backup your data.
Click to expand...
Click to collapse
Thank you, I ended up backing up the data and cache via USB, then did a flash of Cataclysm ROM. I'll let you know if it works.
Can I just restore the data ASAP after installation or do I need Google to finish restoring my backup first?
Edit: Well, restored data, stuck with the boot screen loop again, then goes to Android is upgrading... and shows it optimizing 10 apps, and back to the boot logo.
Did the phone boot without restoring data?
audit13 said:
Did the phone boot without restoring data?
Click to expand...
Click to collapse
No, I made sure it was completed.
Now Play Store keeps quitting when I try to install apps. I can only install specific ones.
I recommend flashing a stock rom to make sure there isn't a hardware problem. Don't restore anything until you are sure the phone works.
audit13 said:
I recommend flashing a stock rom to make sure there isn't a hardware problem. Don't restore anything until you are sure the phone works.
Click to expand...
Click to collapse
Alright, I was able to get all my apps installed besides United Airlines and can't update Chrome.
So the stock rom works fine?
audit13 said:
So the stock rom works fine?
Click to expand...
Click to collapse
Yes, thank you.
I don't think I want to do another custom ROM for now.
The stock rom is the best with the bloat taken out .I think the kernel can be improved though. I use EX
My XT1540/rooted/stock 6.0 ROM/ stock recovery now has an update available. I assume I can not accept this system update, even if I un-root my device. I do have a pre-rooted TWRP back up. I can reload that image, but my concern is the best way to get all my apps and data reloaded. I do have TB backups, but I thought that may not be a good option after system update. I am looking for advise how to proceed getting the latest system update and preserving all my current apps and data.
No offense, but did you Google it or search here? There are several tutorials in this device section and other similar Moto devices of the same generation that tell you different ways to do it...
Easy way... boot (not flash) TWPR, backup in TWRP, restore pre-root backup, accept OTA and allow it flash and fully boot, boot TWRP, flash your root of choice that you were using prior (Magisk or SuperSU), reboot and verify operation, then restore data partition backup you did prior to OTA, clear caches, and reboot.
This works 80% of the time... if your data partition is important then make an alternative backup.
acejavelin said:
No offense, but did you Google it or search here? There are several tutorials in this device section and other similar Moto devices of the same generation that tell you different ways to do it...
Easy way... boot (not flash) TWPR, backup in TWRP, restore pre-root backup, accept OTA and allow it flash and fully boot, boot TWRP, flash your root of choice that you were using prior (Magisk or SuperSU), reboot and verify operation, then restore data partition backup you did prior to OTA, clear caches, and reboot.
This works 80% of the time... if your data partition is important then make an alternative backup.
Click to expand...
Click to collapse
Thanks. I have read conflicting information on the use of Titanium Backup, and that was my main reason for my post. My understanding of your reply is that TB would not be a recommended choice to restore apps&data (using either update.zip or batch mode) and that I have an 80% chance of restoring user apps and data by flashing the /data partition from my pre-OTA TWRP backup. And yes, I will make a pre-rooted backup prior to rooting or restoring apps.
I never heard of Magisk and will read more. In the mean time I will stick with SuperSU unless there is strong advise to go with Magisk.
MrTooPhone said:
Thanks. I have read conflicting information on the use of Titanium Backup, and that was my main reason for my post. My understanding of your reply is that TB would not be a recommended choice to restore apps&data (using either update.zip or batch mode) and that I have an 80% chance of restoring user apps and data by flashing the /data partition from my pre-OTA TWRP backup. And yes, I will make a pre-rooted backup prior to rooting or restoring apps.
I never heard of Magisk and will read more. In the mean time I will stick with SuperSU unless there is strong advise to go with Magisk.
Click to expand...
Click to collapse
I dislike TiBU... It is best to reinstall from scratch each time if possible, if not, this is a simple security update to TWRP should suffice.
Magisk is good, and it appears to be the root method most ROMs are going to because with Magisk Hide and a few tweaks that are built in, the device can still pass SafetyNet API checks, and there is no special process for systemless installing (it is the only way it can be done with Magisk). But if you are on SuperSU now and want to restore the data partition, do NOT switch that way... Get clean ROM and flash Magisk then install Magisk Manager. It has it's own community here: https://forum.xda-developers.com/apps/magisk
I am not saying Magisk is superior, but it is quite versatile and most ROMs seem to be switching to it so devices can pass SafetyNet checks.
I was also thinking this would be simple. Pleasant surprise after almost a year and a half to get a security update. So I uninstalled SuperSU (Tried Full Unroot option & it failed, so then just uninstalled the app.....Looks like I may still be rooted), re-installed the stock recovery, and with absolutely no other modifications to this phone, performed the update. So it failed. I thought I was able to do this on my Nexus 4, but that was a while back, and I always did it with a file, not OTA; maybe that was just OS update, who knows. I was just looking for some security peace of mind while waiting for Nougat to become a bit more stable. If I am going to have to go through hoops to do this, then I guess I will just wait; not going to go through this twice. Besides, will it be another year for the next security update; heck, they are already 1 or 2 months behind already.
The answer is what others said, plus you can try flashing OTA updates with flashfire, and don't choose to wipe data.
Rohi09 said:
The answer is what others said, plus you can try flashing OTA updates with flashfire, and don't choose to wipe data.
Click to expand...
Click to collapse
Oh well. On a side note, always grateful for making Nandroid backups before I start playing around with anything though. Things were acting up after haphazardly trying various SuperSU options, so I had to do a restore.
These constant OTA update messages every few minutes that I have to keep canceling are brutal! I might have to install an app to kill them.
Rohi09 said:
The answer is what others said, plus you can try flashing OTA updates with flashfire, and don't choose to wipe data.
Click to expand...
Click to collapse
Are you saying OTA updates can be flashed successfully without unrooting.
MrTooPhone said:
Are you saying OTA updates can be flashed successfully without unrooting.
Click to expand...
Click to collapse
that's the idea, I have never tried it on moto g 2015 though. As far as I know every root solution had its own Uninstaller. which root interface do you use? magisk or supersu?
Rohi09 said:
that's the idea, I have never tried it on moto g 2015 though. As far as I know every root solution had its own Uninstaller. which root interface do you use? magisk or supersu?
Click to expand...
Click to collapse
I have SuperSU. It would be great to flash an OTA over my current system, but I have heard many reports including @pjc123 above where it did not work.
All my searches resulted in suggestions in going back to stock, accept OTA, then use TB or some other similar program to restore saved apps & data. Tomorrow I will try @acejavelin 's above suggested method of flashing the /data partition. If that does not work, I will try TB. I will report my progress.
MrTooPhone said:
I have SuperSU. It would be great to flash an OTA over my current system, but I have heard many reports including @pjc123 above where it did not work.
All my searches resulted in suggestions in going back to stock, accept OTA, then use TB or some other similar program to restore saved apps & data. Tomorrow I will try @acejavelin 's above suggested method of flashing the /data partition. If that does not work, I will try TB. I will report my progress.
Click to expand...
Click to collapse
you can flash unsu zip or magisk Uninstaller and try to install ota via flashfire, won't hurt trying, might save you some time.
acejavelin said:
No offense, but did you Google it or search here? There are several tutorials in this device section and other similar Moto devices of the same generation that tell you different ways to do it...
Easy way... boot (not flash) TWPR, backup in TWRP, restore pre-root backup, accept OTA and allow it flash and fully boot, boot TWRP, flash your root of choice that you were using prior (Magisk or SuperSU), reboot and verify operation, then restore data partition backup you did prior to OTA, clear caches, and reboot.
This works 80% of the time... if your data partition is important then make an alternative backup.
Click to expand...
Click to collapse
Another dumb question, I am in the process of installing OTA. When I loaded the pre-root rom, I did not see any option to clear clear caches. I did see a wipe data and cache option which I understand to be a factory reset. I know I have seen it before but can't find it, so where do I clear cache after restoring data partition?
MrTooPhone said:
Another dumb question, I am in the process of installing OTA. When I loaded the pre-root rom, I did not see any option to clear clear caches. I did see a wipe data and cache option which I understand to be a factory reset. I know I have seen it before but can't find it, so where do I clear cache after restoring data partition?
Click to expand...
Click to collapse
Another simple Google question...
Open TWRP, go to Wipes - Advanced, and select Cache and Dalvik cache (a misnomer today, it should be called ART cache) and swipe to wipe, then reboot.
Thanks to @acejavelin recommendations, I have successfully applied the latest system update to my XT1540. My steps were as follows:
Booted to TWRP (3.0.2-r5.img)
restored original pre-rooted ROM
rebooted, accepted system updates
backed up new pre-rooted ROM
installed SuperSU 2.62-3, rebooted
updated SuperSU to 2.79 via Playstore
restored /data partition from last saved rooted ROM
wiped Dalvik/ART Cache
Reboot system
took a while, a couple of minutes on “Hand stitched by Peter Crawly”, several minutes optimizing apps. The phone booted succesfully then I got an error message the update failed (which I hit OK) But looking at about phone, latest security patch is listed. Phone looks configured (apps, data, configuration) exactly as it was prior to the update.
Rebooted phone, all still seems fine.
Hello, how do I restore original pre-rooted ROM? When I made the backup I got a folder with 6 files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win
system.ext4.win.md5
system.info
None of them seems to be the .img file
bradmoss said:
Hello, how do I restore original pre-rooted ROM? When I made the backup I got a folder with 6 files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win
system.ext4.win.md5
system.info
None of them seems to be the .img file
Click to expand...
Click to collapse
Your are not going to see an img file. Once booted into TWRP, select Restore, navigate and select your original ROM. Those files you have listed are within the restoration directory that you select with TWRP. Just select the directory with TWRP.
Bad news, I could restore pre-TRWP image using that folder and aplied the update.
But now I am in a loop, it tries to install (again) the update and then boots to TWRP
Is there any way out of this loop?
Thanks!
no idea? Am I the sad owner of a bricked phone?
bradmoss said:
no idea? Am I the sad owner of a bricked phone?
Click to expand...
Click to collapse
You could try a factory reset if you're not worried about losing your data. A factory reset solves most of the problems, though I'm a little doubtful because a factory reset won't uninstall the new update (given that it installed in the first place).
bradmoss said:
Bad news, I could restore pre-TRWP image using that folder and aplied the update.
But now I am in a loop, it tries to install (again) the update and then boots to TWRP
Is there any way out of this loop?
Thanks!
Click to expand...
Click to collapse
If it boots to TWRP, sounds like you didn't have a clean pre-root ROM as you did not have stock recovery. Did you try deleting Dalvik and ART cache?