Why not just flash it yourself in twrpTried to install full system update (11.0.9.9) with Oxygen Updater using twrp option and failed. Twrp made backup and finished without any update.
Tried it and also didn't work. It was not possible to flash the stock firmware. As a result, I flashed it through an internal update in the phone settings.
I believe you can flash it through twrp but I would fastboot it on PC.what is the safest way to go back to stock recovery? should I just flash stock OOS .zip from the latest beta TWRP? don't want to get stuck on bootloop.
will fastboot flash erase all the data?I believe you can flash it through twrp but I would fastboot it on PC.
Are just flashing the stock recovery if so no data whipes for that.
If you're on 8.8 OOS you can pull it yourself using payload dumper. It's good practice to be able to obtain it yourself.does anybody have 10.0.8.8 IN11BA stock recovery .img file and could upload it?
Just curious. Did you follow the instructions on the 2nd post?Yesterday tried to restore my OOS backup after tinkering with a custom ROM. There were no errors when I took the backup. Data restored fine without errors too, but the system didn't boot afterwards, it was boot looping. I did a wipe - factory reset before restoring. Lost about two hours trying to restore the backup so that it would boot and all was in vain. So I had to MSM eventuallyI used beta 7 for backing up and restoring.
Of course. I removed the pin so that the system was unencrypted before backing it up. Then I did a factory reset before restoring.
The process as explained in post #2, when switching ROMs, is to do a format of /data, not a factory reset.Of course. I removed the pin so that the system was unencrypted before backing it up. Then I did a factory reset before restoring.
I have a backup phone (Samsung A5 2017), which also has a TWRP installed. I backed up that phone and restored it over a dozen of times, so I'm kinda familiar with the process.
The process as explained in post #2, when switching ROMs, is to do a format of /data, not a factory reset.
Same problem here, but with custom ROM.I did a format too (where it says type "yes" to continue). As I said, I tried to restore the backup over two hours multiple times, on a clean/wiped/completely formatted system. It does restore the backup without errors, but it never boots. I could still install a custom ROM though and it booted just fine.
When you backed up OOS, what partitions did you backup, other than data?I did a format too (where it says type "yes" to continue). As I said, I tried to restore the backup over two hours multiple times, on a clean/wiped/completely formatted system. It does restore the backup without errors, but it never boots. I could still install a custom ROM though and it booted just fine.
I backed up all partitions, except "persist" and "super partition". When restoring, I tried to restore all of them and also restored "data" only. It didn't make any difference.When you backed up OOS, what partitions did you backup, other than data?
Historically was a format required?I backed up all partitions, except "persist" and "super partition". When restoring, I tried to restore all of them and also restored "data" only. It didn't make any difference.
1. The A12 kernel source is incomplete (missing various things like touch panel driver and techpack)@infected_ now that the kernel source of 12.1 is out, will there be A12 support finally?
#include
/*
*
* Yea, though I walk through the valleys of c++ and java, of the shadow of death on these forums,
* I will fear no evil and i will develop and code restless: for thou art with me and my keyboard;
* thy rod and thy staff they comfort me, and my mouse..
*
*/