Be careful with TeamWin Recovery - Optimus One, P500, V General

Got md5 error then I tried to restore my recent backup (last version of that recovery) after full wipe. Lucky me, I had 1 week old backup (I think 1.3.0.8 version of that recovery) without md5 problems. I suggest everyone do nandroid backups with another recoveries, so you don't have what critical situations. I will go back to CWM recovery, it never make me such ****.

Related

[HOW-TO] backup and restore using nandroid

ok guys, here we are again.. you're wanting to backup your phone for if you want to try a test rom, or just to have a backup in case something goes wrong. this tut will show you how! I will also explain how to restore your phone to a backup you've previously made. it is also possible to backup/restore using rom manager but this is the harder way.. not too hard once you figure it out, but thats all opinion
Pre Requirements:
1.) be rooted
2.) have clockwork recovery installed
3.) not a necessity, but it DEFINITELY helps to have the engineering build installed at least once
BACKUP STEPS:
1.) boot into clockwork recovery mode
2.) scroll down to nandroid and select
3.) click backup
4.) it will now automatically backup your ENTIRE PHONE.. this includes your contacts, messages, emails, everything you have on the phone prior to booting into recovery. you will see a yellow bar at the bottom that shows progress
5.) REBOOT!
6.) there is no step 6... you're done
RESTORE STEPS:
1.)boot into clockwork recovery mode
2.) scroll down to nandroid and select
3.) scroll down to restore and select
4.) scroll to your desired restore nandroid and select
5.) scroll to yes and select
6.) it will now auto restore your backup and everything in it. when done it will tell you DONE!
7.) reboot and you're done!
well there ya go guys, one (two?) more tut(s) done and have fun be safe and remember to wipe if you're ever scared you have a boot loop
I actually do have a specific question about these nandroid backups. If I backup, then flash a "updated" ROM (update to an existing one already installed), and THEN do a restore, does the restore take me back to the previous version of the ROM? I've never used the nandroid backups as I usually never have a need to.
the restore takes your phone back to exactly how it was when you performed the backup
Gotcha, so if you backup, wipe, and then update a ROM, you cannot expect to be able to use your nandroid backup to restore anything you had previously, unless you wanted to go back to the ROMs previous version... gotcha.
where are these backups stored?
I think it's /sdcard/clockworkmod/backup/[BackupDate]/
is it safe to remove them from the sdcard & store for safekeeping until needed & replace in same location?
yep, sure is!
Is it necessary to perform a wipe before restoring, if you currently have a different ROM than what is being restored? Or does nandroid wipe for you?
romis138 said:
Is it necessary to perform a wipe before restoring, if you currently have a different ROM than what is being restored? Or does nandroid wipe for you?
Click to expand...
Click to collapse
no, nandroid doesnt wipe for you. i suggest always wiping if you're changing roms
hi im kinda new to this, but I rooted my slide using the tuts from droiddog.com and here. Got mostly everything working but when I try to backup my current rom clockwork crashes and it doesn't take me to recovery and just reboots the phone. Ive tried clearing the download cashe and downloading an older recovery but nothing seems to work. I basically cant boot into recovery to make backups or flash any roms. any suggestions on what else I could try.
I gave this explination of a nandroid to a friend of mine today. It will act like a time machine and put your device back exactly as it was when you did the backup. Now if you need an explination like that, you realy should not be messing with your phone that way.
freeze
hi
i have a problem. when i try to restore my backup. everything looks fine. but when restoring finish and reboot my phone screen is freezing on htc logo. what can i do?
sorry for my bad english!
Just wait it takes a while to boot sometimes, treat it like you would treat a new ROM being flashed.
i need to wipe data/factory reset or?
ok
i wipe data.. restore backup from nandroid.. reboot phone and i waiting almost 30 min and screen still show only htc logo..
I have copied the nandroid backups on my SD card
but in recovery mode, it is not showing any nandroid backup file ?
warewolf4586 said:
I have copied the nandroid backups on my SD card
but in recovery mode, it is not showing any nandroid backup file ?
Click to expand...
Click to collapse
is it in the sd\clockworkmod\backup folder??
Hello,
I have a question about Nandroid backups using CWM...I read on some forum that...the backup and the installed version of CWM recovery should match to make it work..I.e If I took the backup using CWM version 5.0.0.0 I have to use the same CWM recovery version to restore the ROM and I can not restore nandroid backup using the later version lets say 5.0.1.5 of CWM...is it true?
Thanks..
I kinda doubt that. Itd be much more likely that a nandroid created by 5.0 couldnt be used by an earlier version. I doubt that is true either, just more likely than the other way around.
Nothing wrong with waiting for better confirmation than mine, but if it were an issue I think wed have heard a lot more about it by now.
Sent from my SGH-T999 using xda app-developers app

