So...here's the thing. Supposedly it's impossible to 100% brick an i500. Well I believe I managed it. If not, I would REALLY like to fix it. I use it just for media stuff these days, like reading and music. So...here's what I did. I know it was stupid.
1. Rooted my Samsung Fascinate i500 from Ntelos.
2. Got a bunch of replacement apps, like Go Launcher EX, and pretty much every other thing the GO team came up with.
3. Used Titanium Backup to delete system apps(like the launcher, basic internet, and some other stuff) instead of freezing them. I am an uber noob. It shows, yes?
This was all some time ago, when it was actually connected to a plan and used as a phone. It still worked...most of the time. It would derp and freeze up occasionally, but otherwise worked fine.
4. At some point a few days ago I somehow uninstalled something that caused the wifi to cycle itself back on no matter what I did (including turning on airplane mode, it just turned airplane mode off and cycled the wifi back on) causing battery drain, since it's constantly searching for SVC. So since I couldn't figure out what happened to cause this, I decided it was time to finally get a custom ROM. I used ROM Manager to try and flash a custom rom I cooked in this online kitcheny thing.
It didn't work. Anyway, I went into the recovery and cleared the cache thingies, hoping it would help.
Instead, I no longer have a launcher. Since the default launcher was gone, apparently it won't let me use my Go Launcher EX anymore, or even bring up the menu to set it as a default.
I went through the steps to flash a new ROM or the original I found using ODIN3 and the download screen. I can get to the download screen fine...but ODIN3 won't recognize my phone. At all. Ever. I do have the right drivers, if I'm not mistaken.
Well...at this point, I don't know what the hell to do. I don't have the money for a new one, or I'd get it and start over and do it right this time.
Halp?
This problem is solved.
So...yeah. I forgot I had to use the original cable. My bad. I fixed it. Hooray!
Related
So, for the past month or two my Charge has been great. Absolutely no problems that couldn't be fixed but yesterday this phone started crapping out. First, the phone got itself stuck in a bootloop without me even flashing any files/messing with system files in ANY way. I just noticed I couldn't install any apps through a file manager/market so I rebooted and the boot animation would never end.
I did a factory reset and reflashed Eclipse131, I didn't want to do that because I hadn't backed up my apps but it seemed to be the only way. Well, it fixed the bootloop issue but then EVERYTHING force closed. I literally couldn't do a thing on the phone, anything I tried opening force closed.
So, I used Odin to flash the .pit/.md5 recovery files to fix my phone and all was well... except now I can't recover my contacts from the SD card(so all my 100+ contacts are lost). I can download apps from the market again but installing them through a file manager causes a bootloop! I've never been angry at this phone but right now I'm considering throwing it at the wall, mainly for the 35+ apps, 7 homepages & 100+ contacts I lost for no apparent reason.
Could anyone help? I don't know what the hell is going on and I want to just install the .pit/.md5 again and sell this annoying thing on eBay and buy an S2/Prime when they come out.
I had some similar issues bizarre issues start recently. I would periodically have issues with the market, which I didn't think was a big deal. All of a sudden, my phone was blazing hot in my pocket. I pulled it out and was at the boot animation and it was just sitting there. I pulled the battery, booted it up, and everything start force closing all the time.
I couldn't isolate it because I had recently done a lot of new things to my phone in a short time. I was running GC FE, but installed imoseyen's kernel, V6 SC, Loopy smoothness, Badass tweaks, and the 3G enhancing script all in a short period.
Since all that, I simply ran eclipse with PBJ non-OC for a day and then flashed GC GBE with ext4 when Kejar posted it. No more issues, but I'm trying to be careful with what I install. I'm not even restoring stuff via Titanium right now, just to be safe.
Not really a solution or even a diagnosis of your issues, but I know where you're at.
I've been on Humble 1.42 for about a month now (please don't look down on me, haven't had time to switch since the drama) and I am starting to have some issues with my phone not waking. At random moments, my screen would refuse to turn on no matter what I do. It does, however, respond to me holding down the power button for a forced power off (hard reset?) Anyhow, has anyone else experienced this at all? I had a feeling it was my xfinity mobile app because I had been getting a lot of errors from it lately even though I rarely ever use it. Should I just switch to another rom or is there any other apps known to cause issues with this rom that I should be aware of?
On a side note, I have been on this forum and obsessed with android for the past year and been doing some serious thinking about making a career change into Android development. Been doing some java tutorials on youtube over the last few months and the such and think I'm about ready to start some real android app development. I credit some of the great developers on this site and the awesome experience at Dreamforce this week as the tipping point. Any ideas on additional resources I should look into?
There are a few things that could be causing this problem(that I'm aware of)
1) You may have sideloaded a "virus" app. I attempted to sideload an app once(will never do it again after what happened..) and it completely BROKE my phone. It made apps unable to isntall, the screen would take FOREVER to wake(if it ever did wake) and plenty of other problems. I tried rebooting and got stuck in a bootloop(boot animation would never end), did a factory reset and everything force closed on me so I was forced to flash the .md5/.pit to go back to bare stock and that finally fixed it.
2) Have you flashed Fuju Tweaks? This exact same thing happened when I flashed it on Gummy2.0, worked fine on Eclipse1.3.1 and even works for a lot of people on Gummy2.0 but it wouldn't work for me.
3) Try reflashing your ROM, that's how I fixed the Fuju Tweaks problem. It might fix whatever plagued your phone.
Just let me know of anything you've done recently and I'll try and diagnose the problem(if I didn't already).
Uh-Oh, a virus maybe? Yeah, I will just reflash later on, and change some passwords while I am at it.
I don't think it was that kind of virus but it definitely screwed up my phone.
Now, from what I can gather, this problem stems from a faulty or dirty Micro-USB port. I tried compressed air, but it did nothing for me.
I decided to do a complete unroot, S-ON, factory restore and call HTC to see if I could get it fixed. To my surprise, the problem vanished. Thinking I had lucked out and that fixed it, I re-rooted the phone and the problem still didn't reappear.
Then, thinking I would start small, I flashed a Sense kernel. As soon as I rebooted it went straight to Car Home and began answering in speakerphone. For laughs I went ahead and flashed MIUI then CM7, both of which exhibited the same behavior.
After all of this, I got to wondering just why the stock ROM and kernel worked but nothing third party would. Then it hit me that all the 3rd party stuff I had been using were DHD ports, and not based off the Inspire. I downloaded and flashed ClearDroid, which has an Inspire base, and the problem is once again dormant.
The only sense I can make from it is that HTC has implemented some kind of fix for shoddy USB ports in the Inspire kernel.
So now here's the question: Does anybody know anything about this, and would it be possible to implement said fix in, say, and AOSP kernel?
When you flash a Rom there is a folder created called data on the root of your phone. This contains many files that control various settings on your phone. There is a file in particular where cardock settings get synced in data/data/Com.android.providers.settings/databases/settings.db. When you sign in with your google account some of these settings get restored to the mode in which you had it in when you wiped your phone. This is what causes some people to think that parts of their old Rom are bugging out their phone, I guess in a way it is, but its googles fault. The car dock is getting resynced to being on even though you haven't done anything. In order to fix it you must use SQL editor to open the database and look for the carmode or dock settings and set them back to 0. Once you do this it the next time the phone autosyncs it will save your newer settings.
Also Im pretty sure when your rooted this setting will take effect as to where a nonrooted phone doesn't allow the permission to execute the command.
Gizmoe said:
When you flash a Rom there is a folder created called data on the root of your phone. This contains many files that control various settings on your phone. There is a file in particular where cardock settings get synced in data/data/Com.android.providers.settings/databases/settings.db. When you sign in with your google account some of these settings get restored to the mode in which you had it in when you wiped your phone. This is what causes some people to think that parts of their old Rom are bugging out their phone, I guess in a way it is, but its googles fault. The car dock is getting resynced to being on even though you haven't done anything. In order to fix it you must use SQL editor to open the database and look for the carmode or dock settings and set them back to 0. Once you do this it the next time the phone autosyncs it will save your newer settings.
Click to expand...
Click to collapse
I'll try that, but I can completely wipe my phone (cache, system, data, d-cache), flash CM 7.1.0, and without even logging into my Google account it happens.
After searching it seems this is a common problem with the phone. Some people where able to fix it and some where not. Even when it does go away for a while it will re emerge and get worse.
Some of the fixes are
1. turning airplane mode on for 10 min and then shutting it off
2. Changing chargers(dont ask me)
3. Blowing out port which you said you tried.
I am still not 100% its not some internal issue but why even bother if the hardware is malfunctioning.
I would start the warranty process and get it replaced.
Backing up to the beginning.....Are you flashing ROMs or kernels? Seems to me you are flashing ROMs but keep using the word kernel.
Why not just remove the car dock app from the ROM or use Titanium Backup to freeze it?
Agoattamer said:
Backing up to the beginning.....Are you flashing ROMs or kernels? Seems to me you are flashing ROMs but keep using the word kernel.
Why not just remove the car dock app from the ROM or use Titanium Backup to freeze it?
Click to expand...
Click to collapse
Both.
With the stock ROM and kernel, everything is fine. With the stock ROM and a DHD-based kernel it happens. With any AOSP ROM it happens.
Removing the Car Dock app keeps it from launching, but the phone still defaults to speakerphone for all calls (incoming and outgoing).
Gizmoe said:
After searching it seems this is a common problem with the phone. Some people where able to fix it and some where not. Even when it does go away for a while it will re emerge and get worse.
Some of the fixes are
1. turning airplane mode on for 10 min and then shutting it off
2. Changing chargers(dont ask me)
3. Blowing out port which you said you tried.
I am still not 100% its not some internal issue but why even bother if the hardware is malfunctioning.
I would start the warranty process and get it replaced.
Click to expand...
Click to collapse
The problem about warrantying it is when it's in a stock state, it works fine.
I've never dealt with HTC, but I can't exactly see it going over well if I call up and say "My phone acts funky when I run CyanogenMod".
The airplane mode fix is something I haven't heard before. I guess I'll give it a go.
Hey Guys -
I hope this is the correct forum to post this in - its the closest I could find...
After owning an Nvidia Shield (now "Portable") and loving it, I went ahead and purchased an Nvidia Tablet which came in 3-4 days ago. It's great except for that without the Controller (which is on Backorder ), you really can't do anything a standard tablet doesn't do.
Once updated, I rooted it and proceeded to install all the tools and apps I use. One thing I had always wanted to try out was the Modded Google Play. I saw that it had an installer so installed it and applied the modded version. Once back up, I had some difficulty with stability so went back to the original version installed (4.8.20.)
Since then, sometimes when I boot up, WiFi doesn't work and is disabled. I'm not saying I can't connect, but that it's in the "Off" position and greyed out to where I cannot turn it on! After a 2nd reboot, it would work again.
Yesterday, I rebooted and it was disabled again. This time, though, no matter how many times I restarted, it was still disabled!! I tried uninstalling / reinstalling Google Play a few more times as well as a few other reboots with no luck.
I will also say that I tried one more thing which may be the cause. I tried out Freedom to check it out, but it crashed when opening plus I found out it takes away functionality so uninstalled it. After uninstall, I found out the hard way that I had to rename my hosts file to get online working. At that point, though, WiFi would at least be enabled.
Any suggestions for what I can do? If I need to restore to OEM, I will - I just need to know the correct process as I am rooted. I'm on build KOT49H.20258_426.6902.
Thanks!
I had this happen when I first booted mine up. Then again when I unlocked the bootloader. I didn't do anything other then keep trying and it came on. It hasn't done it since.
Sent from my XT1060 using Tapatalk
Thanks for the reply. I ended up just performing a full reset and starting from scratch. At least I know what I want installed on it, now. That resolved the issue and it retained the root.
Thanks Guys
I was really worried about it, I chatted with nvidia support and they said to return it to the store. For whatever reason it started working, and hasn't done it since. I've seen a couple posts on it, so it might be a software bug.
Sent from my SHIELD Tablet using Tapatalk
hi everyone! I just wanted to explain my situation here so that maybe someone can help me understand what is happening.
I own the Exynos variant of this phone 12/256.
Being a huge fan of debloating my entire life, i got the phone and after some time, seeing that the battery life won't improve, I started digging.
At first, i have removed MANY apps that are useless, but have never touched system related apps, maybe bixby or smth. Nothing happened. Then the OneUi 5.0 came, beta, installed it, then the stable came, installed it, had a factory reset done to start fresh and i got to debloating again. And for about two weeks everything worked smoothly. Then i was at work one evening and i started seeing my phone acting weird, mobile data going on and off(kinda always on 4g+ at work) so i decided to restart the phone. Clicked restart, put it in my pocket and after 5 mins i felt it warm in my pocket. Checked it and saw it was restarting in a loop and after a few more restarts it said " rescue party/ etc/etc, your phone failed to restart multiple times bla bla". The only way to get it up and running was to delete all apps inside that menu then the phone would boot in safe mode so i could backup my data, then i had to factory reset it again. This happened 3 times, in a 1.5 week period. Last time i debloated, i only uninstalled youtube, youtube music, microsoft onedrive, etc etc. Haven't even touched anything related to a system app, because in that menu it would say some system files are missing or smth like that. This evening I ve got the update with the November security patch, downloaded it, installed it and now it's looping again.
Does anyone know what might be the cause? Because obviously i didnt get rid of any system app this time.
Contact Samsung support. Possibly to be replaced under warranty
Maybe just download a firmware that doesn't have much bloat then see if the issue keeps happening without you debloating. If it doesn't happen anymore and then you start debloating things and it happens, then you know your problem.
More than likely you've de-bloated something you shouldn't have.
Back up all your data (if you're still able to), then factory reset & flash clean stock ROM.
Thereafter, flash a de-bloated custom ROM or do a very careful de-bloat yourself (plenty of guides on XDA).
Everything I've debloated was done side by side to a parallel xda thread for samsung debloating, it's not like it was 100% out of my head. Disabling bixby, microsoft onedrive, samsung free, upday, ar core elements inside and out of the camera, live messages from the s pen doesnt look to me like it should make the phone go bootlooping.
I've flashed the first stable firmware last night after the incident, updated it to the latest november update and I'm keeping an eye on it. If it randomly goes bootlooping and to rescue party, I'm taking it to samsung in my city.
stefancrisxd98 said:
Everything I've debloated was done side by side to a parallel xda thread for samsung debloating, it's not like it was 100% out of my head. Disabling bixby, microsoft onedrive, samsung free, upday, ar core elements inside and out of the camera, live messages from the s pen doesnt look to me like it should make the phone go bootlooping.
I've flashed the first stable firmware last night after the incident, updated it to the latest november update and I'm keeping an eye on it. If it randomly goes bootlooping and to rescue party, I'm taking it to samsung in my city.
Click to expand...
Click to collapse
dont root your phone, you might lose your warranty.
i see you flashed the firmware so keep an eye one the phone, debloating shouldnt have to do anything with this issue, a lot of us debload and have not faced this kind of issues.
i did debloat mine, i bought my phone with A12 and it took me 2 days to set it up including the date transfer and debloat, then i received A13 which i installed and kept using it without a reset which i should have done but i was very busy.
I haven't rooted this one, not yet because it's new and I don't need anything root acces can give me at this popoint. Although I have rooted many phones before, including samsung, I've never encountered this before, even though I've seen it was introduced by google in A11 or smth. I dont know.
What variant is your phone? Maybe you can give me a file with what you've debloated so far to compare.