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.
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.
First Android phone, so I still getting up to speed so hoping someone could answer a couple quick questions. I'll start with the questions and then give the history.
1) How do you determine what ROM you have installed?
2) Any ideas why 4G won't connect? Is there any way to troubleshoot this?
3) Is there anyway to tether on 4G?
So I dove right in after purchasing this phone and flashed a ROM (Zedomax) so I could tether. After installing this ROM my battery life went down the drain and it wouldn't hold a charge for more than 6 hours.
So then I flashed the EG30 stock kernel and my battery life returned to normal. Still wanting to tether I tried another ROM (don't remember which one). This ROM had the same battery issues so I once again flashed the stock kernel back to my phone.
So now my battery life is great, but 4g won't connect (i'm in NYC) for a few days now. I've tried pulling battery, want what not to no success.
I believe I am running the stock kernel, but to my surprise I still have root access. No triangle on the home screen and ODIN says I'm using the Samsung Official binary.
Just to clarify, you are flashing kernels, not ROMs. Zedomax is a kernel, EG30 is a kernel, etc. You can find your current kernel version under Settings > About phone > Kernel version.
Also as an FYI, I wouldn't be going all willy nilly flashing kernels that you can't remember the name of. I'd have to imagine that's a good way to possibly brick your phone or have problems like you are with 4G.
I'm no expert on this stuff by any means but I'd probably recommend flashing Bubby's stock kernel or chris41g's version of it that is packaged up with CWM. These will get you back to the stock kernel (assuming you're not there already) and probably get your 4G working. Otherwise you probably need to update your PRL or something along those lines. Someone who actually knows more about this stuff (i.e. not me) may have a better suggestion for you.
Thanks.
Kernel version is 2.6.35.7-SPH-D710.EG30-CL435734
Is that stock?
walkingcrow said:
Thanks.
Kernel version is 2.6.35.7-SPH-D710.EG30-CL435734
Is that stock?
Click to expand...
Click to collapse
Yep! 10 char
Cool.
So flashing to chris41g's or Bubby's kernels probably won't help me. I'll go searching to figure out how to update my PRL but if anyone has any other ideas I'd be grateful.
Also does anyone know if it is possible to tether over 4G? I was never able to connect unless I turned off 4g before tethering.
It is working again. I started over and flashed Stock-EG30.tar and all is good now.
Out of curiosity did you update your system profile after you flashed? I think it's recommended to do that every time you flash a new kernel.
Settings > About phone > System updates then choose update profile.
Edit - Ahh cool looks like you got it worked out. Cheers!
Nope, I never updated my system profile. That could of been a fix....
Interestingly enough, I was retracing my steps after going stock, after each step I checked 4G connectivity. I lost 4G after enabling AdAway. So I disabled (each change requires a reboot) and got 4G back after the boot. I enabled it again hoping to be able to isolate the issue but after that next reboot I got 4G access with AdAway enabled.
Can't say it is AdAway, but after toggling it, I got 4G back.
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
I recently got a new Epic 4G Tough after my previous one **** the bed. I rooted it again and put CM10 on it, but I noticed that my data is ****ty at best. I remember this being a problem on my last phone, where I ran the FF18 or EL27 tempboot to update the PRL and profile and then boot back into CM. I went to do it again, but I'm having trouble. I'm able to tempboot EL27 (FF18 wasn't working for me) and update the PRL and profile. The problem is that afterwards, when I shut down my phone and turn it back on again (there's no reboot option when I hold down power), it reboots into recovery, and the only way to get it back into CM is to restore a backup. Can anyone help me out with what I'm doing wrong? Thanks!
I have been using the rom since beta... Today my wifi started to give me trouble... It will not stay turn itself on and wont connect to anything. I tried full wiping and doing a clean instal of the new version and it is still giving me the same problem.. could this be a hardware issue?
If your wife is giving you trouble then you need to set her straight, lol.
Seriously though, have you tried reflashing the ROM, or flashed back to stock? That would be my first step to troubleshoot it. Try going into wifi settings and see what options are checked first.