Database Develop

My phone has a blackscreen after JPK update

I'd like to start of saying I've read almost every thread regarding this and I understand that there's a good chance that my internal SD is permanently blown up I'd just like to establish some things here that may put me in a different boat.
hatdrawn said:
I just want to be clear ...
So I last night I flashed JPK, PDA/MODEM/CSC with 512pit installed latest oneclick lag fix 2.1.1, SGS tools and other basic apps. Was running perfect all night except that RAM seemed to be eaten up easily.
Then this morning Advanced Task Killer Froyo Beta started acting up. So I tried a reboot and then I got this black screen issue.
Tried reflashing JPK again. Just successfully flashed JH2 but still the black screen.
Recovery/Download mode work. With 2.2 recovery mode I was getting SDCARD connect errors on screen, but since JH2 I don't see them. Tried wiping cache partition, and factory reset. Still black screen. I've tried without external SD and SIM and just recently with external SD.
In this JH2 recovery mode "update media, finished" and Apllying MultiCSC works properly too. When in recovery mode, Kies tries to recognize it, but boot/blackscreen I get nothing.
Is there anything else I can try? I have read through this whole thread, but it's a lot to read and understand. Anything with ADB? When in recovery mode ADB shell returns a device not found
Click to expand...
Click to collapse
Currently it's back on JPK for the time being and using ADB I can finally get it to recognize there is a device, but it says it's offline. What does this mean? Does this mean that it wasn't in debug mode when it crashed? Or something else? At this point does this help me at all. At one point I did get internal and external drives to show up in my computer, but I couldn't acess them. As if they weren't mounted. Actually, that's how it's behaving now.
Can anyone think of anything else for me to TRY at least? I don't want to give up just yet. I realize all signs point to bricked but I just want to try a few more things.
Any tips are appreciated.
Thank you very much

Constant crashes after firmware update

Hi guys, I just updated to the new version through Kies. As soon as my phone booted and I exited lock screen, a lot of popups of processes that crashed show up. This includes android.process.acore, com.google.processes.gapps, Daily Briefing, calendar... pretty much everything shows up and I don't have access to anything on the phone. Apparently usb debug got back on so I can't get kies to recognize the phone.
I have a contract-free galaxy s from germany. Rooted. Uninstalled ryans lag fix through market before upgrading. I don't know what I did wrong.
What can I do? Thank you very much!

ClashBR said:
Hi guys, I just updated to the new version through Kies. As soon as my phone booted and I exited lock screen, a lot of popups of processes that crashed show up. This includes android.process.acore, com.google.processes.gapps, Daily Briefing, calendar... pretty much everything shows up and I don't have access to anything on the phone. Apparently usb debug got back on so I can't get kies to recognize the phone.
I have a contract-free galaxy s from germany. Rooted. Uninstalled ryans lag fix through market before upgrading. I don't know what I did wrong.
What can I do? Thank you very much!
Click to expand...
Click to collapse
Try a factory reset. It will wipe your phone.

dakine said:
Try a factory reset. It will wipe your phone.
Click to expand...
Click to collapse
Just did a factory reset via recovery mode. Did not solve the problem. Weird thing: How can it still know remember what's my lockscreen password if it was factory reset?

Have the same problem here... Before Factory reset the phone was stuck at the Big S, after reset, it started, I could enter my pin and then the force closes started
Now downloading firmware and hope restoring via Odin will work. Luckily downoad mode still works

Hey mate can you please provide links of firmware you are using and odin? Please report if you have sucess too. Thanks!

check the faq:
forum.xda-developers.com/showthread.php?t=723596

Go into the phone settings, manage applications, Choose GMail, clear the data. Go back and choose GMail Storage and choose to clear that data. Try to force a sync.
Then reboot the phone.

Chronos12 said:
Go into the phone settings, manage applications, Choose GMail, clear the data. Go back and choose GMail Storage and choose to clear that data. Try to force a sync.
Then reboot the phone.
Click to expand...
Click to collapse
I can't do anything on my phone mate, the popups won't stop showing up
thanks for the link

tried flashing directly from ODIN, now it got even worse
error is at booting
E:Can't mount /dev/block/st110 (invalid argument) E:copy_dbdata_media:Can't mount DBDATA
Help? I have tried with 512.pic and 803.pic, both failed

Aww, that's bad.
Here all went well. Used Odin to flash back to the original FW I had installed (XXJF3), then used kies to go again to JM2 and just finished installing Froyo
Now to get all my apps back. Hopefully Titanium Backup does what it promises

dabeetle said:
Aww, that's bad.
Here all went well. Used Odin to flash back to the original FW I had installed (XXJF3), then used kies to go again to JM2 and just finished installing Froyo
Now to get all my apps back. Hopefully Titanium Backup does what it promises
Click to expand...
Click to collapse
restore apps only, do not restore settings, else it will crash or cause other weird problems

