[Q] Any advice or is my phone bricked..? - Droid Eris Android Development

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.

Related

gapps/google talk/market/acore crashing/not working

Hi all, i have been having a very bazaar problem lately...When my phone boots up i get a pop-up message indicating that the gapps process shutdown unexpectedly...and sometimes i may even get a acore crash too. Applications from the market do not download...when i select my download i will end up getting a gapps crash and then the supposed download just sits there saying "starting...". Google talk doesn't even open! It will just say that the process quit unexpectedly. Even after a fresh install with factory data reset all these problems will continue. The initial boot up screen/tutorial will even show a gapps crash. I have tried with 3 different versions of cyanogenmod all with the exact same problem..Each version i've tried with a2sd enabled and disabled, formatting the partition each time before a new install to ensure no data carry-over issues. I don't know what to do. To me it seems like it make be something on googles side...but i can't for the life of me figure out whats causing these wild problems. Help would be very much appreciated.
ANDROID Market problems
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
six6star said:
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
Click to expand...
Click to collapse
I have searched and it seems many people have the Market/Gtalk problem.
I have the same problem (with an Eclair 2.1 Cyanogenmod rom) and I've not been able to find a solution. Wiping the cache makes nothing.
Anyone knows how to solve it?
Huh. I had a problem with the market at first with cyan 5.0.8 . I went in the terminal and ran fix_permissions after su and haven't had any problems since. Might try that
Sent from my HTC Magic using XDA App

[TELUS T959D Fascinate]-Running ONECOSMIC'S ICS

