Nandroid restore after failed (accidental) encryption from dirty flash. - Xiaomi Poco F1 Questions & Answers

Hi all,
So I was happily running the 20190722 PE (Pixel Experience) on beryllium-V10.3.6.0.PEJMIXM-9.0-vendor-firmware with DFE and Magisk 19.3 flashed from TWRP 3.3.0. All files from official sources including the Official Telegram.
I come to discover I am 2 updates behind on PE so I created a NANDROID backup of the boot, system, and restore. I then cleared the dav and cache per usual and dirty flashed the ROM.
I then proceed to reboot the phone and it begins to encrypt itself. Given that I am a brilliant engineer, I proceed to interrupt it and restart the phone into TWRP. It loads and prompts a password. I have forgotten to DFE.
At this point I know that I have completely screwed up so, following the ongoing consensus on these forums, I format in TWRP, rebooting and clearing as instructed. I then go to restore the NANDROID. No go, boot loop.
After reading more, conclude that I need to flash the vendor FW and use it to reset/clear the phone and reinstall TWRP via FASTBOOT then flash the NANDROID. Nope, boot loop.
Going farther I discover that I need to flash the NAN on top of it’s working ROM/FW.
I go and flash the previously working ROM AND FW with dfe. To I double check I boot that and it boots properly to Android Setup.
Great! I use TWRP to flash the NANDROID. It boots to a lighted black screen. Pushing power I can get it to come up with a power/reboot/lock down menu that moves around the screen. This will actually restart or turn it off (didn’t touch the last).
I have tried this in various combinations with both my new NAN as well as a known working one.
Any ideas/thoughts/insults/ (I can take it)?

Try flashing 10.3.7.0 and then PE and immediately after DFE. However, I'm not sure it you won't lose everything. When doing your backup from TWRP, choose everything except System & Vendor. These 2 will be covered by System Image & Vendor Image.
HTH

Related

SM-G850W Galaxy Alpha bootloop issues after restoring CM 13 backup over Lineage OS

I seem to have shot myself in the foot recently. I've been on CM 13 for nearly a year now and I wanted to try out LineageOS for the hell of it since I am planning to get a new phone and I wanted to put LineageOS on that as well. So I downloaded an unofficial build of LineageOS for the G850W and followed some basic instructions: backup with TWRP, wipe with TWRP, and flash both the ROM and OpenGApps with TWRP. All three of these went well and I was able to install LineageOS. Now the problem: I tried restoring my backup (a CM 13 based backup) thinking I could restore some things from that backup and when I went to restart the CM boot screen popped up and I immediately knew I must have messed up. Checking my backup it contained boot, cache, system, EFS, modem, and a couple other folders/partitions that I can't remember off the top of my head. I then simply tried to redo everything again: backup, wipe, flash. While I am able to backup, wipe, and flash, and I am able to proceed past my device's boot screen, the Lineage OS boot screen seems to either be stuck or it is taking a long time. I've waited for 30 minutes with no change and I am sure that shouldn't be the case at all. Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever. I managed to reinstall CM 13 but it's a very buggy install as sometimes it restarts randomly and goes through the "preparing applications" thing upon restart. Furthermore data doesn't seem to work and IMEI info is not found and sometimes in the stock recovery mode it shows that the EFS partition could not be found. Same thing happens when I poke around in ADB, I do not see any EFS partition when I type in the mount command. Clearly I've really messed things up. So would there be some way to fix things considering I do have a backup of things before I messed things up? How would I use my backup to fix everything? Would there be other tools I should be trying? Any help would be appreciated.
Flash original firmware
echo124 said:
Flash original firmware
Click to expand...
Click to collapse
I did: "Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever".
Erase everything on your phone (aftet backup) and flash stock again.
echo124 said:
Erase everything on your phone (aftet backup) and flash stock again.
Click to expand...
Click to collapse
I've done that as well already, still the same issue.
:fingers-crossed:Flash stock, flash same version twrp used to backup, flash same version of cm 13 used on backup, try restore.

