Well i had installed a theme that said it was updated to rc33. i installed it and it ended up with my g1 staying stuck in the boot up, i reinstalled the theme it still didnt work. Then i just downloaded another theme and installed it so it ended up working though im missing the browser?
any help?
Fixed.
You can close the thread
Related
Ok, i installed the wm6.1 official update, everything worked perfectly. it installed. connected to my sim exc. when i was restoring my files from 6.0 i think i restored some registry files that 6.1 doesnt like. when i load past the att page the screen goes black. i can get to the tri-colored page. is thier anything i can do?
Do another Rom update that will set it back to square one and do the restore again, this time missing the registry files that it doesn't like would be a good first step. I tried something simialr and found it a pain as well. Though I also downloaded the wrong update for my phone, needed the hutch3 version so had to do it all again. Should have just left well enough alone.
Okay, I'm a Noob! I recently flashed Cyanogen 7 to my captivate. Bad idea since it is still in development. So I decided to try MIUI. I downloaded it and installed through ROM Manager. Everything went well, pulled Titanium back in and restored all of my apps and data. Then did a Clockwork Mod Flash. Problems started when I re-booted the phone. After the AT&T screen I see a Cyanogen 7 logo, then it switches to MIUI. After that nothing works as I get pop ups stating some Android processes are unable to function. I rebooted into recovery and re-installed Cyanogen, which I'm really not fond of. Can't figure out what I did wrong here. Maybe I should download MIUI onto my SD card and install from recovery instead?
mdhorning said:
Okay, I'm a Noob! I recently flashed Cyanogen 7 to my captivate. Bad idea since it is still in development. So I decided to try MIUI. I downloaded it and installed through ROM Manager. Everything went well, pulled Titanium back in and restored all of my apps and data. Then did a Clockwork Mod Flash. Problems started when I re-booted the phone. After the AT&T screen I see a Cyanogen 7 logo, then it switches to MIUI. After that nothing works as I get pop ups stating some Android processes are unable to function. I rebooted into recovery and re-installed Cyanogen, which I'm really not fond of. Can't figure out what I did wrong here. Maybe I should download MIUI onto my SD card and install from recovery instead?
Click to expand...
Click to collapse
Please do your research before opening a new thread. How to flash another rom from cm is in the thread for cm.
Thread closed
Hi, all. I just installed webOS 3.0.4 and now I can no longer get to the Moboot bootloader for booting into CM7. I (perhaps foolishly) did the update via HP's official Update Manager instead of by Preware. Just posting here to give you guys a heads up if anyone else is running Android and is thinking about updating to 3.0.4.
This should be an easy fix, I'm going to just try and reinstall Moboot via novacom. I'm guessing Android is still there, but the HP update just changed the boot back to stock.
EDIT: Yup, reinstalling Moboot fixed the problem.
Similar issue
I have a similar issue, once I updated to 3.04, reinstalled moboot and CM7 now it just hangs at the CM7 loading screen and does nothing. I've downloaded all teh files 4 times, reinstalled after wiping everything clean, still not working.
Don't know if this will help resolve why. I just loaded moboot and cm7 on my 3.0.4 touchpad and it works great. Maybe you need to recover the webos original form, update tp 3.0.4, them do the dual boot. Dunno
edit oops, just saw the first post edit. LOL
You should always CMW backup before doing any updates.
3 0 4 Update Breaks Moboot
You need to run it after the first update, i think the update that breaks it is called librsvg or something similar. I had it aswell on a new install of Sabayon 7 gnome, but running the command mentioned above fixed it straight away.
Not sure if I'm in the right place, but I cant post under the specific rom thread (post count)
Anyways, I'm running a clean install of Jelly "Beans" Build 5. I updated busybox because it was requested by another program and now my phone wont get past the pink boot logo.
So I have two questions...
How can I fix this?
If it involves restoring/reflashing rom, is there any way to get a number from my recent text messages that didn't yet sync with my online google contacts?
Thanks!
+1
Had this exact problem, I'm on Synergy 118 and tried 6 different times to update busybox each time same problem hangs at bootscreen. Only thing I could do was restore and not update busybox. so far everything works as long as I don't update to the latest busybox, when an app tells me it's out of date I just ignore it. Would love a solution to this!
Just dirty flash your ROM and don't update your busy box this time
Sent from my SGS3 running Eclipse 2.1
that's what I ended up trying, and it resolved the problem.
Thanks!
Hello. I posted here long time ago about having a inverted touch after I had to flash my dl1010q due to some virus that installed apps faster than I could delete them.
After finding a supposedly correct firmware and flashing it, I got hit by the dreaded inverted touch.
After more reading here I figured out how to edit my sys prop to get the inverted touch fixed.
But I'm still having issues with "running out of memory" without having a bunch installed and "gps" not working anymore.
I ve tried several firmwares that were supposed be be stock but so far nothing worked.
If someone out there still has the original file, please let me know. Any other help is also appreciated.
Thank you all