Develop Bugs

[Q] [CM10] Bootloop just after startup

I hope this is the right subforum, there are _so_ many q-q
Hello,
Yesterday I was up to surfing on my GNex running CM10 nightly 2012-08-2?, but it just hung, vibrated, showed me the Google logo and booted up again. This is not unusual since it is a very early build, but when it was up again and demanded my PIN, I could hardly enter 3 digits when it hung and rebooted again. After 6 times it really annoyed me and I pulled out the battery.
I tried booting in Safe Mode, but that didn't work either. So I wiped system and both caches, flashed the same build again, same problem
I can imagine that wiping data would help, but my last backup is quite a few weeks old and I don't want to lose my data so this would be the very last solution.
I hope someone will be able to help me
qsuscs

Oh, maybe this could be important: I use ClockworkMod Touch 6.0.1.0

You could try to flash the newest nightly and see if that works, but in the end I think you are going to have wipe your data. You could make a backup from cwm and try wiping than restoring the backup. I don't know if that would help any but it could be worth a shot.

And dont restore app/system data.
Sent from my i9250

If you can still get into the recovery, you can run a backup and then restore apps/data from a nandroid via titanium backup once you get it up and running.

Nandroid does not really work.
Code:
ClockworkMod Recovery v6.0.1.0
SD Card space free: 7426MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Freeing space...
Done freeing space.
Backing up data...
Error while making a backup image of /data!
Does anyone know why it doesn't, or maybe another backup solution?

Could I do a backup with another recovery? Or could flashing anotherr recovery even cause data loss?

Triple post hope you can forgive me
So I flashed TWRP. Nandroid didn't work there, too, but I think I know the reason: /data needs to be mountet read-only for the backup, but this is impossible when it is written to the internal storage (/data/media). And since neither TWRP nor ClockworkMod have a TCP stack, I'll need an USB-OTG-adaptor and an USB flash drive. Luckily, I know someone who has one, gonna ask him tomorrow...

[Q] Wiping to stock "everything"

I'm having problems w/ my GS3 after accidentally restarting w/ no OS.
See original post here: http://forum.xda-developers.com/showpost.php?p=41306538&postcount=5979
I got a response, here: http://forum.xda-developers.com/showpost.php?p=41306968&postcount=5980
I'm unsure of what exactly they meant in the response, but I found a walkthrough, here: http://www.androidjunkies.com/how-to-unroot-att-galaxy-s3-flash-stock-ucdlk3-firmware/
I feel like I've done this, but I'll try it out anywho. I'm wondering:
1. Could it an issue of kernels?
2. Would it help if I wiped everything on my sd card(s)? If so, how do I do that?
3. Could it be an issue of having/not having my sd cards mounted?
Thank you for your generous help.

hoss9009 said:
I'm having problems w/ my GS3 after accidentally restarting w/ no OS.
See original post here: http://forum.xda-developers.com/showpost.php?p=41306538&postcount=5979
I got a response, here: http://forum.xda-developers.com/showpost.php?p=41306968&postcount=5980
I'm unsure of what exactly they meant in the response, but I found a walkthrough, here: http://www.androidjunkies.com/how-to-unroot-att-galaxy-s3-flash-stock-ucdlk3-firmware/
I feel like I've done this, but I'll try it out anywho. I'm wondering:
1. Could it an issue of kernels?
2. Would it help if I wiped everything on my sd card(s)? If so, how do I do that?
3. Could it be an issue of having/not having my sd cards mounted?
Thank you for your generous help.
Click to expand...
Click to collapse
I installed triangleaway and it's saying that I'm not rooted, but somehow still have access to CMW.
Thoughts?
I'm going to try all the other steps.

hoss9009 said:
I installed triangleaway and it's saying that I'm not rooted, but somehow still have access to CMW.
Thoughts?
I'm going to try all the other steps.
Click to expand...
Click to collapse
CMW or any recovery for that matter has nothing to do with any rom or whatever you are running. Recoveries on this device are on their own partition.

