Related
hello I just replaced a broken EVO and now that it is rooted I am trying to restore my old backup from my previous evo.. I am having a problem though
I go through all the normal process to restore a backup and everything works fine the super user permission pops up and the phone reboots but instead of rebooting directly into the reboot session it just boots me into the clockwork mod recovery recovery menu.. when i select the folder the recovery files are located in it shows up blank.. what am I doing wrong here? In the past when I selected to restore a backup from inside the os it just rebooted and started restoring automatically.. I feel like an extra step has now been added and I dont know what it is?
I should also not that while I do not know if it is related or not when I try to restore the backup from the nandroid section of the recovery menu it hangs on checking md5 sums and then says error while flashing boot image!
mind you this is on 2 separate backups I created in the past with clockwork mod recovery
It's probably not a good idea to use an old nandroid backup on a new phone. Think of how kernels run well on some EVO phones and not others. Your current phone might even be one of the EVOs with new hardware.
Sent from my HTC EVO using XDA app
ok but can I still get all my apps and data back?
it would be terrible to lose all of that
and now to make matters even worse my phone is stuck on an endless loop on clockwork mod recovery I every time I select reboot system now instead of it booting into the stock rooted rom it just reloads the clockwork mod recovery menu.. what gives?
yeah, not good to load a backup from a different phone. This has been documented as happening. Just reflash whatever rom you want then radios then kernel. Sorry but if you didn't use a backup prog I thinkyou will have to manually restore apps. You may want to try titanium backup, solves the problem, use it and follow the backup instructions in Titanium backup wiki on their web site and you should be good to go next time.
Did you try a battery pull and reboot?
Sent from my HTC EVO using XDA app
Nandroid backups are phone specific, you can't move them from phone to phone. You probably hosed your RSA keys which means your 4g may be broke. If I were you I would try to flash a stock rom and then reroot if needed. If that gets you out of the bootloop your in. You maybe visiting a Sprint store for a replacement phone again.
guys I could really use some help here please!
I went back to the stock rooted rom today.. all day I was adding apps making changes restarting the phone no problems.. I finally get my phone set up how I like it so I decided it was a great time to make a backup so I open clockwork mod recovery and select backup it gives me the superuser permissions prompt and restarts.. instead of starting the backup automatically it sends me directly to the clockwork mod recovery menu and now it will not load the phone's OS at all just reboot after reboot into clockwork mod recovery this is a 1 day old evo what is going on here!!??
KingKash420 said:
guys I could really use some help here please!
I went back to the stock rooted rom today.. all day I was adding apps making changes restarting the phone no problems.. I finally get my phone set up how I like it so I decided it was a great time to make a backup so I open clockwork mod recovery and select backup it gives me the superuser permissions prompt and restarts.. instead of starting the backup automatically it sends me directly to the clockwork mod recovery menu and now it will not load the phone's OS at all just reboot after reboot into clockwork mod recovery this is a 1 day old evo what is going on here!!??
Click to expand...
Click to collapse
Hey that exact thing happened to me. it happened the first time i ever loaded anything on my phone. I freaked out. Turned out the Clockword mod recovery I had must have had something wrong. I went back into the part where you load the CWM from the computer. My phone is different than yours so I cant be sure but you go into bootloader by pressing stuff, its where the logo stays there the whole time. then you flash the CWM again. and then reload the operating system and stuff. should work but just redo the CWM again. Hope it works out for you. Hope thats what it is for you too.
So I've rooted my phone, got the latest defy clock work recovery thats in the clockwork thread, I've booted into recovery mode and made a backup.
Now I've downloaded a 3.4.3-11 zipped nandroid backup with the img files etc, but when I try installing from them it just sits there doing nothing.
The progress bar stops animating and it looks as if its hung, I left it for 15 minutes and nothing happened so I pulled the battery, phone restarts and boots fine.
I've tried multiple images and they all cause clockwork recovery to hang when attempting to install them.
Can anyone suggest what I might be doing wrong?
Using everything listed in this post:
http://forum.xda-developers.com/showpost.php?p=12122439&postcount=10
from this thread:
http://forum.xda-developers.com/showthread.php?t=993402
edit: If it toggle verification on it says this
E:signature verifications failed
installation aborted
what should I do?
no one ever had this issue before?
Found someone else who also has this problem.
can anyone out there help ?
kind of confused here... What's hanging, CWM? or RSD? You said that flashing SBF causes clockwork to hang.....Thing is..... clockwork don't flash SBF's.
You need RSD for SBF's, clockwork will restore nandroid or apply unsigned .zip updates among many other things but no SBF
zyxwvut said:
kind of confused here... What's hanging, CWM? or RSD? You said that flashing SBF causes clockwork to hang.....Thing is..... clockwork don't flash SBF's.
You need RSD for SBF's, clockwork will restore nandroid or apply unsigned .zip updates among many other things but no SBF
Click to expand...
Click to collapse
Sorry I meant nandroid zip files with the .img files inside of it, not sbf.
So yes clockwork hangs when trying to install zip file with img files in it.
What would cause this to happen and how should I rectify it? I would post in the clockwork thread but I dont have enough posts.
The issue was I was trying to apply an update.zip when what I wanted to do was restore a nandroid backup, being as it didn't give me the option to select any folder other than the clockwork folder I got confused.
Followed these instructions and all is well
the method i could understand:
maybe wrong, i'm warning you..
maybe you could ask someone who real capable of this.
i'm just trying to answer..
Preparing files needed, needed when you want to go back to 2.51
-download SBF of your stock (2.51)
-got root, install custom recovery, restart.
-when phone is ready go to custom recovery app, and install recovery then reboot.
-and then create nandroid backup from custom recovery.
Upgrading froyo with downgrade-ability
-download fixed SBF and nandroid backup of this froyo version.
-from custom recovery, wipe all cache.
-and then restore nandroid backup of the froyo rom
-restart and IMMEDIATELY go to bootloader. immediately press and hold VOL.UP+POWER after you press restart system on custom recovery
-on bootloader, flash the fixed SBF of that froyo rom with RSD Lite 4.9, and make sure you already download motorola driver...
Downgrading:
if you want to go back to 2.51,
-got root, install custom recovery, restart.
-go to custom recovery, and then RESTORE your 2.51 nandroid backup
-restart and IMMEDIATELY go to bootloader. immediately press and hold VOL.UP+POWER after you press restart system on custom recovery
-on bootloader, flash the fixed SBF of your stock 2.51.
Click to expand...
Click to collapse
maybe just another issue pertaining the restoring of nandroid backup. what is the issue if i get a md5 sum mismatch? i did all the thing, flashed sbf, root, wipe and when goes to restore, it just have the md5 sum mismatch. i'm using kb7sqi recovery
Have u checked if usb debugging is off? After rooting u should disable it.
Sent from my MB525 using Tapatalk
what are you doing to cause md5 mismatch??? You go into recovery and suddenly you are greeted with md5 mismatch or is it when you are trying to restore a nandroid? Or is it while applying an update?... Anyhow, if it's wile restoring a nandroid, be sure that a nandroid.MD5 file is included with the package you downloaded. If not you could try advanced restore or find a package with a md5 file or recalculate md5 yourself
roland_harrison said:
The issue was I was trying to apply an update.zip when what I wanted to do was restore a nandroid backup, being as it didn't give me the option to select any folder other than the clockwork folder I got confused.
Followed these instructions and all is well
Click to expand...
Click to collapse
Glad you got it sorted.... I have flashed almost every rom out there. Many many many sbf's. I have bootlooped a few times while experimenting, but always bring it back from the dead. These phones are honestly pretty resilient to user error. As long as the instructions for flashing a particular rom are followed exactly as instructed.. It ALWAYS works. When things go bad boot into stock recovery, wipe, pull battery, hold vol+ while inserting battery to get into bootloader then flash an appropriate sbf and youre back
So i tried to flash muiu rom thru rom manager and got caught in a reset loop at the boot screen. I then flashed a old cm7 zip from the recovery screen just to get the phone to boot. When i tried to restore my backup from rom manager it takes me to the recovery screen and does not restore ( just stays at the recovery screen). i really would like to restore that backup. any suggestions?????
Well, this won't help your back up problem, but trying wiping everything you can, except the SD Card and the flash MIUI in Recovery.
ROM Manager is really not a dependable way to flash a ROM.
Also, you try to reflash your recovery before you do anything and try the back up again.
Oh, and if you're not on it now, use Amon Ra for Recovery. Plenty of threads that tell you how to get it.
Thanks but is there any way to restore the backup I made with rom manager in recovery?
Hey guys,
I have kind of a serious issue right now. I used Touch Recovery 5.8.0.2 and made a full backup today of my whole ROM (2.5GB) before trying out some mods which eventually didn't work. So I decided to wipe and restore the backup I made. No matter what I do I cannot get it to restore my data partition properly. I keep getting "Error while restoring /data!" message, however it does the boot image and system fine but doesn't continue to cache and sd-ext because of the failed data. Whenever I boot it up, some of my apps are missing from the home screen and practically all of them are not working when I launch them (force close). I also get boot up error of Google+ force close, among a bunch of other issues. This is happening even when I try to restore an older backup as well. My device is not working state right now and although I can just restore the stock images to get it working again, it is urgent that I restore my data ASAP! I tried wiping several times and even using the non-touch 5.5.0.4 recovery to restore and same thing keeps happening.
Any help would be highly appreciated!
Please don't tell me my backup is corrupt
Update 1: Eventually I gave up and started from scratch but I have confirmed already this happened on a fresh backup as well, at this time we are trying to figure out what is causing this so I can go back to safely backing up and restoring backups.
Update 2: We have test builds of TWRP Recovery that may have resolved this issue! We need testers!
Please see this post: Link Here
Update 3: We have test builds of ClockworkMod Recovery 6 that may have resolved this issue as well! We need testers!
Please see this post: Link Here
***Always see last few posts on the thread for updates on what we discovered just in case I don't update the OP***
Unfortunately I also have the same error today!
Please help us out.
JayantSparda said:
Unfortunately I also have the same error today!
Please help us out.
Click to expand...
Click to collapse
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Hi Spectre85,
My phone did fine yesterday, I was running AOPK Milestone 3 with FAUX123 kernel.
But when I woke up, my phone looked like it's battery was emtpy.
- When I plugged the phone with the charger, I started the phone again.
- Unfortunately my phone keep looping at the Google screen over and over.
So I pulled the battery and put the battery back again in the phone.
- I went to the bootloader and went to CWM recovery.
Deleted Data, Cache and Dalvike cache.
- Tried to retrieve my backup rom, but keep getting this "Error while restoring /data!" message.
I've tried to install other roms as well, but I still keep getting the bootloop at the Google screen.
Have you guys have any advice for me?
spectre85 said:
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Click to expand...
Click to collapse
For me, no, no (CWM Touch 5.8.0.2), yes (stock rooted 4.0.4), no but my goal is to restore my data not erase it.
I had this happen to me before, what I did was flash a factory image through fast boot and it was fine after.
Sent from my Galaxy Nexus using xda premium
Thanks guys..I flashed the factory image through Fastboot mode and the phone works perfectly again! Too bad I lost all my data, but I'm happier that I have my phone fully functional again
You can't access your backup right? There's no way you can copy the file to your desktop?
mohitrocks said:
You can't access your backup right? There's no way you can copy the file to your desktop?
Click to expand...
Click to collapse
I did copy it. I have full access to the file. Also, just fyi my goal here is not just to get to working state (I'm aware of the stock images) but to actually recover my data. My phone is currently on stock images completely blank and working now.
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
bwcorvus said:
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Nanadroid files can be flashed in fastboot? Are you sure? First time I'm hearing this. Doesn't fastboot need .img files? These are .tar files.
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
bwcorvus said:
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I guess it depends on the recovery version you use. I remember older versions actually had .img files. However 5.5.0.4 and Touch 5.8.0.2 both have ext4.tar files.
Which version of recovery do you use?
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Immix said:
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Click to expand...
Click to collapse
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
open1your1eyes0 said:
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
Click to expand...
Click to collapse
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Immix said:
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Click to expand...
Click to collapse
You're right. This works great for restore data to select apps (got my notes and game saves back). I think the icon layout is held in the launcher settings, I'm about to try and restore the data to the launcher app and see what happens. I'm making a CWM backup of first of my current state (that's assuming this backup will actually work).
EDIT: Yes! That did it! Widgets position weren't saved but it's ok I only had a few so I manually put them back. Thank you! I never knew TB had the ability to work with nandroid backups.
I guess this now just leaves me figuring out what went wrong with the CWM backup. It happened twice (I have two backups from the same day that won't restore). Does anyone else use CWM Touch 5.8.0.2 and have successful backups? I would experiment to see if it works now but I don't want to end up with a corrupt backup and redo everything again.
Yes with me its the same thing my data its corrupt is even worse every time I do a nanobackup and restarted my phone the phone freezes on the boot logo and I have to go back to recovery trying to use my backups but I can't so I have to flash a new from again and start from the beginning again!!!! Anybody here has the same experience with that ???
So AGAIN, I'm having the same issue. This time on a recovery 5.5.0.4 that used to work for me when I originally got my phone. I think either my data partition might be too big or something but this really needs to fixed pronto. Anyone know how to contact Koush directly in regards to this matter?
Hello! I am posting this because i'm new to this rooting/custom roms thing. OK. So i have a Galaxy Note 2 GT-N7100. I rooted it using odin, then tried to install new rom. Downloaded CWM, booted into recovery mode and installed new rom. After this, i accidentally pressed 'Reboot' instead of installing gapps & wiping cache and that stuff. Now, my phone starts with the new rom, but i can't get back into recovery mode to start over. When i press vol-, home and power button, after pressing vol+ it goes into download mode (i can't do anything here). Any help will be appreciated!
UPDATE! I tried to flash odin recovery, and now my phone is stuck at the bootscreen. The only thing i can do is get into download mode. PLEASE HELP!
I've managed to get rid of the problem above by installing original firmware from samsung (android 4.3) and worked. The problem is, after that, i installed X-note rom (v2.1) and i think my imei is corrupted now. When i installed x-note, it asked me if i want to make an efs backup, and i accepted. If this is the problem, does anyone know how to restore the backup made? I found it on phone memory (i know it exists) but when i go into recovery mode in cm and i click restore from /sdcard nothing happens (no files to restore). Can someone tell me how could i restore the efs backup?
P.S. I checked phone's IMEI and it starts with 0049.
darkn3ss88 said:
I've managed to get rid of the problem above by installing original firmware from samsung (android 4.3) and worked. The problem is, after that, i installed X-note rom (v2.1) and i think my imei is corrupted now. When i installed x-note, it asked me if i want to make an efs backup, and i accepted. If this is the problem, does anyone know how to restore the backup made? I found it on phone memory (i know it exists) but when i go into recovery mode in cm and i click restore from /sdcard nothing happens (no files to restore). Can someone tell me how could i restore the efs backup?
P.S. I checked phone's IMEI and it starts with 0049.
Click to expand...
Click to collapse
Alright so what is the back up extension ? Is it efs.IMG? Is it 20 KB ?
Please note that restoring efs backup has nothing to do with CWM recovery, its a program you download on PC that backs up and restores your device.
With regards,
Overdub
Sent from my GT-N7100 using Tapatalk
Hi! My efs file is .tar and it is <1kb, somewhere around 20 bytes. When i open it, it doesn't show any items in the archive.