Related
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.
Allright, so there I was, running a rather stable Comm Rom 2.0 Voodoo Rom with the ED10 Kernel/Radio, and then I saw the thread on the OMFGB GB release, that I, of course, just HAD to have...
So, my first mistake was being impatient and not being able to find any installation notes, and pretending that I knew what I was doing by installing the rom via CWM mod.
Here's the rub, for some reason, whenever I did the 3 finger salute, it would pull a RED CWM that went orange when I applied update.zip ... because if I tried to install rom from sd card with the initial CWM boot, it wouldn't install anything, it would just error out unless I applied update.zip. After selecting apply update from zip, it would boot the orange CWM and allow me to install whatever I wanted...
So after applying the OMFGB rom, it showed the Fascinate/ Cyanogenmod 7 bootscreen, then went to boot loop. I panicked, pulled the battery, then backed up everything to my computer, and formatted the sd card in FAT32 with Windows 7 64 bit...
Shortly thereafter, I was using ODIN and the original "return to stock" files, and ended up getting into the stock OS.
Now I never show 3G or even 1x, and never pull data at all... when I go to place calls, it says that verizon cannot authenticate my phone... when I activate, it reboots and says everything was successful, but was noticeably a faster process than standard activation. Upon reboot, nothing improves... the os is there, everything shows that everything is fine, yet I am still not able to place calls...
Here is where it gets weird... My wife called me today, and the call came through... I received text messages, but still couldn't make calls... My bill is zeroed out, I'm not locked out that I know of, and I just want my phone working again...
Running out of ideas. I have flashed ED01 DL01 and even reapplied the stock .PIT in odin... I am going to try heimdall while I wait for help from here, but any quick help would be GREATLY appreciated...
I believe the issue is you need to convert your system to mtd before flashing omfgb...some one correct me if I'm wrong though as I don't want to spread false info.
but Try installing jt's 0704 cm7 build following his instructions, then install his 0713 build (possible unnecessary step but it worked for me), then flash omfgb. You will most likely have to flash jt's fixed cwm to subsequently flash his cm7 as I had to since I was coming from a stock restore. And now I'm running a blazing fast omfgb...I was able to restore all my apps and data in half the time it took on com rom...good luck let me know how it goes
Sent from my SCH-I500 using XDA App
riceje7 said:
I believe the issue is you need to convert your system to mtd before flashing omfgb...some one correct me if I'm wrong though as I don't want to spread false info.
but Try installing jt's 0704 cm7 build following his instructions, then install his 0713 build (possible unnecessary step but it worked for me), then flash omfgb. You will most likely have to flash jt's fixed cwm to subsequently flash his cm7 as I had to since I was coming from a stock restore. And now I'm running a blazing fast omfgb...I was able to restore all my apps and data in half the time it took on com rom...good luck let me know how it goes
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I will definately take this into consideration, but first i want to confirm that my phone is in full working order...
I appreciate the quick response, and hope to get some more love from the community.
Sent from my Transformer TF101 using XDA Premium App
sounds like your modem may be messed up
this is what i would do:
1) Odin this it is an "Stock" ED01 DB/DO
http://www.multiupload.com/9JSTWA6Y6L
LET IT BOOT FULLY
2) flash the CWM in the OP of CM7
3) Do all Wipes then Flash CM7 0704
let boot fully
USE the Shutdown menu to get to orangeCWM
4) Do all Wipes then flash CM& 0713
let boot fully
USE the Shutdown menu to get to orangeCWM
5)Flash OMFGB
pull battery & 3 finger salute to redCWM
6) Do all Wipes then re-Flash CM7 0704
reboot and bingo you are at OMFGB
xwhofarted said:
sounds like your modem may be messed up
this is what i would do:
1) Odin this it is an "Stock" ED01 DB/DO
http://www.multiupload.com/9JSTWA6Y6L
LET IT BOOT FULLY
2) flash the CWM in the OP of CM7
3) Do all Wipes then Flash CM7 0704
let boot fully
USE the Shutdown menu to get to orangeCWM
4) Do all Wipes then flash CM& 0713
let boot fully
USE the Shutdown menu to get to orangeCWM
5)Flash OMFGB
pull battery & 3 finger salute to redCWM
6) Do all Wipes then re-Flash CM7 0704
reboot and bingo you are at OMFGB
Click to expand...
Click to collapse
Trying this in about 15 minutes, will report asap...
Again, thanks for help...
Sent from my Transformer TF101 using XDA Premium App
when you say OP of CM7 thread, which one, there seem to be many CM7 threads... link please?
martyr2k6 said:
when you say OP of CM7 thread, which one, there seem to be many CM7 threads... link please?
Click to expand...
Click to collapse
also, lets assume I am completely as stock as possible... how should I get CWM on, and which version please link...
Also it miht be worth mentioning, though I think I already did... but when I go to activate my pjone, it says its successful, but then I go to make a call and it say that verizon annot authenticate my phone...
Here's a confusing screenshot...
Sent from my Transformer TF101 using XDA Premium App
Alright the issue is resolved, my main concern was whether or not I could use my phone for phone calls... after finally mustering up the guts to call Verizon, it turned out that the main problem in which I was experiencing was due to some form of typical midnight updates that big red does... apparently, my phone, missed some form of update that ended up de-authorizing my phone, but Verizon was able to help out, even at this late hour.
On the good note, everything went through just fine as far as flashing cm7... I just seem a bit conflicted with which rom is best. I guess its just a matter of personal preference, really. So far I prefer jt's rom just fine, but I might be switching back and forth between jt's and omfgb...
Thanks again for all the help folks, I appreciate it more than you could know.
Sent from my Transformer TF101 using XDA Premium App
xwhofarted said:
sounds like your modem may be messed up
this is what i would do:
1) Odin this it is an "Stock" ED01 DB/DO
http://www.multiupload.com/9JSTWA6Y6L
LET IT BOOT FULLY
2) flash the CWM in the OP of CM7
3) Do all Wipes then Flash CM7 0704
let boot fully
USE the Shutdown menu to get to orangeCWM
4) Do all Wipes then flash CM& 0713
let boot fully
USE the Shutdown menu to get to orangeCWM
5)Flash OMFGB
pull battery & 3 finger salute to redCWM
6) Do all Wipes then re-Flash CM7 0704
reboot and bingo you are at OMFGB
Click to expand...
Click to collapse
Not sure that I totally understand as to why I need to flash cm7 0713, then omfgb, then reflash cm7 0704... seems a bit redundant.
If you could clarify this for me and what improvement this offers, I would appreciate it.
Sent from my Transformer TF101 using XDA Premium App
Because omfgb apparently doesn't convert to mtd but cyan does, so you have to flash cm first
Sent from my SCH-I500 using XDA App
riceje7 said:
I believe the issue is you need to convert your system to mtd before flashing omfgb...some one correct me if I'm wrong though as I don't want to spread false info.
but Try installing jt's 0704 cm7 build following his instructions, then install his 0713 build (possible unnecessary step but it worked for me), then flash omfgb. You will most likely have to flash jt's fixed cwm to subsequently flash his cm7 as I had to since I was coming from a stock restore. And now I'm running a blazing fast omfgb...I was able to restore all my apps and data in half the time it took on com rom...good luck let me know how it goes
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
yup, that was your mistake. prior to flashing omfgb, you need to be on jt's cm7.
I'm too lazy to read all the posts but try flashing cm7 via cwm4. then, Odin back to stock using the right files and configurations. there's a sticky in the development section.
I unlocked the bootloader and rooted it okay... then I flashed a ROM, that also worked fine. I tried to flash a kernel and now it just gets stuck on the HTC screen. I tried restoring my back up, still the same issue. Tried reflashing the ROM, same issue. Not sure how to get it back to normal at this point.
It sounds like the kernel you flashed is either a 2.3.3 kernel that doesn't work on 2.3.4, or it was a bad flash. You should be able to fix this by holding volume down when booting up (opens HBOOT) then choose Recovery and from the recovery you can then either enable USB Mass Storage device and transfer a stock kernel over USB to your SD card then flash the stock kernel, or if you already have a stock kernel on your SD card, you can just select it from the install from zip menu and flash.
This Kernel should work fine (it's stock with CIQ spyware removed):
http://forum.xda-developers.com/showthread.php?t=1224659
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
ROMs usually have kernels. You could just wipe Dalvick cache and cache and flash your original rom (which has it's original kernel). and that should work.
There's a sea of roms. You could try posting on a rom's thread whether a particular kernel is compatible. Just follow the spin of things. Saves from just going round in circles.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
Here's a scenario: If you installed a rooted stock 2.3.4 rom then decided to install Silverneedle kernel, your phone will get stuck in this boot-loop because the silverneedle kernel is not compatible with 2.3.4 yet. So by flashing a stock kernel over what is already on there, it should fix the problem. Before you flash the stock kernel clear cache and dalvik. After that flash the kernel and reboot the phone. Chances are it will boot normally. I doubt you will have to reflash a ROM to fix this.
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Coriolis3ffect said:
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Click to expand...
Click to collapse
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Take it you didn't do a nandroid before flashing?
Sent from my PG86100 using xda premium
Tried to get my nandroid and it still got stuck..
Perhaps I should've also mentioned that my bootloader still says S-ON and I unlocked it using the HTC unlock method.
sn0b0ard said:
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Not sure about any extra firmwares actually.... currently going to try flashing xhaus' ROM and hope that works...
Flashed the superwipe before flashing the ROM, then flashed the ROM... it went to the HTC screen for a second then just vibrated and then turned black.
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Coriolis3ffect said:
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Click to expand...
Click to collapse
Do you have it named exactly PG86IMG.ZIP?
Sent from my PG86100 using xda premium
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Which version of hboot do you have?
Sent from my PG86100 using xda premium
1.50.000 or whatever
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
jayharper08 said:
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
Click to expand...
Click to collapse
+1 on this. RUU method should be bullet proof
Coriolis3ffect said:
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Click to expand...
Click to collapse
It's in the post that xhausx made for the stock rooted 2.08.651.2 ROM.
URL: http://forum.xda-developers.com/showthread.php?t=1223979
List of new firmwares for the 2.08.651.2 update:
(If you do the RUU method, you should have all the firmwares installed automatically btw...)
Radio & PRI Updates Radio 0.97.10.0808 PRI 1.24_003
PG86IMG_radio_pri.zip (MD5: E28414AAC6F91CE9D7B3615B2999AD3A)
RPM Possible fix for Black SOD
PG86IMG_rpm.zip (MD5: DE69396C8922FAD3AC82E5F836EE95FB)
SBL Secure Bootloader?
PG86IMG_sbl.zip (MD5: 5604349AD611241CF1AC152FD3B0DE45)
TZ Trusted Zone - Not sure of it's purpose
PG86IMG_tz.zip (MD5: 75749FBCCE1331A5A85D2A154E15B276)
PG2F2_SPCUSTOM - No idea what it is
PG86IMG_pg2f2_spcustom.zip (MD5: 7A7DE8659A0771919A14B0C299CA18CC)
Click to expand...
Click to collapse
The link posted is for the GSM Evo 3D... will it work on CDMA?
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.
So I have been using Neo's AOSP Rage Rom since about 1.4, and haven't encountered any serious problems (besides some hiccups such as the Trebuchet FC problem in 1.7, although everyone had that). Now, after I have flashed 1.8, I am unable to turn on my Wifi. I checked my md5s, I did 3 clean flashes, and I also flashed the rom with and without the inverted gapps pack.
My Rezound is currently S-ON, and I have no plans to go S-OFF unless necessary.
I'm not sure if this is a kernel problem, or if it's the wifi module, or perhaps something else, but I figured I should ask here first to see if there were others with he same problem.
Most likely kernel, try flashing Snuzzo's kernel
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Most likely kernel, try flashing Snuzzo's kernel
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I've tried that and it didn't help. I tried both of his kernels without success. My problem may be hardware related though. I can't switch back to sense based from without bootlooping. Same thing with flashing ruu.
aftafoya said:
I've tried that and it didn't help. I tried both of his kernels without success. My problem may be hardware related though. I can't switch back to sense based from without bootlooping. Same thing with flashing ruu.
Click to expand...
Click to collapse
If your running an ruu and still boot looping, then something else is wrong. It's gotta be a hardware problem, time for an insurance return
Sent from my ADR6425LVW using xda app-developers app
Well... I figured out what I was doing wrong, which was that I forgot to re-flash the boot.img that came with the Neo's rom. I suppose I forgot to re-flash it because it never said you had to, but I remembered that the rom was intended for S-OFF, and I'm S-ON, so that never occurred to me.
So, yeah, it was basically the kernel.
After I did a clean wipe and flash of Rage again, and flashed the boot.img in the bootloader, everything worked.
Lucasonic said:
Well... I figured out what I was doing wrong, which was that I forgot to re-flash the boot.img that came with the Neo's rom. I suppose I forgot to re-flash it because it never said you had to, but I remembered that the rom was intended for S-OFF, and I'm S-ON, so that never occurred to me.
So, yeah, it was basically the kernel.
After I did a clean wipe and flash of Rage again, and flashed the boot.img in the bootloader, everything worked.
Click to expand...
Click to collapse
Glad to see it works. Yeah so go s off your phone! Lol its worth it
Sent from my ADR6425LVW using xda app-developers app
I've got the same issue. Except wifi, gps, and bluetooth won't turn on. Also, I keep getting the message that my SD card is damaged. I pulled the boot file from the ROM, zipped it, and named it PH89IMG.
So far, everything else seems to work, but this isn't really working for me. Any suggestions?
Are you on ICS firmware or GB firmware? If you are on GB still and trying to flash ICS rom, wifi and sdcard won't work until you flash the old firmware patch.
Sent from my Rezound using Tapatalk 2
Squirrel1620 said:
Glad to see it works. Yeah so go s off your phone! Lol its worth it
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I second that notion. I've been on 1.8 for a while and I feel like it's been the best version so far (I'm S-OFF). 1.9 is out now, so I'll be trying that later tonight.
Performing S-OFF isn't that bad. I thought it was fun - just follow the directions and you should be fine (like anything else).