If you are trying to go back to stock:
1.) Go here and download the correct firmware for your device. http://forum.xda-developers.com/showthread.php?t=1968625
2.) Flash that firmware with odin.
3.) After that's done, reboot into recovery and factory reset.
4.) After that's done you will be fully stock.
5.) You should really consider reading up on all of this stuff. If you don't, you take the risk of bricking your expensive device and rendering it useless.

task650 said:
If you are trying to go back to stock:
1.) Go here and download the correct firmware for your device.
2.) Flash that firmware with odin.
3.) After that's done, reboot into recovery and factory reset.
4.) After that's done you will be fully stock.
5.) You should really consider reading up on all of this stuff. If you don;t you take the risk of bricking your expensive device and rendering it useless.
Click to expand...
Click to collapse
Thank you so much. I know some, but not everything. I'm missing pieces to the puzzle.
I just tried to make a nandroid of my stock rom as is right now and I got the error:
Code:
No /sdcard/ .android_secure found. Skipping backup of applications on external storage. No sd-ext found. Skipping backup of sd-ext. Generating md5 sum... Backup complete!
Why would it say that about my sd card? I feel like directories on my sd card(s) aren't lining up w/ what android wants.
Thoughts?

hoss9009 said:
Thank you so much. I know some, but not everything. I'm missing pieces to the puzzle.
I just tried to make a nandroid of my stock rom as is right now and I got the error:
Code:
No /sdcard/ .android_secure found. Skipping backup of applications on external storage. No sd-ext found. Skipping backup of sd-ext. Generating md5 sum... Backup complete!
Why would it say that about my sd card? I feel like directories on my sd card(s) aren't lining up w/ what android wants.
Thoughts?
Click to expand...
Click to collapse
That's not an error. CMW or any recovery for that matter will not make nandroids of anything on your external sdcard partition. Its supposed to say that.

