hello. The problem I'm having is that right after flashing and first loading the ROM PACman v20.0.1 an unending barrage of force close messages flood me (the process com.android.phone has stopped and Unfortunately system UI has stopped), and there's no signal.
please let me know how i can fix this.
ps. have performed multiple factory resets, wipe cache+dalvik before flashing the rom everytime
ROOTED HTC DESIRE S & S-ON
HBOOT 2.02.0002
4EXT RECOVERY TOUCH V1.0.0.5 RC9
is a chance that the ROM wasn't installed properly, or may not have followed all the steps
you can try another Rom
zgabi28 said:
is a chance that the ROM wasn't installed properly, or may not have followed all the steps
you can try another Rom
Click to expand...
Click to collapse
thanks for helping. but i re downloaded and re installed the ROM PACman v20.0.1. Plus i have followed all the steps even upgraded 4EXT to the latest verion. Wanted to know if others having this kind of problem or is it only me. and any solutions to this would be appreciated. the previous version PACman v18.0.0 is working fine. but not PACman v20.0.1
PACman 20.0.1
Hello guys, my problem is that when i flashed pacman 20.0.1 it stuck on htc bootscreen and nothing is going on ..!! What can i Do to fix that Problem ? Lots of other roms are working fine without any problems.
Please help me !!!
Diiesel said:
Hello guys, my problem is that when i flashed pacman 20.0.1 it stuck on htc bootscreen and nothing is going on ..!! What can i Do to fix that Problem ? Lots of other roms are working fine without any problems.
Please help me !!!
Click to expand...
Click to collapse
What hboot do you have, and what roms worked for you? Did you flash? the boot.img
And don't hijack other people's threads for your issues, they might not be the same and it can lead to confusion. There is a help thread specifically to avoid this issue. Could we move this to that thread http://forum.xda-developers.com/showthread.php?t=2143855
[Desire S HELP THREAD] Ask any question (NOOB friendly)
“Be yourself; everyone else is already taken.”
― Oscar Wilde
jugg1es said:
What hboot do you have, and what roms worked for you? Did you flash? the boot.img
And don't hijack other people's threads for your issues, they might not be the same and it can lead to confusion. There is a help thread specifically to avoid this issue. Could we move this to that thread http://forum.xda-developers.com/showthread.php?t=2143855
[Desire S HELP THREAD] Ask any question (NOOB friendly)
“Be yourself; everyone else is already taken.”
― Oscar Wilde
Click to expand...
Click to collapse
Could you please help me regarding my issue. would really appreciate it. thanks
any help from the experienced senior members????
krak0w said:
any help from the experienced senior members????
Click to expand...
Click to collapse
I've been reading the rom thread and it seems your not the only one with similar issues. I would wait for the next build personally
“Be yourself; everyone else is already taken.”
― Oscar Wilde
You have a non SONY panel.
Non-Sony screen panel Desire S users lounge
If you flash the v19.3 you won't get pass on HTC bootscreen but on v20.0.1 you can boot but most apps will FC.
If you install 20.0.1 base on the instruction on "Non-Sony screen panel Desire S users lounge" you can have a fully working HTC SAGA running PACman ROM v20.0.1 BUT you won't have a brightness controll. Brightness is always at max.
zenesis said:
You have a non SONY panel.
Non-Sony screen panel Desire S users lounge
If you flash the v19.3 you won't get pass on HTC bootscreen but on v20.0.1 you can boot but most apps will FC.
If you install 20.0.1 base on the instruction on "Non-Sony screen panel Desire S users lounge" you can have a fully working HTC SAGA running PACman ROM v20.0.1 BUT you won't have a brightness controll. Brightness is always at max.
Click to expand...
Click to collapse
Really appreciate your help. i checked through the method you gave me using Android Terminal Emulator and it gave a bunch of commands with sony in it. so no doubt my screen panel is sony.
i still have no clue why im still having this problem
Have same problem. v19 is fine, but 20 crashed with pop-up " Unfortunately system UI has stopped". Can anyone help?
krak0w said:
Really appreciate your help. i checked through the method you gave me using Android Terminal Emulator and it gave a bunch of commands with sony in it. so no doubt my screen panel is sony.
i still have no clue why im still having this problem
Click to expand...
Click to collapse
Did you wipe System,Boot etc?
NVardan said:
Did you wipe System,Boot etc?
Click to expand...
Click to collapse
I allways do full wipe, factory reset and format all partitions except sdcard. Also tried flash boot.img from working v19.
My info: Desire Saga, S-ON unlocked, H-BOOT 2.00.0002, Recovery v2.2.7 RC5.
msf0r said:
I allways do full wipe, factory reset and format all partitions except sdcard. Also tried flash boot.img from working v19.
My info: Desire Saga, S-ON unlocked, H-BOOT 2.00.0002, Recovery v2.2.7 RC5.
Click to expand...
Click to collapse
I wasn't answering your question, but if it didn't work for you, I can't help you. Formatting all partitions except SD helps me always.
Sent from my Desire S using Tapatalk 2
Same problem
I got the exact same problem. UI stopped working and the phone.android.com. There were no problems with the 19.3 version of PAC-man. Before I tried PAC-man 19.3 i tried a couble of other JellyBean roms and there were programs that stopped working with all of them. Is it my HBOOT version or RADIO that makes the problem?
I format and wipe everything every time I try a new ROM, so that should not be the problem either.
Here are the information from my Bootloader
***Uncloked***
SAGA PVT SHIP S-ON RL
HBOOT 2.02.0002
RADIO-3831.19.00.110
eMMC-boot
A solution
Okay so I have solved the problem on my phone. I downgraded the HBOOT to 0.89.000 (Shout out to these guys http://forum.xda-developers.com/showthread.php?t=2183380) Afterwards I flashed the Radio to match the one that is recommended for the PACman rom (http://forum.xda-developers.com/showthread.php?t=1672537).
When I then installed the rom once more there were no problems and everything worked
Hi all.
I'm trying to run CM10.2 on my tf101g from this thread: http://forum.xda-developers.com/showthread.php?t=2402752
But all i'm getting after flashing from TWRP only asus splash and nothing is booting there. What i must to check or look for to fix this? CM10.1 with android 4.2.2 running very nice, but when i trying to go on 4.3 it fails. Flashing process done ok without any problem.
KatKiss with 4.3 also booted without any problem, but y really liked CM.
So, any advice? By the way, what happend with those builds from NoName team? No update since the end of september, why so?
Sorry, but I can't post in development forum due to restrictions for new users. Thanks for helping and for great job by the way.
First of all, Ive searched regarding this error a lot and am hoping someone can clarify.
I "mistakenly" updated to the stock kitkat 4.4.2 that was released for the Galaxy s4 recently and after realising how crap it was, i installed a recovery manager and loaded on the Google play edition rom by Danvdh
http://forum.xda-developers.com/showthread.php?t=2539361
The rom works great and for the most part my phone works. But every now and then randomly it reboots and then will show Kernel is not seeandroid enforcing. Im assuming the error is due to the fact that I installed stock kitkat.
Am I able to circumvent this error by installing a different kernel? and Is the error related to the random bootloops?
Any help would be much appreciated.
Daikonran said:
First of all, Ive searched regarding this error a lot and am hoping someone can clarify.
I "mistakenly" updated to the stock kitkat 4.4.2 that was released for the Galaxy s4 recently and after realising how crap it was, i installed a recovery manager and loaded on the Google play edition rom by Danvdh
http://forum.xda-developers.com/showthread.php?t=2539361
The rom works great and for the most part my phone works. But every now and then randomly it reboots and then will show Kernel is not seeandroid enforcing. Im assuming the error is due to the fact that I installed stock kitkat.
Am I able to circumvent this error by installing a different kernel? and Is the error related to the random bootloops?
Any help would be much appreciated.
Click to expand...
Click to collapse
Hi,
Generally you must flash the same kernal which has come with the installation ZIP, Please check if you are using a different kernal and the ROM.
This happened with me , as i was using a CWM nightly Kernal with a PAC ROM, which didnt worked for me.
It worked when i got a Kernal build by the PAC itself.
Hope this might answer your query
atuldarne said:
Hi,
Generally you must flash the same kernal which has come with the installation ZIP, Please check if you are using a different kernal and the ROM.
This happened with me , as i was using a CWM nightly Kernal with a PAC ROM, which didnt worked for me.
It worked when i got a Kernal build by the PAC itself.
Hope this might answer your query
Click to expand...
Click to collapse
Well I havent changed anything yet. I am using the same kernel that came with the Google play rom that I installed.
The phone is not recognizing the Sim card, it seems like I lost the IMEI since I updated to CM12, it was working fine when I was on SlimLP. Could someone help me get the IMEI back? I would be grateful if you could provide me with some information regarding this issue and how its dealt with in general.
jnx_r said:
The phone is not recognizing the Sim card, it seems like I lost the IMEI since I updated to CM12, it was working fine when I was on SlimLP. Could someone help me get the IMEI back? I would be grateful if you could provide me with some information regarding this issue and how its dealt with in general.
Click to expand...
Click to collapse
Hey there,
I'm not devs, just a noob user, and I may not find any answer, but could you be more detail or information about your phone?
i.e: P31xx or P51xx, recovery ver 6.0.x.x, which cm 12 version you take from, andwhat triggered the problem, probably download a new apps or flashing new kernel or something.
As far as I know, my P3100 working smoothly using cwm 6.0.5.1 and cm 12 build feb 15, from Android-Andi (not the Slimlp version).
Perhaps someone could help. Cheers.
theandroidneo said:
Hey there,
I'm not devs, just a noob user, and I may not find any answer, but could you be more detail or information about your phone?
i.e: P31xx or P51xx, recovery ver 6.0.x.x, which cm 12 version you take from, andwhat triggered the problem, probably download a new apps or flashing new kernel or something.
As far as I know, my P3100 working smoothly using cwm 6.0.5.1 and cm 12 build feb 15, from Android-Andi (not the Slimlp version).
Perhaps someone could help. Cheers.
Click to expand...
Click to collapse
The one posted by Android Andi.
It works fine except for the IMEI, tried flashing via CWM and TWRP.
Now I have switched back to SLIM LP which doesn't seem to have the issue. Anyways, thanks for your reply, CHEERS.
jnx_r said:
The one posted by Android Andi.
It works fine except for the IMEI, tried flashing via CWM and TWRP.
Now I have switched back to SLIM LP which doesn't seem to have the issue. Anyways, thanks for your reply, CHEERS.
Click to expand...
Click to collapse
You could have tried restoring efs partition :thumbup:
Anyway you have switched to slimLP so no worries
Tapped from my furious Xperia ZR
Dear All,
Sorry to ask some really basic questions. I am new to rooting and flashing. I have successfully rooted and flashed CM10 to a Galaxy tab2 and then recently decided to root by S2 which I no longer needed on a day to day basis.
I successfully rooted it and then flashed the stable version of CM10.1 to it, then.... got to clever for my own good and flashed a CM12.1 nightly to it and without checking the GAPP package that I had already downloaded....the wrong one!
I am now getting constant error messages when I boot it up saying that AOSP Android keyboard not working and to compound the problem when I flashed CM12.1 it installed Cyanogen Recovery which does not have an option to wipe the Dalvik Cache which I think is what is wrong.
Please be so kind as to point me to any threads that may help as I have searched in vain.
Many thanks
Doug
Hi
Here is a Gapps thread for CM12.1: http://forum.xda-developers.com/android/software/tk-gapps-t3116347
You have to do a clean flash of CM12.1. Do you have the i9100 model?