Database Develop

I am at my wits end here. I'm about to just break down here. G900A help please

So, I have a Galaxy note 3 G900A. Not sure what version and I don't have access to that. So, it has the Alliance rom installed on it. It was working fine for months with absolutely no problems. Then all of a sudden, earlier, it said NFC has stopped working, over and over again. Then, I turned off the phone and it failed to turn on. It will not get past the splash screen. It just wants to stay dark and if I leave it alone long enough, it automatically goes into recovery mode. I can get into recovery mode and download mode normally. I already tried factory reset and all of that. None of my computers will recognize the phone and I have tried multiple cables as well. Odin won't recognize it and neither will samsung kies. I tried installing stock rom through SD card and it says
Verifying update package:
E:Footer is Wrong
E: Signature Verification Failed.
It does that no matter what rom I try to install. I can't afford to get another phone right now and it is the only one I have and I just don't know what else I can do. Any help is greatly appreciated.

Well to start backwards, the stock recovery isn't really meant to flash zips, but it should go farther than saying Footer Is Wrong
Signature Verification has failed. For me, it says that, then if you wait a few seconds, it'll say a few other things, then install from sd card complete and it wipes data and cache then reboots. Next, you have to use an official cable for that, Media Transfer doesn't work correctly without oem cable
Sent from my SM-N9005 using Tapatalk

Have you tried reinstalling the drivers on your pc or tried a different pc?

spookykidmm said:
Well to start backwards, the stock recovery isn't really meant to flash zips, but it should go farther than saying Footer Is Wrong
Signature Verification has failed. For me, it says that, then if you wait a few seconds, it'll say a few other things, then install from sd card complete and it wipes data and cache then reboots. Next, you have to use an official cable for that, Media Transfer doesn't work correctly without oem cable
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I do use an oem cable. Same thing. The rest of what you said does happen though.

dustincrock said:
I do use an oem cable. Same thing. The rest of what you said does happen though.
Click to expand...
Click to collapse
The cord is funky sometimes. Try to "mangle" it a little bit to see if odin will say "Added!". I know I have to basically wrap mine around the computer to get it to work correctly
Sent from my SM-N9005 using Tapatalk

sparx said:
Have you tried reinstalling the drivers on your pc or tried a different pc?
Click to expand...
Click to collapse
Yes I have. Still the same problems.

dustincrock said:
Yes I have. Still the same problems.
Click to expand...
Click to collapse
Any luck?
Sent from my SM-N9005 using Tapatalk

spookykidmm said:
Any luck?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
No. No luck..

A Last Resort
dustincrock said:
So, I have a Galaxy note 3 G900A. Not sure what version and I don't have access to that. So, it has the Alliance rom installed on it. It was working fine for months with absolutely no problems. Then all of a sudden, earlier, it said NFC has stopped working, over and over again. Then, I turned off the phone and it failed to turn on. It will not get past the splash screen. It just wants to stay dark and if I leave it alone long enough, it automatically goes into recovery mode. I can get into recovery mode and download mode normally. I already tried factory reset and all of that. None of my computers will recognize the phone and I have tried multiple cables as well. Odin won't recognize it and neither will samsung kies. I tried installing stock rom through SD card and it says
Verifying update package:
E:Footer is Wrong
E: Signature Verification Failed.
It does that no matter what rom I try to install. I can't afford to get another phone right now and it is the only one I have and I just don't know what else I can do. Any help is greatly appreciated.
Click to expand...
Click to collapse
As a last resort, put the device into download mode and connect to KIES 3. Go to tools and do a complete reinstallation. This will return you device to full factory specs and latest approved software, no custom ROM, no root, and no saved data. But at least you will have a functioning device. As soon as possible look into getting a new battery.

zancro said:
As a last resort, put the device into download mode and connect to KIES 3. Go to tools and do a complete reinstallation. This will return you device to full factory specs and latest approved software, no custom ROM, no root, and no saved data. But at least you will have a functioning device. As soon as possible look into getting a new battery.
Click to expand...
Click to collapse
I even used different batteries. And kid won't work because the phone isn't detected by the computer as being a phone. Kies doesn't pick up the phone, even in download mode

