im getting a weird error everytime i reboot my phone....
its a weird little droid with question marks ablove his head and next to it it says.....KERNEL PANIC............if not that error i get.........POWER RESET or UNKNOWN UPLOAD MODE
WHAT HAPPENED TO MY AWSOME FASCINATE!?
This all started when i switched to Nameless V4......i have now switched the comm rom 2.1 and its still happening........so i went ahead and odined back to DL09 and OTA to ed04 and threw the EC09 modem in and still get eroors....could it be the new modem/radio?
I would re-odin but check off to repartition. If you still get a kernel panic then I'd guess hardware.
Dalamar1320 said:
I would re-odin but check off to repartition. If you still get a kernel panic then I'd guess hardware.
Click to expand...
Click to collapse
well I just noticed that i never enabled voodoo in recovery after i put a voodoo kernel on my phone so it never did the robot lady convert.....
so i did that and listened to the sexy voice...lol....and it seems to be fine now.....did five reboots and no issue so far.
Cool. However, I don't see how the voodoo conversion would fix the issue since the voodoo kernels can run without voodoo enabled. But for your sake I hope it corrected your issue.
Dalamar1320 said:
Cool. However, I don't see how the voodoo conversion would fix the issue since the voodoo kernels can run without voodoo enabled. But for your sake I hope it corrected your issue.
Click to expand...
Click to collapse
well it was all good but i just got the power reset or unknown upload mode error....FML
Dalamar1320 said:
Cool. However, I don't see how the voodoo conversion would fix the issue since the voodoo kernels can run without voodoo enabled. But for your sake I hope it corrected your issue.
Click to expand...
Click to collapse
The VooDoo conversion WOULD fix the issue, his EXT4 was not properly formatted. He still had existing data conflicting with the new ROM. Which is precisely why the RFS and EXT4 reformatting scripts have been released.
Vinnie981 said:
well it was all good but i just got the power reset or unknown upload mode error....FML
Click to expand...
Click to collapse
For ****s and giggles, go to http://forum.xda-developers.com/showthread.php?t=1090127. Try BOTH formatting scripts, flash ROM then kernel of your choice, and proceed as you normally would. Let me know if you still have issues.
Related
If I'm on eugenes ginger r2 with voodoo.... can I backup and flash to try nero v2 with voodoo and not disable?
I know what's safe, but I can't see where the problem would lie.
Also, check out Voodoo Toggle in the Market. Amazing app.
Well supercurio if I'm not mistaken mentioned that there its no need to disable it if you go from ext4 to ext4 supported kernel/rom combination. I might be wrong though. ODIN or alternative should always be ready.
Sent from my bionix powered Vibrant
I second that notion. I also read that you can go from one voodoo rom to another without disabling voodoo.
Cool. ended up disabling using that app just to be safe...and I didn't have the patience.
lqaddict said:
Well supercurio if I'm not mistaken mentioned that there its no need to disable it if you go from ext4 to ext4 supported kernel/rom combination. I might be wrong though. ODIN or alternative should always be ready.
Sent from my bionix powered Vibrant
Click to expand...
Click to collapse
That is exactly right.
Worst-Case scenerio, the new rom doesnt have voodoo and you forget to disable,.... you'll get stuck at the boot, and then you will just use ODIN which will overwrite voodoo right?
Seems like there is no disadvantage to voodoo if that's the case.
s15274n said:
Worst-Case scenerio, the new rom doesnt have voodoo and you forget to disable,.... you'll get stuck at the boot, and then you will just use ODIN which will overwrite voodoo right?
Seems like there is no disadvantage to voodoo if that's the case.
Click to expand...
Click to collapse
As long as you can reliably get into the download mode if need be.
Also if you brick with voodoo don't you have to odin eugenes froyo that doesn't brick then odin to jfd?
Nero2voodoo+jl5 modem
^ really? Seems like any ODIN would work since it overwrites the system.
s15274n said:
Worst-Case scenerio, the new rom doesnt have voodoo and you forget to disable,.... you'll get stuck at the boot, and then you will just use ODIN which will overwrite voodoo right?
Seems like there is no disadvantage to voodoo if that's the case.
Click to expand...
Click to collapse
Actually sometimes ODIN Cannot always fix an EXT4 messup like voodoo when trying to flash a new rom, so just letting you know, it's happened to me.
BTW, I just went from Nero V1 JL4+voodoo to NeroV2+voodoo w/o disabling voodoo the whole flash took a little less than 3 minutes, and there are no bricks on my table
lqaddict said:
BTW, I just went from Nero V1 JL4+voodoo to NeroV2+voodoo w/o disabling voodoo the whole flash took a little less than 3 minutes, and there are no bricks on my table
Click to expand...
Click to collapse
Thats because the newest version of nero is already written with voodoo. To those flashing other roms that are not written with the voodoo kernel and ext4 compatability, disable voodoo prior to flashing your new rom, or else be ready to spend some time with odin.
Ginger Clone's of the World Unite! Via the XDA App
So the current iterations of cwm seem to have trouble working reliably with the newer froyo ROMs, and koush's recovery (although seeming to work correctly) is quite broken. So......
please find below a new recovery package that should work for any ROM for the fascinate, mesmerize, or showcase.
This is a "red" cwm recovery, and it will work with both voodoo and non-voodoo installations.
cwm-recovery-ALL.zip can be flashed via any cwm recovery.
if you are using odin, then use the cwm-recovery-ALL odin (.tar) package.
updated 3/29 - thanks to GizmoDroid for help with fixing fix_permissions script and root permissions typo that screwed up nandroid restores
updated 3/30 - fixed 'umount' typo - actually *fixed* fix_permissions this time - fixed odin/heimdall recovery attachment
Thanks, I just installed it. I'd rather not have a broken clockwork mod.
thanks, will give this a try!
ok, so I flashed this in the old cwm and it does come up red, but also says CwM Voodoo Lagfix Recovery, is that right?
In what ways is the old cm broken with froyo? I haven't noticed any problems.
Thanks! Good to have a fully working recovery again.
renf said:
In what ways is the old cm broken with froyo? I haven't noticed any problems.
Click to expand...
Click to collapse
Yeah, I'd like to 2nd this question. I have DL30 and CW worked for me in setting that up. Granted, I haven't tried anything else after that, but I'd like to know too.
Well I've had weird things happen when flashing stuff (I was using the "new-cwm.zip") , seemed like data being written where it shouldn't be? Just flashing theme files or own stuff I want to add, and I've had the following stuff happen:
Nuked my radio, had an unknown baseband and calls would never work, fortunately Radio Odin fixed it.
Had some /data apps disappear. Had some /data/data disappear. On reboot had Setup Wizard pop-up, even though I still had my Google account registered.
Hoping this new clockwork is completely safe. I suspected that clockwork was responsible for my weird happenings, so data-wiped and haven't flashed anything, so far fine functioning.
Using this is it easy to flash back to a prior set up, for me it would be back to dj05 w superdark and voodoo5?
Ive been holding off on froyo bc I need wireless tether, preferably unreported tether. But I really want to play around and see what the fuss is about. Ive downloaded every dl30 rom, havent installed one fearing I cant go back easily
Sent from my SCH-I500 using XDA App
/data on the fascinate is on /dev/block/mmcblk0p1
koush's recovery mounts /data as mmcblk0p2 (THIS IS OUR /DATA/FOTA. THAT'S BAAADDD)
under most circumstances this does not matter , because recovery.rc mounts data CORRECTLY before cwm gets to it, but there are circumstances where /data can be unmounted and then remounted, in which case cwm is gonna mount mmcblk0p2. If things get written there, at best you've got a **** load of FC's to deal with. At worst, a dead radio.
I've pointed this out to koush before, but was met with a "half-response", and to date it not been addressed (except for the recoveries that I've posted)
installed. When I go to do a backup, it gives the messages below. Backup seems to run fine though
E: missing bitmap progress_empty (code -1)
E: missing bitmap progress_fill (code -1)
Click to expand...
Click to collapse
Thanks, jt.
Copied to sdcard, booted into recovery, ran the program, keep coming back to green, no red.
ETA: Interesting. If I go to recovery from ROM mgr and try to load from sdcard, it does nothing, but if (while in ROM Mgr) I load from SDcard, it works. Got the blue screen, ran update, red appeared.
I likewise get the error message mentioned previously, but got it at install. Backup seemed to ahve run fine.
Installed like a charm, thanks jt!
sent from my fascinating XDA App
jackmei2 said:
thanks, will give this a try!
ok, so I flashed this in the old cwm and it does come up red, but also says CwM Voodoo Lagfix Recovery, is that right?
Click to expand...
Click to collapse
Yes, that is correct. It says in the OP. But it may have been edited since the time you posted and my response, so I'll let it slide
thank you JT!!!!! I thought it was just me, Ive had to start over again with my data about 6 times now becuase of Clockwork either not restoring my backups or my phone freaking out once I restored the backup. Thanks again!!!
beenz said:
Yes, that is correct. It says in the OP. But it may have been edited since the time you posted and my response, so I'll let it slide
Click to expand...
Click to collapse
haha thanks... but he said it will be red and that it is not for voodoo, so that's what I wanted to double check since it does have the voodoo menus and all.
superchunkwii said:
Yeah, I'd like to 2nd this question. I have DL30 and CW worked for me in setting that up. Granted, I haven't tried anything else after that, but I'd like to know too.
Click to expand...
Click to collapse
Lets see:
Broken mass storage function.
Broken data mounting function.
Couldn't wipe properly because of the above.
adrynalyne said:
Lets see:
Broken mass storage function.
Broken data mounting function.
Couldn't wipe properly because of the above.
Click to expand...
Click to collapse
The couldn't wipe properly bit me once already. Glad to have a proper recovery.
Sent from my SCH-I500 using XDA App
Thanks very much for addressing this issue.
For a while, I felt like a fresh n00blet, wondering what I was doing wrong. I tried flashing versions of supposedly compatible cwm's in different ways, always coming to the mounting errors.
Other than the errors from the missing graphics, this one works error free.
Scared to mess with this since i haven't experienced any problems with my current cwm stuff from pre dl09... Might just go ahead and do this tomorrow. For some reason I feel more comfortable using the odin method, so I can do all this over my Super Clean 1.0 with Neon GT theme and not have to do any data wiping or anything first?
So this makes no sense and I think its a weird coincident but as soon as I flashed this my beta version of swype started the force close loop..
EDIT: so weird, I had to uninstall the installer and swype itself using titanium backup and then download the installer and install again (had to do it all twice). Seems to be working again now tho..
Superclean 0.7.. aka Froyo.. Thanks devs!
I have not seen this issue anywhere else yet, and Jamezelle has personally tried to help, however as it is still not fixed, I figured I would try to see if as a collective anyone has any thoughts. Here it is, folks. I recently flashed the MIUI ROM, by Jamezelle, awesome ROM, however just not for me yet. SO, I wanted to flash back to Nitroglycerine's EC01/ED01 ROM, which works alright. It flashes, runs, etc. However, the SECOND that I try to flash a custom kernel, IE JT's newest Voodoo kernels, Imnuts voodoo kernel, etc. I get a boot loop and the FC vibrations. Also, part of the MIUI boot animation will reappear on flash of a new kernel, the graphical text that says "Android". This is all extremely frustrating, anything other than a stock kernel seems to do this. I cannot figure it out. Oddly enough, flashing a custom kernel over SC 2.9.2 seems to work alright, but not on any other ROM. I would appreciate any ideas or suggestions, however please keep in mind, all of the very n00b stuff I most likely already have known or tried. Formatting dbdata/data/system/boot, things like this, I have done, and to no avail. My main goal? Is to end up on Nitroglycerine's ED01 ROM with JT's latest voodoo kernel, any ideas on how to fix the custom kernel boot loops/FC vibrations upon trying this?
The easiest way would be to odin with a PIT file to anything you want, odin to dl09 and follow adryn's guide to get to ed01
Sent from my SCH-I500 using XDA App
micellis said:
The easiest way would be to odin with a PIT file to anything you want, odin to dl09 and follow adryn's guide to get to ed01
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I should have mentioned that I have done that a million times, it does nothing. I still get the same results, the same problems. :-( And I guess no one is interested in this issue, or no one knows a fix. ****ty.
Dread This Day said:
I should have mentioned that I have done that a million times, it does nothing. I still get the same results, the same problems. :-( And I guess no one is interested in this issue, or no one knows a fix. ****ty.
Click to expand...
Click to collapse
Are you wiping before flashing the Custom ED01 rom? This happened to me as well...it worked when i didn't wipe before flashing it
pootoss said:
Are you wiping before flashing the Custom ED01 rom? This happened to me as well...it worked when i didn't wipe before flashing it
Click to expand...
Click to collapse
Oddly enough, I had tried it both ways, wiping AND not wiping, both with the same boot loop results. However, good news. I simply Odin'ed to DL09, and updated to ED01 as Adynalyne posted about, flashed my kernel of choice, then flashed Nitroglycerine's newest ED01 ROM, and it actually booted. My newest conclusion: The version of Nitro's ROM I was trying to flash was probably ****ed, along with dbdata needing to be wiped in ADB. Thanks for the reply though!
Dread This Day said:
Oddly enough, I had tried it both ways, wiping AND not wiping, both with the same boot loop results. However, good news. I simply Odin'ed to DL09, and updated to ED01 as Adynalyne posted about, flashed my kernel of choice, then flashed Nitroglycerine's newest ED01 ROM, and it actually booted. My newest conclusion: The version of Nitro's ROM I was trying to flash was probably ****ed, along with dbdata needing to be wiped in ADB. Thanks for the reply though!
Click to expand...
Click to collapse
Glad to see you got it figured out Dread. I kept thinking the whole time that it was a bad/corrupted download. All in the past now though.
kidserious said:
Glad to see you got it figured out Dread. I kept thinking the whole time that it was a bad/corrupted download. All in the past now though.
Click to expand...
Click to collapse
Thanks bro, but oddly enough I do not think the download itself was corrupted. I read through a lot of Nitro's ED01 thread, and saw a lot of people were getting boot loops from that particular version, and I guess the fact that part of that MIUI boot animation was still there was throwing me in the wrong direction, you know? So I downloaded his newest ROM. But, finally, I'm on ED01, with the kernel I want, and everything is smoooooothe. Again, kidserious, thanks for the replies/help. Much appreciated.
Dread This Day said:
Thanks bro, but oddly enough I do not think the download itself was corrupted. I read through a lot of Nitro's ED01 thread, and saw a lot of people were getting boot loops from that particular version, and I guess the fact that part of that MIUI boot animation was still there was throwing me in the wrong direction, you know? So I downloaded his newest ROM. But, finally, I'm on ED01, with the kernel I want, and everything is smoooooothe. Again, kidserious, thanks for the replies/help. Much appreciated.
Click to expand...
Click to collapse
For sure. Hey man, if total functionality is not a must for you, you gotta try JT's CM7. I can't go back to any other rom. I even flashed his CM6 and still couldn't wait to get back to 7. Dude it's super snappy and silky smooth. IMO, the best the fascinate has ever seen (even in it's present condition). I can't wait to see when he squashes some of those bugs.
kidserious said:
For sure. Hey man, if total functionality is not a must for you, you gotta try JT's CM7. I can't go back to any other rom. I even flashed his CM6 and still couldn't wait to get back to 7. Dude it's super snappy and silky smooth. IMO, the best the fascinate has ever seen (even in it's present condition). I can't wait to see when he squashes some of those bugs.
Click to expand...
Click to collapse
Honestly, CM6 was amazing to me. The speed and stability was for the most part unrivaled...However, I just can't do without the MMS for a long period of time. :-( I hope he gets some of the bugs ironed out, I will FOR SURE switch then.
Hey has anyone else experience this. I'm running Voodoo. It doesn't matter which one, when ever i go into recovery it says voodoo disabled enabled on the next reboot. However after the next reboot it still says the same thing. Also conversion says no.
ghostt021 said:
Hey has anyone else experience this. I'm running Voodoo. It doesn't matter which one, when ever i go into recovery it says voodoo disabled enabled on the next reboot. However after the next reboot it still says the same thing. Also conversion says no.
Click to expand...
Click to collapse
so, your problem is that you can't get it to convert voodoo?
That may not be his problem, and it may not be a problem at all. My guess would be he is running CWM 2.5.1.x (CWM-recovery-all-3-30-fix) which erroneously showed voodoo was disabled and would be enabled on next reboot. CWM 3.0 corrected that display error.
I am running CWR 2.5. Is that the problem?
ghostt021 said:
I am running CWR 2.5. Is that the problem?
Click to expand...
Click to collapse
Its voodoo'd, just a bug in that version of cwm...update to 3 and it works fine
Sent from my SCH-I500 using XDA Premium App
^^ This. Exactly. Not a problem, just a bug. But CWM 3.0 is more functional anyway.
I read that CWM 3 was having problems writing back ups. Is this true, thats why I've struck with 2.5.1
Cwm3 is the way to go these days.
Sent from my SCH-I500 using XDA App
ive flashed back to Stock and then added different roms and everyone ive gone back to after stock, the settings of Anroid System in Settings is 0. the problem is that everytime I reboot the phone, all my settings aren't there anymore such as volume levels I previously set up or even the selection of keyboard - how can I fix this?
I've had this problem too.. a reboot of my phone on any custom rom always wipes my contact list, settings, messages, and apps but keeps my wallpaper and wifi and google info... I've always wondered why and if there's a way to fix it
Sent from my SCH-I500 using XDA App
what did you do to fix it?
jericho831 said:
what did you do to fix it?
Click to expand...
Click to collapse
that's what im hoping to find out
Sent from my SCH-I500 using XDA App
Corrupt DBdata... a nice odin and reformat should fix.. follow these instructions... http://forum.xda-developers.com/showthread.php?t=1124391 props to the author for the write up...
spyd3r05 said:
Corrupt DBdata... a nice odin and reformat should fix.. follow these instructions... http://forum.xda-developers.com/showthread.php?t=1124391 props to the author for the write up...
Click to expand...
Click to collapse
when I get to a computer will give this a try, thanks.. i've noticed an occasional "error mounting /data" when wiping in CWR but payed it no attention since everything works fine when it boots up on first install
edit: im not using any voodoo kernels or CWR so i don't think that ext4 formats gonna work for me.. however it seems my /data and /datadata corruption problems stem from a simple mistake: not booting into the stock rom once first before odin-ing CWR
Sent from my SCH-I500 using XDA App
Lol I'm going threw that crap now. Did u fix it?
Skip the ext4 part do all of the odin part of the tutorial
seemed to fix it for me.. time will tell if the fix sticks, thanks guys
edit: yeah I odined debloated/deodexed EB01, let it do its own data wipe on booting then powered off. I then odined CWR, booted straight into it, did the usual data/cache/dalvik wipe and flashed ComRom 2.0 and let it boot. I then booted into recovery and flashed the 2.1 patch right over it with no wipe. I let it boot up and presto!! no problems after 2 days, it even keeps data after reboots!! problem solved for me
tapatalked from my KangBanged Fascinate