Jump to content

Blade stuck in boot loop after Nandroid Backup?


Recommended Posts

Guest richardw1992
Posted (edited)

So I thought it would be a clever idea to do a Backup through clockworkmod recovery today and try and organise some of my previous backups.

I proceeded by doing a full backup (Backup 3), everything appeared to be fine.

For the purpose of this post I will refer to the backups in this order:

- Backup 3 (most recent)

- Backup 2 *Name here*

- Backup 1 (oldest)

I then thought I would name some of my older backups so I knew what was what, I started by naming one (which I knew what it was). I did so using a file manager through my device, the backup I named was Backup 2.

I then restored Backup 1 (Foolishly without wiping data or cache) to see what it was to name it, this all went to plan.

So I then tried to restore my most recent backup 3, the one I made a few minutes prior to this, in order to name the 'backup 1' folder whilst It wasn't loaded to my device, if that makes sense?

However Backup 3 now just gives me boot loops, even after wiping use data and cache, dalvik cache etc..

Back up 2 just says "Checking MD5 sums... MD5 mismatch!" even after changing the original folder name back to what it was.

So essentially I have a working phone, although the only way I can get it to work is on backup 1, which is quite old :huh: So I would like to know if there is any way I can get back to backup 3 which is the state my phone was in just a few hours ago!!

Further information:

Backup 1 = JJrls9

Backup 2 = JJrls9 with a theme applied

Backup 3 = JJrls9 with same theme applied, and 'dialler partial wake fix' applied.

Any help would be much appreciated! After what I thought was a sensible idea organising my backups, I have caused more stress and problems than good!

Cheers.

Edited by richardw1992
Posted

You changed the file names therefore the MD5 sum does not match anymore - it assumes the file is corrupt.

The only way out that I know of is to rename it back to the EXACT original name otherwise go back to backup 1 or flash a new rom and start again.

Never change the names of backups! (I made that mistake once)

Posted (edited)

It's because of the theme.

This may or may not work - Restore your backup #3, then flash the jj9 zip, wipe dalvik-cache, reboot. After it's booted, then you can flash your theme or the partial wake fix - they change the same file, so not sure they'd work properly together, flash the theme first then the partial wake fix if you're going to do both.

Edited by wbaw
Guest richardw1992
Posted
You changed the file names therefore the MD5 sum does not match anymore - it assumes the file is corrupt.

The only way out that I know of is to rename it back to the EXACT original name otherwise go back to backup 1 or flash a new rom and start again.

Never change the names of backups! (I made that mistake once)

I did rename it back exactly! It still doesnt seem to like it though.. Anyway Backup 3 is the one i'm really after here.

Guest richardw1992
Posted
It's because of the theme.

This may or may not work - Restore your backup #3, then flash the jj9 zip, wipe dalvik-cache, reboot. After it's booted, then you can flash your theme or the partial wake fix - they change the same file, so not sure they'd work properly together, flash the theme first then the partial wake fix if you're going to do both.

I had a feeling the theme might have had something to do with it; I'm about to follow your steps, but the first one "restore backup #3 then flash jj9 zip" backup 3 is the one in the boot loop, so are you saying I should flash the clean jj9 zip on top of my boot loop without clearing the cache or data before hand etc?

many thanks guys!

Guest StevenHarperUK
Posted
I had a feeling the theme might have had something to do with it; I'm about to follow your steps, but the first one "restore backup #3 then flash jj9 zip" backup 3 is the one in the boot loop, so are you saying I should flash the clean jj9 zip on top of my boot loop without clearing the cache or data before hand etc?

many thanks guys!

Yes - think of the /System partition as a read only part (Like a CD in the drive)

The starting of android is checking that the files are what it expects - you have put some UNSIGNED (theme) files in there so it wont boot

If you RE-flash the System with the clean (and signed) JJ9 ROM then you are effectively swapping the files that are not right

After ONE boot you can re-enter clockwork and re-add the themes

I know all this because I did it at the PUB the other night (you don't need a PC if the files are already on your SDcard)

Guest richardw1992
Posted (edited)

That seems to make sense,

I just did all of the above, and now the phone boots up fine running JJ9 and the previous themes and add ons I had installed as per "backup 3"

But half of my apps, data etc is not present is this the case?

I'm trying to regain as much of my data from "backup 3" by doing the advanced restore options in clockworkmod.

I guess I will have to re download the missing apps then...?

EDIT

I essentially did the above, and now I am pretty much back to where I was. Thanks for all the input guys, much appreciated!

One thing i'm not clear on though, is it essentially impossible to do a Nandroid backup and restore if the rom has been custom themed then? because presumably the theme files would cause it to boot loop on every restore?

Edited by richardw1992
Guest StevenHarperUK
Posted
One thing i'm not clear on though, is it essentially impossible to do a Nandroid backup and restore if the rom has been custom themed then? because presumably the theme files would cause it to boot loop on every restore?

It was :

It is now fixed - all developers and themer's have started to sign the code with the same key.

Guest Phoenix Silver
Posted

if you want to change the name of the backup no problem

all you have to do is to generate the md5sum again manually

(just check the md5 to be sure that the files aren't corrupted)

astro manager can do it or with your pc :huh:

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.