Coming from a 4.2 version of PAC-ROM I wanted to upgrade to the 4.3 version.
I am using TWRP for my recovery mod to install the 4.3 nightlies from the [ROM] [4.3] [OFFICIAL] [Nightlies] [d2tmo] PAC-Man AIO. The issue is I can download the 4.3 gapps and the 4.3 nightly and install them fine. The phone reboots and I get to set it up like normal. However there is no phone service. So I try to reboot the phone after rebooting it will sometimes boot and have service but most of the time it will just hang on the boot load screen with the blue logo. I have tried every combination of wipe and format. I don't have anything I am trying to save on this phone so I don't care if I lose anything.
Can anyone explain what I am doing wrong? I have no issue installing any older version and other roms seem to work great. I just love the PAC-ROM.
creeksideweb said:
Coming from a 4.2 version of PAC-ROM I wanted to upgrade to the 4.3 version.
I am using TWRP for my recovery mod to install the 4.3 nightlies from the [ROM] [4.3] [OFFICIAL] [Nightlies] [d2tmo] PAC-Man AIO. The issue is I can download the 4.3 gapps and the 4.3 nightly and install them fine. The phone reboots and I get to set it up like normal. However there is no phone service. So I try to reboot the phone after rebooting it will sometimes boot and have service but most of the time it will just hang on the boot load screen with the blue logo. I have tried every combination of wipe and format. I don't have anything I am trying to save on this phone so I don't care if I lose anything.
Can anyone explain what I am doing wrong? I have no issue installing any older version and other roms seem to work great. I just love the PAC-ROM.
Click to expand...
Click to collapse
You answered your own question. I might suggest using the last stable 4.2.2 release of it?
Aerowinder said:
You answered your own question. I might suggest using the last stable 4.2.2 release of it?
Click to expand...
Click to collapse
I understand, but why wouldn't it work on a clean phone? It works on some phone and not on others? I just like to have an idea of why and if it is possible to make it work.
Thanks
creeksideweb said:
I understand, but why wouldn't it work on a clean phone? It works on some phone and not on others? I just like to have an idea of why and if it is possible to make it work.
Thanks
Click to expand...
Click to collapse
I think you already know the answer but don't want to accept it. It's most likely an unusable buggy mess like every other 4.3 ROM. I really don't understand how people can use these as DD. 4.2 was pretty bad when it was first released (4.2.1?). Calls wouldn't come through sometimes, couldn't make outgoing calls sometimes. It got a lot better in the end. Except that you had to have a custom kernel to keep the battery drain in check. Anyhow, 4.3 is 10x worse than 4.2 on it's worst day. Half the time, your IMEI or baseband is unknown. This means no calls and no internet. Why put up with it? For what? I love AOSP, but issues like this are ultimately the reason I'm using Dandroid now.
If you have a T999, and the ROM is specifically built for the T999, you can't fix it. Because the problem isn't on your end. It's not what you want to hear but it's the truth.
Related
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
JonnyZaggi said:
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
Click to expand...
Click to collapse
Since yesterday I am facing the same problems you are describing. At first I thought it was a bad flash or something like that. Clean installed various 4.3 costum roms and it's always the same.
Right now I will look deeper into it since the phone is unusable in that condition.
If I find a solution I will comment.
Best regards
Edit: Okay, works again flawlessly. I simply flashed an nightly from carbon-rom and the lags were gone. Hope it helps. What exactly caused the lag I don't know. For now I am staying on 4.2.2 Carbon as it is my favourite rom anyway and I will wait till there are stable 4.3 from carbon.
Are you sure it's the phone and not an app?
chrisinsocalif said:
Are you sure it's the phone and not an app?
Click to expand...
Click to collapse
Not pretty sure, but it still occured after countless factory resets, wipe cache, wipe dalvic cache and wipe system via TWRP.
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes I did. I only flashed for example newest PA and their PA Gapps.
So far I resolved it by "downgrading" to a 4.2.2 nightly from carbon. The lags are completly gone. I will stay and wait till carbon has stable 4.3.
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Zepius said:
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Click to expand...
Click to collapse
Already did that.
I am having the same/similar problems with my GNex too. Specifically bullets [1-3] from the original post. I am running unmodified yakjuux and have tried with just my google account with no other apps and the same problem exists.
Mine makes a noticeable "click" sound with a vibration followed by a reboot.
It usually happens during calls and after it boots the phone call log shows no record of the incoming/outgoing call that just happened. Its like a blue screen of death for android!
I have sent the phone back to Samsung's warranty service 4 separate times and each time they reported no trouble found in the completion report. They just factory reset or put an older version of jelly bean back on the phone and send it back to me with some notes of PRL updates and other nonsense to make it seem like they did something to fix it.
Does anyone have any suggestions (logs, adb, etc) how I can help prove to Samsung/service absolute that the phone is a lemon (other than trying to video tape the phone hoping it reboots - because that is the last resort)?
I already escalated to executive customer service and they refused an exchange because the completion reports show no trouble found :crying:
Thx!
well... I also have this problem.
First happened when I flash Cm10.2 nightly (don't remember which one).
Then I flash PA, or whatever... Looks like the random reboot relating to notifications? It's usually happened when whatsapp notification coming in, but not always.
But a few weeks ago I flashed stock ROM rooted (via TWRP, not fastboot).
The problems solved. No random reboots anymore. Then today I tried latest CM10.2, and it happened again... Wonder why... Looks like it's a very rare problems.
Interesting to see someone having the same problem...
Now I want to flash stock ROM via fastboot to check if it'll fix.
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
lonestrider said:
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
Click to expand...
Click to collapse
I believe CM offers an upgrade option somewhere in the system settings. Unless you want to wipe your phone and flash directly to 10.2 in which case I do not think you need to flash stock 4.3 first. Maybe just do a reset within 10.1 before you flash CM10.2 via whatever recovery (clockwork etc) you are using but even that may be unnecessary.
My 1 year warranty expires this month so if I can't manage to get something out of Samsung I am going to play around with flashing stock 4.3 as you suggested. I have tried converting yakjuux to yakju in the past but still saw the problem then which made me revert back to yakjuux so I could send the phone back for service).
Hi there!
My WiFi seems to disconnect and then reconnect every 5 to 10 minutes or so, after I have installed different KitKat ROMS. It happens with different ROMS.
My girlfriend also has a Note 2, and I also updated her phone with a KitKat ROM (Android Revolution HD), but her's doesn't disconnect at all.
You guys know what's happening here? I did flash latest MJ5 bootloader, but it says failed. Then I also flashed the WiFi Fix. In Download mode, Phone says, KNOX VOID: 1.
Thanks in advance.
Anyone?
It happens a lot now..sometimes. It seems a 4.4.2 rom issue in combination with my router.
Laptop doesn't disconnect, but phone of my girlfriend does as well. On her phone I also installed a 4.4.2 rom. Different one though.
dmxl said:
Anyone?
It happens a lot now..sometimes. It seems a 4.4.2 rom issue in combination with my router.
Laptop doesn't disconnect, but phone of my girlfriend does as well. On her phone I also installed a 4.4.2 rom. Different one though.
Click to expand...
Click to collapse
dmxl said:
Hi there!
My WiFi seems to disconnect and then reconnect every 5 to 10 minutes or so, after I have installed different KitKat ROMS. It happens with different ROMS.
My girlfriend also has a Note 2, and I also updated her phone with a KitKat ROM (Android Revolution HD), but her's doesn't disconnect at all.
You guys know what's happening here? I did flash latest MJ5 bootloader, but it says failed. Then I also flashed the WiFi Fix. In Download mode, Phone says, KNOX VOID: 1.
Thanks in advance.
Click to expand...
Click to collapse
Another user from Phoenix ROM is reporting the same. WiFi keeps dropping on his phone. Which ROM did you flash on your gf's phone ? And which ROM are you using ? The guy I'm talking about first flashed a stock KK ROM and then Phoenix ROM so he's on the newest boot loader already
Sent from my GT-N7100 using Tapatalk
singhpratik87 said:
Another user from Phoenix ROM is reporting the same. WiFi keeps dropping on his phone. Which ROM did you flash on your gf's phone ? And which ROM are you using ? The guy I'm talking about first flashed a stock KK ROM and then Phoenix ROM so he's on the newest boot loader already
Click to expand...
Click to collapse
Hi, thanks for replying! My girlfriend (still) uses the Android Revolution 30, I use the SupremeKat. I plan to install SupremeKat on hers as well, after mine is configured and all.
Before that we both had Android Revolution version 19, which is still Android 4.1.2 I think. No WiFi problems at that time....
Any idea who it was that reported the same issues?
dmxl said:
Hi, thanks for replying! My girlfriend (still) uses the Android Revolution 30, I use the SupremeKat. I plan to install SupremeKat on hers as well, after mine is configured and all.
Before that we both had Android Revolution version 19, which is still Android 4.1.2 I think. No WiFi problems at that time....
Any idea who it was that reported the same issues?
Click to expand...
Click to collapse
It was @Puffin617 he flashed the official stock ROM first and then flashed the custom 4.4 rom called Phoenix ROM and he reported that the WiFi keeps dropping. I've asked one of the users on xda who has a bit more knowledge about such things that what could be causing this cause many users are complaining about battery drain and frequent WiFi drop not sure why is it only affecting a few phones when people have flashed the same stock ROM and your case a custom ROM. If I find anything useful to share I'll get back at you. Perhaps switch custom ROM? Give Dr ketan's version 7 a shot and see if that removes the WiFi issue. Good luck
Sent from my GT-N7100 using Tapatalk
I have same problem. Stock rom - not root. It drops and reconnect every 2 or 3 minutes.
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
Hi, the link you provided points to build 4. You can find build 9 which is the latest slimkat here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
This is the one I have for my Koodo I747M. *note camera seemed a little buggy in some instances, so I installed open camera. Seemed to work a lot better.
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
drakemiller40 said:
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
Click to expand...
Click to collapse
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
serathe said:
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
Click to expand...
Click to collapse
Im not very experienced lol and got lost on:
"The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course. "
I'm using TWRP
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
serathe said:
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
Click to expand...
Click to collapse
Yeah I always create a nandroid and backup my IME.
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
First thing to try for GPS problems is taking off the back cover and snugging up all the little screws around the phone. Sometimes they work their way loose and the GPS antenna seems to be the first thing to suffer from it.
If that doesn't cure it you might need to flash a stock or at least stock based ROM and rebuild the nvram. Here's a link that describes how to do that if you need to.
Someone showed me the thread with the 12.1 cm rom and the .img for the recovery is it okay if I use flashify to put the recovery on my phone instead of using odin after rooting? Or does someone have a .tar recovery for the L520 in a drop box somewhere? also do I need to update my firmware before flashing a rom? I think I'm on firmware na7 on 4.2.2
it's fine, trust me use flashify. Odin doesn't flash .img files. No, you don't need to update your firmware, it's going to be flashed over anyways.
Seemed to work fine. That cm 12.1 rom still working okay for you?
There's a few little annoyances but it's working okay otherwise. I get an exclamation point by my bars sometimes and have to reset the apn to fix it. GPS has some issues so it's become more a roadmap than actual guidance and I can't send mms but that's not really an issue as I have unlimited data and can just facebook messenger as a workaround. I hope that these issues get fixed but I understand that alot of 5.1 roms have issues with the exclamation point thing and even some unrooted 5.1 phones have the problem. It would be nice to see a fix for these issues but I don't see anyone making any more roms for this phone and the guy that made this rom seems to have landed a job with cyanogenmod and is too busy to update this rom. What a shame but at least I have 5.1 now.
Hmm I suppose I'll stay at 4.2.2 till I feel like flashing 12.1 thanks for all the info. You don't have any overheating issues or random restarts right? Also how does the GPS not work well?
No overheating or random restarts. All things considered its a pretty smooth rom if just a little incomplete. I only tried using the GPS once and it came up with my location and the route for where I needed to go but when i was driving along the GLS was not updating my location. It may have been just a one time thing, idk, I havent needed to use GPS since.
Cool do you know a way to go back to stock if I don't like the cm 12.1 rom?
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Oyongx said:
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Click to expand...
Click to collapse
I'd try using the latest wild kernel.
g0at1 said:
I'd try using the latest wild kernel.
Click to expand...
Click to collapse
well i think i did try wild kernel with cm12.1 latest nightlies. The issue gotten worse. More random reboot occured.
Currently on slimLP with his zerkernel v1.7. I thought this one is perfect, but then out of nowhere the random reboot occured again. It's not as frequent as before but still happen.
Right now I'm using Mokee with wild kernel and everything is going well.
Oyongx said:
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Click to expand...
Click to collapse
Random rebooting is a common issue with all the cm 12.1 based ROM for lg ogp. The cm12. 1 in my opinion was never fully stabilized even by the time the devs were starting to switched to the newer hardwares. If you keep the number of apps you unstated to minimum, you may be able to keep random rebooting down, but this just my observation. I thought the latest bliss pop 4.03 had the rebooting issues sloved, but it rather just had the occurrence down to where it's less. But there are other issues such as the device getting extremely hot, which in turn causes shutdown. To the point where I give up on using LP once again on this device, and move back to kk. The kk may be an older rom, but at least it's stable. With the LP, I think issues with it unable to find the sim card, GPU issues that cause screen to flicker and blackout, all are never fully fixed. Rather, those issues were patched and rigged to make the rom run, but not smooth enough where you see issues such as rebooting and overheating.
Sent from my LG-E980 using XDA-Developers mobile app
hawkwind212 said:
Random rebooting is a common issue with all the cm 12.1 based ROM for lg ogp. The cm12. 1 in my opinion was never fully stabilized even by the time the devs were starting to switched to the newer hardwares. If you keep the number of apps you unstated to minimum, you may be able to keep random rebooting down, but this just my observation. I thought the latest bliss pop 4.03 had the rebooting issues sloved, but it rather just had the occurrence down to where it's less. But there are other issues such as the device getting extremely hot, which in turn causes shutdown. To the point where I give up on using LP once again on this device, and move back to kk. The kk may be an older rom, but at least it's stable. With the LP, I think issues with it unable to find the sim card, GPU issues that cause screen to flicker and blackout, all are never fully fixed. Rather, those issues were patched and rigged to make the rom run, but not smooth enough where you see issues such as rebooting and overheating.
Sent from my LG-E980 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, i think the issue are only on cyanogen based ROM. When i use the lolipop such as Super Mini V6.5 by henrypham91 and lgviet team, it's all good. Deep sleep normaly, no sound delay when game on 2D graphics, and all. But then again, it's noticeably slower if you compare against CM head to head. I really love CM or AOSP based rom because they are so fast.
g0at1 said:
Right now I'm using Mokee with wild kernel and everything is going well.
Click to expand...
Click to collapse
Never heard about Mokee. I'll look maybe and try that. Thanks Edit: it is an AOSP based rom! Might try that. Hopefully my phone survive lol
Oyongx said:
Never heard about Mokee. I'll look maybe and try that. Thanks Edit: it is an AOSP based rom! Might try that. Hopefully my phone survive lol
Click to expand...
Click to collapse
Mokee is a Chinese CM based rom.
g0at1 said:
Mokee is a Chinese CM based rom.
Click to expand...
Click to collapse
The download link seems invalid. I don't understand chinese but on the downlaod the url there's an error 404 written. :silly:
Oyongx said:
The download link seems invalid. I don't understand chinese but on the downlaod the url there's an error 404 written. :silly:
Click to expand...
Click to collapse
Their website has an English version. There should be a British flag on the upper right side. Then download their history zip which is a kind of final release.