task650 said:
That's not an error. CMW or any recovery for that matter will not make nandroids of anything on your external sdcard partition. Its supposed to say that.
Click to expand...
Click to collapse
No no, I tried to make a nandroid backup OF my system and put it on ON my sd card (which I've done a billion times before).

task650 said:
That's not an error. CMW or any recovery for that matter will not make nandroids of anything on your external sdcard partition. Its supposed to say that.
Click to expand...
Click to collapse
Is there a way to wipe/format both sd cards? i have everything backup on my comp.

hoss9009 said:
Is there a way to wipe/format both sd cards? i have everything backup on my comp.
Click to expand...
Click to collapse
Use your comp to format your external sdcard. Wipe the internal in recovery.

task650 said:
Use your comp to format your external sdcard. Wipe the internal in recovery.
Click to expand...
Click to collapse
Thanks. Really hoping this works. I don't know why it says that I'm not rooted when I can access CMW.

hoss9009 said:
Thanks. Really hoping this works. I don't know why it says that I'm not rooted when I can access CMW.
Click to expand...
Click to collapse
You're not reading what I posted is why you don't understand. Its very simple. Root has nothing to do with recovery. CMW is a recovery. Not a root method. Just because you have a custom recovery doesn't mean you have root. You have to root your device if you want it rooted.

task650 said:
You're not reading what I posted is why you don't understand. Its very simple. Root has nothing to do with recovery. CMW is a recovery. Not a root method. Just because you have a custom recovery doesn't mean you have root. You have to root your device if you want it rooted.
Click to expand...
Click to collapse
Ah, ok. I've always that they were synonymous.
But here's where I'm confused. I've used oden and have unroot/rooted about 5 times in the last few days. Also, while using Oden, it gives me the i9300 label at the top. Is that normal/correct?

hoss9009 said:
Ah, ok. I've always that they were synonymous.
But here's where I'm confused. I've used oden and have unroot/rooted about 5 times in the last few days. Also, while using Oden, it gives me the i9300 label at the top. Is that normal/correct?
Click to expand...
Click to collapse
You don't want to use anything i9300 related. Please only use what I've linked you in an earlier post. All of this is very simple and I've given you all of the steps to do this correctly. There's no need for you to be making this complicated. Everything you need is all right in front of you here.

task650 said:
You don't want to use anything i9300 related. Please only use what I've linked you in an earlier post. All of this is very simple and I've given you all of the steps to do this correctly. There's no need for you to be making this complicated. Everything you need is all right in front of you here.
Click to expand...
Click to collapse
Thank you so much. But I don't get why it says my phone is a i9300. It's an ATT phone. When I plug into my comp, oden tells me it's a i9300 phone. I'm afraid I really messed it up.
I just wiped my cache and it says
Code:
Formatting /cache
Cache wipe complete.
E:unknown volume for path [sd-ext]
Dalvik Cache wiped
Should I be concerned if it says "E:unknown volume for path [sd-ext]"??

hoss9009 said:
Thank you so much. But I don't get why it says my phone is a i9300. It's an ATT phone. When I plug into my comp, oden tells me it's a i9300 phone. I'm afraid I really messed it up.
I just wiped my cache and it says
Code:
Formatting /cache
Cache wipe complete.
E:unknown volume for path [sd-ext]
Dalvik Cache wiped
Should I be concerned if it says "E:unknown volume for path [sd-ext]"??
Click to expand...
Click to collapse
Also, in the "Mounts and Storage Menu" of CMW, I get this:
Code:
- mount /system
- unmount /data
- unmount /cache
- mount /emmc
- mount /sdcard
(all format options below these)
Should I be concerned w/ the "unmounted" items?

hoss9009 said:
Also, in the "Mounts and Storage Menu" of CMW, I get this:
Code:
- mount /system
- unmount /data
- unmount /cache
- mount /emmc
- mount /sdcard
(all format options below these)
Should I be concerned w/ the "unmounted" items?
Click to expand...
Click to collapse
This is what I was talking about...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hoss9009 said:
This is what I was talking about...
View attachment 1957243
Click to expand...
Click to collapse
OK.... so I'm assuming the oden I was using was not the best to use. I found this article: http://gs3.wonderhowto.com/how-to/root-your-samsung-galaxy-s3-and-flash-stock-roms-using-odin-for-windows-0142713/, and have it working now.
This oden looked different:
I don't know why, but I got it to work this time. I'll attempt to install AOKP and see what happens....

hoss9009 said:
OK.... so I'm assuming the oden I was using was not the best to use. I found this article: http://gs3.wonderhowto.com/how-to/root-your-samsung-galaxy-s3-and-flash-stock-roms-using-odin-for-windows-0142713/, and have it working now.
This oden looked different: View attachment 1957279
I don't know why, but I got it to work this time. I'll attempt to install AOKP and see what happens....
Click to expand...
Click to collapse
Ok, @Task650. Everything's working :victory:

hoss9009 said:
Ok, @Task650. Everything's working :victory:
View attachment 1957376
Click to expand...
Click to collapse
My recommendation: do not try to root until you know all of the common problems that are encountered for the device model your using. Your problems here should have been able to been resolved within 15 to 20 minutes (not including setting your phone back up). Had you done your due diligence beforehand and learned more, this would have been easy and never an issue.
I would highly suggest you stick with the stock rom until you have thoroughly educated yourself. While I am not a developer, I respect those who are. As such I take upon myself to learn as much as I can so I do not have to bug them about any problems I run into.

[Q] Cloning the /data partition between devices

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi there!
What I'm trying to do is to "pre-configure" 70 devices (you read that right, 70) to have identical software/wallpaper/security settings/etc.
All devices are identical GT-N5100 with 4.1.2 (JZO54K.N5100XXBMD1) Android version.
The thing is, we absolutely _should_ keep the warranty and OTAs, therefore flipping the "System state" flag is definitely not what I want here.
I already tried backing up the device with adb backup, but this kind of backup doesn't contain all applications (specifically, those with android:allowBackup=false are not exported) and most of the settings (disabled apps' list or security settings)
So I came to a point that I _need_ to replace the whole /data partition. Which, obviously, requires custom recovery.
The main concern is, how to avoid triggering that "System state"?
Let's say I'll flash an alternate recovery image, backup/restore the system, then restore the original recovery, without booting into Android. Would that work, or since we change the flash counter, it will also cause the flag to change to "Modified"?
If it changes, could TriangleAway restore it back? Mind that I won't be able to wipe /data at this point, it defeats the purpose.
Again, I don't need root access on these tablets at all, I only need to have identical /data partition between them.
Any ideas?
Did anyone check that "recovery trick" I described?
Thanks in advance.