Nandriod Restore - Need Help

I am having a strange issue with restoring a nandroid backup. It started on TWRP V2.0 so I went gone back to V1.1.1 and it is still happening.
When I try to restore a nandroid and after the reboot completes for some reason I have to re-set up everything like a fresh install. Here is what I have checked when I make a back up: system, data, boot, recovery, wimax, .android_secure and compress. Also just to clarify, should I do a full factory reset or just wipe cache/dalvik?
Thanks for any insight as it has me stumped.
If you're restoring a sense ROM with a LOT of apps on the SD it (sense) doesn't seem to play nice. I've had success restoring system and boot, botting, then restoring just data. YMMV. Make sure you're not also restoring cache, and of course wiping properly first.
il Duce said:
If you're restoring a sense ROM with a LOT of apps on the SD it (sense) doesn't seem to play nice. I've had success restoring system and boot, botting, then restoring just data. YMMV. Make sure you're not also restoring cache, and of course wiping properly first.
Click to expand...
Click to collapse
Thanks il Duce. I don't have any apps on SD. I did a fresh backup with just system and boot checked and still have issues with it not working correctly. Every time I restore a backup it keeps putting me back to having to set everything up again.
I am not sure what is going on, but can't seem to figure out how to fix.
If u are hboot 1.5 S-On Unlocked, keep in mind you may have problems restoring Nandroid (recovery) backups, ie boot.img/kernel, if you don't use fastboot to enter recovery first ( fastboot boot YourRecoveryFilename.img ) .
I had some similar issues (see link in my signature for specifics & walkthru). The new Cwm Touch 5.img file loaded up for me. Cwm v4.0.1.4 & TWRP2.0 were the only others that would work on mine.
I had a few posts in this other thread that might help too...
http://forum.xda-developers.com/showthread.php?p=22054499
(Q) How To Flash A Recovery From Bootloader 1.5
Sent from my "Up all night, sleep all day" Evo3D via Tapatalk.
mpgrimm2 said:
If u are hboot 1.5 S-On Unlocked, keep in mind you may have problems restoring Nandroid (recovery) backups, ie boot.img/kernel, if you don't use fastboot to enter recovery first ( fastboot boot YourRecoveryFilename.img ) .
I had some similar issues (see link in my signature for specifics & walkthru). The new Cwm Touch 5.img file loaded up for me. Cwm v4.0.1.4 & TWRP2.0 were the only others that would work on mine.
I had a few posts in this other thread that might help too...
http://forum.xda-developers.com/showthread.php?p=22054499
(Q) How To Flash A Recovery From Bootloader 1.5
Sent from my "Up all night, sleep all day" Evo3D via Tapatalk.
Click to expand...
Click to collapse
Tottally agreed.
I would suggest installing the Rom you want and just restoring data if your data will be compatible with the Rom you have if you have hboot 1.5
Sent from my PG86100 using Tapatalk

[Q] CWM md5 errors

I just booted into recovery to try and do a full nandroid backup of current miui system and then restore my checkrom backup.
After it completed the backup it finished with the message 'error generating md5 checksum' (or something to that effect). I wasn't too worried but when i tried to restore my checkrom backup it said 'md5 mismatch' (or whatever) and did not restore.
Should i be worried about this and is there anything i can do?
Thanks
The patch attached to my post works with older builds of Galnet Miui that had this problem. I guess it would probably work with other Miui variants. Tho I seriously doubt it will do any harm if you flash it, obviously if you do, you do so at your own risk
Flash it in CWRecovery, reboot into recovery and you should be able to run your backup fine.
the problem is with a missing nandroid-md5.sh script in the recovery image...

TWRP 2.8.5.0 fails to backup encrypted phones and restore password-protected backups