Bricked the phone by wiping every partition in TWRP

My Redmi 5 plus won't boot as I messed up everything while trying to flash a couple of ROMs. At first the two ROMs that I flashed were working well. But after some time, whatever ROM I flashed, the phone started to restart while setting up the first boot (choosing language, region, etc.) and no further. So I tried wiping every partition there is under the TWRP wipe section (cache, system, vendor, data, internal storage, and so forth). Then flashed a custom ROM again with and without GApps but no success. I noticed that the phone even started to restart before the first boot finished. Also, after flashing stock ROM, TWRP said no OS installed. I even tried flashing stock MIUI ROM in fastboot mode. Although it went well, still bootloop and the device keeps restarting. However, before all of these problems, I did take a backup of every partition, leaving nothing behind, so I restored everything but again the "No OS installed, are you sure to boot?" message. Now I'm freaking out, not knowing what to do. I read somewhere that flashing via QPST tool may help but I'm having problems with installing it.
If I manage to make my phone work again, I will not flash any other ROM, ever.
Try installing new firmware with recovery, if that doesnt help you can try flashing with EDL mode.
Just open your phone and bridge these points ( on photo ) and connect phone to PC.
It should appear in XiaoMiFlash as COM[number].
Good luck!
steve_i7 said:
My Redmi 5 plus won't boot as I messed up everything while trying to flash a couple of ROMs. At first the two ROMs that I flashed were working well. But after some time, whatever ROM I flashed, the phone started to restart while setting up the first boot (choosing language, region, etc.) and no further. So I tried wiping every partition there is under the TWRP wipe section (cache, system, vendor, data, internal storage, and so forth). Then flashed a custom ROM again with and without GApps but no success. I noticed that the phone even started to restart before the first boot finished. Also, after flashing stock ROM, TWRP said no OS installed. I even tried flashing stock MIUI ROM in fastboot mode. Although it went well, still bootloop and the device keeps restarting. However, before all of these problems, I did take a backup of every partition, leaving nothing behind, so I restored everything but again the "No OS installed, are you sure to boot?" message. Now I'm freaking out, not knowing what to do. I read somewhere that flashing via QPST tool may help but I'm having problems with installing it.
If I manage to make my phone work again, I will not flash any other ROM, ever.
Click to expand...
Click to collapse
Did u have the global or Chinese rom installed?
And which twrp version do u have?

Pocophone F1 no os after sideloading going wrong

