Yesterday my phone started acting up:
- Applications started failing
- Couldn't uninstall apps (it acted like they uninstalled, but they were back after reboot)
I tried wiping from recovery mode, but all apps are still there
I've even tried using Odin to do a master clear and reflash to stock, yet all the apps are still there. All the startup apps crash when I restart the phone, including the launcher, so the phone is unusable.
I'm desperate here, as I'm without a phone... any help is greatly appreciated
Ok put the phone in download mode but don't reboot to download mode where you see the yellow droid. Make sure you are at the home screen. Then run Odin then plug the phone in and make sure odin recognizes it. Then hit master clear and the phone will be wiped. Then put it back to download mode, with the yellow droid and then flash back to stock.
That's exactly what I've already done, but I'll try it again
Actually, follow up question; how do I put it into download mode without going to the yellow screen?
Another edit: did you mean to say debugging mode?
Yeah sorry I keep referring to usb debugging as download mode sorry for that.
setting > applications > development > usb debugging
ok, completed the master clear. It stated everything was successful. After the reboot, the phone came back, all apps still installed, and all apps still trying to launch on startup and FC-ing immediately. Going to try the reflash to stock now
Same thing... after master clear and reflashing, everything is still there...
Do a facotry reset from the privacy menu and see how that works if not then reboot into recovery and clear data/cache and see if that does anything. Master clear completely wipes the phone there is nothing on it at all. Can you get into any program to uninstall stuff.
I would take it back and tell them its got a mind of its own.
I've tried all of those things multiple times. When using uninstall programs, the device acts like it's uninstalling, but does it way too quickly and says it's successful. They're still there, though, and after I reboot they show up again.
brookssw said:
I've tried all of those things multiple times. When using uninstall programs, the device acts like it's uninstalling, but does it way too quickly and says it's successful. They're still there, though, and after I reboot they show up again.
Click to expand...
Click to collapse
Ok here is what you do...Menu/settings/sd card and phone storage..scroll to internal storage and unmount sd card...then format sd card...Then reboot in to downlaod mode and reflash with odin 1 click...after it boots up reboot into recovery mode and clear cache and user data...then reboot and you will be good to go...You willl lose all your stuff on your internal storage so back up anything important...
Sadly this didn't do the trick either, and I unmounted/formatted the internal twice for good measure. It's like there's a hardware problem, or the storage is locked out somehow. I gave up earlier today and called in the warranty, so there's a refurb on the way now. I hate to give up, but I think it was the only remaining option
Related
I have a Bell Vibrant. Voodoo Lagfix and rooted.
I unapplied the lagfix by creating a folder inside the Voodoo folder called "disable lagfix". Then rebooted the phone. After the lengthy disable process, the phone booted back up. I then went into settings and formatted the Internal SD card.
Then I rebooted the phone, went into 3 button recovery mode, and did a factory reset and cache wipe.
Now when the phone boots back up, it still detects the voodoo lagfix. Then boots up but all I get are constant force close. I can't do anything in the phone other than continually press the force close button.
In particular, it loops between com.google.process.gapps and android.process.media
What can I do to get my phone working again?
Thanks!
I had this same problem on monday, to fix it i used the REGEDIT trick on kies to make it think it was an older version of firmware, and reflash the latest firmware on kies. Now everything is fixed and working well.
How did you get Kies to recognize the phone, without being able to select Kies mode when attaching USB cable to the phone?
davanw said:
How did you get Kies to recognize the phone, without being able to select Kies mode when attaching USB cable to the phone?
Click to expand...
Click to collapse
I patiently went to do another factory reset through the privacy settings tab, took like 5 minutes of advancing when there was a short gap before another fc popped up. Once that was done, the force closes slowed down enough that I could connect it to kies. took patience but eventually I got it working
Same problem here. Re-flashed with Odin.
Sent from my GT-I9000 using XDA App
Hi,
I want to say that everyone is very helpful in this forum and you all rock. I'm having some problems with my rooted samsung captivate. I installed the I9000 Full rom, and it was running fine for a few days then I notice it was very sluggish, so I did a factory restore, but data and apps didn't delete. So I then when in to recovery (R2) and deleted cache and all user data files, then it did a factory restore, and it went in boot up pass the att and samsung S i9000 screen and when to the lock screen, but once I unlock the phone, its just in the black screen, when I click and hold on to the home button it goes to recent, no recnet application and under Task Manager, I have 0 active applications. It won't load any programs or apps. I tried restoring the phone by holding the down volume key and power on button, it goes to R2 recovery and then reinstall package, but it can't find the package. I have it on the memory card, but I guess I deleted it from the internal memory when I did a factory restore. Am I screw, or can someone guide me through this and fix my fone. Thanks in advance. XDA Rules.
Odin one click back to stock, assuming you can get into download mode. Also do a master clear just to be sure. A fresh start might be just what your Captivate needs.
Sent from my SAMSUNG-SGH-I897 using XDA App
The same thing happened to me yesterday. Phone was on, battery fully charged. I got on my flight and left it on (forgot I guess) and when I got off the flight, the screen was black. I'll also add, that over the past 3 days the phone was starting to get extremely sluggish (for no reason that I can think of). But back to the rest of the story...
I couldn't get it to turn on, so I pulled the battery and tried again. This time I got the AT&T logo and the Samsung animation. Once the animation was completed the screen goes black.
The phone is still on. How do I know? If I touch any of the bottom buttons they light up.... and stay lit up until I do a battery pull.
Deleted/cleared everything, same behaviour.
I tried reflashing JI6, it works but fails to reinstall the packages, otherwise same behaviour.
I tried reflashing JF6, same behaviour.
The flashes always succeed, but always end up in failure.
Now for the interesting part. I went into recovery mode on JI6. I try to format the internal /sdcard, I get a message that it cannot mount /sdcard /dev... not found.
So to recap, phone not working, recovery mode available, download mode available. adb doesn't seem to be working, but if someone can tell me how to access the phone with "adb shell" while in recovery mode, I might be able to diagnose why /dev... is not mounting... Or at least how I could fix it using adb.
Any help would be appreciated. I'm traveling and needless to say, this is a huge inconvenience, I'm lucky I had my backup phone to at least be able to get online and be able to make calls.
HI,
thanks for quick response. I can get to the recovery mode, where the android holding the shovel. But when I load Odin one click, it don't seem to detect and do anything. o success 0 failed. I installed the samsung captivate windows 7 drivers, the funny thing is when I plug my brink phone in the usb port, it say unrecongize usb. Any other suggestions. Thanks
hksmr2 said:
HI,
thanks for quick response. I can get to the recovery mode, where the android holding the shovel. But when I load Odin one click, it don't seem to detect and do anything. o success 0 failed. I installed the samsung captivate windows 7 drivers, the funny thing is when I plug my brink phone in the usb port, it say unrecongize usb. Any other suggestions. Thanks
Click to expand...
Click to collapse
the shovel is NOT recovery mode, it is download mode.
have ODIN running BEFORE you get your phone in download mode
Can I factory reset the phone using ADB? I have root access but I am unsure what they would be.
The reason I ask is that the phone has a broken screen but still works fine otherwise, so I want to wipe it clean.
Unfortunately without a screen I can't do anything in recovery or through traditional methods...
Would adb be the easiest way? I was thinking about using ODIN but I wouldn't be able to verify the firmware worked or had cleared my data on a bad flash?
Just to update this, I nearly managed this but ended up still not wiping the phone and i'm slightly stuck.
I downloaded the following program:
http://code.google.com/p/androidscreencast/
Since I had developer options installed I rebooted into recovery (I had SpeedMod installed). Luckily this program displayed the screen and I could navigate the options and wipe the phone.... (Factory reset in recovery without Internal Storage ).
At that point I rebooted the phone and now i've lost ADB... and whilst I have recovery the developer options are not ticked so I cannot use the screencast app anymore.
I've tried KIES but I cannot get it to connect, it sounds like the MTP app starts up, and KIES inserts a registry entry for the phone but will not connect....
Any ideas on how I can wipe the internal storage? It's the last step of the process.
Hello everyone,
I've been literally 12 hours searching for possible answers on how to repair my Galaxy Note N7000 which from what I've concluded, has a problem that can be easily repaired but I've found nothing but limitations when I have a go at it. It doesn't seem to be bricked as I can still access recovery mode, download mode and it effectively boots, it's only giving me errors.
Here's what happened:
1) I tried rooting it using UnlockRoot PRO. Paid the PRO version, detected the device. Later I find it says the N7000 with 4.1.2 is not compatible so the rooting process was never completed, so I rooted it using Root_SuperSU.0.95.Only-signed and it worked just fine.
2) Everything worked fine, downloaded Andromizer to customize the phone.
3) Changed the DPI size to test it, then went to Developer Options and changed the Animation scales to 0.5 to make it all run faster.
4) Rebooted the device. Once I did, I got nothing but "SystemUI has stopped working" together with "TouchWiz home has stopped working errors".
I checked around the web and so far, what I've found (and tried) is this:
1) There seems to be a bug related to TouchWiz and the Animation Scale option (or perhaps the DPI size option in Andromizer). So I tried to do a wipe data / factory reset through recovery mode.
2) When trying the wipe data / factory reset through recovery mode, I rebooted the phone, only to find the SAME errors after I registered everything.
3) First option that came to mind was to wipe everything and immediatly reinstall the Official JellyBean 4.1.2 firmware (at this point I want to pretty much unroot the device as I didn't know it was going to give me so much trouble). When I tried that, I realized that SUDDENLY, Odin (nor Heimdall) are NOT detecting the phone in download mode. I'm guessing it's because USB Debugging is turned off but, I can't access the phone settings. It's my only logical conclusion, although it should be turned on given I could install PhilZ Custom Recovery later.
4) I search around the web and it says it's a driver problem. So I uninstall everything, run CCleaner, USBDeview to uninstall everything related to the Samsung Galaxy. Reboot. Install drivers again. Reboot. Plug booted phone and let Windows detect the device, installed successfully. Reboot in download mode. Let windows detect the device, installed successfully. Run Odin: DEVICE NOT DETECTED. (It does detect it while it's booted though, only it doesn't work for **** obviously).
I've literally tried everything. I've tried checking for a way to install the firmware via Recovery Mode instead of Download Mode. I've tried checking for a way to remotely access the device and mod the settings from there using ADB, and I get the same problem in ADB, doesn't detect the device.
Also tried to reset settings to normal via PhilZ Custom Recovery which I managed to install later.
Isn't there just a way to reset all settings to normal? Shouldn't a factory reset do this? How can I get SOMETHING to work and try to recover the phone? Any Aroma Recovery Script? Any way to mess with the system folder and modify settings manually via notepad or something since due to the SystemUI / TouchWiz home errors I can't access the phone settings?
I'm barely awake at this point. Can't believe I've stressed myself this much. Please help. This is beyond retarded.
Thank you,
Z
i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping
I read the post but it seems you have done a lot of things and nothing worked. So what is the situation right now? You can boot as normal but cannot get any icons or settings as sysUI and TW crashes?
Try installing GB ROM then wipe/cache first. If good, root GB ROM then do full wipe. Then test ROM for crashing.
If good then install JB rom and test. Let us know.
unable to enter phone setting ？ then just simply look for a secsetting.apk for ur version then replace it n set the permission rw-r--r--
You could use adb to modify your build.prop
Sent from my SGNote
Makrilli said:
You could use adb to modify your build.prop
Sent from my SGNote
Click to expand...
Click to collapse
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.
nice to hear that you had this one fixed
Glad to hear its working now.
n7000 touchwiz home stopped
Zardonic said:
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.
Click to expand...
Click to collapse
hi.... im having the same problem as yours. i dont know what to do
lulu2050 said:
i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping
Click to expand...
Click to collapse
I have tried to upgrade my touchwiz to the new one, but got the danger message, would clearing the cache help?
Sent from my SM-N910C using Tapatalk
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Titerepayaso said:
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Click to expand...
Click to collapse
Sounds pretty accurate. You'll have to get a jig to get in download mode, flash stock Odin KK4 to fix w/e happened during your testing.
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Titerepayaso said:
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Click to expand...
Click to collapse
Make a backup with ADB.
Once that's done, push download mode with it and get Odin KK4 (without bootloaders). You'll have to start from there to fix w/e went wrong.
You don't have to wipe your sd doing so but you will lose your apps and such. If you backed up your phone with your Play Store account, it will re-download your apps as you're done booting up.
To get back up where you were, grab Corn Kernel, flash it with Odin 1.87 and then follow the full instructions of the ROM you wanna use.