hey there,
I flashed some custom roms months ago and everything went fine.
Now no matter what roms I take in Exynos Section, Im getting bootloops.
Installing is fine i dont get any error. I wipe everything from cache, data, dlvik, factory reset and I still get the bootloops. It happened on 3 different roms now.
Usually a full wipe fixed the problem but now nothing. I can go back to my old custom rom but cant flash any new.
Has this happened to anyone? got a fix for it?
Thanks
Running on lastest TWRP
IIIPowerIII said:
hey there,
I flashed some custom roms months ago and everything went fine.
Now no matter what roms I take in Exynos Section, Im getting bootloops.
Installing is fine i dont get any error. I wipe everything from cache, data, dlvik, factory reset and I still get the bootloops. It happened on 3 different roms now.
Usually a full wipe fixed the problem but now nothing. I can go back to my old custom rom but cant flash any new.
Has this happened to anyone? got a fix for it?
Thanks
Running on lastest TWRP
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2507403
here you go buddy flash this after flashing a rom all should be good
Related
ok so i was trying to get LTE option back on my phone and flashed the stock rom twice. didnt work. thought it could need a factory reset. didnt fix it. tried flashing stock another 2 times. still no LTE.
flashed TWRP recovery did a wipe inc system, data and cache. flashed stock in odin.
now wont boot up. gets stuck at the S4 logo.
trying again to flash the stock rom in odin will post soon if it starts up. but if not what do I do?
also how come i couldnt get LTE back in mobile networks?
only had the phone for 2 days LOL
came from the s2 and s3 so have a fair bit of knowledge about these.
thanks
EDIT: NOPE still wont boot
have you tried to wipe data/factory reset after odin i suppose it won't if not also try a Rom with another build either a complete stock on odin or a pre rooted one
ok so after a hour of playing with it i fixed it. I used wipe data factory reset and it just booted up lol.
back on omega rom now
Hello,
I've got a problem with my gt-i9505.
I've managed to root the phone and install TWRP.
So i decided to install CM10.2 (21-08) and the right gapps for it.
Everything worked very good and I couldn't be happier.
All my apps were back and it was ready to use it!
I turned off the phone and went to sleep.
The next day i turned it on and it got stuck on the bootscreen (not the CM bootscreen, but the SAMSUNG GALAXY S4 bootscreen).
So I tried to do factory reset and install rom again, gapps again, afterwards again wipe dalvik and cache.
But i keep having the same problem. Right now after flashing the rom it doesn't even boot up the first time.
I also tried going back to 10.1, but same problem.
I don't know what to do, i just got my s4. Really hope i can fix it.
Luckily i can enter the recovery. But i didn't do a backup or anything.
Does anyone have any tips on how to get it working again?
ricomana said:
Hello,
I've got a problem with my gt-i9505.
I've managed to root the phone and install TWRP.
So i decided to install CM10.2 (21-08) and the right gapps for it.
Everything worked very good and I couldn't be happier.
All my apps were back and it was ready to use it!
I turned off the phone and went to sleep.
The next day i turned it on and it got stuck on the bootscreen (not the CM bootscreen, but the SAMSUNG GALAXY S4 bootscreen).
So I tried to do factory reset and install rom again, gapps again, afterwards again wipe dalvik and cache.
But i keep having the same problem. Right now after flashing the rom it doesn't even boot up the first time.
I also tried going back to 10.1, but same problem.
I don't know what to do, i just got my s4. Really hope i can fix it.
Luckily i can enter the recovery. But i didn't do a backup or anything.
Does anyone have any tips on how to get it working again?
Click to expand...
Click to collapse
Hi,
Look HERE
Put everything back to stock then, try again.
I found some 10.2 ROMS do not like rebooting,and just hang.
Remove the battery and try again normally worked.
malybru said:
Hi,
Look HERE
Put everything back to stock then, try again.
I found some 10.2 ROMS do not like rebooting,and just hang.
Remove the battery and try again normally worked.
Click to expand...
Click to collapse
Thanks for replying
I followed the instructions and succesfully installed the official stock rom for my device and region.
But it's still stuck at the samsung boot screen.
And now i can't boot into TWRP anymore either, is that correct?
After that I flashed with the .pit file. But still stuck on bootscreen.
Is there any other way to solve this problem?
idgaf about custom roms or CM10.2 anymore, i just want my phone to work.
Wether it's with custom or with stock firmware.
Really hope I didn't break my phone. :crying:
EDIT:
I wiped cache after flashing, but no data wipe/factory reset. That did the trick.
God i can't be happier my phone finally works again. Now i'm scared to flash a custom rom again. I think i need to install TWRP or CWM again too I'll just wait for now.
Hi All,
I'm having an issue with my G2. I've been running the CM11 nightlies for a while now, they've been pretty decent.
I decided to flash the newest Snapshot today when I saw it pop up on my update list. As soon as I booted, I got the error "Unfortunately, the process com.android.phone has stopped".
This happened yesterday, so I booted into recovery, cleared cash, reinstalled the rom, cleared cache again, reinstalled gapps, cleared cache again, and it worked. Now I'm not getting so lucky. Anyone have any ideas on how to fix this? I'm really hoping this isn't going to be an issue with every CM nightly moving forward.
The best solution I could find seems to be specific to HTC phones, which involves reinstalling the boot.img. I don't think that applies to us, but if it does, how can I do that.
Thanks for your help.
EtherBoo said:
Hi All,
I'm having an issue with my G2. I've been running the CM11 nightlies for a while now, they've been pretty decent.
I decided to flash the newest Snapshot today when I saw it pop up on my update list. As soon as I booted, I got the error "Unfortunately, the process com.android.phone has stopped".
This happened yesterday, so I booted into recovery, cleared cash, reinstalled the rom, cleared cache again, reinstalled gapps, cleared cache again, and it worked. Now I'm not getting so lucky. Anyone have any ideas on how to fix this? I'm really hoping this isn't going to be an issue with every CM nightly moving forward.
The best solution I could find seems to be specific to HTC phones, which involves reinstalling the boot.img. I don't think that applies to us, but if it does, how can I do that.
Thanks for your help.
Click to expand...
Click to collapse
You've done a clean flash? Meaning you wiped Dalvik, Cache, System, Factory reset? I usually erase twice and then install CM and then GAPPS then restart the phone (Don't install custom kernel) some custom kernels are having trouble because looks like they updates some things in their kernels.
xxxrichievxxx said:
You've done a clean flash? Meaning you wiped Dalvik, Cache, System, Factory reset? I usually erase twice and then install CM and then GAPPS then restart the phone (Don't install custom kernel) some custom kernels are having trouble because looks like they updates some things in their kernels.
Click to expand...
Click to collapse
Thank you.
After some more digging, I had the idea to check the development thread of the CM ROM here. Apparently, a few other users have had the same issue.
It turns out, the newest version of CM needs to be cleanly installed, a dirty flash won't work. I just did a wipe and it's now downloading all my apps and reinstalling.
*sigh* such a pain, but whatever. Could be worse.
EtherBoo said:
Thank you.
After some more digging, I had the idea to check the development thread of the CM ROM here. Apparently, a few other users have had the same issue.
It turns out, the newest version of CM needs to be cleanly installed, a dirty flash won't work. I just did a wipe and it's now downloading all my apps and reinstalling.
*sigh* such a pain, but whatever. Could be worse.
Click to expand...
Click to collapse
Yeah it can be such a pain, I flashed nightlies when they sounded like they fixed an important issue (it'd be every other day) and I flashed clean all the time. Now im just going to stick to CM11 M4 until the next milestone.
try changin network type to GLOBAL.
I have rooted my phone and its been months now. Have used different roms like gummy, Nameless, Mahdi etc. Recently I had Nameless rom and 3 days back, my phone started freezing when the screen timed out and also froze when there was no sound. I updated the rom but still faced the same problem. Changed to Mahdi but same problem again. Finally I went back to gummy and I face same problem here too. I have done everything except unrooting and going back to Samsung rom.
Pls help me. I cannot understand what is wrong with my phone.
Sid014 said:
I have rooted my phone and its been months now. Have used different roms like gummy, Nameless, Mahdi etc. Recently I had Nameless rom and 3 days back, my phone started freezing when the screen timed out and also froze when there was no sound. I updated the rom but still faced the same problem. Changed to Mahdi but same problem again. Finally I went back to gummy and I face same problem here too. I have done everything except unrooting and going back to Samsung rom.
Pls help me. I cannot understand what is wrong with my phone.
Click to expand...
Click to collapse
Hi,
Most of this problems come from flashing , did you full wipe / clear dalvik and cache before installing rom?
MAX 404 said:
Hi,
Most of this problems come from flashing , did you full wipe / clear dalvik and cache before installing rom?
Click to expand...
Click to collapse
yes when i updated my nameless rom to a newer version, i did a full wipe cache and dalvik. this problem started when i upgraded to nameless from gummy. it was working fine but 2-3 days back this thing started.
Sid014 said:
yes when i updated my nameless rom to a newer version, i did a full wipe cache and dalvik. this problem started when i upgraded to nameless from gummy. it was working fine but 2-3 days back this thing started.
Click to expand...
Click to collapse
Hi ,
Did work fine for 2-3 days? maybe something you installed or restore from you back up.
I would flash rom again No wipe and see how it works , if is working fine i will restore only apps ( not system data) one by one and see if you find the culprit
1430
MAX 404 said:
Hi ,
Did work fine for 2-3 days? maybe something you installed or restore from you back up.
I would flash rom again No wipe and see how it works , if is working fine i will restore only apps ( not system data) one by one and see if you find the culprit
Click to expand...
Click to collapse
4 days back I installed Nameless updated version and flashed it by wiping data cache and dalvik. I m guessing this problem started after installing the Nameless version. But now I'm off Nameless. I'm back to gummy and I just found that my sounds r not working well and I can't speak or hear when I receive or make a call. Should I just unroot my phone and get the stock firmware? Doing this will it get the phone back to normal?
Sid014 said:
4 days back I installed Nameless updated version and flashed it by wiping data cache and dalvik. I m guessing this problem started after installing the Nameless version. But now I'm off Nameless. I'm back to gummy and I just found that my sounds r not working well and I can't speak or hear when I receive or make a call. Should I just unroot my phone and get the stock firmware? Doing this will it get the phone back to normal?
Click to expand...
Click to collapse
Flashing stock is an option but before that
I have Philz touch
Make a nandroid back up and copy it with the rom you want to use in your external SD , copy all your music , data , pictures from the internal SD to the external SD
Wipe data / factory reset
Wipe Cache
Wipe Dalvick
Mounts and Storage / format /data and /data /media (/sdcard) to clean any possible leftover file from any other rom
Now flash your rom from Sdcard1
If does not work go back to stock a re start all over...
MAX 404 said:
Flashing stock is an option but before that
I have Philz touch
Make a nandroid back up and copy it with the rom you want to use in your external SD , copy all your music , data , pictures from the internal SD to the external SD
Wipe data / factory reset
Wipe Cache
Wipe Dalvick
Mounts and Storage / format /data and /data /media (/sdcard) to clean any possible leftover file from any other rom
Now flash your rom from Sdcard1
If does not work go back to stock a re start all over...
Click to expand...
Click to collapse
Thank you so much for the help. I will try doing this, if it works well n good or else I will unroot n start over. It was great talking to u.
Thanks a ton.
Hey guys,
so I recently flashed the Ressurection Remix ROM v5.6.0 and all was working fine until today the touch screen decided to stop working. I couldn't unlock the phone so I tried rebooting it and now it's stuck on the boot logo screen. I can access TWRP and the touch screen works fine so I think the ROM has an issue of some kind? Just wondering if anybody else has experienced a similar issue with this ROM at all? The phone is SM-G900I and I flashed the kltedv ROM onto it. As I said it worked fine for a couple of days then all of a sudden it decides to stop working
Any and all help is appreciated
Did you do a clean flash? If not, try a clean flash or installing again. Also, try clearing your cache and dalvik
Well I did a factory restore using TWRP before flashing the rom on and then cleared Cache and Davlik after installing (as per developer recommendation) and it was fine for a couple of days which is what's stumping me! :S