I tried (succeeded) in downloading and flashing Synergy RLS1 God Mode. everything went well until i just noticed i have no 3g connection? should i recover and reflash and see if it fixes it? or is there something im missing?
(i searched but found nothing useful)
DivineDecay said:
I tried (succeeded) in downloading and flashing Synergy RLS1 God Mode. everything went well until i just noticed i have no 3g connection? should i recover and reflash and see if it fixes it? or is there something im missing?
(i searched but found nothing useful)
Click to expand...
Click to collapse
You have a couple of options, restore and reflash (making sure to wipe your data, cache, and dalvik cache). Or try flashing RLS 1 without god mode again making sure to do a complete wipe.
Sent from my Synergized Freedom Evo.
Or update your PRL/profile and then reboot your phone. Should work and if it doesnt then you can always flash calks latest radios for the EVO through recovery. Make sure to wipe cache and dalvick cache. (Amon_RA 2.3) works the best in my opinion.
Sent from my PC36100 using XDA App
thanks guys. i found My 3g comes on, but i have to leave the phone open for 2-3 min before it finally connect, and then as soon as the screen turns off, it disconnects, and i have to do the same thing again.
Related
Did this get broken by sprint? I get error 67s when I try and tether with ava froyo 3
Sent from my PC36100 using XDA App
You need WiFi Tether version 2.0.5 pre 6
Sent from my FROYO'D EVO using xda App
to get USB tethering working?
Sprint looks to have broken usb tethering as well as wireless tethering. now all tethering seems to need the extra service from sprint. as is. You Can still do both with netarchy's kernal if you are rooted.
every time I have tried to install netarchy's kernal, I get that damn boot loop... (Ava Froyo 3revA) with both clockwork recover and ra recovery...
MalaysianMafia said:
every time I have tried to install netarchy's kernal, I get that damn boot loop... (Ava Froyo 3revA) with both clockwork recover and ra recovery...
Click to expand...
Click to collapse
Did you wipe your cache? That happened to me once. I had a brain fart and didn't wipe my cache.
though i am sure you are you also are using the froyo version of the kernel correct?
if wiped cache and froyo version still causing boot loop let us know.
JUST cache? I wiped dalvik and such too when I've tried it...
MalaysianMafia said:
JUST cache? I wiped dalvik and such too when I've tried it...
Click to expand...
Click to collapse
I'd wipe all three: Data/Factory Reset, cache, and dalvik
If you don't want to lose your apps/screen setups, you can try just the cache and dalvik wipes...but personally I would do all three to leave all doubt out of my mind.
Then I would reflash the kernal and see if that helps. I don't know what else to tell you right off. I was running the same config you have yesterday.
And like he said above. Make sure you have the kernal for 2.2.
Hey guys,
so i was on a plane yestarday and obviously they want you to turn your phone off. I did so and when i landed i tried turning it back on but only to my surprise it would. Was just stuck at the White HTC screen and just kept resetting and doing the same.
Luckily I was able to get into the bootloader and reflash the rom and backup, however, its a pain in the butt to have to do so every time my phone shuts off or I have to shut it off.
Havent tried another custom rom yet, will do so shortly, but just wondering why this is happening? Any advice?
What rom were you on? And make sure to install with a clean install.
i was using calkulins evio rom.
and yes, i did a full factory wipe with cache and dalvik as well....is there all required for a clean install?
hasseye said:
i was using calkulins evio rom.
and yes, i did a full factory wipe with cache and dalvik as well....is there all required for a clean install?
Click to expand...
Click to collapse
You pretty much want to wipe everything but the sd card. So cache, data, dalvik, boot, and system. Then flash your rom and boot it up.
Sent from my hand with XDA Premium installed
I have this same problem with calks rom. Maybe try a different kernel?
Sent from my PC36100 using Tapatalk
Fyi, if you used cwm to do the wipe, this is probably where you failed. Cwm fails to wipe dalvik most times. I have had weird issues on sense roms specially when using cwm. I changed to ra and no wipe problems since.
How do I know this? After so called full wipes using cwm and installing evio most or all of my apps and settings would still be there.
I have confirmed this with many others that have used both recoveries. Ra is nicer anyway.
Real men don't need rom manager anyway.
Sent from my EVO 4G using XDA Premium App
hermanlf said:
Fyi, if you used cwm to do the wipe, this is probably where you failed. Cwm fails to wipe dalvik most times. I have had weird issues on sense roms specially when using cwm. I changed to ra and no wipe problems since.
How do I know this? After so called full wipes using cwm and installing evio most or all of my apps and settings would still be there.
I have confirmed this with many others that have used both recoveries. Ra is nicer anyway.
Real men don't need rom manager anyway.
Sent from my EVO 4G using XDA Premium App
Click to expand...
Click to collapse
I just don't understand why koush dosen't fix this and be done with it. I love that program... I use titanium backups dalvik cleaner anywho just saying that all
I'm having this sort of issue as well. I have wiped many times, gone back to stock, unrooted, even updated the hboot version. Has anyone figured out what exactly may cause this sort of boot loop? Sometimes, my phone just randomly reboots (even on stock default) and gets stuck in a boot loop.
Keeping the battery out for about 5 minutes allows it to boot back up, but I'm getting rather frustrated with it. I can't seem to pinpoint an exact issue. sometimes, it seems my battery is rather warm to the touch, sometimes, it's nice and cool. I've tried sense roms, non-sense, GB, and as I said earlier, stock RUU. Nothing I've done stops the reboots. I took it to the sprint store, and they saw nothing wrong with it. (Of course, it didn't reboot for them. Figures, eh?) I even got 2 alternate batteries. (One was the super big extended life)
Has anyone else had this same issue? I'm at a loss of where to go from here. I've poured over these forums, and the development forums for days. I never had this issue before...it's only started happening in the last week and a half. Keep thinking I must have missed something, but I'm not sure what.
My phone will detect Wifi, and try to connect, but will never connect. It just finds it, goes to "connecting," then "disconnected," then "connecting," then "disconnected," etc.
What did I screw up on my phone? I've tested Wifi using Fresh, CM7, Caulkin's, and the leaked plain gingerbread.
I've flashed 2 different kernels, each has the same result. Not to mention that some of the roms have different kernels already.
I've also downgraded my radio just to see if that would help.
What could I possibly have messed up? I don't get it.
Obviously, I've spent a lot of time like this, and I am, quite honestly, literally insane at this point.
Any help is appreciated.
Later.
Could it be your router that's going bad and not your phone??
Also, try placing a stock sprint rom and go from there
I ran into this as well before with my current ROM Mikfroyo.. the trick for me was just to back up my apps and wipe/reinstall the ROM. If you backup more, be sure to NOT backup the Wifi settings as that may cause the issue to happen again (I've been down this road more than once with my phone because I'm a flashing junkie )
That's the only suggestion I can offer.. sucks but at least for me it fixed my issues with Wifi not connecting.
Good luck!
--edit--
after reading deeper into the OP I guess this might not work as it seems flashing new ROMs didn't help either..
trim81 said:
Could it be your router that's going bad and not your phone??
Also, try placing a stock sprint rom and go from there
Click to expand...
Click to collapse
I don't think so, because at home my wireless printer still works, and I can connect an iPad.
I'll flash a stock rom tonight.
fastamx79 said:
I ran into this as well before with my current ROM Mikfroyo.. the trick for me was just to back up my apps and wipe/reinstall the ROM. If you backup more, be sure to NOT backup the Wifi settings as that may cause the issue to happen again (I've been down this road more than once with my phone because I'm a flashing junkie )
That's the only suggestion I can offer.. sucks but at least for me it fixed my issues with Wifi not connecting.
Click to expand...
Click to collapse
I have been using Titanium backup to restore settings, that is a good point. Maybe tonight I'll re-install the router, remove all apps from the Apps2SD, flash a stock ROM, then manually re-install all of the apps from a market.
Sounds like a good Friday night. Blehhh.....
If your using cwm to flash wipe all 3 times each then when you restore apps do apps only not system data. Somewhere your introducing info back into the rom that's confusing it.did you back up your wimaxx keys before you flashed your radio?
Sent from my PC36100 using XDA Premium App
lambofgod13 said:
did you back up your wimaxx keys before you flashed your radio?
Click to expand...
Click to collapse
No, but cwm and RA both do that for you now, right? Plus, I can still connect to 4G, so the wimax keys should be there.
But that's a question I can't find the answer to- does the radio have anything to do with connecting to WiFi?
Well cwm doesn't do a good job at cleaning dalvik cache. You've got to manualy wipe 3 times to make sure. Your not using rom manager are you? What version of clockeork you using?
Sent from my PC36100 using XDA Premium App
lambofgod13 said:
Well cwm doesn't do a good job at cleaning dalvik cache. You've got to manualy wipe 3 times to make sure. Your not using rom manager are you? What version of clockeork you using?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I use ROM manager. What's wrong with it?
I'm using 3.0.0.5
Don't use rom managet it causes to many problems. Go into recovery and wipe system data facrory reset, then go into advanced and wipe dalvik cache 3 times each then flash your rom. Your issues will go away.
sent from my morse code machine!
You should go into rom manager and flash other recovery re. That's amon re its more stable than cwm.
sent from my morse code machine!
Sounds more like your wireless router is the issue. Just because your other devices connect, doesn't rule out your router. Try to connect to a different wireless router and see if that works.
i am also having this same issue, and i cant find an answer to it.. but i will try giving it a shot with amon ra recovery and manually clearing dalvik cache n data.
Hey Sprockethead try using this recovery http://forum.xda-developers.com/showthread.php?t=1339654, it's known to work for a LOT of people here... Like the others have mentioned I think it might have to do something with not wiping properly... You can still flash your CWM recoveries with this one.
Ok here is a strange thing I can't wrap my head around. I have been rooting and flashing for quite awhile, but have a problem I cant solve....I have a EVO hardware 2 about a year old that has been rooted and running MIUI fine for several months. I recently have been playing with kernels and undervolting. I noticed some random reboots and tried resetting voltages back to normal and flashing diffrent kernels back, but still it locks on bootup or reboots. So I RUU flashed back to stock and everything worked fine, boots good no reboots and temp around 34 deg. nice and stable. Figured all was good re-rooted and boom back to not booting again. I have tried old nand backups that were stable but they do the same thing. Is there some trick to doing a full wipe that I an missing? Also just to mention I recently had problems with the GPS locking on and add the new driver to try and fix it...
Thanks for any ideas....
PS new info...I put a blank card with just the new miui flash on it and reflashed.....it seems to fix the problem...there must be some settings on the card that conrols the cpu settings....will test further and report...may help someone else...
What recovery are ya running?...sounds like its not wiping corectly.....if yur using CWM I would recommend AMON....ALSO.....SUPERWIPE is the way to go....wipes system,data, and boot twice when u flash it....I'm lying in bed and my PC is shut down....u can just google SUPERWIPE ....and for AMON just head over to his thread for his PC36IMG.....BUT IT SOUNDS LIKE YUR RECOVERY ISNT WIPING PROPERLY......would hurt to try em
Sent from my PC36100 using XDA Premium App
If you have Amon Ra, you really don't need those "super wipe" things.
Just wipe all twice and then do cache and dalvik again, separately, and you'll be fine.
Even that's over kill....
HipKat said:
If you have Amon Ra, you really don't need those "super wipe" things.
Just wipe all twice and then do cache and dalvik again, separately, and you'll be fine.
Even that's over kill....
Click to expand...
Click to collapse
Dood I've always wiped ALL and dalv twice....up until a couple of months ago.....ran into a lot of bootloops....BIG TIME....but I figured it wild be a little reassuring for him......also I'm not sure what the other responses he got else where.....al personal preference I guess......have a good one guys
Sent from my PC36100 using XDA Premium App
Hi Guys,
I read through a lot of rebooting threads on here, but none talked about the rebooting issue after a radio update. My EVO NEVER, EVER had a rebooting issue. I just upgraded the radio, and now the phone keeps rebooting nearly IMMEDIATELY, when it loads into the ROM.
Even downgrading to the original radio version I had, the phone was still rebooting.
The rebooting threads don't really offer a solution that worked. Can someone please confirm for me if anything worked for them, minus the replacement phone, cause I can't have that, I got mine off of Craigslist. Thanks for your help and thanks for reading, looking forward to your responses!
Have you tried wiping cache and dalvik cache then fix permission?
I've never had that happen from radios but earlier today my sdext got messed up some how and my phone was doing that and then it just wouldn't boot after a while I did the fix sdext thing in Amon Ra recovery and it fixed my issue not sure if that helps you in any way though.
Sent from my PC36100 using XDA App
linsalata28 said:
Have you tried wiping cache and dalvik cache then fix permission?
I've never had that happen from radios but earlier today my sdext got messed up some how and my phone was doing that and then it just wouldn't boot after a while I did the fix sdext thing in Amon Ra recovery and it fixed my issue not sure if that helps you in any way though.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I haven't tried wiping the data, or the caches, yet. I wanted to be sure of it, before I did that. I did a NANDROID as well, but not sure if that will be any useful IF the fix was clearing the cache.
Any other ideas, guys?
ProFragger said:
I haven't tried wiping the data, or the caches, yet. I wanted to be sure of it, before I did that. I did a NANDROID as well, but not sure if that will be any useful IF the fix was clearing the cache.
Any other ideas, guys?
Click to expand...
Click to collapse
Try just wiping cache and dalvik cache and fix permissions and see if that helps.
FYI you can wipe those caches and no harm will come to your ROM you should always wipe them before you flash anything.
Sent from my PC36100 using XDA App
Did you just flash the radio or did you flash the combo? If you upgraded everything but only downgraded the radio, it could be one of the other components (pri/nv, wimax).
Once you've tried wiping cache/dalvik, try flashing a different radio if you only flashed the radio to begin with, or downgrading everything else if you used the combo zip and are still experiencing reboot issues.
By the way, you can still insure a phone that was purchased somewhere else. You may want to do that in the future.
If none of the suggestions work, it could be something other than the radio. You can always make a backup and do a full wipe to see if that helps - or run an RUU and return to stock if all else fails.
Sent from my Evo + MIUI using Tapatalk!
Some of the radio updates that I have seen posted also indicate that you may need to reflash your kernel after loading the radio update.