help rooted samsung captivate wont fully boot

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

[Q] Repair Galaxy Note N7000 SystemUI / TouchWiz home stopped working errors?

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

Please help in translating this logcat

I just recently switched from HTC to this Galaxy S3 i8910 mini and in some kind of a problem.
The phone would reboot after a period of time in NORMAL mode. I think an app installed is triggering the event, after the reboot any changes you made would revert the phone settings files to it's last state (kind of similar to Windows TEMP profile) wherein it is not remembering or saving any changes made to it.
I have tried anything I can find in the internet including flashing variou PIT and TAR files but none worked. So I tried grabbing a logcat and just let it run until the phone does the reboot.
Currently the phone can boot to SAFE mode and will not boot not until I try to uninstall ANY application that was downloaded by the previous owner. Worth mentioning also that even after factory reset and performing wipe via stock recovery is of no help at all. I can get to download mode and recovery mode with no problem it's just with the reboots and reloading of it's last state is the problem.
I am suspecting that this thing maybe suffering from a bad NAND set to R/O but I can't conclude yet until I can have the logcat be read by someone who knows how to. I am not a developer knows not much about codes so any help will be appreciated.
I have read about this issue in this thread http://forum.xda-developers.com/showthread.php?t=2562596 and found no solution yet so I am trying my luck if there is anyone that can help. TIA. :highfive:

auxdefault said:
I just recently switched from HTC to this Galaxy S3 i8910 mini and in some kind of a problem.
The phone would reboot after a period of time in NORMAL mode. I think an app installed is triggering the event, after the reboot any changes you made would revert the phone settings files to it's last state (kind of similar to Windows TEMP profile) wherein it is not remembering or saving any changes made to it.
I have tried anything I can find in the internet including flashing variou PIT and TAR files but none worked. So I tried grabbing a logcat and just let it run until the phone does the reboot.
Currently the phone can boot to SAFE mode and will not boot not until I try to uninstall ANY application that was downloaded by the previous owner. Worth mentioning also that even after factory reset and performing wipe via stock recovery is of no help at all. I can get to download mode and recovery mode with no problem it's just with the reboots and reloading of it's last state is the problem.
I am suspecting that this thing maybe suffering from a bad NAND set to R/O but I can't conclude yet until I can have the logcat be read by someone who knows how to. I am not a developer knows not much about codes so any help will be appreciated.
I have read about this issue in this thread http://forum.xda-developers.com/showthread.php?t=2562596 and found no solution yet so I am trying my luck if there is anyone that can help. TIA. :highfive:
Click to expand...
Click to collapse
that is a long log to go through, what time did it reboot at?

efaustino84 said:
that is a long log to go through, what time did it reboot at?
Click to expand...
Click to collapse
Hi efaustino,
First of all thank you for taking the time to respond. About the time, I am unsure of it. I normally happens within a time frame of 2 mins or less from the time of first boot.
In addition to that, I have recently tried re-flashing CM 11 from @mcclaw and got a message in download mode that says movi_write card status:2 (1) start_blk:6144 in red.
I have found out in even in SAFEMODE I am able to recreate the reboot by making the phone read the internal memory information, such actions would trigger a reboot:
Within Settings:
-Going to Applications Manager
-Going to Storage
-Uninstalling any application in safemode

auxdefault said:
Hi efaustino,
First of all thank you for taking the time to respond. About the time, I am unsure of it. I normally happens within a time frame of 2 mins or less from the time of first boot.
In addition to that, I have recently tried re-flashing CM 11 from @mcclaw and got a message in download mode that says movi_write card status:2 (1) start_blk:6144 in red.
I have found out in even in SAFEMODE I am able to recreate the reboot by making the phone read the internal memory information, such actions would trigger a reboot:
Within Settings:
-Going to Applications Manager
-Going to Storage
-Uninstalling any application in safemode
Click to expand...
Click to collapse
something wrong with the locations it tries to reference from memory
when you tried the various pit files etc did you select re-partition when using odin?

efaustino84 said:
something wrong with the locations it tries to reference from memory
when you tried the various pit files etc did you select re-partition when using odin?
Click to expand...
Click to collapse
I was too busy with work and only got the chance to check your response. Yes I did, I even tried wiping NAND but to no avail. Re-Partition with only a pit file in place will show successful but when a .pda file is placed together with the .pit file Odin will fail in writing to NAND.
With NAND wiping checked, Odin will get stuck in Erasing for a few minutes and would just fail the process. I'm running out of idea on how to turn this expensive brick to a phone again. :silly: