Hello!
Already few times I've tried to upgrade. From EG31 to EK02 and EL13. With EG31 everything works just fine but after upgrading I'm starting to get random reboots and device is hitting.
I've tried everything and only stocks Rom.
Can somebody give me some advice how can I figure out what causing reboots and hitting?
Maybe somebody can give some other advice? Because I'm trying to upgrade for a long time and can't.
Please, help me, guys? Is it only me not so lucky?
Please?
Use the EL13 ODIN tar in my signature. Use the one that resets your user data. (backup your data first)
If it is still happening, post back here.
Related
Almost every text I send fails.. I have full bars, go to send a text and then after a while the text fails to send..(they still end up receiving it anyway,but its a huge issue because the phone constantly alerts that my text failed). I can make calls just fine. Is anyone else having this problem with this ROM? IS there a fix? I'm 99% sure its installed just fine and my hardware is impeccable.
I had this before on ee odin then reflash to bonsai it should fix it. Btw i dont have this on bonsai
Sent from my SPH-D700 using XDA App
If you're using gingerbread theme, try this.
If not, do what the post says above and it should fix the problem. If you're wanting to try something easier first, simply try reflashing the ROM. But I think it does occur to many people that have a problem during switching Modems in Odin.
The same thing is happening to me, but Im not using a custom rom. I'm using stock D118
I had an issue with bonsai where my messages would stick on "sending". I rebooted the phone and the problem hasnt come back until i flashed v2.0 of bonsai..i rebooted again and all is well. for safety measures i reflashed the dk28 modem...i replied to your post in the bonsai thread and said that you can also odin the DI18 modem which some people have said works better than DK28 and the internet speeds are much better..
hmm darn, well i just restored to the point before i flashed bonsai and flashed nebula 1.0.7 instead and its working perfectly
Having the same radio problems with this one as Midnight v 3.1, I've tested both and can hardly send a text to save my life. I go to send it times out and fails then i get the error message did not send, yet they still recieve it. Its frustrating because I really wanted to run either of those two. Not sure why but these two must be similar causing the same problem. (in midnight theres a huge thanks to bonsai dev's so just assuming its a similar Rom)
coke32 said:
Having the same radio problems with this one as Midnight v 3.1, I've tested both and can hardly send a text to save my life. I go to send it times out and fails then i get the error message did not send, yet they still recieve it. Its frustrating because I really wanted to run either of those two. Not sure why but these two must be similar causing the same problem. (in midnight theres a huge thanks to bonsai dev's so just assuming its a similar Rom)
Click to expand...
Click to collapse
I've been restoring to the point of when i just flashed stock dk28 and reflashing both these roms and still every other text fails to send. should i try to odin back to stock dk28 and reroot? does that do a more effective wipe then restoring back to stock dk28 with root? (because i made a backup right after i did the oneclickrootcw3)
well i odin'd back to stock and rerooted and reflashed midnight and im still failing every other text Im a heavy texter and like to go fast and often when im going.. when every other message is failing it becomes impossible to talk to someone. calls work fine.
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.
I rooted my Epic 4G Touch last night and now my wi-fi isnt working. (Everything else is working well and I get very nice benchmark scores) I will try to turn on wifi, and it looks like it turns on but then it shuts off by itself a couple seconds later. I've tried a couple different kernels(zedomax, lostkernel). Also, maybe this is a related issue, but I downloaded WiFi Tether and when I start it, a few errors show up in the log (configuring softap, starting softap, activating WiFi interface--all failed). Not sure where to go from here. Couldn't find anything helpful in any other forums. I did try installing the EL26 modem but that didnt fix the issue.
Any ideas?
Sometimes this happens going between the recompiled kernels and stock.
I would backup your data and start from scratch by ODIN flashing EG30 or EK02 (from my signature) and do a ##786# reset per the instructions in those posts.
Make sure your running the same kernel with the same build. ie EL13 ROM with EL13 Kernel
sfhub said:
Sometimes this happens going between the recompiled kernels and stock.
I would backup your data and start from scratch by ODIN flashing EG30 or EK02 (from my signature) and do a ##786# reset per the instructions in those posts.
Click to expand...
Click to collapse
Couldn't I just wipe and then flash Calkulin's EL13 rom? or is flashing to stock different? Sorry, I'm new to all this.
You are welcome to try what you want. I like to start with pure stock and reset everything to see if that works, then slowly introduce changes.
cant seem to find one....
anyone know if there is one?
Is this what your looking for?
http://www.theandroidsoul.com/clockworkmod-recovery-for-epic-4g-touch-el29-firmware/
http://forum.xda-developers.com/showpost.php?p=21135009&postcount=2
Look at a4.
Thank you both. highly appreciated.
follow up question...
I just went back to fix the gps issue. Worked like a charm, however.... I keep getting a "sorry, maps has stopped working" message. It still works though. Any idea what may cause this?
Im on mijjz ics blend fc14 v2.3
EL29 modem
FC07 kernel with recovery
Also, If i flash the FC14 Modem, would it undo the gps fix?
edit: ok i did lose maps and gps lock.... any ideas?
Any insight is greatly appreciated.
After successfully installing Alpha 1 and 2 with no problems, Alpha 3 will not let me connect to the Sprint network. On boot up the phone is in airplane mode, and when switched off, it still will not give me any signal. Any help would be greatly appreciated as this is my only phone. Lol. Also, the lock screen sometimes takes ages to light up?
Also, if no one knows how to fix this, can someone point me in the right direction to flashing back to a completely stock rom?
Stock rom.
http://forum.xda-developers.com/showthread.php?t=1433101
GO back to el26/29 and fresh install
Odin to EL26, update Profile and PRL, and then come back. It may also help to switch around your Modem.
Same thing just happened to me.
I just went and updated my profile and it started working again. Not recommending doing anything but it worked for me.