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!
Related
So I've never had problems backing up my Nexus one in the past using clockwork mod, but the past day, I've been trying to back it up so that I can try out Rodriguezstyle's new MIUI mod, but the backup keeps getting stuck on "Backing up sd-ext"
In particular, it says its getting stuck on "apparently this looks like a link?"
look down vertically for the thing I'm getting stuck on.
However, when I've pulled out my battery and reset into the recovery, I've found that the backup I was trying to make has actually been logged. I've been too scared to actually try to restore that backup to see if it's worked, because honestly I don't have any other recent backup and I don't want to mess anything up.
Any help would be appreciated! I might try to flash another recovery and backup that way...
I'm running RodriguezStyle's 2.9.2 MIUI ROM along with wildmonk's kernel and the most recent version of ClockworkMod Recovery if anybody's asking.
apparently I can't write out the exact file that it's stuck on...it thinks that it is a link...
ok here goes: "[email protected]@[email protected]"
Have you tried to fix permissions?
Yup I've tried that multiple times, rebooted, and it still didn't work.
You using cwm 3.0? It's known to cause problems like that. Happened to me before that's why I switch to amon ra
crazylilazn said:
So I've never had problems backing up my Nexus one in the past using clockwork mod, but the past day, I've been trying to back it up so that I can try out Rodriguezstyle's new MIUI mod, but the backup keeps getting stuck on "Backing up sd-ext"
In particular, it says its getting stuck on "apparently this looks like a link?"
look down vertically for the thing I'm getting stuck on.
However, when I've pulled out my battery and reset into the recovery, I've found that the backup I was trying to make has actually been logged. I've been too scared to actually try to restore that backup to see if it's worked, because honestly I don't have any other recent backup and I don't want to mess anything up.
Any help would be appreciated! I might try to flash another recovery and backup that way...
I'm running RodriguezStyle's 2.9.2 MIUI ROM along with wildmonk's kernel and the most recent version of ClockworkMod Recovery if anybody's asking.
Click to expand...
Click to collapse
Did you find any solution? I have the same issue after trying to restore from CWMrecovery. I have changed to Amon_RA so I will never come back to CWMr...
But I would like to recover to backup...
Clockwork recovery versions 3.x and higher have been known to mess up ext partitions. You may need to reformat your card and switch to an earlier version of Clockwork (or maybe try Amon Ra).
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?
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?
I tried to update my brothers phone to 4.4 from 12B because he kept saying that it would try to update but would fail which I didn't understand why because he only had root but that's not the problem. I installed TWRP and made a backup right away. I then installed the boot stack from this thread http://forum.xda-developers.com/showthread.php?t=2715408 then rebooted and was bootlooping. So, I put it in recovery mode and think I probably messed something up so I'll just restore the backup I made. I restore it and everything is looking good no errors or anything until I go to reboot it and it's still bootlooping. I'm stuck here because everything I've tried has failed.
I recommend following the restore to stock instructions (the tot method going to 11a then OTA to 12b) in the general section. Then use Cloudy's Malidus 2.0.2 files to update to 4.4.2.
Sent from my VS980 4G using Tapatalk
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)