I tried to install CWM earlier today and its gone wrong and now i get the dreaded error message
Firmware upgrade encountered an issue etc
Kies wont recover it either.
Now im hoping i can get it going again quickly
Just from skimming through here while trying to pack i gather i need to use odin to reflash the stock firmware.
I wouldnt normally ask but could some nice person spoon feed me given the circumstances of time constraints
Gavin01 said:
I tried to install CWM earlier today and its gone wrong and now i get the dreaded error message
Firmware upgrade encountered an issue etc
Kies wont recover it either.
Now im hoping i can get it going again quickly
Just from skimming through here while trying to pack i gather i need to use odin to reflash the stock firmware.
I wouldnt normally ask but could some nice person spoon feed me given the circumstances of time constraints
Click to expand...
Click to collapse
All you need to do is search google. No one spoon feeds you in real life so no one shouldn't spoon feed you here also.
http://forum.xda-developers.com/showthread.php?t=2261573
You need to follow these instructions but you need to download your correct firmware.
Sent from my SAMSUNG-SGH-I337
Use Odin to flash stock firmware by following this guide, I assume that you have the i9505, if so then flash this CWM,
thanks i need to find the right rom now
thanks fingers crossed
EDIT
im guessing this is the right rom
I9505XXUBMEA_I9505OXXBMF1_XEF.zip
thanks guys weve done it!
its resurrected!
cheers
I stuffed my phone up again and thought id post here instead of making a new thread.
flashed the latest modem which in turn has for some reason fubored all my dialling out and messages etc so i cant use the phone for anything other than browsing .....
I9505XXUBMEA_I9505OXXBMF1_XEF.zip<<<<<<<<<<<<this is what i used last time and it didnt work this time
so ive now tryed this one I9505XXUFNB8_I9505BTUFNB3_I9505XXUFNB8_HOME.tar.md5
my phone is a sim free s4.
the second one appears to work but wont get passed the lock screen with out continuous errors. (i note i now have the knox label in the bootloader)
How do i find the latest stock rom for my phone? so i can start again?
thanks
I had exact same issue so i falshed XXUFNB9 from sammobile and now im rooted runnin cm11 m9 .
Do suggest UNISTALLING samsung usb drives from pc and reinstalling fresh new ones for your device snd then flashing. I flashed 4 different firmwares. It was only until i reinstalled s4 usb drives my phone becsme alive. Dunno how but i reckon usb drives is the issue
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 all!
First of all i want to thank this site (and the people behind it) that makes everything android possible.
I feel privileged to be a member of this forum specially on rough times like what i am facing right now.
I rooted my Galaxy A8-A800i the other day and everything went great. I followed the instructions that i found here. Unfortunately, yesterday i turned off the OEM Unlock on my phone. Now, as the thread title says it. it is stuck on the Logo Screen with the annoying " Custom Binary blocked by FRP Lock ". i read a guide that ashyx made and i felt stupid. I didn't know that turning the OEM Unlock will do that to my Phone.
Right now, I am digging deep on this forums to try and revive my phone that is currently in Brick state.
i am downloading a firmware from sammobile for my phone, the problem i have is... i don't know how to use it. I don't know much about my phone but I do want to learn a lot and i know that this is the right place. I would like to ask assistance on how to use the firmware that I am downloading right now, and also, can i make the Knox Counter go "0" again?
Thanks for everything guys. I highly appreciate everything i've learned here so far.
rissered said:
Hello all!
First of all i want to thank this site (and the people behind it) that makes everything android possible.
I feel privileged to be a member of this forum specially on rough times like what i am facing right now.
I rooted my Galaxy A8-A800i the other day and everything went great. I followed the instructions that i found here. Unfortunately, yesterday i turned off the OEM Unlock on my phone. Now, as the thread title says it. it is stuck on the Logo Screen with the annoying " Custom Binary blocked by FRP Lock ". i read a guide that ashyx made and i felt stupid. I didn't know that turning the OEM Unlock will do that to my Phone.
Right now, I am digging deep on this forums to try and revive my phone that is currently in Brick state.
i am downloading a firmware from sammobile for my phone, the problem i have is... i don't know how to use it. I don't know much about my phone but I do want to learn a lot and i know that this is the right place. I would like to ask assistance on how to use the firmware that I am downloading right now, and also, can i make the Knox Counter go "0" again?
Thanks for everything guys. I highly appreciate everything i've learned here so far.
Click to expand...
Click to collapse
you can try flashing the official firmware I hope it fixes your phone.
and knox cannot be reset to 0
nepalbiraj said:
you can try flashing the official firmware I hope it fixes your phone.
and knox cannot be reset to 0
Click to expand...
Click to collapse
Thank you!... i downloaded the stock firmware from sammobile. but whenever i extract it there's a rar message saying it is corrupted so i DLed a new one, it has the same result. I haven't tried using it to fix my phone but i will try right now. Ill give an update on how it goes.
Tried flashing the new firmware but Odin can't detect my phone. i have the latest Driver for SAMSUNG and i have the latest Odin. I tried restarting my phone and my computer several times but it still fails. i am really frustrated and our of options right now. Even if Odin detects my phone there's no guarantee that the stock firmware will be installed properly since it always shows corrupt when i extract it from zip
rissered said:
Tried flashing the new firmware but Odin can't detect my phone. i have the latest Driver for SAMSUNG and i have the latest Odin. I tried restarting my phone and my computer several times but it still fails. i am really frustrated and our of options right now. Even if Odin detects my phone there's no guarantee that the stock firmware will be installed properly since it always shows corrupt when i extract it from zip
Click to expand...
Click to collapse
Install the Samsung drivers first, reboot your pc.
Start odin in Admin mode then put your device in download mode, plug in the usb cable. Your device should be detected.
Don't try flashing a corrupt firmware, it will be rejected anyway as it will fail the md5 check.
I suggest you use a different browser to download.
@ashyx hey! thanks for all your help. my internet went offline while i was trying to respond to the other thread. my phone is now fixed with your help. Thank you so much! only took 3 mins for the while Odin flashing to complete
This issue is now FIXED
rissered said:
This issue is now FIXED
Click to expand...
Click to collapse
but how? I have installed official firmware and flashed via odin and it shows"success", but then it gets stuck in the samsung logo. please help
Well the title says it all. Made a similar post in that wrong area I believe. That's probably why I didn't get a response.
Anyway, I had 6.0 but had downgraded to 5.0 and my build is SM-G870AUCUBF03. I tried to apply a stock kernel, G870A_NE4_Stock_Kernel.tar.md5, more specifically and it appears to be soft-bricked.
It shows the Samsung splash then after awhile going into recovery mode. I can still access Download mode as well. I tried hard-resetting, wiping data/factory settings. Any help would be very much appreciated. Thanks for taking the time to read this.
You could try the restore firmware function in Kies. It will be the easiest way to get back a working phone
I'm trying that right now, but it is saying that the connected device is not supported.
Can't find 5.0 stock firmware or anything really that leads me to believe that I can recover this phone. I can't believe this.
bfletxh said:
Can't find 5.0 stock firmware or anything really that leads me to believe that I can recover this phone. I can't believe this.
Click to expand...
Click to collapse
Read here.
https://www.sammobile.com/forum/showthread.php?t=30248
First Google search.
https://www.sammobile.com/firmwares/galaxy-s5-active/SM-G870A/
I'd suggest staying away from KIES and using Odin instead. In fact if you use Odin, and you have KIES installed on the same PC, disable it first. When all else fails, Odin is your friend. Just read up on the steps for using Odin if you're unfamiliar with it. And make sure you have the right firmware.
Sent from my Samsung SM-G900I using XDA Labs
The phone of my girlfriend has been stuck in a bootloop for a few days. It happened while she watched a video. Apparently at the same time she got a message that her phone ran out of space. Then it crashed and has been stuck in the loop since then. Her phone is not rooted. She did restore the device to default settings using recovery mode. This didn't do anything however.
I've tried using ODIN 3.12.3 to flash the newest rom from sammobile since her carrier is T-Mobile. I followed a guide from adnroid central since I never had done anything like this before. It all worked as far as ODIN goes but is still stuck in the bootloop. I'd link the guide but I need 10 posts before I can include outside links.
I'm not sure what the next step would be. If I should try an older ODIN version or use a different stock rom. Before the whole incident her android version was 6.0.1 I believe. Also in the download mode the product name is SMG-900T.
I hope someone can point me in the right direction on what to do. Thank you!
beerbat123 said:
The phone of my girlfriend has been stuck in a bootloop for a few days. It happened while she watched a video. Apparently at the same time she got a message that her phone ran out of space. Then it crashed and has been stuck in the loop since then. Her phone is not rooted. She did restore the device to default settings using recovery mode. This didn't do anything however.
I've tried using ODIN 3.12.3 to flash the newest rom from sammobile since her carrier is T-Mobile. I followed a guide from adnroid central since I never had done anything like this before. It all worked as far as ODIN goes but is still stuck in the bootloop. I'd link the guide but I need 10 posts before I can include outside links.
I'm not sure what the next step would be. If I should try an older ODIN version or use a different stock rom. Before the whole incident her android version was 6.0.1 I believe. Also in the download mode the product name is SMG-900T.
I hope someone can point me in the right direction on what to do. Thank you!
Click to expand...
Click to collapse
Have you tried flashing the marshmallow boot loader in odin?
RomBetaTester said:
Have you tried flashing the marshmallow boot loader in odin?
Click to expand...
Click to collapse
I'm not sure what you mean since I'm quite new to anything android. Would this be what you are talking about? I know it says only for S5 G900F and I have the G900T but would the overall process be the same?
Thank you for the reply though!
beerbat123 said:
I'm not sure what you mean since I'm quite new to anything android. Would this be what you are talking about? I know it says only for S5 G900F and I have the G900T but would the overall process be the same?
Thank you for the reply though!
Click to expand...
Click to collapse
Google search for marshmallow bootloader and flash it through Odin. I am very good with android. I can fix your problem. Is there anyway you could direct message me?