dustincrock said:
I even used different batteries. And kid won't work because the phone isn't detected by the computer as being a phone. Kies doesn't pick up the phone, even in download mode
Click to expand...
Click to collapse
Your only remaining option might be to send your device away for professional help. In the past I have used the services of Josh at: http://mobiletechvideos.com/ . (I am not related to that organization in any way.) For around $50.00 they can do a complete refresh, and in my case offered to root and load the custom ROM of my choice for a small additional fee. It took about one week.
Good luck.

G900A?
zancro said:
Your only remaining option might be to send your device away for professional help. In the past I have used the services of Josh at: http://mobiletechvideos.com/ . (I am not related to that organization in any way.) For around $50.00 they can do a complete refresh, and in my case offered to root and load the custom ROM of my choice for a small additional fee. It took about one week.
Good luck.
Click to expand...
Click to collapse
I checked back to see if you had solved the problem and noticed something I missed earlier... Your OP says you are using a G900A. Are you referencing a Note 3 or some other device?

Solved

(Solved) and thank you everyone!
I have a Galaxy Note 5 for tmobile. I have been running Note 7 express rom. Also I had a backup or Hell Rom.
The problem is is I went to change the DPI settings and although I made a backup I forgot to take off the fingerprint lock or possibly delete a Google account and when the phone shut down and came back on it showed a custom boot animation. The boot animation was Biohazard.
At this time I have tried to download the last 4 firmwares DOK and PDH and the phone will go as far as to accept the boot but once it gets to where it should pass it will not. The phone will let me go into download mode however it won't let me do anything from that point and tells me that the custom binary has been blocked by FRP.
And hoping someone can help me as I can't afford a new phone at this time the phone is pristine and I'd hate to see it become a paperweight I took it in to Samsung and obviously pretended like I wasn't the one who did the damage and they said that they wasn't sure what it was or what it was doing but it wasn't working so I quickly realized that I had no help there and I thought I'd ask my brothers and sisters here.
If anyone can direct me to the right software or a proper flashing tool that might be able to get past the FRP lock please let me know as I am dying here in Ohio without my phone.
Thank you in advance all

DAD12345 said:
I have a Galaxy Note 5 for tmobile. I have been running Note 7 express rom. Also I had a backup or Hell Rom.
The problem is is I went to change the DPI settings and although I made a backup I forgot to take off the fingerprint lock or possibly delete a Google account and when the phone shut down and came back on it showed a custom boot animation. The boot animation was Biohazard.
At this time I have tried to download the last 4 firmwares DOK and PDH and the phone will go as far as to accept the boot but once it gets to where it should pass it will not. The phone will let me go into download mode however it won't let me do anything from that point and tells me that the custom binary has been blocked by FRP.
And hoping someone can help me as I can't afford a new phone at this time the phone is pristine and I'd hate to see it become a paperweight I took it in to Samsung and obviously pretended like I wasn't the one who did the damage and they said that they wasn't sure what it was or what it was doing but it wasn't working so I quickly realized that I had no help there and I thought I'd ask my brothers and sisters here.
If anyone can direct me to the right software or a proper flashing tool that might be able to get past the FRP lock please let me know as I am dying here in Ohio without my phone.
Thank you in advance all
Click to expand...
Click to collapse
Are you saying you tried stock firmware flash to phone? Download the stock firmware from samsung official website and flash through ODIN. If it fails try a different cable, try a different USB port (sometimes 2.0 and 3.0 fail for unknown reasons), try using windows 7 instead of 8, 8.1, and 10 or vice versa. Use a different version of ODIN. These are all common ODIN issues that cause flash to fail. Should accept a flash of completely stock firmware.
Let me know what you come up with.

obliviousmnd said:
Are you saying you tried stock firmware flash to phone? Download the stock firmware from samsung official website and flash through ODIN. If it fails try a different cable, try a different USB port (sometimes 2.0 and 3.0 fail for unknown reasons), try using windows 7 instead of 8, 8.1, and 10 or vice versa. Use a different version of ODIN. These are all common ODIN issues that cause flash to fail. Should accept a flash of completely stock firmware.
Let me know what you come up with.
Click to expand...
Click to collapse
Thank you, I will try those

obliviousmnd said:
Are you saying you tried stock firmware flash to phone? Download the stock firmware from samsung official website and flash through ODIN. If it fails try a different cable, try a different USB port (sometimes 2.0 and 3.0 fail for unknown reasons), try using windows 7 instead of 8, 8.1, and 10 or vice versa. Use a different version of ODIN. These are all common ODIN issues that cause flash to fail. Should accept a flash of completely stock firmware.
Let me know what you come up with.
Click to expand...
Click to collapse
Great news ! I found a photo of my settings on accident and was able to factory reset with Smart Switch. Tha k you for your time helping me.

