So when I tried restoring a backup it did not boot and when I booted back into TWRP all my files are crypted... it didn't prompt me to enter my password... what can I do?
never mind, I just wiped...
Related
So I read the tutorial on how to remove the MTD mod. I cant seem to get it to uninstall though. I tried flashing a new recovery image through terminal emulator and then doing a factory reset/wipe. Here are the steps I did to attempt to get rid of the MTD mod, please let me know where I went wrong here, thanks.
Flashed a new recovery via terminal emulator
Rebooted phone into recovery
Performed a nandroid backup of current ROM
Performed factory reset/wipe
Rebooted recovery
Nandroid restore of ROM
When this didn't work I attempted this:
Rebooted into recovery
Modified mtdpartmap.txt file with MTD 0
Ran the boot patcher
Factory reset/wipe
Nandroid restore
Both methods did not remove the MTD resizing I did. What/where did I go wrong?
All I do is run the boot patcher then reboot.
Wouldn't nandroid restore just return it to whatever it was when you backed it up?
PcFish said:
All I do is run the boot patcher then reboot.
Wouldn't nandroid restore just return it to whatever it was when you backed it up?
Click to expand...
Click to collapse
Nandroid restore only restores the ROM itself though doesn't it which wouldnt impact the recovery image and boot flasher?
Ok, so I did the nandroid restore and then I ran the custom boot patcher with my mtdpartmap.txt set to MTD 0 and rebooted...looks like im stuck at the start up splash screen...what is going on???
EDIT: Figured it out:
Formatted system, data, and cache
Resized mtdpartmap.txt to "mtd 0"
Flashed boot patcher
Advanced nandroid restore of system, data, and cache
reboot
ROM booted right up and I am back to stock partition sizings.
Well... I installed Vicious V2 of the Jellybean ROM (toro), and things were running OK. I used titanium backup to try to restore my SMS data, and found that I could not boot back up. It just bootloops. Since then, I have tried mutliple things, but nothing ends it...
I've tried:
*Restoring a NANDroid, but /data will NOT restore, and phone will bootloop.
* factory Reset/reinstall old AOKP ROM. It will not boot.
*Reinstall Jellybean ROM. Still bootloops
*I'm working on trying to get ODIN to detect my phone, but my computer won't stop detecting it as "Samsung ADB Interface". I've verified there is no response from ADB while in ODIN mode on the phone.
I just... can't stop the bootloops. There is another thread of the same issue, but his resolved over time. Mine doens't seem to be... I really want my phone to boot. The interesting thing is that none of my Nandroids will restore "Data". It just says "Completed in 0 seconds"
Are you able to use fastboot?
Sent from my Captivate
Yes.
Speaking of fastboot, I can re-flash my recovery just fine. I've tried everything on both Clockwork, and TWRP. Results are the exact same.
Same thing
Mine did the exact same after installing the same ROM after a TiBu restore (no system apps, no sms just regular apps with data). I tried wiping/reflashing several ROMs I had on the SD to no avail, all my nandroids would fail to restore data. I finally ended up using the Odin method I found to flash it back to stock 4.0.2 unrooted, unlocked. I lost all of my data on the SD card in the process.
I loved JB and would like to install again if I could find out what I did wrong to avoid this mess, any input guys?
Just a note: In recovery you have access to ADB. You can backup your SDcard with the command "adb pull /data/media C:\SD_backup"
It will save to... C:\SD_backup
If you get a file not found then, "adb shell", then "mount data", then "Exit", then try the adb pull again.
I'll keep messing with drivers then to see if I can get ODIN to detect me.
I'm an idiot. ODIN was seeing my phone the whole time. I just forgot where it shows that the phone is connected. I'll try an ODIN in the morning. I'm backing up my SD right now. I need sleep.
Edit: Nevermind.. It doesn't see it while in Odin mode.. but does see it on and off while booting into recovery.
Edit 2: I found that it was indeed a driver error. Fixed. Now back to backing up my SD card that I accidentally interrupted. I'll report back my ODIN results after I wake up.
my phone is doing the exact same thing
I was able to bring my phone back to life with ODIN restoring a 4.0.2 factory image.
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error while restoring /system!
I did nothing but boot into recovery and this is all that happens when trying to recover my cwm backups. The version of CWM should not have changed and I've flashed these files before. I accidentally started another backup and shut the phone off while it was plugged in through usb (debugging might have been enabled but I don't use adb commands or have a shell).
I can restore my rom but I want to restore my backup.
How can I know the version of the backups and see if they are different from the cwm recovery version? Also in the past I have flashed and backup through rom manager, but would my rom manager boot into cwm recovery load a different cwm recovery (it shouldn't)?
I also tried this...reload the rom but restore each partition except for system, but it fails on data too then.
At a loss here. I love my backup. I was just a system camera apk away from perfection
Please help
Solution: 5 hours of playing around and the solution is that you need to make sure the cwm version is always the same...through rom manager.
I have a modified TWRP .28 and I have tried to restore a backup. It succeeded, but with a few errors.
The restoration reached 100%, but then it froze. I was unable to navigate the recovery, so powered of my device by pressing the power button. I figured that since it said 100%, the restoration process would be successful, and TWRP just froze. But once I booted up (because boot was successful, no bootloops), I saw that everything was fine, BUT I DIDN'T HAVE MY APPS, DATA, AND SETTINGS CONFIGURATION.
At least my backup wasn't faulty faulty... But if a backup messes up, you're screwed. If anybody knows what happen, please help.
I have a problem with my TWRP backups created for 32.3.A.2.33 version. When I restore them, the phone restarts once and in the next boot int goes into recovery directly.
I have flashed:
E6853_32.3.A.2.33_1299-1511_R3D.ftf
Boot and recovery from:
https://forum.xda-developers.com/z5...ting-xperia-z5-z5p-variants-drm-keys-t3437902
And works perfectly, backups creates correctly from recovery, but when I try to recover them doesn't work.
The problem seems to be in system partition , data partition recover with no problems.
Any suggestions?
I have the same problem.
srg84 said:
The problem seems to be in system partition , data partition recover with no problems.
Any suggestions?
Click to expand...
Click to collapse
Is dm-verity turned off in kernel? If not this is the reason why. You need to backup system image instead of backup files from system partition like usually in TWRP.
Can you try to make backup and restore with this recovery?
flash with "fastboot flash recovery lineage_twrp_recovery.img"
To boot into recovery power off phone, wait 5-7 sec then press power+vol_down until it vibrate.
Select "System Image" to system partition backup.