HI
after some wrong uninstalling service from my clean miui 9.6.25 global
i tried to restore rom by usual way from twrp.
but when done the pocophono never run to boot only logo screen(waiting atleast 15min which ofcourse is not normal).
has anyone faced that?
do i need to flash ENCRYPT disabler again after restore?:silly:
Come on......!!! cant be only me???!!!heheheh
TWRP is for lifesaver not to trouble as all know
I've found this too.
Encryption shouldn't matter.
Try restoring only one partition at a time to see which is causing the error. I think it's Userdata in my case, but Userdata Image may work.
I've not bothered to investigate why this happens yet.
ok
i will try mate.
thank u!
i will come backup for update
My phone had latest Miui9, then I installed Twrp and backup the Miui9 rom by Twrp.
then I flashed Miui 10, back up it with TWRP.
Then try to restore my Miui 9 Twrp backup, after done the phone boot to Fast boot mode only.
Even tried restore Miui10 still it would boot to fastboot mode only. Flash new rom and reboot it will ask for encryption password.
The fix is need to format data (Wipe > Format data > type yes, after flashed the rom), and reboot it should work.
Yeah, restoring MIUI backups is a real pain... Because of that, I always flash the ROM zip file first, then restore the data only, reboot and it works.
mario123m said:
Yeah, restoring MIUI backups is a real pain... Because of that, I always flash the ROM zip file first, then restore the data only, reboot and it works.
Click to expand...
Click to collapse
so steps:
1st flashing miui rom.zip
2nd restore files with twrp backup file?
and all works perfect????
data? system? image system? which please
first time i hear this method...hehehe
pin\password asking after?
miui account find device e.t.c?
I switch ROMs pretty often and MIUI never booted after restoring.
There's a simple workaround: just reflash MIUI whenever you restored.
emmanuelo7 said:
so steps:
1st flashing miui rom.zip
2nd restore files with twrp backup file?
and all works perfect????
data? system? image system? which please
first time i hear this method...hehehe
pin\password asking after?
miui account find device e.t.c?
Click to expand...
Click to collapse
Install MIUI zip (with the same system you backed up), then go to restore and just restore data and nothing else. If you used Magisk before, flash it too after restoring. Then reboot. I don't know about Global ROMs as I always use Xiaomi.eu but I think it should work the same way. Oh, and never backup data with a password/pin/fingerprint set because it will not recognise it after reboot and you will have to use TWRP to delete locksettings from /data/system which adds unnecessary steps to this tedious procedure. Good luck.
thank u bro!
mario123m said:
Install MIUI zip (with the same system you backed up), then go to restore and just restore data and nothing else. If you used Magisk before, flash it too after restoring. Then reboot. I don't know about Global ROMs as I always use Xiaomi.eu but I think it should work the same way. Oh, and never backup data with a password/pin/fingerprint set because it will not recognise it after reboot and you will have to use TWRP to delete locksettings from /data/system which adds unnecessary steps to this tedious procedure. Good luck.
Click to expand...
Click to collapse
Hi, I'm having the same issue.
I get a PIN code. How can I bypass it?
How can I avoid it in the future?
Thanks!
if password promt during boot u have no option other than format data
only lockscreen can be deleted via twrp
I had the same problem in my pocophone and solved it like this:
1. Advanced wipe all data except Internal storage (so you do not lose your data)
1.1 Flash or boot twrp again
2. Install the official rom using the way you know
3. Starts android the first time but without doing the initial configuration of android (I'm not sure if this is necessary but it costs nothing to do it)
4. Through twrp, restores the data but only the options Boot and Data, dont select System
And that's it. I hope it works for you.
I was trying different combinations and I realized that it is the system folder that has a problem when you make the restoring, don't know why.
I was using pocophone with MIUI 10.2.2
mario123m said:
Install MIUI zip (with the same system you backed up), then go to restore and just restore data and nothing else. If you used Magisk before, flash it too after restoring. Then reboot. I don't know about Global ROMs as I always use Xiaomi.eu but I think it should work the same way. Oh, and never backup data with a password/pin/fingerprint set because it will not recognise it after reboot and you will have to use TWRP to delete locksettings from /data/system which adds unnecessary steps to this tedious procedure. Good luck.
Click to expand...
Click to collapse
Thanks a lot!
So I created a full backup of my device using TWRP and now just tried to restore it and it's just completely messed up my device. I got an error saying extracttarfork() process ended with error=255. My device was a custom timurs rom which I dont remember how to go through the whole process again. From the videos I have seen apparently I need to reflash it. How do I do that? What files do I need? Can someone please help
So, although the message logs shows that it formatted and wiped the system, I just thought i would give it a restart and see if I get a bootloop. But it seems to have not done anything of such like deleting or wiping because the system is still the same. However, I did notice my bootanimation logo has gone back to the version before the backup. So I don't know what exactly has happened.
Is it possible on TWRP to do a clean fresh install and then flash the Timurs Kernel rom back on? My tablet is in fix mode and I don't really have access to the volume buttons to force TWRP easily. So I'm thinking I would like to do a clean android refresh and flash the kernel again.
It's definately messed something up because now when I try to transfer a file into the System partition using TWRP i get error saying Full SELinux support is present. This never happened before. Any ideas please on how I can just start fresh on this?
Was updating my nord EU .12 > .14.
Always had my device rooted with magisk. But before updating i flashed my stock boot.img(android/magiskbackup)
This time i did the same flashing with fastboot.
After that i tried to download the OTA update only like i did with previous updates. (hidden folder .ota)
But this time it did not download only and, did not gave me the option to install but only to reboot system, and also the hidden .ota folder not to be found.
So i thought maybe in this forum manual update zip file so i found one Nort posted (15dec) in topic Stock Boot & Patched images.
Booted into TWRP first creating a backup and after that installing the update_A12_auf_A14.zip
Device tried to boot but did not boot. Only the oneplus nord image in bootloop.
Ok so updating went terribly wrong, so i thought i would restore my backup.
Booted TWRP restoring my image.
Device tried to boot i see the oneplus nord image and it starts to boot but after that i see a black screen with the text shutting down...
If i press the power button screen turns off and when on stays in this shutting down... screen image.
What has happened to my device how can i restore it can anyone please help me out what to do next?
Also, previous updates i did for the nord 2 rooted device went fine.
For some reason after i did factory reset wiping data/cache etc.
And restored the backup, it was able to boot.
But TWRP now changed my lockscreen pin and also i'm not able to decrypt internal storage anymore after the restored backup.
I was able to manage to remove the lockscreen pin by removing locksettings.db in data/system.
The recovery was a mess because it now is still half broken with my background image and the text shutting down.. i couldn't access my homescreen/launcher, only able to get into settings with the drop down slidebar. (confirmed back to A12 version).
And now i have another problem i cannot access my internal storage anymore through TWRP and through android transfer files.
So i cannot install any zip or img anymore and restore/have access to my backups.
So is the only option now adb sideload i cause. What should i do now?
I do not want to wipe my internal storage data i really need access to those files.
Does anyone with experience have good suggestions?
So, I can't restore my backup due to the error above. When I restore my backup, I get that error and a reboot loops me straight back into TWRP. You can read all that stuff below if you need the backstory.
(I had Lineage OS 18.1 installed and wanted to restore a backup from two weeks ago. So, I booted into TWRP, did a normal factory reset and restored the Backup of Lineage. However, it put out an error regarding something in root (structure needs cleaning). I tried rebooting into system, but it ended in fastboot mode. So I googled it and one thread said you can solve that by formatting system. "System" is backed up anyway, so I thought there was no harm, wiped it and restored the same backup once again. No error this time.
However, when I rebooted into system, the unlock pattern didn't work any more, even though I never changed it and always use the same one. I had to reboot into recovery, and now the TWRP unlock pattern didn't work either. Had to skip it and did another reset.
Now, every time I restore a backup (and those backups contain basically every partition available) it works, but when I reboot into system it just stops at the boot logo, then reboots into recovery. Basically a boot loop plus. Tried a fresh flash, same loop.
Also, all of my pictures and downloaded files are gone, because it's encrypted. I had to wipe data, which led to the whole encryption issue going away, however, I'm still stuck in that loop.
Does anyone know how to solve this cluster****? How do I get it to boot into system?
Edit: Managed to flash LIneage new after wiping data and system and it actually boots, hallelujah, but when I flash the back up I'm still at square one with the same fail and it fails to boot. )
Hello!
Yesterday, I updated my phone from A10 to A12 with full OTA and applied magisk on inactive slot.
After rebooting, all seems to work, no bootloop, android was optimizing apps... so far so good, I reached the point where my patter was asked. There was no problem with it.
The problem appeared when trying to open any APP and the android answer was (for any app) "Failed to read the app data. Cannot start the app"
Okay, I tried to go to settings and was unable to do so. After putting phone in airplane mode, settings worked but clearing apps cache or data did not help.
Trying to fastboot boot twrp.img did not work until I found https://github.com/rabilgic/twrp_device_oneplus_hotdogb/tree/Android-12.1 by another xda user.
Even being another device it worked (afaik they were unified twrp so they should work for both). However, once booted, the first problem appears. Inserting my patter did not decrypt the data in twrp... Booting into system removing pattern and try TWRP again and nothing changed...
Checking in twrp the data/data lead see all folders and files encrypted there... So this is probably why any app is working...
After reading, I saw that fbev2 was applied to A12 so this might be the problem. My guess was that flashing a A11 rom might save my data since the encryption should be the same older one v1. However, I am unable to flash ROMS with TWRP... Tried with OTG or sideload, but both failed. I would like to know if there is a way to flash an older rom (A10 whcih was my original one or A11) to decrypt the data or make the A12 decryption work to recover all my apps and data.
I do not know if flashing any further (of if I had already) lost the decryption keys or what is going on.
I had extracted the .img from a full A10 OTA (OOS) and I am hesitant of flashing all 32 images to the phone or if that will wipe data partition.
How can I proceed if possible without losing data with a flash, or how can I decrypt the data to make it work with A12?