Hey all, so it appears that I screwed my phone, I am not sure how.
I was running LineageOS, and wanted to update to Android 10 one, so I followed the steps, and I think I screwed the sideloading part, so... long story short now when rebooting from OrangeFox RecoveryProject it says no OS detected, and when it boots it says encryption unsuccessful, I tried wiping and installing DisableForceEncryption_Treble_v17.2 and restarting, and the same thing happens.
I tried to flash through recovery both, and did not work:
https://xiaomifirmwareupdater.com/firmware/beryllium/
https://xiaomifirmwareupdater.com/archive/vendor/beryllium/
And when trying to flash through miFlash it doesn't work:
I go to fastboot in poco, hit refresh in miflash, it shows a device in the list, but the phone goes dark with 'something key to shutdown` written in the top left corner and if I hit the flash button nothing happens.
Can anyone assist with that please?
kishikaisei said:
Hey all, so it appears that I screwed my phone, I am not sure how.
I was running LineageOS, and wanted to update to Android 10 one, so I followed the steps, and I think I screwed the sideloading part, so... long story short now when rebooting from OrangeFox RecoveryProject it says no OS detected, and when it boots it says encryption unsuccessful, I tried wiping and installing DisableForceEncryption_Treble_v17.2 and restarting, and the same thing happens.
I tried to flash through recovery both, and did not work:
https://xiaomifirmwareupdater.com/firmware/beryllium/
https://xiaomifirmwareupdater.com/archive/vendor/beryllium/
And when trying to flash through miFlash it doesn't work:
I go to fastboot in poco, hit refresh in miflash, it shows a device in the list, but the phone goes dark with 'something key to shutdown` written in the top left corner and if I hit the flash button nothing happens.
Can anyone assist with that please?
Click to expand...
Click to collapse
This happened to me when I accidentally deleted the OS when flashing the latest MIUI 11 build (using TWRP). THIS IS HOW I FIXED IT.
Find a full firmware of whatever you wanted to flash, either Lineage or MIUI 11. Then flash via your recovery (you said you have orangefox). Use an external sd card, external USB or HDD since you technically wouldn't have access to your internal data. After flashing, same process as most updates, clear cache and dalkiv. Then flash a newer DFE (if you still want to decrypt, there is a page here in xda with it. Or go to miui forums Happybuddhist, the mod there, made a new one prebuilt with Magisk). Then reboot into recovery to make sure you keep your custom recovery. Once booted to recov. Boot to system. Should fix the issue.
You could check my guide here on how to unbrick your pocophone:
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
mecoromeo said:
This happened to me when I accidentally deleted the OS when flashing the latest MIUI 11 build (using TWRP). THIS IS HOW I FIXED IT.
Find a full firmware of whatever you wanted to flash, either Lineage or MIUI 11. Then flash via your recovery (you said you have orangefox). Use an external sd card, external USB or HDD since you technically wouldn't have access to your internal data. After flashing, same process as most updates, clear cache and dalkiv. Then flash a newer DFE (if you still want to decrypt, there is a page here in xda with it. Or go to miui forums Happybuddhist, the mod there, made a new one prebuilt with Magisk). Then reboot into recovery to make sure you keep your custom recovery. Once booted to recov. Boot to system. Should fix the issue.
Click to expand...
Click to collapse
I tried that, now I am a step forward I think, I flashed the stock firmware I found, and installed the latest stock ROM, rebooted (doesn't say no os anymore), but the only thing I see is a DELETE ALL DATA button and at the bottom 'Encryption was interrupted and can't be completed. As a result, the data on your phone is no longer accessible.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account.'
Darklouis said:
You could check my guide here on how to unbrick your pocophone:
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
Click to expand...
Click to collapse
I have an issue with the MiFlash part, it seems that it doesn't work as I mentioned...
Aight all, formatting data partition to ext4 worked, now it is booting
kishikaisei said:
Aight all, formatting data partition to ext4 worked, now it is booting
Click to expand...
Click to collapse
Works now?
mecoromeo said:
Works now?
Click to expand...
Click to collapse
So I had an OS-less phone that don't get recognised in MiFlash, and I had orangeFox recovery.
The steps to fix were:
- Flash a full stock Firmware
- Flash the stock ROM
- Flash DFE
- Format data to ext4
- Reboot and it works
So thanks all for your help

Now the system only boots to recovery (TWRP 3.4), but no ROMs

Hello
I was at RUI C07 stock firmware.
I've managed to unlock the bootloader and to install TWRP 3.4.0. Then I've tried to flash derpfest (android 10), LineageOS and RevengeOS.
All of them seems to have flashed successfully, but TWRP always warns that there is no OS installed when I try to reboot. When I do reboot, it tries to load something, fails and goes back to TWRP.
What is the problem? Should I try to flash vbmeta? Where can I find it? I'm completely lost.
Thanks in advance
I've just followed the "unbrick guide" and there was little developement...Now the phone boots to fastboot/bootloader by default. I can boot to recovery if I request it. But if I just turn on the system or if I request system, it stops at the bootloader.
What a roller coaster ride!
What seems to have worked for me was to flash yet another ROM (crDroid). But this time I made sure that I've formatted DATA, and then I've wiped vendor, system, caches, internal disk.
I may have forgotten to format the data partition before, which might have been the cause for so much trouble.
If you are reading this, don't forget to format the data partition before flashing a custom ROM, at east when coming from the stock rom.

Serious issue with the TWRP/Nandroid backup - twrp backup failed to mount system root structure needs cleaning - keeps looping back into TWRP

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. )

Categories

Resources