I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again. I've tried reflashing PA, but it gave me a "E: failed to set up expected mounts for install; aborting".
OMGMatrix said:
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again.
Click to expand...
Click to collapse
I don't think the recovery was "restored" / flashed to the boot partition but maybe try just in case. Flash the boot.img for Viper ROM and see if it stops the bootloop. After that you can make a clean wipe and install the ROM again, not restore but INSTALL. You surely have the ROM's .zip still?
Reason I suggested boot.img: i cannot get anything to restore with the h3g__001 backups keep getting recovery.emmc.win' is larger than target device '/dev/block/mmcblk0p42 error
mmcblk0p42 is the boot partition, so I don't know why TWRP tried to restore/flash a recovery to boot partition. He solved it by manually flashing boot.img after renaming.
if anyone gets this error heres how i solved it.change the boot.emmc.win to boot.img and it let me restore
Just a suggestion...
So this has been thoroughly confusing.
It seems that I had to clear the cache several times in PhilZ in order to resolve the first error. I tried to flash the original rom zip for Viper, but it still failed even though the "E: can't mount" messages weren't showing any more. However, I was able to re-flash the rom zip for PA, and upon booting, I found that Many of my apps were still there dispite the fact that they should have not been.
I then was able to reboot to recovery and flash the zip for Viper.
No clue what happened, but at least if anyone else has this problem, they'll be able to see how I fixed it
OMGMatrix said:
So this has been thoroughly confusing.
It seems that I had to clear the cache several times in PhilZ in order to resolve the first error. I tried to flash the original rom zip for Viper, but it still failed even though the "E: can't mount" messages weren't showing any more. However, I was able to re-flash the rom zip for PA, and upon booting, I found that Many of my apps were still there dispite the fact that they should have not been.
I then was able to reboot to recovery and flash the zip for Viper.
No clue what happened, but at least if anyone else has this problem, they'll be able to see how I fixed it
Click to expand...
Click to collapse
The apps will be there if you restored without making changes to the data partition which contains the your userdata. I've converted and changed over from International to Developer edition quite a few times now and not once in all those times did I lose my data, I just never restored the data partition.
Not sure if you have to actively choose whether to flash over data or not, I'm not that big into custom ROMs, only tried Viper ROM and even then I kept my original data.
OMGMatrix said:
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again. I've tried reflashing PA, but it gave me a "E: failed to set up expected mounts for install; aborting".
Click to expand...
Click to collapse
Had that exact same issue as you. What version of twrp were you running when the issue started? Also, did you make any firmware upgrades or downgrades recently?
I ended up just running an RUU and starting over. I was able to adb pull all my files from internal sd card before i ran it.
mattprice86 said:
Had that exact same issue as you. What version of twrp were you running when the issue started? Also, did you make any firmware upgrades or downgrades recently?
Click to expand...
Click to collapse
I was using a version of TWRP that had been bundled with a previous version of Viper that was supposed to have been newer, but was actually 2.7.0.1. I updated to the newest (2.8.0.3) from the TWRP site through fastboot, but that didn't change anything. I had somewhat recently updated to the 3.xxx.xxx.7 firmware, but had flashed other roms since that without issue.
BerndM14 said:
The apps will be there if you restored without making changes to the data partition which contains the your userdata. I've converted and changed over from International to Developer edition quite a few times now and not once in all those times did I lose my data, I just never restored the data partition.
Click to expand...
Click to collapse
I did a factory reset (cache, Dalvik, data) before attempting the nandroid restore.
It looks like TWRP failed to actually do the reset in the first place, which caused it to get hung up thinking that the storage was actually being used.
OMGMatrix said:
I did a factory reset (cache, Dalvik, data) before attempting the nandroid restore.
It looks like TWRP failed to actually do the reset in the first place, which caused it to get hung up thinking that the storage was actually being used.
Click to expand...
Click to collapse
Doesn't matter mate, if you restore the data partition the backup that you made of data gets restored, period. It'll be another issue worth interest if you deselected "data" while doing the restore. As you clearly stated yourself, you did a factory reset(wipe all) BEFORE you did the nandroid restore(In which case you might have restored "Data" as well), in that case the factory reset doesn't matter at all. If you did it after you restored then, again, it's something different.
BerndM14 said:
Doesn't matter mate, if you restore the data partition the backup that you made of data gets restored, period. It'll be another issue worth interest if you deselected "data" while doing the restore. As you clearly stated yourself, you did a factory reset(wipe all) BEFORE you did the nandroid restore(In which case you might have restored "Data" as well), in that case the factory reset doesn't matter at all. If you did it after you restored then, again, it's something different.
Click to expand...
Click to collapse
I don't think you understand.
The restore never happened. It rebooted before anything happened when I told it to restore. Nothing got restored.
Related
Every time I take a nandroid backup in TWRP and boot the phone up, I seem to get boot loops.
Yesterday
------------------
I was running HTC's factory 4.4.2 firmware that came with my phone when I bought it. It was rooted and I was using XPosed. I wanted to upgrade to 4.4.3 via OTA, but I wanted a roll-back method. So I took a nandroid, all is well.
I flash stock recovery and take the OTA. All is well. I re-root, install xposed, tinker with some modules and then the phone reboots itself.
I did the upgrade from 4.4.2 to 4.4.3 again after restoring my nandroid backup. All is well. I decide not to tamper with root stuff, but the su binary has been flashed. I restored a majority of my apps and app data by using titanium backup to load application data from my TWRP backup. Everything is STILL fine.
Today
------------------
My TWRP backup of 4.4.2 was at work so I had to wait until I got back to move the backup back onto my phone. So here I am. I decide to do the following:
1. I shut my perfectly working 4.4.3 ROM down so I can take a nandroid before I load the 4.4.2 nandroid and try another fresh update
2. I make the nandroid backup and boot the OS back up so I can copy the TWRP folder over to my computer
3. Phone boot loops again.
What is causing this? I've tried a bunch of things like fixing permissions from TWRP, clearing the dalvik and cache. I tried sending "adb logcat" to a file on my computer to examine the output but nothing sticks out before it reboots.
Only fix I know is to factory reset and start the long process all over again.
M8_UL
HBOOT-3.18.0.0000
RADIO-1.19.21331147A1.09G
Carrier: Wind Mobile (Canada)
Have you tried fastboot erase cache, and flash TWRP again?
No I have not. Once I try that, what point will I be at? Will I be able to boot into my OS or will I need to restore my backup again?
What does fastboot erase cache do? Is it the same cache I can clear from TWRP?
One thing I just remembered... I'm using TWRP 2.7.1.0, where prior to upgrading I was using TWRP 2.7.0.2 from Hasoon2000's toolkit. Not sure if this matters or not yet.
ninjai117 said:
No I have not. Once I try that, what point will I be at? Will I be able to boot into my OS or will I need to restore my backup again?
Click to expand...
Click to collapse
The point is to re-install TWRP. As I don't have issues with the phone rebooting after doing a nandroid, I'm just guessing that maybe its just a bad TWRP install.
For that matter, try to download the TWRP file again, to make sure the file isn't corrupt.
You won't be able to boot into the OS just from what I suggested, you will still need to restore the nandroid.
erase cache is suggested as sometimes folks have trouble re-installing TWRP, and erase cache will often solve this. I always install TWRP by fastboot, so fastboot erase cache just takes 2 more seconds, which is time well spent to reduce headaches.
redpoint73 said:
The point is to re-install TWRP. As I don't have issues with the phone rebooting after doing a nandroid, I'm just guessing that maybe its just a bad TWRP install.
For that matter, try to download the TWRP file again, to make sure the file isn't corrupt.
You won't be able to boot into the OS just from what I suggested, you will still need to restore the nandroid.
erase cache is suggested as sometimes folks have trouble re-installing TWRP, and erase cache will often solve this. I always install TWRP by fastboot, so fastboot erase cache just takes 2 more seconds, which is time well spent to reduce headaches.
Click to expand...
Click to collapse
OK well I reverted back to my nandroid I created with my previous version of TWRP, and did the OTA again. Have not bothered to root or create further nandroids. So far everything is great. Just wish I could create a nandroid without the thing going crazy on me.
ninjai117 said:
Just wish I could create a nandroid without the thing going crazy on me.
Click to expand...
Click to collapse
I haven't had this happen to me. Only issue with TWRP for me so far on this device, is a backup failed to restore on an earlier TWRP version (so I had to flash a ROM and setup again) and I haven't had this issue on more recent TWRP versions.
Again, I'd suggest downloading TWRP again, and doing a fresh install of it and see if the problem persists. Or try CWM.
redpoint73 said:
The point is to re-install TWRP. As I don't have issues with the phone rebooting after doing a nandroid, I'm just guessing that maybe its just a bad TWRP install.
For that matter, try to download the TWRP file again, to make sure the file isn't corrupt.
You won't be able to boot into the OS just from what I suggested, you will still need to restore the nandroid.
erase cache is suggested as sometimes folks have trouble re-installing TWRP, and erase cache will often solve this. I always install TWRP by fastboot, so fastboot erase cache just takes 2 more seconds, which is time well spent to reduce headaches.
Click to expand...
Click to collapse
redpoint73 said:
I haven't had this happen to me. Only issue with TWRP for me so far on this device, is a backup failed to restore on an earlier TWRP version (so I had to flash a ROM and setup again) and I haven't had this issue on more recent TWRP versions.
Again, I'd suggest downloading TWRP again, and doing a fresh install of it and see if the problem persists. Or try CWM.
Click to expand...
Click to collapse
I instead flashed TWRP from Hasoon2000's HTC M8 All In One Kit, which is what I previously had and created my 4.4.2 nandroid with. Every time after that I was using the latest version from TWRP's website. I suspect that is the culprit, but I have no evidence yet as I have not created a nandroid again. I'm currently on 4.4.3 with SuperSU.zip flashed. No problems yet.
ninjai117 said:
Every time after that I was using the latest version from TWRP's website. I suspect that is the culprit, but I have no evidence yet as I have not created a nandroid again.
Click to expand...
Click to collapse
I always get TWRP from their website.
Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );
if you can still get to recovery, download latest gapps and flash that
Did you factory reset before or after you restored your back up?
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Try to factory reset again
vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.
So yesterday I flashed Santod's Nusense version 8(verizon base 4.4.3). Until now I have only used the stock 4.4.3 ROM since fully flashing the RUU from the OTA version. At first I attempted to flash it with the newest official TWRP release(2.8.5) but it froze, so I fastboot flashed his modified 2.8.3 TWRP, wiped, then was able the flash. My concern is that the first two times I tried to wipe in his 2.8.3 before flashing the ROM, I got an error in red text telling me "cannot mount (data/system) partition". I've never seen this before. I exited recovery, restarted, and tried again. After the reboot, it worked.
Basically my question is, since I initially got those errors for "unable to mount", does this mean my radio partitions are screwed up and I need to wipe with the stock recovery? Or could it be a harmless glitch in that version of TWRP? It's such a pain to restore everything after stock wiping that I really want to avoid it if possible. But I did get the dreaded "Unfortunately the process com.phone.android has stopped working" error in the ROM twice since then, and had to clear the cashes and let "android optimize apps" on boot to fix it. Is that a sign of the partitions getting messed up?
BranC85 said:
So yesterday I flashed Santod's Nusense version 8(verizon base 4.4.3). Until now I have only used the stock 4.4.3 ROM since fully flashing the RUU from the OTA version. At first I attempted to flash it with the newest official TWRP release(2.8.5) but it froze, so I fastboot flashed his modified 2.8.3 TWRP, wiped, then was able the flash. My concern is that the first two times I tried to wipe in his 2.8.3 before flashing the ROM, I got an error in red text telling me "cannot mount (data/system) partition". I've never seen this before. I exited recovery, restarted, and tried again. After the reboot, it worked.
Basically my question is, since I initially got those errors for "unable to mount", does this mean my radio partitions are screwed up and I need to wipe with the stock recovery? Or could it be a harmless glitch in that version of TWRP? It's such a pain to restore everything after stock wiping that I really want to avoid it if possible. But I did get the dreaded "Unfortunately the process com.phone.android has stopped working" error in the ROM twice since then, and had to clear the cashes and let "android optimize apps" on boot to fix it. Is that a sign of the partitions getting messed up?
Click to expand...
Click to collapse
The bug with 2.8.5 official twrp, is once you wipe /system or /data, it then has problems mounting either, as they are fully wiped in a way that twrp no longer sees them.
Since you did that wipe with that recovery first, you saw the errors from doing so.
Using my recovery fixes that problem....
You don't need to worry about it, since you fixed it by flashing my twrp and then Rom.
Your other error in the Rom, sounds like a bad flash though.
Might want to start over fresh and could be due to the launcher you chose in aroma.
But since I don't get any errors with the Rom, it's hard to say.
Hey guys,
So last night I accidentally wiped internal storage in TWRP. I guess that messed up my partitions or something, I don't know. Anyway, I can still access recovery, and I've tried to do a restore (one that I made back when I was on stock 4.4.2 I think) but after that it tries to boot, gets to "Android is upgrading... Optimizing app Y of X." and once that operation completes it shows the lockscreen for about a tenth of a second, and the phone reboots.
I'm stumped. Anyone know what can I do?
Sorry if this has been asked a hundred times. For some reason the search function in the forums isn't working for me. And I've been looking for a solution all morning.
EDIT: FYI when I tried the restore I did only System and Data and not Boot, because I was afraid that'd cause more problems.
Did you try restoring and performing a factory wipe before booting the newly-restored ROM?
It seems that Marshmallow based roms aren't working, but Lollipop ones will boot. Not sure why as I didn't have any problem with the same MM roms in the past.
More info:
MM roms wont flash in TWRP; after the failed attempt, TWRP says system cannot be mounted until I either wipe or install a 12.1 rom.
Tried to install a stock rom (4.4.2) and it failed in TWRP. Just says "Error Flashing"
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
audit13 said:
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
Click to expand...
Click to collapse
Yes to full wipe. TWRP is 2.8.7.0, so yeah I think it's the newest? Not 100% sure.
Wiping internal storage should not affect the partitions. I'm not sure that TWRP even has the ability to change partitions.
Yes, 2.8.7.0 is the latester version of TWRP.
If you are on the nj2 bootloader, try flashing this in TWRP: http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006
Welp, seems to be all good now. Not sure if I really did anything to fix it or not. I tried to install a stock ROM but it wouldn't boot (stuck on Samsung logo) but after that my CM13 ROM installed properly again. The one CM13 ROM I have still wont install at all - maybe that file became corrupt or something? Not sure if that's even possible.
Either way I'm all fixed up. Thanks for all your help.
Cheers
Glad you got it sorted out. If you do figure out what you did to get it working, post your answer as it may help others that are in a similar situation.
I tried Factory Reseting my phone earlier today through Recovery, It said everything was reset so I restarted my phone. My phone is now in a bootloop, it vibrates, shows the "erasing" screen, then the hidden LED light turns on and the screen goes black, then the phone does that forever. It's on the erasing screen for about 3 seconds before restarting. Trying to enter Recovery Mode just sends me back to the "erasing" screen.
Any help would be wonderful!
Were you completely stock? On a ROM? With custom recovery?
What steps did you use? Wipe data and factory reset? Did you wipe the cache partition?
If you were on stock, I would suggest you tried to wipe again. You could try to do it with ADB and fastboot if you are not able to access the recovery (which I don't think would happen if you're completely stock).
If you were not on stock or with a custom recovery, the easiest way to solve this would be to reinstall the ROM you were using.
victorhbm15 said:
Were you completely stock? On a ROM? With custom recovery?
What steps did you use? Wipe data and factory reset? Did you wipe the cache partition?
If you were on stock, I would suggest you tried to wipe again. You could try to do it with ADB and fastboot if you are not able to access the recovery (which I don't think would happen if you're completely stock).
If you were not on stock or with a custom recovery, the easiest way to solve this would be to reinstall the ROM you were using.
Click to expand...
Click to collapse
I was Stock ROM with root, I edited the build.prop file and rebooted the device, that’s when the issues began. I had TWRP installed and restored my backup of my phone from before I made any changed, this didn’t help anything (I was stuck on the “Your device is unlocked” screen). I restored the stock recovery and I now have the original recovery installed. Finally after some well timed button presses I am no able to access the Stock Recover, however if I try to side load a working ROM onto my phone it shows the percentage of the side load but then fails this:”
E:footer is wrong
I:verify_file returned 1
E:Signature verification failed
E:error 21
W:failed to read uncrypt status: No such file or directory
“
It’s a little late now, so I’ll be back tomorrow to do some more research.
Dubstepwolf123 said:
I was Stock ROM with root, I edited the build.prop file and rebooted the device, that’s when the issues began. I had TWRP installed and restored my backup of my phone from before I made any changed, this didn’t help anything (I was stuck on the “Your device is unlocked” screen). I restored the stock recovery and I now have the original recovery installed. Finally after some well timed button presses I am no able to access the Stock Recover, however if I try to side load a working ROM onto my phone it shows the percentage of the side load but then fails this:”
E:footer is wrong
I:verify_file returned 1
E:Signature verification failed
E:error 21
W:failed to read uncrypt status: No such file or directory
“
It’s a little late now, so I’ll be back tomorrow to do some more research.
Click to expand...
Click to collapse
Did you factory reset already?
I don't think you can sideload a ROM with stock recovery.
Don't try to flash anything with stock recovery, better go back to TWRP.
PD: If when going to TWRP you slid the "swipe to allow modifications", that's what caused the bootloop, as it made modifications to the partitions. Or so I read on a guide here.
victorhbm15 said:
Did you factory reset already?
I don't think you can sideload a ROM with stock recovery.
Don't try to flash anything with stock recovery, better go back to TWRP.
PD: If when going to TWRP you slid the "swipe to allow modifications", that's what caused the bootloop, as it made modifications to the partitions. Or so I read on a guide here.
Click to expand...
Click to collapse
Thinking back again I guess it didn’t make much sense trying to flash a rom through Stock Recovery. Yes I did Wipe the Cache partition and then I Wiped data/factory reset through Stock recovery, all I did in TWRP was restore everything from the backup.
*An hour later*
So I was able to get TWRP installed again. Unfortunately when I try to restore from a backup I made with TWRP before messing with anything it restores with no errors or warnings, but when I reboot the system it gets stuck on the "Your device is unlocked and cannot be trusted" screen. Probably sounding stupid saying this, but shouldn't a restore of a backup be straight forward?
*Another hour later*
I was able to get ToxycOS 3.0 installed and running, but personally I don't like it and want to go to Motorola's Software... now I just need to fix whats wrong with my restore.
Dubstepwolf123 said:
Thinking back again I guess it didn’t make much sense trying to flash a rom through Stock Recovery. Yes I did Wipe the Cache partition and then I Wiped data/factory reset through Stock recovery, all I did in TWRP was restore everything from the backup.
*An hour later*
So I was able to get TWRP installed again. Unfortunately when I try to restore from a backup I made with TWRP before messing with anything it restores with no errors or warnings, but when I reboot the system it gets stuck on the "Your device is unlocked and cannot be trusted" screen. Probably sounding stupid saying this, but shouldn't a restore of a backup be straight forward?
*Another hour later*
I was able to get ToxycOS 3.0 installed and running, but personally I don't like it and want to go to Motorola's Software... now I just need to fix whats wrong with my restore.
Click to expand...
Click to collapse
Why not fastboot install stock firmware?
Isn't that available, here?
pizza_pablo said:
Why not fastboot install stock firmware?
Isn't that available, here?
Click to expand...
Click to collapse
In the end I was able to install the Stock Moto Z2 Play firmware... I hate when people don't include the fix in their answers for other people, but currently I am unable to post any links because they are on a different device. I'll get back later with the links.