Hello,
I ran into a couple of problems, because my last phone was an LG G5 and had no a/b slots, so I'm new to this. I did read lots, and found that some folks say things about data encryption etc. But the version of orangefox we have for munch (thanks! @iscle for ofox and @M1LL3R for twrp) supports (de)crypt DATA. I managed to do a full backup of all partitions. But I am asking now if someone tried to restore a backup, yet? Somehow I messed up the OS, I got to "rescue party" reboot loop / boot to recovery - twice - no fun, google it. Sort of fixed it 2nd time by choosing other slot to boot, but magisk is gone. So now, because I need the phone in the next few weeks daily and don't have time to do a full new flash of OS, I don't dare to restore the backup right now in case something goes wrong.
When I have time, I will flash Poco firmware and do full reset and flash custom rom again, but I can't right now. So any information is very much appreciated!
DidierMoulin said:
So any information is very much appreciated!
Click to expand...
Click to collapse
I made backup using and twrp and orangefox: System, boot, data. Then immediately restored the data - the phone did not turn on. Made backup else time. Format data - restore data, don't turn on. Phone freezes on the miui logo. I don’t know what is the problem, I couldn’t restore using backup copy.
Thank you @Dimon909. I found time and trried it, too. Just freezes at boot screen (in this case the evo x boot logo) with strange colors at logon screen. Maybe something wrong with DATA. Recovery works afterwards, though. Maybe it's necessary to switch slots after restoring? Or before, but wouldn't make any sense, I guess.
DidierMoulin said:
Maybe something wrong with DATA. Maybe it's necessary to switch slots after restoring?
Click to expand...
Click to collapse
Backup of data was made several times. There cant be errors.
If I saw that the system was installed at slot A, I installed backup in the same partition. If in B - switched to B. It did not help. Seems TWRP has not been completed. And i cant move, delete system fails (ex. any .apk in system_root/system/app). System is only read. Some protection installed ?
Maybe it's all because data is encryption?
That's what I ment, some problems with restoring data (not because of wrong backup) but while restoring or booting, maybe because of encryption, like you said. though after I flashed the same rom or an update of it several times, both slots (a/b) should have contained the same decryption key, I guess.
I didn't pay attention to that, but if you switched to the right slot, then there's a different problem. Next time I'll check if it's slot related, by using both slots to restore, one after another and try to boot either.
What surprises me, is that twrp (or ofox) work with encryption and that I restored whitout changing encryption key on data (at least I think so, maybe even a new dirty rom flash does something?).
it's a problem of recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes, I read that, too. But it says:
* Restoring data backup in MIUI will result in a bootloop 100% of times.
Click to expand...
Click to collapse
I didn't have MIUI left on my device, afaik. So did you restore DATA from any custom rom, yet?
DidierMoulin said:
Yes, I read that, too. But it says....
Click to expand...
Click to collapse
maybe the creator of orangefox tried to restore data only on miui?
I tried on evolution ROM - bootloop.
But new SparkOs data can restore from backup.
Dimon909 said:
maybe the creator of orangefox tried to restore data only on miui?
I tried on evolution ROM - bootloop.
But new SparkOs data can restore from backup.
Click to expand...
Click to collapse
Ha ha, so I am on evolution now, but don't want to try really if it works ...
DidierMoulin said:
Ha ha, so I am on evolution now, but don't want to try really if it works ...
Click to expand...
Click to collapse
And don't need try. After restoring data of SparkOS the phone turned on, but the data became encrypted (hieroglyphs)
Dimon909 said:
And don't need try. After restoring data of SparkOS the phone turned on, but the data became encrypted (hieroglyphs)
Click to expand...
Click to collapse
Here https://orangefox.download/release/634aea7f3c05f43c193c2c92/buildnotes it says to restart the phones once or twice via power button. If I remember correctly it did it even three times (reboot), but that was with an older version of ofox and evolution, still didn't work.
Related
I just attempted to flash my Note 2, and install Jellbomb w/ Aroma. All went well, with status code of 0, but when I restarted my device, I got the following screen:
Encryption Failed
Unable to complete encryption due to interruption. Perform factory data reset (erasing all your data) before use. After resetting, try encrypting device again.
Click to expand...
Click to collapse
Edit: I am now aware that this occurs of what ROM I install. *Got the same problem, after installing LabRats 1.0.
I am able to wipe the device, but this does not help. I get the same message on boot-up.
Is there a way to disable encryption to bypass this screen so that I can use the newly-installed ROM?
Thanks in advance.
ForgottenSolstace said:
I just attempted to flash my Note 2, and install Jellbomb w/ Aroma. All went well, with status code of 0, but when I restarted my device, I got the following screen:
Edit: I am now aware that this occurs of what ROM I install. *Got the same problem, after installing LabRats 1.0.
I am able to wipe the device, but this does not help. I get the same message on boot-up.
Is there a way to disable encryption to bypass this screen so that I can use the newly-installed ROM?
Thanks in advance.
Click to expand...
Click to collapse
I can tell you it's not a Lab Rats issue, and as I keep up with jelly bomb its not a reported issue there either. Do a one click and start over.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ForgottenSolstace said:
Is there a way to disable encryption to bypass this screen so that I can use the newly-installed ROM?
Click to expand...
Click to collapse
This is not a ROM issue. The problem you're describing happens when you've encrypted your device, and did not undo the encryption before flashing a new ROM. The fix is easy... Boot into TWRP and go into the WIPE menu. One of the wipe options will warn you that you're about to delete the full internal data partition, removing encryption. Do that, then re-flash the the ROM.
Sent from my SPH-L900 using xda app-developers app
Didn't Work
swalter718 said:
This is not a ROM issue. The problem you're describing happens when you've encrypted your device, and did not undo the encryption before flashing a new ROM. The fix is easy... Boot into TWRP and go into the WIPE menu. One of the wipe options will warn you that you're about to delete the full internal data partition, removing encryption. Do that, then re-flash the the ROM.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but I already tried that yesterday. I tried completely wiping the internal memory. I still get the same error.
The strange thing is, I never encrypted my device earlier.... ever. Maybe if I try encrypting it and removing encryption, this will help?
I saw somewhere on these forums that that message is just a generic message that you get when Android can't access the /data partition. Is this possibly the case, and perhaps do I have a different issue? I did have issues mounting /data earlier, but I resolved those by updating TWRP.
Thanks in advance.
ForgottenSolstace said:
Thanks, but I already tried that yesterday. I tried completely wiping the internal memory. I still get the same error.
The strange thing is, I never encrypted my device earlier.... ever. Maybe if I try encrypting it and removing encryption, this will help?
I saw somewhere on these forums that that message is just a generic message that you get when Android can't access the /data partition. Is this possibly the case, and perhaps do I have a different issue? I did have issues mounting /data earlier, but I resolved those by updating TWRP.
Thanks in advance.
Click to expand...
Click to collapse
Do like I said and do a one click, it wipes everything and re partitions it.
Still Can't Fix This - Months Later
fryingpan0613 said:
Do like I said and do a one click, it wipes everything and re partitions it.
Click to expand...
Click to collapse
This is just an update for this thread, for those experiencing the same issues. A number of older posts, similar to this one, with the "encryption failed" dialog, are already on XDA:
http://forum.xda-developers.com/showthread.php?t=1957155&page=23
http://forum.xda-developers.com/showthread.php?p=26317290
I have been researching this topic in great depth over the last few months, and I was able to reach the conclusion that I need to re-root my device, and go back to stock.
So I tried, that failed too.
Here's the image that results from attempting to re-flash my device.
Note: I am inclined to believe that the encryption is a result of rooting a WIND Mobile device (not Sprint) when it was not supported in the Galaxy Note 2 Toolkit.
Thanks for any help.
Hi,
I was on OOS 3.1.3 (rooted).
I installed the latest 3.2.0 by:
wiping cache/dalvik
installing full .zip 3.20 via TWRP (downloaded via the amazon aws link)
wiping cache/dalvik
Flashing SuperSU
wiping cache/dalvik
Reboot
Everything seems fine but my phone says no sim card installed. The baseband in About is unknown. And I can't open the screen which shows the IMEI etc on my phone.
Is my EFS wiped out? I made a backup so should be ok. But I am confused as to how to proceed on this?
I have tried to fix this by:
1. Trying to restore the EFS backup using the "fastboot flash modemst1 modemst1.bin" commands (same for modemst2.bin) - I had made a backup of EFS earlier. It doesn't seem to do anything and when I reboot, there is still no baseband.
2. Trying to flash the full ROM zip again - without success
Before I proceed to do anything further, I am hoping someone more intelligent than me can shed some light as to what may have gone wrong and what I can do about it, instead of me managing to make things worse.
Any help would be much appreciated!
Where u got 3.2.0 ? never heard about it
http://forum.xda-developers.com/oneplus-3/how-to/rom-update-to-oxygenos-3-2-0-received-t3410714
I used the same method and the same file and everything is fine here, no apparent issues and I can make/receive calls fine, so the file is ok.
Have you tried rolling back to a previous backup to see if everything works again before trying to reflash?
Hmm, I didn't have much on my phone so decided not to take any nandroid backup. Wasn't expecting any problems (stupid of me, I know).
Hearing all the reports of things being fine, I think the file itself is fine. However, my phone definitely is not. I am truly at my wit's end on how to fix it.
On further discovery, I have noticed that my TWRP has been overwritten with the standard recovery.
PhoenixAG said:
On further discovery, I have noticed that my TWRP has been overwritten with the standard recovery.
Click to expand...
Click to collapse
Well that sounds really odd, and didn't happen on mine, TWRP was still in place for me after the update.
Yes, the whole thing is odd. But I swear I followed the same basic steps as everyone else to try and install the new version.
It's really got me worried, specially the part where I try and restore EFS and everything seems to flash fine, but it doesn't work. I am now trying to sideload the previous version using the default recovery, but its stuck at 92%.
PhoenixAG said:
Yes, the whole thing is odd. But I swear I followed the same basic steps as everyone else to try and install the new version.
It's really got me worried, specially the part where I try and restore EFS and everything seems to flash fine, but it doesn't work. I am now trying to sideload the previous version using the default recovery, but its stuck at 92%.
Click to expand...
Click to collapse
Good luck mate.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PhoenixAG said:
Yes, the whole thing is odd. But I swear I followed the same basic steps as everyone else to try and install the new version.
It's really got me worried, specially the part where I try and restore EFS and everything seems to flash fine, but it doesn't work. I am now trying to sideload the previous version using the default recovery, but its stuck at 92%.
Click to expand...
Click to collapse
What about sideloading an older Oxygen Version?
same thing happened to me too. After Nandroid restore everything back to normal. I am wondering if my TWRP is wrong somehow...using 3.0.2-0
Same thing happened to me too. I flashed back to 3.1.2 and it's working again.
Edit: There's also people in the OnePlus forums having this issue: https://forums.oneplus.net/threads/oxygenos-3-2-0-ota-sim-problem.453972/
same here, no sim and phone get's hot
how did you downgrade?
Want model number did you have? A3000 or A3003 ?
Sent from my ONEPLUS A3000 using Tapatalk
Guys, I managed to sideload version 3.1.3 back using the ADB sideload on the stock recovery, which I automatically received (don't know how).
All my data is safe and it feels like nothing happened, everything works. Hmm, I am now using adb sideload to just flash the OTA (~400MB) and checking what happens. If it works or doesn't work out, will report back!
DooMMeeR said:
same here, no sim and phone get's hot
how did you downgrade?
Click to expand...
Click to collapse
I flashed this image from TWRP: https://www.androidfilehost.com/?fid=24591020540823765
PLONTER said:
Want model number did you have? A3000 or A3003 ?
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
A3003.
I also downloaded the OTA with the builtin updater and the hash is equal to the one from here: https://www.androidfilehost.com/?fid=24591020540823766
Those links are from this thread: http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870
Dam4rusxp said:
I flashed this image from TWRP: https://www.androidfilehost.com/?fid=24591020540823765
A3003.
I also downloaded the OTA with the builtin updater and the hash is equal to the one from here: https://www.androidfilehost.com/?fid=24591020540823766
Those links are from this thread: http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870
Click to expand...
Click to collapse
A3003 here as well. No Sim detected...
I haven't checked my model number yet - should have. So I side loaded the OTA and its the same result. Phone starts burning hot and no sims detected.
So now I am back to sideloading 3.1.3 yet again. Wish they take out a proper fix for our phones, as I suspect mine is A3003 as well.
You can try to take out the modem file from the zip and try.
Sent from my ONEPLUS A3000 using Tapatalk
Do you have two sim cards or just the one? If two cards, try removing one. If just one, try changing sim card slot.
I had done a nandroid back up with system data and boot, I tried to restore and getting 255 error, never had issues with OPO, 3 and 3T, I made 2 backups one before updating and one after updating and getting everything set up, and neither work, using blu_spark, again used on previous devices and no issues ever restoring
can someone please help me, has anyone had to restore a nandroid backup yet, i have done 5 back ups and all 5 give me the error when restoring data. Never had any issues with other devices, Oneplus one, 3/3T never came across this data restore issues. thank you. using Blu_spark TWRP
im in the same boat i had made a stock back up and i went to use it and it gave me the same error, i flashed freedomos and im on that now.
slaya811 said:
im in the same boat i had made a stock back up and i went to use it and it gave me the same error, i flashed freedomos and im on that now.
Click to expand...
Click to collapse
I guess u and I are the only ones, I even tried asking bluespark and no answer, I am stumped, I have clean flashed my phone every day since I have had it the op3 and t were so easy to mod this thing bootloop on everything
Bradl79 said:
I guess u and I are the only ones, I even tried asking bluespark and no answer, I am stumped, I have clean flashed my phone every day since I have had it the op3 and t were so easy to mod this thing bootloop on everything
Click to expand...
Click to collapse
when i flashed Freedomos i ran into problems with that saying insufficient storage in the system partition. its been a very weird flashing experience for me on the 5T. i have been flashing since my touch slide 3g lol
slaya811 said:
when i flashed Freedomos i ran into problems with that saying insufficient storage in the system partition. its been a very weird flashing experience for me on the 5T. i have been flashing since my touch slide 3g lol
Click to expand...
Click to collapse
lol right, i have never had so many problems with a device, especially with TWRP, never had any issues, i was never decrypted on my Oneplus One, 3 and 3T, never any issues, and this is a pain, i could easily extract the apks mod them and move them back most of the times no issues, with this thing i can't even do that b/c it will bootloop, i hope once official TWRP comes out we won't have the flashing issues.
Bradl79 said:
can someone please help me, has anyone had to restore a nandroid backup yet, i have done 5 back ups and all 5 give me the error when restoring data.
Click to expand...
Click to collapse
I have restored multiple times from different backups without issue using blu_spark as well....sorry you're having issues
Bradl79 said:
i could easily extract the apks mod them and move them back most of the times no issues, with this thing i can't even do that b/c it will bootloop
Click to expand...
Click to collapse
Totally unrelated, but this is my 6th or 7th rooted device yet the first one where root uninstaller cannot remove system apps. I get a message that says "rooted, but cannot grant RW on system " There's definitely some quirky stuff with this device.
Dazed No More said:
I have restored multiple times from different backups without issue using blu_spark as well....sorry you're having issues
Click to expand...
Click to collapse
are u decrypted?
My backup and restore process went fine, but I am using the TWRP by blu spark in his kernel thread. Also I am encrypted
Bradl79 said:
are u decrypted?
Click to expand...
Click to collapse
Nope....just to be sure you mean decrypted as in format data correct? Still nope.
Bradl79 said:
are u decrypted?
Click to expand...
Click to collapse
Have you had any luck yet??
slaya811 said:
Have you had any luck yet??
Click to expand...
Click to collapse
i haven't tried yet, i had clean flashed the 1st 5 days i had the device, i just gave up right now until a new update comes out, i did make some changes to my twrp settings that may work, if u would like i will share them with u and see if they work
As far as I know, you have to remove screen lock before backup
bgumble said:
As far as I know, you have to remove screen lock before backup
Click to expand...
Click to collapse
No lock here, still no luck here
Backup = error 255, restore = incomplete
Pfeffernuss said:
No lock here, still no luck here
Backup = error 255, restore = incomplete
Click to expand...
Click to collapse
yeah same here
here are the settings i got from my Oneplus 3 and 3T, have yet to see if it works b/c i was getting tired of clean flashing, but let me know if works
Under Backup - compression optional
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Under Settings
bgumble said:
As far as I know, you have to remove screen lock before backup
Click to expand...
Click to collapse
This is true, but the error they are getting is not related to this.
I have not yet done a backup/restore in TWRP.
Also getting this error on every backup I try and restore. The latest doesn't have security and it still errors out. I found a video on YouTube that states to unmount data to fix the error, but then I don't have access to the backup file.
Can a backup be restored from the PC via ADB?
What if u perform a factory reset in TWRP, then try to restore just the system and boot from your backup? If it boots, u can try restoring data from TWRP. Was your backup encrypted, and when u performed the backup, did u remove fingerprint security first? These can all cause issues with backup & restore.
Maybe it's because you used parallel apps. A new user is created and this causes the error while backing up.
Try this:
Deactivate parallel apps,
in terminal type
su
pm remove-user
I had Redmi note 5 whyred with MUI global rom 10.2.1 (Oreo) with unlocked bootloader and rooted with the latest twrp.
After I deemed the latest miui update not worth it so I decided to flash Pixel experience extended on my phone. First I had to flash the latest firmware available (10.3.2.0) on my phone so I can flash the pie version of PEE, first boot got stuck on google logo fixed on a second flash attempt by reflashing twrp img after flashing the firmware. By after I got to the set I noticed the phone not detecting my sim card which was there so I skipped to wifi, the wifi kept searching without detecting any and when I go to advanced wifi setting my mac address and IP are blank ( check included picture). So I tried reflashing the same rom, then tried to flash another rom (bootleggers) but always ended up in the same result, not detecting wifi and can't skip to home screen.
Another solution I tried is flashing persist.img (taken from fastboot rom 10.3.2.0) through orangefox recovery since it should fix the wifi not working but that also failed.
If there is any other option or solution plz let me know, I can't afford to lose this phone, thank you in advance
Picture for the problem included down
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your EFS (+modem) partition is corrupted ...do u have a backup? (TWRP Backup?)...I know this cause I have the same issue....for about 2 months now...Hope you get a fix..
rtm2000 said:
Your EFS (+modem) partition is corrupted ...do u have a backup? (TWRP Backup?)...I know this cause I have the same issue....for about 2 months now...Hope you get a fix..
Click to expand...
Click to collapse
I lost my backup after I got a twrp password that encrypted my data and solve it like an idiot by wiping my internal storage. Can I find a way to flash it like persist.img ? or does flashing stock rom via fastboot fix it since it's the only thing I haven't tried yet
Edit: looks like you are right, I have found this methode which I'm gonna try and keep you updated, perhaps we'll be both saved
https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/
Edit2: Didn't do much
Rarohd said:
I lost my backup after I got a twrp password that encrypted my data and solve it like an idiot by wiping my internal storage. Can I find a way to flash it like persist.img ? or does flashing stock rom via fastboot fix it since it's the only thing I haven't tried yet
Edit: looks like you are right, I have found this methode which I'm gonna try and keep you updated, perhaps we'll be both saved
https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/
Edit2: Didn't do much
Click to expand...
Click to collapse
The thing is that I have tried almost all methods available online none seem to work...
My only hope is to get it restored by cell phone repair shops as they have access to tool boxes (miracle,umt etc.)..
Lets see what happens...also dont flash miui cause then you wouldnt be able to verify your mi account if the issue doesnt get resolved...you would be completely stuck..
rtm2000 said:
The thing is that I have tried almost all methods available online none seem to work...
My only hope is to get it restored by cell phone repair shops as they have access to tool boxes (miracle,umt etc.)..
Lets see what happens...also dont flash miui cause then you wouldnt be able to verify your mi account if the issue doesnt get resolved...you would be completely stuck..
Click to expand...
Click to collapse
Hello rtm, I fixed mine I'm using a costum tom and it's up and running as it should be.
All I did was flashing the latest fastboot rom via miflash ( flash all bat and kept the bootloader open) and just like that my phone was fixed, only thing to keep in mind is it asked me ofc about my MIaccount which I miraculously remembered the password and the mail.
Hopefully this will be helpful and you'll find your fix soon as I know how much frustrating the situation you're in now.
Rarohd said:
Hello rtm, I fixed mine I'm using a costum tom and it's up and running as it should be.
All I did was flashing the latest fastboot rom via miflash ( flash all bat and kept the bootloader open) and just like that my phone was fixed, only thing to keep in mind is it asked me ofc about my MIaccount which I miraculously remembered the password and the mail.
Hopefully this will be helpful and you'll find your fix soon as I know how much frustrating the situation you're in now.
Click to expand...
Click to collapse
Thanks for the reply...but in my case custom roms just bootloop without any reason...also flashing via mi flash tool gives the antirbpass error even though I flash an anti 4 rom over an antti 4 rom ...no idea y this happens...
Anyway good to know ur device got fixed...cheers
Let me start this by saying my most recent device that I just came from was a Galaxy S5 on Android 5, so my knowledge on Android 9 and new tips tricks and methods is a little outdated. But I have a Google variant of the pixel 3XL that has the bootloader unlocked and TWRP installed for the recovery and the phone is rooted. I recently decided to try and restore a backup I had made shortly after rooting the phone. This backup consisted of the data and system partitions along with the vendor image. I had never seen the vendor image or system image as a recovery option to back up in previous versions of Android, again my knowledge being a little outdated. So I wasn't sure if I needed the vendor or system image and had read somewhere that the vendor image was recommended. So my restore consisted of restoring the data in system partitions and the vendor image. But after the phone rebooted it wouldn't boot, just a black screen. I was able to fix this by flashing the factory image without performing the Wipe through fast boot. I believe this successfully brought me me back to the date of which the backup was by looking at my text messages. But my question is; what did I do wrong and why did I get a black screen after performing a restore and have to do an additional step of flashing a factory image to get the phone back in working condition? Should I not select the vendor image as part of my backup or do I need to include the system images well?
teknikalcrysis said:
Let me start this by saying my most recent device that I just came from was a Galaxy S5 on Android 5, so my knowledge on Android 9 and new tips tricks and methods is a little outdated. But I have a Google variant of the pixel 3XL that has the bootloader unlocked and TWRP installed for the recovery and the phone is rooted. I recently decided to try and restore a backup I had made shortly after rooting the phone. This backup consisted of the data and system partitions along with the vendor image. I had never seen the vendor image or system image as a recovery option to back up in previous versions of Android, again my knowledge being a little outdated. So I wasn't sure if I needed the vendor or system image and had read somewhere that the vendor image was recommended. Show my restore consisted of restoring the data in system partitions and the vendor image. But after the phone rebooted it wouldn't boot, just a black screen. I was able to fix this buy flashing the factory image without performing the Wipe through fast boot. I believe this successfully Road me back to the date of which the backup was by looking at my text messages. But my question is is what did I do wrong and why did I get a black screen after performing a restore and have to do an additional step of flashing a factory image to get the phone back in working condition? Should I not select the vendor image as part of my backup or do I need to include the system imagAes well?
Click to expand...
Click to collapse
My experience restoring from twrp hasn't been that great. But you need the system image, not partition, and vendor image.
jd1639 said:
My experience restoring from twrp hasn't been that great. But you need the system image, not partition, and vendor image.
Click to expand...
Click to collapse
Thanks! So to confirm, with the Pixel 3XL I only need to back the System Image and the Vendor Image and leave the Boot, Data, and System Partitions unselected?
Like this..?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
teknikalcrysis said:
Thanks! So to confirm, with the Pixel 3XL I only need to back the System Image and the Vendor Image and leave the Boot, Data, and System Partitions unselected?
Like this..?
Click to expand...
Click to collapse
The only thing I have had any success with is backing up and restoring data only. Anything else and you get into trouble. Nandroids are just not working, especially on 10. Lots of discussion in the dedicated TWRP thread under "Roms, Kernels, Recoveries". Best of luck.
v12xke said:
The only thing I have had any success with is backing up and restoring data only. Anything else and you get into trouble. Nandroids are just not working, especially on 10. Lots of discussion in the dedicated TWRP thread under "Roms, Kernels, Recoveries". Best of luck.
Click to expand...
Click to collapse
Thank you! I'm on Android 9... The device came with 10, but I used a factory image to downgrade back to 9 because I had read that the restore option in Titanium Backup wasn't working and I need that to migrate most of my stuff from my old device to the new pixel 3xl...I'll stay off the 10 train until custom recovery and certain bugs like that get worked out....
I'll experiment around with twrp Android backups and restores... That makes sense about the data only partition. That might serve my need with backups and restores, I'll try it ..#TrialAndError
Only thing that ever worked for me was data. TWRP, even on 9, had issues with system and vendor. Google kind of locked those partitions down, even more so in Android 10.
teknikalcrysis said:
...
I need that to migrate most of my stuff from my old device to the new pixel 3xl...I'll stay off the 10 train until custom recovery and certain bugs like that get worked out....
...
Click to expand...
Click to collapse
Just pointing out that depending on the age of the old device, using Google backup does a petty good job getting settings and data to new devices during initial setup.
ktmom said:
Just pointing out that depending on the age of the old device, using Google backup does a petty good job getting settings and data to new devices during initial setup.
Click to expand...
Click to collapse
Yeah but it doesn't transfer the data associated with each app like titanium backup tho, correct?
teknikalcrysis said:
Yeah but it doesn't transfer the data associated with each app like titanium backup tho, correct?
Click to expand...
Click to collapse
Depends on the app. System settings are restored. There is nothing preventing the use of TiBu on A10. You shouldn't be restoring system with TiBu anyway.
ktmom said:
Depends on the app. System settings are restored. There is nothing preventing the use of TiBu on A10. You shouldn't be restoring system with TiBu anyway.
Click to expand...
Click to collapse
I know that titanium backup isn't for system backup/restores just user app data..but I thought I had read on a thread here some where that on Android 10, Titanium Backup was performing backups correctly but not restores...I could be wrong tho
teknikalcrysis said:
I know that titanium backup isn't for system backup/restores just user app data..but I thought I had read on a thread here some where that on Android 10, Titanium Backup was performing backups correctly but not restores...I could be wrong tho
Click to expand...
Click to collapse
I thought that was resolved with the TiBu 8.4.0 update ¯\_(ツ)_/¯
ktmom said:
I thought that was resolved with the TiBu 8.4.0 update ¯\_(ツ)_/¯
Click to expand...
Click to collapse
Okay, I guess I didn't come across that bit of info.. probably didn't read far enough...my last phone was a Galaxy S5 on Android 5...so I've got a lot of catching up to do when it come to the latest knowledge...I'd tried to cram all the knowledge I could before I got my hands on my new Pixel 3xl but I haven't absorbed it all yet...
The TiBu issue and not having a fully working recovery (as far as I had read) was the two main reasons why I didn't stay with Android 10 and downgraded back to 9 as soon as I got the device