Hello.
This is where you can look at the tutorial and get the files to install if you feel like jumping into it ...
ICS Step by step and files
Note: if you do flash this and it hangs at the boot screen, pull the battery and flash it again and it should work. Some have had to do it 3 times.
I take no credit for this ROM and full props go to the developers of the above post and all those working to make this happen.
First the look and feel of ICS is nothing short of superb. The speed as of now is similar to all the other ROMS I have tried with a little chop here and there but nothing major.
Yes lots of little issues and items that do not work like the camera and GPS but not a huge deal for me so I am willing to stick to it.
Battery so far is decent. 13 hours and 43 min. on the first charge to calibrate and sitting at 24% still. This included allot of playing with the phone and reboots to test jigs
As for the issues that are somewhat bothersome, they include the following.
1. No home or search button. I know same as usual when installing an i9000 ROM but the key mappings from the GB ROMS does not work.
2. BLN (issue all around) will remain lit until you wake the phone to get the notification.
3. They had to do some funky stuff to get 3G to work so it lags to start. Not a huge deal cause it does start and remain working.
I will be continuing to use this ROM and hopefully everything will be working soon (these guys are flying. Also I have been told that the folks over at Glitch are already working on the kernels for the ICS port so that is promising as well.
If there are any other out there running this on our phone chime in with your thoughts or fixes if you have any.
Thanx
Bucky
Thanks for starting this thread. Can't wait to hear about your progress.
Alpha 7
Hey here is the update ...
Installed the Alpha 7 update today and I have to say this rom is fantastic.
1. Camera is fixed and works like a charm.
2. GPS locked in seconds and accurate indoors!! Big improvment over all other roms I have used.
3. HW Acceleration is fixed and working from what I can tell
4. You Tube is fixed and can watch video
Still on the not working list
1. Can not plug the phone in while off as it just restarts. this is a work in progress and known issue
2. Can not record video
3. Will not read a SIM card for contacts and so on (thank god for Google sync)
4. Still no home or search buttons (I think I may need to work on that on myself unless a kernel is released)
SO my review so far ...
No real issues with the general use of the phone. Text, phone, email and web are solid, I have installed apps from the market with no issues and not one FC yet. Battery life is good and nothing is taking over. I have been able to use the phone all day and still have lots left over before going to bed and plugging in. I have not been through a full battery as of yet but that is what I am working on now.
Memory - Last I looked I had 174MB of memory remaining which is the highest I have seen.
ICS is really smooth and fast while moving around. I am going to continue to play with it and report back here for everyone.
I don't use a whole lot of apps so there won't be much regarding those.
Thanx for stopping by and I will post pics when I can.
Bucky
Nevermind
Sent from my SCH-I500 using XDA App
Thanks for the update. From your review, it sounds like an awesome rom. Can't wait to try it but need them to fix the video recording first. Although I might just cave and try it out just to see what the fuss is all about
Can always restore my current setup... lol.
Update ...
been getting the SOD today and not sure why, I mentioned above that the HW acceleration was working, I misunderstood and it is not fully working yet.
I found that the system partition is very small. There was an update which required copying libs and there was not enough space left to do this (2MB). Not too sure if this is due to coming from MIUI or just a ROM issue.
Alpha 8 was released but had quite a few issues so not flashing that one.
Daily use has been great so far (except for the SOD) with no reception or data issues.
I am still working on the home and search buttons but I think that will get fixed with a kernel update. I tried the keymap file but these buttons do not even register in recovery so I get nothing in the ROM either.
More to come ...
Haven't tried this (likely won't as I need the phone for work) but buck have you tried the manual key fix - some directions in our thread on putting on Darkys 10.3.
Sent from T959D running Miui
Yup been there done that no go
Sent from my GT-I9000 using XDA App
Hey buck , was doing some searching in teamhacksung's thread about their ICS port, and someone suggested to change the following and then the key mapping for our phones will work properly. Not sure if the file system is the same for both, but definitely a bit of info if it isn't!
All you have to do is change this part on**arch/arm/mach-s5pv210/mach-aries.c*
*Original**(line 1216~1221)
static const int touch_keypad_code[] = {
#if defined (CONFIG_SAMSUNG_GALAXYS) || defined (CONFIG_SAMSUNG_GALAXYSB)
KEY_MENU,
KEY_BACK,
*0,*
*0*
----------------------------------------------------------------------------*
*Edited*
static const int touch_keypad_code[] = {
#if defined (CONFIG_SAMSUNG_GALAXYS) || defined (CONFIG_SAMSUNG_GALAXYSB)
KEY_MENU,
KEY_BACK,
*KEY_HOME,*
*KEY_SEARCH*
Sent from my GT-I9000 (T959 mod) using XDA App
Thank for the input. After flashing bata 1 all the buttons are working. More to come: )
Sent from my GT-I9000 using XDA App
Hey, have a telus fascinate too. Know how to flash and all that fun stuff. Just don't fully follow where you make the changes for key mapping...if you could just guide me in the right direction, I can figure the rest out...
changes in the kernel zip? the beta zip? after flashing? something completely different?
thanks a lot!
There are no changes to be made with this ROM, they are built in. Just flash and all good.
I will post update tonight after work.
Sent from my GT-I9000 using XDA App
yeah sorry realized that immediately after posting / flashing to the new rom.
have you tried out BT audio? I can connect to different devices but audio won't stream
havoksupertwit said:
yeah sorry realized that immediately after posting / flashing to the new rom.
have you tried out BT audio? I can connect to different devices but audio won't stream
Click to expand...
Click to collapse
There are allot of BT related posts in the QA. I personally do not use any BT but I do have a headset that I will try when I get home.
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
bucknetbucky said:
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
Click to expand...
Click to collapse
Calibrated my phone this morning. Heavy use today configuring everything but about 52% now (sooo 5 hours or use?)
Why god! Whhyyy!!
bucknetbucky said:
There are allot of BT related posts in the QA. I personally do not use any BT but I do have a headset that I will try when I get home.
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
Click to expand...
Click to collapse
AT LEAST YOU GUYS HAVE IT RUNNING!!
I am having a hell of a time trying to get it to work. I have tried so many different ways to get it up and running but no luck.
I've tried installing it from MIUI 3 times but all I get when trying to boot into ICS for the first time is a Black Screen after the FuguMod boot screen.
The funny thing is that the 4 soft buttons at the bottom light up still.
So I then decided to try the JVT way:
-Flashed JVT DARKYROM (ODIN)
-Lagfix OFF
-FULL WIPEs (factory reset, cache, dalvik)
-FLASHED CM7.1 STABLE
-FULL WIPEs (factory reset, cache, dalvik)
-Flash ICS BETA1
-Flash kernel
-FOR THE SECOND TIME:
-Flash ICS BETA1 AGAIN
-Flash kernel AGAIN
Same issue, black screen after the FuguMod boot screen, buttons still light up.
So i tried a couple more times in a few different ways based off what I have already tried, but this time, before booting into ICS for the first time, I installed the 'Superuser-3.0.6-efgh-signed.zip' package.
Same issue. I'm not having any luck here.
iwebsource said:
AT LEAST YOU GUYS HAVE IT RUNNING!!
I am having a hell of a time trying to get it to work. I have tried so many different ways to get it up and running but no luck.
I've tried installing it from MIUI 3 times but all I get when trying to boot into ICS for the first time is a Black Screen after the FuguMod boot screen.
The funny thing is that the 4 soft buttons at the bottom light up still.
So I then decided to try the JVT way:
-Flashed JVT DARKYROM (ODIN)
-Lagfix OFF
-FULL WIPEs (factory reset, cache, dalvik)
-FLASHED CM7.1 STABLE
-FULL WIPEs (factory reset, cache, dalvik)
-Flash ICS BETA1
-Flash kernel
-FOR THE SECOND TIME:
-Flash ICS BETA1 AGAIN
-Flash kernel AGAIN
Same issue, black screen after the FuguMod boot screen, buttons still light up.
So i tried a couple more times in a few different ways based off what I have already tried, but this time, before booting into ICS for the first time, I installed the 'Superuser-3.0.6-efgh-signed.zip' package.
Same issue. I'm not having any luck here.
Click to expand...
Click to collapse
OK so here is what I did ...
Started from MIUI 1.11.18
1. Do a nandroid backup
2. download all the files to the SD card. This includes the ROM, Kernel and super user fix
Links:
Kernel:http://ice-cream-sandwich-sgs.googlecode.com/files/FuguModICS_GT-I9000_update.zip
ROM:http://ice-cream-sandwich-sgs.googlecode.com/files/ICS_4.0.1_r1-Beta1-i9000.zip
Super User:http://ice-cream-sandwich-sgs.googlecode.com/files/Superuser-3.0.6-efgh-signed.zip
3. Boot to recovery and do factory reset, wipe cache and davlik cache
4. Install the Kernel first and reboot now
5. Boot into recovery factory reset and wipe cache and Davlik and Install the ROM then reboot now
6 Boot back to recovery and install the Kernel again with out the wipe
7. If after reboot you do not have root then boot to recovery and flash super user fix
8. reboot and it should be working at least it was for me
It seems to me that you are missing the first flash of the kernel before the ROM. It sets up the file system from what I gather
Note: If needed flash the kernel and rom then kernel again with all the wipes as mentioned above.
I know there are allot of folks having issues getting it to run. Not too sure if it was the way I installed MIUI that might have made the difference.
My battery is charging now so I can calibrate it and see how it goes after that (it drained pretty quick today) lol.
I hope you can get it going cause it truly is awesome
Still not working:
Can not charge with the phone off
Google TTS stops working
Phone will not vibrate for SMS or email when in silent mode
BLN stays on for notifications until the phone is taken out of sleep (can be turned off)
Compass is why off (have not attempted to calibrate yet though)
11 MB left in the system partition (not much but I do not think there will be many changes there)
Video play back is choppy and some will not play
Bucky
regarding the black screen:
- had that too... I let it sit on the black screen for 2-3 minutes and then it went to the boot screen animation (a multi-coloured )...that for a few minutes...then finally booted.
How i got it working:
a) Started on MIUI...booted into clockwork
b) Backup
c) Wipe data / factory reset and cache and dalvik cache
d) Install rom and then kernel
e) Restart
f) Install rom and then kernel
g) Restart and wait very patiently for a little while
h) Once it all works, can reboot into clockwork and install superuser
Good luck! I really think the rom is nearly stable enough for daily use...
-------
Also have the no vibrate on silent... haven't tried the other stuff yet.
Oh and TTS hasn't crashed on this version yet for me...
Astrid glitches a little to a lot.
Changing from google tts to picco tts solves the problem there. As for the other stuff it is all reported as known.
I am using as a daily on my phone and no issues with general use. Still testing battery and that seems to be a bit of an issue with regard to Android OS as usual
Sent from my GT-I9000 using XDA App
So to install this ROM I would just have to install it as per totallydubbed's instructions? I don't want to flash miui if I don't have to to try this out.
Sent from my GT-I9000 (T959 mod) using XDA App