NeverGone\RU said:
Hi there!
What I'm trying to do is to "pre-configure" 70 devices (you read that right, 70) to have identical software/wallpaper/security settings/etc.
All devices are identical GT-N5100 with 4.1.2 (JZO54K.N5100XXBMD1) Android version.
The thing is, we absolutely _should_ keep the warranty and OTAs, therefore flipping the "System state" flag is definitely not what I want here.
I already tried backing up the device with adb backup, but this kind of backup doesn't contain all applications (specifically, those with android:allowBackup=false are not exported) and most of the settings (disabled apps' list or security settings)
So I came to a point that I _need_ to replace the whole /data partition. Which, obviously, requires custom recovery.
The main concern is, how to avoid triggering that "System state"?
Let's say I'll flash an alternate recovery image, backup/restore the system, then restore the original recovery, without booting into Android. Would that work, or since we change the flash counter, it will also cause the flag to change to "Modified"?
If it changes, could TriangleAway restore it back? Mind that I won't be able to wipe /data at this point, it defeats the purpose.
Again, I don't need root access on these tablets at all, I only need to have identical /data partition between them.
Any ideas?
Did anyone check that "recovery trick" I described?
Thanks in advance.
Click to expand...
Click to collapse
Gosh your spinning your wheels on something so simple.
Install saferoot.zip on all 70 devices
On the completed master clone device
create a admin google account for system apps
add the admin google account and make sure play store has the admin account selected.
pay for Ti Backup Pro and install
set google account back to original google account if available.
setup Ti Backup to save on SD, etc... note: Ti Backup has a lot of options in pro, you will have to make sure things are set to your needs.
For example, remove Google store from apps, so you have control over updates.
Remove admin google account
Do a full backup on SD
Remove Ti Backup Pro from backed up apps
Copy SD to spare 2GB (minimum) SD chip(s)
Insert SD chip in each device to be slave cloned
If each device has already gone through initial setup, do a factory reset.
When google account is needed use the admin account for syncing the Ti backup Pro
Start Ti Backup Pro and do not change system ID by ignoring.
Set Ti Backup pro to use the SD card and do a restore missing apps + system data.
When prompted after starting... select XML.
Be sure to deselect the check box for ignore system...
Reboot and make sure everything looks good, if not you may need to restore again using Snapshot.
remove Ti Backup, and uninstall root within SuperSu as a wipe for reinstall.
Reboot again and you are done.
All wallpaper, Icons and folders, along with app settings will all be the same.
This is a 90% accurate way to do it, as I have no idea what apps you are using, custom or paid. You will need to fine tune what options you may need to add in the procedures given.

gooberdude said:
Gosh your spinning your wheels on something so simple.
Install saferoot.zip on all 70 devices
On the completed master clone device
create a admin google account for system apps
add the admin google account and make sure play store has the admin account selected.
pay for Ti Backup Pro and install
set google account back to original google account if available.
setup Ti Backup to save on SD, etc... note: Ti Backup has a lot of options in pro, you will have to make sure things are set to your needs.
For example, remove Google store from apps, so you have control over updates.
Remove admin google account
Do a full backup on SD
Remove Ti Backup Pro from backed up apps
Copy SD to spare 2GB (minimum) SD chip(s)
Insert SD chip in each device to be slave cloned
If each device has already gone through initial setup, do a factory reset.
When google account is needed use the admin account for syncing the Ti backup Pro
Start Ti Backup Pro and do not change system ID by ignoring.
Set Ti Backup pro to use the SD card and do a restore missing apps + system data.
When prompted after starting... select XML.
Be sure to deselect the check box for ignore system...
Reboot and make sure everything looks good, if not you may need to restore again using Snapshot.
remove Ti Backup, and uninstall root within SuperSu as a wipe for reinstall.
Reboot again and you are done.
All wallpaper, Icons and folders, along with app settings will all be the same.
This is a 90% accurate way to do it, as I have no idea what apps you are using, custom or paid. You will need to fine tune what options you may need to add in the procedures given.
Click to expand...
Click to collapse
I would do exactly this, but I need to keep devices "stock" for warranty purposes — I won't see any of them after sending them to customer. Hence, having root = "System state: modified" = no warranty. Yea I can unroot afterwards, but it might also fail and keep the "System modified" flag in place. Risky.
Thanks anyway, let's see how it goes.

