Hey guys, so I haven't booted into WebOS since the day CM7 came out back in October.
I'm curious as to whether I need to take precautions with anything, Wifi, etc before doing so. Anyone?
You should be fine, I use both all the time... one OS doesn't affect the other. However, I don't know if you ever updated webOS to 3.0.4. It may do it automatically so if that happens you will lose moboot (and some patches). Just reinstall moboot only through ACMEinstaller if that happens.
Dont update WebOS and you'll be fine. If you do update I think you'll have to run ACMEinstaller again.
no probs here
I also use both (mainly cm7) and havent noticed any issues what so ever. Don't know about how updating web os will affect cm7 since I have only had cm7 since the latest web Os update. Works like a charm.
If you boot into webOS, it'll download the update. Then you can install it, then run acme installer to install moboot again. Works like a charm.
Sent from my Legendary 2.2 infused device.
I run both OS's everyday just about without issue. Like others have said, if you havn't updated WebOS to the latest version you may have to. Ensure that you remove any patches you have before you run the update and of course you will lose moboot.
Related
I can't seem to get Update All to work. I am rooted on cyanogen mod 7, running 2.3. When I click Update All most of the downloads/installs fail. and the eris is dog slow. Do I need to go back to updating one app at a time?
My Eris just hung then rebooted trying to use Update All. Oh well.
You don't say which ROM.
I had that problem with GSB, but I do not with CondemnedSoul's CM7 ROM. (Though, to be fair, GSB would eventually all update if I just kept doing it.)
Well here is the issue, I bought the HTC Thunderbolt awhile ago. I then rooted my phone but left the original ROM on it since the custom roms were not stable. I noticed verizon was pushing me some update and I just ignored them. I woke up today to see my phone rebooted with the screen on an exsclamation point. And then my Thunderbolt keeps rebooting itself now. I tried going into ROM Manager to download a Custom ROM but the phone just reboots before I can do it. I just installed Liquid Gingersense v1.6 rom with the MR2 OTA Radio which said it installed just fine after installing the Liquid Gingersense rom. I went through setting up the google account fine and after it booted to the main screen now my phone boots all over again, get stuck at htc screen for a bit then loads the phone fine then boots again. I am really not sure what the heck is going on. I am new to the MR2 OTA Radio since I cam from the Droid 1. So I hope it was not the install order I did it. I Have turned off the phone booted it with still same rebooting over and over issue. If anyone has idea's please let me know. Much appreciated. Thanks
I'm in the same boat. I have wiped the SD card and done a factory reset on the phone. It is no longer rooted, as I can't install and run apps requiring root permission. The update fails every time it tries to install, I also get the exclamation point android screen when the update tries to install. I'll take the update, I don't care. I just want a reliable phone again.
I'm seeing this issue come up a lot. Some of you folks seem pretty upset by it, and reasonably so. Search through the threads and you'll find you solution.
For those who are STILL running that antique and wildly obsolete ROM that the jcase rooting process leaves you with, I'd like to set a few facts before you. First of all, that ROM wasn't provided as a long-term daily driver. It's OLD and it's not very efficient with the battery. Second, simply because it's stock doesn't mean it's inherently stable. It's probably less stable than the custom ROMs out there. Third, the only ROMs really struggling with stability were the 2.01 RUU gingerbread builds. That build is obsolete, but not nearly as obsolete as the ROM that the rooting process leaves you with. The stability issues with the second OTA had nothing to do with the ROM, but rather, the radio that came with the RUU. In short, it's foolhardy to believe that custom ROMs are somehow inherently dangerous or unstable.
I'd like to suggest to whoever might be running the rooted ancient ROM the rooting process leaves you with to abandon it at your earliest convenience. Flash an MR2 radio, and if you like stock, use the stock rooted debloated ROM based on the 1.70 RUU. If you decide not to do this, and your phone auto-accepts the update, you'll probably lose everything on the phone trying to get it working again. Save yourself that hassle. Flashing ROMs isn't hard and people do it everyday.
Forgive me if missed this, but I'm finally getting mine from HP tomorrow, and I think I'll hold off on CM until some of the major bugs are worked out, but I still want to play with WebOS.
--
Sent from my Droid Bionic.
You can still install the cyanogen mod alpha with the update, it doesn't change anything as far as that goes. If you have the alpha installed already, you'll have to rerun the command to install it again, but it still works with the update.
You will have to install only moboot not everything.
Update first and then install CM7. I did this and can confirm that it works.
rootnik said:
Update first and then install CM7. I did this and can confirm that it works.
Click to expand...
Click to collapse
+1 ... Just did a co-workers TouchPad today and CM7 installed smoothly.
Side note: 3.0.4 is in fact really "snappy", I like the updated camera app and no lag on the stock kernal.
I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
richfreestone said:
I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
Click to expand...
Click to collapse
I've installed a couple of the nightlies and not had major issues. There were indeed bugs, which made me move on to other ROMs (among other reasons, including the fact that my old HD2 had CM7 and it got a bit old).
As far as my experience goes, the nightlies have been quite stable. As mentioned, there were bugs here and there, and a force close from time to time. But I didn't have the problem you've mentioned with hanging at install.
They did take a while to load the first time, longer than I remember was the case on my HD2. Did you wait long enough? Delvic/cache cleared?
EDIT: I also found a CM9 around New Years, but it wasn't as stable and had charging issues. But I think it's out and the waiting's over, really.
EDIT AGAIN: The other option would be to try out the official ICS release, which can be found at samfirmware.com. That's my plan for the weekend.
like the previous...Sounds like your flashing over existing roms without wiping everything first...From recovery mode after backing up, the best way I find is to wipe data/clear cache and wipe dalvic cache from advanced menu before flashing any roms...that way your starting with a clean slate and will be less conflictions from old to new.
for me CM7.1 not stable
I'm waiting a stable CM9 its promising
If you follow the instructions on how to install it, it's stable for everyone. I'm using it for many many months now, and it's stable.
If you're coming from other ROM's, make sure you do a FULL wipe, and flash the rom TWICE in a row, without rebooting recovery.
And yes, we're waiting for CM9. CM7 is not supported anymore for SGSII.
I cleared the data, the cache, went into advanced and cleared the dalvik cache.
Installed the nightly, which I thought was trange was only 100mb, normally ROM's are like 300mb.
I'll try flashing the ROM twice as TheSaw has said. However, after seeing that CM7 isn't supported, I may think twice, i'm just getting bored of the stock.
Might also be worth noting, i'm using [email protected] #k2-18 kernel.
Also, by the way Sean is here, did you know you've got a USA flag in your mini profile under your username? will the official release be a odin flash? or can I just use a .zip through CWM to flash it? and would I still be able to use the speedmod kernel with ICS?
Always working for me and thousands of others .
Usual story is wrong install .
jje
I managed to get this working, by installing the ROM once, and then installing it again straight after.
I was just wondering, is there a way to move the lock screen lock down to the bottom of the screen, i.e. above the unlock and camera buttons? and is there a way to change the clock?
I have a Motorola Atrix on Bell (Canada), and for the past few months it's been running perfectly on a ICS version of Paranoid Android with no issues. I recieved a 32gb SD card for xmas, and I was reinstalling the ROM to move it to internal storage so that I can use my SD Card for music. I decided that since I was reinstalling the ROM I may as well get a new one, so I got the Paranoid Android JB ROM. I installed it to internal storage, with the tweaked body option, and it worked fine. Then I used the option chooser and installed some gapps like the play store, maps, youtube, as well as nova launcher and adobe flash, then rebooted. I first noticed that the wi-fi isn't working. It gets stuck at 'turning on wifi'. Also, none of the gapps were installed, just the launcher. The main issue, is that every couple minutes the phone will shut off. It also takes much longer than usual at the M screen (30-60 sec). It seems to turn off whenever I press the power button to wake it, whenever I plug in or unplug the device, and occasionally just randomly when the device is in use.
The phone is semi-operational right now besides having no Play store and the very frequent shut offs. Any help would be appreciated. I've tried a few different JB ROMs and they all have the shutting off issue, but Paranoid Android seems to be the only one with the Options chooser not working correctly.
Flashed back to the CM7 ROM Neutrino 2.9 . Works perfectly. Still though, is there any reason the JB Roms won't work for me? I know I've tried one in the past and it worked fine, but didn't want to keep is since is was still in Alpha at the time.
bjgrenke said:
Flashed back to the CM7 ROM Neutrino 2.9 . Works perfectly. Still though, is there any reason the JB Roms won't work for me? I know I've tried one in the past and it worked fine, but didn't want to keep is since is was still in Alpha at the time.
Click to expand...
Click to collapse
All ICS/JB ROMs are in early beta still. They're stable, just lacking hardware acceleration.
Did you do proper wipes and format /system partition before installing? Did you re-downloading the ROM and installing again? Did you try CM10 build from EPinter's? Sounds like your using Aroma installer, try flashing normal zip files for gapps, never had issues.
A lot of people are running CM10 as daily without issues, so retrace your steps to see if you overlooked anything.
エイトリックス から 送ります