'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
I got myself a bricked OV, was able to fastboot and flash new images.
Now it boots up directly to Android System Recovery, from where I got a copy of a stock nandroid backup.
When I first tried to restore, it said to go to adb and run nandroid-mobile.sh, couldn't figure out how to get it to work from within adb shell.
Then I formatted the SD card as FAT32, put the nandroid backup, back into it.
This time the restore worked. After select this directory, it goes
Restoring: ..............................................................
It's been about 10min and the dot just keeps moving. None of my other phones have taken this long.
I followed method 1 on this page to get new images flashed.
http://androidforums.com/optimus-v-...-optimus-v-rooting-roms-tutorials-thread.html
I tried flashing the stock ROM on the next post, which didn't do anything either. Kind of stuck on what I'm supposed to do at the moment.
Any suggestions?
Hrm I flashed CWM instead and ran the same nandroid backup.
It worked this time, but when I do a system reboot, it still just goes directly to recovery.
Well all I had to do was flash the Xionia Recovery from
http://forums.androidcentral.com/op...st-boot-loop-issues-caused-factory-reset.html
and it fixed itself at this point.
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 rooted my phone last night and installed Cyanogenmod 10. I had it working fine, but my contacts weren't loading. I tried to restore data from the recovery I had in CWM, but when I restarted my phone it's stuck at the splash screen now. When I try to boot into recovery, it goes directly into the samsung recovery instead of CWM.
I'm not really sure what I should try next, as I can't get into Cyanogenmod or CWM. Any ideas?
Use Odin and flash CWM recovery again. If necessary re-flash CM as well. Should work.
this is the i9300 forum
I have a rooted S5 G900T, with PhilzTouch CWM and a stock 5.0.1 rom. I decided to update to 5.1.1 yesterday. I couldn't do the OTA update, so I used Kies. The update worked, except the phone and mobile data wouldn't work. No problem, I thought--I made a nandroid backup before I did anything. I reflashed Philz Touch CWM using Odin, rebooted into recovery, and restored from my nandroid backup. Everything appeared to work successfully.
But now, it's just sitting on the white boot screen. I get the T-Mobile jingle boot sound, and then nothing.
Solutions?
Thanks
problem solved. Reflashed firmware.