NeverGone\RU said:
I would do exactly this, but I need to keep devices "stock" for warranty purposes — I won't see any of them after sending them to customer. Hence, having root = "System state: modified" = no warranty. Yea I can unroot afterwards, but it might also fail and keep the "System modified" flag in place. Risky.
Thanks anyway, let's see how it goes.
Click to expand...
Click to collapse
I don't have any system state modified on my tablet. Saferoot does not flash. And will allow OTA and Kies to update without issues. You should at least look up the thread for saferoot and see its function. It installs the root not flashes it. The flash counter is what you are worried about. Though triangle away will reset the counter, and once cleared can be removed, if flashing a root. What keeps the counter coming back is the use of flashed custom ROMs.
I use to follow the popular threads on flashing and found that saferoot is exactly what it says, and I will not do any other rooting without it. That is how good it is.

8.5" - Can get to recovery but error on installing any image?

Hi -
Brand spanky new owner of a Tab S 8.4, and took the plunge and rooted. The rooting process seemed to work find, and I could run SU. But then I went to try and load a couple ROMs. First I tried CyanogenMod (for T700). I noticed a couple errors (see screenshot below) and it went quite a bit quicker than I expected. When tablet rebooted, it booted back to OEM (but rooted) image. I tried this a few times, double checked MD5, etc., etc, and still the same issue. So then I thought I'd try a different ROM, BlissPop (also for the T700). Interestingly, I got the exact same error and problem. I've tried different microSD cards, and I should also clarify I wipe data/factory reset and wipe cache partition before each attempt to install ROM.
Any chance anyone has any advice? Did I maybe root incorrectly?
Here's an image of what my recovery screen looks like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And here's a picture capturing those couple errors right before it reboots on me:
Thanks in advance for any advice anyone may have!!!!

Hi did you apply the sd fix for kitkat? It seems your installing from sd card. And the images are broken. I cant see them... Try to download the rom onto your internel storage and flash again

DUHAsianSKILLZ said:
Hi did you apply the sd fix for kitkat? It seems your installing from sd card. And the images are broken. I cant see them... Try to download the rom onto your internel storage and flash again
Click to expand...
Click to collapse
I'm not familiar with the sd fix for kitkat. If it makes a difference I take the microSD out and put it in my laptop to copy the ROM zip.
I tried to install from the internal SD card, but my recovery doesn't give me the option to change to there. Just the external.
Sorry you can't see the images. Let's see if this helps:
Picture of my normal recovery screen:
http://s6.postimg.org/q14p6gaxt/Normal_Recovery_Screen.jpg
Picture of the errors I was getting trying to load ROMs:
http://s6.postimg.org/swhsdbext/Error_Installing_ROM.jpg

crackface said:
I'm not familiar with the sd fix for kitkat. If it makes a difference I take the microSD out and put it in my laptop to copy the ROM zip.
I tried to install from the internal SD card, but my recovery doesn't give me the option to change to there. Just the external.
Sorry you can't see the images. Let's see if this helps:
Picture of my normal recovery screen:
http://s6.postimg.org/q14p6gaxt/Normal_Recovery_Screen.jpg
Picture of the errors I was getting trying to load ROMs:
http://s6.postimg.org/swhsdbext/Error_Installing_ROM.jpg
Click to expand...
Click to collapse
Hi, from those pictures... You need to install twrp recovery. Since your rooted download a an app called flashify. Now grant it root and choose twrp recovery. Now pick twrp 2.8.1.0 and hit yup to install. Now just reboot into recovery and hit install then pick the zip and slide to install. Wipe cahes first too

