Related
First, I'm sorry if there's a similar thread, I did search for it.
I'm waiting for the oficial OTA JB update for quite some time now and the only thing that stopped me from unlocking my bootloader and flashing a custom rom till now was the fact that it's going to wipe my data. I'm loosing my patience and am ready to go on with it, but still, I have to try:
Is there a way to unlock without wiping/backup and restore the whole data (incl. apps and their settings) after unlocking the bootloader?
Thanks in advance!
snigna said:
First, I'm sorry if there's a similar thread, I did search for it.
I'm waiting for the oficial OTA JB update for quite some time now and the only thing that stopped me from unlocking my bootloader and flashing a custom rom till now was the fact that it's going to wipe my data. I'm loosing my patience and am ready to go on with it, but still, I have to try:
Is there a way to unlock without wiping/backup and restore the whole data (incl. apps and their settings) after unlocking the bootloader?
Thanks in advance!
Click to expand...
Click to collapse
You've pretty much answered your question.
Backup and restore?
I was almost sure this was the only option, but how?
adb backup will do most of it, but you'll have to get the options right.
So I followed this guide to backup using adb: h**p://www.thesuperusersguide.com/adb-backup--restore.html, but no backup file appears. It takes like 2-3 seconds before it says that the backup is complete (impossible, I think). Drivers are installed, everything seems OK. Any ideas?
EDIT: Found the solution in another thread. The command that worked for me was
adb backup -apk -shared -all -f /backup/backup.ab
Click to expand...
Click to collapse
You might want -nosystem, but I'm not sure. Double check everything, and take multiple backups with different optuobs. Hopefully one will work close enough.
snigna said:
So I followed this guide to backup using adb: h**p://www.thesuperusersguide.com/adb-backup--restore.html, but no backup file appears. It takes like 2-3 seconds before it says that the backup is complete (impossible, I think). Drivers are installed, everything seems OK. Any ideas?
EDIT: Found the solution in another thread. The command that worked for me was
Click to expand...
Click to collapse
BenPope said:
You might want -nosystem, but I'm not sure. Double check everything, and take multiple backups with different optuobs. Hopefully one will work close enough.
Click to expand...
Click to collapse
IIRC, you start with snigna's command first. When it gets stuck along the process, you cancel it (or it stops itself, don't remember now), you use BenPope's switch instead and it resumes where it left off. Please double check.
Actually I didin't even have to use the backup, after flashing JB it downloaded all the apps I had, which was the main reason I wanted to do it.
I'm fairly new to Android and the Nexus 7. I am unlocked, rooted, and have installed Ti Backup. I just recently received the OTA for 4.4.4 and installed it, and then manually loaded TWRP back and rerooted.
This doesn't seem like the cleanest install (maybe it's my OCD tendencies with hardware and software), so I'm wondering what is the best way to install Android updates? Should I reset to the factory image and then use Ti back up for all my apps? Is the way I proceeded just as good as other possible methods? My goal is to follow a plan that will support the 7 performing as best as possible.
Any info or opinions would be appreciated.
Thanks,
Rick
C5Longhorn said:
I'm fairly new to Android and the Nexus 7. I am unlocked, rooted, and have installed Ti Backup. I just recently received the OTA for 4.4.4 and installed it, and then manually loaded TWRP back and rerooted.
This doesn't seem like the cleanest install (maybe it's my OCD tendencies with hardware and software), so I'm wondering what is the best way to install Android updates? Should I reset to the factory image and then use Ti back up for all my apps? Is the way I proceeded just as good as other possible methods? My goal is to follow a plan that will support the 7 performing as best as possible.
Any info or opinions would be appreciated.
Thanks,
Rick
Click to expand...
Click to collapse
I prefer using multirom. What I do, is wait for a flashable full version of the latest and greatest stock from Tasssadar (he usually has one the same day or 2), then flash it as secondary, root it, install xposed, gb, and a couple other modules and viper4android, qualcom dalvik and bionic patches, flash elementalx, go into primary, make backups with TiB, go into recovery and do a complete nandroid, put them onto my meenova (and pc), delete all the big apps that take up a lot of room, then boot into secondary, restore android ID with TiB, install only small apps I need (I prefer reinstalling instead of restoring from backup), then use TiB to restore app data only (only the things I need) and wifi networks, once I am satisfied with it being complete, I use multiroms swap rom function to swap secondary to primary, then confirm it works, then I delete the secondary (which is the old version), then I install and restore data for the big items. If you have a 32GB N7, you probably can be more careless with the deleting of big app data.
This way I get a clean start, loose nothing and have multple ways of going back if I need to, also I can take my time restoring stuff and still use my working older version until I am ready.
C5Longhorn said:
I'm fairly new to Android and the Nexus 7. I am unlocked, rooted, and have installed Ti Backup. I just recently received the OTA for 4.4.4 and installed it, and then manually loaded TWRP back and rerooted.
This doesn't seem like the cleanest install (maybe it's my OCD tendencies with hardware and software), so I'm wondering what is the best way to install Android updates? Should I reset to the factory image and then use Ti back up for all my apps? Is the way I proceeded just as good as other possible methods? My goal is to follow a plan that will support the 7 performing as best as possible.
Any info or opinions would be appreciated.
Thanks,
Rick
Click to expand...
Click to collapse
Well, i think it depends a bit on what kind of update it is. Usually the "smaller OTA updates (like 4.3.1 to 4.3.2) doesnt wipe your system, so all you have to do is re-root it again (if you want). All Apps and Data is kept. If the update is one that changes the Android Version like 4.1 to 4.3 (wich wont happen on the Nexus) then i would suggest a factory-reset before and maybe even after again, yes.
Off topic a bit: To be honest, i never bothered with backup systems because i somehow doesnt feel its a good idea but that is really my own thinking, im very aware that many ppl use backups successfully.
Games i play are usually saved on the server anyway, contacts, emails and all that are automatically there anyway if you use a google account and if your system is set to automatically restoe apps then all the apps get automatically downloaded again anyway.
Somehow i dont seem to use a single app that needs data to be backed up. And theres none that comes to my mind, besides savegames of non-server-saved games probably. But for that theres Helium. The cloud (be it "owncloud" or the official ones) saves me all this trouble with backups.
For the cleanest install I can think of (and usually do myself):
1. Grab latest factory image from Google and extract it so you're left with a folder with scripts and stuff (can be 4.4.4, or even L preview atm; folder should look similar to razor-lpv79)
2. Get platform-tools (either straight from Android SDK or from a trusted location (do not use a toolkit) ; make sure it's up-to-date, and for a good idea, add the executable path to PATH)
3. Boot N7 to Bootloader (power it off, hold vol down + power)
4. Unlock bootloader via fastboot oem unlock (confirm it on N7 with vol and power buttons)
5. Run flash-all.bat found in the factory image folder (fastboot executable either needs to be put into that folder, or you need it on PATH already)
6. Watch the tablet and wait for it to reboot, immediately when it reboots, hold vol down and go back to bootloader
7. Do fastboot oem lock to re-lock the bootloader
8. Boot to recovery
9. Clean Cache, then Data/Factory Reset (in that order)
10. Reboot
11. Profit
That process should ensure future updates work without issue or snag But of course you'd lose root. You probably don't have to re-lock the bootloader though.
espionage724 said:
For the cleanest install I can think of (and usually do myself):
1. Grab latest factory image from Google and extract it so you're left with a folder with scripts and stuff (can be 4.4.4, or even L preview atm; folder should look similar to razor-lpv79)
2. Get platform-tools (either straight from Android SDK or from a trusted location (do not use a toolkit) ; make sure it's up-to-date, and for a good idea, add the executable path to PATH)
3. Boot N7 to Bootloader (power it off, hold vol down + power)
4. Unlock bootloader via fastboot oem unlock (confirm it on N7 with vol and power buttons)
5. Run flash-all.bat found in the factory image folder (fastboot executable either needs to be put into that folder, or you need it on PATH already)
6. Watch the tablet and wait for it to reboot, immediately when it reboots, hold vol down and go back to bootloader
7. Do fastboot oem lock to re-lock the bootloader
8. Boot to recovery
9. Clean Cache, then Data/Factory Reset (in that order)
10. Reboot
11. Profit
That process should ensure future updates work without issue or snag But of course you'd lose root. You probably don't have to re-lock the bootloader though.
Click to expand...
Click to collapse
In fact, unless it's going back to the factory I'd recommend never relocking it.
mdamaged said:
In fact, unless it's going back to the factory I'd recommend never relocking it.
Click to expand...
Click to collapse
It's not really too much trouble to unlock it again, but if anything, re-locking it can be pretty nice from a security-standpoint.
I mainly just re-lock it just to keep that Google experience
espionage724 said:
It's not really too much trouble to unlock it again, but if anything, re-locking it can be pretty nice from a security-standpoint.
I mainly just re-lock it just to keep that Google experience
Click to expand...
Click to collapse
To each their own I guess.:good:
Thanks to all who responded. Good info and ideas on installs. I may end up doing a clean install and following the methods you all mentioned. Right now, I'm monitoring the performance to see if anything further is necessary.
Thanks,
Rick
espionage724 said:
It's not really too much trouble to unlock it again, but if anything, re-locking it can be pretty nice from a security-standpoint.
I mainly just re-lock it just to keep that Google experience
Click to expand...
Click to collapse
I agree that it's not too much trouble to unlock the bootloader BUT... you will completely wipe your entire device everytime you unlock the bootloader! There is only one way that I know of to get around that. "BootUnlocker for Nexus Devices" is supposed to be able to unlock the bootloader without wiping the device but for it to work you will have had to unlock the bootloader to gain root beforehand, then you can use the app to lock unlock. I've never used "BootUnlocker for Nexus Devices" so I can't make any claims as to how well it works or if it will continue to work after future updates. If you ever want to fastboot flash the factory image or parts of a factory image the bootloader will need to be unlocked. And as far as I know to flash images with a toolkit (I don't use any) like Wug's the bootloader needs to be unlocked. Unlocked bootloader from a security standpoint? You're absolutely right that there is a risk! IF your device physically ends up in someone else's possession. We do have the "Android Device Manager" now that gives the ability to locate and wipe our devices. And, I have an additional theft warranty provided by Ruger so I don't spend much time worrying about losing any devices. ; ) There are much bigger security risks from just being rooted and/or having "unknown sources" enabled, web exploits and sideloaded apps. Unless you leave your device completely stock and unrooted, relocking your bootloader can create a significant hurdle that needs to be overcome to solve problems, especially for inexperienced android users. For what it's not worth, just my 2 cents! ; )
Update: after doing some research and installing BootUnlocker it seems to work well! Sweet! I don't need it and prefer to just stay unlocked so I'm deleting the app. Downside of having a locked bootloader is if you can't boot up and want to flash the system or factory images you'll need to "fastboot oem unlock" which equals "wiped device"
C5Longhorn said:
I'm fairly new to Android and the Nexus 7. I am unlocked, rooted, and have installed Ti Backup. I just recently received the OTA for 4.4.4 and installed it, and then manually loaded TWRP back and rerooted.
This doesn't seem like the cleanest install (maybe it's my OCD tendencies with hardware and software), so I'm wondering what is the best way to install Android updates? Should I reset to the factory image and then use Ti back up for all my apps? Is the way I proceeded just as good as other possible methods? My goal is to follow a plan that will support the 7 performing as best as possible.
Any info or opinions would be appreciated.
Thanks,
Rick
Click to expand...
Click to collapse
I think you and I feel the same way about OTA updates. I've always felt that flashing the factory image will provide a much more consistent and reliable result. I'm not a big fan of using the OTA's but do use them occasionally for very small updates like 4.4.4. Usually the bigger OTA updates will fail because I have too many modified files in the system and because they are bigger I would rather flash the image anyway. Generally, for the most part, I will open the factory image and pull (extract) from there the specific images that were updated in the OTA and fastboot flash those. On the N7 only the system image was changed with the 4.4.4 update. The 4.4.3 update changed the boot and system images. You can either flash the images that are needed for the update individually or the whole factory image. Flashing the individual images will not wipe your storage, settings or user apps and the factory image Can also be flashed without wiping your storage, or losing your installed apps and settings. When you extract the factory image you will see;
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-ktu84p.zip
Inside the "image-razor-ktu84p.zip" is where you will see the individual images;
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
To flash the factory image without wiping data all you have to do is open up the 'flash-all.bat' with editpad lite or whatever notepad you use and remove the -w from the text. The -w flag will cause the userdata.img to be flashed which wipes your device. If you really want to make sure the os is clean you can do a factory reset with TWRP after flashing the images which will wipe the cache, data and dalvik and remove any settings but will leave your storage intact. I seldom do that though. If you are using a custom recovery it will be replaced with the stock recovery image when you flash the factory image which is why I generally flash the images separately. Not a big deal though because it only takes a few seconds to fastboot flash a custom recovery. My bootloader is always unlocked and I always have TWRP installed on my devices. Leaving TWRP installed gives the ability to flash an OTA that you sideloaded if you don't want to wait for it to get to your device. When you flash the system image, factory image or an OTA you will always lose the supersu binary which causes you to lose root. Before booting up after flashing the images you can go into your custom recovery and flash the supersu zip to regain root. Which is what I always do and I always leave a recent copy of the supersu zip on my devices. I always recommend learning how to use adb/fastboot, toolkits work fine for a lot of people but learning adb/fastboot is not hard and gives you more options and a better understanding of what is being done. A lot of problems you see posted here in the forums are from inexperienced users that are using toolkits. Just saying! ; )
Thanks for the response. I'm actually going back to just using adb/fastboot and flashing. I seem to run into more hiccups using toolkits that just a command line window.
Rick
I have not been able to update my shield tv 2015 16gb device to 5.2.
The device is rooted with latest 3.1.1 TWRP recovery. Each time I select upgrade with the stock settings it will reboot into recovery and won't update.
Does anyone have a link to the latest ROM or know where Nvidia stores the OTA file? I would rather flash the image my self if I can find get the ROM.
I'm sure this we'll help a few other people I can't be the only one with this issue. Need the 5.2 image not the 5.0.2 which is the previous version of Shield experience update.
you should not flash TWRP to your device reflash original recovery and remove su then try update again
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)
Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
.)
Click to expand...
Click to collapse
i didnt know that :good:
but if he has TWRP installed couldnt he format data pation from TWRP thus saving hours of thumb twiddling
Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)
Click to expand...
Click to collapse
Obviously thats a much longer and worse route.
afgok said:
you should not flash TWRP to your device reflash original recovery and remove su then try update again
Click to expand...
Click to collapse
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
On another thread looks like others are having this same issue with only this version 5.2.. ill just wait for the Dev Images to show up hopefully soon.
I unrooted but still got the same issue, it wont install. But I also have another issue, i can't restore my 2015 shield 16gb by using official recovery rom and official tutorials. It consistently fails to flash system.img and vendor.img by saying that the data is too large. The only way I got my system back was by flashing this file https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-ota-5-1-feb-17-zip-file-t3559062 through twrp
Diehardshorty said:
Obviously thats a much longer and worse route.
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.
Ichijoe said:
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.
Click to expand...
Click to collapse
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0
If you're rooted, the right answer is to wait for Nvidia to release the 5.2 image.
If you absolutely need 5.2 right now for some reason, several people said that doing a factory restore worked. Just unrooting and restoring stock recovery won't do it, you need to do a full restore.
Diehardshorty said:
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0
Click to expand...
Click to collapse
The Dev images are quite a bit different, and are also on an entirely different timeline to either the Preview, (Which I'm on), or the most current version.
But, yeah I could see how those would work. Alas mores the pitty that the rooted asspects of those Dev Images, only go as far as ADB, and not say a full /system wide root. Than again... It's probably for the best that way.
But, that doesn't really change the answer if you want / need to update (From root), than you are going to have to bite the big One, and run a Factory Reset. Which again, on the Pro, means a 2h+ reformating (zeroing out), of the /data Partition.
16gb version doesn't take as long to format but I've always remember flashing SuperSU.zip after ROM just incase. Short response for now at work.
Diehardshorty said:
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Use to be here:
/data/data/com.nvidia.ota/app_download
You obviously need root to reach that folder...
If i have time i will upload later this small OTA update to MEGA.
I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886
sammarbella said:
I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886
Click to expand...
Click to collapse
Sweet thanks I'll give that a try from the sounds of it it might not work but I'll give a shot after work. Thanks
No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS
Diehardshorty said:
No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS
Click to expand...
Click to collapse
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update
Cameron581 said:
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update
Click to expand...
Click to collapse
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.
Diehardshorty said:
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.
Click to expand...
Click to collapse
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.
Cameron581 said:
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.
Click to expand...
Click to collapse
Ahhhhh that missing point for "error 7".
So the new app bypass that problem!
Thanks for posting it. :good:
I have FB factory, flashed ROM's and nothing is sticking. Might be corrupt storage. I was wondering if there is a more thorough way to wipe/flash the phone so I can make a ROM/OS stick?
Have you tried a factory image with the -w as in wipe everything?
Sent from my Pixel XL using Tapatalk
Soooperstar said:
Have you tried a factory image with the -w as in wipe everything?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yes, I have done all of the typical things and I am having very, very bad luck. Out of the box, thinking is critical.
Fixed!
Scottay5150 said:
I have FB factory, flashed ROM's and nothing is sticking. Might be corrupt storage. I was wondering if there is a more thorough way to wipe/flash the phone so I can make a ROM/OS stick?
Click to expand...
Click to collapse
Fastboot format system, fastboot erase userdata, fastboot format cache. There was a guide somewhere someone had about clean flashing. I had an issue once but after totally wiping and a clean install of stock, I haven't had any issues since. Use the flash-all.exe to flash, idk if you flash your images separately, but flashing the zip as a whole through fastboot yielded better results for me. Also being sure that my adb.exe files were up to par. Also be sure to wipe both slots, as it might be slot b giving you problems. Google search should find you the right fastboot commands, I've forgot them off the top of my head. Of course if you're going to wipe you would need to back everything you need up.
Bryanx86 said:
Fastboot format system, fastboot erase userdata, fastboot format cache. There was a guide somewhere someone had about clean flashing. I had an issue once but after totally wiping and a clean install of stock, I haven't had any issues since. Use the flash-all.exe to flash, idk if you flash your images separately, but flashing the zip as a whole through fastboot yielded better results for me. Also being sure that my adb.exe files were up to par. Also be sure to wipe both slots, as it might be slot b giving you problems. Google search should find you the right fastboot commands, I've forgot them off the top of my head. Of course if you're going to wipe you would need to back everything you need up.
Click to expand...
Click to collapse
Yes, my SDK is up to date, from Google site. Interesting about flash-all.exe.
Fastboot format system
fastboot erase userdata
fastboot format cache
These were the commands you have used?
Anyone have beta how to wipe both a and b??
Does anyone want to link me to clean flashing?
Scottay5150 said:
Yes, my SDK is up to date, from Google site. Interesting about flash-all.exe.
Fastboot format system
fastboot erase userdata
fastboot format cache
These were the commands you have used?
Anyone have beta how to wipe both a and b??
Does anyone want to link me to clean flashing?
Click to expand...
Click to collapse
You need to go back to square one.. Asking questions like this lead me to believe you have absolutely no idea what you are doing and you need to leave things alone before further damaging your device...
stebomurkn420 said:
You need to go back to square one.. Asking questions like this lead me to believe you have absolutely no idea what you are doing and you need to leave things alone before further damaging your device...
Click to expand...
Click to collapse
OK folks. I want to apologize for my flooding of the forums attempting to repair my situation last week. Yes, I have been flashing for a long time without real complications. I haven't been on my ADHD meds for a while and that did not help me with the drama last week. Unfortunately my world like most of you is in my phone, I was panicked. Sorry about that.
Needless to say I needed other eyes on what I was doing for perspective sake. I went to my PC tech, luckily had personal flashing experiences with Android, Pixel even. We worked on it for about 6 hours in total. He couldn't get RR to work.
The issue was this after following the OP instructions. Once in the system I couldn't get the WiFi to connect with the phone, not being able to download whatever the phone was looking for. Google play services kept FC'ing. Google TTS kept FC'ing as well. I don't know if there is a fix or a forthcoming fix for this abnormal issue. I deleted data from the apps that were FC'ing and other Google that might be related. PS: not a RR issue I had this same issue with Benzo)
Unfortunately, we didn't save anything from the old RR setup because I couldn't be without a phone for another day. Any constructive thoughts would be welcomed.
I shall attempt to reinstall RR at some point to see if it works, or to get data to help the devs understand what might have happened or might had happened.
I am back on stock, not loving it that is for sure.
Scottay5150 said:
OK folks. I want to apologize for my flooding of the forums attempting to repair my situation last week. Yes, I have been flashing for a long time without real complications. I haven't been on my ADHD meds for a while and that did not help me with the drama last week. Unfortunately my world like most of you is in my phone, I was panicked. Sorry about that.
Needless to say I needed other eyes on what I was doing for perspective sake. I went to my PC tech, luckily had personal flashing experiences with Android, Pixel even. We worked on it for about 6 hours in total. He couldn't get RR to work.
The issue was this after following the OP instructions. Once in the system I couldn't get the WiFi to connect with the phone, not being able to download whatever the phone was looking for. Google play services kept FC'ing. Google TTS kept FC'ing as well. I don't know if there is a fix or a forthcoming fix for this abnormal issue. I deleted data from the apps that were FC'ing and other Google that might be related. PS: not a RR issue I had this same issue with Benzo)
Unfortunately, we didn't save anything from the old RR setup because I couldn't be without a phone for another day. Any constructive thoughts would be welcomed.
I shall attempt to reinstall RR at some point to see if it works, or to get data to help the devs understand what might have happened or might had happened.
I am back on stock, not loving it that is for sure.
Click to expand...
Click to collapse
Sounds to me like you used the wrong GApps. Or maybe used the wrong TWRP, or tried installing TWRP when you should have just booted it. Something like that.
borxnx said:
Sounds to me like you used the wrong GApps. Or maybe used the wrong TWRP, or tried installing TWRP when you should have just booted it. Something like that.
Click to expand...
Click to collapse
I wish I could say the wrong GAPPS, the version from the OP was used (others had issues as well), TWRP 3.2.0 again from the OP was installed per instructions. They were not. Not letting system boot up might have been the bigger issue. I shall never know.
New to the Moto Z2 play, moved to this from a Z2 force on Verizon after the shattershield started peeling. Anyway, there seems to be a lot of conflicting information here, and i'm struggling to actually nail down the process for root. My bootloader is already unlocked, however between several different versions of TWRP, Retus based phones vs Albus, ability to unroot and update if the system is modified, rooting with or without disabling encryption, countless different variants with different procedures, etc. i'm a little overwhelmed. Can anyone point me in the right direction of rooting my device (hopefully) WITHOUT losing all my data?
StATicxTW0T said:
New to the Moto Z2 play, moved to this from a Z2 force on Verizon after the shattershield started peeling. Anyway, there seems to be a lot of conflicting information here, and i'm struggling to actually nail down the process for root. My bootloader is already unlocked, however between several different versions of TWRP, Retus based phones vs Albus, ability to unroot and update if the system is modified, rooting with or without disabling encryption, countless different variants with different procedures, etc. i'm a little overwhelmed. Can anyone point me in the right direction of rooting my device (hopefully) WITHOUT losing all my data?
Click to expand...
Click to collapse
I'm about to buy the unlocked Moto Z2 Play from the Moto site (64GB variant... not sure of the model number) but have you checked out these threads?...
https://forum.xda-developers.com/showpost.php?p=75098899&postcount=40
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615/page3
allstar21369 said:
I'm about to buy the unlocked Moto Z2 Play from the Moto site (64GB variant... not sure of the model number) but have you checked out these threads?...
https://forum.xda-developers.com/showpost.php?p=75098899&postcount=40
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615/page3
Click to expand...
Click to collapse
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
I have a rooted XT1710-01, also. If you are going to install Xposed and Gravity Box, I recommend not updating Magisk, above v14. After v15 and now v16, I have had issues with Automate It app and Tasker rules not working, until I uninstalled Xposed.
Downgrading Magisk versions requires flashing your stock ROM and basically starting over.
Motorola has not posted firmware for this model.
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
So glad to see someone have it working and with a clear guide. I'm going to buy the phone this week.
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
I just wanted to let everyone know that the guide posted in that post worked for me perfectly. I had an XT1710-01 that I had unlocked the bootloader before but stopped there. Then I finally wanted to root it, and ran into everything the OP ran into - just so many different guides and versions of TWRP/Magisk not working with the Z2 Play, it was hard to nail down the exact versions of everything I needed and make sure I didn't flash an incompatible version or something. I found that same guide a few days ago as well but never did it until today, and can confirm it works. I already had my bootloader unlocked and just did the rooting portion and all my data was saved (but I wasn't too worried about my data honestly, it's all backed up anyway).
And a special thanks to OP for coming back and posting his solution. Nothing is more frustrating than searching for a problem online, finding a hit on your exact problem in a thread that was posted years ago, and then no solution is ever posted in that thread. So good job. :good:
Johmama said:
I just wanted to let everyone know that the guide posted in that post worked for me perfectly. I had an XT1710-01 that I had unlocked the bootloader before but stopped there. Then I finally wanted to root it, and ran into everything the OP ran into - just so many different guides and versions of TWRP/Magisk not working with the Z2 Play, it was hard to nail down the exact versions of everything I needed and make sure I didn't flash an incompatible version or something. I found that same guide a few days ago as well but never did it until today, and can confirm it works. I already had my bootloader unlocked and just did the rooting portion and all my data was saved (but I wasn't too worried about my data honestly, it's all backed up anyway).
And a special thanks to OP for coming back and posting his solution. Nothing is more frustrating than searching for a problem online, finding a hit on your exact problem in a thread that was posted years ago, and then no solution is ever posted in that thread. So good job. :good:
Click to expand...
Click to collapse
I just received my Z2 Play, unlocked the bootloader, and am about to flash the custom TWRP (albus_twrp.img) posted in the guide linked above... but the guide never says to "flash" TWRP, it just says to "boot" with TWRP and also "Enter your FBE password: it must work! (turn off screen and turn it back on if not responsive)"...
I'm not 100% sure what to do here. Should I boot TWRP first, do a full backup and then flash TWRP? I don't want to wipe it.
And what is this FBE (File-Based Encryption) password? I've never set one and don't want everything encrypted.
allstar21369 said:
I just received my Z2 Play, unlocked the bootloader, and am about to flash the custom TWRP (albus_twrp.img) posted in the guide linked above... but the guide never says to "flash" TWRP, it just says to "boot" with TWRP and also "Enter your FBE password: it must work! (turn off screen and turn it back on if not responsive)"...
I'm not 100% sure what to do here. Should I boot TWRP first, do a full backup and then flash TWRP? I don't want to wipe it.
And what is this FBE (File-Based Encryption) password? I've never set one and don't want everything encrypted.
Click to expand...
Click to collapse
I didn't flash TWRP on my phone. I think I tried it once and it failed for some reason, so I just followed the guide of booting into TWRP, backing up my phone, and pulling the backup. Should be okay for what I need, in case of a failure I will have a backup somewhere and can recover the device. But yes, I'd at least boot into TWRP, then backup your device like in that guide so you have a backup. Flashing it is up to you, I've always flashed a custom recovery but on this phone I'm keeping the original recovery so I can get an OTA. On my Nexus devices I don't care about OTA because I just flash ROMs all the time so it's no big deal.
The FBE password as far as I can tell is the 4 or 5 digit PIN number you are asked to input upon a fresh wipe of your device to set as a password. I have my phone set up to use my fingerprint to unlock the phone, and if that fails it will ask for my PIN, which is the same as the FBE of mine. I used that same number in TWRP when it asks for a password to unencrypt the data and it worked. As far as turning off encryption, I'm not sure if there's a way to do that. There could be, but to turn it off, it wipes your data as a security measure.
Johmama said:
so I just followed the guide of booting into TWRP, backing up my phone, and pulling the backup. Should be okay for what I need, in case of a failure I will have a backup somewhere and can recover the device. But yes, I'd at least boot into TWRP, then backup your device like in that guide so you have a backup.
Click to expand...
Click to collapse
Yeah, I can't backup my ROM most likely because I don't have an FBE password. When I go to backup my ROM in TWRP it fails.
Johmama said:
The FBE password as far as I can tell is the 4 or 5 digit PIN number you are asked to input upon a fresh wipe of your device to set as a password. I have my phone set up to use my fingerprint to unlock the phone, and if that fails it will ask for my PIN, which is the same as the FBE of mine. I used that same number in TWRP when it asks for a password to unencrypt the data and it worked.
Click to expand...
Click to collapse
I tried entering my unlock code and the pin I created but neither worked for my FBE password. I don't ever remember being asked to enter a password when setting up my device. I suppose this means I'll have to wipe data and then setup an FBE password.
allstar21369 said:
I tried entering my unlock code and the pin I created but neither worked for my FBE password. I don't ever remember being asked to enter a password when setting up my device. I suppose this means I'll have to wipe data and then setup an FBE password.
Click to expand...
Click to collapse
If it helps at all, the first time I tried it also didn't work for me and I did end up wiping my phone for other reasons before I came back and tried that guide again and it worked. I thought I set up the PIN they're talking about the first time around but I did have troubles in TWRP before the first wipe of my data. I would just boot up the phone regularly, plug it in to your computer, and try to grab any files you need and wipe it. I know that isn't the answer you're looking for, but it's all I can give I guess. Once you reset, hopefully they'll prompt you to make a PIN during the setup process and that should be the FBE password. Then follow the guide. I hope you get it man.
Oh, and to a note to you and everyone reading this, I booted to TWRP 3.2.1-0-albus and Magisk-v14.0. Dunno if it's just rumors or not but I heard the newer versions of Magisk might not work with the Z2 Play past version 14. Dunno if that's true but v14.0 worked for me.
Johmama said:
If it helps at all, the first time I tried it also didn't work for me and I did end up wiping my phone for other reasons before I came back and tried that guide again and it worked. I thought I set up the PIN they're talking about the first time around but I did have troubles in TWRP before the first wipe of my data. I would just boot up the phone regularly, plug it in to your computer, and try to grab any files you need and wipe it. I know that isn't the answer you're looking for, but it's all I can give I guess. Once you reset, hopefully they'll prompt you to make a PIN during the setup process and that should be the FBE password. Then follow the guide. I hope you get it man.
Oh, and to a note to you and everyone reading this, I booted to TWRP 3.2.1-0-albus and Magisk-v14.0. Dunno if it's just rumors or not but I heard the newer versions of Magisk might not work with the Z2 Play past version 14. Dunno if that's true but v14.0 worked for me.
Click to expand...
Click to collapse
Okay. I just wiped and re-set up everything and still no FBE password was asked for OR works when I go into TWRP. I'm using TWRP 3.1.1-0... I suppose I'll try it all again using TWRP 3.2.1-0-albus after deleting data.
*Edit: I did exactly what I just said I was doing booted TWRP 3.2.1-0-albus instead of 3.1.1-0 and when I it booted up and asked me for a decryption password I entered the pin I set up previously and it has been stuck at the "Mount, Trying Decryption" screen for a long time... but it's not frozen. It says "Updating partition details... ...done
Unable to mount storage
Full SELinux support is present.
Data successfully decrypted, new block device: '/dev
/block/dm-0'
Updating partition details...
...done"
And the progress bar/thing at the bottom is still animated like it's working... no forward or back buttons or anything and turning off/on the screen hasn't done anything... not really sure what to do here... I don't want to unplug it and brick my phone or force it off...
*Edit 2:
I now have it all sorted out.
TWRP never finished trying to decrypt data so I long pressed the power button and eventually went here -> https://forum.xda-developers.com/z2-play/development/twrp-moto-z2-play-t3729531 , downloaded "twrp_albus_3.1.2_r18_64.img" and in adb used the command:
fastboot boot twrp_albus_3.1.2_r18_64.img
This TWRP looks a bit different than all of the others but it let me boot up and use my recently created PIN code to actually decrypt my data and make a full backup. After that I just installed Magisk (the latest one, 16.4) as indicated in this guide -> https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792 and everything is fine. I never even flashed TWRP, just booted it.
Just curious what you guys have done about getting OTA updates since you've rooted and installed Magisk.
Have @allstar21369 or @pizza_pablo had the chance to figure out the update process?
I'm currently trying to navigate the Magisk uninstall --> OTA update process and could use some insight if either of you guys have any to share.
joefuf said:
Just curious what you guys have done about getting OTA updates since you've rooted and installed Magisk.
Have @allstar21369 or @pizza_pablo had the chance to figure out the update process?
I'm currently trying to navigate the Magisk uninstall --> OTA update process and could use some insight if either of you guys have any to share.
Click to expand...
Click to collapse
I didn't want updates, especially the oreo "upgrade".
pizza_pablo said:
I didn't want updates, especially the oreo "upgrade".
Click to expand...
Click to collapse
Hmm, didn't even think about just sticking on what works... Did Oreo give people some issues?
Since this was Day 1 with the new phone, I was just trying to get up to speed and probably sit on one version until I had compatibility issues with something, but everything just works.
joefuf said:
Hmm, didn't even think about just sticking on what works... Did Oreo give people some issues?
Since this was Day 1 with the new phone, I was just trying to get up to speed and probably sit on one version until I had compatibility issues with something, but everything just works.
Click to expand...
Click to collapse
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Double - double \_0_/
pizza_pablo said:
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Click to expand...
Click to collapse
I feel exactly the same way. No benefits for me. I don't want the bright white interface and I would never use the "Picture in Picture" (or floating video) feature (and if I did want that there are a couple apps for Nougat that do it).
But If I do decide I want it and give upgrading a shot I'll definitely post it here.
pizza_pablo said:
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Click to expand...
Click to collapse
Yeah, very understandable. It really is superfluous to the general experience.
allstar21369 said:
I feel exactly the same way. No benefits for me. I don't want the bright white interface and I would never use the "Picture in Picture" (or floating video) feature (and if I did want that there are a couple apps for Nougat that do it).
But If I do decide I want it and give upgrading a shot I'll definitely post it here.
Click to expand...
Click to collapse
Thank you sir! Keep me posted. I'm posting everywhere right now to learn the new methods so I know if there ever comes a time. This is my first phone since my Motorola Droid 4. Back then it was one click root, install and run Safestrap apk to get custom recovery, boot into custom recovery and flash zips to your heart's content. I'm sure this will be as "simple" once I learn, but it's pretty daunting in prospect.