I have a rooted lg optimus v and recently install bobs homes cyogen mod 10 jellybean rom and the download went good and the ROMs very smooth later on I went to flash his jellybean gapps and the install went good when i rebooted the phone the screen said upgrading android optimizing apps 1 of 60 once that finished it went to the lock screen I unlocked the phone and went to my apps and there were no Google apps ifvtried to flash other jellybean gapps and the same thing happens anyone know what could be wrong
Related
So I purchased my new LG Optimus 2x from Wind two days ago and I managed to root it today. After rooting it, I downloaded ROM Manager from the android market and did I backup using the built-in clockworkmod recovery app. After doing that, I installed the latest Cyanogenmod stable release and installed it. Everything worked fine, until it rebooted. Now, my device won't get past the lg splash screen. Any help would be greatly appreciated!
thefantasticdron said:
So I purchased my new LG Optimus 2x from Wind two days ago and I managed to root it today. After rooting it, I downloaded ROM Manager from the android market and did I backup using the built-in clockworkmod recovery app. After doing that, I installed the latest Cyanogenmod stable release and installed it. Everything worked fine, until it rebooted. Now, my device won't get past the lg splash screen. Any help would be greatly appreciated!
Click to expand...
Click to collapse
That isn't bricked.
NVFlash Clockworkmod (EXTREMELY IMPORTANT)
Then get the latest nightly, the stable CM7 is too old to be relevant or usable compared to the nightlies and wipe data, cache, dalvik cache, and system before flashing, and then flash gapps and you will be good.
Know that this will wipe everything though.
After flashing clockworkmod with nvflash, would it be possible to go back to my old, wind-provided stock android rom?
Phew, I managed to fix it by installing the T-Mobile rom onto my phone. Thanks for the help! Mods, you can close this thread as you please.
download another version and flash again.u will be fine.
I am having a really weird issue I'm hoping someone can help me out with. I was on 4.1.2 Clean ROM which was working great. I wanted to move to 4.3 Clean ROM (8.1 Core Edition). I did the upgrade and then flashed my modem to ML1 both via TWRP.
The ROM setup fine and ran great. However the first time I did a reboot, the phone gets stuck at the Samsung Galaxy S3 logo and never goes anywhere. I left it sit there for 30 minutes and it was hard locked. Only a battery pull would reset it. Through numerous reboots/pulls, the same thing would happen. I tried wiping Dalvik and Cache in TWRP and fixing permissions, to no avail. Reinstalling Clean ROM 8.1 via TWRP without formatting data did not fix the issue either. The only way to get my phone back up and running was a complete wipe and reinstalling from scratch. Then as soon as I reboot the first time, the issue comes back. I've tested this on a clean install - letting the phone go through the initial setup process but not installing or updating any apps - and it still happens.
So I moved on to try AllianceROM build 22, also a 4.3 build and wiped to do a clean install. No matter what options I choose in the setup, the same problem happens. Interestingly in AllianceROM I always get a acore process has failed error on the first boot.
Then I went to download the Knox-free rooted version of stock 4.3 available from Scott's website. I have the same issue with this. Also a wipe with clean install.
It's obvious there is something my phone doesn't like about moving from 4.1.2 to 4.3. In total, I have probably installed three different ROM's about 20 times now after the past couple days.
I've searched about this problem extensively and the only thing I found is a thread for the AT&T S3 that talks about this exact issue, and using Odin to go to stock 4.3 and loading a custom ROM to fix the issue. But I am under the impression that a 100% stock 4.3 will lock my bootloader.
What I plan to do next is use Odin to flash a stock 4.1.2, then go through the process of moving to a custom 4.3 ROM again.
If anyone knows of a tar'd version of 4.3 that won't lock my bootloader, I would be grateful!
If anyone knows of a different way to fix my problem, I would be grateful for that too!
Well I think I can declare victory. My phone is running Clean Rom 8.1 CE and has survived a reboot after every app install for a total of 15 so far.
As it turns out, I think being on TWRP 2.5 and trying to upgrade to Android 4.3 was the issue. Before I went the route of flashing a stock 4.1.2 release, I thought to check if my version of TWRP was the latest, and it was not. I flashed TWRP 2.7, and did a complete wipe and clean install of Clean Rom 8.1 CE, and it's running like a champ.
I know, I know...the install guide on most every ROM says to use the latest version of your recovery - until now I thought that was a "recommendation" or "best practice" and not a hard requirement. Turns out, at least for me, that it is very much a hard requirement. In reading the release notes for TWRP 2.6 and 2.7, they both appear to implement things specifically for Android 4.3 or 4.4.
Hopefully this info helps someone who may be having the same issue.
So I started having trouble with the Cyanogen I'd been running and decided to move on to a new rom since there are a lot more options available now. I'm running the t-mobile version moto g and am rooted and using CWM and all that jazz, but it seems like I can't get any roms to run on my phone, the only one I got working was the pac rom (ended up doing a recovery back to february from stock 4.3 with root access) I did a clean install with it, and each time it would start having issues of the buttons disappearing and jumping the screen size around (kind of like it was switching in and out of immersive mode every half a second) I tried it 3 times and made sure the settings for full screen were off and it would still start randomly doing that after about 15 minutes or so. On one of my factory resets (the only way I could get out of this jumping screen) I tried updating to 4.4 and ofcourse that failed, then I tried moving on to another rom cyanhacker and cyanogen 11 with aerokernal and both of these said they couldn't install over a corrupted something or another.
So basically what do I need to do? Am I going to have to go back to stock and then update to 4.4.4 and then re-root and a new image and all that jazz or is there any easier way of getting pac-rom on my phone from 4.3?
Bueller? Bueller? Anyone?
Hey guys, this is my first time ever trying something like this, and I already figured most of it out, but I have a little issue, I have the Samsung Galaxy S2 i9100 and I want to update the android version to atleast 4.1.2 Jelly Bean but I can't seem to get it working, every time I install the new update through Odin it would be stuck in a boot loop(when i download the old version 4.0.3 it works straight away), but I decided to try Cyanogenmod 11, I can't get that working aswell, I've tried wiping data,cache,dalvik cache. First I installed the Cyanogenmod ROM and then Google Apps, I get stuck on the cyanogen boot(I've waited for like 30 minutes, nothing).. Please, help.
Thread closed as OP reposted in the correct section
http://forum.xda-developers.com/galaxy-s2/help/samsung-galaxy-s2-cyanogenmod-11-t3428880
I been haveing some issues with roms my screen color would glitch all the time now when i install a rom. It started when I finally got crdroid to install. I installed it 4 times in a row had same issue. so I went back installed rr rom and the phone was fine but the battery drained way to fast so I found a website that had alot more roms to install then what xda shows has I saw viper rom so I installed that it worked till i decided to mess with the settings and the colors start glitching again had to redo everything.
I had crdroid installed before everything worked great upgraded the rom had no issues it all started to happen right after I tried to install linage os is there something I am doing to make it happen a bad install or do I need to do a blankflash allthough my phone not bricked