So, I tried to root my phone using instructions here
http://forum.xda-developers.com/showthread.php?t=1703488
I skimmed it the first time and missed the red, bold text saying not to use this on the US version and I also did not perform a backup, but thats in the past. Currently, it will boot, give me the Samsung logo and shutdown.
I'm sure this is wrong, so I hope someone can correct me.
-First, I need to find the correct rom(which I've been unable to do so far)
-I boot the phone into download mode(Vol down+home+power?) and plug it into my pc
-I open Odin, select the new rom as the pdf file, and press start.
Also, if I manage to screw this up again, would at&t be willing to help since its not totally bricked?
anonymous78 said:
So, I tried to root my phone using instructions here
http://forum.xda-developers.com/showthread.php?t=1703488
I skimmed it the first time and missed the red, bold text saying not to use this on the US version and I also did not perform a backup, but thats in the past. Currently, it will boot, give me the Samsung logo and shutdown.
I'm sure this is wrong, so I hope someone can correct me.
-First, I need to find the correct rom(which I've been unable to do so far)
-I boot the phone into download mode(Vol down+home+power?) and plug it into my pc
-I open Odin, select the new rom as the pdf file, and press start.
Also, if I manage to screw this up again, would at&t be willing to help since its not totally bricked?
Click to expand...
Click to collapse
Yes, this is correct. I would recommend looking on Sammobile and see if you can find a stock version for your phone model. You use the PDA file in ODIN, then you flash.
As for AT&T, I am not sure of their policy regarding software crashes on phones.
NightSkylar said:
Yes, this is correct. I would recommend looking on Sammobile and see if you can find a stock version for your phone model. You use the PDA file in ODIN, then you flash.
As for AT&T, I am not sure of their policy regarding software crashes on phones.
Click to expand...
Click to collapse
I looked last night and I didn't see it (sgh-i747 right?). Some guides use a PIT file in odin as well, will I need this and where would I find it? If I can't get the stock rom are there any compatible custom ones you'd recommend?
anonymous78 said:
I looked last night and I didn't see it (sgh-i747 right?). Some guides use a PIT file in odin as well, will I need this and where would I find it? If I can't get the stock rom are there any compatible custom ones you'd recommend?
Click to expand...
Click to collapse
Its rare that you would have to use a PIT File, mostly for the fact that it can mess up the bootloader.
As you have performed a soft brick, you likely do not have CWM, thus you cannot flash any custom firmware. *
My advice would be to wait to see if someone will upload the stock firmware for your model. I would also visit AT&T and say that your phone suffered a software crash.
:good:
* However, it is possible to flash a custom ROM if they can be flashed VIA ODIN, such as the CM9 Resurrection edition. (Does not exist for the AT&T Edition just yet)
I considered going into the store and playing dumb, but I heard they just replace the phone on the spot and sometimes later check the bricked phone before fixing it. I don't want to risk receiving a $600 bill in two weeks.
Can they tell the difference in my case?
I doubt it, as they are not trained as samsung tech support is.
Go into download mode, at the top corner, you will see
Produit name:
Custom Binary download:
Current Binary:
System Status:
Can you tell me what those are on your device?
NightSkylar said:
I doubt it, as they are not trained as samsung tech support is.
Go into download mode, at the top corner, you will see
Produit name:
Custom Binary download:
Current Binary:
System Status:
Can you tell me what those are on your device?
Click to expand...
Click to collapse
Product name: SGH-I747
Custom Binary download: yes(3 counts)
Current Binary: Custom
System Status: Official
In this case, as it is a custom Binary, it would most likely void your warranty. However, if they do not know how to check, then you should be good
So I went down to the at&t store and they couldn't do anything without sending it to tech or having them come in or something. She also said that if the warranty is void they won't do anything, not even for a fee.
I suppose I'll have to activate my old phone until the rom is released.
I'm sorry to hear that mate, but no worries, it wont be long till someone post's the official stock firmware
I hope you had taken a efs backup before this blunder.
Sent from my GT-I9300 using XDA
Man, I feel for you but just got to be patient with things like this. You're performing something that can and will damage your phone if you don't read the directions.
Sent from my GT-I9300 using xda app-developers app
Related
First off, I updated my GS4 OTA to I337UCUAMF3, which I wish I hadn't done. I lost root from it from it because I didn't do my research before accepting the update. I then searched for a way around the update and was able to re-root my phone. When I went to flash CM10 to my phone, it booted into download mode (Odin Mode) with a message in the upper left corner that reads:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
I found a fix for this that allows me to reboot my phone into working order. However, I am no longer able to boot into Recovery Mode, nor am I able to factory wipe my phone. Any time I attempt either of these things, it goes back into the "Could not do normal boot." Odin mode. I tried going back to stock, but it fails every time. I'm sort of new to all of this, obviously, but any help would be appreciated. Everything I have tried has been based on things I've read on XDA, but I guess just because someone posts something doesn't mean you should try it. Lesson learned.
AT&T Samsung Galaxy S4
SGH-I337
Baseband: I337UCUAMF3
Android 4.2.2
Build number: JDQ39.I337UCUAMF3
Kernel version: 3.4.0-812098
[email protected] #1
I can try my best to provide any further information that may assist you in assisting me! Just ask. Thanks in advance.
babrandon said:
First off, I updated my GS4 OTA to I337UCUAMF3, which I wish I hadn't done. I lost root from it from it because I didn't do my research before accepting the update. I then searched for a way around the update and was able to re-root my phone. When I went to flash CM10 to my phone, it booted into download mode (Odin Mode) with a message in the upper left corner that reads:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
I found a fix for this that allows me to reboot my phone into working order. However, I am no longer able to boot into Recovery Mode, nor am I able to factory wipe my phone. Any time I attempt either of these things, it goes back into the "Could not do normal boot." Odin mode. I tried going back to stock, but it fails every time. I'm sort of new to all of this, obviously, but any help would be appreciated. Everything I have tried has been based on things I've read on XDA, but I guess just because someone posts something doesn't mean you should try it. Lesson learned.
AT&T Samsung Galaxy S4
SGH-I337
Baseband: I337UCUAMF3
Android 4.2.2
Build number: JDQ39.I337UCUAMF3
Kernel version: 3.4.0-812098
[email protected] #1
I can try my best to provide any further information that may assist you in assisting me! Just ask. Thanks in advance.
Click to expand...
Click to collapse
having the same exact issues. Ive been trying the past 4 hours on getting it to work.
I think you're both hosed. You can try jtag. Check out mobiletechvideos.com. but call them first and explain what you did. Jtag may not even work.
Mf3 update has new bootloader. No custom recovery options as of now. You can have root but no recovery no flashing.
Sent from my HTC One using xda premium
You lost root because, as you said, you didn't do any research before accepting the OTA update. Now you're about to bork your device trying to flash onto it without, yet again, doing any research. I don't mean to be a hardass but I don't want to see anyone with a brick on this forum. You would be better off with an unrooted stock s4 and just keep your eyes and ears on xda for root/recovery updates for MF3.
Cheers
babrandon said:
First off, I updated my GS4 OTA to I337UCUAMF3, which I wish I hadn't done. I lost root from it from it because I didn't do my research before accepting the update. I then searched for a way around the update and was able to re-root my phone. When I went to flash CM10 to my phone, it booted into download mode (Odin Mode) with a message in the upper left corner that reads:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
I found a fix for this that allows me to reboot my phone into working order. However, I am no longer able to boot into Recovery Mode, nor am I able to factory wipe my phone. Any time I attempt either of these things, it goes back into the "Could not do normal boot." Odin mode. I tried going back to stock, but it fails every time. I'm sort of new to all of this, obviously, but any help would be appreciated. Everything I have tried has been based on things I've read on XDA, but I guess just because someone posts something doesn't mean you should try it. Lesson learned.
AT&T Samsung Galaxy S4
SGH-I337
Baseband: I337UCUAMF3
Android 4.2.2
Build number: JDQ39.I337UCUAMF3
Kernel version: 3.4.0-812098
[email protected] #1
I can try my best to provide any further information that may assist you in assisting me! Just ask. Thanks in advance.
Click to expand...
Click to collapse
I get the same thing as well. You said "I found a fix for this that allows me to reboot my phone into working order". Could you explain how you got this to reboot back to normal? That's all I want at this time too.
l33t_killa said:
I get the same thing as well. You said "I found a fix for this that allows me to reboot my phone into working order". Could you explain how you got this to reboot back to normal? That's all I want at this time too.
Click to expand...
Click to collapse
you just have to go to ur phone download mode by holding volume down and home button and when u get to download mode just simply click on cancel(restart) it will boot ur phone..
mdanish4 said:
you just have to go to ur phone download mode by holding volume down and home button and when u get to download mode just simply click on cancel(restart) it will boot ur phone..
Click to expand...
Click to collapse
Currently, it's sitting on the ATT sphere, white background, with the blue LED light on, got the opening chimes on the reboot as well. Been a couple of minutes now sitting there...
UPDATE
Was able to power it off as it was getting hot, got it plugged into laptop, charging animation is on, with the red LED light on as well. Cooling back down. What do you think now?
UPDATE 2
Did a reboot after charging for a bit, still hanging on the ATT sphere, white background, with the blue LED light on
mdanish4 said:
you just have to go to ur phone download mode by holding volume down and home button and when u get to download mode just simply click on cancel(restart) it will boot ur phone..
Click to expand...
Click to collapse
I am/Was in the EXACT same boat as the OP. I did what was posted above and I was good to go, meaning I can use my phone etc. I have had the phone for 5 days after using an iPhone for 5 years so I am still learning and almost learned the hard way. I will just wait until I can flash ROMs etc.
Thanks for making this thread OP.
babrandon said:
First off, I updated my GS4 OTA to I337UCUAMF3, which I wish I hadn't done. I lost root from it from it because I didn't do my research before accepting the update. I then searched for a way around the update and was able to re-root my phone. When I went to flash CM10 to my phone, it booted into download mode (Odin Mode) with a message in the upper left corner that reads:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
I found a fix for this that allows me to reboot my phone into working order. However, I am no longer able to boot into Recovery Mode, nor am I able to factory wipe my phone. Any time I attempt either of these things, it goes back into the "Could not do normal boot." Odin mode. I tried going back to stock, but it fails every time. I'm sort of new to all of this, obviously, but any help would be appreciated. Everything I have tried has been based on things I've read on XDA, but I guess just because someone posts something doesn't mean you should try it. Lesson learned.
AT&T Samsung Galaxy S4
SGH-I337
Baseband: I337UCUAMF3
Android 4.2.2
Build number: JDQ39.I337UCUAMF3
Kernel version: 3.4.0-812098
[email protected] #1
I can try my best to provide any further information that may assist you in assisting me! Just ask. Thanks in advance.
Click to expand...
Click to collapse
I'm having the exact same problem. I had read on the forums that people with root were able to install the OTA update no problem. But after I'd installed it this problem came up and there were no solutions in sight
ashkan101 said:
I'm having the exact same problem. I had read on the forums that people with root were able to install the OTA update no problem. But after I'd installed it this problem came up and there were no solutions in sight
Click to expand...
Click to collapse
The solution is in post 7 of this thread...though that will get you able to boot, you will not have a stock (or any) recovery...as trying to install a custom recovery when it's not actually possible is a bad thing!
ashkan101 said:
I'm having the exact same problem. I had read on the forums that people with root were able to install the OTA update no problem. But after I'd installed it this problem came up and there were no solutions in sight
Click to expand...
Click to collapse
Adding myself to this post... Having the same problem.
sincity said:
Adding myself to this post... Having the same problem.
Click to expand...
Click to collapse
Have you tried what was explained in post 7. Boot into download mode and when it gives you the option to continue or cancel, cancel. Others have reported this working.
jd1639 said:
Have you tried what was explained in post 7. Boot into download mode and when it gives you the option to continue or cancel, cancel. Others have reported this working.
Click to expand...
Click to collapse
Yes I did. Actually my situation is a little different. But was hoping to grab info from here too.
What happened: Installed Chainfire3D by accident. Reboot and from that point it got stuck in boot.
Rooted AT&T I337 MF3
sincity said:
Yes I did. Actually my situation is a little different. But was hoping to grab info from here too.
What happened: Installed Chainfire3D by accident. Reboot and from that point it got stuck in boot.
Rooted AT&T I337 MF3
Click to expand...
Click to collapse
Oh, didn't see it was for froyo and Gb only. What firmware do you have?
jd1639 said:
Oh, didn't see it was for froyo and Gb only. What firmware do you have?
Click to expand...
Click to collapse
whatever 4.2.2 is I'm assuming...
My phone was stock... I can't boot into recovery either.
sincity said:
whatever 4.2.2 is I'm assuming...
My phone was stock... I can't boot into recovery either.
Click to expand...
Click to collapse
All of these are 4.2.2, mdb, mdl, mf3. If you have the first two there's hope. If you have the last one, which I'm guessing you do, its no going to be so easy.
jd1639 said:
All of these are 4.2.2, mdb, mdl, mf3. If you have the first two there's hope. If you have the last one, which I'm guessing you do, its no going to be so easy.
Click to expand...
Click to collapse
MF3 - and I'm learning that I might just have to be patient until someone releases a stock/bootloader MF3. Sucks to have this issue.
sincity said:
MF3 - and I'm learning that I might just have to be patient until someone releases a stock/bootloader MF3. Sucks to have this issue.
Click to expand...
Click to collapse
Or perhaps the creeps in charge at AT&T will unlock the bootloader, that would get everyone up and running again. I've done my part to send them messages to that effect...(perhaps I should have not called them creeps, but I can't come up with a nastier term that is able to be printed politely.)
Stuck in download mode SGH-I337 AT&T!! KIES and Odin both fail
Is there a fix yet? I just got my device, successfully had it rooted and then tried installing a custom recovery using goo. It was stupid without research, but it happened.
Hi all,
Long time lurker, first time poster
I've been experimenting with a spare i9505 that I have, flashing roms etc (it was having serious wifi issues so I was trying to fix it)
However something's gone wrong and I now have the 'Firmware upgrade experienced an issue' screen, and Knox Warranty is 0x1. I don't really care about it as it's a spare, but I'd like to flash a ROM to it so that it at least works.
I'm not exactly a power user when it comes to this stuff, more an 'enthusiastic amateur'. I followed instructions in a similar thread to flash TWRP and use that to Advanced Wipe before flashing a new ROM, which I've done, but the threads I've found feature loads of ROMs and I don't know which one to use. I found a couple that I tried to use, but Odin is failing every time and SW Rev Check Fail pops up on the screen, which I believe (from more lurking!) means I'm trying to use the wrong firmware.
Was hoping someone here could point me in the right direction!
Just to recap the phone status:
- S4 i9505
- UK based (came from Vodafone if that matters?)
- Firmware update encountered an issue
- Knox Warranty Void 0x1
- Previously running 4.2.2
Thanks guys
Knox warranty void cannot be recoverd till now
Sent from my GT-I9500 using Tapatalk
aayushkhajuria2842 said:
Knox warranty void cannot be recoverd till now
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
I'm not worried about the warranty, I've read up on it and I know that's a lost cause. I just want the phone to work really as it's currently displaying 'Firmware update encountered an issue' on boot. I only mention the 0x1 thing as from my research I understand that it limits you in terms of what ROMs you can install, meaning I would need a particular one to get the phone working again.
Thanks!
Then install stock firmware via odin first
Sent from my GT-I9500 using Tapatalk
aayushkhajuria2842 said:
Then install stock firmware via odin first
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
... That's kinda the point of my post. I know what I need to do, I just don't know which file to use.
For example, this thread http://forum.xda-developers.com/showthread.php?t=2250824 has a bunch of stock firmware files, but I don't know which one I would need to download, for my specific circumstance.
What firmware u tried to install? If u tried to install android 4.3 or android 4.4.2 maybe ur bootloader is updated and u cant flash android 4.2.2. Give us more info :fingers-crossed:
Joku1981 said:
What firmware u tried to install? If u tried to install android 4.3 or android 4.4.2 maybe ur bootloader is updated and u cant flash android 4.2.2. Give us more info :fingers-crossed:
Click to expand...
Click to collapse
I was worried that might be the case.
OK so I've tried two md5 files so far:
I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME.tar.md5
I9505XXUFNB8_I9505BTUFNB3_I9505XXUFNB8_HOME.tar.md5
To PROPERLY go back and re-cap from beginning...
- Phone was stock, wi-fi didn't work (worked for a bit, then cut off and wouldn't come back on)
- Ran CyanogenMod Installer to update and hopefully fix the issue
- Install was successful but didn't fix wi-fi issues
- Used Odin to flash the 2nd md5 listed above, went back to stock but wi-fi still didn't work
- Tried to flash the 1st md5 listed above, didn't work and must have errored at some point as now I get that 'Firmware upgrade encountered an issue' message.
- Looked up the issue in a thread on here, followed instructions to flash TWRP, boot into Recovery > Wipe > Advanced wiping everything bar last two options, and then 'install your stock recovery firmware'
Only issue I have now, I don't know which file that is As I say the last two I tried (above) give me the SW Rev error, so they're clearly incorrect.
I don't care about warranty, and I don't care about root either really... just want the phone to work again, even on stock!
Well. Step by step:
- You will have to WIPE all
- If the phone is branded to Vodafone is one thing, if not is other.
- I let u the correct firmware for ur phone with Vodafone: HERE or HERE
- If ur phone is unbranded the correct firmware is: HERE
- Download it and flash it through ODIN
- If u have problems with ODIN, paste it here and good luck :highfive:
Awesome! Thanks man, the phone came from Vodafone initially but I don't think it's branded (no logos on the phone, no Vodafone logo on boot)
I'm downloading both just to make sure. Will let you know results ASAP! Thanks again :good:
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!
So I upgraded from 4.4.2 kitkat to 5.0 lollipop. However, I soft bricked my phone by installing the wrong xposed SDK. Now I'm trying to flash 4.4.2 kitkat back onto my bricked phone and then update back to lollipop. Problem is ODIN is not wanting to flash the g900a stock rom back. It gives me an error saying 'SW REV CHECK FAIL : [ABOOT]FUSED 2 > BINARY 1' does anyone know how to fix this as I'd like to fix my phone soon!
900A? That's the AT&T model isn't it? That being the case, the locked bootloader on your device is only ever going to let you flash 5.0 if you had 5.0 on your device before you bricked....
http://i.imgur.com/rVnFwJM.jpg
help
keithross39 said:
900A? That's the AT&T model isn't it? That being the case, the locked bootloader on your device is only ever going to let you flash 5.0 if you had 5.0 on your device before you bricked....
Click to expand...
Click to collapse
That's good an all but where can I find a 5.0 in a tar format! My phone is literally bricked so I can't access it to flash the .zip files to it. I can't find a .tar of lollipop 5.0 anywhere no matter where I look all the links for ones have been taken down! You wouldn't happen to have one would you?
Not sure fella.....checked every hosting/firmware website I can think of, and all I'm seeing are KitKat firmwares.....
Have you tried Kies to see if it'll perform an 'emergency recovery/restore'?
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Not sure fella.....checked every hosting/firmware website I can think of, and all I'm seeing are KitKat firmwares.....
Have you tried Kies to see if it'll perform an 'emergency recovery/restore'?
Click to expand...
Click to collapse
Kies won't recognize my device! It just says it's not supported! ;-; this is really unfortunate I've been looking everywhere with what little time I have (I work and I'm in college and it's around finals season for the semester so that doesn't help with time to fix this). I've been scouring everywhere but can't find anything. This is really unfortunate and I don't have the money to afford to have my phone fixed ;-; I'm really hoping I can find a solution soon! Everytime I try to install a kitkat 4.4.2 rom it just says FUSED 2 > BINARY 1 or something along those lines. From what I've heard that means I can't downgrade. Like I said what happened was I installed the wrong xposed sdk and it soft bricked. Every lollipop 5.0 rom I've found is in zip format. Now this wouldn't be a problem if I had a custom recovery that could flash zips and the means to put the zip on the phone. The problem is I don't (yes I've tried using ADB it refuses to put the zip on the phone it only lets me put .tar.md5's on there with the sideload and everything else just returns an error). If you find a solution or anyone else does please let me know! I'm In very dire need of help!! Also, my phone it makes it to the samsung galaxy s5 powered by android screen and then after that I just hear the AT&T noise but the screen doesn't change it just hangs there. I've also tried a full cache wipe and system restore in the recovery menu!
First of all.....The obvious....lol
These zips you mention, have you extracted them to see what's inside them.....
I know that sammobile and Samsung-updates provide their firmware .tars inside zips.....
Secondly, until someone makes an AT&T Lollipop firmware available, it looks like you're going to have to play the waiting game......at this point, I believe that with the correct firmware package, you WILL be able to recover your device....that may not be true further down the line if you continue to try 'potential' fixes.....
My advice is to leave it 'as-is' (unsatisfactory...I know) and wait for the firmware to become available......
Do you have an older device you can use in the mean time?
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
First of all.....The obvious....lol
These zips you mention, have you extracted them to see what's inside them.....
I know that sammobile and Samsung-updates provide their firmware .tars inside zips.....
Secondly, until someone makes an AT&T Lollipop firmware available, it looks like you're going to have to play the waiting game......at this point, I believe that with the correct firmware package, you WILL be able to recover your device....that may not be true further down the line if you continue to try 'potential' fixes.....
My advice is to leave it 'as-is' (unsatisfactory...I know) and wait for the firmware to become available......
Do you have an older device you can use in the mean time?
Click to expand...
Click to collapse
Yes I unzipped the zip. It was just files inside. I might just take it by an AT&T I'm pretty sure with all I've done to it the warranty is void but it's a worth a shot maybe they will take it in. I don't have an older device right now and I need to have some my phone soon as I have important usage of it with work. It seems I guess I don't have a choice left ;-; thank you though for all your help I'm very thankful for it
My Father-in-law tried updating the firmware on my wife's SM-G900V and now it's stuck in a boot loop. I am able to get it into download mode and recovery (I've cleaned the cache and factory reset it dozens of times), and I have been able to flash the latest marshmallow and lollipop images using Odin (passes with no issues), but it's still stuck in the boot loop.
When I get home from work tonight my plan is to try some of the "debricking" and or "rooting" guides I've found on this site:
https://forum.xda-developers.com/ve...images-hardbrick-recovery-plan-t3387010/page1
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Should one of these do the trick, or will I be wasting my time and should be trying something else? Thanks in advance for your advice/help!
RetroRider said:
My Father-in-law tried updating the firmware on my wife's SM-G900V and now it's stuck in a boot loop. I am able to get it into download mode and recovery (I've cleaned the cache and factory reset it dozens of times), and I have been able to flash the latest marshmallow and lollipop images using Odin (passes with no issues), but it's still stuck in the boot loop.
When I get home from work tonight my plan is to try some of the "debricking" and or "rooting" guides I've found on this site:
https://forum.xda-developers.com/ve...images-hardbrick-recovery-plan-t3387010/page1
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Should one of these do the trick, or will I be wasting my time and should be trying something else? Thanks in advance for your advice/help!
Click to expand...
Click to collapse
I have not tried the first method so I cannot say if it will work for a stock debrick. If you are going to use that, make sure the phone is on a PB1/PD1 firmware.
The second one is rooting the phone. I have usedthis one with both CIDs and have had no issues. Since the phone wont boot, you might not be able to locate the CID, so please read the following thread before starting:
https://forum.xda-developers.com/verizon-galaxy-s5/help/to-id-cid-15-loading-app-t3756413
UPDATE: Also, Here is a link to a firmware with the pit file:
https://forum.xda-developers.com/ve...rmware-pit-verizon-samsung-galaxy-s5-t3757416
You may want to try that first before doing the other ones. Having a pit file during the firmware install sometimes helps to fix it.
Try it, see if it works, if you have any more issues, let me know.
Good Luck!
Thanks for the quick reply!
I updated the pit file and didn't get any errors from Odin. I think the issue I'm stuck with is I don't know what original firmware was on here, so I randomly pick on of the many available ones (like I mentioned previously, I've tried Lollipop and Marshmallow). This time I tried this one:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar
The phone actually boots up and I hear the music of it booting up, but the screen doesn't come one. I can still get to recovery and download mode (but I can't see what I'm doing). Is this a matter of just working my way through the list of firmwares until I find the one that works?
Thanks again
RetroRider said:
Thanks for the quick reply!
I updated the pit file and didn't get any errors from Odin. I think the issue I'm stuck with is I don't know what original firmware was on here, so I randomly pick on of the many available ones (like I mentioned previously, I've tried Lollipop and Marshmallow). This time I tried this one:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar
The phone actually boots up and I hear the music of it booting up, but the screen doesn't come one. I can still get to recovery and download mode (but I can't see what I'm doing). Is this a matter of just working my way through the list of firmwares until I find the one that works?
Thanks again
Click to expand...
Click to collapse
Do you see the "Samsung Galaxy S5" logo when it first boots up? It sounds like the screen went bad.
Fear_The_Fluff said:
Do you see the "Samsung Galaxy S5" logo when it first boots up? It sounds like the screen went bad.
Click to expand...
Click to collapse
It depends on which firmware I flash it with.....usually I get the logo as it's in the bootloop. The only change was when I used that PB1 firmware and it actually booted, minus the screen....
RetroRider said:
It depends on which firmware I flash it with.....usually I get the logo as it's in the bootloop. The only change was when I used that PB1 firmware and it actually booted, minus the screen....
Click to expand...
Click to collapse
Try going into Download/Odin Mode and (first grab some binoculars LOL!) take a look at the top (small letter) information and (you may want to write it down) see what the device information states there.
It just seems as though you may have a specific variant of the S5 that may have been unlocked and flashed to the one you believe that you have...
... OR you are correct with the Variant but, are trying to flash the wrong Firmware Version (one of the previous releases) and the device is preventing it.
I think that it may be the first assumption but, I could be wrong...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Fear_The_Fluff said:
Do you see the "Samsung Galaxy S5" logo when it first boots up? It sounds like the screen went bad.
Click to expand...
Click to collapse
Ibuprophen said:
Try going into Download/Odin Mode and (first grab some binoculars LOL!) take a look at the top (small letter) information and (you may want to write it down) see what the device information states there.
It just seems as though you may have a specific variant of the S5 that may have been unlocked and flashed to the one you believe that you have...
... OR you are correct with the Variant but, are trying to flash the wrong Firmware Version (one of the previous releases) and the device is preventing it.
I think that it may be the first assumption but, I could be wrong...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
here's what I see when I go into download mode:
ODIN MODE
PRODUCT NAME: SM-G900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD : ENABLE
UDC START
Is there anything there that tells me what version of firmware I should be using?
RetroRider said:
Is there anything there that tells me what version of firmware I should be using?
Click to expand...
Click to collapse
Product name is correct.
I'd flash this one: https://androidfilehost.com/?fid=818070582850486654
It's the latest firmware with full-wipe.
The first boot should take 12-15 min.
If the phone does not boot within 20 min. it will mean a hardware problem.