I currently on a continuous bootloop with the new Comm 2.0.
Comm 2.0 with no Kernel, Comavolt, voodoo, and ED01.
I was using Comm 1.3. I tried to do recover from backup but that has failed. Before going to Comm 2.0, I want to CWM 3.0 Any suggestion is appreciated!
Edit: I odin Comm 1.3 using Landshark Odin but I still would appreciated if any help...will try again later
Did you back-up in CWM 3?
I am curious, before you went to COM 2.0, did you back-up in CWM 3x or CWM 2x?
I have been unable to do back-up using CWM 3x withput getting an error message (See my question later int the forum). I saw other posts from users that have the same problem. I have posted a Q here but have not yet received any replies.
Sorry I don't have an answer for your concern.
Related
For the past few weeks Ive been getting error message when using Clockwork Mod Rom Manager, under 'Download ROM" "Error Occured while processing the ROM List!" when trying to download a ROM under SonofSkywalker3. Im running Eugene's Ginger Clone now but also had that problem under NeroV3. I was running Macnut R14 a fews weeks ago and it worked fine. So I dont think its the ROM. Anyone else been having that problem? Is there a fix? See attached pic. Thanks.
Are you using voodoo?
Sent from my Nero powered Vibrant
I'm using Voodoo, and getting the same error
Are your trying to flash a rom or mod? If so, why don't your just put the .zip in the root of you're SD card to flash from there with cwr?
I've never used the option that you're trying to use.
Sent from my SGH-T959 using XDA App
Gopena said:
I'm using Voodoo, and getting the same error
Click to expand...
Click to collapse
If you have the recovery option in the power menu use that.
Sent from my Nero powered Vibrant
I think you guys are missing the point. Skywalker has a bunch of stuff to download thru rom manager. But its been showing an error for a few weeks. Not sure what's up with it. He uploaded it to rom manager so it could all be in one place.
Powered by Axura with a dash of Voodoo
GreggoryD502 said:
I think you guys are missing the point. Skywalker has a bunch of stuff to download thru rom manager. But its been showing an error for a few weeks. Not sure what's up with it. He uploaded it to rom manager so it could all be in one place.
Powered by Axura with a dash of Voodoo
Click to expand...
Click to collapse
I guess this question should be raised to the developer.
Not using Voodoo with Gingerclone but did use it with Nero. Anyways, Voodoo is disabled.
Im not flashing a ROM, but pieces from the ROM. I just want to get some of the goodies that Sonofskywalker has like Widgets and Wallpapers. Skywalker offers Ala Carte options instead of downloading an entire ROM.
I'm having the exact same problem. I been looking everwhere to fix this problem,but so far found nothing. I'm running Axura 2.2.5.7 rom. I'm not sure if its the roms. I odin back to stock and downloaded Skywalker Black hole 1.2 beta and some other goodies download went fine at frist. I trying going back in rom manager to get some more goodies and got an error "Error while processing rom list" I am a rom manager premuim user. Help Please!!!
I have the same problem. Trying to pull up any ROM list will result in the same error.
Sent from my SGH-T959 using XDA App
To Clarify, this feature worked in Nero Beta 3, and Nero V1.
Going to try reinstalling Rom Manager
Running Nero V3 with SBGB and Voodoo
Been having the same issue with Nero v3. And I can confirm that for the first several days of v3 it was working fine, and then it went kuput. I know I'm only adding to list of people looking for a fix, but at the very least want to let the OP know they're not alone with this issue. I don't believe it is ROM specific.
I do have a few things i've picked up over the past week, because i'm aware of the problem, but not how to fix it.
1. Some people have reported that by using odin to revert to stock they can then get rom manager working.
2. rom manager does successfully download my manifest, but it errors out while trying to process it.
3. it's nothing wrong with my manifest, because i have changed all the entries for the vibrant over to fascinate and the fascinate reads it fine
4. I have tried contacting koush, but haven't gotten any help.
This info leads me to two possible conclusions:
1. It's a problem with something in some custom roms (including Blackhole) that prevents rom manager from using something it needs to read the javascript on the vibrant
2. It's a problem with the rom manager software, either the version you have, or just on the vibrant in general.
some info that might help me fix this:
1. if anyone can get me a logcat of while the problem happens, i may be able to see what the issue is
2. if someone can tell me the rom manager version, it may be an older one and i can post the latest from the fascinate, which might help.
also i'm going to try to release a 2.0 beta based on JL5 later this week which may or may not fix these issue. and i'm going to continue to hope for help from koush.
Thanks SonofSkywalker. Really appreciate it. Love your work. I'm busy right now but hopefully I can find time to do a logcat in a couple days.
quest4fire said:
Thanks SonofSkywalker. Really appreciate it. Love your work. I'm busy right now but hopefully I can find time to do a logcat in a couple days.
Click to expand...
Click to collapse
Update: I read the logcat and it was showing my Vibrant as a Fascinate in CWM and it there was definitely an error with downloading. So I decided to restore my backups I had of Macnut R14 and Nero to see if I could download your ROM and was unable to, same error message. Then my phone got corrupted because of restoring the backups. I Odin back to stock 2.1 JFD and now I am able to download your ROM in CWM. So I dont think its a CWM issue. Unfortunately I lost my logcat because i had it inside my phone, was using a Logcat app from the market because I was having trouble getting my ADB server starting.
quest4fire said:
Update: I read the logcat and it was showing my Vibrant as a Fascinate in CWM and it there was definitely an error with downloading. So I decided to restore my backups I had of Macnut R14 and Nero to see if I could download your ROM and was unable to, same error message. Then my phone got corrupted because of restoring the backups. I Odin back to stock 2.1 JFD and now I am able to download your ROM in CWM. So I dont think its a CWM issue. Unfortunately I lost my logcat because i had it inside my phone, was using a Logcat app from the market because I was having trouble getting my ADB server starting.
Click to expand...
Click to collapse
sonofskywalker3 said:
I do have a few things i've picked up over the past week, because i'm aware of the problem, but not how to fix it.
1. Some people have reported that by using odin to revert to stock they can then get rom manager working.
2. rom manager does successfully download my manifest, but it errors out while trying to process it.
3. it's nothing wrong with my manifest, because i have changed all the entries for the vibrant over to fascinate and the fascinate reads it fine
4. I have tried contacting koush, but haven't gotten any help.
This info leads me to two possible conclusions:
1. It's a problem with something in some custom roms (including Blackhole) that prevents rom manager from using something it needs to read the javascript on the vibrant
2. It's a problem with the rom manager software, either the version you have, or just on the vibrant in general.
some info that might help me fix this:
1. if anyone can get me a logcat of while the problem happens, i may be able to see what the issue is
2. if someone can tell me the rom manager version, it may be an older one and i can post the latest from the fascinate, which might help.
also i'm going to try to release a 2.0 beta based on JL5 later this week which may or may not fix these issue. and i'm going to continue to hope for help from koush.
Click to expand...
Click to collapse
I'm using Rom Manager 3.0.0.7 and can't get into any roms. Not sure how to get a logcat, but once I figure it out, I will send it your way
I had the same issue and I was able to get Rom Manager working again by performing the following steps:
1) Clear the cache from the Rom Manager app (under Settings/Applications/Manage Applications)
2) From within Rom Manager run "Fix Permissions"
3) Reboot (which you're prompted to do when the "Fix Permissions" step is completed anyway)
This has worked for me twice.
Good Luck
What's up guys,
I looked everywhere and I couldn't find the exact answer I needed. I'm relatively new to the Android modding scene. My problem is that I am unsure of how to restore all my stuff (mainly all my apps, etc.) after flashing Eugene's Dead Horse ULF OC/UV kernel.
- I have flashed = Bionix V, KA7 modem, and the Dead Horse kernel (above)
I did a backup of Bionix V via Rom Manager and also backed up all my apps and data via Titanium Backup (I had a successful Ti backup right after I flashed Bionix). However, I didn't do a Nandroid backup of my stock 2.1 rom/things before Bionix. I JUST NEED HELP RESTORING ALL MY STUFF, PLEASE - still currently on the things flashed ABOVE. I backed up my internal SD on my computer and transferred it back after flashing Dead Horse kernel (flashing this DID wipe my internal SD).
Disabled Voodoo lagfix by creating "disable_lagfix" file in Voodoo folder (successful, followed all the correct procedures).
Now, the Android Market market is missing and I cannot access Rom Manager or Titanium backup. I have tried a Factory Reset (didn't work).
I can see all my backups in the Files app but do not know what to do!
Any help is appreciated! THANK YOU!
Try re-flashing the rom from CWR. You may just have had a bad download.
I would odin back to stock (jfd or the Alt Method, noob guide)
then flash something stable
Then move folders from pc to phone
Then restore like normal.
If the noob guide doesn't cover it, pm me
Hey, thanks for replying! I have been following your noob and downloaded everything you recommended for this process. However, while using Odin, it seems to have gotten stuck on the "All threads completed. (succeed 0 / failed 0)" part --> it's been almost 10 min and my Vibrant is still in Download mode.
What should I do?
I realized that Odin was not able to recognize my Vibrant. I have been searching for hours and cannot find a solution. I installed the Samsung drivers from their support page; are there different drivers for Odin?
Phone is NOT bricked. I can still get into Download mode and Recovery Mode (not stock)
Still on Bionix V and, again, no access to the Market or previous backups.
Thanks!
bfranksd said:
I realized that Odin was not able to recognize my Vibrant. I have been searching for hours and cannot find a solution. I installed the Samsung drivers from their support page; are there different drivers for Odin?
Phone is NOT bricked. I can still get into Download mode and Recovery Mode (not stock)
Still on Bionix V and, again, no access to the Market or previous backups.
Thanks!
Click to expand...
Click to collapse
Have you tried using the toolbox?
http://forum.xda-developers.com/showthread.php?t=954509
I just created a thread with the link to the drivers.. Called "drivers 32/64" if you want to search.
Once the drivers are installed odin should recognize it. If you were on some rom like cm7, you nee red the nexus s drivers.
THANK YOU! Everything helped and i figured out that I had to reinstall Samsung Kies. I appreciate all the help and suggestions, really.
Hi, all. Relative noob here. Fascinate, Stock ED04 OTA, Rooted, modified stock kernel to "stick" CWM, Bloat frozen using TB.
I want to take the next step of flashing a ROM, and am doing (I feel) due dilligence by reading everything possible in this forum. However, I think I'm starting to suffer from information overload, and confusion has set in.
I used Odin to flash CWM 3.0.2.8x.ti. Immediately after selecting backup and restore/backup, I get "Error while backing up boot image". I see a few posts with the same statement, but no resolution. Flashed back to CWM 2.5; and backup appears to complete successfully. However, the date of the backup is 2000-01-01; and this is consistent on repeated attempts. The time and date on my phone (when booted) is correct.
Am I missing something? Any help would be greatly appreciated.
dhartman977 said:
Hi, all. Relative noob here. Fascinate, Stock ED04 OTA, Rooted, modified stock kernel to "stick" CWM, Bloat frozen using TB.
I want to take the next step of flashing a ROM, and am doing (I feel) due dilligence by reading everything possible in this forum. However, I think I'm starting to suffer from information overload, and confusion has set in.
I used Odin to flash CWM 3.0.2.8x.ti. Immediately after selecting backup and restore/backup, I get "Error while backing up boot image". I see a few posts with the same statement, but no resolution. Flashed back to CWM 2.5; and backup appears to complete successfully. However, the date of the backup is 2000-01-01; and this is consistent on repeated attempts. The time and date on my phone (when booted) is correct.
Am I missing something? Any help would be greatly appreciated.
Click to expand...
Click to collapse
i have had the same thing happen every time i try and backup. I'm wondering if it has anything to do with the newer recovery b.c when i had 2.5 i had no issues with it. Anybody have an answer for this?
I was in the same boat as you: rooted and bloat frozen via TB since the first week, and just added the modified kernel with CWM 3 earlier this past week. Haven't had any problems with it. I used Heimdall to flash CWM and the kernel. Now I'm running Evil Fascination with the LG Alternate Launcher. Tried ComRom but didn't care for it, though the default wallpaper was very pretty.
Back to the point, after I flashed the kernel and CWM I restarted the phone, let it boot, then rebooted into recovery to backup, instead of unplugging it and immediately booting Recovery.
Honestly, you've made it this far, you want to get a new ROM, I say download one and follow the directions (read them three times top-to-bottom) before flashing, and you should be good.
Yeah - I think Evil is where I want to end up until CM7 is fully functional (just spent all morning reading the CM7 waiting room thread).
Unfortunately, I'm apprehensive about flashing a new ROM until I can get a good backup image. I'm not sure why I'm getting the erroneous date on the backups. I could certainly be doing something wrong; just not sure what (if anything).
Maybe I need to use a different CWM? 2.5.1 and 3.0.2.8. don't seem to have worked for me. Also, If I understand what eulipion2 said, I have already fully booted, then powered down and rebooted into CWM to do a backup. 3.0.2.8 fails and 2.5.1 gives be incorrect dates.
Going to do a few hours of reading on CWM, I guess!
I'm using the first kernel listed in this thread from times_infinity. I initially flashed ComRom, didn't like it, kept this recovery, and flashed EF. Works great so far.
Give the Nandroid a go with this Recovery and see if it works for you.
hey i figured out how to get the back up to work. you have to enable voodoo and then it will work
Hey guys. Thanks for the suggestions. Tried the CWM 3 link from above, still no dice. I suspect I may need to have a voodoo kernel installed to actually enable the voodoo and try the backup again. Makes sense I guess.
Getting frustrated.
Success! Flashed a voodoo kernel, and was able to get (what appears to be) a successful nandroid backup with 3.0.2.8 (red). Never did get 2.5.1 (yellow) working. Strange, but irrelevant. CM7 build 7 is looking like it's ready for a test drive.
Hey all. I am having trouble finding a Rom that will work on my Fascinate. I have ROM Manager and all the options I am getting from that are for builds that are different than mine. I tried several that were not labeled with a build and they all failed. I am using Clockwork Mod recovery. As it finishes the restart and begins applying the Rom it says that files failed to initialize. Operation aborted. Here are my phone details:
Firmware: 2.2.1 Froyo
Base band: S:i500.04 V.EC01
Kernel:2.6.32.9
Build:SCH-I500.ED03.
Any suggestions on a Rom and kernel (non-voodoo please) that will work with my phone? Am I doing something wrong? Do I need to flash via Odin to accomplish this? I would rather use Clockwork Mod if possible. Any help or suggestions will be greatly appreciated. Please excuse my ignorance as I am pretty new at this rooting stuff but learn a bit more everyday. Thanks again.
1. ROM manager is a big no-no for the fascinate.
2. You probably need to install a newer CWM via odin.
3. I am using ComRom2.1 w/ OTB 1/6 kernal (voodoo) but all you have to do is disable voodoo in the CWM settings.
4. Not sure why you don't want a voodoo kernal.
http://forum.xda-developers.com/showthread.php?t=1013312
Scroll though that thread. It has all the current roms and kernals and even CWM versions.
my friend just got a fascinate that's been flashed to cricket.
i've been searching for hours for him (yes, hourS, plural). he desperately wants it rooted
it's currently running 2.1 update1 EA28
after all the searching i've quickly learned that's insanely out-of-date.
so first things first.... all guides for rooting i've seen are DI09 and DL01 (before what he's got), and then there's some for froyo and GB.
first priority here would be root...
question 1:
Is there a one-click for 2.1.1 EA28? if yes, that link is very elusive and a little help would be wonderful.
question 2, if answer to 1 is no:
would simply flashing a rooted kernel with odin do the trick?
question 3, curious:
can GB be flashed to cricket as well? it's odd that the cricket dealer would give it to him on eclair. (simple yes or no will be fine)
question 4, this one i havent searched for, but is the EA28 modem from froyo? thought i saw a result w/ 'froyo' and DL30 something
honestly, i think flashing clockwork recovery using ODIN, booting into recovery, and then pushing the SU binaries from androidsu.com should work. remember if you reboot and don't reboot into recovery directly, the clockwork recovery will be overwritten.
you can grab the clockwork recovery from cyanogenmode website.
I'm pretty sure (might be wrong) that EA28 was just a small release to fix the emergency dialer from the previous update. Try super one click. With 2.1 you might even be able to get z4 root to work.
Sent from my SCH-I500 using XDA App