Anyone experience this kind of problem using TWRP? i tried creating a backup (crdroid) before i change custom rom but when i go back to the custom rom i like (crdroid), i install again the rom (crdroid) then format then open the rom, it can open normally without a problem but when go back to twrp then i tried to restore my backup it can restore successful but it goes back to the file size of which is new formatted even tho i already restore my backup... this is the first time i experience this kind of problem hahaha in my pocof1 and oppo phone this never happened.
can anyone help me
anyone ??
Try flashing orange fox recovery:
[RECOVERY][UNOFFICIAL] OrangeFox for Xiaomi Mi11X / Redmi K40 / POCO F3 [R11.1][alioth]
OrangeFox Recovery * I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this Recovery...
forum.xda-developers.com
Try restoring your twrp backup with OrangeFox recovery
Related
The other day I was restoring a backup in TWRP 2.6.0 on my Sprint Galaxy S3. The ROM I was on was AOSP based and the one I was restoring was AOSP based. During the restore, the phone rebooted during the data restore and then started a boot loop on the device, where it appeared I was starting TWRP again, only to have the device reboot at the TWRP splash screen.
I eventually finagled the device into getting TWRP to load by starting DL mode and then booting into recovery where I proceeded to do a full wipe and install a ROM from fresh. Anyone know why this would occur? It was very scary to think I was about to brick my device over something as simple as restoring what was a successful backup. I have not tried to restore any backups since out of fear of this issue occurring again. I also read on the TWRP page about a defect of reboot during restores if not enough data is available, but I have plenty of storage room available on my internal (26.26) and external (29.93) SD cards.
Not much help here, and at the risk of sounding like a Negative Nelly, I gave up on image-based backups several devices ago. The only device that I could get reliable nandroids was my HTC EVO 4G running AmonRA recovery. Since then, I've owned/rooted 4 or 5 other Android devices, and every single one of them have been completely unreliable with nandroid restores to the point that I just gave up, use Titanium Backup, and then just flash the ROM again. That's been with CWM and TWRP, all versions (and I've probably tried them all) on all of my devices.
I would love it if someone could enlighten the both of us on how to be successful with nandroid backups/restores. Again, sorry I'm not of much help, but consider me a confirmation of what you're encountering (a "yeah, what he said").
dante32278 said:
The other day I was restoring a backup in TWRP 2.6.0 on my Sprint Galaxy S3. The ROM I was on was AOSP based and the one I was restoring was AOSP based. During the restore, the phone rebooted during the data restore and then started a boot loop on the device, where it appeared I was starting TWRP again, only to have the device reboot at the TWRP splash screen.
I eventually finagled the device into getting TWRP to load by starting DL mode and then booting into recovery where I proceeded to do a full wipe and install a ROM from fresh. Anyone know why this would occur? It was very scary to think I was about to brick my device over something as simple as restoring what was a successful backup. I have not tried to restore any backups since out of fear of this issue occurring again. I also read on the TWRP page about a defect of reboot during restores if not enough data is available, but I have plenty of storage room available on my internal (26.26) and external (29.93) SD cards.
Click to expand...
Click to collapse
What I have found out the hard way is that every device is different. Some prefer CWM Recovery, some TWRP Recovery. If TWRP is not working for you, try CWM. A stable Custom Recovery is a must have.
TEAM MiK
MikROMs Since 3/13/11
Hi, recently rooted my phone and tryimg to backup everything before i install a rom but when trying to back up the IMEI/NVRAM MTK droid tools gives me the errors
"ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!! --- Unknown ROM structure, backup NOT possible! "
I've tried searching for solutions which have suggested
* Install Busybox- tried but seen no change.
* Download MTK droid tools from a different source- tried this too
* Slot in an SD card with sufficient space into the phone- i have enough space on my sd
* When prompted for Super User permissions on the phone and PC, select Ok or Grant - done.
I want to backup as much as possible before installing a new rom but not sure how to get by this issue/error. Any help would be appreciated thanks.
Any suggestions thanks? Currently I understand the error unknown rom structure occurs because the phone isnt a mtk phone of which it is and ive tried downloading mtk droid tools from a different source with the same errors occuring.
When i rooted my phone I used a method that attempted to install cwm but when I try to boot into it the samsung logo just jumps around the screen. Would this have anything to do with the errors?
Sorry for the amount of questions.
Note2mk said:
Any suggestions thanks? Currently I understand the error unknown rom structure occurs because the phone isnt a mtk phone of which it is and ive tried downloading mtk droid tools from a different source with the same errors occuring.
When i rooted my phone I used a method that attempted to install cwm but when I try to boot into it the samsung logo just jumps around the screen. Would this have anything to do with the errors?
Sorry for the amount of questions.
Click to expand...
Click to collapse
the most important is EFS backup, which can be done with apk from play store. Other things you can backup with titanium backup, then flash custom recovery i.e. TWRP and do full backup in recovery. That's all you need. everything else you can restore with stock rom
yaro666 said:
the most important is EFS backup, which can be done with apk from play store. Other things you can backup with titanium backup, then flash custom recovery i.e. TWRP and do full backup in recovery. That's all you need. everything else you can restore with stock rom
Click to expand...
Click to collapse
Thanks for your reply. I just backed up the EFS using EFS professional using a tutorial I read on here. Also used titanium backup aswell. What method would you recommend flashing TWRP or CWM? Would flashing any of those interfere with the currently attempted installation of CWM that wont boot?
Note2mk said:
Thanks for your reply. I just backed up the EFS using EFS professional using a tutorial I read on here. Also used titanium backup aswell. What method would you recommend flashing TWRP or CWM? Would flashing any of those interfere with the currently attempted installation of CWM that wont boot?
Click to expand...
Click to collapse
flash TWRP for your model i.e. N7100, N7105, etc. using Odin 3.10.7. Do not repartition and your phone would be ok. There are guides and even movies on youtube how to use Odin
Hi there,
I have a big problem. I run a OP3 with TWRP 3.1.1.2. After flashing a custom ROM e.g. Resurrection Remix, all my data on the internal storage + apps are lost and my OS seem except for the google account like factory resetted.
My phone is also encrypted. Can it be a problem with permissions on the sd-card?
Thanks in advance
PS: Is there a tool with which I can recover my non meida data like zip files and so on? DiskDigger works mostly for photos.
Flashing blu_spark TWRP seemed to fix it. Found it out after some research.
Try new approach to flash RR5.4.8, but nandroid backup first
- Ensure TWRP is 3.1.1-2, turn power off and after switch on enter TWRP (do not start recovery from OS or TWRP)
- Flash OB22 Firmware and Modem; then Boot patch for dm-verity to remove storage encryption
- Flash Resurrection ROM and GAPPS, Whenever you take nandroid backup make sure Secuity=None to avoid restoration issues
- Even if this approach won't maintain your apps (it could be the reason that original storage is encrypted as dm-verity not disabled),
i suggest using this approach for flashing any custom ROM. Since had started this approach all RR and Nadorid issue just vanished
Hope to have helped you ?
HI Guys,
I'm on android pie (Whyred) on the Pixel Experience ROM. Although I could take full nandroid backup using TWRP, when I try to restore the same, the phone is not booting into system and gets stuck at mi logo. Also, there is no error message while restoring, it seems to go well.
So this made the rom switching very hard and I don't like to use Titanium backup as it requires root. I just need that Nand restore.
Do you guys face the same issue? is there any solution to this?? Please pitch in guys.
Thanks in advance:good:
Hi all, I'm currently running miui EU rom 11.0.11 with bootloader unlocked and TWRP installed. However there are so many different twrp recoveries available all with different things working....
So far I've only flashed one rom since I've got the phone but with all these amazing looking custom ROMs around, I'd like to try out a few but it seems backup and restore is currently not possible.
TLDR: anyone know of a TWRP with working backup for Xiaomi redmi note 9s CURTANA?
Cheers
1qazwsx4 said:
Hi all, I'm currently running miui EU rom 11.0.11 with bootloader unlocked and TWRP installed. However there are so many different twrp recoveries available all with different things working....
So far I've only flashed one rom since I've got the phone but with all these amazing looking custom ROMs around, I'd like to try out a few but it seems backup and restore is currently not possible.
TLDR: anyone know of a TWRP with working backup for Xiaomi redmi note 9s CURTANA?
Cheers
Click to expand...
Click to collapse
You should use the latest recovery version available, I think now is the OrangeFox recovery, it's the unified (miatoll) version. To can make backup, the recovery need to able to handle the encryption installed by ROM. To restore the backup... another challenge. I using only data backup and when want to restore, I wipe data, flash the rom, wait for first boot (set same pin code as used in backup), than restore the data in recovery. In case of unlucky situation (encryption difference between "restored" and previous rom, the rom stuck at first boot and need to format data partition (will delete internal storage too!!).
I use ofox recovery, having stock rom in an sd card and migrate backup I just flash new rom and when I want to come back, I flash stock and restore migrate. Nandroid backups are a bit risky I think.