[Q] Help with CarbonRom/TWRP/RazrM?

Question:will someone help me?
I will begin by saying that I have no idea where the problem exists for my individual situation, and it would be great if I could get some help.
Background:
I used to run Dead Rage 1.2.
Now I have been back and fourth between Skrilax nightlies and Bytecode's cm10.1 with little to no hiccups.
Over time I began to notice a little lag(notification drawer, swiftkey, and basic ui elements).
Problem description:
Then I decided to try some other roms to fix my issues.
When I flash Carbon rom:
- It has no lock screen by default (and I have not been able to fix this in lockscreen settings)
- The home button does not work (neither in pie controls)
- the quick settings panel button in the notification drawer does not open the quick settings( nor can I access the quick settings any other way)
- the home screen apps are strangely and slightly above the software buttons
I saw someone with similar problems in the posts of carbon but it was resolved by a single reflash.
I also tried a relatively new rom called Revolt on droidrzr:
- I experienced similar issues with the home button
- I did not delve into the issues more because the issues were similar to carbon
Explained, further:
As explained above I have flashed without issue before.
I am under the impression that the way to flash is:
1. mount system
2. wipe system
3. repeat
4. reboot recovery
5. mount system
6. flash
I have tried every variation on this set of rules I think is possible for carbon. I initially had TWRP 2.3. I have flashed without rebooting recovery, without mounting system, with a factory reset on the previous rom, wiping cache and delvik as well. If I don't wipe the system I get weird crashes and the home button still doesn't work but it fixes other things like quick settings. Sometimes when I would wipe system, and not do a factory reset, and flash carbon all my apps from the Bytecode build persisted. This made me think it was a recovery problem.
Then I flashed TWRP 2.5. I have similarly tried everything with TWRP 2.5 and get the same results. I have tried 6/21, 6/23, 7/2, 7/4 carbon on both recoveries.
I have a backup of bytecode cm10.1 and I am running that currently.
If some one would help me troubleshoot or fix my problem, I would love to get carbon. And I would be very much appreciative.
If I am in the wrong place please point me.
I did not post in the carbon topic because I do not have more than 10 posts.
I know that people are not paid to help me so I respect when they do.
Also if you need screenshots, I can reflash carbon and take some shots too.
mrnathanman said:
Question:will someone help me?
I will begin by saying that I have no idea where the problem exists for my individual situation, and it would be great if I could get some help.
Background:
I used to run Dead Rage 1.2.
Now I have been back and fourth between Skrilax nightlies and Bytecode's cm10.1 with little to no hiccups.
Over time I began to notice a little lag(notification drawer, swiftkey, and basic ui elements).
Problem description:
Then I decided to try some other roms to fix my issues.
When I flash Carbon rom:
- It has no lock screen by default (and I have not been able to fix this in lockscreen settings)
- The home button does not work (neither in pie controls)
- the quick settings panel button in the notification drawer does not open the quick settings( nor can I access the quick settings any other way)
- the home screen apps are strangely and slightly above the software buttons
I saw someone with similar problems in the posts of carbon but it was resolved by a single reflash.
I also tried a relatively new rom called Revolt on droidrzr:
- I experienced similar issues with the home button
- I did not delve into the issues more because the issues were similar to carbon
Explained, further:
As explained above I have flashed without issue before.
I am under the impression that the way to flash is:
1. mount system
2. wipe system
3. repeat
4. reboot recovery
5. mount system
6. flash
I have tried every variation on this set of rules I think is possible for carbon. I initially had TWRP 2.3. I have flashed without rebooting recovery, without mounting system, with a factory reset on the previous rom, wiping cache and delvik as well. If I don't wipe the system I get weird crashes and the home button still doesn't work but it fixes other things like quick settings. Sometimes when I would wipe system, and not do a factory reset, and flash carbon all my apps from the Bytecode build persisted. This made me think it was a recovery problem.
Then I flashed TWRP 2.5. I have similarly tried everything with TWRP 2.5 and get the same results. I have tried 6/21, 6/23, 7/2, 7/4 carbon on both recoveries.
I have a backup of bytecode cm10.1 and I am running that currently.
If some one would help me troubleshoot or fix my problem, I would love to get carbon. And I would be very much appreciative.
If I am in the wrong place please point me.
I did not post in the carbon topic because I do not have more than 10 posts.
I know that people are not paid to help me so I respect when they do.
Also if you need screenshots, I can reflash carbon and take some shots too.
Click to expand...
Click to collapse
see post #7 here: http://forum.xda-developers.com/showthread.php?t=2355676
this should probably be in the Q&A/Help/Troubleshooting section....
Thank You So Much!!!!!!!!!!!!!!!!!
I know its soon and I am still crossing my fingers, but thank you!

