Database Develop

[q] need help! Black screen on my verizon galaxy tab 7

I tried a flash and think i messed my tab...now its just a black screen with a faint light in the background like its on but its no images.......my battery icon pops up then distorts away and thats it ....can get into download mode but not recovery.....tried holding all 3 buttons got this lil android dude in the corner with a sign sayin something about power reset but cant select nothing......help me please......

Put it in d/l mode and flash one of the stock roms with Heimdall.
D

i tried a stock flash with heimdall it flashed successfully but i still get the SAMSUNG logo that flashes and go away,buttons light up at the bottom,can go in download mode but not reboot mode,phone stay on with a faint light ,so i assume that its on somehow.....help

Did you follow this exactly?
http://forum.xda-developers.com/showthread.php?t=967175
One thing I missed here before was to wipe data and cache. Otherwise I go into boot loop.

how to get recovery mode
i cant wipe nothing because i cant get to recovery,just download mode

done it step by step
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......

chubbyflood said:
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
Click to expand...
Click to collapse
Use UnBrickable Mod
http://forum.xda-developers.com/showthread.php?t=1341753

Although you get a black screen on boot, it might still be working....
Chubbyflood,
If you are in the same situation as I am then the tab is still working, you are just getting black screen on boot up. It played tricks on me for ages when I was first rooting by tablet; but it turned out it is just the boot up screen that isn't showing.
This is my situation:
-Press and hold Power button to turn on.
-I see the Galaxy Tab / Samsung initial boot image for about 1 second, and also hear the "boot chime"
-Then the screen goes completely blank (but you can tell it is still on with a little light showing.
-The four "hard button" lights will light up briefly a couple times
-Wait approximately 30 seconds to a minute (to be safe and give the tablet time to boot up - it is actually booting up)
-Tab the Power button once, to turn the tablet off (now the screen is clearly off)
-Tab the Power button again, and the tablet will be up and running as normal.
I am guessing the boot animation / images are failing in some way, but the tablet is booting up as normal.
I've just learned to live with it, because I haven't had a chance to figure out what's going on, but it honestly took me a good hour or so, and a few (unnecessary) flashes, before I realized the thing was up and running fine, it just need to have the button pressed on and off.
One final thing to mention; don't have the tablet plugged into anything. I seem to remember leaving it plugged into the PC didn't help (I think).
Hope that makes sense.
Cheers
Ed.

Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.

Juiced_RL said:
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Click to expand...
Click to collapse
Have you found a resolution to this? Mine tab is doing the exact same thing as yours after the cubed rom.

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.

[Q] GT-N7100 multiple issues

Hi guys, first of all this is my first post here and won't be my last.
I am an Apple/iPhone long time user and want to tryout Android, just because I think it's time for a change , without knowing if I could get used to the new OS and wanting to spend as less as possible on this "endeavor" I bought a second hand Galaxy Note 2 GT-N7100 from a friend, the phone worked perfectly when I bought it, it had Android 4.1.2 on it and I wanted to update it to 4.4.2, did some research on the net about this (learned about the locked bootloader - this wasn't an issue for me coming from the iPhone) and updated the phone using Kies - and this is were the fun begins.
The update failed, and the phone was softbricked but could still go into download and recovery mode, after reading a few hours on the internet, I used Odin to flash a 4.3 stock rom for the n7100 which I downloaded from samsung-updates, the software got installed on the phone but it was very laggy (with the phone opened but locked, when I pressed the power button it took about 7-8 seconds for the display to light-up, the animations were very sluggish and phone was unusable).
I installed another ROM, using Odin, this time a 4.4.2, with the same results (every time I reset to factory setting and wipe cache from recovery - this didn't help).
I then installed clockwork recovery and rooted the phone then installed cyanogenmod 10.1 which worked almost ok but if i locked the phone after a few seconds the phone would restart, wipe cache/restore factory settings didn't help, i installed it again hoping it would be just an issue with the installation but had the same result, phone would restart.
I've followed all tutorials I could find related to this phone and this issue, installed several patches, reinstalled several stock roms, installed Criskelo rom, all with the same result, the phone is very very very slow and freezez after a while or it restarts after i lock the phone.
So, let me just give u some history on the phone, enumerate the symptoms and where I am right now:
History:
The phone was bought from Vodafone Romania, was never rooted and was never updated (before me ) and still has 3 months warranty.
Symptoms:
- Phone is very slow, unusable
- Freezes after the display is locked
- it is not recognized in windows, when I connect it i can hear the windows connect chime but the phone storage is not mounted, in device manager the phone is recognised as "cdc communication interface" which is not installed - i have the samsung drivers installed, and i have tried on other PC's with the same result, I also tried with several data cables - same thing - the phone works ok when in recovery/download mode
- sometimes when the phone is connected to the PC and the screen goes dark a gray battery appears with a "wait circle" and the phone freezes
- in recovery the phone displays 14 bynaries downloaded and also knox warranty void 1
- most of the roms freez in the language selection screen - i boot-up the phone (after i do a restore factory settings) the installing application dialog appears and then the language selection screen appears, then after 5-6 seconds the phone freezes - the freeze is not triggered by something I do it's triggered by time, after 5-6 seconds no matter what I do with the phone the phone freezes, if it makes any difference, exactly before the phone freezes the display brightness goes to the maximum setting.
Where I am right now
- I installed another stock rom, 4.4.2, it worked acceptable for a few minutes (it got passed the initial setup with no issues) then i left it on the desk, the display went dark and the battery thing happened again and the phone froze, i restarted the phone in recovery, did a factory reset, when the phone started it froze on the language selection screen.
I am at this for about a week now and I have no more ideas and no more patience, and run out of threads and tutorials to read, I am 1 step away of using the phone as a paperweight so please help, any idea would be appreciated, even if it's to enlighten me about what happened and telling me that the phone is bricked.
I am willing to try anything even if it is risky and can totally brick the phone, this is not my main phone and it's purpose is to help me understand android, and help me not make the same mistakes next time.
But, if it's possible I would like to fix the phone because even though it's pretty old it's still an ok phone.

Sorry wrong forum. You need N7100, not the n7000. Good luck.

Note 5 stuck in loop while updating firmware at %24

Hi All,
Sorry if this is asked before. I have a new Note 5 unlocked. I turned it on yesterday and started using it. Late at night, its screen froze. I tried pressing Power+Volume_Down buttons to restart the phone. The phone restarted but the the screen was black. Only the notification light was on (blue).
In the morning, the light was still on and the phone was froze. I tried restarting it and I succeeded it. Then I realized the phone was very, I mean veeeery slow. By the time, a firmware update notification popped up. I believe it was Marsmallow update. I hit the yes button. The phone started the update and was stuck at %24. Then it restarted itself. The update process starts over and when it reaches %24, it starts over.
This happened before with my note 4 when I tried to root it. This phone is brand new and is not rooted. However, I transferred my Google profile but I did not select to download my previous apps. So, I don't think it is rooting issue but stucking at the same percentage makes me nervous.
I tried to get into recovery mode but the button combination does not work at all. So I can neither factory reset nor clear the cahe partition. When I press Volume_Down+Home+Power buttons, a custom rom download screen appears but Volume_Up+Home+Power buttons do not work at all. I cannot shut off the phone. It constantly restarts itself, starts the update, fails at %24 and starts the process over again.
What might be the problem? How can I fix this?
Regards

Hi,
Try flashing some stockfirmware via Odin (ideally something of the same android version i.e. lollipop/marshmallow). Once it's installed you should be able to access recovery from which I strongly recommend clearing your cache afterwards as you've already suggested. If you are not worried about loosing any data, then flash new firmware that is inclusive of BL/CP/CSC files too (each one has a category for such in Odin). With the latter, by all means flash marshmallow etc. :good:
Regards

Stuck on AT&T logo and cannot enter recovery mode

This is my first post, but I've had my phone rooted for a few months now with no problems until today out of the blue. What I've done to root my phone in the first place was flash to 4.4.2 NE3, root it, then upgrade to 5.0.1 OC 7 DeOdexed while keeping the root according to the link below. And then I put Xposed framework on it.
https://forum.xda-developers.com/galaxy-s4-active/general/how-to-update-to-i537oc6-5-0-1-t3089355
And this has worked well for me for a few months since that was back at the end of December. Flash forward to today when my phone was being rather slow to respond to my actions so I decided to restart it. And upon restarting it, it's been stuck on the AT&T logo screen for a very long time. I can power it down with the power button, but think it actually just restarts it because then it boot ups again on its own. I cannot enter recovery mode with power+home+volume up, but I can get to the custom OS screen with power+volume down. My computer cannot see it as an adb device either. I've also tried removing the SIM card and the SD card and it's still gets stuck at the AT&T logo.
I've done nothing different with the OS or Xposed recently. The only new thing was about 2 hours prior to restarting it, I connected it to my computer to transfer some video files to the sd card. While I had it connecting to the computer and looking at the files on it through the phone's My Apps, it was sluggish to respond to my actions. But after disconnecting it, it was fine. I don't know if this is related, but I haven't done anything else different with it. Is there anyway to get my phone to boot up correctly? Or am I going to have to reflash it all over again? Thank you for any help.
Edit: I can enter recovery mode and I tried wiping the cache. It still gets stuck at the AT&T logo screen. I should also note that it no longer shows the Samsung "custom" boot screen anymore like it used to after rooting, now it just has the default Samsung boot screen, so it would certainly seem like my OS has been corrupted.