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
Related
I am unable to flash any roms except cm6 ( I can also flash any nightlies. )
This is driving me crazy. I have tried to flash fresh 3.2 to no avail. I have also tried to install the new virus rom. I attempted to install the rooted version off the newest ota with the same results.
After each attempt the result is the same. It will just hang on the HTC evo 4g screen.
I have downloaded the roms a few times each to ensure they were completed correctly.
I have pulled the battery and waited.
I have deleted all data / dalvik / Cache several times in a row.
I have attempted to flash using a different version (earlier) of clockwork with the same results.
I even attempted to flash with RA recovery. Same results.
I am completely lost as to why I can only flash cm6 roms
Please let me know any suggestions.
Sent from my PC36100 using XDA App
From what I have read...................
You need to restore a 2.1 or a 2.2 rom you have, boot to that, then you can flash to a 2.2 rom.
You can't go from CM directly to another rom.
I am on 2.2
Sent from my PC36100 using XDA App
An HTC rom.
CM is not a typical ROM.
Restore your original backup, and try from there. If you don't have one, you may need to RUU
Bielinsk said:
An HTC rom.
CM is not a typical ROM.
Restore your original backup, and try from there. If you don't have one, you may need to RUU
Click to expand...
Click to collapse
Ok, so basically I am going to unroot - reroot?
I just flashed from cm6 straight to baked snack directly with no problems. Not really helpful but you shouldnt need to flash to a stock rooted rom first. Note sometimes you have to wait a good 5 minutes for the htc screen to go away. Probably took about 5 when I moved from cm6 to snack.
I just tried again, attempted to go to fresh. I let it sit for 10 minutes with no results.
Defpdp said:
I just tried again, attempted to go to fresh. I let it sit for 10 minutes with no results.
Click to expand...
Click to collapse
I unrooted- rerooted with the same results, I cannot flash ANY roms other than Cm6 it seems, this is very frustrating..
Anyone else have any ideas at all??
Thanks!
Try flashing a new recovery. If you're using the newest amon go back to the last one or vice versa. Or even move over to clockwork. But I would ask about that I know clockwork doesn't play well with cm6. This could get you in trouble but I guess you always go back to amon.
crimeslunk said:
Try flashing a new recovery. If you're using the newest amon go back to the last one or vice versa. Or even move over to clockwork. But I would ask about that I know clockwork doesn't play well with cm6. This could get you in trouble but I guess you always go back to amon.
Click to expand...
Click to collapse
Nothing worked, tried going to different recoveries/versions. Nothing.
Anybody? Any advice?
if you flashed cm6 and have it working... its my understandung that you cqn not just go and flash a different rom. there is a process that needs to be followed.
but i have never and never will use cm6 so i could easily be talking from my rear.
Sent from my PC36100 using XDA App
I flash from cm6 to rooted stock rom when I need to update prl and stuff.
After you flash wipe dalvik and cache again I had that problem when flashing snap.
Im not sure if these don't help. Maybe you can send a tweet to cyanogen himself to get it resolved. If fix pst your findings
Sent from my PC36100 using XDA App
Re root and see what happens
Sent from my PC36100 using XDA App
Also check your kernel, you shouldnt have to flash anything but the rom you want when switching from cm6
I am using the newest amon recovery. Everytime i try to restore a nandroid i save it gives me bootloops. I normally wipe everything twice and flash caulks format all zip. Is there something im doing wrong?
Sent from my PC36100 using XDA App
i would love to have this answer also...was getting the same thing happening to me, sumtimes bootloop off a hot restart...various roms, mysn, mik, virus, miui, didnt really matter which i was coming from or going too...
have since unrooted my phone and rerooted it just to see if sumthing was off...so far so good...would still like to have answers as to why though.
amon ra 2.3
latest radios
oo3 hardware
3.70
hboot .76 eng boot
Same here i rerooted and then reooted back and i still get the same result. Wonder if i am supposed flash the rom, then restore? On my hero i never had issues.
Amon ra 2.3
004 hw
Newest everything
Myns rls5
Ziggy nwest
Sent from my PC36100 using XDA App
Is your usb plugged in while either backing up or restoring? Have you tried loading a different version of amon?
U need to flash a kernel, nandroid dont save that
Sent from my SGH-T959 using XDA App
so your are saying flash the kernal first then restore nandroid restore?
Okay I just tried what you said and I still got bootloops. And my USB is never plugged in when i do a nandroid.
Something in the backup is giving you bootloops. Try completely wiping, the flashing a new rom.
You can review the recovery log too.
Sent from my PC36100 using XDA App
DEFINITIONOFREAL said:
U need to flash a kernel, nandroid dont save that
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes it does. Likely the issue is that a wipe is not being performed before restoring the data in the nandroid.
Sent from my PC36100 using Tapatalk
Garbage in, garbage out.
If your device was unstable when you backed it up, it will continue to be so after you restore.
Try a different Sd card. If your device continues to be unholy, revert back to a stock based rom or even RUU. If your issues persist, you likely have a hardware fault.
Basic troubleshooting 101...
Nandroids dont replace the kernel, do the nand then flash the kernel
Sent from my SGH-T959 using XDA App
i really need sum help...have posted here once before on this issue...i just flashed mik4.5 last nite...made a backup this am...flashed sum mods and made another nand backup this afternoon...needed a text message off the first nand backup so i wiped everything and started the nand restore...installed just fine and started to boot up just fine untill the boot animation stopped...then it started bootlooping...wth man...i have had my evo since it came out and been using amon ra since i started this adventure we call rooting...never have i had so many things go wrong with nand restore or backups...9 out of 10 backups i have made since 1.8 has become obsolete has not worked...please help...ty
Man I'm having bootloops all the time now ever since i updated the new combo radios and flashed myn RLS5. On sense with rls5 my phone reboots a lot kinda and with AOSP roms like MIUI my phone reboots like every 24 hours and goes on a bootloop. I can't figure out what's going on. Tried messaging some devs but they don't answer me
Did u run Calkulins Format All.zip?
Sent from my PC36100 using XDA App
LuvThyMetal said:
Man I'm having bootloops all the time now ever since i updated the new combo radios and flashed myn RLS5. On sense with rls5 my phone reboots a lot kinda and with AOSP roms like MIUI my phone reboots like every 24 hours and goes on a bootloop. I can't figure out what's going on. Tried messaging some devs but they don't answer me
Click to expand...
Click to collapse
When you switched roms, did you do a format data/calkulin's format all? doing either or should fix your bootlooping problem.
I always use caulkins format all. Still get bootloops. Wipe everything, still get bootloops. I dont know what to somwtumes except star all over from scratch.
Sent from my PC36100 using XDA App
marcusva79 said:
I always use caulkins format all. Still get bootloops. Wipe everything, still get bootloops. I dont know what to somwtumes except star all over from scratch.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Same here bro. I've tried 3 different roms this weekend thinking it was just miui causing the problem but I actually got bootloops on all of them . This is weird
Sent from my PC36100 using XDA App
"Wipe everything", is that a factory restore/reset?
Cause that's what I do (factory reset).
Then the nand restore............
marcusva79 said:
I always use caulkins format all. Still get bootloops. Wipe everything, still get bootloops. I dont know what to somwtumes except star all over from scratch.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Are you flashing kernels over that?
I have been using the syndicate rom for months to perfection, love it. But I was using the wifi tether and suddenly my phone restarted. After it booted up the sms, google talk and email app will not work; I open them and they force close all the time.
What can I do?
Thanks.
restore a backup or reflash.. and post in the correct section
Moved to Q&A. And wipe data to fix it.
Thanks.
Sorry for not posting in the correct area.
I reflashed the rom and it syill gives me the problem. Guess I will have to wipe then reflash the rom?
If I do a rom backup, and restore that one, will I have the same errors?
Yes... Happen to me twice... Make backups weekly is your only hope. It reboots and nothing work again. After two reboot more it stops in the acs loading screen
Sent from my SPH-D700 using Tapatalk
that happened to me too. what fixed it for me was to odin to dk28 and use a rom from there im still using truly epic rebirth for dk28 and haven't even thought of switching to and eb13 or ec05 rom
Acs backs up data when you reflash, and puts it back on.. therefore returning the corrupt data.. so you have to wipe data before reflashing or you'll be in the same boat. I always format system and data before flashing a rom just to make sure. Do regular nandroid backups and mybackup root or titanium backups if you are going to run a no journals rom
Sent from my SPH-D700 using XDA App
Thanks to all.
I fixed it.
I had to boot into CWM and fix permissions there. What I don't get is that I did the "fix permissions" through Rom Manager...so what's the difference?
If that didn't work then I would've had to wipe/reflash.
Hope this helps someone else with the same problem.
Rom manager doesn't work with the epic.
LunaticWolf said:
Rom manager doesn't work with the epic.
Click to expand...
Click to collapse
This. It is still currently trash. Don't even bother.
I am currently running EvoKings GB RC3 and loving it. But since I can't leave well enough alone, I want to update to the RC4.
I just have a couple of questions concerning this ROM.... I see where he mentions its based on CM7... is it based on CM7 7.0.0.0 or CM 7 7.0.2.1?
Also will I need to do the GPS fix again and update PRL, as I assume I have to wipe dalvik/cache to update from RC3 to RC4 (as it seems its more than just an update)?
Speaking of the GPS fix, when I did it, I was on RC3 of the EvoKings GB rom, and this is the steps I followed:
Booted into recovery
Made a Nandroid backup
Wiped All Data
Flashed into a backup sense rom I have (Mikfroyo 4.6)
Performed GPS fix and updated PRL
Booted back into recovery
Performed Nandroid restore (no data wipe)
Back into RC3
Was that correct... that I dont do a data wipe and just do a nandroid restore? I have been reading so many conflicting reports on this. My assumtion was to always wipe data before doing a restore.
Thanks everyone.
First of all, if you're updating a current rom, them all you should have to do is wipe cache & dalvik and then flash the updated rom. As for not wiping data, no, it isn't necessary, however, I'm one of the people who do especially if I'm changing roms. I don't want any remnants of the previous rom.
posting & replying via the XDA Premium app.
dougjamal said:
First of all, if you're updating a current rom, them all you should have to do is wipe cache & dalvik and then flash the updated rom. As for not wiping data, no, it isn't necessary, however, I'm one of the people who do especially if I'm changing roms. I don't want any remnants of the previous rom.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Ok cool, thanks. When doing the GPS fix, is the info stored somewhere else, which is why it doesnt get removed when doing a wipe of stuff?
Trying to figure that out... since yeah I am worried about having some type of conflict when switching from a sense to an AOSP rom. I havent had any issues so far with RC3 doing that, minus some issues with the screen not coming on with a button press while playing music.. but not sure if thats just something with the ROM itself or the GPS fix.
I am not sure where the gps fix is stored, but there should be no conflicts. I have switched between AOSP and Sense tons many times since I did the fix and have never had any problems.
Sent from my Infected Evo using Tapatalk Pro!
whiterider13 said:
I am not sure where the gps fix is stored, but there should be no conflicts. I have switched between AOSP and Sense tons many times since I did the fix and have never had any problems.
Sent from my Infected Evo using Tapatalk Pro!
Click to expand...
Click to collapse
+1.....I've never had to apply a GPS fix and I, too, have switched between AOSP and Sense numerous times. As a matter of fact, my current rom is Salvage-Mod and the GPS works as it should and I still didn't have to apply a fix.
posting & replying via the XDA Premium app.
I had to do the gps fix when I first switched to cm7 rc2. Since then I have never had to redo it nor have I had any issues.
Sent from my b3 Infected Evo using Tapatalk Pro!
whiterider13 said:
I had to do the gps fix when I first switched to cm7 rc2. Since then I have never had to redo it nor have I had any issues.
Sent from my b3 Infected Evo using Tapatalk Pro!
Click to expand...
Click to collapse
Thank you both, thats what I wanted to hear. I havent wanted to switch roms because I got the GPS working and I didnt want to switch roms and have it broke again. Thank you!
No prob man, just glad I could help.
Sent from my b3 Infected Evo using Tapatalk Pro!
What build of CM 7 is this rom built off of?
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.