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!
Related
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.
I have some major issues!!!!
I have tried everything that I can think of and I still have problems!!! I have flashed several different radios, Different Kernals, Different ROMS ASOP and Stock and I don't know why my phone keeps restarting randomly! Sometimes it will go for an hour and sometimes it will go for 30 seconds but it keeps restarting itself. Currently I am running CM7 with the new GB Radio leak. Still happeneing please can someone help ease my frustration with this god forsaken phone! Thanks for any Suggestions!
Just a thought, are you undervolting your kernel at all? If undervolted too much mine has constant reboots.
All I can think of, but by no means am I an expert.
Are you wiping all partitions before flashing?
Full Wipe:
1. Wipe Data/Factory Reset
2. Wipe Cache Partition
Go into Mounts and Storage
3. Wipe System
4. Wipe Data
5. Wipe Cache
Go into Advanced
6. Wipe Dalvik Cache
7. Wipe Battery Stats
8. Install zip (ROM)
9. Power off/on, the boot back into recovery
10. Install zip (GApps)
11. Power off/on
*These are not my instructions. Saved them in evernote but I can't remember what thread it was from.
SD?
Had this same thing happen w/ a friend's DInc.
Copied all SD files to PC, removed and reformatted SD to FAT32, copied files back to SD, remounted, problem went away.
It was a guess on my part, and worked for her, idk if that was the issue, but the reboots stopped.
does it do it when you just install a rom with the stock kernal it comes with? Try running just 1 thing for a while to see what is causing it.
Or it may be a hardware issue.....you can search these threads for 'random reboots' and see that you may just need a new phone. I had the random reboots issue which originally lead me to rooting......which still didn't help. My problem started when I let the phone get way too hot on a car charger, does it seem heat related? Just a thought, would seem more likely than a kernel issue as every time you flash a new ROM you get a different kernel....
I had the same issue and had to get a replacement. Just make sure you put everything back to stock before you take it in. There is a great thread in develompement that will walk you through it. You may want to even try going back to stock anyway and see if the problem persists.
I can run stock everything and I still get the same problem I'm going to try and format my sd card and see if that works.....i don't know what else to do. And yes i have wiped everything before installing new ROM...
Sent from my ADR6400L using XDA Premium App
Problem with returning the phone is that I'm going to have to pay the hundred for insurance... Damn
Sent from my ADR6400L using XDA Premium App
FrierEM said:
Problem with returning the phone is that I'm going to have to pay the hundred for insurance... Damn
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I thought it was $50? and I also thought they ran out of Incs?
What I meant by back to stock is unroot, s-on, ect... You mentioned that you have tried different roms so I am assuming you are still rooted.
They are not out of incs, but if they were you would get an upgrade anyway.
Sent from my ADR6300 using XDA 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.
Does any one here know if some of the Kernal cleanser zips from the s2 for TMO would work on the s3? If not are there any similar options?
Also is there a davlik wipe that works properly on the s3? Similar to the dark side zips. Cwm is not doing so correctly.
Sent from my SGH-T999 using xda premium
Wildchld has a Superwipe script in the op of his xquizit thread. That's the closest thing I can think of for us right now, but it wipes everything.
Don't use any from another device. Depending how its written it could brick you.
Should be pretty easy to make it work for ours. Ill try to find it and see if I can't get it working for us.
Do you have a link to it?
Just curious, how is cwm not doing the job for you? Does it error or just seem to not work right?
Sent from my SGH-T999 using xda app-developers app
This is the link for superwipe for the Hercules
http://sourceforge.net/projects/darksidetools/files/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip/download
Sent from my SGH-T999 using xda premium
Well not exactly what I was looking for but it will work for clean flashes. Thanks kind sir. This is from the same dev as the s2 so it's solid I am sure.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Wildchld has a Superwipe script in the op of his xquizit thread. That's the closest thing I can think of for us right now, but it wipes everything.
Don't use any from another device. Depending how its written it could brick you.
Should be pretty easy to make it work for ours. Ill try to find it and see if I can't get it working for us.
Do you have a link to it?
Just curious, how is cwm not doing the job for you? Does it error or just seem to not work right?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It just seems not to work. It goes way to fast to seem to be working and throws the same extsd error as the s2 had done. How is twrp? Is it worth the try? I have heard many issue can occur with it.
Sent from my SGH-T999 using xda premium
I have been using TWRP since I rooted my phone back in June, have not had 1 issue with it. Everything works flawlessly, I have flashed almost every AOKP, CM10, TW ICS & TW JB ROM out there thru TWRP and never lost my IMEI and the wipe functions in it work just fine. I usually wipe cache/delvik, system & factory reset 3 times. For me it seems to wipe pretty fast ( that's why I do it 3x ).Just to be safe.
belial20xx said:
It just seems not to work. It goes way to fast to seem to be working and throws the same extsd error as the s2 had done. How is twrp? Is it worth the try? I have heard many issue can occur with it.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Well isn't this normal since there is no external sd ext partition? I mean sure one could write a simple zip to delete /data/dalvik-cache.
And there really isn't a way to check it either. Cause I don't think adb works in recovery mode.
Sent from my SGH-T999 using Tapatalk 2
The Dalvik wipe in CWM works fine. It's very fast (just a few files), and the "error message" can be safely ignored. It's more like an informative message, not an error message. If you don't think it worked, just reboot your phone, and you will see that it did, infact, work.
There are still people going on about IMEI loss with CWM. First of all, you should have backed up your IMEI with su > reboot nvbackup in a terminal emulator. When your IMEI is 0, what happened was your nvdata got corrupted, so the backups were restored. Problem is you didn't make a backup, so those partitions contained nothing but dummy data, instead of the nvdata they are supposed to contain. It's been theorized that this is a screw up at the factory level. Easily rectified.
Last I checked, no one has figured out why this corruption happens. Flashing a nightly flashes the kernel and copies system files. Which means it can happen with either CWM or TWRP. I suspect the disparity in user bases, combined with the rarity of the problem, is why you don't see people complaining about IMEI loss with TWRP.
Kernel cleanser? You don't need one. Just flash a new kernel, it will overwrite the old one (it's a partition).
What problems have you heard about with TWRP? My complaints are mostly nitpicks, and I'm biased. It works fine. Make sure you're always using the latest versions, though.
Aerowinder said:
The Dalvik wipe in CWM works fine. It's very fast (just a few files), and the "error message" can be safely ignored. It's more like an informative message, not an error message. If you don't think it worked, just reboot your phone, and you will see that it did, infact, work.
There are still people going on about IMEI loss with CWM. First of all, you should have backed up your IMEI with su > reboot nvbackup in a terminal emulator. When your IMEI is 0, what happened was your nvdata got corrupted, so the backups were restored. Problem is you didn't make a backup, so those partitions contained nothing but dummy data, instead of the nvdata they are supposed to contain. It's been theorized that this is a screw up at the factory level. Easily rectified.
Last I checked, no one has figured out why this corruption happens. Flashing a nightly flashes the kernel and copies system files. Which means it can happen with either CWM or TWRP. I suspect the disparity in user bases, combined with the rarity of the problem, is why you don't see people complaining about IMEI loss with TWRP.
Kernel cleanser? You don't need one. Just flash a new kernel, it will overwrite the old one (it's a partition).
What problems have you heard about with TWRP? My complaints are mostly nitpicks, and I'm biased. It works fine. Make sure you're always using the latest versions, though.
Click to expand...
Click to collapse
Its actually not just a few files. Its quite some 60 megs depending how many apps you have installed
I made a dalvik cache wiper.
If you notice when you use CWM to clear dalvik cache, then reboot, it doesnt say android is upgrading at all. Making me think it doesnt work.
But when you just flash my script, it says its upgrading.
the zip is simple, all it does is delete_recursive("/data/dalvik-cache/") and thats it.
elesbb said:
Its actually not just a few files. Its quite some 60 megs depending how many apps you have installed
Click to expand...
Click to collapse
Obviously, it was an exaggeration.
After your report on dalvik wipe not working, I was inclined to try it myself, since I always wipe cache+dalvik when flashing a new rom. Wiping just dalvik, I was greeted with the optimizing apps prompt on the next boot.
Aerowinder said:
Obviously, it was an exaggeration.
After your report on dalvik wipe not working, I was inclined to try it myself, since I always wipe cache+dalvik when flashing a new rom. Wiping just dalvik, I was greeted with the optimizing apps prompt on the next boot.
Click to expand...
Click to collapse
So did i.. but it optimized the same amount of apps that the "wipe cache" option does. I seriously wonder now if they are one in the same. Like if they are coded to wipe /cache and /data/dalvik-cache. Cause when using my zip, i only optimize 58 apps.