Hello, i am having trouble flashing the latest build of Dirty Unicorns for my note 4 sprint variant. The latest build i flashed 8-18-15 (i think) Goes through the normal boot, then starts to optimize the apps, but before it can do that, it reboots.
So i thought about trying an earlier build, i flashed the 7-x-xx build they have, does the same thing, but then optimizes the full 92 apps, then reboots. any ideas as to why? i would greatly appreciate the help.
*note* the build is a 5.1.1 build, i am currently on the 0g5 firmware for note 4 (rooted).
Related
Anyone having issues with the lock screen not working when they loaded build 88? Tried loading older roms from recovery and it is not taking care of the problem
HELP!!!
You never have to wait long for the next nightly build. Just flash them as they come along as any bugs that are present in one build are quickly squashed in the next.
factory reset
wipe cach/dalvik
flashed pa and gaps
has no keyboard, got around it now it reads all these errors
googleplaystore stopped
androidaosp stopped
.com.android.phone stopped
is this compatible, fixable? worth it?
forgot to add it has android 4.1.2 3.0.46 cynogenmod kernel and pav 2.5
Which gapps are you using?
Also, is there no updated ROM for you device?
Hi,
I recently upgraded to Android 4.4.2 and I have the latest CM 11 Nightly installed.... cm-11-20140217-NIGHTLY-d2att.zip
I installed pa_gapps-modular-full-4.4.2-20140531-signed
and installed the latest modem firmware modem_CWM_I747MUMUEND3
My problem is that the phone keeps randomly rebooting.... no idea why.... anyone else experience this issue?
Also the phone tends to freeze for about 3-6 seconds.... strange....
Other then the random reboots the phone seems to be working quite well. no issues at all.
Any help is appreciated!!! thanks!!
Could be a sensitive power button
Well that's why there called nightlies it might just be a bug....its weird that there hasn't been a stable build yet.....but you can try the monthly snapshot and see if that works
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Try an AOSP-based ROM or return to stock to see if it still happens.
I want to flash CM onto my SGH-T999, but the latest CM nightly is from February. I recently flashed SlimKat and they consolidated d2tmo and the other s3 models under d2lte. Would this apply to CM as well?
Also is a nightly basically a rom that is still buggy and therefore needs to be reflashed every so often when a new nightly is available? Would I have to wipe and reset my phone each time?
Thanks in advance.
CM is the one that merged all d2 devices to d2lte so yes.. And you don't have to wipe and reset every time you flash a nightly, but just remember you may experience a few bugs if you don't from time to time
Canadian T999V
I have a very similar question and I saw this thread and decided not to open a brand new one, but will the dtlte also work for the Canadian t999v, I just want to make sure so I don't brick my device. Going to be flashing it tonight. \
Update: I just flashed the M9 stable, works. Very Nice
Hello everyone,
I'm posting on here because I can't find any solution to my dilemma which I am sure that other people in the AOSPA legacy community have also experienced. I have been using Paranoid Android on my T989 since the 4.4.3 update and I have regularly updated my roms since then. Somehow ever since I updated my phone to 4.5 beta 3, something prevents me from being able to hear or be heard during regular phone calls around an hour after I restart my phone.
I have tried everything to try to make my phone back to normal, I have updated my versions of AOSPA, I have downgraded to stable versions, I have gone to a debloated stock rom (which worked perfectly fine but who likes touchwiz android 4.1.2?) and back to AOSPA, I tried the latest Carbon nightly rom and the problem persisted, I have wiped my internal memory, cache, davlik, etc. multiple times. I am at a total loss as to what I should do to fix this issue. I'm currently running it on 4.6 beta 1 and I still have the issue.
I really love my GS2 and I don't want to part with it or have it running stock. Please help me.
I really appreciate it,
Chris
I've had the same issue , I was running the latest liquid smooth rom . I just flashed back to stock using Odin and all is fine on the stock rom . I just rooted again and am hesitant to install another kitkat rom for fear of this calling issue ........ Anyone else with this problem ?
Playnhooky said:
I've had the same issue , I was running the latest liquid smooth rom . I just flashed back to stock using Odin and all is fine on the stock rom . I just rooted again and am hesitant to install another kitkat rom for fear of this calling issue ........ Anyone else with this problem ?
Click to expand...
Click to collapse
I am also getting this problem on Slim 7.8....must be an audio-caf issue....Can someone go back to an old KK rom (one from earlier months) and see if they experience the same issue? Preferably cyanogenmod
I flashed to stock rom via oden and spent the weekend with the phone and all was good , I flashed to the latest cm-11 with no addons , stock cm-11 kernal and after an hour or so I lost call audio again . We must have done something to the phone in a previous rom cause not many people are having this issue . Now I have flashed about 75 different roms with no issue , I hope someone finds the problem cause I'm not to keen on the stock rom !
I've seen posted that snapchat was the cause of the no call audio problem we are having , I flashed the latest liquid smooth rom last night , download all my apps that I usually do except snapchat and I've had no issues with the calling bug . All is working great .