I was trying a new rom so I made a twrp backup, I was on MIUI 9 stable, It was an Oreo based rom, flashed gapps, custom kernel and magisk and MIUI firmware
Trying to restore the twrp backup after formatting (Tried Every option to format) It basically shuts off the phone while restoring, just the system (or system Image) partition, restoring data was working fine. I had to flash the system manually, then restoring data, which worked fine. Just for testing I tried to recreate a backup and restoring It Just After and the same behaviour happened! Even without flashing anything. Whats happening?
lukypuie said:
I was trying a new rom so I made a twrp backup, I was on MIUI 9 stable, It was an Oreo based rom, flashed gapps, custom kernel and magisk and MIUI firmware
Trying to restore the twrp backup after formatting (Tried Every option to format) It basically shuts off the phone while restoring, just the system (or system Image) partition, restoring data was working fine. I had to flash the system manually, then restoring data, which worked fine. Just for testing I tried to recreate a backup and restoring It Just After and the same behaviour happened! Even without flashing anything. Whats happening?
Click to expand...
Click to collapse
There is a new twrp version (3.2.0.0) which is supposed to show better oreo support. Are you on that version?
Sounds a little confusing how you described what you flashed in which order ... Also I don't get exactly which rom you're trying to restore. Can you give more accurate and precise info?
Related
As title suggest I'm having trouble booting after a successful restore in TWRP. I went to back to oOS nougat rom and didn't like how stripped down it was compared to resurrection remix.
I decided to restore NANDROID backup from the prior day. TWRP restored it correctly but it will not boot.
I restored the exact same backup without any issues previously.
Any suggestions?
I would try to dirty flash the corresponding ROM (RR it sounds like) over it. After restore in TWRP, wipe cache and davlik then flash the ROM. Make sure it's the same as what your restoring. This should realign the system and boot images but keep the data.
I'm using TWRP 3.1.0-1, running Resurrection Remix-N v5.8.0-OnePlus 3T. I want to go back to OOS, I have a TWRP backup of OOS before I flashed RR and I want to restore from that.
So in TWRP -
- Took another backup of RR
- Wiped Dalvik, System, Data and Cache
- Restored OOS
OOS starts and prompts to use my swipe pattern, I swipe my pattern and it's "incorrect", (I didn't forget my pattern, same one I have used for a long time). Ok so back to RR, so I did the same wipes and restored latest RR, now it bootloops. I restored OOS again and wiped. I'm back to OOS, but of course it's "new".
Is there a way to restore OOS successfully or any of RR from my TWRP backups?
Don't know if it makes a difference, but had some issues originally flashing RR, had a bunch of problems, DM-verity and softbricked, I restored to stock using this:
https://forum.xda-developers.com/oneplus-3t/how-to/guide-return-youre-op3t-to-stock-lock-t3569383
After restoring to stock, I successfully removed the default encryption following another guide. I guess I don't know if RR by default encrypts or not, if that matters.
Have you changed your twrp after doing the initial backup
Because twrp before 3.0.4.1 does backups differently and will not restore if restore them by using twrp 3.0.4.1 or newer
kunal1540 said:
Have you changed your twrp after doing the initial backup
Because twrp before 3.0.4.1 does backups differently and will not restore if restore them by using twrp 3.0.4.1 or newer
Click to expand...
Click to collapse
To the best of my knowledge I am using the same version both to backup and restore. I definitely used the same version to backup/restore the latest RR (which bootloops).
RocKKer said:
To the best of my knowledge I am using the same version both to backup and restore. I definitely used the same version to backup/restore the latest RR (which bootloops).
Click to expand...
Click to collapse
Normally, I'd say the backup is just damaged or has some error, preventing proper restore of it. But it's strange that you have two RR backups which won't restore.
If the intent is to get RR working, with your previous user data; maybe try to flash RR, then just use TWRP to restore the data partition?
If you plug your phone in your computer and you computer recognizes your phone, then you can use ADB to wipe everything again. I had the same problem but my phone only charge if I plugged it into my PC so I wasn't able to revive it...
I've got the same problem here. Running TWRP 3.1.0-1, and sultan CM13 20170402. Backed up everything. Tried:
1. restore everything
2. restore only system
3. restore only system and data
None worked. Bootloop immediately after OnePlus splash screen. I also tried the above in combination with wiping everything, wiping system only and wiping data only. File systems are ext4/f2fs/f2fs on system/data/cache.
This is making me go nuts. The only thing I can think of is to try restoring under TWRP 3.0.4.
@RocKKer
try this
go to TWRP Home >> Settings >> tick use rm -rf instead of formatting
and then restore your backup
maybe this helps
cheers
The newest TWRP 3.2.3.-1 does not let me boot into ROM, just brings me back to TWRP again. I have to restore a backed up boot image (with 3.2.3-0) to boot normally. Even flashing TWRP 3.2.3-0 in TWRP does not bring me back.
Anyone else having experiencing this? I have attached my recovery logs.
I was on stock ...and just install los16 without problem... So i dont have problems with TWRP.
Resolved.
After dirty flashing the ROM zip/GAPPs and flashing TWRP, I was able to boot successfully. I Then just saved a new backup including the newest TWRP.
It is strange that just flashing TWRP would make the OS unbootable.
jhedfors said:
Resolved.
After dirty flashing the ROM zip/GAPPs and flashing TWRP, I was able to boot successfully. I Then just saved a new backup including the newest TWRP.
It is strange that just flashing TWRP would make the OS unbootable.
Click to expand...
Click to collapse
There is always a risk when flashing your device. One of the reasons why I prefer to flash using Linux was that Windows would have so much going on in the background that I risked the data transfer being corrupt. That said, if you're using Windows, I'd close all programs and especially disable any anti-virus running in the background. Sure, Linux may have a few things running, but I have always found it did a better job multitasking resources than Microsoft Windows with a fewer chance of data loss.
It is probably because after installing Google Apps, your /data partition gets corrupted.
So after installing Google Apps, go to TWRP > Wipe > "Format Data" & reboot.
I've the same problem & this resolves the issue for me.
For me, this did not help. I had to reflash everything from bootloader.
Funny thing is: it just has downloaded and installed an OTA update. With open bootloader.
I ran into this issue yesterday when a bad flash caused the infamous "no bootable A/B" error. After I resolved it and install TWRP I kept being rebooted back into TWRP. The 3.2.3-0 version resolved everything. I really do believe 3.2.3-1 is a bit buggy. I mean it works, but once you really start to use it more than the average user, you start to notice little things.
I too had this same issue. Eventually realized that updating TWRP by flashing zip from TWRP caused it. I had to flash stock boot partition, then follow the process for flashing TWRP as if you are flashing it for the first time (first boot into TWRP and then flash the corresponding zip). This resolved the issue.
Hi togehter,
I had some problems with flashing new custom roms and ended up in a bootloop with not being able to boot to recovery. This could be solved by flashing the stock image with the xiaomi flash tool.
Before I will fu up again I would like to bring some light into the darkness.
When coming from Stock Rom:
1. Unlock Bootloader -> done successfully
2. Flashed TWRP Recovery -> done successfully but storage (data) was encrypted
3. Flashed Magisk via Recovery -> done successfully (storage still encrypted)
from here I was happy using the Stock Rom with Root.
Now I started messing things up:
Because there are a few things that bother me about the stock rom i wanted to use lineageOS/Pixel Experience. So I proceeded as following:
1. Backup my data (still have to enter key when starting twrp to decrypt the storage) -> done successfully
2. Flash LineageOS -> resulted in bootloop to TWRP
When entering twrp there was no query about the key and data where encrypted. Also the Backup was not accessible .
3. I used all in one tool to erase storage and decrypt data. -> successfully... Now i was able to place data on the internal storage again and start flashing a rom
4. Flashing LineageOS -> done successfully and able to boot into rom
Back to TWRP data was encrypted and I had to enter key.
5. Flashing remove force encryption script via twrp. -> done but now i was facing boot to black screen. TWRP was not working anymore.
Only way to get it work again, was flashing stock image.
Why is the data system always encrypted. This is rly annoying and backups don't work, because i can not encrypt them. Also, I can not put any files on the memory because it is encrypted.
I would rly like to try a custom rom, but I would also like to be able to go back to a backup. What have i done wrong?
You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.
SeppGoPro said:
Hi togehter,
.... What have i done wrong?
Click to expand...
Click to collapse
You need to format data (not just wipe data) in TWRP. Some people suggest before flashing a ROM and some say after, but I don't think it makes a great deal of difference either way.
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Then in TWRP wipe cache and dalvik, then format data.
Reboot into TWRP, or unmount and mount the data partition in TWRP so it correctly reads the data partition.
Copy across the ROM (and GApps if needed)
Them flash.
Boot into the ROM and you should be good.
After initial setup, if you want root, boot into TWRP and flash Magisk.
From here, if you've set a pin on the ROM, you'll be encrypted, but everything should still work normally. You should be able to access everything normally in TWRP and also perform backups. You should be able to got data across from/to a PC normally.
Turbine1991 said:
You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.
Click to expand...
Click to collapse
Not true in many ways.
There is need to flash no dm verity. It's one way of solving the issue, but it's not the only way. You should only do this if you know what it's for and if you know you want this.
AOSP ROMs are not unstable. I've been using them on mine for over 4 months. None are perfect and they have a few minor issues/bugs, but they are far from being considered unstable. I've never had shutdowns, reboots or FC'S.
Thanks for the replies.
Robbo.5000 said:
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Click to expand...
Click to collapse
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?
SeppGoPro said:
Thanks for the replies.
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?
Click to expand...
Click to collapse
Fastboot ROMs are official ROMs that are flashed through the Mi Flash Tool
, with the phone booted into fastboot mode and connected to the PC. They contains almost all partitions, including vendor and all firmware. They will be a .tgz file. They are mainly used as an almost failsafe way to recover the phone, should you mess things up. Flashing them will restore the phone to factory, so will lose TWRP, but you're guaranteed a clean starting point.
If, for example, you want to install Havoc 3, it is recommended to flash it on top of either China or India 10.4 vendor and firmware. So if you're phone is currently on global firmware, you would then need to flash, say, Chinese firmware and vendor flies, before flashing Havoc.
If you have been previously flashing other mods, such as 75Hz, screen refresh rate, for example, then you might choose to flash the official Chinese fastboot ROM, instead of just the firmware and vendor, to ensure that you've cleaned the phone of any mods, etc. In most cases you will be fine flashing firmware and vendor, though.
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.
Robbo.5000 said:
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.
Click to expand...
Click to collapse
So in this case, i can just flash this rom and there is no need of flashing a diffrent vendor or firmware.
So final question: I'm happy with the stock rom plus root. I would like to try a custom rom but I'm not willing to go through the whole installtion procedure again. Is there a way of making a backup and keeping it?
When I backup the stock rom right now, the backup will ne encrypted again...When I formate the data, all my data will be gone again ?
I've tried a couple of 10 ROM but, as far as i see, there're still too many bugs that makes very unpractical for me to use android 10 as a daily driver.
I'm planning to revert back to a pie custom ROM but I'm worried that I might overlook something.
I know that I have to backup some partiotins (persist? EFS? something else? in 10 in order to restore them in Pie, but I'm not sure wich partiotions and how to restore them (before flasing the new ROM, after flashing the new ROM, should I change the active slot?)
Can someone please give me some advices?
Thank you in advance
Don't do anything you Use mi flash tool for android 10 to move android 9 i do tow time and it working for me know am using android 9 pie.
Thank you for your answer, but I'm not really sure if using miflashtool fits my case.
Isn't miflash tool designed to flash only stock ROM?
If it's not, can you please provide me a link to a guide or some explanation on the usage of miflashtool? I'm not very confortable using automated tools to flash ROM
Thank you
Malobestino said:
Thank you for your answer, but I'm not really sure if using miflashtool fits my case.
Isn't miflash tool designed to flash only stock ROM?
If it's not, can you please provide me a link to a guide or some explanation on the usage of miflashtool? I'm not very confortable using automated tools to flash ROM
Thank you
Click to expand...
Click to collapse
to start backup everything and put on pc with usb cable ..
better just flash a recovery.zip of miu pie or oreo or even custom
but if you go full stock with miflash be careful*
dont get rom with ARB activated or delete the firmware upgrade folder
also when downgrading from 10 to 9 or 9 to 8 your persist partition will get corrupted
look in the official Telegram to get a recovery flashable persist restore zip
custom pie and stock pie are pretty stable ..
remember if going for miu get recovery flashable zip and flash twrp image again after flashing rom..boot straight into recovery ...flash magisk ..use stock
Thank you for your detailed answer
Just a couple of more questions
KevMetal said:
better just flash a recovery.zip of miu pie or oreo or even custom
Click to expand...
Click to collapse
Can I just use the recovery I have now (TWRP) or, if not, flash a TWRP.img from fastboot?
but if you go full stock with miflash be careful*
dont get rom with ARB activated or delete the firmware upgrade folder
Click to expand...
Click to collapse
I intend to flash a custom ROM so shouldn't be any issue with anti rollback
also when downgrading from 10 to 9 or 9 to 8 your persist partition will get corrupted
look in the official Telegram to get a recovery flashable persist restore zip
Click to expand...
Click to collapse
Can I just restore my persist backup from within TWRP?
Thank you again for your patience
.........Just a couple of more questions
@Malobestino
Can I just use the recovery I have now (TWRP) or, if not, flash a TWRP.img from fastboot?
*You can use twrp but just make sure you have the latest . The best one is an unofficial one that supports encryption/decryption from 4pda. I use Orange Fox . Lots of people recommend pitch black.
I intend to flash a custom ROM so shouldn't be any issue with anti rollback
*Yes you are right, then it won't be an issue.
Can I just restore my persist backup from within TWRP?
*Maybe , yes& no . Some twrp recoveries don't support flashing persist or even backing it up ..if the version you are using does that, you can backup your persist partition ...
*There are recovery flashable zips of persist for Wayne and Jasmine on the support groups in Telegram too.
Thank you again for your patience
*No worries
KevMetal said:
.........Just a couple of more questions
@Malobestino
Can I just use the recovery I have now (TWRP) or, if not, flash a TWRP.img from fastboot?
*You can use twrp but just make sure you have the latest . The best one is an unofficial one that supports encryption/decryption from 4pda. I use Orange Fox . Lots of people recommend pitch black.
I intend to flash a custom ROM so shouldn't be any issue with anti rollback
*Yes you are right, then it won't be an issue.
Can I just restore my persist backup from within TWRP?
*Maybe , yes& no . Some twrp recoveries don't support flashing persist or even backing it up ..if the version you are using does that, you can backup your persist partition ...
*There are recovery flashable zips of persist for Wayne and Jasmine on the support groups in Telegram too.
Thank you again for your patience
*No worries
Click to expand...
Click to collapse
Thanks to your indications I successfully downgraded from custom 10 (lineage 17) to custom 9 (havoc 2.8)
As you predicted I had some difficulties restoring the persist partition and flash persist.img
However I found a persist flashable zip on a telegram channel as you suggested and I successfully flashed from TWRP.
This is what i did:
- reboot to previously installed TWRP 3.3.1.0
- wiped system, dalvik, cache, data and external data
- switched to other slot and rebooted to recovery (recovery was already flashed to both slots from previous ROM flashing)
- wiped system, dalvik, cache, data and external data
- flashed havoc 2.8
- flashed flashable_persist.zip
- switch to other slot reboot to recovery (no recovery flashing as Havoc has built in TWRP)
- flash gapps
- flash magisk
- reboot to system
For the time being everything seems to work correctly. I checked the sensors with an app and everything seems fine.
Only issues I'm having are that autobrightness doesn't seems to work even if it's active, and that, after restoring its own backup, I cannot change notification sounds in whatsapp (?!?). Every time I try it crashes from within whatsapp settings
This issue is really strange. If i just install the app without restoring the backup from gdrive, I can change the notification sound just fine, but if I resotore the backup it crashes every time I try to access to notification submenu in whatsapp settings (every other setting works just fine).
Again, thank you for your help
Malobestino said:
Thanks to your indications I successfully downgraded from custom 10 (lineage 17) to custom 9 (havoc 2.8)
As you predicted I had some difficulties restoring the persist partition and flash persist.img
However I found a persist flashable zip on a telegram channel as you suggested and I successfully flashed from TWRP.
This is what i did:
- reboot to previously installed TWRP 3.3.1.0
- wiped system, dalvik, cache, data and external data
- switched to other slot and rebooted to recovery (recovery was already flashed to both slots from previous ROM flashing)
- wiped system, dalvik, cache, data and external data
- flashed havoc 2.8
- flashed flashable_persist.zip
- switch to other slot reboot to recovery (no recovery flashing as Havoc has built in TWRP)
- flash gapps
- flash magisk
- reboot to system
For the time being everything seems to work correctly. I checked the sensors with an app and everything seems fine.
Only issues I'm having are that autobrightness doesn't seems to work even if it's active, and that, after restoring its own backup, I cannot change notification sounds in whatsapp (?!?). Every time I try it crashes from within whatsapp settings
This issue is really strange. If i just install the app without restoring the backup from gdrive, I can change the notification sound just fine, but if I resotore the backup it crashes every time I try to access to notification submenu in whatsapp settings (every other setting works just fine).
Again, thank you for your help
Click to expand...
Click to collapse
I'm glad everything worked well. The auto brightness is most likely a rom bug ..check on Havoc thread ..
Maybe it could be fixed with a custom kernel ...kangmeng or something like that
As for restoring ...it is amazing the amount of strange behaviours it can cause .
Try this : ... Before backing up whatsapp change the notification to stock behaviour ..default notifications ..do backup ..
When you restore ...clean install whatsapp ..restore only data with titanium por from google drive..dont use ...just exit.. force stop ..clear cache ..open and use like normal ..will fix this problem i think .
KevMetal said:
I'm glad everything worked well. The auto brightness is most likely a rom bug ..check on Havoc thread ..
Maybe it could be fixed with a custom kernel ...kangmeng or something like that
Click to expand...
Click to collapse
Im' also quite convinced that is something related to the ROM or the kernel. Fro the time being isn't that big of an issue. I will look into it in the next days
As for restoring ...it is amazing the amount of strange behaviours it can cause .
Try this : ... Before backing up whatsapp change the notification to stock behaviour ..default notifications ..do backup ..
When you restore ...clean install whatsapp ..restore only data with titanium por from google drive..dont use ...just exit.. force stop ..clear cache ..open and use like normal ..will fix this problem i think .
Click to expand...
Click to collapse
Apparently this issue resolved during nightime by itself.
My theory is that the autobackup during last night realigned automagically the app (which doesn't make a lot of sense, but I don't really know how whatsapp's backup works, what it writes or read to the gdrive backup).
Anyway I really appreciated your help, thank you again