I have gone from various roms/themes dozens of times and just restore my favorite nandroid image to get back to what I like. Today I am getting this message while trying to restore nandroid: Error while erasing boot image
I use times infinities CWR 3 and always use the same recovery as I made the nandroids out of. Thanks in advance for any help.
Were you trying to go from 2.3 AOSP (cm7/muiu/jts gb) to a froyo ROM or vice-versa?
No, I was staying with froyo. I have gone from Com Rom to EF with no problems. I test drove Powerwashed and tried to go back to my Com Rom backup but no go.
sfd0124 said:
No, I was staying with froyo. I have gone from Com Rom to EF with no problems. I test drove Powerwashed and tried to go back to my Com Rom backup but no go.
Click to expand...
Click to collapse
Did you odin a stock rom package before going back to com rom? Although I dont think its required but it might fix your issue.
odin a stock .tar file in PDA with atlas 2.2.pit
let it boot up
power off and odin cwm
reboot to cwm via three finger method
wipe data,cache,dalvik
install com rom.zip
reboot and let it boot up fully
reboot to cwm and select your restore file
Thanks for the reply. Tried it, still no. Can't figure out what is different from the last 5-6 times I restored.
Got my phone back to the way I like it. Tried to make a nandroid backup and get the message: Error while backing up boot image!
I use 3 different computers between home and work to configure my phone. Thats all I can come up. Why would that matter anyway?
Related
'm running stock Froyo on a T-mobile Vibrant. I tried to get Rom Manager to backup the current rom. When it boots into recovery and I select reinstall packages it fails on signature. Apparently this is a 2E/3E Recovery issue.
So I went ahead and ran the 3e_recovery installer
http://forum.xda-developers.com/showthread.php?t=833423
which says it succeeded. Now when I run backup the current rom, it boots to recovery, and reinstall packages no longer complains about signature. instead it just reboots back into recovery so quickly that I can't really read the 4 lines of messages, though I can just make out a "replacing stock .. " as one of the last lines.
Reboot system still does work, so I can get back into normal operation, but I'm stuck as far as gettting a backup.
Help!
Well things have changed a bit.
I went ahead and did the KB5 upgrade, which got me back to stock recovery. So now I'm back to the case where CWM will fail on signature.
How are other Vibrant users dealing with this?
- what color is it?(lol, thats funny. I werk in parts)
- is there an update zip? what happens if you flash that?
kmandel said:
'm running stock Froyo on a T-mobile Vibrant. I tried to get Rom Manager to backup the current rom. When it boots into recovery and I select reinstall packages it fails on signature. Apparently this is a 2E/3E Recovery issue.
So I went ahead and ran the 3e_recovery installer
http://forum.xda-developers.com/showthread.php?t=833423
which says it succeeded. Now when I run backup the current rom, it boots to recovery, and reinstall packages no longer complains about signature. instead it just reboots back into recovery so quickly that I can't really read the 4 lines of messages, though I can just make out a "replacing stock .. " as one of the last lines.
Reboot system still does work, so I can get back into normal operation, but I'm stuck as far as gettting a backup.
Help!
Click to expand...
Click to collapse
i have exactly the same issue...i tried everything posted here but not working...last chance is to odin back i guess
If I were you I would do a back up then> odin back to stock then> root then> download Rom manager Then> Flash a new custom Rom. The Stock TMO one is sucky and does not run as smooth as the custom ones. Then you will an awesome phone
why can't i flash rom's no more.
When i flash a new rom(froyo, toxic) i get :
formating update
formating system
formating data
deleting files
copying files
and then instalation complete en then it reboots and this is whithin a minute. And ofcourse the rom do not work correctly so i have to odin back to stock. I wipe and reset to factory, tryed other roms( zen, biwinning) same thing happens. Olso my nandroid backups will not work, they all hang at bali kernel screen(palmtree). So now i am stuck with stock waiting for a solution. thanks
After you ODIN to JFD... can you explain what steps you are taking?
The more detail, the better.
after i odin back to stock, i root the phone, install rom manager, flash clockworkmod recovery. If i do a nandroid restore i get samsung screen followed by bali screen with a female robot voice saying something about paritioning 2 min and counting then it hangs. I also do a wipe before the restore. If i flash a rom in rom manager or in recovery mode i only get wat i mention above, i do not get a loading bar. Thank you for the reply
Don't restore, your nandroid has voodoo enabled, likely causing issues.
Try this:
Odin to jfd (assuming you have no issues, if you do, try my )
download my option b update.zip (from noob guide) - this allows you to avoid ROM Manager/cwr.
Download a good ROM, I would suggest miui revamped or birgertime's cm7 build (my preference)
Download Bali for cm7/miui
Move all 3 to internal sd
Hold in both volumes + power (can be done with phone on after going to jfd and moving files to phone)
Release at vibrant screen
This is stock 2e recovery, reinstall packages (2x maybe)
Should be in cwr now
Flash ROM
Flash Bali
Reboot phone (don't do anything else)
After it boots, wait 10, reboot
Restore ONLY non-system apps, reboot
Enjoy bad ass phone.
Let me know...
Ok I will try this tomorrow, I will let know, thanks again.
For the roms you mention I do not need bootlaoders right.
Correct. That's about the most dangerous thing you can do also.
I flashed ss-6 miui. So far everything works, calling, sms/mms, even gps and wow this is a really nice rom. I am really happy now, stock is so boring and slow. But leaves me wondering why i could not flash froyo roms. Thanks and greetings from a happy island(aruba) i got a lot of custumizing to do so cheers
Glad you are up and running with my guide. You could repeat those steps with froyo roms, no problem
Sent using the XDA app.
I am new to modding my vibrant (phone is rooted but that's all) but looking to flash a new ROM. I dl'd rom manager and installed cwr. When I reboot into recovery mode via rommanager or manually doing it,I do not get the prompt to backup. Only options I get are to reboot system, reinstall packages, delete all user data, delete cache data, and format internal sd-card. Anyone know how to fix this? I just updated to 2.2 froyo UVKB5 kernel 2.6.32.9 if that helps.
looks like you have stock recovery.
try reinstall packages, might take a couple times..
or install CWM via replacing update.zip
What he said, yeah.
So just delete the current update.zip file on my phone and replace it with a new one? Any links to download the update.zip file?
Sometimes you have to Reinstall Packages twice for it to go from regular recovery to CWR. If you flash a custom ROM though, most have a custom recovery built in.
If you have to replace the update.zip (which I don't think that you do), this worked for me the first time I rooted.
http://forum.xda-developers.com/showthread.php?t=849028
How to Root.
I am rooted, but I want to back everything up so that way if I do not like the new custom rom I can go back. I tried reinstalling the update.zip file from the link but s till have the same issue. Any other solutions besides going back to stock and going from there? And if I did go back to stock, would I lose everything?
I backed up using Titanium Backup, is that the same as going into recovery mode and backing up?
Re-download recovery using ROM Manager, then repeat. Worked when I had a similar issue.
Tried that several times. I also reuploaded the update file and reinstalled the package several times. Still no luck so I think I might go back to stock using Odin.
Then DL Eugenes froyo don't brick ROM with the 2e recovery update in it, then re-install packages, maybe twice and you'll have the green recovery menu your seeking
Googled Eugene's DL and I do not feel to confident with it. Is it supposed to fix the issue with getting into recovery mode?
So I went back to stock last night using Odin, upgraded to 2.2, and rooted using Superoneclick. Phone's back up and running but faster than the first time I upgraded to 2.2. I still have the issue getting into the proper recover to install the zip file. I've read that deleting Slacker helped some people, assuming it freed up space on the System ROM. My system ROM was full until I started to delete some apps. I now have 20.7 MB free. Could not enough System ROM space be the issue?
I am now also getting a "Fail" attempt when I try and update su saying that it failed to find currently installed su binary. Any advice on fixing this?
TIA!!!
it would probably be easier to just odin back to stock jfd and then flash a deodexed kb5 build thats rooted with SU already in it from here in the forums.
http://forum.xda-developers.com/showthread.php?t=1036193&highlight=deodexed
If you flashed kb5 from kies or odin and don't want to reinstall the rom then you will need to flash a modified 3e recovery because you probably are not quite rooted and won't be able to use CWM until you flash the modified 3e recovery...
http://forum.xda-developers.com/showthread.php?t=833423
You might want to check out the AIO vibrant toolbox (pinned topic in the development thread) it will give you big easy buttons and instructions to flash back to jfd and root and flash a new rom if you need to... It comes with Odin so you can wander into the install folder and fire up Odin to flash the modified 3e recovery if you decide to go that route too.
If I flash a deodexed kb5 will i still be able to flash a custom rom?
I am currently trying to flash my vibrant back to stock 2.2. My latest attempt was done using the AIO tools. Every method I have tried has lead to the Vibrant boot screen appearing for a few seconds, and then rebooting. Any suggestions?
Have you tried Odin?
Sent from my SGH-T959 using XDA
whatever5 said:
Have you tried Odin?
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
Yes, I have tried Odin with and without AIO tools. In all of the threads I have looked at, the answer seems to be flash back to 2.2 stock, but that is what I am trying to do. Thanks.
Try to boot into recovery and factory reset and see if that breaks the bootloop. If not, see below.
*********
Do you have a nandroid backup of the 2.2 you were on an using? If so, I suggest Odin-ing to stock (2.1), then pull the CWR from my signature put it on your internal card and label it Update.zip. Boot into recovery and hit Reinstall Packages. It will cycle through and you'll have to hit it again. It will cycle through again and your stock (blue) recovery will go to CWR (green). From there you can restore your nandroid backup of the 2.2 you last made (or should have).
You can go to 2.1 using the toolbox, as it has the correct pit/tar files to do so.
Woodrube said:
Try to boot into recovery and factory reset and see if that breaks the bootloop. If not, see below.
*********
Do you have a nandroid backup of the 2.2 you were on an using? If so, I suggest Odin-ing to stock (2.1), then pull the CWR from my signature put it on your internal card and label it Update.zip. Boot into recovery and hit Reinstall Packages. It will cycle through and you'll have to hit it again. It will cycle through again and your stock (blue) recovery will go to CWR (green). From there you can restore your nandroid backup of the 2.2 you last made (or should have).
You can go to 2.1 using the toolbox, as it has the correct pit/tar files to do so.
Click to expand...
Click to collapse
I currently can not get into recovery mode. I am holding the power, vol+, and vol- buttons, inserting the battery and then releasing them when the vibrant screen appears. But it just continues to boot cycle.
I flashed the pit and tar that came with AIO tools. No go. Still just boot cycles. Sorry for being a pain.
I do have a backup, but I am not sure what I can do with right now.
Try turning the phone off, plug in USB hold just volume up and power on the phone..... that should put it into download where you can run Odin and flash back to stock
Sent from my touchpad using XDA
related problem (sort of)
Solved: problem solved. I reflashed CM7 over the bootlooping mess, and it took. Then I was unable to get AIO Vibrant Toolbox to recognize that debugging mode was on, even though it was. So I just copied the files over and went through a massive round of forcing the zip files on again and again. I now have Slim 3.5 on my phone, so I can start playing with it.
*****************************************
I'm an extreme noobie, trying to upgrade my T959 to ICS. I've picked Slim 3.5 (latest release version as of this week) as my first attempt (but really any simple but well-functioning ROM will do for me).
I've rolled back to Eclair (from the official Tmo Froyo upgrade way back when), rooted, and numerous times followed various directions to install the zip for Slim -- sometimes trying CM7 as an intermediate step. The CM7 install failed in the same way as the ICS, as described below.
I've done it with and without AIO Vibrant Toolbox. I've used ClockworkMod Recovery 2.5.1.2 to wipe the data, clear both cache partition and Dalvik cache, and format system. I've popped the zip file in various folders and at toplevel, both external and internal SD.
In all cases, it gets off to a good start, and then I'm left with endless bootlooping: Vibrant logo, Mod logo, a textblock of about 15 lines, repeat. I've always been successful after that in using Odin3 v1.81 to get back to Eclair.
I got sucked into a tech vortex until 4:30 am last night trying again and again, and I'm way way too old for that!
Any thoughts?
This is my first time posting.
I am a noob, but I am trying to get beyond that. I have flashed kernels and ROMS to my GT-I9100, with success. The other day, I was going to flash a new ROM, and I tried to make a Clockworkmod backup of my current ROM...while the phone was charging. Is this a major blunder?
The reason that I ask is that CWM crashed in the middle of the backup, and now I can't enter CWM recovery and the phone doesn't boot properly. I just get stuck in a bootloop. I can get into download mode. I used Pistachio's post about how to fix a soft-bricked GS2 to flash back to stock thru Odin. Then I used CF-ROOT to re-root the phone. After that, everything works fine, and I can get to Android recovery mode. Then when I try to flash a ROM, Titanium Backup must be restoring the previous version of ROM Manager, and I get stuck in the same bootloop when trying to get into CWM recovery.
Is Clockworkmod corrupted? Did the recovery partition get corrupted? Should I flash back to stock, delete ROM Manager, then re-install it? Should I bite the bullet and delete my Titanium Backup folder, then re-install everything from scratch? Should I flash back to stock with Pistachio's .PIT file and tick RE-PARTITION?
I looked for an answer specific to this problem, and cannot find the exact same scenario in any other threads. There are similar problems, but I think that I have a CWM app or recovery partition problem, or I may have a NAND rw corruption. I don't think that it is a NAND rw corruption though, because I can flash different kernels and ROMs.
I have been using Resurrection Remix versions 2.2, 2.4.1, and 2.5.3.
I have been using Siyah 3.3.2 kernel.
Please help, and excuse my noobness if I am beating a dead horse with this question.
Sounds like Rom Manager borked CWM/CWRecovery, which it seems to do on SGS2 quite a lot.
Most of the scenario you outlined in para.3 of your post (back to stock, delete ROM Manager) sounds like a good WTG, but do not reinstall it.
If you're going to use a kernel which has CWM/CWRecovery (like Siyah), do not use Rom Manager at all. Uninstall it & keep it that way. CWM/Recovery can do pretty much everything Rom Manager can, and you're playing with fire having both on the phone. Eventually Rom Manager will bork CWM again if you use it.
In the first instance, go back to stock, re-root your phone & reinstall the rom/kernel you're wanting to use. If Rom Manager is installed by default, uninstall it before you do anything else. With a bit of luck, you shouldn't have to do anything else (like messing around with PIT's which you also mentioned in para.3). If you batch restore your apps with TI, make sure you don't restore Rom Manager.
Thanks for the speedy reply.
I will try what you have suggested, but how do I flash the .zip file from my phone without ROM Manager? Do I have to do it through Odin?
Yep, that's right. Get an Odin flashable rom from Intratech's thread (search for it on here). If links in that thread don't work, search here or Samfirmware.
Edit - And once you've got your phone back up & running the way you want, use CWRecovery to do all your flashing.
My apologies, I should have been more specific. I want to flash the RR 2.5.3.zip. Should I still download it to the PC, then flash through Odin, or can I use Android recovery to do it through the phone?
OK. Let's rewind a bit.
What state is your phone in right now ?
I am flashed back to stock, and about to use CF-ROOT.
OK. Root the phone, CWM/Recovery will be installed by default. Once the phone is rooted, reboot into CWRecovery, flash your RR zip & you should be GTG. Just remove Rom Manager if it's installed as part of that process before you do anything else (including backing up). If you're going to restore a backup, again, uninstall Rom Manager immediately after you restore.
OK, after I flash CF-ROOT, I will re-install Titanium Backup, and delete ROM Manager to be safe before proceeding. Then I will flash the ROM.zip and test CW recovery and reboot again. I will reply after doing so.
Thanks
ARRRGH!
After flashing CF-ROOT I cannot get to the splash screen upon reboot. I made sure that I ticked USB debugging before flashing the kernel. I can still get into download mode and CWRecovery, so I flashed back to stock, and tried again to no avail. I tried flashing the RR 2.5.3.zip, in CWRecovery, and it flashed. I get to the splash screen but no further. I feel like a terrible noob now, because yesterday I had the phone flashed to stock and rooted no problem. Is there something that I am missing? I made sure that I used the proper CF-ROOT kernel.
So you're getting bootloop when you flash RR ? Have you tried booting into recovery & doing a wipe/factory reset ?
I believe that I am fixed.
I restored a Nandroid backup of my stock ICS from right after my original rooting, and the phone booted fine. I did a wipe/factory reset and wiped cache. Then I flashed RR 2.5.3. The phone rebooted fine again. I IMMEDIATELY uninstalled ROM Manager and made sure it was out of Titanium Backup as well. I have rebooted several times, normal, download, and CWRecovery, and everything works as it should. I think that I am getting over my noobness.
I WILL NEVER INSTALL ROM MANAGER AGAIN...DOWN WITH ROM MANAGER!!!!!!!!!!!!!! Except for the Little Alex icon, that's still pretty cool.
A thousand thanks for your help. At least I was on the right track when I first asked for help. I was pretty sure it was a problem with ROM Manager, because when it crashed, it started this whole mess. I'll be sure to press the THANKS button for your help, and I'm going to thank Pistachio for his thread as well.
Not n00bness, stuff happens sometimes ;-) You weren't the first person to get tripped up by Rom Manager (I did not long after I got my phone), and you won't be the last.
Yep you had a fair idea of what might have caused it, and your detailed OP certainly made it a lot easier to work out WTF was causing the problems.
No probs. Glad you got it sorted ;-)