Related
Hi all,
I've recently tried to update the Matr1x kernel to the 9.0 CFS version on my already installed NSCollab 1.0.50 mod. Unfortunately, this didn't seem to go so well, because my Nexus S (i9023) entered an infinite reboot loop. I was a bit surprised since a lot of people seemed to have no problems with this kernel, and even though I'm new to this stuff, I tried to follow all the guides & tutorials around.
Anyways, here's what I did:
- I downloaded the kernel on my phone from this forum;
- I used ROM Manager, selecting the "Install ROM from SD Card" option;
- I let the "Wipe Dalvik Cache" option enabled.
Once I experienced the reboots, I dropped into recovery and tried to re-wipe the cache & the dalvik cache several times, with no luck. I then proceeded to restore the backup I made before doing this...
Did I do something wrong or stupid?
try flashing the rom(gapps if needed) then the kernel, then reboot.
simms22 said:
try flashing the rom(gapps if needed) then the kernel, then reboot.
Click to expand...
Click to collapse
Does this mean I have to wipe my data again?
I've never used ROM Manager to flash anything (I prefer to be hands-on and do it myself), but if you told ROM Manager to install a ROM from zip and fed it a kernel file, I can't see how that can possibly have a positive outcome hahaha.
Go into CWM, do a factory reset/full wipe and reinstall NSCollab 1.0.50. Once you've installed that, you can immediately install a custom kernel. Reboot, wait for it (the first boot always takes longer) and you should be fine.
Greetz
PS: Remember to always make backups with Titanium Backup, or even Nandroid backups if you're not sure about the actions you're about to do.
mux_ said:
Does this mean I have to wipe my data again?
Click to expand...
Click to collapse
no. go to recovery(dont use rom manager), flash your rom(and gapps), flash the kernel, reboot.
Well, since my system was still fully functional (as I said, I had done a backup from ROM Manager previously and restored it), I tried the manual method first; that is dropping into recovery, wiping dalvik cache, and using 'install zip from sdcard'.
Everything went just fine, and I'm running the Matr1x 9.0 CFS kernel without any issue for now!
Thanks a lot for the help.
Hi all,
I just discovered CleanROM yesterday, and I'm trying to throw it on my S3 now. Everything installs fine, I go through all of the choices, and at the end TWRP pops up and tells my that it ppears that mt root is "broken" and asks if I want to repair permissions. I tell it 'yes', it seems to do its job, and I reboot.
After that, I have waited 20 minutes with no boot. It starts the boot animation, which is a 4-color 'X' on the screen, and nothing more. I have looked around, and people say that on first boot, there are sometimes orphan files that need to be resolved, but they said maybe 6 or 7 minutes, not 20.
Some background:
I probably rooted about a month ago in order to install CyanogenMod
I am not sure what method I used to root the phone with, mostly because I had issues from the beginning(Apparently not unheard of with the S3), but I know that I am rooted.
My bootloader is also unlocked, AFAIK, since I wouldn't have been able to instal CM10 otherwise.
I am using TWRP 2.4 as my recovery and it seems to be working wonderfully.
Process:
I boot into recovery
Choose 'Install'
Point to my download of CleanROM and follow all prompts, choosing launcher, file manager, etc.
Tell it to wipe data and cache
After the install, there is the message from TWRP telling me that root is "broken"(I think that's the term it uses), and asks me if I want to repair permissions, and I of course repair them.
After rebooting is when nothing happens. I finally pull the battery and either try again, or restre my phone so I can use it. I'm probably 0/4 at this point, I downloaded the ROM from the Dev's site, and have no problems, since it gives no errors during install.
So I guess I have three questions:
1. Can I re-root my device? Will this help, or could it frak things up worse?
2. Is there a way to fix those file permissions for good? The fix doesn't seem to be holding when I choose "repair" in TWRP.
3. Is this a ROM issue instead, and should I downgrade a version? Also, is anyone else seeing this?
Thanks in advance for any help guys! :good:
Mikey1969 said:
Hi all,
Process:
I boot into recovery
Choose 'Install'
Point to my download of CleanROM and follow all prompts, choosing launcher, file manager, etc.
Tell it to wipe data and cache
After the install, there is the message from TWRP telling me that root is "broken"(I think that's the term it uses), and asks me if I want to repair permissions, and I of course repair them.
After rebooting is when nothing happens. I finally pull the battery and either try again, or restre my phone so I can use it. I'm probably 0/4 at this point, I downloaded the ROM from the Dev's site, and have no problems, since it gives no errors during install.
So I guess I have three questions:
1. Can I re-root my device? Will this help, or could it frak things up worse?
2. Is there a way to fix those file permissions for good? The fix doesn't seem to be holding when I choose "repair" in TWRP.
3. Is this a ROM issue instead, and should I downgrade a version? Also, is anyone else seeing this?
Thanks in advance for any help guys! :good:
Click to expand...
Click to collapse
I think you are referring to the /root partition, not actually being rooted.
The problem is your order of operations. You are wiping the ROM after you install! You are supposed to wipe data/cache BEFORE you install the ROM.
This is not a ROM issue, I just installed CleanROM 6r2 and it is fast as heck and worked fine. I suggest you boot into twrp and perform the install correctly.
shutin said:
I think you are referring to the /root partition, not actually being rooted.
The problem is your order of operations. You are wiping the ROM after you install! You are supposed to wipe data/cache BEFORE you install the ROM.
This is not a ROM issue, I just installed CleanROM 6r2 and it is fast as heck and worked fine. I suggest you boot into twrp and perform the install correctly.
Click to expand...
Click to collapse
I wondered about that, but using TWRP in the 'Install' mode, it doesn't prompt for wipe until after(Unless I'm doing something wrong there). Just to be clear, you're just suggesting that I manually wipe first, then let TWRP and CleanROM take me through the process after that, right?
Thanks
Boot into twrp.
Hit the wipe menu.
Wipe the top four boxes
(Wipe cache
Wipe dalvik cache
Factory reset.
Wipe system.)
Install ROM
Should boot within 2 minutes tops.
Sent from that young galaxy.
God bless the American People.
barrackOBAMA said:
Boot into twrp.
Hit the wipe menu.
Wipe the top four boxes
(Wipe cache
Wipe dalvik cache
Factory reset.
Wipe system.)
Install ROM
Should boot within 2 minutes tops.
Sent from that young galaxy.
God bless the American People.
Click to expand...
Click to collapse
That did it. Thanks!!
You mind hitting the thanks Button.
I'd greatly appreciate it
Sent from that young galaxy.
God bless the American People.
There ya go... Sorry, didn't even know the thing existed until yesterday.
Hello,
my tf700 doesn't finish the boot after I've installed CM.
Before flashing a new rom I've tried to make a system back-up from GooManager.
I don't know if the back-up is fully functional because in the "Breaking back-up in multiple archives" it has remained stuck at 100% (or complete progress bar) for like an hour.
After an hour or so I've interrupted the back-up process and entered the TWRP Recovery v2.5 (which I'm still able to access at the moment) and tried to flash a ROM downloaded by GooManager (cm-10.0.0-tf700t.zip). I've wiped the Dalvik cache and Cache in the process.
The flash seemed to be successful but the reboot doesn't finish, even though I've let it for two hours or so.
After that I've reentered the TWRP and tried a different rom cm-10.1-20130513-NIGHTLY-tf700t.zip, but with similar result, after installation it doesn't finish the boot.
I've reentered the TWRP and tried restoring the back-up. It did restored the system, passed the "configuring application" stage and gave the message "Finishing boot" and nothing afterwards, it just stuck in the process.
Right now I'm still able to enter TWRP, and navigate through the folders on the tablet, but I don't have a functional rom.
Can you please help me with some advices?
Thank you.
Which ROM did you have before, and which bootloader version?
_that said:
Which ROM did you have before, and which bootloader version?
Click to expand...
Click to collapse
Before that I had the stock ROM with the latest OTA firmware from Asus.
I don't know what was the initial version of the bootloader.
I've unlocked the device using Asus apk
I've pushed the TWRP on the tablet using the TF700T-ADB- Tool v3
I've granted super user rights from TWRP, I think using SuperUser application.
Ive installed from market GooManager and after that I've done what I've described in the previous message.
Thanks for your prompt answer.
Maybe CM is confused by existing data - did you wipe data (factory reset) as written in the CM instructions?
_that said:
Maybe CM is confused by existing data - did you wipe data (factory reset) as written in the CM instructions?
Click to expand...
Click to collapse
No, I didn't. I've just wiped the Dalvik cache and Cache.
If I do wipe data, I will still have user data, like downloaded ZIP ROMs or GAPPS zip?
I mean, at the moment I'm still able to try different ROMs and kind of operate the tablet. If I do wipe the data and is something wrong with the flash will I be able the try something else? Before I wipe existing data should I take other precautions?
Mihai_Preda said:
No, I didn't. I've just wiped the Dalvik cache and Cache.
If I do wipe data, I will still have user data, like downloaded ZIP ROMs or GAPPS zip?
I mean, at the moment I'm still able to try different ROMs and kind of operate the tablet. If I do wipe the data and is something wrong with the flash will I be able the try something else? Before I wipe existing data should I take other precautions?
Click to expand...
Click to collapse
From what I've read (but never tried myself), a "Factory Reset" is supposed to delete all your apps, app data and system-specific data, but not the contents of your internal emulated SD card. Your ROM and recovery are definitely not affected. But I'd wait until someone else can confirm.
It seems strange that the back-up isn't fully working either, it gets stuck after "Finishing boot".
I've noticed somtheing while flashing the two CM ROMs. On the instalation, of each of the two, it was a message that the MD5 is being checked, and after that that MD5 is missing and the check is being skipped. The instalation did continued and the message "Instalation succesful" was given.
But I don't know if it's alright not findind the MD5.
_that said:
From what I've read (but never tried myself), a "Factory Reset" is supposed to delete all your apps, app data and system-specific data, but not the contents of your internal emulated SD card. Your ROM and recovery are definitely not affected. But I'd wait until someone else can confirm.
Click to expand...
Click to collapse
I've checked on other sources and the wipe data seems to leave intact the user data.
But I'm still wondering at what state the tablet will be reseted since I've tried flashing to different ROMs and the back-up restore didn't work quite properly.
The last functioning ROM is still available from other means that restore back-up (which doesn't work) even though I've tried flashing new ROMs over it?
Mihai_Preda said:
On the instalation, of each of the two, it was a message that the MD5 is being checked, and after that that MD5 is missing and the check is being skipped. The instalation did continued and the message "Instalation succesful" was given.
Click to expand...
Click to collapse
The missing MD5 file is not a problem. If it says "installation successful", you can assume that it is.
Mihai_Preda said:
I've checked on other sources and the wipe data seems to leave intact the user data.
But I'm still wondering at what state the tablet will be reseted since I've tried flashing to different ROMs and the back-up restore didn't work quite properly.
The last functioning ROM is still available from other means that restore back-up (which doesn't work) even though I've tried flashing new ROMs over it?
Click to expand...
Click to collapse
Your backups not working is somewhat strange, but that's another area where I have very limited experience.
You said you were on the "latest OTA" stock ROM. Was that 10.4.4.25 (Android 4.1) or 10.6.1.14.4 (Android 4.2)? Also check the bootloader version - boot into the bootloader menu with holding volume-left, then read the tiny text near the top of the screen. It should contain the build number of your bootloader, which is identical to the build number of the stock ROM until you flash one of them separately.
_that said:
You said you were on the "latest OTA" stock ROM. Was that 10.4.4.25 (Android 4.1) or 10.6.1.14.4 (Android 4.2)? Also check the bootloader version - boot into the bootloader menu with holding volume-left, then read the tiny text near the top of the screen. It should contain the build number of your bootloader, which is identical to the build number of the stock ROM until you flash one of them separately.
Click to expand...
Click to collapse
It's Android 4.2.1: "Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03"
Right now the tablet is left with the attempted back-up recovery. Should I enter TWRP and do the wipe data or wipe data from the bootloader menu?
Or is something else that I should do first?
Ok, I did wipe the data, and even though it erased the user data too (media, docs, zip files etc) it restore the tablet to cyanogen mode not the original stock ROM. It finished the boot restore my gmail account. SuperUser is updated. And it seems the overall responsiveness is better.
Thank you for your time and advice!
Mihai_Preda said:
It's Android 4.2.1: "Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03"
Right now the tablet is left with the attempted back-up recovery. Should I enter TWRP and do the wipe data or wipe data from the bootloader menu?
Or is something else that I should do first?
Click to expand...
Click to collapse
OK, your bootloader is the latest one, and it works with Android 4.1 and 4.2 ROMs. There have been several reports of unrecoverable bricks after using "wipe data" from the bootloader menu with a broken or incompatible recovery - so even if your recovery works fine, I would not recommend to take any unnecessary risk.
If you have any important data on your device it would be a good idea to store a backup on an external microSD card, just in case you do wipe all data by accident or something unexpected happens.
_that said:
OK, your bootloader is the latest one, and it works with Android 4.1 and 4.2 ROMs. There have been several reports of unrecoverable bricks after using "wipe data" from the bootloader menu with a broken or incompatible recovery - so even if your recovery works fine, I would not recommend to take any unnecessary risk.
If you have any important data on your device it would be a good idea to store a backup on an external microSD card, just in case you do wipe all data by accident or something unexpected happens.
Click to expand...
Click to collapse
I'm surprised that after wipe data procedure it restored the system to a cyanogen mode not the original rom. I'm surprised by this because the last functional ROM was the stock one and because after flashing the last zip with CM ROM I've tried to restore the back-up ROM. Even though it didn't finish the boot, this back-up seemed to be installed over the previous CM ROMs. I'm not sure what happened, why I do have a CM ROM functioning, even though I did tried to install it I don't know why it managed to be installed.
If you have little more time and you know what happened here please let me know.
Thank you again!
Mihai_Preda said:
I'm surprised that after wipe data procedure it restored the system to a cyanogen mode not the original rom. I'm surprised by this because the last functional ROM was the stock one and because after flashing the last zip with CM ROM I've tried to restore the back-up ROM. Even though it didn't finish the boot, this back-up seemed to be installed over the previous CM ROMs. I'm not sure what happened, why I do have a CM ROM functioning, even though I did tried to install it I don't know why it managed to be installed.
Click to expand...
Click to collapse
The ROM and your data are completely separate. If you install a ROM and it says "install successful", the ROM is installed. "Wipe data" does not touch the ROM. However your data can prevent the ROM from starting up correctly. Apparently the restore fixed something in your data partition so that the last ROM that you installed can now boot.
_that said:
The ROM and your data are completely separate. If you install a ROM and it says "install successful", the ROM is installed. "Wipe data" does not touch the ROM. However your data can prevent the ROM from starting up correctly. Apparently the restore fixed something in your data partition so that the last ROM that you installed can now boot.
Click to expand...
Click to collapse
That means the TWRP didn't actually restore the ROM from back-up even if it did say the restore was successful...The last installed ROM was a CM one.
Thanks for the help!
HI i installed fulmics rom and it did not work , now it will not allow me to install a rom because twrp says "done" almost instantly , how can i delete fulmics. I have 855 international version. THanks
stupify007 said:
HI i installed fulmics rom and it did not work , now it will not allow me to install a rom because twrp says "done" almost instantly , how can i delete fulmics. I have 855 international version. THanks
Click to expand...
Click to collapse
When you boot to TWRP, choose the "Wipe" option, on the next screen, choose "Advanced Wipe", then on the next screen, choose "system" and "data" partitions(do not choose any of the other partitions). Then slide the slider at the bottom to wipe, then tap the home button in TWRP and choose the "Install" option and flash your RIM like you normally would, then after it flashes, wipe cache and Dalvik/ART cache, after it wipes the caches, select reboot and you're done.
Sent from my SCH-I535 using Tapatalk
Didn't Work
hi, that didn't work, it says it has done but then it boots straight back up into fulmics. Any other ideas.
Droidriven said:
When you boot to TWRP, choose the "Wipe" option, on the next screen, choose "Advanced Wipe", then on the next screen, choose "system" and "data" partitions(do not choose any of the other partitions). Then slide the slider at the bottom to wipe, then tap the home button in TWRP and choose the "Install" option and flash your RIM like you normally would, then after it flashes, wipe cache and Dalvik/ART cache, after it wipes the caches, select reboot and you're done.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
hi, that didn't work, it says it has done but then it boots straight back up into fulmics. Any other ideas.
stupify007 said:
hi, that didn't work, it says it has done but then it boots straight back up into fulmics. Any other ideas.
Click to expand...
Click to collapse
There is probably something wrong with your recovery. They flashing an older or newer version of TWRP for your model number, then try flashing a different ROM.
If your recovery was working correctly then the steps to wipe that I told you about should have wiped your system partition, if it had done that properly then you wouldn't have anything to boot to at this point if your new ROM didn't flash. Since you booted to the ROM you tried to wipe then it didn't wipe.
Also, make sure that you still have root before you flash another recovery, use the root checker app, if you don't have root, try flashing SuperSU.zip in TWRP, then try flashing the new ROM.
Droidriven said:
There is probably something wrong with your recovery. They flashing an older or newer version of TWRP for your model number, then try flashing a different ROM.
If your recovery was working correctly then the steps to wipe that I told you about should have wiped your system partition, if it had done that properly then you wouldn't have anything to boot to at this point if your new ROM didn't flash. Since you booted to the ROM you tried to wipe then it didn't wipe.
Also, make sure that you still have root before you flash another recovery, use the root checker app, if you don't have root, try flashing SuperSU.zip in TWRP, then try flashing the new ROM.
Click to expand...
Click to collapse
I never faced this issue before, I had installed roms before and was able to flash a new rom , so could the recovery really be the issue.
stupify007 said:
I never faced this issue before, I had installed roms before and was able to flash a new rom , so could the recovery really be the issue.
Click to expand...
Click to collapse
Just try another recovery and eliminate that possibility, you're not gonna cause any issues with the new recovery unless you use the wrong one.
Sent from my SCH-I535 using Tapatalk
stupify007 said:
I never faced this issue before, I had installed roms before and was able to flash a new rom , so could the recovery really be the issue.
Click to expand...
Click to collapse
Try advanced wipe including everything. then flash stock rom or any official ones. If you got qualcomm device then use QFIL or Qualcomm Flash Tool
hi i just tried that and it didn't do anything, once again it says done but it didn't do anything, I think it may be the recovery as suggested by Droidriven. I am going to try and flash a different version of TWRP or maybe clockworkmod recovery , I will keep you updated. But do you guys have any suggestions to what may have caused this, Fulmics never worked for me.
Droidriven said:
Just try another recovery and eliminate that possibility, you're not gonna cause any issues with the new recovery unless you use the wrong one.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
[[QUOTING MY POST SO YOU CAN SEE]]
.hi i just tried that and it didn't do anything, once again it says done but it didn't do anything, I think it may be the recovery as suggested by Droidriven. I am going to try and flash a different version of TWRP or maybe clockworkmod recovery , I will keep you updated. But do you guys have any suggestions to what may have caused this, Fulmics never worked for me.
Also guys , i installed TWRP using my OS and now it doesnt work so what is the alternative, I have all pc drivers?
stupify007 said:
Also guys , i installed TWRP using my OS and now it doesnt work so what is the alternative, I have all pc drivers?
Click to expand...
Click to collapse
It sounds to me like you flashed something that was not made for your model number. Find the correct stock firmware and flash that, then start over and find something different for your device this time.
Sent from my SCH-I535 using Tapatalk
quick story. I reinstalled of the same version (2.8) and the problem is still here, I am going to try to install a different version.
Sorry to keep posting but I tried a factory reset using TWRP and it says failed. Could that mean something.
Actually guys, IT says failed underneath for everything but in the console it shows no signs of failure.
SOrry guys for being a noob, this can now be shut down as i have fixed the problem by unchecking simulate actions.
stupify007 said:
SOrry guys for being a noob, this can now be shut down as i have fixed the problem by unchecking simulate actions.
Click to expand...
Click to collapse
How in the world did that setting get changed, it should have been set to what you needed by default.
Sent from my SCH-I535 using Tapatalk
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?