Ive tried to look for the answer online but havent got a certain solution. Basically I have backed Up my Rom using Rom manager, and I put a differernt Rom on my Phone. MIUI.
Now Im trying to Put my Backup ROM back on, but I get the error.
Error While Flashing Boot, when am in Recovery Mode...
Whats the cause of this?? thanks
Does Rom Manager work on SGS2? I thought it was still experimental. I've read making backups using Rom Manager can bring some problems.
I think you won't be able to fix this, other than just installing a new rom.
I think you are right, I just backed up my phone using Recovery, And Flashed it again. using the same procedure..
but the backup made with Rom manager , didnt work..
Anyway to decompile the backup made with Rom manager to access my files ??
thanks
Related
I rooted my tab and installed rom manager to install clockwork mod. went to reboot into recovery and pphhhttt! it keeps cycling through the samsung icon. I know I had root with the su app installed I'm just not sure what I need to do to restore or how to get it off this boot loop could someone please help me?
automaddux said:
I rooted my tab and installed rom manager to install clockwork mod. went to reboot into recovery and pphhhttt! it keeps cycling through the samsung icon. I know I had root with the su app installed I'm just not sure what I need to do to restore or how to get it off this boot loop could someone please help me?
Click to expand...
Click to collapse
rom manager can sometimes create issues. im still not sure why people use it when you can easily flash cwm recovery through odin and it only takes about 2 seconds. im sure you didnt make a backup considering you were trying to flash recovery. the only thing you can do now is flash a stock rom via Odin now to get back up and running. for the future i would suggest you flash cwm through odin instead of trying to do it via rom manager.
thank you so much for responding. ok I think I might have odin installed on my pc. it says "odin in a nutshell". honestly I have no idea how to use it.
Ok guys heres the deal....i recently got a samsung fascinate from my sister cause I couldnt mod my inc any more. ok so....i got the phone rooted. i have su perm. i downloaded rom manager and installed it. now heres my problem. i can preform a backup no problem, but when i go to restore that backup it boots into clockwordmod and begins and then get an error about erasing boot img. or something like that. can tell exactly if i get some help from this. also cant install custom roms like i can with my incredible. i know it can be done cause i see roms and all for this phone. can someone please please help me.
Thats because cwm3 will not perform nandroid restores on stock roms. You need to flash cwm 2.5.1.x red recovery. Its the best recovery imo for any bml(touchwiz) rom. Go over to my guide in general section and you cand find cwm 2.5 in section 2&5. Oh and ditch rom manager...manually install cwm via odin!
If you're coming from an incredible, also keep in mind you don't have to be rooted to flash roms either, you just have to have a custom recovery. There aren't really any modifications like rooting procedures, S-OFF, etc, required for rom flashing, just odin a recovery and flash your selected rom.
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 ;-)
I'll try to keep this short:
I STUPIDLY....tried to use the new CM installation of the mod via my pc (their new method). I had made a backup of my original at&t firmware on my internal card...using my preferred method, TWRP.
Now, once the CM installation completed, it gave an error and I decided the heck with that, and I installed Rom Manager back on my phone and selected my original backup; and then....it booted in the CWM recovery and guess what....when I go to restore from sdcard, it CANNOT FIND THE BACKUP.!! I rebooted and looked in rom manager, and its there. Now at the top of the rom manger window, it it showing twrp as the recovery method, but when reboot, it goes only to CWM.....HELP!!!!!!!!!!!!!! I want to get my backup rom back on my device!!!
Forgot to mention: Once I got the error, it did boot into CM and now I'm stuck on CM. From there, I reinstalled Rom Manager and tried to restore from my backup.
chrisxpierce said:
I'll try to keep this short:
I STUPIDLY....tried to use the new CM installation of the mod via my pc (their new method). I had made a backup of my original at&t firmware on my internal card...using my preferred method, TWRP.
Now, once the CM installation completed, it gave an error and I decided the heck with that, and I installed Rom Manager back on my phone and selected my original backup; and then....it booted in the CWM recovery and guess what....when I go to restore from sdcard, it CANNOT FIND THE BACKUP.!! I rebooted and looked in rom manager, and its there. Now at the top of the rom manger window, it it showing twrp as the recovery method, but when reboot, it goes only to CWM.....HELP!!!!!!!!!!!!!! I want to get my backup rom back on my device!!!
Forgot to mention: Once I got the error, it did boot into CM and now I'm stuck on CM. From there, I reinstalled Rom Manager and tried to restore from my backup.
Click to expand...
Click to collapse
It sounds like you may have to use fastboot to flash twrp recovery. Or try to sideload it.
rdyfor_wteva said:
It sounds like you may have to use fastboot to flash twrp recovery. Or try to sideload it.
Click to expand...
Click to collapse
I was able to use ADB to flash it, and when I rebooted, TWRP was there, but...my backup did NOT appear in my backups. I have since flashed a different from; figuring by chance something might be cleared up, guess what.... When I open Rom Manager, my backup is there, (and twrp is indicated as recovery) it FRICKEN REBOOTS in CWM and from there, I can't see my backup; or anything in my storage!!! The only backup I see using CWM is one that i created using CWM and its NOT the one I want/NEED!
I'm thinking hard about trying to return it, again, to stock (unroot), but that's what started all my issues in the first place! LOL!
My problem unfortunately remains, in that I have a backup created in TWRP, that I can't restore to! Is it possible to use ADB to restore a nandroid back up:? I have the backup saved in my adb folder, it is however not a zip file, it saved as just a folder.
chrisxpierce said:
I was able to use ADB to flash it, and when I rebooted, TWRP was there, but...my backup did NOT appear in my backups. I have since flashed a different from; figuring by chance something might be cleared up, guess what.... When I open Rom Manager, my backup is there, (and twrp is indicated as recovery) it FRICKEN REBOOTS in CWM and from there, I can't see my backup; or anything in my storage!!! The only backup I see using CWM is one that i created using CWM and its NOT the one I want/NEED!
I'm thinking hard about trying to return it, again, to stock (unroot), but that's what started all my issues in the first place! LOL!
My problem unfortunately remains, in that I have a backup created in TWRP, that I can't restore to! Is it possible to use ADB to restore a nandroid back up:? I have the backup saved in my adb folder, it is however not a zip file, it saved as just a folder.
Click to expand...
Click to collapse
your problem is Rom Manager quit installing it.
use es file manager and move your backup to the new twrp folder
I'm guessing the old backup is in data/media/twrp/backup/ move it to data/media/0/twrp/backup
reboot to recovery (twrp) and restore and your all set
clsA said:
your problem is Rom Manager quit installing it.
use es file manager and move your backup to the new twrp folder
I'm guessing the old backup is in data/media/twrp/backup/ move it to data/media/0/twrp/backup
reboot to recovery (twrp) and restore and your all set
Click to expand...
Click to collapse
SPOT ON, THANK YOU VERY MUCH!!! One happy camper now thanks to you! !!!
chrisxpierce said:
SPOT ON, THANK YOU VERY MUCH!!! One happy camper now thanks to you! !!!
Click to expand...
Click to collapse
your welcome ...glad i could help
I have downloaded and tried to install several different ROMs on Vibrant T959 . I recently managed to get back to stock 2.1 ROM with ODIN and it works fine. As I understand it I need an older version of ClockworkMod so I have CWM 2.5.1.2 installed .
All attempts to flash a new ROM fail with "Error.....(Status 0) Installation aborted.
Maybe I am missing a step here? Do I need to go to 2.2 first?
Thanks.
Update.....
So I Found an older ROM I once installed it was "Bionics" looks like "Team Whiskey" which did install .
From there I was able to install ROM Manager and update Clockwork Recovery (Updated to 2.5.1.3) . When I tried to initiate a ROM flash from clockwork recovery The error was something like
This Package is for "vibrant.vibrantmtd.SGH-T959" devicethis is a "".
I also notice that google play simply calls this device "phone" , but there is no SIM installed and could the lack of SIM cause any of this?
I have old EFS backups of both locked and unlocked states but I thought this was just IMEI . The IMEI does appear to be intact.
I think the vibrant has an identity crisis
markosjal said:
Update.....
So I Found an older ROM I once installed it was "Bionics" looks like "Team Whiskey" which did install .
From there I was able to install ROM Manager and update Clockwork Recovery (Updated to 2.5.1.3) . When I tried to initiate a ROM flash from clockwork recovery The error was something like
This Package is for "vibrant.vibrantmtd.SGH-T959" devicethis is a "".
I also notice that google play simply calls this device "phone" , but there is no SIM installed and could the lack of SIM cause any of this?
I have old EFS backups of both locked and unlocked states but I thought this was just IMEI . The IMEI does appear to be intact.
I think the vibrant has an identity crisis
Click to expand...
Click to collapse
you might check the build.prop in your/system folder and see what it shows as the device name next to ro.product.model=
some roms change it to i9000 which would not pass the check some flashable zips have to make sure you are flashing them on the right phone.
or in this case it might even be blank or have some odd characters which would cause no name to display.
I would try re-flashing the rom which should replace the build.prop with a clean copy from that rom and then try to flash the new rom.
if that doesn't work it can be edited but I would only do that as a last resort.
on a side note error 0 means the wrong update script type was used (Amend or Edify)
Amend is the older one and Edify the newer.
you either needed a newer or older version of clockworkmod or a rom that used the other type of script.
I know you got that part fixed already by chance but I thought it might help to know what happened just in case it comes up again.
Actually i worked this out , although thanks for the reply. your reply prompted me to post my findings here to help the next poor sap with the same issue.
I installed a bunch of useless efs backup and restore apps which none would work with the efs backup I had previously made . I then installed the original galaxy s unlock app which did restore the efs backup.
Apparently the efs partition was buggered . I had several different backups and found the original locked efs then unlocked it.
I now have omni ROM 5.1.1 installed on my vibrant.
BTW if you install omni ROM 5.1.1 the recommended Google apps packages do not install, but I found another package that did install and also do not use the launcher in omni ROM (launcher 3 ?) It is buggy. The Google launcher was in the Google apps package I installed and it is far better than the omni ROM bundled launcher. I can not say that I like either of them however the seem so ordinary.