So I have been running cm12 for a few days, tried flashing Barrin,sacs v2 and cloudy 1.2 , all of which I have ran successfully before flashing cm12. I make it to the setup on each one and the phone freezing during set up and reboots. iI am at work so I don't have access to the lg flashtool, but I am scratching my head here.I even reflashed twrp, tried invisibleks philz recovery. Nothing works
Lol that happened to me too so I've been on cm12 since it dropped ... I did get cm11 nandroid to work also but my phone won't work stock
I was able to flash barrin v1 , then dirty flashed v2 and v2.1 . stock zv6 flashed first though. It was weird , plus my extsdcard needed to be reformatted.
Try stock zv6 that worked for me. Oh and I flashed a SuperSU zip..I don't know if that did anything just something I did
You may have to wipe internal sdcard.
Glad you got it going I wasn't really that pressed lol I only tried 2x and that was it
Related
I have a p7510 that is Canadian, but I have flashed an American 3.2 rom which I've rooted with CWM 5.5.04. I've been trying to load up Maple Syrup's Jellybean July 18 build. I first flashed this dirty. But I got the flashing X screen for like 15 minutes. Then I tried a different download of CWM 5.5.0.4 because my system was coming up on the computer as a p7500. I thought perhaps I had the wrong cwm. So I went back to 3.2 to do a clean wipe. I've done this twice, reflashing JB after I would root 3.2 again. I have had no luck getting JB to get beyond the flashing animation. Any advice?
Fix
HunchedoverPhone said:
I have a p7510 that is Canadian, but I have flashed an American 3.2 rom which I've rooted with CWM 5.5.04. I've been trying to load up Maple Syrup's Jellybean July 18 build. I first flashed this dirty. But I got the flashing X screen for like 15 minutes. Then I tried a different download of CWM 5.5.0.4 because my system was coming up on the computer as a p7500. I thought perhaps I had the wrong cwm. So I went back to 3.2 to do a clean wipe. I've done this twice, reflashing JB after I would root 3.2 again. I have had no luck getting JB to get beyond the flashing animation. Any advice?
Click to expand...
Click to collapse
OK, now I'm giving my self some advice, or sharing my wisdom. After about 5 or 6 attempts to flash JB with CWM 5.5.0.4, I finally decided to try 5.8....through rom manager. I should have known that this might work, because I had been having trouble backing up my files with 5.5, but it worked quite well with 5.8. Anyway, JB is running smoothly now. I found that Rom Manager with CWM 5.8 and a clean install did the trick.
Thanks again for the rom all you hard workers out there.
Hi, as XDA doesn't allow me to ask this neither on the Omega Thread and on Ktoonsez Thread of the S4 development, I'l have to ask it here untill I have 10 posts.
I have a i9505 Galaxy S4, (I had an S3, a Note II with Omega, and an S2) and installed Omega 5.0 through the way ::indie:: indicates on Omega's thread which is as follows:
Installation Instructions:
1. Backup all your app and data so you can restore them to Omega v5.0 (I use Titanium Backup)
2. Make a full wipe (Data, System, cache, dalvik Cache) from recovery then boot to download mode immediately and flash Stock I9505XXUBMEA with odin
Get the firmware from here.
Flashing stock XXUBMEA is needed to make wifi work. Many users reported that it took them many flashes with odin to make wifi work on stock firmware.
3. Make sure all are working ok with stock XXUBMEA firmware, check if wifi + LTE (if your provider supports LTE) are working ok
4. Flash TWRP Recovery with odin, get it from here
5. Boot to TWRP Recovery and flash Omega Rom.
Wipe data from recovery is not needed, wipe your data only if you want to.
6. If LTE is not working flash this zip: I9505_Enable_LTE.zip
Ok.
Everything working great!
But then I installed Katoonsez GREAT WONDERFULL Kernel, but the device got so hot, and I could observe throught KTweaks that my cores were allways ever online and the clocks weren't adjusting well.
This happened with every governor and scheduler.
Then I could install every Kernel including reintalling the rom with the original kernel afterwards that this happened. The only way to make it stop was going to recovery (TWM didn't helped, but CWM allowed me to format every folder like system folder) and only after formating everything, and installing XUAME2 stock ROM through Odin would make my phone not boot so warm again.
It happened several times and got me lots of flashings to dyscover the baove procedure to make the phone not get warm.
Once, it wokrd I don't know why, with Omega 3.1 and KT-SGS4-TW-JB-INTL-05-30-2013. Actually it had the same issues, but specifically with intelidemand it suddenly started to work fine for the first time, and was the best week I ahd with a phone ever!!!
Then yesterday I tried to update to Omega 5.0 and KT-SGS4-TW-JB-INTL-06-06-2013 and all the madness started again :crying:
I'm stuck in the loop and I simply don't know what in the process is making this happens. I tryed to flash in sevral different ways, but in every single way this happens.
I tried flashing the kernel in the same CWM session as I instal the ROM, I tryed doing separately, I tryed wiping wvwrything, I tried wiping only some things and not others, I tried fixing permissions and not fixing permissions after Kernel install (they recomend to fix permissions)...
Well, it is a nightmare!!! All I wish is to get my phone working as lovely as it was with Omega 3.1 again, but even installing the same files in the same way I did, I'm not geting it!
Please help!!!
BTW when I updated to KT-SGS4-TW-JB-INTL-06-05-2013 also on Omega 3.1 it was still working great.
Even on undervolted note 2 I never seen a Battery last longer! It was amazing! Then yesterday when trying to updadte to get HDR video on Omega 5.0 it all started again...
Wouldn't it make more sense for you to have asked this in the i9505 forum if you're using an i9505?
Sent from my SCH-I545 using Tapatalk 4 Beta
I'm new to this forum and find the i717 a wee bit more complicated than my old phone. (a Galaxy S 4g.)
I've managed to get CWM touch 5.5.0.4 on the phone and have successfully flashed the deodexed stock jelly bean rom. However when I try to flash any of the "quincy.att" based rom, CWM gives me an error, which I imagine means that I need a more recent CWM. Before I flashed stock jelly bean, I was able to get the 6.0.3.6 quincy.att CWM on the phone using the terminal but when I tried using it, it did not see the external sdcard and I could not get there to flash any rom. I tried using ODIN to flash CWM 5.8.4.3 but ODIN just sat there and nothing got loaded onto the phone at all.
So it is kind of a chicken and egg situation here. What is the minimum version of CWM I need to flash any of the quincy.att roms and how do I get it on there and working? Or am I supposed to use TWRP? I haven't tried that. I remember it from the 4g and it was a pain to use on that phone. I have tried to flash the 10.1 quincy.att plain Cyanogen and the chameleon rom and I just get error messages from CWM,
Just use twrp.....your probably getting error 7 ...install twrp
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
TWRP is piece of cake here. you will never look back
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
longhairdaddy said:
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
Click to expand...
Click to collapse
If 6.0.4.3 touch works "fine", why don't you just use that?
veningTrMarchal
tube517 said:
If 6.0.4.3 touch works "fine", why don't you just use that?
Click to expand...
Click to collapse
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
longhairdaddy said:
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
Click to expand...
Click to collapse
Try CM11 for KitKat. It's very stable.
tube517 said:
Try CM11 for KitKat. It's very stable.
Click to expand...
Click to collapse
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
longhairdaddy said:
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
Click to expand...
Click to collapse
I had the same issues with 4.4 kitkat roms. Did you format system in CWM when wiping? This solved my bootloop issues. Also, make sure you have a clean download of the ROM. Flash the ROM twice back to back when flashing a new kitkat rom
I have previously installed custom ROMs before and have successfully been running wanamlite for several months, however, i tried to install CM11 today.
I installed CM10.2 first to get CWM 6.0.4 and then continued to flash CM11. It was successfully installed and booted fine but apps kept crashing such as the playstore. I decided to go back to my wanamlite backup so went back, cleared the caches and went to restore to find that it couldnt find any files. Now when i try to reboot i get the Cyanogen mod cymbol then it loads the background but with a message that reads "the process com.android.phone has stopped" and i cant do anything from there. It will still boot into recovery and download yet this happens everytime i try to boot the phone into the normal mode.
So what did I do wrong? Whats the extent of my problem? & does any bright soul know if and how i can fix it?
Thankyou everyone
Jakeymd said:
I have previously installed custom ROMs before and have successfully been running wanamlite for several months, however, i tried to install CM11 today.
I installed CM10.2 first to get CWM 6.0.4 and then continued to flash CM11. It was successfully installed and booted fine but apps kept crashing such as the playstore. I decided to go back to my wanamlite backup so went back, cleared the caches and went to restore to find that it couldnt find any files. Now when i try to reboot i get the Cyanogen mod cymbol then it loads the background but with a message that reads "the process com.android.phone has stopped" and i cant do anything from there. It will still boot into recovery and download yet this happens everytime i try to boot the phone into the normal mode.
So what did I do wrong? Whats the extent of my problem? & does any bright soul know if and how i can fix it?
Thankyou everyone
Click to expand...
Click to collapse
With what recovery did you perform the backup? Maybe flashing that recovery will let you restore your backup.
All sorted now. I flashed the stock rom through odin and started again with the jeboo kernel and took extra care when flashing everything and now it's all working. KitKat-ed.
Missing some of the aspects of touchwiz a bit and i got a lower score on antutu than with wanamlite but i'll stick with it for a big, if only for the bragging rights when i get back to work on Monday.
Hey folks,
I'm desperately trying to get a CustomRom working on my GP4.
I'm relatively new to the device, but not to CustomRom's, since I was using a Motorola Defy untill last summer, running CM7.2 and CM9, MIUI and a couple of others.
So here's my issue:
I flashed the Terrasilent Kernel in order to get CWM so I could flash the .zip's from there, as some weren't available for odin.
The kernel works fine, but as soon as I try to flash any CustomRom (I tried CM9, CM10.2, Hydrogen and the PACMAN Rom), I'm just getting infinite bootloops.
I also tried flashing with SD card removed, SD card back in....doesn't help. No matter whether it's done with odin or CWM.
Mostly I get stuck at the Samsung screen , the PACMAN insert coin or the Terrasilent phonebooth .
Does anyone have suggestions how I could make it work?
Cheers!
basti_b24 said:
Hey folks,
I'm desperately trying to get a CustomRom working on my GP4.
I'm relatively new to the device, but not to CustomRom's, since I was using a Motorola Defy untill last summer, running CM7.2 and CM9, MIUI and a couple of others.
So here's my issue:
I flashed the Terrasilent Kernel in order to get CWM so I could flash the .zip's from there, as some weren't available for odin.
The kernel works fine, but as soon as I try to flash any CustomRom (I tried CM9, CM10.2, Hydrogen and the PACMAN Rom), I'm just getting infinite bootloops.
I also tried flashing with SD card removed, SD card back in....doesn't help. No matter whether it's done with odin or CWM.
Mostly I get stuck at the Samsung screen , the PACMAN insert coin or the Terrasilent phonebooth .
Does anyone have suggestions how I could make it work?
Cheers!
Click to expand...
Click to collapse
Did you wipe the data/cache? Also, I believe you're supposed to flash then ROM first, THEN you flash the kernel.
TheKryptonite said:
Did you wipe the data/cache? Also, I believe you're supposed to flash then ROM first, THEN you flash the kernel.
Click to expand...
Click to collapse
Forgot to mention that: I tried various ways: first wipe data/cache, then flash ROM; first flash ROM, then wipe cache; wipe cache, flash ROM, wipe again...
In order to get CWM recovery and being able to flash a zip I flashed the Kernel first. For CM9 I followed this http://forum.xda-developers.com/showthread.php?t=2213152
As I couldn't flash any of the pre-flash zip from stock, I thought it's necessary to flash a kernel including CWM first. It was done in the same way in some youtube tutorial I watched, where the guy already had the terrasilent kernel on his device.
For odin, I will check if it works with first flashin the ROM and afterwards the kernel.
Cheers for your fast reply!