Awesome i glad everything worked out for you. May want to edit title to [solved] or something

[G900A]Need Help bricked phone

I have the G900AUCU2AND3 and i hard bricked it by not paying attention when a link took me to a note 3 Alliance Rom instead of the GS5 one and i flashed it, when i told safestrap to reboot it just went dead now my dad is upset and wants me to fix it, but it's a black screen it doesn't turn on it doesn't charge as far as i know and it's not recognized when i plug it in some one please help me i've tried for 2 days and still haven't found anything
thanks in advance

Have you tried holding volume down, home and power to get you into download mode?

BROKKANIC said:
Have you tried holding volume down, home and power to get you into download mode?
Click to expand...
Click to collapse
yea 4 different times even taking the battery out before trying and holding it for over half a minute, nothing.

Well, the next thing I would try is pull the battery, plug in the usb to a pc and try the three button hold again.

i did that too, my computer would just tell me it couldn't recognize the usb device.

Logic195 said:
i did that too, my computer would just tell me it couldn't recognize the usb device.
Click to expand...
Click to collapse
Go into device manager and see if the appropriate drivers are installed. If they aren't there, the device will show up with a little triangle on the icon.

AptLogic said:
Go into device manager and see if the appropriate drivers are installed. If they aren't there, the device will show up with a little triangle on the icon.
Click to expand...
Click to collapse
yup they were the first thing i went to install since i was following a guide, in fact it's still in my computer i just checked.

Have you tried reinstalling the Samsung drivers?
Do that first. Uninstall the Samsung drivers. Then reinstall. Plug in phone. Then open Odin and try and flash.
Unless you messed with the boot loaders it should flash. The fact that windows recognizes that something is plugged in means it reads something on the phone. So it's not completely bricked.

it only detects something is there when i pull the battery out and put it back in and then plug it but if i unplug and replug it, it won't read anything anymore but i'll give it a try thanks.

Worst case scenario you've got a hardbrick and will need to JTAG into the device and force the firmware onto it.

AptLogic said:
Worst case scenario you've got a hardbrick and will need to JTAG into the device and force the firmware onto it.
Click to expand...
Click to collapse
well my computer just tells me that it can't recognize the usb device and that it might be damaged, but another problem i have is i can't find the firmware for this phone, It's G900AUCU2AND3 and i can find everything except ND3 i found NCE but can i still flash that? Because i thought it had to be the exact same firmware of the phone for it to work.

Logic195 said:
well my computer just tells me that it can't recognize the usb device and that it might be damaged, but another problem i have is i can't find the firmware for this phone, It's G900AUCU2AND3 and i can find everything except ND3 i found NCE but can i still flash that? Because i thought it had to be the exact same firmware of the phone for it to work.
Click to expand...
Click to collapse
At this point I'd say all you can do is take it to your local Best Buy and ask them to flash NCE on it. If you try to flash NCE on a UCU2 by yourself it'll fail the qfuse check.

AptLogic said:
At this point I'd say all you can do is take it to your local Best Buy and ask them to flash NCE on it. If you try to flash NCE on a UCU2 by yourself it'll fail the qfuse check.
Click to expand...
Click to collapse
hmm i always get mixed responses from best buy but thanks for all the help i really appreciate it i'll see what i can do with best buy.

Check this page: https://forum.xda-developers.com/att-galaxy-s5/help/g900a-g900az-t2965038 read post#15 onward

gello924 said:
Check this page: https://forum.xda-developers.com/att-galaxy-s5/help/g900a-g900az-t2965038 read post#15 onward
Click to expand...
Click to collapse
Thank you guys so much I'll see what my dad wants to do.

Stuck in a boot loop can't get into recovery

Hi,
Just received my note 9 and downloaded the latest firmware. Installed via odin. One of the files failed so I redownloaded the file and updated just the AP. I probably should have done all files. It installed fine but i'm now stuck in a boot loop.
I can't get into recovery with ether volume up, bixby and power. I just get a blue screen with an android on its side?
Any tips. Very worried the phone is bricked. Hoping I don't have to wait for the battery to die as that could take a couple of days.

