So, I've been trying to get back onto my stock firmware backup after checking out cm10.1 and am absolutely stumped on how to get the backup to restore. So what I've done to get on CM10.1 is:
Rooted stock with locked (but unlockable) boot loader. Restored NFC function and restored unlockable status to yes.
Made a backup in CWM
Unlocked my bootloader.
Fasboot flashed cm10.1 kernel, flashed cm10.1 from recovery.
Had working CM10.1 but decided I wanted to go back.
Restoring the backup results in the phone not booting. LED flick red and it powers off. I put CM back on at this stage, got the kernel from the stock backup, flashed that and the restore still won't boot.
Fastboot is still accessible and I can easily get back to CM10.1 so at least that's something. I really want to restore that backup though dammit!
I am now back on the backup I had made of CM10 and all is working as it should. Is there any specific method to smoothly get back to my stock CWM backup?
I realise that I could allways just download a stock firmware and flash it with flash tool, but I don't want to go this path if the option to simply restore my backup is viable. (currently don't have broadband at home so have to go easy on the downloads).
I am sure I must be overlooking something but just can't figure it out, is there some specific method or order to do things I missed?
Related
I tried restoring from a nandroid backup I made and after the restore, I could only get as far as the i9000 boot screen. I went into recovery to try and flash a ROM, but CMW recovery could not mount my partitions (partitions got messed up by nandroid?) The only quick way I could think of was to use odin and refalsh and repartition.
I restored my nandroid from within CWM recovery. Is there something I am missing in the restore process? Obviously something went wrong.
asicman said:
I tried restoring from a nandroid backup I made and after the restore, I could only get as far as the i9000 boot screen. I went into recovery to try and flash a ROM, but CMW recovery could not mount my partitions (partitions got messed up by nandroid?) The only quick way I could think of was to use odin and refalsh and repartition.
I restored my nandroid from within CWM recovery. Is there something I am missing in the restore process? Obviously something went wrong.
Click to expand...
Click to collapse
Hey man, sounds like you tried to restore one system over another,
Forexample, stock over cm7? and that messes up the partitions as you see!
Try to install the rom you are trying to restore before you start restoring!
Should work then!
Hope this helps
I did indeed try to restore a ROM which was very different from the installed ROM. I will keep your suggestion in mind the next time I do a restore.
Just to confirm : yes, you need to flash the base ROM you're trying to restore.
I played with ICS over the weekend and got back by flashing a stock - well stock+ - JVZ and restoring nandroid.
Did the same thing, stupid as I am,
the big problem is that none of the computers I've tried with is detecting my phone right now.
I get in to CWM but and to download mode but that ain't helping me since i can't use Odin to flash back to stock rom.
Any ideas?
I need to a Nandroid Restore on my phone. It's currently running CM9RC2 with Semaphore ICS 1.3 and CWM6. The backup was taken from a Gingerbread 2.3.6 stock ROM (although I can't remember which exactly) with Semaphore 2.7.4 and CWM5
So what do I need to do to successfully restore without messing anything up? Do I need to reflash back to stock ROM, or can I just run the restore as it is and it'll put everything back to how it was?
bigdave196 said:
Do I need to reflash back to stock ROM, or can I just run the restore as it is and it'll put everything back to how it was?
Click to expand...
Click to collapse
look in My Guides and Manuals about nandroid
You can't use different CWM to restore your nand I would suggest Odin back to stock re-root and make sure you add the same CWM recovery so you can update to 2.3.6 then after boot go back in recovery wipe and all the usual and then restore your back up
Sent from my SGH-T989 using xda app-developers app
Hurray, managed to sort everything out and my phone is back to exactly how it was before I installed CM9.
Thanks for the help guys
Hey all, been cruising just fine on Hellybean with devil recovery. It started acting funky so I went to a backup back in August that was a fresh, perfect install. Well I forgot it was the next to last backup and not the latest backup. The first backup was an accident backup that never backed up correctly. Well after it not booting I tried the "3rd" backup thinking that was the correct one. That put me back to ICS. Well after I booted into ICS I went back to recovery but it was CWM recovery instead. So I determined the "2nd" backup was the right one after the former ones didn't either. Well unless my backups changed when It went from Devil recovery to CWM recovery then I have no clue what happened. I selected the "2nd backup" and I guess that was from a complete different backups from a different recovery.
Sorry if my post is confusing. Hard to explain all of it on text.
As of now the phone is sitting at the splash screen for whatever OS it has on it now. Want to say a year old or so. I can't get into the recovery by turning it off and holding the volume buttons while turning it on so I'm a little stuck.
Any advice to get back to my JB backup or did I lose any JB backup I had when devil got replaced with CWM?
blackinches said:
Hey all, been cruising just fine on Hellybean with devil recovery. It started acting funky so I went to a backup back in August that was a fresh, perfect install. Well I forgot it was the next to last backup and not the latest backup. The first backup was an accident backup that never backed up correctly. Well after it not booting I tried the "3rd" backup thinking that was the correct one. That put me back to ICS. Well after I booted into ICS I went back to recovery but it was CWM recovery instead. So I determined the "2nd" backup was the right one after the former ones didn't either. Well unless my backups changed when It went from Devil recovery to CWM recovery then I have no clue what happened. I selected the "2nd backup" and I guess that was from a complete different backups from a different recovery.
Sorry if my post is confusing. Hard to explain all of it on text.
As of now the phone is sitting at the splash screen for whatever OS it has on it now. Want to say a year old or so. I can't get into the recovery by turning it off and holding the volume buttons while turning it on so I'm a little stuck.
Any advice to get back to my JB backup or did I lose any JB backup I had when devil got replaced with CWM?
Click to expand...
Click to collapse
Since you have no idea what you've currently got running and you can't seem to get into recovery then my only suggestion is to get it into download mode. From there get yourself the KK4 one click and take it back to stock. Then flash back to helly bean. As far as your backups go if you're sure of which one is which at this point you should be able to restore from it. But you might just start from scratch and forego the potential issues again.
The backups should all be there though, unless your internal and/or external storage got wiped by accident at some point.
Let me start by saying that after the error, through the use of the power and volume down buttons (the timing was different, seemed a little slower, if that makes sense), I was able to get my phone to boot into TWRP and restore the nandroid I made just prior to the error, so I'm up and running fine. What I don't understand is 1.) Why it happened and 2.) How to restore my other nandroid.
After flashing xdabbeb's 26A Bootstack and his VS982.5 ROM and all was running well, I wanted to go back to my nandroid prior to flashing the VS982.5, which is simply the stock Verizon ROM on 25b. I made a backup of VS982.5, then went and restored my previous stock backup. After I restored my stock backup, I got the following error when I tried to boot, and then the phone would go black.
boot certification verify
--------------------------------
secure booting error!
cause: boot certification verify
Based on the other threads I have read regarding the error, it seems like I was very lucky to get back into recovery. Can anyone tell me why this happened so I understand what I did wrong and avoid it in the future and what I might be able to do to restore my previous backup should I want or need to go back to Stock?
I didn't think this was specific to xdabbeb's ROM so I put it under general help instead.
wrswldo said:
Let me start by saying that after the error, through the use of the power and volume down buttons (the timing was different, seemed a little slower, if that makes sense), I was able to get my phone to boot into TWRP and restore the nandroid I made just prior to the error, so I'm up and running fine. What I don't understand is 1.) Why it happened and 2.) How to restore my other nandroid.
After flashing xdabbeb's 26A Bootstack and his VS982.5 ROM and all was running well, I wanted to go back to my nandroid prior to flashing the VS982.5, which is simply the stock Verizon ROM on 25b. I made a backup of VS982.5, then went and restored my previous stock backup. After I restored my stock backup, I got the following error when I tried to boot, and then the phone would go black.
boot certification verify
--------------------------------
secure booting error!
cause: boot certification verify
Based on the other threads I have read regarding the error, it seems like I was very lucky to get back into recovery. Can anyone tell me why this happened so I understand what I did wrong and avoid it in the future and what I might be able to do to restore my previous backup should I want or need to go back to Stock?
I didn't think this was specific to xdabbeb's ROM so I put it under general help instead.
Click to expand...
Click to collapse
I believe it's because your 25b isn't bumped. Xdabbeb's newest ROM is bumped. You'll have to downgrade to non-bumped kernel to restore that backup.
Fixed it?
wrswldo said:
Let me start by saying that after the error, through the use of the power and volume down buttons (the timing was different, seemed a little slower, if that makes sense), I was able to get my phone to boot into TWRP and restore the nandroid I made just prior to the error, so I'm up and running fine. What I don't understand is 1.) Why it happened and 2.) How to restore my other nandroid.
After flashing xdabbeb's 26A Bootstack and his VS982.5 ROM and all was running well, I wanted to go back to my nandroid prior to flashing the VS982.5, which is simply the stock Verizon ROM on 25b. I made a backup of VS982.5, then went and restored my previous stock backup. After I restored my stock backup, I got the following error when I tried to boot, and then the phone would go black.
boot certification verify
--------------------------------
secure booting error!
cause: boot certification verify
Based on the other threads I have read regarding the error, it seems like I was very lucky to get back into recovery. Can anyone tell me why this happened so I understand what I did wrong and avoid it in the future and what I might be able to do to restore my previous backup should I want or need to go back to Stock?
I didn't think this was specific to xdabbeb's ROM so I put it under general help instead.
Click to expand...
Click to collapse
Were you able to fix this? I did a similar thing. I am stuck on the on the black screen and can't in recovery.
Thanks!
Hey guys, having some issues restoring a backup of a GPE ROM that I made with ROM Manager on a working device. It goes through the process of doing the restore and then boots to the google splash screen, but never goes past that point (waited 45 minutes twice).
The ROM is GPE 5.0.1 rooted. I'm using the lastest recovery from clockwork mod and have tried several times. Not finding anything on the web regarding this issue. Perhaps the backup is just borked?? Im (obviously) S-Off and unlocked. Not sure why im not able to restore to my prevous state. Works like a charm with cyanogenmod ROMS...
Any thoughts?
I want to help but I don't entirely get what you did.
so you made a backup and you can't restore it, right? I have some questions, if you were kind enough to answer them, I may be able to help you:
> What "ROM Manager" did you create your backup with?
> Is it an entire ROM backup, like the TWRP, CWM do it?
> What Android Version is the backup?
I am thinking that you might didn't backup the boot partition properly so you can't boot your phone. there would be a compatibility issue with your boot.img and the system and data partition. So you can boot but because of the compatibility issues you can't boot entirely and keep stuck in the bootloop. that's what I think what it is but I am not 100% sure so I asked you the questions above.
And it would be very helpful if you could make a photo of the backup restore screen (inside cwm/twrp .. with whatever of those you are trying to restore the backup)