Hi,
I know this is a weird question, but I was wondering:
Is it possible to create a full bricked Note 4 on purpose?
I mean to make it really really dead, no booting any more, no recovery, no download mode, nothing.
So that a new mainboard is a must? Like, what happens when you flash a BL file and pull the cable in the middle?
And no, I don't want to destroy foreign Notes on purpose.
I am thinking about my Note 4, a 700€ phone which is slightly older than 1 freaking year and where the internal memory suddenly fails,
to maybe get my warranty for this Samsung bull**** to be repaired.
I always treated it like my precious, but unluckily I was one of the cases with a faulty mmc Note 4 (google it, it's quite common).
And since I rooted it, I should pay for the faulty hardware instead of Samsung, which I find a liiiittle bit unfair. :crying:
I remember someone posted a comment about that recently.
Maybe it was in answer to one of those "will root void my warranty by tripping knox" type questions.
From memory, I think the person suggested something like cross circuiting the battery and sim card port, or similar.
It was a physical act and not just software related.
To fully brick your device, flash a bootloader or firmware made for some other model of the note 4 (other than your model) or that of some other samsung phone series like note 5 or s6
Shane_Picardo said:
To fully brick your device, flash a bootloader or firmware made for some other model of the note 4 (other than your model) or that of some other samsung phone series like note 5 or s6
Click to expand...
Click to collapse
Can authorized service discover what you did and then denie your warranty?
I also have some issues that authorized service does not recognize (weak mobile signal).
Shane_Picardo said:
To fully brick your device, flash a bootloader or firmware made for some other model of the note 4 (other than your model) or that of some other samsung phone series like note 5 or s6
Click to expand...
Click to collapse
This just won't flash, and the phone will be in download mode
ph03n!x said:
This just won't flash, and the phone will be in download mode
Click to expand...
Click to collapse
I don't know about this coz about 3 years ago my aunt wanted android 4.x on her galaxy S phone. So I had installed cyanogenmod but then she didn't like it so she told me to revert back to the original firmware. Unfortunately, I downloaded the firmware for gt-i9003 while hers was gt-i9000. It got bricked and I was in a soup!
---------- Post added at 12:32 PM ---------- Previous post was at 12:25 PM ----------
guls said:
Can authorized service discover what you did and then denie your warranty?
I also have some issues that authorized service does not recognize (weak mobile signal).
Click to expand...
Click to collapse
Samsung devices after S3 and note 2 come with "Knox" security. The moment you flash any firmware or ROM that is not official (not signed by samsung), it will trip the counter. It is like a fuse that can't be reset. Go to download mode and check your knox warranty void. If it is: 0x1 then you have lost warranty. It can't be made 0x0 anymore. Thats how service centers get a clue that you have tampered with the OS.
Samsung devices after S3 and note 2 come with "Knox" security. The moment you flash any firmware or ROM that is not official (not signed by samsung), it will trip the counter. It is like a fuse that can't be reset. Go to download mode and check your knox warranty void. If it is: 0x1 then you have lost warranty. It can't be made 0x0 anymore. Thats how service centers get a clue that you have tampered with the OS.
Click to expand...
Click to collapse
If the phone is bricked, how can they see Download mode?
Well, thats exactly the question.
Assuming you flash a bootloader file through Odin, and you then interrupt the process in the middle... What would happen?
Phone dead I guess. But is the DL mode still reachable? Or like someone suggested, maybe try to flash some unfitting FW.
The thing is, with all the warranty denies from Sammy, I am astonished that no one else thought about trying to disguise the Knox flag via completely killing the Software...
Although i think that, even if the device seems very dead, Sammy will still have ways to check the Knox flag. Though it would be worth a try, whats there to loose...
MisterKanister said:
Well, thats exactly the question.
Assuming you flash a bootloader file through Odin, and you then interrupt the process in the middle... What would happen?
Phone dead I guess. But is the DL mode still reachable? Or like someone suggested, maybe try to flash some unfitting FW.
The thing is, with all the warranty denies from Sammy, I am astonished that no one else thought about trying to disguise the Knox flag via completely killing the Software...
Although i think that, even if the device seems very dead, Sammy will still have ways to check the Knox flag. Though it would be worth a try, whats there to loose...
Click to expand...
Click to collapse
Did you find it ? the way of course ...
scamex said:
Did you find it ? the way of course ...
Click to expand...
Click to collapse
No.
My Note further degraded and every try to flash something through Odin fails immediately.
So I only have the Download Mode and Stock Recovery left.
MisterKanister said:
No.
My Note further degraded and every try to flash something through Odin fails immediately.
So I only have the Download Mode and Stock Recovery left.
Click to expand...
Click to collapse
You can find + and - of the sim and after that see where they make contact on simcard reader. After that find a transformer rated 12V and touch with the wires the 2 sim contact. I`m sure it will damage the board.
It wont, it will just fry the sim card circuitry fuse and it will still be able to boot. You could hex edit the bootloader file and write junk data in it, pack it to tar and add md5 to it, then just flash it. I am not responsive for what you do with this.
Related
after using the "Odin3 One-Click Downloader" my i9000 only loops the att logo on and off, recovery mode and download mode are no longer working... had anyone experienced this?
well this is f...ed up..... my i9000 was unbranded, and that one click crap must have flashed the captivate fw or smth, should i let my phone die in peace now?
There are different oneclick apps for different branded SGSs. Which one did you download? Sounds like you downloaded the AT&T version.
You have to boot your phone into download mode again to flash the correct ROM for your specific phone. There are many different ways to get the phone into download mode. Check the dev forum or instructions.
foxbat121 said:
There are different oneclick apps for different branded SGSs. Which one did you download? Sounds like you downloaded the AT&T version.
You have to boot your phone into download mode again to flash the correct ROM for your specific phone. There are many different ways to get the phone into download mode. Check the dev forum or instructions.
Click to expand...
Click to collapse
"[STOCK ROM] Odin3 One-Click Downloader and Drivers" I've downloaded this one... and i cant boot into download mode, the 3 button methods died on me
Its for captivate.... And your phine iscompletely bricked. Needs a new mother board.
Why people download weird **** from untrusted sources?
Sent from my GT-I9000 using XDA App
Phone is completely bricked. Happened to me, and a few others too. Seems that these one-click odin downloaders do more harm than good. Hahaha...
Anyway, phone is bricked. Samsung replaced the motherboard for me. Luckily it's under warranty at no cost to me..
Seifer1975 said:
Phone is completely bricked. Happened to me, and a few others too. Seems that these one-click odin downloaders do more harm than good. Hahaha...
Anyway, phone is bricked. Samsung replaced the motherboard for me. Luckily it's under warranty at no cost to me..
Click to expand...
Click to collapse
replace the motherboard? what the fudge.. i gave it to a local repair shop (samsung recommended one) and well.. they will try to reflash it or smth.. if that wont work, how much would replacing the motherboard cost? i'm out of warranty
dupel said:
Its for captivate.... And your phine iscompletely bricked. Needs a new mother board.
Why people download weird **** from untrusted sources?
Click to expand...
Click to collapse
What untrusted source? He went into Captivate forum here in XDA to download Captivate stock ROM. What do you think the outcome will be?
it might cost you around $150 or so, if i remember reading a recent post about a guy replacing his mb too. I think he had the same problem as you.
SwiftPolar said:
it might cost you around $150 or so, if i remember reading a recent post about a guy replacing his mb too. I think he had the same problem as you.
Click to expand...
Click to collapse
could you find that post for me? i cant seem to find it myself...
well, so far, i've found out that by flashing the i9000 (unbranded) with a captivate FW remapped all the buttons except for the power button, so download mode or recovery mode is impossible via any button combination. But if the phone does show something on the screen, its still only semi-bricked, in my case, its stuck at the bootloader. its fixable with JTAG ... i hope the service i took it to has a jtag device and will reflash to the i9k FW. and it would only cost me 10$ for the repairs
who had a similar experience?
I had exactly the same problem, after updating my phone through kies which failed halfway through i downloaded odin which at the time i didn't know was the wrong one and not for the i9000. in the end i had to get a new phone.
Sent from my GT-I9000 using XDA App
aaronlivo said:
I had exactly the same problem, after updating my phone through kies which failed halfway through i downloaded odin which at the time i didn't know was the wrong one and not for the i9000. in the end i had to get a new phone.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
were you under warranty? did you try to repair it ?
well my sgs is not fully bricked, it does not need a new motherboard... it just needs to be reflashed with jtag or smth >.<
a fully bricked (faulty) device would not turn on at all
allright, so just by flashing the phone with that one click odin crap, the repairs are going to cost me 250$
Hello.
My sensor for S View cover is broken (just like many others), which means S View screen is on all the time which renders the phone completely useless (it's impossible to leave this screen).
For a while, I've used CyanogenMod to get around it, as it doesn't have this S View "feature". Now I want to send my phone to repair so the S View sensor can be fixed. I believe I have flashed a stock firmware and rom, and I have also rooted it, and I need help with the next steps:
I need to reset my binary counter.
I need to reset my "CURRENT BINARY: Custom"
I need to reset my "CURRENT STATUS: Custom"
My problem is that I can't use triangle away, because it's an app that I need to install and use on the phone. I am completely unable to use the screen (lets imagine the screen is dead). So is it possible to do this via odin?
I captured a quick video, to show the current status of the phone (and it has been like this on any rom that is based on stock rom - even GPE).
Inrego said:
Hello.
My sensor for S View cover is broken (just like many others), which means S View screen is on all the time which renders the phone completely useless (it's impossible to leave this screen).
For a while, I've used CyanogenMod to get around it, as it doesn't have this S View "feature". Now I want to send my phone to repair so the S View sensor can be fixed. I believe I have flashed a stock firmware and rom, and I need help with the next steps:
I need to reset my binary counter.
I need to reset my "CURRENT BINARY: Custom"
I need to reset my "CURRENT STATUS: Custom"
My problem is that I can't use triangle away, because it's an app that I need to install and use on the phone. I am completely unable to use the screen (lets imagine the screen is dead). So is it possible to do this via odin?
Click to expand...
Click to collapse
Can you still boot in download mode? and does it say Knox void warranty?
Repulsa said:
Can you still boot in download mode? and does it say Knox void warranty?
Click to expand...
Click to collapse
Yes I can. And it says nothing about Knox
Inrego said:
Yes I can. And it says nothing about Knox
Click to expand...
Click to collapse
Download this mate http://www.androidfilehost.com/?fid=23050663588004454 then flash it via odin , once your done , Download triangle away . and reset the binary .
Edit: Sorry about that , Now redownload it should be okey
Repulsa said:
Download this mate then flash it via odin , once your done , Download triangle away . and reset the binary .
Edit Link
Click to expand...
Click to collapse
Download what? I think you missed the link
Inrego said:
Download what? I think you missed the link
Click to expand...
Click to collapse
Hello , hehe actually i fixed the link have a nice day.
Repulsa said:
Download this mate http://www.androidfilehost.com/?fid=23050663588004454 then flash it via odin , once your done , Download triangle away . and reset the binary .
Edit: Sorry about that , Now redownload it should be okey
Click to expand...
Click to collapse
I forgot to mention my phone is rooted currently. But the problem is that I cannot use the OS because of the S View thingy. So unless S View is disabled in the rom you linked, I think I will have the same problem. I'll give it a try, though.
I captured a quick video, to show the current status of the phone (and it has been like this on any rom that is based on stock rom - even GPE).
Inrego said:
I forgot to mention my phone is rooted currently. But the problem is that I cannot use the OS because of the S View thingy. So unless S View is disabled in the rom you linked, I think I will have the same problem. I'll give it a try, though.
Click to expand...
Click to collapse
EDIT : Im sorry to break this to you mate , you need to send your phone to technical service. this is a hardware problem . Im sorry . http://forum.xda-developers.com/showthread.php?t=2410642
Repulsa said:
EDIT : Im sorry to break this to you mate , you need to send your phone to technical service. this is a hardware problem . Im sorry . http://forum.xda-developers.com/showthread.php?t=2410642
Click to expand...
Click to collapse
Ok, it is flashing now. I am 90% sure it is a hardware problem. I also wrote in the first post that I want to send it to repair, but I wanted to restore everything to stock so I am sure there is still warranty
Inrego said:
Ok, it is flashing now. I am 90% sure it is a hardware problem. I also wrote in the first post that I want to send it to repair, but I wanted to restore everything to stock so I am sure there is still warranty
Click to expand...
Click to collapse
Im sure there is still warranty for that phone because your still on old bootloader and it doesnt say any Knox void warranty when you boot into download mode., but im guessing once they fix your phone they might update your phone to the newest stock firmware with the newest bootloader on it. Goodluck mate
Okay, thanks
Sent from my Nexus 5 using Tapatalk
Hello Everyone
First of all,my phone isn't rooted and I haven't flashed other single ROM until today in order to try to fix this problem
So...getting started
My phone was working clear and normal the past few days and today (14/12/2014) after 5 months without a single problem my phone suddenly bricked when I was listening to music with my headphones.
Being precise,I was listening to music in the car and it glitched and rebooted by itself and then it stopped at the boot animation and since then it stayed like that,I noticed that the phone started to get very hot at the point of being unable to hold it(yeah,it was very hot). So I took out the phone battery and waited until it cooled of a little bit before trying to turn it on again but after that nothing happened,stayed at the boot animation, tryed to get to the recovery menu but no good,made it to Download mode but nothing other than that.
Every time I plug it in it stuck at the boot animation and starts to get hotter and hotter forcing me to take out the battery from it
Arriving home I flashed 2 official ROMs, one from Argentina and the other from Vietnam but no success,stayed the same,bricked at the boot animation.
What should I do in order to make it functional again? What could be the problem?
My phone model is : SM-G900H
SSN : -G900HGSMH
Sorry for any English mistakes.
Please Help me
Thank you
Felipe
What I can say is that the hot comes from being stuck at an animation.
did you wiped after flashing?
Take it to the Samsung customer care.
Did you do a factory reset after you installed Official rom.
And just for the record , you are not bricked if you can still go to download mode.
SM-G900W8, 0x1
A recovered flashaholic since Aliance Rom 5.5
venereo said:
What I can say is that the hot comes from being stuck at an animation.
did you wiped after flashing?
Click to expand...
Click to collapse
ragz said:
Did you do a factory reset after you installed Official rom.
And just for the record , you are not bricked if you can still go to download mode.
SM-G900W8, 0x1
A recovered flashaholic since Aliance Rom 5.5
Click to expand...
Click to collapse
I can't do a full wipe or factory reset because I can't go to Recovery mode either unlock the phone,the only thing that is possible is going to the download mode but it doesn't make a difference
Feliipegon said:
I can't do a full wipe or factory reset because I can't go to Recovery mode either unlock the phone,the only thing that is possible is going to the download mode but it doesn't make a difference
Click to expand...
Click to collapse
Do a search on how to flash stock firmware through odin. It is also important how you enter into download mode, search this as well.
Sorry I'm at work and can't give you the threads.
I would redo the install from odin , at least once or twice. It looks as though it's not installing properly. As long as you have download mode you should have no problem fixing.
SM-G900W8, 0x1
A recovered flashaholic since Aliance Rom 5.5
Possible Bad Motherboard
I hate to say this, but if you are a non-rooted Galaxy S5 user, there is no way that a phone be stuck on Bootloop without you tinkering and modifying it in any way. Plus the fact that the phone gets got when it is stuck on that Boot Animation, will tell you that it's no longer a software issue, but hardware-related. My experience with all of the Galaxy S phones, starting with the GT-i9000 and with it's Exynos Processor, it tends to fail at a hardware level. Remember that SDS issue with the Galaxy S3? It maybe somewhat similar to what you are having, only the scenario is different.
Try to flash a Stock Firmware like what the others are saying. If that doesn't fix your problem, then definitely you've got a bad motherboard on your S5. Hopefully you are still on warranty.:fingers-crossed:
Look at this thread as well file the odin instructions to use odin to install factory tar files. And for that it does not matter about root.
http://forum.xda-developers.com/showthread.php?p=53454972
SM-G900W8, 0x1
A recovered flashaholic since Aliance Rom 5.5
ragz said:
Do a search on how to flash stock firmware through odin. It is also important how you enter into download mode, search this as well.
Sorry I'm at work and can't give you the threads.
I would redo the install from odin , at least once or twice. It looks as though it's not installing properly. As long as you have download mode you should have no problem fixing.
SM-G900W8, 0x1
A recovered flashaholic since Aliance Rom 5.5
Click to expand...
Click to collapse
Sorry for not mentioning it on the main text but,the 2/3 times I tryed flashing the stock firmware were through ODIN and that's why I sayed it didn't made a difference :crying:
Paolonicus said:
I hate to say this, but if you are a non-rooted Galaxy S5 user, there is no way that a phone be stuck on Bootloop without you tinkering and modifying it in any way. Plus the fact that the phone gets got when it is stuck on that Boot Animation, will tell you that it's no longer a software issue, but hardware-related. My experience with all of the Galaxy S phones, starting with the GT-i9000 and with it's Exynos Processor, it tends to fail at a hardware level. Remember that SDS issue with the Galaxy S3? It maybe somewhat similar to what you are having, only the scenario is different.
Try to flash a Stock Firmware like what the others are saying. If that doesn't fix your problem, then definitely you've got a bad motherboard on your S5. Hopefully you are still on warranty.:fingers-crossed:
Click to expand...
Click to collapse
Damn,the phone barely has 1 year and it's possible to already has such a problem like that? With the motherboard?
If so,I'll be unable to get a warranty in it because I bought it outside my country :crying:
Feliipegon said:
Sorry for not mentioning it on the main text but,the 2/3 times I tryed flashing the stock firmware were through ODIN and that's why I sayed it didn't made a difference :crying:
Damn,the phone barely has 1 year and it's possible to already has such a problem like that? With the motherboard?
If so,I'll be unable to get a warranty in it because I bought it outside my country :crying:
Click to expand...
Click to collapse
Have you tried different versions of odin, go back and reread everthing to make sue your not missing some little thing that makes a big difference.
You are flashing a 4.4.2 version back onto a 4.4.2 previous version right. You haven't messed around with any stock 5.0 lollypop versions. And you are sure your downloading the proper stock tar file.
Just giving ideas not saying your wrong.
SM-G900W8, 0x1
A recovered flashaholic since Aliance Rom 5.5
ragz said:
Have you tried different versions of odin, go back and reread everthing to make sue your not missing some little thing that makes a big difference.
You are flashing a 4.4.2 version back onto a 4.4.2 previous version right. You haven't messed around with any stock 5.0 lollypop versions. And you are sure your downloading the proper stock tar file.
Just giving ideas not saying your wrong.
SM-G900W8, 0x1
A recovered flashaholic since Aliance Rom 5.5
Click to expand...
Click to collapse
Beside that detail nothing else is missing in the main text
The stock ROMs that I downloaded were from the samsung firmware website,so yeah,they weren't any Lollipop version as far as I know
Just asking,will a different version of ODIN make any difference?
Feliipegon said:
Beside that detail nothing else is missing in the main text
The stock ROMs that I downloaded were from the samsung firmware website,so yeah,they weren't any Lollipop version as far as I know
Just asking,will a different version of ODIN make any difference?
Click to expand...
Click to collapse
Some people have stated that it does, the worst that can happen is it works, or you can give up and…… .. just sayin?
SM-G900W8, 0x1
A recovered flashaholic since Aliance Rom 5.5
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
UPDATE <21_03_2015><16_54_09_524>____________________________________________________________
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
intervall said:
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
Click to expand...
Click to collapse
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
st3chn0 said:
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
3XTR3M1ST said:
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
Click to expand...
Click to collapse
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
1. If its possible for him to return to the seller then yes but he can't to samsung. Due to knox being tripped. If he does its just basically a 50/50 chance
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
3. Using odin to flash any official firmware. Is not bad advice.
Sent from my SM-N9005 using XDA Free mobile app
celderic said:
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
Click to expand...
Click to collapse
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
st3chn0 said:
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
Click to expand...
Click to collapse
This is a softbrick, if the hardware is fine then you should be able to fix it in 10mins by flashing a stock rom, but as the seller has sold it in this state then i assume it is softbricked for a reason so you can't test the device for example.
cryostasis25 said:
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
Click to expand...
Click to collapse
But his knox is already tripped.. he bought a phone with knox 0x1 that's why i suggested returning it.
3XTR3M1ST said:
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Click to expand...
Click to collapse
If the seller is not responding, then it points to them tampering with the device before selling it. Where did you buy it from, i would ring your bank as soon as possible.
Download the latest n9005 rom from sammobile and flash it through odin if you want to try and fix it, shouldn't really matter what csc as your knox is already tripped anyway so you can't recieve OTA updates or warranty from samsung anymore, mine is a BTU device but i have used many XEO roms.
If the phone isn't connecting to the computer properly like you say, then it's probably best to leave it. As this could result in the connection failing when it is flashing the bootloader or something. But if it works fine, then there should be no problems.
Here is something you could try, start up odin (i use v3.09), close all processes relating to kies, boot the device into download mode, that screen you provided pictures of. Plug the phone in and wait a few minutes to check the connection is stable, move the cable around to make sure the socket and cable are okay. You will see it come up on the top left in odin after windows has installed the drivers.
If this all works fine then flashing a stock rom should fix the device if the hardware is okay.
Just a quick question. From what site did you buy the phone and how did you pay for the phone?
Sent from my SM-N9005 using XDA Free mobile app
Where is a reliable source to download the official firmwares? I cant find it on the samsung site.
Tried http://www.samsungupdate.com/how-to/download-firmware but the file sizes are different on either filehost mirrors and it seems shady.
www.sammobile.com/firmwares/
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit
3XTR3M1ST said:
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Click to expand...
Click to collapse
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
sirobelec said:
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after a little more research.
I have no idea what the phone was before, or what the seller did to it since he's just not responding anymore.
So I tried flashing the new bootloader as suggested, it seem to have worked to some extent, but then I screw it up again by pulling out the cable before seeing "PASS!". What now?
http://forum.xda-developers.com/showpost.php?p=59616074&postcount=16 said:
iketil said:
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
Click to expand...
Click to collapse
I'm still stuck on the "Samsung GALAXY Note3 SM-9005" screen. However I do think that the "hlte_lollipop_bootloader_modem.tar.md5" has "done its thing". I was previously unable to get to the recovery, but I was able to get to this <3e>recovery after flashing.
Also managed to see some logs of "i'm not sure what it is" before the phone went blank. I presume its due to battery going flat.
Later, I tried putting TWRP on it. Starting with "twrp-2.8.3.0-hlte-4.3.img.tar". But being a novice odin user I mistakenly unpluged the phone when odin is showing "RESET!". Then I tried going into recovery using VOLUP+HOME+POWER, and got this screen instead. I'm not sure if removing the phone before "PASS!" in odin could have caused this? Subsequently I tried flashing "twrp-2.7.0.3-hlte-4.3.img.tar" and
"twrp-2.7.2.0-hlte-4.3.img.tar", which resulted in the same error screen about SEANDROID.
I also noticed it increased my KNOX counter?
This is before and after.
Next I tried flashing ""hlte_lollipop_bootloader_modem.tar.md5" again hoping it would fix it. It didnt work. Silly me, this flash does not have a recovery image in it does it?
Anyway, now I dont have a working recover and is still stuck on the "Samsung GALAXY Note3 SM-9005". Thankfully odin mode still work. What should I do next? Please see this thread below for a little background to my problem. Thank you.
http://forum.xda-developers.com/galaxy-note-3/general/help-unfamiliar-error-screen-image-t3059227
Click to expand...
Click to collapse
HORRY SHET!!
I think my phone is asian! I just flashed the latest taiwan firmware released (N9005ZSUGOC3_N9005OZSGOC3_BRI) after flashing the new bootloader and everything works now!
I'm not sure what actually made it work since this is the first taiwan firmware I tried (its all XEO and BOB previously), but big thanks to everyone who helped!
Hello my brothers,
it was the first post me here at XDA
will give you the original file for the reset counter the KNOX for note3 n900 only.
and I will raise it on the MEGA.
did you have to do is download and run ODIN program file and enter the device on the status of the DOWNLOADMODE and then you connect the device to USB and choose to reset the counter file after completion remove the battery and reinsert then enter into the DOWNLOADMODE once again and then chose any Software installed and want to be here have restored security
ALRA7AL.SYRIA 😉
Greetings to you if you like this topic only thank enough for me
https://mega.nz/#!VYV3xCzb!_XOkBLULxoAqO73ll2FR_o1I04We2iwCEAKeUCYkeHU
alra7al.syria said:
Hello my brothers,
it was the first post me here at XDA
will give you the original file for the reset counter the KNOX for note3 n900 only.
and I will raise it on the MEGA.
did you have to do is download and run ODIN program file and enter the device on the status of the DOWNLOADMODE and then you connect the device to USB and choose to reset the counter file after completion remove the battery and reinsert then enter into the DOWNLOADMODE once again and then chose any Software installed and want to be here have restored security
ALRA7AL.SYRIA ?
Greetings to you if you like this topic only thank enough for me
https://mega.nz/#!VYV3xCzb!_XOkBLULxoAqO73ll2FR_o1I04We2iwCEAKeUCYkeHU
Click to expand...
Click to collapse
There are already two methods to reset knox.
No point in opening another thread.
Reporting via N910G.
yashthemw said:
There are already two methods to reset knox.
No point in opening another thread.
Reporting via N910G.
Click to expand...
Click to collapse
thank bro i was reported
Sent from my SM-N900 using XDA-Developers mobile app
alra7al.syria said:
Hello my brothers,
it was the first post me here at XDA
will give you the original file for the reset counter the KNOX for note3 n900 only.
and I will raise it on the MEGA.
did you have to do is download and run ODIN program file and enter the device on the status of the DOWNLOADMODE and then you connect the device to USB and choose to reset the counter file after completion remove the battery and reinsert then enter into the DOWNLOADMODE once again and then chose any Software installed and want to be here have restored security
ALRA7AL.SYRIA 😉
Greetings to you if you like this topic only thank enough for me
https://mega.nz/#!VYV3xCzb!_XOkBLULxoAqO73ll2FR_o1I04We2iwCEAKeUCYkeHU
Click to expand...
Click to collapse
Also note 3 is too old and will not get any updates. Notb many would be interested in resetting the Knox.
Does this method actually work, my counter is 0x1, i didnt think it could be reset on the N9005??
gazza35 said:
Does this method actually work, my counter is 0x1, i didnt think it could be reset on the N9005??
Click to expand...
Click to collapse
Read post one .
will give you the original file for the reset counter the KNOX for note3 n900 only.
JJEgan said:
Read post one .
will give you the original file for the reset counter the KNOX for note3 n900 only.
Click to expand...
Click to collapse
Ah ok i see, not the N9005, cheers Anyway.
ok bro
gazza35 said:
Does this method actually work, my counter is 0x1, i didnt think it could be reset on the N9005??
Click to expand...
Click to collapse
us this link
http://forum.xda-developers.com/gal...t-guide-note-3-lte-sm-n9005-lollipop-t3093183
alra7al.syria said:
us this link
http://forum.xda-developers.com/gal...t-guide-note-3-lte-sm-n9005-lollipop-t3093183
Click to expand...
Click to collapse
Yer i have root already and Phronesis installed, unfortunatley i had tripped knox, probably when i installed twrp, but as of yet i dont think there is anyway to reset it.
Unless the phone has warranty or you want to sell the phone, I don't think resetting the Knox counter means much as a tripped Knox counter has never caused me any problems with the phone using stock or custom ROMs.
audit13 said:
Unless the phone has warranty or you want to sell the phone, I don't think resetting the Knox counter means much as a tripped Knox counter has never caused me any problems with the phone using stock or custom ROMs.
Click to expand...
Click to collapse
Yer it was just for re-sale purposes. just to make sure everything as it should be, but i know, means nothing really, just samsungs way of getting out of honouring warranty, interestingly, i once owned a galaxy s2, and purchased a USB JIG, years ago, i then had a s3, s4 and the jig wouldnt work on them so i threw it in a draw.
The other day i came across the jig, and thought id try it on my Note which reported the binary as custom and the counter as 0x1, Upon turning off my Note 3 and inserting the jig into the usb socket, it did indeed fire my phone straight into download mode, although my phone counter is still 0x1, it has indeed changed the binary from custom to official.
Lol, didnt think it would do anything but there ya go, Partial success.
Just Flashed today...
I got my device soft-brick after flashing it,
when i power the phone up, it doesn't boot into system, but showing..
Error Code : [ RST_STAT = 0X400 ]
POWER RESET or
UNKNOWN
UPLOAD MODE
Pls, did somebody experience it?...
---------- Post added at 09:25 AM ---------- Previous post was at 09:15 AM ----------
Thank a lot guys..
The problem is solved..
I have got my device back.