Related
I am in the process downgrading my Tmobile G2.
I got the # , ok
I got the version changed, ok
I got the temp root (maybe).
But once I got the temp root and trying to backup.
The apps says I don't have root access.
It means after I pushed busybox ,etc ,ect. I click the backup apps, the backup apps say good to go. But even I reload the apps the 2nd time. It will show I don't have root access.
But I still have the # sign.
I checked the forum as someone else had the same problem, but I did not find the answer.
Does anyone have some suggestion?
Thanks
be sure to disable the fastboot option. turn your phone off, pull the battery and leave it like this for a minute... then start again
hoffmas said:
be sure to disable the fastboot option. turn your phone off, pull the battery and leave it like this for a minute... then start again
Click to expand...
Click to collapse
I got the same trouble with my Desire Z. You can see my question near the the week ago. And advice was the same, but it didn't help. I think temporary root was honest but may be backup application managed to destroy some reserved memory for root, i don't know. I couldn't to backup system either MyBackup Pro or Titanium.
So I can't rooting my phone.
I will very glad if anybody help me and you.
sure you can root your phone. if the backup doesn´t work just skip it.
"If you have nothing to back up or don't care to back anything up, proceed to the next section." (...from the guide)
I agree
hoffmas said:
sure you can root your phone. if the backup doesn´t work just skip it.
"If you have nothing to back up or don't care to back anything up, proceed to the next section." (...from the guide)
Click to expand...
Click to collapse
After rooting when I tried to backup the stock rom even I got some errors.
"Can't mount..some something"
Googled for it a lot and most of them indirectly said the phone might be bricked. Since I had nothing else to do I continued with the next step i.e. installing custom rom (cynogemod in my case) and everything turned out fine.
I am not recommending that you skip the backup process, if you can find anything then surely take a backup else skip it and continue.
hoffmas said:
if the backup doesn´t work just skip it.
Click to expand...
Click to collapse
I afraid that skipping backup procedure before rooting is not a better advice.
I've bought my device over a year ago and now it has a lot of useful app and files. I usually use MyBackupPro to store non-system data without rooting.
However, it seems to me that's not enough, or am I wrong?
I think that after the rooting and replacement of the firmware I get a new, empty device without my usual things.
Is it enough or not after rooting to restore only the non-system data to continue to use the device as before plus root ?
Thanks.
yes =) just backup your apps and restore afterwards... you wont loose any sdcard content while rooting (except for goldcard). sure you can´t backup system apps, but this doesn´t make sense anyway because they wont work with your new rom
backup while rooting could be important for warranty issues... but actually isn´t really cause you can use a wwe ruu.
My stupid mates managed to lock my phone under the "too many attempts" thing... I REFUSE to wipe my phone... all im trying to do is turn on either wifi or data connection through adb using key events
i (think) i know the settings bit is
adb shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
that worked for gingerbread... i dont know if ics has changed
but i need the keyevents for it
i HAVE tried sqlite but i get the responce
"CAnnot update file - read only"
ive tried
chmod777 (whatever...)/settings.db
but it doesnt affect it
Worst case, you can run a nandroid, wipe, then use Titanium backup (You might need the pro version) to restore all your apps+data from your nandroid backup.
I can't provide any support for what you're trying to do, that is just a possible alternative.
Bump.... please help... i want my phone back :/
Just so you know, what I posted will only take about 10-15 minutes, and you won't lose a thing. It's like re-installing an OS, then importing all apps+settings from a backup.
Edit: Unless you have stock recovery installed, then this method is a no-go.
Ryands991 said:
Just so you know, what I posted will only take about 10-15 minutes, and you won't lose a thing. It's like re-installing an OS, then importing all apps+settings from a backup.
Edit: Unless you have stock recovery installed, then this method is a no-go.
Click to expand...
Click to collapse
It's ok i did it, but thanks
I feel like I should know how to do this and I just can't think right now...
I have 8.0 and the latest TWRP installed. Root with Magisk as well. I want to update to 8.1 but I don't want to have to factory reset the phone by flashing 8.1 to it and then reflashing root & TWRP. There's a way to do this that I'm not thinking of, right?
I read another post about using FlashFire but regardless of where I put the factory image, the app doesn't see it. So I feel like I'm at a loss right now.
Am I missing something? Thanks in advance!
WyldOne91 said:
I feel like I should know how to do this and I just can't think right now...
I have 8.0 and the latest TWRP installed. Root with Magisk as well. I want to update to 8.1 but I don't want to have to factory reset the phone by flashing 8.1 to it and then reflashing root & TWRP. There's a way to do this that I'm not thinking of, right?
I read another post about using FlashFire but regardless of where I put the factory image, the app doesn't see it. So I feel like I'm at a loss right now.
Am I missing something? Thanks in advance!
Click to expand...
Click to collapse
This is how I upgraded to 8.1, my setup before I upgraded was the same as yours.
1. Bootloader and unlock_critical both unlocked?
2. Download and extract the factory image, and place all contents in your SDK platform tools folder.
3. Edit the flash-all.bat file and remove the -w in the last line of code. (This prevents your data from being wiped)
4. Double click the flash-all.bat file to start the process. It'll take a little while, so be patient.
5. Once it's done, get back to bootloader mode.
6. Flash the twrp.img file. This will take you to temporary twrp.
7. Once in twrp, flash the twrp.zip, then flash custom kernel.zip(optional) then flash your magisk.zip.
8. Reboot and done.
Couple of caveats, make sure your using a good USB transfer cable, and it's recommended to remove your finger print and/or password/pin, and uninstall any themes you have installed. Hope all goes well for you :good:
Badger50 said:
This is how I upgraded to 8.1, my setup before I upgraded was the same as yours.
1. Bootloader and unlock_critical both unlocked?
2. Download and extract the factory image, and place all contents in your SDK platform tools folder.
3. Edit the flash-all.bat file and remove the -w in the last line of code. (This prevents your data from being wiped)
4. Double click the flash-all.bat file to start the process. It'll take a little while, so be patient.
5. Once it's done, get back to bootloader mode.
6. Flash the twrp.img file. This will take you to temporary twrp.
7. Once in twrp, flash the twrp.zip, then flash custom kernel.zip(optional) then flash your magisk.zip.
8. Reboot and done.
Couple of caveats, make sure your using a good USB transfer cable, and it's recommended to remove your finger print and/or password/pin, and uninstall any themes you have installed. Hope all goes well for you :good:
Click to expand...
Click to collapse
Cool thank you I will give this a shot later tonight! One question, what is "unlock_critical?" I haven't seen that mentioned anywhere else before.
WyldOne91 said:
Cool thank you I will give this a shot later tonight! One question, what is "unlock_critical?" I haven't seen that mentioned anywhere else before.
Click to expand...
Click to collapse
The pic is from the Google factory image page. Unlock_critical must be performed on the P2XL to allow the bootloader to be updated with future monthly security or software updates. This does not apply to the standard P2. Be advised, this WILL wipe your phone. However, you really don't have much choice if you want to flash monthly factory images.
Badger50 said:
The pic is from the Google factory image page. Unlock_critical must be performed on the P2XL to allow the bootloader to be updated with future monthly security or software updates. This does not apply to the standard P2. Be advised, this WILL wipe your phone. However, you really don't have much choice if you want to flash monthly factory images.
Click to expand...
Click to collapse
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
WyldOne91 said:
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
Click to expand...
Click to collapse
No problem my friend. There's a lot to learn on these new pixel devices. There are plenty threads on these forum with tons of info on whatever topic you may have questions about. Just takes time, patience, lots of reading, and a willingness to learn :good:
WyldOne91 said:
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
Click to expand...
Click to collapse
Since you are rooted, and already have the mindset that all is or will be lost you have the opportunity to try a couple options that if fail nothing lost...
After doing away with screen security and any themes, do Full backup in TWRP and also use TiBu to back up all your apps and then move them off the phone until after you do your thing.
After you do the critical unlock and get 8.1 installed and rooted you could try restoring the TWRP data partition and see what happens. Worst case it's either not booting or just acting funky. Do a factory wipe and not much lost.
Or... Use TiBu to save some time restoring all your apps. While I have had pretty good luck with restoring data on most apps, a few either won't restore or are boned in some way. Some other folks had a really hard time with restoring data so maybe just restore the apps without data. I run over 100 apps and have been through some version of this many times while playing around. With my crappy internet out here in the boonies it took 4 hours for google to restore all my apps and that's with hardly no data. It took about 20 minutes to restore most everything through TiBu. I would not restore data in the big initial bulk restore but instead go back and cherry pick the data restore on the things you need.
Again worst case all lost but you assumed that anyway and maybe you can save some time and effort if either option works.
Badger50 said:
No problem my friend. There's a lot to learn on these new pixel devices. There are plenty threads on these forum with tons of info on whatever topic you may have questions about. Just takes time, patience, lots of reading, and a willingness to learn :good:
Click to expand...
Click to collapse
Yeah for sure. I'm always willing to learn!
CyberpodS2 said:
Since you are rooted, and already have the mindset that all is or will be lost you have the opportunity to try a couple options that if fail nothing lost...
After doing away with screen security and any themes, do Full backup in TWRP and also use TiBu to back up all your apps and then move them off the phone until after you do your thing.
After you do the critical unlock and get 8.1 installed and rooted you could try restoring the TWRP data partition and see what happens. Worst case it's either not booting or just acting funky. Do a factory wipe and not much lost.
Or... Use TiBu to save some time restoring all your apps. While I have had pretty good luck with restoring data on most apps, a few either won't restore or are boned in some way. Some other folks had a really hard time with restoring data so maybe just restore the apps without data. I run over 100 apps and have been through some version of this many times while playing around. With my crappy internet out here in the boonies it took 4 hours for google to restore all my apps and that's with hardly no data. It took about 20 minutes to restore most everything through TiBu. I would not restore data in the big initial bulk restore but instead go back and cherry pick the data restore on the things you need.
Again worst case all lost but you assumed that anyway and maybe you can save some time and effort if either option works.
Click to expand...
Click to collapse
Yeah I actually already ran a backup with Titanium Backup and moved it to my PC last night just in case I did something stupid haha but I appreciate the tips!
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.
I tried backup and restore on POCO F3 and I think it was successful on A11 but I dont think restore ever worked since A12. Always had error 255 at the beginning of restoring data partition. Has anyone been successful restoring a backup of android 13?
Aserar said:
I tried backup and restore on POCO F3 and I think it was successful on A11 but I dont think restore ever worked since A12. Always had error 255 at the beginning of restoring data partition. Has anyone been successful restoring a backup of android 13?
Click to expand...
Click to collapse
Of course. Backup and restore work fine on OrangeFox.
Bit unrelated, but I always use Swift Backup for backing up apps+appdata. It can backup other things as well.
Requires Root, but you can always uninstall Magisk Root
DarthJabba9 said:
Of course. Backup and restore work fine on OrangeFox.
Click to expand...
Click to collapse
Both OFX and TW failed me at restore I can't think of any reason why if it's working with others. Do you remove screen lock before backing up? Never had to before but it's the only thing I could think of
cyanGalaxy said:
Bit unrelated, but I always use Swift Backup for backing up apps+appdata. It can backup other things as well.
Requires Root, but you can always uninstall Magisk Root
Click to expand...
Click to collapse
Yeah I do a swift backup also messages call log all of it but setting up the rest of the phone, logging back into accounts, is a pain, plus I always find an app or something that I forgot to refresh its backup. Nothing is like nand backup if you're testing new rom and might just go back
Aserar said:
Both OFX and TW failed me at restore I can't think of any reason why if it's working with others. Do you remove screen lock before backing up? Never had to before but it's the only thing I could think of
Click to expand...
Click to collapse
Possibly a result of user error. If you explain the process that you went through in order to restore the backups, and provide logs of the restore process, then I might be able to comment.
And you might want to read this wiki very carefully.
DarthJabba9 said:
Possibly a result of user error. If you explain the process that you went through in order to restore the backups, and provide logs of the restore process, then I might be able to comment.
And you might want to read this wiki very carefully.
Click to expand...
Click to collapse
Oh I've gone through the ofx wiki before with no success. It could be the screen lock on EU A13 roms. I had the issue two times then I gave up on backing up roms. I didn't care to save a log sadly bc I was in a hurry to get the phone working again. The restore process was straight forward. Restore from OTG. It starts normally and as soon as it hits restoring /data it ends with error 255. It doesn't start restoring data then fails after a while. It fails instantly as soon as restore data partition appears. I'll try without screen lock if it still fails I'll send you the log. Thank you for your hard work though
Aserar said:
Oh I've went through the ofx wiki before with no success. It could be the screen lock on EU A13 roms. I had the issue two times then I gave up on backing up roms. I didn't care to save a log sadly bc I was in a hurry to get the phone working again. The restore process was straight forward. Restore from OTG. It starts normally and as soon as it hits restoring /data it ends with error 255. It doesn't start restoring data then fails after a while. It fails instantly as soon as restore data partition appears. I'll try without screen lock if it still fails I'll send you the log. Thank you for your hard work though
Click to expand...
Click to collapse
1. Idk about EU. But I have backed up and restored stock MIUI 14 many times, with no problem.
2. "Error 255" is always accompanied by an explanatory message in the recovery logs, which will show what caused the error.
3. Firstly, ensure that your OrangeFox is actually up-to-date (ie, that you are using the latest release).
4. Whether or not you have a screenlock before making the backup should not affect anything (as long as there is no screenlock set up at the time of restoring the backup). The lockscreen PIN/password is not included in the backups.
DarthJabba9 said:
1. Idk about EU. But I have backed up and restored stock MIUI 14 many times, with no problem.
2. "Error 255" is always accompanied by an explanatory message in the recovery logs, which will show what caused the error.
3. Firstly, ensure that your OrangeFox is actually up-to-date (ie, that you are using the latest release).
4. Whether or not you have a screenlock before making the backup should not affect anything (as long as there is no screenlock set up at the time of restoring the backup). The lockscreen PIN/password is not included in the backups.
Click to expand...
Click to collapse
Yeah screen lock was never an issue before but it is the only thing I could think of. It could be something with EU. And yes I keep recovery up to date even when I don't switch roms. I made a backup of AOSP rom that I will probably restore soon. I'll keep you updated if the issue persists.
Aserar said:
Yeah screen lock was never an issue before but it is the only thing I could think of. It could be something with EU. And yes I keep recovery up to date even when I don't switch roms. I made a backup of AOSP rom that I will probably restore soon. I'll keep you updated if the issue persists.
Click to expand...
Click to collapse
Well, I have now made backups and restores of the latest EU ROM (14.0.6.0) - boot and data partitions - without any problem (both with and without screen locks - obviously there must be no lockscreen PIN/password when restoring).
DarthJabba9 said:
Well, I have now made backups and restores of the latest EU ROM (14.0.6.0) - boot and data partitions - without any problem (both with and without screen locks - obviously there must be no lockscreen PIN/password when restoring).
Click to expand...
Click to collapse
And I restored my AOSP backup with no errors! I wish I hadn't deleted my EU backup that I got the error with. The EU rom I had was the latest weekly release V14.0.23 bc the official release had issues but I doubt its that. I'm at a loss :/
Aserar said:
And I restored my AOSP backup with no errors! I wish I hadn't deleted my EU backup that I got the error with. The EU rom I had was the latest weekly release V14.0.23 bc the official release had issues but I doubt its that. I'm at a loss :/
Click to expand...
Click to collapse
Do you have a link for that release?
Sorry for also deviating, just my two pennies worth,
I moved away from Migrate-GPE and Swift backup and have been using DataBackup.apk, this also requires root.
As usual DB saves your Apps and there Data, you also have the option to save Media Folders, DCIM, Download, Music, Pictures, Folders, i also save these to my Usb Stick using a OTG adaptor, DataBackup can be found is my "Temporary Recovery" folder.
DarthJabba9 said:
Do you have a link for that release?
Click to expand...
Click to collapse
Honestly I can't be sure of the exact release since its weekly. I looked it up and I can narrow it down to like 3 or 4 releases but it could be this one
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-WEEKLY-RELEASES/V14.0.23.4.10.DEV/xiaomi.eu_multi_HMK40_POCOF3_V14.0.23.4.10.DEV_v14-13.zip/download
johnr64 said:
Sorry for also deviating, just my two pennies worth,
I moved away from Migrate-GPE and Swift backup and have been using DataBackup.apk, this also requires root.
Click to expand...
Click to collapse
Is this on the Play Store?
johnr64 said:
As usual DB saves your Apps and there Data, you also have the option to save Media Folders, DCIM, Download, Music, Pictures, Folders, i also save these to my Usb Stick using a OTG adaptor, DataBackup can be found is my "Temporary Recovery" folder.
Click to expand...
Click to collapse
Having an alternative backup plan is good. But I have always found nandroid backups sufficient - as long as you know what you're doing.
Aserar said:
Honestly I can't be sure of the exact release since its weekly. I looked it up and I can narrow it down to like 3 or 4 releases but it could be this one
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-WEEKLY-RELEASES/V14.0.23.4.10.DEV/xiaomi.eu_multi_HMK40_POCOF3_V14.0.23.4.10.DEV_v14-13.zip/download
Click to expand...
Click to collapse
I have backed up and restored this release as well, with no problem. I have satisfied myself (again) that there is no problem with backup/restore in OrangeFox Recovery, so, for me, this investigation is concluded.
DarthJabba9 said:
I have backed up and restored this release as well, with no problem. I have satisfied myself (again) that there is no problem with backup/restore in OrangeFox Recovery, so, for me, this investigation is concluded.
Click to expand...
Click to collapse
Lol there was no need for investigating my friend! The point of the thread was to see if its generally working with others and so eliminate it as the reason for the fail.
DarthJabba9 said:
Is this on the Play Store?
Having an alternative backup plan is good. But I have always found nandroid backups sufficient - as long as you know what you're doing.
Click to expand...
Click to collapse
Sorry for not getting back sooner,
I found DataBackup while watching youtube videos "Like You Do",
the source is on GitHub
Aserar said:
Lol there was no need for investigating my friend! The point of the thread was to see if its generally working with others and so eliminate it as the reason for the fail.
Click to expand...
Click to collapse
It's no big deal. I always try to investigate problems, since they might possibly point to a problem in the recovery.
Same here. Since a12 that nandroid gives error on restoring. After that I don't count with that anymore. Ive been relying on Google to restore some apps, and on swift backup to restore the ones that are out of ps.
Before I was using migrate, but have put it aside, since the last time I've got error on zip file and so unable to restore my apps (a real pita). Swift have working flawlessly, and with the advantage of restore app settings too.