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.
Related
Trying to get to the bottom of my kernel issues and I just noticed that instead of getting a # in adb, I get a /#. Anyone know what that means?
I'm guessing you're using netarchy kernel and bash. RTFM on custom shell prompts.
I'm using KingX and I don't know what bash is. Anyway, I just tried adb again and it's back to a #, so that's a non issue now. I still can't figure out why I can't flash ANY of the new kernels without causing a bootloop. KingX 7 and 8, netarchy 4.1.9.1 or any of the 8.x snap kernels, none of them work. I can flash older ones without issue (kingx #4, #6, netarchy 4.1.8, snap 7.11). Nobody else seems to have this issue, is it possible I screwed up my Evo?
_MetalHead_ said:
I'm using KingX and I don't know what bash is. Anyway, I just tried adb again and it's back to a #, so that's a non issue now. I still can't figure out why I can't flash ANY of the new kernels without causing a bootloop. KingX 7 and 8, netarchy 4.1.9.1 or any of the 8.x snap kernels, none of them work. I can flash older ones without issue (kingx #4, #6, netarchy 4.1.8, snap 7.11). Nobody else seems to have this issue, is it possible I screwed up my Evo?
Click to expand...
Click to collapse
You'll need to wipe your phone. Data dalvik, cache.
Sent from my PC36100 using XDA App
SharkUW said:
You'll need to wipe your phone. Data dalvik, cache.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Done that about 50 times now :/
_MetalHead_ said:
Done that about 50 times now :/
Click to expand...
Click to collapse
I've pretty much stayed away from the tricked out kernels because the instability scares me, but the few times I used one I noticed that sometimes my phone had to reboot two or three times before it booted and stayed on. Just a thought.
_MetalHead_ said:
Done that about 50 times now :/
Click to expand...
Click to collapse
If you are running ClockworkMod, you need to wipe with amon-RA. they say ClockworkMod does not wipe completely.
http://forum.xda-developers.com/showpost.php?p=6855542&postcount=1
illogic6 said:
I've pretty much stayed away from the tricked out kernels because the instability scares me, but the few times I used one I noticed that sometimes my phone had to reboot two or three times before it booted and stayed on. Just a thought.
Click to expand...
Click to collapse
I've sat and watched it reboot 10 times in a row before I gave up and restored my nand.
If you are running ClockworkMod, you need to wipe with amon-RA. they say ClockworkMod does not wipe completely.
Click to expand...
Click to collapse
I've done it multiple times with both. AmonRA is my preferred recovery.
dwertz said:
If you are running ClockworkMod, you need to wipe with amon-RA. they say ClockworkMod does not wipe completely.
http://forum.xda-developers.com/showpost.php?p=6855542&postcount=1
Click to expand...
Click to collapse
Afaik clockwork has always wiped ok. I think there were a lot or still are people confused by dalvik being in a separate menu. There are also people that will tell you to wipe twice. It's not a rubber eraser, it's a filesystem.
Sent from my PC36100 using XDA App
SharkUW said:
Afaik clockwork has always wiped ok. I think there were a lot or still are people confused by dalvik being in a separate menu. There are also people that will tell you to wipe twice. It's not a rubber eraser, it's a filesystem.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I had issues with it and several other people have and I know there were seperate menus. Just saying, it has been several people even ones that have been around awhile.
http://forum.xda-developers.com/showthread.php?t=758633
http://forum.xda-developers.com/showthread.php?t=719763
from Netarchy
An important note for Clockwork mod Recovery users:
Clockwork Mod is reportedly not wiping correctly (ie; if you try to wipe cache/dalvik-cache/data/etc it's not actually doing it, or not doing it right)
You may want to consider using Amon Ra Recovery instead.
I how you know that your first link is all posts, at least as far as I read into, detailing the various levels of crazy required to believe that cm isn't wiping the dalvik cache. Did you read it or just the op?
Sent from my PC36100 using XDA App
SharkUW said:
I how you know that your first link is all posts, at least as far as I read into, detailing the various levels of crazy required to believe that cm isn't wiping the dalvik cache. Did you read it or just the op?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I read the posts. Some people are just having issues and some people are not. All I was stating is that CWM has been known to have a few issues and to try Amon RA to see if the problems get fixed. I used to have issues installing kernels with CWM. I used it through Rom manager because it made it easy. I ended up going to Amon RA because all the issues I had personally. I know Amon RA has been reducing the size because some people had bad blocks. Have you thought that maybe your phone doesnt and some people does causing the full recovery not to be there?
dwertz said:
I had issues with it and several other people have and I know there were seperate menus. Just saying, it has been several people even ones that have been around awhile.
http://forum.xda-developers.com/showthread.php?t=758633
http://forum.xda-developers.com/showthread.php?t=719763
from Netarchy
An important note for Clockwork mod Recovery users:
Clockwork Mod is reportedly not wiping correctly (ie; if you try to wipe cache/dalvik-cache/data/etc it's not actually doing it, or not doing it right)
You may want to consider using Amon Ra Recovery instead.
Click to expand...
Click to collapse
switching from rom to rom, i just do a full factory wipe, isn't that technically what dalvik is not doing in clockwork, i've had no issue's yet by doing this, even with some rom's i haven't done it and things have worked fine, but that's besides the point.
tomh1979 said:
switching from rom to rom, i just do a full factory wipe, isn't that technically what dalvik is not doing in clockwork, i've had no issue's yet by doing this, even with some rom's i haven't done it and things have worked fine, but that's besides the point.
Click to expand...
Click to collapse
Yes, the general wiping instructions are very redundant. Dalvik is within cache which is why clockwork has it under a sub menu. You "wipe" dalvik 3x with factory reset, cache, dalvik. Some roms have dalvik under data by my understanding, in which case you've wiped it once.
Sent from my PC36100 using XDA App
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.
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.
Now for about the last 2 months now this phone has been really getting to me. I have been putting different roms on my phones thinking that my roms have been messing up , but everytime i put a new rom on my phone i have the same issue. when i tried to log on the internet it will force close then i have to do it again to log online. it is really an issue now. does anyone know if it is my phoneor something? someone suggested that i got to rom manager and go to fix permission and i did that and it did not work. my ast resr s taking this root off my phone. the reason for that is because i am about to sell my phone and i dont want to sell it and the phone keeps having this issue. any suggestions?? thanks
May have to unroot and take to sprint, only thing I can think of
Sent from my Gruesomes Rom using xda premium
Trying switching your recovery to amon ra and I don't recommend using ROM manager instead flash your Rom manually in the recovery
Sent from my Gruesomes Rom using XDA App
well i doubt its anything sprint can do. i never had this issue before i believe its something thats on the phone from the root
nickhowell25 said:
well i doubt its anything sprint can do. i never had this issue before i believe its something thats on the phone from the root
Click to expand...
Click to collapse
Simply having root will not cause force close issues. It's more likely that you're either not wiping thoroughly, or that you're restoring system data.
Have you tried wiping everything (system, data, cache, dalvik, boot, sd-ext, and android_secure)? If you've been using ClockworkMod, you've probably only been wiping data, cache, and dalvik.
If this is the case, either switch to Amon Ra and wipe those before flashing, or use a wipe script that will wipe those options. Running an RUU may be another means to the same end.
If you've been wiping everything, or if it doesn't work, it could also be something with your radio. You can try updating or downgrading.
Sent from my Evo + MIUI using Tapatalk!
I've got an evo 4g, I've been rooted for about a year. i flashed cm7.1 and it was running for about 3 months and last week wifi and 4g just stopped working. i used rsa checker to check my keys and they're still there. i think the problem is my ip address. its unavailable on wifi and 4g. i dont really know where to look. can someone point me in the right direction?
Did you just flash a new kernel?
Try flashing Tiamat... see what happens.
i just flashed savaged zen, but that was after the problem. i reflashed clockwork again, as well as cm7 again. how do i update my ip address? i think thats the prroblem. by telling you i already flashed a kernel, do u think it will help? how?
biggda said:
i just flashed savaged zen, but that was after the problem. i reflashed clockwork again, as well as cm7 again. how do i update my ip address? i think thats the prroblem. by telling you i already flashed a kernel, do u think it will help? how?
Click to expand...
Click to collapse
Just flash Tiamat and see what happens. This is almost definitely kernel related. Make sure you wipe dalvik cache and cache (preferably with Amon RA or TWRP recoveries).
I love you man, I'm talking serious bromance! Can you explain why that worked? Did my old kernel go bad? Thank u so much!
Sent from my PC36100 using XDA App
it broke again, I flashed again. It didn't come back.
Sent from my PC36100 using XDA App
Try a different version of CM7. You can also try an entirely different rom for troubleshooting purposes. Generally 4G & wifi issues stem from the kernel. Are you flashing any mods or running anything that makes system changes, like V6 Supercharger? If you're using V6, undo the kernel tweaks.
Best bet is to flash a different version of CM7, even if you have to downgrade. Do a full wipe - data, cache, dalvik, system, boot, SD-ext, .android_secure - and flash only the rom and gapps. Try 4G & wifi before restoring anything. If they work, you can then restore anything you've backed up with TB, just try to avoid restoring system apps/data. If the problem comes back then it may be something in one of your apps or the data you've restored... though unlikely.
If this doesn't work, do a full wipe again and flash a fully stock rooted rom. Update your radios etc with the combo zip. If that fails, RUU.
There are plenty of options, but I don't think you'll have to go as far as running an RUU. Start from the top and work your way down.
Supersonic Evo 4G | MIUI | Tapatalk
I went to 7.1 rc then I reflashed 7.1 without gtalk . Works fine now. Thanks.
Sent from my PC36100 using XDA App
the only thing I could see that broke it was font installer app or google talk. Its fine now. Ill keep u updated. Thanks
Sent from my PC36100 using XDA App