I'm having some trouble and hopefully someone can help. I broke my nexus 4 and Im back to my s2. I had to replace the digitizer and screen and since then I've had the issue. I never had this issue until recently. The ROM will download fine, but will not install, I'm stuck on Slimrom 3.1.0 official. Some apps won't install or update either. I keep getting error "-24". Anyone have any ideas?
coolguyjosh said:
I'm having some trouble and hopefully someone can help. I broke my nexus 4 and Im back to my s2. I had to replace the digitizer and screen and since then I've had the issue. I never had this issue until recently. The ROM will download fine, but will not install, I'm stuck on Slimrom 3.1.0 official. Some apps won't install or update either. I keep getting error "-24". Anyone have any ideas?
Click to expand...
Click to collapse
did you fix it? ive had the error 24 problem when restoring app data, that shouldnt affect flashing a new rom -so long as you wipe everything first then reboot recovery- also that should clear the data/data folders
Related
I have never had any problems updating roms before and I have been using XenonHD for a long time. I've been trying to update to the 4.2.1 and it will not make it past the boot screen at all. It's driving me crazy! I have soft-bricked this phone 4 times trying this update. The 4.2.1 CyanogenMod 10 - Nightly worked perfectly for me and I don't know what else to try to get this update to work. Anyone else having these issues??
I have the Verizon Galaxy Nexus let me know if any more info is needed.
msimsi10 said:
I have never had any problems updating roms before and I have been using XenonHD for a long time. I've been trying to update to the 4.2.1 and it will not make it past the boot screen at all. It's driving me crazy! I have soft-bricked this phone 4 times trying this update. The 4.2.1 CyanogenMod 10 - Nightly worked perfectly for me and I don't know what else to try to get this update to work. Anyone else having these issues??
I have the Verizon Galaxy Nexus let me know if any more info is needed.
Click to expand...
Click to collapse
Chances are it could be a corrupt download. This does happen from time to time. I updated with no problem. I would suggest to redownload the ROM again and then make a nandroid. Then reboot to recovery and do a full wipe of cache system factory and davlik. Do each twice to be sure. Try to re flash again and see what happens. Good Luck.
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).
Here is my problem on 4.3 roms, i have no trouble installing them and the load up perfectly but after i do a restart i cant get past the boot screen. It does it on all 4.3 roms, i have the latest twrp recovery latest modem and stuff everything is up to date only have this problem on 4.3 ive formatted the internal storage numerous times and always followed op instructions. i cant find anyone else with this problem any help is appreciated tia
The only time I had this issue was after I changed font in Rom Toolbox. How are you wiping?
sent from my GS3 running Illusion4.3
joeyhdownsouth said:
The only time I had this issue was after I changed font in Rom Toolbox. How are you wiping?
sent from my GS3 running Illusion4.3
Click to expand...
Click to collapse
im using twrp first i tried to factory reset, caches that didnt work i formated internal storage same problem everything works great untill i restart the phone then wont go past boot screen. like its not reading the internal drive even did fix permisions and wiped caches after install. Also i used the updated su to flash after still problems, beyond me no problems with older ones or tw just the 4.3 roms
I, also, am having this very same issue. I'm honestly surprised that noone else seems to have run across this issue.
Installing is never an issue, running is never a problem, but if I ever reboot, if a ROM reboots itself, I'm left stuck at the GalaxyS4 splash screen, and the only way out it to Wipe everything and reinstall.
I see youre posting from an S3, I am using an AT&T S4.
Clearly, the issue is related to 4.3...
I had that problem with an unofficial build. But that was a bad download. Do you have new phones? The mount points are different on the newer sg3's. There's a thread with a fix for that
i had that problem. for some reason it locks your recovery and internal storage. you have to wipe it and install a rom via odin to work again. thats why im staying away from 4.3
i got my phone last december so its not real new, guess Ill just stay away from 4.3 roms. my recovery never got locked it just wont boot back up after restart. thanks for all the ideas
I did some searching, and found other people having issues with their Galaxy S3 rebooting randomly, but they were having that issue with CM 11. Since I'm still on 10.2, though, the methods that they suggest (mainly installing the updated gapps for CM 11) won't work.
Heres's the background info:
I'm on Sprint, and have been having issues with LTE reception ever since I switched from Touch Wiz to CM back in October. The issue started a couple weeks ago when I found out that the MK3 modem was available. I was still on MD4, and having issues with LTE reception, I thought this new modem would help. I downloaded an install zip file I found on this site and used CWM to install it. That same day I also found out about an updated apns-config.xml file that had helped out other people that used Sprint/Ting with LTE reception. I found that file here (I'm still considerd a new user, so replace _ with a period):
help_ting_com/entries/23423026
The install zip that I downloaded from that site didn't work, so I backed up the original apns-config.xml, and manually replaced it with the new one. I had to change permissions on a couple folders in order to replace it, too.
That day is when the random reboots started happening. I've since reverted back to the MD4 modem, and have also reverted to a backup of the old apns-conf.xml. I've also changed the permissions to the system and system/etc folders to what they were before, as well. The random reboots keep happening, though.
Any help would be amazing.
cbellk said:
I did some searching, and found other people having issues with their Galaxy S3 rebooting randomly, but they were having that issue with CM 11. Since I'm still on 10.2, though, the methods that they suggest (mainly installing the updated gapps for CM 11) won't work.
Heres's the background info:
I'm on Sprint, and have been having issues with LTE reception ever since I switched from Touch Wiz to CM back in October. The issue started a couple weeks ago when I found out that the MK3 modem was available. I was still on MD4, and having issues with LTE reception, I thought this new modem would help. I downloaded an install zip file I found on this site and used CWM to install it. That same day I also found out about an updated apns-config.xml file that had helped out other people that used Sprint/Ting with LTE reception. I found that file here (I'm still considerd a new user, so replace _ with a period):
help_ting_com/entries/23423026
The install zip that I downloaded from that site didn't work, so I backed up the original apns-config.xml, and manually replaced it with the new one. I had to change permissions on a couple folders in order to replace it, too.
That day is when the random reboots started happening. I've since reverted back to the MD4 modem, and have also reverted to a backup of the old apns-conf.xml. I've also changed the permissions to the system and system/etc folders to what they were before, as well. The random reboots keep happening, though.
Any help would be amazing.
Click to expand...
Click to collapse
When I 1st flashed a cm11 based rom, I had random reboots. I solved the problem by changing kernel governor from interactive to on demand. I have not had a single reboot in months. All phones are built differently though. I've had mine since they 1st came out.
sent from my GS3
Jessooca said:
Does your phone get to the Samsung logo and reboot?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Nope, it's the CM logo.
joeyhdownsouth said:
When I 1st flashed a cm11 based rom, I had random reboots. I solved the problem by changing kernel governor from interactive to on demand. I have not had a single reboot in months. All phones are built differently though. I've had mine since they 1st came out.
sent from my GS3
Click to expand...
Click to collapse
Thanks. I tried this, and it didn't seem to work. Phone's still randomly rebooting. I'm on 10.2, btw. Haven't moved to 11 yet.
Jessooca said:
The best way to truly fix your issue is to start back over at square 1... Odin it back to stock with the tar or MD5 file. The last thing you want to do is make things worse trying too many things.
If you can get back into recovery wipe everything, (but not your Sd card ) as long as you've got a Rom on your Sd card to flash. Don't flash the same rom again, your issue could be a number of things.
- If you made a backup before flashing then revert back to it. Then try to download the rom again, or if you can download the latest slimkat on another pc and copy it to your sd card it's small a quick download and it will get you back up and running.
That is, if you don't feel like using Odin.
Click to expand...
Click to collapse
So I wiped, and started over, and then restored data, but the random reboots are still happening. Should I not have restored data? I'd like to avoid losing everything if I could.
cbellk said:
So I wiped, and started over, and then restored data, but the random reboots are still happening. Should I not have restored data? I'd like to avoid losing everything if I could.
Click to expand...
Click to collapse
Data restore could very well be the culprit.
sent from my GS3
joeyhdownsouth said:
Data restore could very well be the culprit.
sent from my GS3
Click to expand...
Click to collapse
So I'd have to start from scratch? Is there any way I could keep my data?
Good afternoon everyone.
I have a huge problem. When I got my OP one back in 2014 I flashed it, installed CWM and CM and later switched to LineageOS. Everything worked fine until today. For some reason, after I installed lineage-18.1-20210415-nightly-bacon-signed.zip, my phone is now booting but after a while, while still booting it shuts itself down and restarts into recovery mode!? Does anyone know how to fix this? Your help is highly appreciated. Thank you and stay safe.
EDIT: So far I wiped user data and dalvik cache but nothing seems to work. Is there anyway to fix this without loosing all data/apps on my phone?
AnotherStupidUser said:
Good afternoon everyone.
I have a huge problem. When I got my OP one back in 2014 I flashed it, installed CWM and CM and later switched to LineageOS. Everything worked fine until today. For some reason, after I installed lineage-18.1-20210415-nightly-bacon-signed.zip, my phone is now booting but after a while, while still booting it shuts itself down and restarts into recovery mode!? Does anyone know how to fix this? Your help is highly appreciated. Thank you and stay safe.
EDIT: So far I wiped user data and dalvik cache but nothing seems to work. Is there anyway to fix this without loosing all data/apps on my phone?
Click to expand...
Click to collapse
You already lost apps by wiping data, but you still have your photos.
If you had GApps installed before android version upgrade, you now need to flash android 11 GApps. Wiki.lineageos.org tells you what and how.
Thank you for your help. Surprisingly for some reason I found a work around as the unofficial GApps didn't work as well. I wiped data again, so the apps were gone (it took me 3 hours to restore that), but all files were still there and I flashed back to 17.1 with GApps and it worked. Phone is working same way as before. Guess I will wait a LOOOOOOOONG time now until I will try 18.1 again. But again thank you