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.
Related
I flashed the DoW rom/kernal using clockworkmod on my vibrant and it gets to the boot screen (the screen with tw in brackets and an atom cloud) and just hangs. Anyone know what's goin on?
rmp5s said:
I flashed the DoW rom/kernal using clockworkmod on my vibrant and it gets to the boot screen (the screen with tw in brackets and an atom cloud) and just hangs. Anyone know what's goin on?
Click to expand...
Click to collapse
As far as I know DoW is a kernal not a rom. Make sure it will work with whatever your current rom is. Working great flashed over nero5.
I would odin back to stock, flash custom froyo rom then kernal....
By chance did you have lag fix disabled?......works fine with nero 4.1 and 5 for me.....but I found nerov5 works great without it
Sent from my SGH-T959 using XDA App
K5C5S5 said:
I would odin back to stock, flash custom froyo rom then kernal....
Click to expand...
Click to collapse
+1
Also remember that not all phones will handle the oc'd kernels
if you can get into recovery, you can try flashing a different kernel or reflashing your rom.
I'm currently running Bionix oc/uv and love it.
I DID undo the lagfix before flashing this.
If I could get a link to the stock odin files to flash so I could give the amazing sounding DoW a shot, I'm sure I could get it working.
Im running DoW 1.3 on AxuraJL5, and it does the same thing. i often have to pull the battery for a successful reboot. its sucks, but ive learned to live with it
wrong section to post this in, not to be a drag but its just that these forums can get clogged up with stuff like this if we dont keep posts in order. Q&A or under the DoW thread would suffice.
funeralthirst said:
if you can get into recovery, you can try flashing a different kernel or reflashing your rom.
Click to expand...
Click to collapse
With all due respect, if I could get into recovery, I wouldn't be posting this...
I made a fresh Nandroid before trying this but I can't get to recovery or anything.
brandonkahn said:
wrong section to post this in, not to be a drag but its just that these forums can get clogged up with stuff like this if we dont keep posts in order. Q&A or under the DoW thread would suffice.
Click to expand...
Click to collapse
I understand. If a mod moves it, it's all good. Just looking for help...my phone is sitting stuck at the atomic bomb screen still. It's been 2 hrs...just lookin for a hand. :-D Thanks!
have you tried getting it into download mode? i know you said you cant get into recov. but download mode is different.
first, do you know how to get into download mode?
well in short if you dont, when ur phone hangs.. pull the battery. with the bat. out hook it up to ur comp with odin running... as ur holding down the vol. up and down buttons stick in the batt. then you will be in download mode. then flash back to JFD
Maybe im wrong but isn't the dow kernel for 2.2. Didn't he say he was on bionix and isn't that a 2.1?
Powered by Axura with a dash of Voodoo
you are correct, i missed that he stated he was using bionix. OP there is your problem, you flash a 2.2 kernel with a 2.1 rom. flash back to stock via my instructions and you willl be fine.
you will need this http://forum.xda-developers.com/showthread.php?t=734475
Glad we got that taken care of.before he hard bricked his phone.
Powered by Axura with a dash of Voodoo
GreggoryD502 said:
Glad we got that taken care of.before he hard bricked his phone.
Powered by Axura with a dash of Voodoo
Click to expand...
Click to collapse
lol...I did this with my wife's phone...no boot and no recovery is very disheartening to say the least. lol
So...I flash back to stock using the thread provided and then flash DoW?
rmp5s said:
lol...I did this with my wife's phone...no boot and no recovery is very disheartening to say the least. lol
So...I flash back to stock using the thread provided and then flash DoW?
Click to expand...
Click to collapse
after you flash back to stock you of course are going to want to root your phone again, then youre going to want to go to team whiskey and download Nero... a 2.2 rom that works with the kernel. then you will want to flash DoW. I would also consider downloading setcpu because that kernel will drain the heck out of your bat. make sure you dont set to boot with setcpu, and just use the conservative setting.
team whiskey http://teamwhiskey.com/DownVibrant.html
again make sure its a 2.2 rom.
DoW works with any Nero (2.2) Team Whiskey Rom. You have to disable Vodoo LF before flashing, otherwise you will get stuck in a boot loop. Make sure to let the Rom run for a few minutes after flashing before replacing the kernal. You can always pull a logcat to see what your phone is doing when it hangs.
brandonkahn said:
after you flash back to stock you of course are going to want to root your phone again, then youre going to want to go to team whiskey and download Nero... a 2.2 rom that works with the kernel. then you will want to flash DoW. I would also consider downloading setcpu because that kernel will drain the heck out of your bat. make sure you dont set to boot with setcpu, and just use the conservative setting.
team whiskey http://teamwhiskey.com/DownVibrant.html
again make sure its a 2.2 rom.
Click to expand...
Click to collapse
Very fist, I wanna say thanks a million to all the replies and help. :-D
Ok...now...to set the record straight, my phone just tries to boot to the DoW and does nothing after. It just hangs.
Yes. I was running a 2.1 rom (Bionix) with a 1.2ghz oc, the uv kernal and the voodoo lagfix (which WAS DISABLED before flashing) but I thought I did everything right. If I had known that switching from a 2.1 rom to a 2.2 rom would have been this much more involved than I thought, I might have reconsidered...lol
I did a Nandroid backup using clockworkmod prior to doing anything else. I got to the red recovery (not 100% sure how I did it, to be honest) and tried to flash my backup and it didn't work.
I'm going to try the previous post about flashing back to stock, then doing the DoW flash but that's kind of a last resort. I'd like to not wipe my data, nandroid, etc before flashing but it's kinda whatever at this point since my phone doesn't work at all right now...lol
Thanks once again all of you!!! This is what makes Android what it is.
OK, so just yesterday, I realized that for some reason, I cannot play any videos on my Vibrant. This includes both videos I have put on my phone as well as those I have taken with my camera.
I am running Bionix 1.3 ROM. I searched but didn't find anything. I have not had this issue before. Any help is appreciated.
Reflash,I suggest odin to stock and reflash or try just flashing the new vrs of the overstock kernal.
Carl
carlcj5 said:
Reflash,I suggest odin to stock and reflash or try just flashing the new vrs of the overstock kernal.
Carl
Click to expand...
Click to collapse
Agree flash back to stock, then reflash best way
Thanks
OK. I've never used Odin before. To be honest, I'm a bit intimidated. Would you suggest using that AIO Vibrant Toolbox to do it?
cccheel said:
OK. I've never used Odin before. To be honest, I'm a bit intimidated. Would you suggest using that AIO Vibrant Toolbox to do it?
Click to expand...
Click to collapse
toolbox is very simple and straight forward
cccheel said:
OK. I've never used Odin before. To be honest, I'm a bit intimidated. Would you suggest using that AIO Vibrant Toolbox to do it?
Click to expand...
Click to collapse
Don't be afraid of Odin....
true: you can screw up if you use the wrong files or disconnect before it finishes...but if used correctly Odin can be your Vibrant's best friend...
EDIT: I've been having that same problem since KB1.....might be a DRM issue pointed out by Br1ck'd in my thread here:
http://forum.xda-developers.com/showthread.php?t=961841
Yea, but the thing is, it's not just DRM files - it's any video file.
Fixed
Just rebooted, and it seems to be fixed...hm... Thanks anyways, guys.
cccheel said:
Just rebooted, and it seems to be fixed...hm... Thanks anyways, guys.
Click to expand...
Click to collapse
but it comes back after some time. yes when you do a reboot it goes away but i after some time it comes back then you have to do reboot again i don't want to do that. why does it keep on doing it in first place. any ideas?
Try a 2.2.1 rom
Sent from my T959 using XDA App
This happens no matter what if you haven't rebooted in a while. My buddy on his completely stock KA6 was complaining about it all the time, just reboot at least once a day and you will be fine. No Rom will fix this issue that I am aware of but to be honest I have NEVER had this problem by always doing the before mentioned fix.
I feel like an ass. Normally things like this don't slip by me. I tested myself and it ran fine, but I never thought non voodoo users would have issues.
I am very, very sorry.
Anyway, enough grovelling from me.
To fix your phone and get back to some semblance of normal:
1. Download this EB01 Odin. This is the FULL enchilada. It is just like the DI01 all in one. http://www.multiupload.com/I9HBT8MXN1
Use this PIT: http://dl.dropbox.com/u/2056318/atlas_v2.2.pit
Odin file goes in pda section of Odin, and pit goes in pit section.
Flash and boot up once.
Turn off phone and go back to Download Mode.
Flash this recovery from Odin (credit jt1134)
http://db.tt/6dZUc7d
Reboot once.
Boot back to recovery and restore your nandroid, or flash a new rom.
Once again, very sorry for the whole mess.
Most of you probably know this already, but I'd like to add that you should flash 2.6, then flash 2.7.1 to get it to work properly. Do NOT flash the 2.7.1 update after the 2.7 update.
Edit: This relates to non-voodoo users. I'm not aware if voodoo users had problems or not
So I'm nonvoodoo. Is there anything I should worry about?
edit: I'm dumb. I read that wrong. but I don't think I am having problems. What is it I should look out for?
Sooo... I flashed 2.7 then 2.7.1 with CW3 (before I referred back to this thread) and I do not have a problem that I am aware of. Was the issue only with non-voodoo?
The only issue I had is when I tried to reflash the EB16 voodoo kernel again (after 2.7.1 flash)... it aborted. But, I rebooted and all is well.
Outside of that, the only other issue I've had, and this was with 2.6, 2.7 and now with 2.7.1, Launcher Pro fc's during or just after media scanning/start-up... but when it restarts after that, it works great.
def
I just flashed 2.7 and I don't have any problem, I'm nonvoodoo also, however I'll notify you if something happens
hrez2kx said:
Most of you probably know this already, but I'd like to add that you should flash 2.6, then flash 2.7.1 to get it to work properly. Do NOT flash the 2.7.1 update after the 2.7 update.
Click to expand...
Click to collapse
Not exactly correct, i flashed 2.7.1 over 2.7 and had no problem. Majority of the issues are with non voodoo and those on voodoo who disabled lagfix.
Sent from my SCH-I500 using XDA Premium App
What does the PIT do in Odin?
I too flashed 2.7.1 over 2.7 with no problems at all. Flashed every release as they became available without issue. Great job Adrynalane
Sent from my Super Clean 2.7.1 Froyo - Voodoo - Fascinate!
adrynalyne said:
I feel like an ass. Normally things like this don't slip by me. I tested myself and it ran fine, but I never thought non voodoo users would have issues.
I am very, very sorry.
Anyway, enough grovelling from me.
To fix your phone and get back to some semblance of normal:
1. Download this EB01 Odin. This is the FULL enchilada. It is just like the DI01 all in one. http://www.multiupload.com/I9HBT8MXN1
Use this PIT: http://dl.dropbox.com/u/2056318/atlas_v2.2.pit
Odin file goes in pda section of Odin, and pit goes in pit section.
Flash and boot up once.
Turn off phone and go back to Download Mode.
Flash this recovery from Odin (credit jt1134)
http://db.tt/6dZUc7d
Reboot once.
Boot back to recovery and restore your nandroid, or flash a new rom.
Once again, very sorry for the whole mess.
Click to expand...
Click to collapse
This instance of issues with superclean is really odd as with my experience with all your superclean releases not once did i encounter any major problem. Your prompt action to provide fixes and updates to those affected shows profesionalism. Thank you Sir.
Sent from my SCH-I500 using XDA Premium App
Don't sweat it adrynalyne
We all know the risks of dabbling in the custom rom scene
I for one was able to flash 2.7.1 without issue. Thanks for all your hard work & dedication.
I was on 2.5 voodoo upgraded to 2.6 with no problem and today just flashed to 2.7.1 only doing the wipe data, cache, dalvik about 3 times each with no problems. On Eb01 kernal as well.
Adryn you are awesome. I follow you on twitter and here and I love your Roms. You don't need to apologize for anything sometimes bad things just happen. Keep up the awesome work.
Being a parent myself I know its hard taking care of kids and being able to dev. I hope your daughter is doing ok and note good things come to those who wait
Sent from my awesome Super Fc 2.7.1 VoODoO Fascinate
[/QUOTE]
I am very, very sorry.
Anyway, enough grovelling from me.
[/QUOTE]
I don't think you have any reason to grovel. Mistakes can happen, and anyone doing this knows the risks. Family and personal life always take priority. I've been flashing your roms since m2d2 for the i910, it would take a lot to make me lose faith in your work. Thank you for all of your hard work, you are truly a gentleman and a scholor. And now I'm done cluttering your thread :-D
Samsung Fascinate
Frankenclean 2.7 Voodoo
Honeycomb Theme
Sent from XDA Premium App
Adryn, not only are you one hell of an asset to the Fascinate community, you are one CLASS ACT!
Sent from my SCH-I500 using XDA App
Thank you adrynalyne
Trust me adrynalyne, you have nothing to worry about. I have had 4 phones (all Android). I have used your roms for all the phones. you develop great roms and explain in layman's term. I can't thank you enough. Looking forward to your future projects.
+1 ....don't sweat it at all.
Adrynalyne, you have put a TON of time and effort into all this stuff, and I am nothing but grateful. Without your work, my wife's fascinate would be...well, less than desirable. With it, I have to question my decision to go with the Droid Inc!
Hey, we take risks using ROMS, and that's just how it goes sometimes. But the reward far outweighs the risk!
Thanks again for all your hard work, and for helping out this community. I think I can speak for the collective (dare I?) when I say that.
Pathfinder81 said:
Trust me adrynalyne, you have nothing to worry about. I have had 4 phones (all Android). I have used your roms for all the phones. you develop great roms and explain in layman's term. I can't thank you enough. Looking forward to your future projects.
Click to expand...
Click to collapse
Adrynalyne Thank you for all your hard work. I didn't have any issues and have had very little with all of your Roms. Don't be so hard on yourself **** happens
Grateful to have such great Dev as yourself
Theres another way of restoring instead of doing full odin. Just boot into recovery. Plug the phone to computer and start adb.
use this command:
adb push "name of rom" /sdcard
after its done. Just go back and flash the working rom from recovery. Much safer and easier than using ODIN. Anyway.. I have been using android phones for a long time and stuff like this happens ..
I have SC 2.7 Voodoo. All rights. All works fine.
Just a one, is a gps fix, like Vanila. Gps bad works. And more localizations for the other countries, like kaoss build and vanila too. We have only eng and spain. But this phone Have many people of world. WZ don't know this! But you can do it!
Big thanks to you for your works!
Sent from my fascinate using SC 2.7
khanable said:
Don't sweat it adrynalyne
We all know the risks of dabbling in the custom rom scene
I for one was able to flash 2.7.1 without issue. Thanks for all your hard work & dedication.
Click to expand...
Click to collapse
Ditto this! Thanks for all your hard work!!
Special Request
Can you put non-voodoo kernel in base ROM?
Hey, everyone. I've been having this problem a lot... when I was on CM7, about once a month everything would force close. First an app (xScope, Twicca, anything), then GApps, then my keyboard... the phone starts FCing everything within about an hour of being turned on. In the past, I've just fully wiped the phone... I'm on Pool Party now (the version before the newest one right now), and everything is FCing again. Is there a solution that isn't just "wipe everything?"
Did you make any drastic changes before it started force closing everything or has it been that way since you flashed the new ROM? Or was your ROM working fine in the past and it mystically started happening
Sent from my SCH-I500 using XDA App
This just mystically started today. It's been about a month and a half since the last time this happened, on CM7.
My phone got all screwed up one time when I installed either a bad gapps zip or the wrong one and I ended up having to wipe everything and start over to get out of that mess, although it's weird it randomly is happening to you.
I highly recommend the new ics roms
Sent from my SCH-I500 using XDA App
kadin.zimmerman said:
My phone got all screwed up one time when I installed either a bad gapps zip or the wrong one and I ended up having to wipe everything and start over to get out of that mess, although it's weird it randomly is happening to you.
I highly recommend the new ics roms
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
@OP... I installed TSM Pool Party, flashed gapps for CM7, [big mistake???] and then today everything FC. Couldn't load my browser, only ADWlauncher and perhaps a few other apps I tried worked.
I tried flashing the correct gapps, not sure if it fixed it, rebooting now. if not I will have to reflash tsm pool party.
@above poster, where is this new ICS fascinate rom? Is it stable?
GApps is GApps, man. Wondering if it's a sync issue...
mvmacd said:
@OP... I installed TSM Pool Party, flashed gapps for CM7, [big mistake???] and then today everything FC. Couldn't load my browser, only ADWlauncher and perhaps a few other apps I tried worked.
I tried flashing the correct gapps, not sure if it fixed it, rebooting now. if not I will have to reflash tsm pool party.
@above poster, where is this new ICS fascinate rom? Is it stable?
Click to expand...
Click to collapse
Yeah the ics ROM is very stable, I love it. Go to Google and type in "rootzwiki fascinate ics build 6" and you should find it on the rootzwiki website. Let me know if you end up using it and if you like it or even if you need help...I have encountered most problems people have had so I experienced them first hand lol
Sent from my SCH-I500 using XDA App
Gonna boot my phone up for the first time in 24 hours, maybe it's calmed down. I'd love to switch to ICS, but this isn't solving my "I don't want to wipe everything AGAIN" ordeal.
obsidianchao said:
Gonna boot my phone up for the first time in 24 hours, maybe it's calmed down. I'd love to switch to ICS, but this isn't solving my "I don't want to wipe everything AGAIN" ordeal.
Click to expand...
Click to collapse
Yeah I understand you on that...makes you sick to your stomach when you lose everything. Did you not have any backups of when your phone was in its working state? Backups are one of the most important things in my opinion. I learned the hard way
Sent from my SCH-I500 using XDA App
I haven't done a proper backup in a while. I should really start doing that, sigh.
obsidianchao said:
I haven't done a proper backup in a while. I should really start doing that, sigh.
Click to expand...
Click to collapse
boot into cwm and wipe cacnhe and dalvik. I normally do this once a week. Also if you have alot of apps downloaded to the internal memory this can happen. Check rootzwiki out for a thread about fixing the datadata force close issues.
http://rootzwiki.com/topic/5635-problems-with-datadata-causing-force-closes-for-google-apps/
Ahhh, thank you so much, this is perfect!
kadin.zimmerman said:
Yeah the ics ROM is very stable, I love it. Go to Google and type in "rootzwiki fascinate ics build 6" and you should find it on the rootzwiki website. Let me know if you end up using it and if you like it or even if you need help...I have encountered most problems people have had so I experienced them first hand lol
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Ah nice. I was hoping to see a stable ICS. So, it says there's no video hardware acceleration.. does that mean future updates will bring hardware acceleration for the fasciante? like h264 mkv's, or h264 mp4's, or even mpeg4 avi's? tsm/jt's rom doesn't have good video hardware support, MX video has to use SW almost all the time.
So I think I would like to check it out, but I wish I knew about it before I went through all the trouble last night to reflash and reinstall all my apps.. [was up till 3am working on it] lol
any major troubles with it? Also what CWM do I use? Perhaps the one on the CM7 fascinate wiki? [cwm4-bml-i500.tar] or the cwm 5.0.2.7 in vanilla gb?
Also do I need to odin it to anything? or can I go from what I've got now [tsm pool party]?
I've had no major troubles with the past 2 builds and definitely build 6 is the best. Not exactly sure what is meant by the hardware acceleration but everything about this ROM runs smooth. As for cwm version, just install any cwm and the ics ROM has its own that it will install. Once it installs it's own, it is recommended to not flash a new kernel once it does it's own because the one it puts on has stuff built in to make all the features work.
As for Odin, hmm....too be safe I would go back to stock and then throw a cwm kernel on. Then do a wipe data + cache and install build 5. Make sure it is running good then just clear cache and install build 6
Do a backup before you start all this just to be safe!!
Sent from my SCH-I500 using XDA App
kadin.zimmerman said:
As for Odin, hmm....too be safe I would go back to stock and then throw a cwm kernel on. Then do a wipe data + cache and install build 5. Make sure it is running good then just clear cache and install build 6
Do a backup before you start all this just to be safe!!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Ok so how come I should install build 5 first?
mvmacd said:
Ok so how come I should install build 5 first?
Click to expand...
Click to collapse
I'm not sure if you have to or not, probably don't actually I'm not sure why I said that lol...I guess in my situation I had troubles along the way so I started at build 3 and worked my way up.
just go straight to build 6 and in that case wipe data and cache. And I still would go to stock first because I read somewhere that it best to go from the bml based versions to mtd.
I would then update your radio to EH03 if it isn't already
Sent from my SCH-I500 using XDA App
kadin.zimmerman said:
I'm not sure if you have to or not, probably don't actually I'm not sure why I said that lol...I guess in my situation I had troubles along the way so I started at build 3 and worked my way up.
just go straight to build 6 and in that case wipe data and cache. And I still would go to stock first because I read somewhere that it best to go from the bml based versions to mtd.
I would then update your radio to EH03 if it isn't already
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
awesome... yes I was planning on Odin'ing again, because I've found it gives the rom you flash after it better chance of survival.
It is a inconvenience though because I have to boot up W7 [Dual boot Linux] every time I wanna Odin.. haha, same thing back when I used my ipod touch for iTunes.
So what radio does the ics build 6 have? can they not use the eh03 radio [I'm assuming is superior to whatever it has]? And I assume heimdall can flash the "modem.bin" radio that I untar from the "CI500_VZW_EH03_GB_CM.tar.md5" like so:
heimdall flash --modem modem.bin
right?
The ics builds don't have a specific radio, it doesnt mess with the radio you currently have, so whatever radio you have now is what you will have after the rom. I just didn't know what radio you had now, and the reason i recommend the EH03 is because it is the newest stock radio from verizon - meaning it is definitely reliable.
I'm not sure what you mean by untaring the .tar file. Odin uses the .tar file, so do not untar the file, just leave it the way it is. Unless you mean you can specifically take the radio.tar file out from the other tar file. I have the EH03_radio.tar file so if you wanted it i could upload it somewhere and give you the link. Odin back to any stock firmware, then load a cwm recovery as well as the EH03 radio.
EDIT: Here you go http://dl.dropbox.com/u/32493357/eh03_radio.tar.md5
kadin.zimmerman said:
The ics builds don't have a specific radio, it doesnt mess with the radio you currently have, so whatever radio you have now is what you will have after the rom. I just didn't know what radio you had now, and the reason i recommend the EH03 is because it is the newest stock radio from verizon - meaning it is definitely reliable.
I'm not sure what you mean by untaring the .tar file. Odin uses the .tar file, so do not untar the file, just leave it the way it is. Unless you mean you can specifically take the radio.tar file out from the other tar file. I have the EH03_radio.tar file so if you wanted it i could upload it somewhere and give you the link. Odin back to any stock firmware, then load a cwm recovery as well as the EH03 radio.
EDIT: Here you go http://dl.dropbox.com/u/32493357/eh03_radio.tar.md5
Click to expand...
Click to collapse
sorry... what I meant is, I know how to extract the EH03 modem.bin file out of the ".tar.md5" file for the stock Verizon eh03 firmware.
I know how to flash CWM with heimdall, but I guess I do not need to flash the radio [ right? ] because I just came from a fresh eh03, completely wiped, cache, dalvik, and..... urmm, it is showing the same animation I had back on "Eclipse ROM" for Droid X2... ew... For some reason I do not like that particular animation. I guess you can change the boot animation though?
mvmacd said:
sorry... what I meant is, I know how to extract the EH03 modem.bin file out of the ".tar.md5" file for the stock Verizon eh03 firmware.
I know how to flash CWM with heimdall, but I guess I do not need to flash the radio [ right? ] because I just came from a fresh eh03, completely wiped, cache, dalvik, and..... urmm, it is showing the same animation I had back on "Eclipse ROM" for Droid X2... ew... For some reason I do not like that particular animation. I guess you can change the boot animation though?
Click to expand...
Click to collapse
Use the program "odin" to flash all your .tar.md5 files. You don't extract those files, you leave them in the .tar format. I gave you the link to download specifically the eh03 radio, but if you have it already on your phone you dont need to worry about it. As for the boot animation, the ics rom will install its own boot animation so no worries there.
You know about odin right? It is definitely the easiest way to flash kernels, radios, and stock firmware.
I'm running the ths build 6.1, flashed gltich B5 for 6.1 and it booted up fine. Went to reboot and now the phone is stuck in the recovery, wiped, both caches, rebooted, still stuck. Restored back up, still just reboots to recovery. This has happened twice. Followed all the instructions. Why can't I flash this kernel.
Should I have flashed another older build of the kernel first then upgraded to the B5?
Can someone please maybe give me a different kernel to flash for the AOKP build as well. I've had poor luck with this rom and glitch and wouldn't mind running something else.
Thanks for the help
Same thing happened to me first time I flashed 6.5. I forgot to flash build 2 before 6.5, I blamed it on that. Since starting from scratch, adding Build 2 and Glitch my phone is running pretty darn good. Hope this helps.
See I flashed build 2 rather than build 1, due to better results, and it still did this. (Unless you're referring to Glitch Build 2 and not THS) ICS and Glitch v14 seem to be way more involved or complicated than GB and V13. I think I'm just not doing something incorrect.
I know there is other good kernels out there I'd rather run at the moment. I read that the Sephamore Kernel add some Voodoo Fix options like BLN and Voodoo Sound which is all I really care about.
Id rather have Glitch though
It sounds like you may have possibly 3-fingered into recovery at some point? That will make you bootloop. Also, you don't want to flash semaphore kernel or any other kernel/rom/whatever that is for a different device, that's pretty much asking for a brick. Glitch is the only custom kernel available on this device for ICS.
I think I honestly just did something out of order. I originally reflashed the nandroid because I lost 3G once the glitch was flashed. I'll have to give it another shot.
Sent from my SCH-I500 using xda premium
Keuka79 said:
I think I honestly just did something out of order. I originally reflashed the nandroid because I lost 3G once the glitch was flashed. I'll have to give it another shot.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
You flashed the wrong glitch... Read more flash less.
Sent from my SCH-I500 using xda premium
k_nivesout said:
It sounds like you may have possibly 3-fingered into recovery at some point? That will make you bootloop. Also, you don't want to flash semaphore kernel or any other kernel/rom/whatever that is for a different device, that's pretty much asking for a brick. Glitch is the only custom kernel available on this device for ICS.
Click to expand...
Click to collapse
I think that may have happened in my pocket. Is there any way out of that if I'm at work? I can't odin until I get home.
Sorry, I don't know of any way to get out of the bootloop short of odin (assuming there was a 3-finger). You'll just want to reflash the CWM4 fixed recovery in odin, then boot into that and try clearing cache/dalvik or just reflash your rom.
That was the only solution, thanks.
Tapatalking on my Fascinate