DUHAsianSKILLZ said:
Hi, from those pictures... You need to install twrp recovery. Since your rooted download a an app called flashify. Now grant it root and choose twrp recovery. Now pick twrp 2.8.1.0 and hit yup to install. Now just reboot into recovery and hit install then pick the zip and slide to install. Wipe cahes first too
Click to expand...
Click to collapse
That did the trick. Thank you so much!!!!

Just for future reference you cannot install custom images with the stock recovery, thats why you needed TWRP. The auto rooting process flashes back the stock recovery.

Z2 Play stuck on boot up screen...

I'm rooted on stock Nougat ROM (I think... I rooted it a couple years ago), bootloader unlocked.
A few days ago my phone just stopped booting up correctly. It boots to the blue Moto screen with the boot animation but stays there forever.
I can get into TWRP and view all of the files in system, Internal SD card, and External SD card. I've backed up a bit of it just in case but I'm hoping someone here can tell me what to try to get it to boot correctly.
Is there a quick or obvious way to fix this that anyone is aware of?
I have an old TWRP backup and when I go into "Restore" I have the option to restore System, Data (excl. storage), Boot, Recovery, EFS, and logo... so is worth it to try restoring one of these (such as boot or system)?
I'm looking to try the safest things first... I really don't want to have to wipe my device or worse, brick it.
Thanks

Well, if you don't have any important data in the phone (you can copy files via USB), you can just do factory reset and see

Klen2 said:
Well, if you don't have any important data in the phone (you can copy files via USB), you can just do factory reset and see
Click to expand...
Click to collapse
Well, I have some important data but I can backup my /data/ folder. The problem (other than the fact that it will take a lot of time) is that I'm not sure how to restore the apps and data once I factory reset it.
It would be different if they were Titanium Backup backups but I don't know of a way to restore an app with just having the apps data folders.

What will happen if I go into TWRP and Install the stock rom zip file? Will I lose data or root or mess with anything important?

More generally:
a) your problem may be in system - then reflashing system would help. It can be done without loosing data
b) your problem may be in data (which is more likely) - you have to wipe data
a) Reflashing system can be done by flashing correct images via fastboot (using script that doesn't wipe data) or in recovery if you have flashable zip of your rom (I'm not sure whether there are any). However, even after flashing system, it still may not work because of some conflicts with data so wiping data may be unavoidable
b)how to minimalize losses: what kind of important data do you have? If it is files, they can be copied easily. If it is app data, it's harder. However, if you have Google Backup turned on, most apps use it to backup their data. What particular app's data do you need to save, if you don't mind telling?
I know there used to be app that was able to extract individual app's data from TWRP backup and restore it. Maybe it was Titanium Backup Pro. But as nowadays non-cloud backups aren't a thing anymore, these apps quite vanished or their development stopped and they also may not work with new android versions.
You can download stock firmware here: https://mirrors.lolinet.com/firmware/moto/albus/official/
Nougat is available for RETAIL, RETLA, RETRU, RETUS and VZW. Where did you buy your phone? It is best to flash the ROM for the same region to avoid problems if you want to keep data. But you can flash any.

