shell32 keeps crashing :( - HD2 General

Thought I would try going to a custom rom and when I decided to go back to the factory 1.48 rom I have had nothing but problems.
shell32 keeps on crashing all the time (mostly when I tap start), random lockups, wifi connects once and then disconnects and I cannot get back onto my wireless network.
Tried resetting to factory defaults, tried 1.61 wwe with the same results
Is there anything which could get left behind from using a custom rom?
Before this it was rock solid so would love some help, lost count how many times I have reset and flashed this phone now

Related

wizard has weird call/text problems...

so i've been having a problem recently where sometimes when i try ending a call no matter how many times i hit the end key, it won't hang up.
i thought this was just something wrong with the rom so i flashed it to the original rom and tried out blackdiamond touch.
then i started missing phonecalls and texts, so i flashed the original rom, flashed the radio rom and upgraded it to TNT professional.
i'm STILL having the problem of missing calls/texts, inability to hang up, and just a general difficult time whenever using the phone (calls dropping, losing service out of nowhere and cant get service until i restart, etc).
does anybody have any ideas? because outside of flashing the rom as well as the radio rom, i'm clueless. much thanks!
you can try to install the raido fix for wm6

[Q] HD2 Freezing, Rebooting constantly.... HELP

Hey fellas, I have been a long follower of the Android Developer threads and lately I have been experiancing a lot of problems.
The problems go as follows.
1. Sometimes upon starting windows, the device will freeze and reboot itself and then get stuck on the splash screen with the numbers at the bottom. ... (Battery Pull)
2. Sometimes when running say a certain app or answering a phone call the device would freeze then make a buzzing sound for 5-10sec and then reboot and again get stuck similar to #1.
3. Sometimes upon running android which runs fine the phone would freeze and reboot again.
Now At frist I had the OEM rom, then mooved to the Chunky Tab rom, then to MIRIs rom... after that I experianced the shut down issues, then did the Task 29... didnt seem to fix anything... then OEM ROM and back to MIRIs ROM an again nothing.
Now I did a lot of reading on the issues and the only thing that people report is a bad CPU>.. my battery life is also terrible...
NEED HELP or ADVICE on the situation... should I get rid of the HSPL and send it in to Tmobile?
I would try this first.....remove every single cab, app or mod you you've done to the phone, hard reset, remove/delete your data file/folder and ultimately...remove Hspl go back to stock and try
Keep us posted pls
If M_T_M's steps don't work you could try flashing a ROM like UnOff and maybe switch radios (after deleting the App Data folder) and just see how it works before having to go back to stock..

[Q] Why does my Wifi & Bluetooth not working even with stock rom?

Hey guys,
I have a Galaxy S4 (i9500). I installed Omega ROM v22 on it and everything went smoothly, Wifi & BT working perfectly.
After a few hours of using the device (nothing special at all, texts and stuff like that) - I noticed my wifi isn't working and by not working I mean that I click the wi-fi button and it changes from gray to the mid-state between gray to green for around 20 seconds before it goes back to green ago.
If I open the menu to see my networks it just says "Enabling" without any networks there.
I had to drive somewhere so I went to my car and tried to enable Bluetooth, and same thing happens there - Bluetooth will not turn on and will stay stuck on mid-state between gray and green for a while and go back to green.
I flashed omega rom v22 again and the problem was gone, or so I thought. I went back to the car for another drive and realized the bluetooth issue is back - and when I got home I realized the wifi issue is back as well.
I figured I need to reset everything so I tried the following:
Full wipe (including dalvik and even including "internal SD card") and then flashing stock rom (from the official website, stock rom of my country).
The issue was back after a few hours. I do not have BT or Wifi access. Yesterday Wifi suddenly started working for a few hours but then it stopped working again.
I really need help! I have no idea what to do with this issue!
Well rule number one when you have problems after flashing without wipe.
1. perform a full wipe and see if the problem persists.
Lennyz1988 said:
Well rule number one when you have problems after flashing without wipe.
1. perform a full wipe and see if the problem persists.
Click to expand...
Click to collapse
Tried that, no luck.
What else would you try?
In some places when people had problems with Wi-Fi they said to flash a different kernel but I don't see why I would have this specific issue with Omega Rom and why the default kernel with it wont work well?
Maybe this could be a root issue? My root works fine but I have this weird gut feeling like this is some permissions thing that's going on.
I'm trying to think why it would work right after the wipe but then stop working shortly after.
Another symptom: It randomly started working for a few minutes and then stopped again (around three hours ago).
Any idea what's going on?
Well, if you fully wiped and didn't restore any apps and settings then it can be two other things.
Or it's a bug in the rom or a hardware failure in your phone.
I would suggest trying a different rom first. Do not restore anything, not even your google account.
wi-fi fix?
Do you actually have an i9505? or is it a canadian or att version? if its the latter sometimes the devs offer some wifi-fixes, also try a different kernel. otherwise it could be that your radio/modem are not compatible with the version of the ROM you are flashing.
Tried arrow ROM and this issue doesn't seem to happen in this rom. Hope it stays like that...
morhsn said:
Tried arrow ROM and this issue doesn't seem to happen in this rom. Hope it stays like that...
Click to expand...
Click to collapse
Sadly, it did happen with this rom, after just a few hours.
I'm now using stock rom and still suffering from the issue.
Does anyone have ANY idea what I can do to fix this?
Thanks in advance!

[Q] Odd problem.... lose service after hitting power button/screen off

Hello all,
I've been searching for 3 days now and cannot find a solution to this problem. Normally I try to avoid starting a thread since there is usually one on the internet somewhere already, but this has me stumped.
I have a SGH-I337M on Bell, was running SlimKat 4.4.4 with no problems, and wanted to upgrade to LP. I first tried installing the CM12 optimized build, but it would never get past the boot screen. Then I tried GPE 5.0.2, and it looked beautiful and ran smoothly, but it would not automatically connect to Bell's network. If I went into the mobile networks menu and waited for it to scan, and then selected Bell, it would connect, but a few minutes later it would disconnect again. WiFi worked fine. Needless to say, having no constant service was unacceptable. After that I tried installing SlimLP (wiping cache, system, etc in between all installs) and had the same service disconnection problem.
Then I tried:
-flashing modems
-flashing back to stock from SAMmobile and reinstalling (where a similar problem persisted)
-starting from fresh to GPE, then starting from fresh to SlimLP
-reflashing GPE with all 3 kernel choices, cutting out as many installation options as I could
-trying different combinations of preferred wireless mode, APN, etc
Nothing works. I am back on SlimLP and I have got it to the point where the Bell service will work as long as the screen is on, but when I hit the power button and/or the screen goes off, the network disconnects again. If WiFi is NOT on, when I hit the power button and unlock the lock screen, it will automatically connect to Bell again, but this does not happen if WiFi is on.
Any ideas here..? I've read countless threads and nothing seems to work. Any help would be much appreciated as this is driving me crazy!!
The issue has been resolved! Apparently I was too impatient and was not using the proper modem
But I can't find a way to delete this thread. Damn I must be getting old

[Q] Samsung Galaxy S5 SM-G900W8 Running Omega Rom V17 Reboots when WiFi Connects

Not sure if this is the place to post this question, but I've been searching everywhere and I haven't found anyone online who is having the same issues as me.
I installed Omega V17 (for G900F) on my Rogers G900W8 S5 a few weeks ago (didn't choose to use the Omega Kernel) and it seemed to work OK, but it seemed to reboot randomly (all of a sudden when I'm in the middle of doing something, the Omega loading animation would appear). I didn't update my modem, as my phone was reporting that I was already using version VLU1BOC1. I have been trying to find out what has been causing the issue. I reinstalled Omega, tried removing all apps, but it would still crash.
I finally started to notice a pattern while at work. When I would walk across to our other building, it would always reboot. The only thing my phone would be doing when walking across the parking lot would be disconnecting from the WiFi in the one building and connect to the other. I suppose the other times when it would reboot where when the phone would, for some reason, drop the WiFi connection and reconnect (or I'm assuming that's why it reboots when I'm stationary).
When I did the install, I wiped both caches and did a factory reset beforehand and it seemed to install fine, so I don't think it is an issue with the Omega install, but I did try installing Cyanogenmod and it has been fantastic (stable and fast). I would rather run Omega for Touchwiz, but it keeps rebooting and it's pretty much unusable in that state. I noticed that there was a new version of Omega (V18) for G900F so I was going to try that version to see if it might work, but I just can't at the moment (I should be able to in the next couple days and will report back with an update).
I was wondering if there is any way to confirm what is causing the Omega reboots, and if anyone else has seen this issue before?

Categories

Resources