Hey guys,
I wanted help installing Unofficial CM 11 ROM on my Galaxy S III (T-Mobile). I tried installing sswb27's unofficial ROM of CM 11 (http://forum.xda-developers.com/showthread.php?t=2547825&highlight=cm+11) I tried installing it with latest version of CWMR & TWRP, it is installed but it doesn't boot up, like the bootup animations just keep going, I've waited for about 2 hours. But it doesn't seem to work. If anyone can figure out what I'm doing wrong, I'd really appreciate your help!
Cheers!
Wipe Dalvik + Cache in recovery. If that didn't help, do factory reset.
Perseus71 said:
Wipe Dalvik + Cache in recovery. If that didn't help, do factory reset.
Click to expand...
Click to collapse
Did all of those. Dalvik, Cache, & Factory Reset.
Try another Kitkat Rom if that's what you are looking for. Perhaps the port has issues.
Give the official CM11 nightlies for our phone a try: http://download.cyanogenmod.org/?device=d2tmo
Perseus71 said:
Try another Kitkat Rom if that's what you are looking for. Perhaps the port has issues.
Click to expand...
Click to collapse
Upgrading to the newest TWRP did the trick! Everything is working fine now. :good:
Thanks for the help!
Related
Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!
Firewalker1980 said:
Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!
Click to expand...
Click to collapse
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily
ahmadallica said:
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily
Click to expand...
Click to collapse
Hey thx for your suggestions!
I always flash a "new" rom that way though. But an update of the same rom, I "dirty" flash, which should be fine according to everyone.
No matter what Rom/Kernel I use, I still frequently have to pull the battery out.
It's never from locking up within Android. It just freezes/loops on the Google bootlogo.
I once wiped everything, even the storage space, and it helped for a little while, but did not make it go away for good.
Could it be related to certain apps ? Maybe PGM or Seeder or smth ?
All input welcome
---------------------------------------------------------------
Phone: Samsung Galaxy Nexus Maguro
Rom: AOSPA 2.99 latest
Kernel: AK Purity v20
Recovery: TWRP 2.3.3.0
Hello,
I'm having issues to get the Pacman 19.1a (GSM) to start. It's stuck at boot. I've tried flashing 19.1, which is booting fine, however this is not allowing me to enter a PIN code. This issue was reported fixed in 19.1a which is why I tried.
I'm using the following kernel: boot-HELLBOY-CM10-201212251747.img
Is anyone else experiencing this issue?
Thanks!
Did u do factory reset n cache wipe
Sent from my One V using Tapatalk 2
bahubali67 said:
Did u do factory reset n cache wipe
Click to expand...
Click to collapse
Sorry forgot to mention that; yes I did and I wiped Dalvik as well.
flash the latest kernel then in recovery do a wipe data/factory reset then try to install
FTMC said:
Sorry forgot to mention that; yes I did and I wiped Dalvik as well.
Click to expand...
Click to collapse
The same experience, also fully wiped. Stuck on Pacman logo.
gulsher said:
flash the latest kernel then in recovery do a wipe data/factory reset then try to install
Click to expand...
Click to collapse
As far as I know, I'm using the latest hellboy kernel. I've tried CM9 and CM10, but they both have the same effect. Should I be mistaken, could you provide me with a download link or version number I should get?
@brusell: So it seems I'm not the only one? I would have reported it in the ROM's topic, however my current postcount does not allow me to...
Resolved in Verdion 19.3
Just wanted to post the "solution"; the issue has been resolved in version 19.3.
Ok so I did a factory reset wiped cache and wiped dalvic, installed pacman 19.3 using twrp and then flashed hellboy kernel and rebooted, but I've been stuck at the pacman logo for 2 hours!! Did I do anything wrong? Can you tell me how u got out of it on 19.1?Do i just wait for the battery to die?
nvr mind got it
swhatevers said:
Ok so I did a factory reset wiped cache and wiped dalvic, installed pacman 19.3 using twrp and then flashed hellboy kernel and rebooted, but I've been stuck at the pacman logo for 2 hours!! Did I do anything wrong? Can you tell me how u got out of it on 19.1?Do i just wait for the battery to die?
nvr mind got it
Click to expand...
Click to collapse
Hey mate, i'm having the same problem as you did. Could you post the solution? Thanks in advance!
I upgraded my phone from the stable cm10, to the experimental cm10.1 (stupid, I know), after getting too frustrated with the glitches I went to downgrade back to 10.0 using CWM, I did a factory reset, and cleared the cache and everything and found myself in a bootloop. Thinking I just had to live with CM10.1 until a stable version came out I tried to flash CM10.1 back on again to get out of the bootloop, unfortunately my phone is still stuck in a bootloop. Does anyone have any ideas on how I can fix this? I'm thinking that flashing the stock ics rom, then reflashing cyanoganmod 10 might work but i'm not sure.
WhittyAndrew said:
I upgraded my phone from the stable cm10, to the experimental cm10.1 (stupid, I know), after getting too frustrated with the glitches I went to downgrade back to 10.0 using CWM, I did a factory reset, and cleared the cache and everything and found myself in a bootloop. Thinking I just had to live with CM10.1 until a stable version came out I tried to flash CM10.1 back on again to get out of the bootloop, unfortunately my phone is still stuck in a bootloop. Does anyone have any ideas on how I can fix this? I'm thinking that flashing the stock ics rom, then reflashing cyanoganmod 10 might work but i'm not sure.
Click to expand...
Click to collapse
Try TWRP 2.5.0.0 does a great job of wiping
read the steps on how to wipe and flash in the text file link
hope this helps you out m8
http://forum.xda-developers.com/showthread.php?t=2249849
IVIorph said:
Try TWRP 2.5.0.0 does a great job of wiping
read the steps on how to wipe and flash in the text file link
hope this helps you out m8
http://forum.xda-developers.com/showthread.php?t=2249849
Click to expand...
Click to collapse
Thanks for the help man, did the stock rom flash which worked, then i did another cyanogenmod rom flash and still got a bootloop. I ended up just doing a darkside super wipe and it booted fine. One other quick question for anyone that can help, my phone keeps breifly freezing every 5 or so seconds, it's just like a quick stop and happens for everything from scrolling a page, to watching a video. Does anyone have an explanation for this?
My boyfriend's Gnex was having problems so I told him to update his phone. We were both using Rufdroid and since I wanted to try a new rom with 4.3 OS I flashed my phone first. I went quite nicely and I'm loving PA3+ right now. Problem is when my bf flashed his gnex following the same steps I did with mine, his home soft key and most apps aren't working. he tried to reflash the rom and reinstall the apps but it's still the same. how can I fix this??
Did he dirty flashed the ROM?
Sent from my Galaxy Nexus using xda premium
pr0xyw0rm said:
Did he dirty flashed the ROM?
Click to expand...
Click to collapse
I followed the steps on the PA3+ thread here.
TeddyChris said:
I followed the steps on the PA3+ thread here.
Click to expand...
Click to collapse
What he meant was did he not do a factory reset, clear cache and clear dalvik when he flashed the ROM?
You have to do a factory reset which deletes the previous OS (including all your apps) then only flash PA3+.
Factory Reset ALONG with SYSTEM wipe
he did all that
Seraz007 said:
Factory Reset ALONG with SYSTEM wipe
Click to expand...
Click to collapse
System wipe is wasted step. The install script formats the /system partition for you.
Factory reset alone is sufficient for a new ROM flash.
Sent from my Galaxy Nexus
Got the problem solved. I changed the recovery from TWRP to CWM and reflashed the rom. There was an error during the installation, but now it's working great.
Anyway, thanks for your help. :good:
Is anyone having an issue with the new D2LTE builds that have been built recently?
I have tried to flash a few (carbon and c-rom) and just get stuck at kernel splash page. I am on the newest TWRP(2.7), the lk3 modem/bootloader and wiped data,cache, dalvik, and reformatted my internal sd card.
If anyone else is experiencing this, what was done to resolve it?
Edit: I have now also tried
1. Restoring to original stock touchwiz 4.1.1
2. Wiping cache from original recovery
3.Rerooting
4.Restoring a backup of 4.3
5.Attempted to update to C-Rom, Carbonrom, Resurrection Remix -- No Luck Fails
Corvetrims77 said:
Is anyone having an issue with the new D2LTE builds that have been built recently?
I have tried to flash a few (carbon and c-rom) and just get stuck at kernel splash page. I am on the newest TWRP(2.7), the lk3 modem/bootloader and wiped data,cache, dalvik, and reformatted my internal sd card.
If anyone else is experiencing this, what was done to resolve it?
Click to expand...
Click to collapse
I'd like to know myself. I'm stuck too. I can flash a 4.3 rom and everything works, but when I reboot, it gets stuck. All was fine until I flashed Wicked rom and flashed " MJ2 bootloader MJB" Now every time I reboot it gets stuck. Also If I try a reflash, the only way to get it to bootup is to format before flashing.
Try using Philz Touch as your recovery program.
audit13 said:
Try using Philz Touch as your recovery program.
Click to expand...
Click to collapse
I had cwm when I originally started out, switched to twrp to see if the recovery was the issue.
I assume you were running the latest version of cwm before you switched to twrp so it can't be the recovery.
Are you doing a full wipe of the system, cache, data, and Dalvik before installing the ROM?
Yea every time I wiped data, cache, dalvik , I even reformatted once. I have managed to boot up into tasl650AOKP which is a d2lte build but no other ROMs. I mean at this point it looks like I should just wait a bit to see if it is something with the ROMs interacting with my phone(as per all phones are made different)
Sent from my d2lte using Tapatalk
Are you wiping the system before installing? Have you tried wiping system, dalvik, data, cache, install the rom, wipe and re-install the same ROM a second time without trying to boot the ROM in between the 1st and 2nd ROM install?
audit13 said:
Are you wiping the system before installing? Have you tried wiping system, dalvik, data, cache, install the rom, wipe and re-install the same ROM a second time without trying to boot the ROM in between the 1st and 2nd ROM install?
Click to expand...
Click to collapse
Yeah I gave it a shot still no dice. I keep seeing other people having similar issues, so I am still leaning it has to do with the differences in d2lte builds vs dtatt builds
Sent from my d2lte using Tapatalk
d2att ROMs are okay? Just not any d2lte?
audit13 said:
d2att ROMs are okay? Just not any d2lte?
Click to expand...
Click to collapse
As I stated before I am able to boot int Task650AOKP(Which is a d2lte build), any of the others that I have tried have not worked. There are some updates out today, I am going to attempt again and post back results.
As a test, I flashed my i747m back to stock 4.1.2 via Odin. I then installed the latest version of Philz Touch for the d2lte and installed the d2lte version of Validus. Validus booted without any problems.
Edit: just tried the lastest nightly Pac-Rom and Resurrection ROM. Both ROMs had no problem booting to the desktop.
audit13 said:
As a test, I flashed my i747m back to stock 4.1.2 via Odin. I then installed the latest version of Philz Touch for the d2lte and installed the d2lte version of Validus. Validus booted without any problems.
Edit: just tried the lastest nightly Pac-Rom and Resurrection ROM. Both ROMs had no problem booting to the desktop.
Click to expand...
Click to collapse
Thanks for the help, I actually was just able to boot into C-Rom by following the same steps except I am using TWRP. No idea really what caused the Roms to get stuck on boot. Quite annoying.
I had TWRP on my phone but I was having problems installing ROMs when I first got the phone in January.As soon as I switched to CWM or Philz, no problems at all except for ROMs based on a stock 4.3 ROM.