[Q] Help me pls, no phone signal

Ok, I was running PA 4 Beta3 but was having problems with the screen delay so thought I would completly wipe my phone, fresh install PA and install the mini Gapps (I had prev installed the stock but didnt want all the apps)
Here is where it started to go wrong, Phone would not start ptopery, would get past animation screen but that was it, would then just crash with small date in corner.
Wiped and flashed just the Rom and this also failed.
Wiped and installed 3.99 and this seem to work but then the wizard crashed and I had to power down.
Booted back up into recovery and dirty flashed Beta 3 again and this seemed ok. Flashed Stock Gapps and rebooted.
All apps have installed again, titanium back has been run but I still have no network what so ever.,
If i go into settings, more, vpn, mobile networks I get 'unfortunately settings has stopped'.
I have dirty flashed again but still have same problem.
I cant do a complete wipe and install again as need to get out of the office, however with the prev problems I had I am weary about doing so.
Can anyone shed any light on any of the issues i had at all?
foxguard said:
Ok, I was running PA 4 Beta3 but was having problems with the screen delay so thought I would completly wipe my phone, fresh install PA and install the mini Gapps (I had prev installed the stock but didnt want all the apps)
Here is where it started to go wrong, Phone would not start ptopery, would get past animation screen but that was it, would then just crash with small date in corner.
Wiped and flashed just the Rom and this also failed.
Wiped and installed 3.99 and this seem to work but then the wizard crashed and I had to power down.
Booted back up into recovery and dirty flashed Beta 3 again and this seemed ok. Flashed Stock Gapps and rebooted.
All apps have installed again, titanium back has been run but I still have no network what so ever.,
If i go into settings, more, vpn, mobile networks I get 'unfortunately settings has stopped'.
I have dirty flashed again but still have same problem.
I cant do a complete wipe and install again as need to get out of the office, however with the prev problems I had I am weary about doing so.
Can anyone shed any light on any of the issues i had at all?
Click to expand...
Click to collapse
Sounds like a radio issue. If you are running 3.99, you need the radio for 4.3 which I do believe 3.99 is based on. You need the radio for KitKat when running the new betas.
Sent with my Nexus® 10 minus 3
This is the easiest way to flash a new radio http://forum.xda-developers.com/showthread.php?t=2607221
If you went up to a 4.4 based rom and it changed your radio to .97 or .98 then you'll need to flash back to a .84 or before.
to go back to 4.3.
I think I basically said that. Sometimes I believe in not holding hands and let the guy/gal do some of the, legwork.
Sent with my Nexus® 10 minus 3
Thank you every one. I have reverted back to my recovery and all is well but I don't understand why when I flash the ROM ad gapps it happens. My recovery is the same ROM and gapps. No idea.
Oh well stuck with the screen delay for now!
Sent from my Nexus 4 using Tapatalk
mrhiab said:
This is the easiest way to flash a new radio http://forum.xda-developers.com/showthread.php?t=2607221
If you went up to a 4.4 based rom and it changed your radio to .97 or .98 then you'll need to flash back to a .84 or before.
to go back to 4.3.
Click to expand...
Click to collapse
Hi mate, thanks for this. I have reflashed my phone again and still have the same problem. My baseband is showing as 84 though s that is correct?
EDIT, dont worry a reboot has fixed this issue. Odd.
Thanks again though.
foxguard said:
Hi mate, thanks for this. I have reflashed my phone again and still have the same problem. My baseband is showing as 84 though s that is correct?
EDIT, dont worry a reboot has fixed this issue. Odd.
Thanks again though.
Click to expand...
Click to collapse
Ohh you are having issues with ur network !! Seen people completely losing their Imei during flashing !! Not to scare you but its better to get the imei files backed up !!
Check my post on the below mentioned link
http://forum.xda-developers.com/showpost.php?p=49753344&postcount=11
Hit the thanks button if you find my post useful

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.

Categories

Resources