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

[Q] Phone won't display home screen.

So I was looking through the topics in this part of the forum today, and I saw "[Q] What is causing "Communication Failed" error?" (It won't let me post the link to it?) I followed the link in that topic and did what that guy said would help, and after doing that I restarted my phone. It did all of the startup animations correctly, I can still access the recovery menu out of it, but when I get past the startup animations, I'm just greeted with a black screen. The buttons on the bottom of the phone are lit up, but the screen gives no response. I can't turn it off without taking out the battery, and that doesn't help. If possible I'd like to try to fix this without sending my phone in, or without deleting the user data. Any fixes for this?

I would try re-downloading the ROM you want to use and then re-install it. But maybe there's a better fix, that's just what I've done whenever I encounter something strange.

sschrupp said:
I would try re-downloading the ROM you want to use and then re-install it. But maybe there's a better fix, that's just what I've done whenever I encounter something strange.
Click to expand...
Click to collapse
I can't exactly put anything onto my phone with this problem. I can't access the screen at all past the startup animations. It's just black.

Not Bricked!
You have a few options as it seems your phone is "on" and should be recognized by your computer still.
What was it you were doing to the phone before it started doing this behavior.. wasn't quite clear on that....
If it was a mod to change your framework-res.apk. You can find the "stock" one in the ROM you originally downloaded and revert back to stock by doing an ADB Push to your /system/media folder.
Or... you will need to flash your phone back to stock - which means you will need to go here and download Odin and run it.
Always helps to have that "plan b". Bottom line though - your phone isn't bricked and you should be able to restore it and continue on. But... please note that ODIN will wipe your phone and anything you had on it will go bye bye.

androidforums.com/captivate-support-troubleshooting/217905-cant-connect-t-server-updates.html
I followed the advice on how to fix that problem in the second post in that topic. When I restarted my phone the screen just ended up going black. I'm going to try that Odin thing, I hope it works.
e. It's kinda annoying how I can't post links.
Ok Edit again, I've tried the Odin thing, and it just isn't working. Now whenever I try to put my Simcard back in, It doesn't even do the startup things, it just goes to that Phone Caution symbol PC picture thing. I'm worried that I'd have to go get a replacement.

Can you please provide us with a list of everything you have done to your phone and how you tried to use Odin? That will help us help you. Please be specific, this will get you the help you need. I read the link, did you use ADB or the first method in that thread? Sounds like you messed up while trying to fix your device manager. I am not sure how it is you tried to use Odin, try using a rear usb port, Odin can be a pain, make sure you have the drivers installed.

Ok, Here's a list of what I've done to my phone over the past few days.
1. I rooted it.
2. I kinda sorta half-assed the process of allowing me to put on Non-Market apps onto my phone, I made it so that the settings.db file had the permissions all set up, but I never replaced the first settings.db file. (It's just sitting on my phone's interal SD card.)
3. I tried to do that Non-ADB method listed in that topic I linked to. After that I started having these problems.
4. I accidently ended up clearing the Data cache through the recovery menu thing. Just an accidental moving of the buttons. It didn't seem to effect anything.
5. I booted the phone into recovery mode and tried the Odin thing. It got stuck at File Analysis, and I tried again. It still got stuck, and I let it continue trying it while I was eating dinner. After I got back it was still on that, so I took out the USB cord and phone battery and put the Sim card back in. When I try to boot it up it goes to that PC error phone thing. (I can't exactly get an image of it, I hope you know what I'm talking about.)
And that's all I've done to it. I'd try a different USB port, but I don't have any more. I'd try my other computer, but that's a Linux machine, and Odin is a Windows/DOS executable file. I'm pretty sure the drivers are installed correctly, as I had been doing stuff with the phone via USB just yesterday.
I hope that's enough detail to help figure out something.

I'd hate to doulbe post, but I really really do need the help with this. If any of you have any advice for it all, please, feel free to contribute. If there is no fix for this, and my phone is actually bricked, just let me know so I can go get a replacement.

Did you make sure you had odin started up BEFORE you put your phone in download mode? Odin is very touchy and you have to do things exactly right or it won't work.

Yes, I've made sure to follow all of the steps right to the last peroid. I'm probably just going to have to go get a replacement anyway.

[Q] Galaxy S Plus - Stuck in Reboot loop

Hi
I got a rooted Samsung galaxy plus 9001.
I installed font changer and busy box.
With the font changer i chose a ttf font from the internal memory card, and after applying it, i got the pop up menu reboot now.
After clicking on reboot now my phone stuck in reboot loop.
I can access android recovery menu, i treid wipe all user data but still stuck in reboot loop.
Please help me guys.

You'll have to reinstall the rom you were using... that should get you out of bootloop. If that doesn't work, do factory defaults (you'll lose all apps and settings!) and install the original rom again (or for instance XXKPS).
One more tip: always make a (cwm/feamod) backup before changing system defaults
Regards,
Nika.

Thank you.. Thanks alot

nikagl said:
You'll have to reinstall the rom you were using... that should get you out of bootloop. If that doesn't work, do factory defaults (you'll lose all apps and settings!) and install the original rom again (or for instance XXKPS).
One more tip: always make a (cwm/feamod) backup before changing system defaults
Regards,
Nika.
Click to expand...
Click to collapse
any link to step by step instructions on how to do this available anywhere?
i have similar boot loop problem.

I doubt anyone has created that. How did you get into the loop?
Sent from my GT-I9001 using xda premium

Boot Loop
When you are stuck in the boot loop:
1. Take out the battery and re-insert it.
2. Put the phone in download mode (using 3-button combo - down+home+power)
3. Open Odin, and reinstall the stock firmware (using all 3 md5 files: PDA, CSC and PHONE); you will be able to find the files in the stock firmware 2.3.5 from the post in XDA-stock gingerbread roms for i9000.
4. After you have done this, root your phone, install custom kernel, and then install custom firmware through custom recovery menu.
Thats the way i did it....i dunno if there is a short cut to it.
Hope it helps!

I also find bootloop can be resolved by going into download as stated by puneetgandhi and flash a VOODOO KERNEL using ODIN (it goes on PDA).
Then booting to recovery and turning off all lags.

Link to the stock firmware page i was referring to:
Link to the stock firmware page i was referring to:
http://forum.xda-developers.com/showthread.php?t=846913

nikagl said:
I doubt anyone has created that. How did you get into the loop?
Click to expand...
Click to collapse
No idea, it has been going in and out of boot loops a few times already for last few months works fine for ages. All of a sudden it would starts lagging on an app or when texting and reboots into a loop
although i never had the problem on froyo only in gingerbread (a few week or so after i got my phone back from repair shop, they upgraded it to gingerbread without my notification, but since i had voodoo on before on froyo i don't know, maybe they updated it wrongly ).
First time i fixed it with a fix on here about transferring a system file through odin.
second time it fixed itself after i left it for a day as i didn't have time to fix it .
this time i finally fixed it with a factory reset for the 4th or 5th time in a row, after wiping cache and so on, didn't work first few times.
So not sure whats causing it, could be a failing internal memory card i suppose or overheating corrupting the memory, hoping its a software issue that the factory reset will permanently fix (but doubt it).

If you were on Froyo, please look or create another thread for I9000 Samsung Galaxy S. This thread is about Samsung Galaxy S plus I9001... That's the device I own, and stuff like Voodoo and Froyo do not exist on SGS+ (and I have no experience with - probably other with an I9000/SGS do).

[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

Captivate gets stuck with black screen after booting. No response to anything

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.