So I've recently used ODIN to restore the stock ND8 factory image on my S3 and now it is constantly crashing and then rebooting and I'm not sure the reason. I don't have an issue on a stock rooted rom, or another custom rom just the factory image itself. I do not have an SD card in my phone as I know sometimes they cause issues. The phone is booting up and if I'm fast enough and I keep doing something on it, sometimes it will keep working until I stop using it and sometimes it just crashes anyways and reboots.
If anyone has any other solutions to try or knows how to fix this issue I would appreciate it.
Thanks in advance.
Related
hi all, been following the Epic forums for sometime, finally decided to start getting involved
Im experiencing an issue with EB13. when it first came out I Odined EB13, everything worked great. Since then I have ran into the same issue every time I switch ROMS. I will flash the new rom, about half the time it works great. The other half I get no connectivity at all, and the UI is sluggish. Going into about phone, I see that my baseband is unknown, and my hardware version is unknown.
I can usually get it to connect after re-flashing and re-flashing the rom a few times.
Also, noticed that once I get it to actually connect and I get "bars", I will of course then do a fresh Nandroid, after a full nand backup the issue reappears.
Anyone know what this could be? weird thing is just that its so random. I can get it to work most of the time, just have trouble when switching roms.
Set up:
CWM3.0.0.6/EXT4
Just flashed SyndicateROM today.
EB13 (sometimes)
FIXED
FIXED. all the computers in my home are Macs so odining the modem again is not a quick fix option.
Booted into CWM3 and Fixed Permissions.
Booted up and connected.
Interesting stuff
I've been experiencing the exact same problem as the OP, but for me, running fix permissions in CWM (2.5.1.0) doesn't (always) solve the issue.
It seems to happen anytime I flash a zip from CWM, and goes away randomly (usually after sever flash attempts and modem restores with Odin).
Really hoping someone has an idea what's causing this issue, because it makes flashing things very tedious knowing half the time I'm gonna be stuck with a useless phone until I can get the modem working again.
I'm wondering if it's somehow a hardware issue, since it doesn't seem to affect everybody.
If it helps, I have the stock deodexed EB13 ROM with the Genocide 0.3a kernel.
I'm definately thinking its a cwm issue.. ill even just do a nandroid backup for kicks, reboot and it will do it sometimes.. eventually I might odin back to eb13 and reflash cwm and custom rom and see if I can get it to go away
Sent from my SPH-D700 using XDA App
DrKaotica said:
I'm definately thinking its a cwm issue.. ill even just do a nandroid backup for kicks, reboot and it will do it sometimes.. eventually I might odin back to eb13 and reflash cwm and custom rom and see if I can get it to go away
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Let me know if that works for you, because it happens to me all the time, and it's really annoying.
There also doesn't seem to be a simple way of fixing it.
Seems to just randomly go away as suddenly as it comes on.
Okay, so I just odined back to stock EB13 and I still have modem issues.
Currently going all the way back to DI18 to see if that fixes things, but is it safe to assume it's a hardware issue if even Odin doesn't fix it?
Okay, so the unknown baseband issue is back for me, and I seem to have made some headway on what causes it.
I had just tried to initiate a ROM backup in ROM Manager, but it hung while rebooting into CWM (on the Samsung Boot Logo).
I think I might have been doing something with ROM Manager last time it happened as well.
Can anyone who knows more about this stuff than I do think of a reason it'd happen when using ROM Manager?
I'd very much like to nip this issue for good, because it's making it hard to justify using CWM/root if I'm gonna keep losing the phone part of my phone.
Can I bump this? My battery died, and when I turned it back on, I have the unknown baseband, unknown hardware problem. I've been googling all night, and haven't found a solution.
I have been running ERA Legendary v3 on the EI22 Modem for a few weeks with ACS Recovery that I've had installed since it came out.
Any help would be awesome.
---------- Post added at 07:28 AM ---------- Previous post was at 07:17 AM ----------
And I've tried flashing modems/roms and odining modems/roms. Even Heimdalling modems/roms. No luck. I've mainly tried ec05 and up. I will try older ones right now, if I can find them.
since updating to 4.2.2 Liquid rom i am unable to downgrade to any version below that without my phone switching off after 5 secs and me having to reboot back in..
any idea?? seems like by upgrading to 4.2.2 something has been upgraded and anything below that, even 4.2.1 just refuses to work and switches itself off.
and doing it through odin with stock rom even fails to stop the phone switching off..it installs fine and then proceeds to promptly switch off, but the minute I put the custom 4.2.2 rom back on...its fine again and doesnt switch off, which makes me think something has been upgraded along the way and anything other than 4.2.2 now will not work correctly on my phone..
How can i get back down to 4.2.1 etc.. is it baseband or something? This makes me think that all others on here with their phones switching off have potentially done the same thing as me? If you have any feedback is welcome...
Also if you managed to fix your shutting down after 5 secs and having to reboot issue issue I would love to know how this was achieved
any help is greatly appreciated as always
Do a mega wipe. Then flash stock rom.
this is XXXDDDAAA
OK mega wipe?? can you explain this to me and how to do that??
I currently have the stock rom for the UK 4.1.1
N7100XXALJ3_N7100OXXALJ4_BTU
so even though I can install this it still switches itself off after 5 secs and I have to reboot.. i am now at my wits end and will try anything to get my phone back to stock and actually working...
so any help is greatly appreciated....
http://forum.xda-developers.com/showthread.php?t=1983489.
this is XXXDDDAAA
Thanks for that...however gutted..it didnt fix my problem...
Then flash stock rom and fully unroot it.
Then go to Samsung store.
this is XXXDDDAAA
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 have read around regarding this problem without luck, and hope that someone can advise if I have missed anything.
I used to use this phone and as I liked to tweak it was running a custom rom (think it was Wanams). Anyway I got an upgrade ages ago, and my wife carried on using the phone for a while. As she just needs a standard rom I recently decided to factory reset and use Odin to flash the newest stock rom (N7100XXUFNE1 - UK). This is when the problems started. Initially the Wifi wouldn't come on, but after factory resetting and using the Samsung Updater in Kies I finally managed to get Wifi back. Then, while setting it up and installing apps from the Play store it started freezing and had to be rebooted every 5 or 10 mins. Finally after doing this a couple of times, all the apps were installed and after leaving it to "settle" it seemed to be better. Now however, 2 or 3 times a day, when playing games or using other apps, it will just reboot.
What I have tried is:
* I have tried clearing cache through the stock recovery
* Tried a number of Factory Resets
* After reading about the SDS problem I have tried running the "dummy file generator" to fill the internal memory and this completes ok. I guess this means that although I have memory that is/was susceptible I applied the original SDS fix early enough with the custom rom that all the memory is still ok?
As I have the newest bootloader I can't downgrade that, but as I don't care about triggering Knox I was thinking of rooting and installing a custom rom to see if any of the other Kernels help?
Has anyone got any idea's what could be causing this and what I can do to fix it?
Thanks.
This is an extremely strange problem that I've never encountered before. The issue is whenever I shut down my device, it wont ever boot back up again. The way I've been getting around this issue is going into my TWRP recovery and backing up/restoring the same backup and that fixes it. That has been becoming a nuisance so I've decided to come here for help. I did a few Google searches so I'm sorry if someone else has posted this issue. I am currently using the T989D (The T989D Is the Canadian version of the T989) Running CM11 (4.3.1) And TWRP Recovery.
Bump. Still having the issue. Wiped Data + Cache. The issue is still reoccurring.