Hello!
Around a month ago I installed a custom rom on my Samsung Galaxy Note Pro 12.2 (SM-P905), which ran smoothly until a week ago, when my tablet suddenly wouldn't leave the Samsung Galaxy Logo screen when booting. I was also unable to access recovery (I had TWRP installed), however I was able to access download mode. Then I decided to try to install the stock firmware using Odin. It seemed fine until it was about halfway through the installation, when it seemed to disconnect and the installation failed. After several attempts this still happened. I also tried installing both TWRP and CWM, both of which passed in Odin, however I am still unable to access recovery mode. I also tried installing the custom rom, with the same results as I mentioned earlier. In addition to this the screen has also begun flickering a whole lot, both when showing the Samsung logo and when in download mode, however it seems to intensify during the latter. This, in addition to the fact that I am unable to get any response when it isn't hooked up to my computer, has led me to believe that there is some issue with the battery as well, however I am absolutelly clueless at the moment.
I also have to mention that this is my first post here and my first attempt at installing a custom rom or doing anything of this nature to my devices. Any help would really be appreciated!
mbrau said:
. In addition to this the screen has also begun flickering a whole lot, both when showing the Samsung logo and when in download mode, however it seems to intensify during the latter. This, in addition to the fact that I am unable to get any response when it isn't hooked up to my computer, has led me to believe that there is some issue with the battery as well, however I am absolutelly clueless at the moment.
Click to expand...
Click to collapse
Your battery connector needs to be re soldered first before trying to flash firmware.
Read the threat " Flickering Screen " for more information. Cracked battery connector will cause flickering screen, reboot, hang on samsung logo at boot..etc...
Related
Hi everybody, my beloved P6800 started a couple of days ago to exhibit a strange behavior : after a full battery discharge (my bad), it remained stuck on the Samsung logo (not bootloop), et recovery was no longer available.
Only OS Download mode works, i've tried stock Samsung ROMS + recovery, Odin tells me everything works fine, but i'm unable to access recovery again, and whatever the recovery/rom I flash, the same symptoms happen.
I've heard of defective RAM on some 7.7 Tabs, forcing users to repartition excluding bad chips, but without recovery access, I'm quite blind
Has anybody encountered such behavior on a 7.7 ?
Thanks in advance and have a nice day !
sebguilbaud said:
Hi everybody, my beloved P6800 started a couple of days ago to exhibit a strange behavior : after a full battery discharge (my bad), it remained stuck on the Samsung logo (not bootloop), et recovery was no longer available.
Only OS Download mode works, i've tried stock Samsung ROMS + recovery, Odin tells me everything works fine, but i'm unable to access recovery again, and whatever the recovery/rom I flash, the same symptoms happen.
I've heard of defective RAM on some 7.7 Tabs, forcing users to repartition excluding bad chips, but without recovery access, I'm quite blind
Has anybody encountered such behavior on a 7.7 ?
Thanks in advance and have a nice day !
Click to expand...
Click to collapse
Hello!
I have same problem with my tab. When I try charging it shows battery with "wait" sign and no progress. Is it the same for you? Have you found a fix?
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
somesortofthing said:
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
Click to expand...
Click to collapse
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
ShapesBlue said:
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
Well, can I somehow get my phone into working order? Because it's as good as bricked right now.
Samsung Galaxy S5 G900A (AT&T)
Previously on a day off I became very bored, and decided to root my phone. After playing around with everything for a day i did not like it. So i just went into recovery mode and did factory rest on my phone. Now I used supersu and a basic root everything worked perfect after i rooted it. But once I tried to put the stock firmware back on my phone it started acting funny. With showing Unfortunately Context Service has stopped. It was so absurd my phone couldnt function properly. I tried flashing the stock firmware on there in hopes that it would fix my problem, but it only made my phone completely inoperable. I have been trying multiple ways to fix this using odin v3.09 and odin v 3.10.6. Here are some of the files I have tried to get my phone back to stock. (G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5) I have tried downgrades. Odin seems to fail on every single one besides this set up (AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5) (CP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5) (CSC_ATT_G900AATT1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5) Odin loads those three files onto my phone perfectly with in 3 minutes but after they are installed on my phone. When i power it up it gets through the first screen and only shows half of the samsung logo freezes and goes to a black screen with a blue light. I have been working at this problem for a little over a week a couple hours a night and i really can not seem to make any progess. Help would be greatly appreciated.
Still having troubles
Flashes firmware perfectly fine but still can not seem to get past the samsung logo loading super slow and then just cutting out and going to a black screen with a blue stationary light on top left of phone.
Still looking for advice
bump
ksutinen said:
Flashes firmware perfectly fine but still can not seem to get past the samsung logo loading super slow and then just cutting out and going to a black screen with a blue stationary light on top left of phone.
Still looking for advice
bump
Click to expand...
Click to collapse
Boot into recovery mode and do full wipes wipe cache ,wipe del Vick cache,factory reset
I think this will resolve your problem
Regards
Mohamed786
Let me start by addressing I know this isn't the sprint thread but there's a lot more development here which equals more help. Plus this issue seems to be able to happen to any variant.
Second, this isn't my device I'm trying to see if it can be fixed for a friend. I'm not that familiar with Samsung devices but I have been able to get them working in the past via Odin or kies but this time I need some help.
So this is what's going on, my friend recently rooted his S6(SM-920P) not sure which method he used (don't think it matters at this stage) and was on stock rom (LP5.0.2) with xposed framework installed. He hadn't changed the kernel AFAIK oh but I did install TWRP for him and everything was working. Long story short he woke up a couple days ago to his phone being unable to turn back on. I told him how to get to download mode and I asked him what did it say on the top left corner it said something like "system binary not SEandroid locked" underneath that it said fac lock
So I had him give me the phone thinking somehow it did a OTA update while he was asleep or something either way I was confident using Odin to flash the firmware would solve the issue. Had the firmware finished flashing I'm confident it would have but halfway through Odin simply froze on installing system. I figured its just gonna take a while 45 mins later it was still stuck at the same spot.
Not really thinking about it I figured I will just reboot the phone back into download mode restart the process it should be fine. Not a good idea. Now all I get is a green screen saying to access the smart switch emergency recovery system. But it gets better.
My computer isn't recognizing the device now. I installed smart switch software and it's not recognizing it. I even installed Kies and it's not recognizing either.
Is his phone toast or what? I tried emergency system recovery but I need the S/N of his phone to possibly get this thing working again, but it boot into anything anymore except the screen that says Samsung switch...
PLEASE HELP ME if it's bricked it's bricked I get that but if there's a way to figure out what to do I'm all ears. Thanks in advance
Greetings everyone,
I decided to post my problem with my phone after searching the entire internet for similar problem but with no luck. Anyway I used to play around with my Samsung j7 pro for 2 years, I managed to flash twrp and thus many other custom roms, until last week when I recklessly flashed a sboot.img.tar file through Odin in order to fix cellular network in a rom I flashed earlier, this alone bricked my phone refusing to get past the Samsung logo, so like I do always, I tried to restore my phone by flashing the stock firmware (9.0) which I always keep on my PC, but surprise, the phone refuses to go through the process and gives me this error:
sw rev check fail bootloader device -1 binary 6
(same with 8.0 and 7.0 firmware)
I searched the internet for same error but with no luck, because I understand it's a mismatch between device bootloader current version and the firmware bootloader's, that they should be the same or higher, meaning you can't downgrade, I get that! but I never seen device with negative figure (-1) what that's supposed to mean? my device bootloader used to be on 6, how did it managed to jump to minus one ?
then I tried to flash TWRP to see if I could flash a rom and get around it, so I did, but when booting into recovery the screen goes black, I thought first the phone turned off, but not really, because TWRP seems to work with screen completely black, I knew that because I accidentally touch the screen and I sense vibration, I managed to reboot the phone via twrp just by guessing the buttons location (screen always black) in order to prove that TWRP is working with screen off. I tried to flash multiple TWRP versions but the same problem, no screen just touch, by the way there is nothing wrong with display hardware because it shows Samsung logo at start and also can boot into download mode just fine.
I hope someone could help me overcome this big of an issue, because I tried everything.