Database Users

[Q] Any advice or is my phone bricked..?

Flashed from DamageR_DCG v4.6 Eris Port to CYANOGEN V8 THEMED.
I wish I would have read this post before proceeding further with f*ing up my phone.
I think the following fix would have worked if I hadnt started flashing other roms to try to fix the issue myself.
["-Second: if unresponsive and showing 3G signal bypass setup by touching all four corners of the screen starting with the top left and going clockwise. At the bottom touch the screen just above the language and emergency call buttons."]
After flashing CYANOGEN V8 THEMED, I waited for it to start up and load. Unexpectedly, there was an android icon presented in the middle of the screen, with a hand directing me to touch it. I touched the android icon, it turned white, but that was the end of it. As soon as I let go of the screen, the icon would turn into its normal green and black color scheme. So i touched everywhere, haha, and rotated the screen and continued to press every available space on my phone's screen. I gave up and thought the rom, itself, was "broken". So I tried flashing my previous rom, and the trouble began. I am now experiencing an error message with each rom I try to use. It says "Sorry! The process android.process.acore has stopped unexpectedly. Please try again. Force close button". The error message listed above pops up whenever the phone starts, neither HTC Sense nor Nexus Home loads. I could use some help.
I will try looking for a newer rom version to flash, but I dont think it will work. ;(
**Update - Problem Solved - I did a factory reset/wipe, Dalvik-cache wipe, and proceeded with flashing a new rom.
**Thanks, gnarlyc, it was the Dalvik-cache wipe that fixed the problem.

Go back into recovery and wipe data and dalvik-cache and flash another ROM.

gnarlyc said:
Go back into recovery and wipe data and dalvik-cache and flash another ROM.
Click to expand...
Click to collapse
Okay, I wiped, and am now flashing CELB Froyo2.2.
I will update this post when it is finished.

Cyanogen tazz needs the Google apps flashed right after you flash the rom.
Then you have to wait a minute or so for the 3g icon to appear. Then you can tap the android and proceed with setup.
Tazz v1.0 is super stable and fast. I would try this rom again but make surer you flashed the right Google apps package.
Sent from my Cyanogen Froyo using Tapatalk

Thanks, gnarlyc, it was the Dalvik-cache wipe that fixed the problem.

akaarnaz said:
Thanks, gnarlyc, it was the Dalvik-cache wipe that fixed the problem.
Click to expand...
Click to collapse
Anytime. Been there myself. Not too long ago either.

Kyrillos (v4.0 Final) wiping data on reboot

Hi all,
I rooted my Samsung Galaxy 3 with Kyrillos v4.0. Everything worked fine but I discovered that when I'm rebooting the phone it automatically forgets everything I made with the phone (options, synchronization, widgets, everything..). So it seems like it wipes the data on every reboot.
Anyone have an idea what the problem should be?
Could it be a problem that I had I5800XXJPM before I got Kyrillos?
It says I should need I5800XXJPF to upgrade to Kyrillos or something..
I hope u can help me,
Thanks!

RynoRn said:
Hi all,
I rooted my Samsung Galaxy 3 with Kyrillos v4.0. Everything worked fine but I discovered that when I'm rebooting the phone it automatically forgets everything I made with the phone (options, synchronization, widgets, everything..). So it seems like it wipes the data on every reboot.
Anyone have an idea what the problem should be?
Could it be a problem that I had I5800XXJPM before I got Kyrillos?
It says I should need I5800XXJPF to upgrade to Kyrillos or something..
I hope u can help me,
Thanks!
Click to expand...
Click to collapse
Hm reflash v4.1

I'll try that today.
Thanks!

iam having the same problem with him , the only difference is i was flashing the 4.1 one

red02498 said:
iam having the same problem with him , the only difference is i was flashing the 4.1 one
Click to expand...
Click to collapse
try to install I5800XXJPF first and then install kyrillos´ROM.

u guys r having "zero mb free space" issue ...!! it means u have zero mb free on /data partition.. so whatever changes u changed , is not getting saved in /data partition..!! so after a reboot u r back to the same position where u were before ur previous reboot..

Yeah, it says I have no free space on phone. I can't install an app on my device. So the problem is what you said but what can we do with it?

Helper
Flash XXJPF
Flash Kyrillos.
Install Kies
Download mode. Press = Power + Home + Volume Up.

Wifi problem

Hello i have a problem with the wifi of my xperia, it stucks on seraching and doesn't show any network like if it were not activated. I don't know when it happens but it was working good and suddenly it just stop working.
I'm ussing the gingerDXv14 room, but i have this problem since using CM6 room and after instalating this other room the wifi is still not working. I don't know what to do help please

Flash the hotfix.
Sent from my Shakira using XDA App

I've just installed the hotfix via xrecovery but nothing changed it continues stucking in "searching"

aru2011 said:
I've just installed the hotfix via xrecovery but nothing changed it continues stucking in "searching"
Click to expand...
Click to collapse
You have to install both GingerDX and the Wifi hotfix through CWM, not xrecovery. DX changed it so that it now has to be done on CWM instead. Hope I've helped you.

My WiFi stopped working on v14 too. At first I did it on xRecovery but then I did both the v14 and the hotfix in CWM. Still wouldn't work so I just flashed it back to v13.
Although 3G doesn't work for me now.

Drumbum said:
My WiFi stopped working on v14 too. At first I did it on xRecovery but then I did both the v14 and the hotfix in CWM. Still wouldn't work so I just flashed it back to v13.
Although 3G doesn't work for me now.
Click to expand...
Click to collapse
Initially, that happened to me too but then I full wiped with system and dalvik cache. Then I flashed both V14 and the hotfix and rewiped the system and dalvik cache once again. This was all done on CWM and it worked for time.

AlexLoafTran said:
Initially, that happened to me too but then I full wiped with system and dalvik cache. Then I flashed both V14 and the hotfix and rewiped the system and dalvik cache once again. This was all done on CWM and it worked for time.
Click to expand...
Click to collapse
I'll try that when I get the time! It's a bit tedious...

huawei u8800 pro lockscreen issue

hi
i have a problem with my u8800pro. i have installed a cyanogenmod7 rom and when i press the lockscren button the device shut down instead of locking and i have to reboot it
anyone have the same problem?

Nope.
Sent from my ragelis

Check CM7 thread. I think I've seen complain about this. Didn't happen to me though.

I've got exactly the same problem. And can't find how to solve it. Moreover it turns off instead of locking when time for locking comes.
If anybody knows what causes it and how to solve this problem - please help.
It also happens whit MIUI ROM

Yes the same with me.
Here is 2.2 froyo stock rom http://forum.xda-developers.com/showthread.php?t=1315823

Oi! I had the same prob, the system worked like it should but as soon as I pushed the power button to go to sleep the device reeboted. You need to make sure that you clean the Dalvik cache, wipe data, wipe partition, before you install your Cyanogen ROM. I did that and it helped.

Custom Roms Not Responding.

Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.

Maybe its realy screen problem... did the touch screen works on twrp

fire_onCA said:
Maybe its realy screen problem... did the touch screen works on twrp
Click to expand...
Click to collapse
Yes It Does. Its not the screen issue because on stock rom everything works properly.
Im guessing somethings interrupting with the OS, causing the apps to crash.

aymanabdulla said:
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Click to expand...
Click to collapse
Flash twrp 3.0.0 (over your existing twrp 3.1). Just copy the twrp.zip to your root directory of internal storage and flash using twrp 3.1. Maybe that will help because it helped me.

mfaisal98 said:
Flash twrp 3.0.0 (over your existing twrp 3.1). Just copy the twrp.zip to your root directory of internal storage and flash using twrp 3.1. Maybe that will help because it helped me.
Click to expand...
Click to collapse
but I've already tried that! I started off with 3.0 and when that didn't work I moved to 3.1!
I also noticed I get a small message on top when. I start the phone with the Samsung logo saying that something isn't seandroid when I install a custom room but it isn't like an error or something.
Could the issue be with the kernal?
Or should I try cwm recovery now?

aymanabdulla said:
but I've already tried that! I started off with 3.0 and when that didn't work I moved to 3.1!
I also noticed I get a small message on top when. I start the phone with the Samsung logo saying that something isn't seandroid when I install a custom room but it isn't like an error or something.
Could the issue be with the kernal?
Or should I try cwm recovery now?
Click to expand...
Click to collapse
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck

I suggest flashing the stock 4.4.2 ROM via Odin and then start everything from scratch. Currently facing the same problem after flashing the Ressurection Remix M 5.7.4.

mfaisal98 said:
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
Click to expand...
Click to collapse
Its not actually an error message but a small notice on the top left corner.
When I restore my official rom back the message is normally gone.
But I will try again with ur advice again because I always wipe system before flashing the rom so it could be causing the issue.
Thanks I'll let u know what happens

kaiserfakinaway said:
I suggest flashing the stock 4.4.2 ROM via Odin and then start everything from scratch. Currently facing the same problem after flashing the Ressurection Remix M 5.7.4.
Click to expand...
Click to collapse
I did do that. I have the official stock rom running now since RR and cyanogenmod isn't responding.

aymanabdulla said:
I did do that. I have the official stock ROM running now since RR and CyanogenMod isn't responding.
Click to expand...
Click to collapse
Have you tried flashing RR or CM13 after flashing the stock ROM?
and could you give me the full name of the stock ROM?

aymanabdulla said:
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Click to expand...
Click to collapse
Did you flashed the vendor.zip provided after flashing the rom?If not,then it is the cause of that problem

kaiserfakinaway said:
Have you tried flashing RR or CM13 after flashing the stock ROM?
and could you give me the full name of the stock ROM?
Click to expand...
Click to collapse
Yes, thats what i did.
G7102DDUBNK1_G7102ODDBNK1_G7102DDUBNK1_HOME.tar.md5 this was the file name. it works fine i guess, had some issues with the sim as the phone keeps on asking to reboot but no other issues.

Subhashis said:
Did you flashed the vendor.zip provided after flashing the rom?If not,then it is the cause of that problem
Click to expand...
Click to collapse
Yes i did. as well as the front cam + patch fix. i flashed both yet still the same issue.

mfaisal98 said:
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
Click to expand...
Click to collapse
Ok i tried this with the steps u have told me. still no luck
i went to twrp opened wipe, wiped dalvik cache, cache, internal storage and data. but not the system.
same issue. also the small message which comes in the top left corner is
"Kernal is not seandroid enforcing" red colour font
"set warranty bit : kernal" yellow colour font
why is this shown?
should i try cwm?

So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
aymanabdulla said:
Ok i tried this with the steps u have told me. still no luck
i went to twrp opened wipe, wiped dalvik cache, cache, internal storage and data. but not the system.
same issue. also the small message which comes in the top left corner is
"Kernal is not seandroid enforcing" red colour font
"set warranty bit : kernal" yellow colour font
why is this shown?
should i try cwm?
Click to expand...
Click to collapse
That small message is not a problem. It is showing because the kernel is not selinux enforcing.

kaiserfakinaway said:
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
Click to expand...
Click to collapse
Why Doesnt any one else have this problem?
oh is it? what about lineage os 13.1 running MM?
Fine i have put cm12.1 for download, will flash it and let u know what happened.
Fingers Crossed

kaiserfakinaway said:
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
Click to expand...
Click to collapse
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.

aymanabdulla said:
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
Click to expand...
Click to collapse
Have you tried any TW MM ports like J7 Hybrid MM Heavily Debloated Port or [ROM][6.0.1][TW][Electron Rom][Version 1] or [ROM][6.0.1][TW] JSERROM Version 3.1 [BETA][ms013g]?

kaiserfakinaway said:
Have you tried any TW MM ports like J7 Hybrid MM Heavily Debloated Port or [ROM][6.0.1][TW][Electron Rom][Version 1] or [ROM][6.0.1][TW] JSERROM Version 3.1 [BETA][ms013g]?
Click to expand...
Click to collapse
Nope, all of them have camera issues too.
but im sure there will be a fix for this, since its running LOLLIPOP.
I'll let u know.

aymanabdulla said:
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
Click to expand...
Click to collapse
Might not be a kernel issue because I have also tried with this custom kernel [KERNEL][5.x/TW/6.x]Infected Kernel R4[15-05-2016] and still the same.