Klen2 said:
More generally:
a) your problem may be in system - then reflashing system would help. It can be done without loosing data
b) your problem may be in data (which is more likely) - you have to wipe data
a) Reflashing system can be done by flashing correct images via fastboot (using script that doesn't wipe data) or in recovery if you have flashable zip of your rom (I'm not sure whether there are any). However, even after flashing system, it still may not work because of some conflicts with data so wiping data may be unavoidable
b)how to minimalize losses: what kind of important data do you have? If it is files, they can be copied easily. If it is app data, it's harder. However, if you have Google Backup turned on, most apps use it to backup their data. What particular app's data do you need to save, if you don't mind telling?
I know there used to be app that was able to extract individual app's data from TWRP backup and restore it. Maybe it was Titanium Backup Pro. But as nowadays non-cloud backups aren't a thing anymore, these apps quite vanished or their development stopped and they also may not work with new android versions.
You can download stock firmware here: https://mirrors.lolinet.com/firmware/moto/albus/official/
Nougat is available for RETAIL, RETLA, RETRU, RETUS and VZW. Where did you buy your phone? It is best to flash the ROM for the same region to avoid problems if you want to keep data. But you can flash any.
Click to expand...
Click to collapse
Honestly, what I needed to recover were unread messages/whatsapp messages I never read and mostly just to avoid the headache or starting over but I'm over that. And what you said about using Titanium Backup to restore individual apps from a nandroid backup... that's exactly what I read about yesterday and was planning on doing.
Just now I tried restoring an old system backup and and a recent data/system backup but both times it got stuck at boot... so I think I'm either going to just flash my stock rom or do a restore of my system/data from last year...
My phone was running "Albus 7.1.1/NPS26.118-24/25" and I found a zip named "ALBUS_C_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" (which has SW listed as "SW Version: albus_c-user 7.1.1 NPS26.118-24 25 release-keysM8953P_23.33.07.34R") so I think I found the right one.
Would you recommend restoring system and data from a working (but old) backup in TWRP or just flashing my rom again?
Also, I'm not sure if I need to reflash magisk or flash the no-verity-opt-encrypt zip (or wipe something).
Either way, I'm going to just try one of those once I hear you recommendation.
Thanks

SMS may be backed up by Google, WhatsApp not if you didn't have automatic backup turned on (or done backup manually).
First of all, I would flash just system and other stuff except data. I don't recommend flashing official zips in recovery. If the phone is rooted, they will fail anyway and they may delete data. It is better to flash via fastboot. Do you remember your update channel Do you have US retail device? Then you may try the zip you found. But not in recovery. It is not a recovery flashable zip. Extract it and I will send you a .bat file to flash via fastboot.

Klen2 said:
SMS may be backed up by Google, WhatsApp not if you didn't have automatic backup turned on (or done backup manually).
First of all, I would flash just system and other stuff except data. I don't recommend flashing official zips in recovery. If the phone is rooted, they will fail anyway and they may delete data. It is better to flash via fastboot. Do you remember your update channel Do you have US retail device? Then you may try the zip you found. But not in recovery. It is not a recovery flashable zip. Extract it and I will send you a .bat file to flash via fastboot.
Click to expand...
Click to collapse
It's an unlocked, US, Moto Z2 Play (XT1710-01). I ordered it from motorola's website. I never updated it, I just followed these instructions (https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792) to unlock bootloader, boot TWRP, back it up, and flash magisk.

extract your zip, place there fastboot.exe from attachment if you don't have one and run the bat. It will install the rom without wiping data. It is made for newest Nougat 'XT1710-01_ALBUS_C_7.1.1_NPSS26.118-24-23_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip' rom from here: https://mirrors.lolinet.com/firmware/moto/albus/official/RETUS/

Klen2 said:
extract your zip, place there fastboot.exe from attachment if you don't have one and run the bat. It will install the rom without wiping data. It is made for newest Nougat 'XT1710-01_ALBUS_C_7.1.1_NPSS26.118-24-23_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip' rom from here: https://mirrors.lolinet.com/firmware/moto/albus/official/RETUS/
Click to expand...
Click to collapse
So place your bat file in the extracted folder and run the bat file? Does my phone need to be in fast boot and do any of these files need to be on my phone or I can just do it from my PC?

All files in the same folder, phone in fastboot. Then run the bat

Klen2 said:
All files in the same folder, phone in fastboot. Then run the bat
Click to expand...
Click to collapse
I gave it a go but it's still hanging on boot.
Here's what the command window showed...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Then you'll probably have to wipe data. Backup them (to SD) and then try wipe

If you have unlocked bootloader and TWRP backup it is almost impossible to brick your Z2 Play, just flash Stock Nougat, Stock Oreo or Stock Pie and your phone should boot again.
By the way it looks, you will lose all your personal information.
If the classic wipes haven't worked you gotta try flash Stock ROM through fastboot.