Recently, I've been experimenting with increasing the security of my phone which was recently migrated to CM (12.1) and TWRP (2.8.5.0). Let's just say that it did not go well.
First, I tried enabling a password for my TWRP backups. I set the password/encryption option and the backup seemed to complete fine.
Problem 1:Next I tried encrypting my phone. The encryption worked fine, but once the phone was encrypted, I noticed that TWRP lost the ability to create a nandroid backup. As soon as I enabled encryption, TWRP now prompts for a password automatically when it is launched. However, when I typed my passphrase, it says "Password Failed, Please Try Again".
Problem 2:Given that I've lost the ability to do a nandroid backup, I decided to revert the decision to encrypt the phone. Which basically means wiping the phone and restoring my latest nandroid phone. The wipe went fine and the restore proceeded without error. However, upon booting up the phone, it acted as if it just went through a factory reset. (e.g. a cleared /data partition). Just as an experiment, I tried restoring a week-old TWRP backup that was not password-protected. Once I rebooted the phone, its state was identical to how it was when I backed it up. I tried going into TWRP to restore the more-recent password-protected backup, but this time I purposely typed the wrong passphrase. It said that the password was incorrect. So I typed the actual passphrase, restored the backup, and once the phone rebooted, it was back to the factory-reset mode.
Conclusions:
TWRP 2.8.5.0 cannot back up an encrypted phone. At least my M8.
TWRP 2.8.5.0 cannot restore password-protected backups.
While an encrypted phone and encrypted nandroid backups are a good idea from a security perspective, they appear to just not work. The fact that the features are advertised as working is frustrating.
Questions:
Will a newer TWRP version address either of the problems? I installed 2.8.5.0 as I had heard of some issues with newer versions.
If TWRP doesn't work for this, is there another recovery image that will both backup encrypted phones as well as support the creation and restore of password-protected/encrypted backups?
Note that I tried the latest 2.8.7.0 build of TWRP: https://twrp.me/devices/htconem8gsm.html . Although the title in that page says "all variants", the URI includes "GSM" which my phone is not. However, I can't imagine why there would be carrier-specific builts of TWRP in the first place. 2.8.5.0 is the latest Verizon-specific build of TWRP for the M8: https://twrp.me/devices/htconem8verizon.html
Anyway, when I try to do an encrypted backup with 2.8.7.0, I get:
createTarFork() process ended with ERROR=255
Which apparently has been reported by others:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/452
I get the impression that this stuff isn't close to ready for prime time.
Although I suppose that erroring at backup time is better than backing up w/o error and then only noticing that there's a problem at restore time (when you really need it). For what it's worth, looking at an encrypted TWRP file (e.g. data.ext4.win400) that was created by 2.8.5.0, it does indeed look to be encrypted. It has high entropy and magic bytes of "OAES". But something about the restoration of such a backup fails. It's not clear at this point if the two issues are related.

Bootloop aftert restoring a TWRP backup

As the title says I always get a bootloop into recovery when the restore process finishes.
I tried everything, flashing the same rom as in the backup before restoring, however it never boots normally.
As I am on a stock MIUI 13 I flashed the stock image and then restored the backup, still a bootloop into recovery.
No matter what I do I am unable to restore my TWRP backup, so every time I want to try a new ROM I end up reinstalling everything from scratch.
Is it because my data is encrypted, or dynamic partitions? This never happened with any of my previous phones, is it possible to restore a backup on Mi10?
alfaholic said:
As the title says I always get a bootloop into recovery when the restore process finishes.
I tried everything, flashing the same rom as in the backup before restoring, however it never boots normally.
As I am on a stock MIUI 13 I flashed the stock image and then restored the backup, still a bootloop into recovery.
No matter what I do I am unable to restore my TWRP backup, so every time I want to try a new ROM I end up reinstalling everything from scratch.
Is it because my data is encrypted, or dynamic partitions? This never happened with any of my previous phones, is it possible to restore a backup on Mi10?
Click to expand...
Click to collapse
Backups and restore on the TWRP with some phone models does not work correctly either because it does not decrypt or is too old compared to the rom or you try to restore an older rom version on a more recent rom and sometimes the reverse also does not work (because of the system).
Try a more recent Twrp (just in case) but anyway the restoration will not be done with a more recent Twrp.
If you are on MIUI micloud works relatively well but obviously you can only restore the data not the system.
https://androidfilehost.com/?w=files&flid=318277
alfaholic said:
As the title says I always get a bootloop into recovery when the restore process finishes.
I tried everything, flashing the same rom as in the backup before restoring, however it never boots normally.
As I am on a stock MIUI 13 I flashed the stock image and then restored the backup, still a bootloop into recovery.
No matter what I do I am unable to restore my TWRP backup, so every time I want to try a new ROM I end up reinstalling everything from scratch.
Is it because my data is encrypted, or dynamic partitions? This never happened with any of my previous phones, is it possible to restore a backup on Mi10?
Click to expand...
Click to collapse
try flashing miui 12 rom first, then restore twrp back up (format data also before restoring)
and chose the latest version of twrp for android 11 or 12 (depends on your Rom)
maybe it will work

Categories

Resources