mardon85 said:
Hi,
Just received my note 9 and downloaded the latest firmware. Installed via odin. One of the files failed so I redownloaded the file and updated just the AP. I probably should have done all files. It installed fine but i'm now stuck in a boot loop.
I can't get into recovery with ether volume up, bixby and power. I just get a blue screen with an android on its side?
Any tips. Very worried the phone is bricked. Hoping I don't have to wait for the battery to die as that could take a couple of days.
Click to expand...
Click to collapse
Can you get into download mode?

Nope can't seem to get into ether.
Any tips?

mardon85 said:
Nope can't seem to get into ether.
Any tips?
Click to expand...
Click to collapse
At this point, your only two options are EDL (emergency download mode) which technically requires you to crack op the device and mess with the board inside of the device, or just a warranty replacement if you haven't tripped Knox.

Ok thanks for the info. I was only trying to install the latest stock firmware via odin so i'd hope Knox wasn't tripped.
Interestingly my SM-N9600 doesn't have any serial number on the back. When I took it to samsung to see if they had any special tools they wouldn't touch it because they said it was a refurb phone.
I'm wondering if the refurb is infact not a SM-N9600 which would be why the flashing a new recovery bricked the phone.

mardon85 said:
Ok thanks for the info. I was only trying to install the latest stock firmware via odin so i'd hope Knox wasn't tripped.
Interestingly my SM-N9600 doesn't have any serial number on the back. When I took it to samsung to see if they had any special tools they wouldn't touch it because they said it was a refurb phone.
I'm wondering if the refurb is infact not a SM-N9600 which would be why the flashing a new recovery bricked the phone.
Click to expand...
Click to collapse
Well, that's a crap move by them. I know for sure that they have a proprietary software that can revive pretty much any Samsung phone as long as it's not hard bricked. They could've just flashed it and helped you. I have a friend who works for Samsung and I have seen him use that software at best buy once. I mean, you've spent your own money to use their phone after all. I don't know why it matters if it's just software.

Question SM-G998B Bricked

Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?

Seems different?
Well I would try Odin and an official ROM anyway, no pain no gain right?

What exactly were you doing before this occured?

You try the old delete usb driver, restart computer, install usb driver then restart computer and restart phone and try again.

SirDigbyCC said:
Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?
Click to expand...
Click to collapse
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something

flairepathos.info said:
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something
Click to expand...
Click to collapse
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.

To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.

SapphireEX said:
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.
Click to expand...
Click to collapse
Oh I see the issue now you need to wipe all and re-flash full firmware when flashing the device using Odin
if that doesn't work flash the partitions with the kernel drivers and system partition
I had a similar issue with my current mtk phone and it was because the boot/preloader partition bilieved i had flashed the wrong firmware for my device(it was just a different firmware release for my phone
Just to be safe some ota updates break wehn the bootloader is not unlocked (when updationg from say android 8(oreo) -9(pie)...)
especially because of code errors in the update, cache/vendor partition being too full after downloading update

SirDigbyCC said:
To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.
Click to expand...
Click to collapse
If you're telling the truth, and it wasn't a bad module / firmware / etc, it is possible your eMMC got too hot and melted some solder. I've seen it happen before.
You'll want to diagnose everything you can. If you're on Windows, does it recognize a USB device or a COM device? If linux, does lsusb return anything useful about it?
If it's not being detected, and multiple wires doesn't change anything, are you able to access sahara mode / download / DFU? If so, go to those and try again.
If you are lying, and this is a bad firmware flash / OTA brick, you'll need to tell us otherwise we'll be going in circles.

So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?

SirDigbyCC said:
So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?
Click to expand...
Click to collapse
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.

SapphireEX said:
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.
Click to expand...
Click to collapse
I appreciate the vote of confidence, I don't think it was an OTA update that did it this time, it usually requests to do updates which I highly doubt I would have pocket approved through a flip case only short after pressing play on Spotify.

So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!

SirDigbyCC said:
So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!
Click to expand...
Click to collapse
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!

shriom_manerker said:
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!
Click to expand...
Click to collapse
It was free, turned out to be a hardware issue internally so I think covered by warranty as I have Care+ which has an excess of £40 which they didn't make me pay. They also replaced the screen due to some dead pixels, and the battery! Happy days!
Thanks all for your suggestions!