Related
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.
okay guys so i made this thread since it was getting too confusing and hard to track CLEAR INSTRUCTION on how to root from Rooted rom to cm7 or omfg roms!!
Basically this is what i did and STILL have iSSUE:
1.ODIN and atlas v.2.2pit (DL09 stock rom)
2. updated all OTA
3. pulled out battery and ODINed blue CM7 (latest one from jt's site)
4. did 3 method cmr and clear all data/wipe/davik
5. installed latest cm7 7/17
6. waited and seem like everything is perfect then it stops at cm7 logo with galaxy s sign and kept waiting and nothing HAPPENS anyone help???!!!
this is really pissing me off because I've been trying this several times now!!
ALSO for omfg i dont even know the instruction to get there anyone help it would be great!!!
Did you remember to flash gapps?
Sent from my SCH-I500 using XDA Premium App
izzjkjoe said:
okay guys so i made this thread since it was getting too confusing and hard to track CLEAR INSTRUCTION on how to root from Rooted rom to cm7 or omfg roms!!
Basically this is what i did and STILL have iSSUE:
1.ODIN and atlas v.2.2pit (DL09 stock rom)
2. updated all OTA
3. pulled out battery and ODINed blue CM7 (latest one from jt's site)
4. did 3 method cmr and clear all data/wipe/davik
5. installed latest cm7 7/17
6. waited and seem like everything is perfect then it stops at cm7 logo with galaxy s sign and kept waiting and nothing HAPPENS anyone help???!!!
this is really pissing me off because I've been trying this several times now!!
ALSO for omfg i dont even know the instruction to get there anyone help it would be great!!!
Click to expand...
Click to collapse
- In step 1 use vzw eb01 instead of dl09
- No need for step 2 just flash eb01 and reboot fully
-In step 3 pull batt and odin cwr 3-30 fix all (instead of jts blue one) and immediately do step 4...
-do step 4 the same as you did..wipe data/cache/delvik
-install cm7 build date 7/4 and reboot
That will get you running on cm7...from there you can install mtd kernel of choice (if you want something different then the one thats comes with, it) gapps, and/or the newest cm7 build..do not wipe here to go to the newest build but make sure you only use the recovery that came with cm7 by accessing it via the power button menu, or terminal emulator...reboot recovery...no three finger booting recovery from here out.the cm7 recovery will also be blue..you only odin the 3_30 fix all to get the cm7 build on your phone do after that first time seeing red recovery after you're on cm7 it will be blue from there on.
-odin desired radio.
Sent from my SCH-I500 using XDA App
well apparently, there seems to be no links to the earlier versions of cm7 and the only thing is the latest cm7 with blue recovery from jt's site can..... i really want to try CM7 geez im missing out...
You can just install the latest CM7 following the same steps the previous poster gave you. No need to install 7/4. Install 7/17 then 7/18 update.
wjsmaggle said:
You can just install the latest CM7 following the same steps the previous poster gave you. No need to install 7/4. Install 7/17 then 7/18 update.
Click to expand...
Click to collapse
Thanks for the info but that is the issue i'm having I'm currently in stock froyo then i ODINED cmr 4 (blue from jt site) then i installed the latest 7/17 and everything seems to be working then i'm left hanging on cm7/galaxy s logo forEVER!! and nothign happens...
AND i did wipe date/davik/cache... please anyone???
izzjkjoe said:
Thanks for the info but that is the issue i'm having I'm currently in stock froyo then i ODINED cmr 4 (blue from jt site) then i installed the latest 7/17 and everything seems to be working then i'm left hanging on cm7/galaxy s logo forEVER!! and nothign happens...
AND i did wipe date/davik/cache... please anyone???
Click to expand...
Click to collapse
My previous post says to try to flash it with cwr 3-30 fix all did you odin that recovery and try to flash cm7 from there?
Sent from my SCH-I500 using XDA App
well there was no link on jt's site for cmr 3 or cm7 7/4 your talking about
izzjkjoe said:
well there was no link on jt's site for cmr 3 or cm7 7/4 your talking about
Click to expand...
Click to collapse
The Latest build should still work just try flashing it with the 3-30 recovery
here is a link
http://forum.xda-developers.com/showthread.php?t=942021
Scroll down to the .tar file and download it..odin it and three finger boot into recovery wipe everything and flash the newest cm7 build and reboot...once on cm7 don't three finger boot anymore.
Sent from my SCH-I500 using XDA App
When you odin, did you tick the re-partition box? Also you need to use one of the tar balls in the sticky about moving from cm7 to another rom. I know you're not going from cm7 but the tar balls still apply to this situation.
Sent from my SCH-I500 using XDA Premium App
I also had problems installing cm7 at first so what I did was installed latest miui.us build first which gave me blue cwm and converted all my files. Then flashed cm7 with no probs. This worked for me.
Sent from my I500 using XDA App
well tell me the instructions not just say "install miui" obviously i dont know how to do give me the steps!
Sorry, I had stock 2.2 eb01 (edo3/4 should work) to start. Then I used odin and flashed cwm-all (2.x.x or something) / three button boot to get to recovery/ wipe data/cache/flash super user zip/reboot/power off and back to odin/flash cwm-all again/three button boot/wipe data/cache/dalvik/flash latest miui . At this point it should reboot (cyanogen logo) then back to recovery and automatically install/reboot recovery/flash cm7 11.1. But like I said this worked for me, for some reason miui installed perfect like any other rom and not cm7. Sorry if this doesn't help.
Sent from my SCH-I500 using XDA App
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.
It recognizes it as a I9100 and wont let me do anything through rom manager.
i would say dont use Rom manager on TP, as its not officially supported.....use CM way to install clockwork recovery using aceminstaller
but some people have used Galaxy Tab's recovery and it seems to work....
Even though it isn't officially supported yet, with CM9 alpha 9.0.6, Rom Manager will recognize it. So far I have used it to rename backups to something more descriptive.
Sent from my cm_tenderloin using Tapatalk
Rom manager will recognize clockwork but it wont let you flash anything because its not supported in this model.
The only way to flash is through acme(which I cant stand). I already did this but the flash didn't take I guess because its missing now so I am assuming I have to use acmeinstaller every time to boot clockwork because it isn't actually flashing it into memory.
or downgrade to cm7 before they made the phone recognized as a I9100 and flash.
Most people already did this but I picked up a 2nd touchpad today and skipped cm7 straight to cm9 which is incompatible with clockwork.
Anyone know how to change how the device is recognized to something compatible with rom manager? I really dont want to mess with acmeinstaller anymore.
MrWesson said:
Rom manager will recognize clockwork but it wont let you flash anything because its not supported in this model.
The only way to flash is through acme(which I cant stand). I already did this but the flash didn't take I guess because its missing now so I am assuming I have to use acmeinstaller every time to boot clockwork because it isn't actually flashing it into memory.
or downgrade to cm7 before they made the phone recognized as a I9100 and flash.
Most people already did this but I picked up a 2nd touchpad today and skipped cm7 straight to cm9 which is incompatible with clockwork.
Anyone know how to change how the device is recognized to something compatible with rom manager? I really dont want to mess with acmeinstaller anymore.
Click to expand...
Click to collapse
For CM9, I wiped everything and flashed CM9 Alpha 0 and CWM using acmeinstaller2 from the main thread in rootzwiki. Haven't had to use acme since. Alpha updates 0.5 and 0.6 both applied using CWM. Haven't had any issues. With alpha 0.6, Rom Manager will recognize it, just not supported yet. However it does work for backup management. FYI, the official CM9 build uses "cm_tenderloin" in build.prop, not I9100.
Sent from my cm_tenderloin using Tapatalk
Hi everyone,
I just installed Neutrino 2.9 following the main thread instructions and so replacing Clockworkmod Recovery with Romracer Recovery as suggested.
Everything is working fine except I lost most of the Rom Manager functionalities because it require Clockworkmod Recovery installed.
Now I was wondering if I can go back to Clockworkmod and keep Neutrino ROM installed.
Also, will the OTA Update have issues if it does not find Romracer?
Thanks and very good job to anyone is developing these custom ROMs.
Max
You should be able to install ROM Manager's recovery, then flash RomRacer's. That should trick ROM Manager into thinking its recovery is in place, thus giving you back its functionality.
Sent from my Motorola Atrix 4G using Tapatalk 2
MJPollard said:
You should be able to install ROM Manager's recovery, then flash RomRacer's. That should trick ROM Manager into thinking its recovery is in place, thus giving you back its functionality.
Sent from my Motorola Atrix 4G using Tapatalk 2
Click to expand...
Click to collapse
Thanks MJ
I actually did it and it worked, I flashed CWM Recovery and then reinstalled RomRacer's again using Rom Manager.
Now Rom Manager shows that I have CWM installed while I don't anymore but at least it released almost all functionalities (except update check).
Bye,
Max
well, I dont have any issues, I have CWM Touch, so I dont give a chainsaw why you have to get only RRRecovery
ovitz said:
....... I dont give a chainsaw why you have to get only RRRecovery
Click to expand...
Click to collapse
It is actually strongly suggested by installation guidelines.
Anyway I had to go back to stable CM7.2 because my Atrix started to freeze (or turn off) and to get it back on I have to try several time to remove battery and put it back while holding the button power on.
With CM7.2 it happens less frequently than with Neutrino, of course I can't really say that this is the reason but I need my phone and I had to do something.