I own a Galaxy S4 locked to AT&T. I had my phone rooted and i was running on 4.4.2 through OTA update with NI1 baseband. I also had installed safestrap as my recovery. I was trying to unlock my phone and a guide said to downgrade to NB1 and so i downgraded to NB1 through odin as I read. After doing so my phone was stuck on the AT&T logo while booting. So i tried to flash back to NI1 but the phone went to a bootloop with and i still had 'custom' below the samsung logo when it booted. I tried to fix it with Kies but it failed to fix it and now all i get is ' Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I tried to fix it through Kies emergency firmware recovery and also through Kies firmware upgrade and initialisation and after downloading the firmware it shows it encountered and unknown error and when it does not show anything in the list below in recovery window. I tried flashing NI1 stock recovery and kernel as well as NC1. But couldn't fix it. I also tried to see how to get rid of odin mode but still i failed to fix it.
At the top of the screen after turning it on it says:
ODIN MODE (shows in red color)
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enabled
eMC BURST MODE enabled (Last two lines are in gray color and every lines except the first is in white color)
In download mode when kies fails two more lines in red are added :
START [224, 140]
SV REV. CHECK FAIL : fused , Binary : 1
Thanks to all you for your time. This is my first post I am sorry if i made it lengthy with irrelevant and or unnecessary information. Thank you once again.
View attachment 2999531
View attachment 2999534
View attachment 2999535
View attachment 2999536
View attachment 2999550
View attachment 2999553
View attachment 2999554
It's not uncommon to have to do a factory reset after doing an Odin restore. I'd use it to reflash the latest version and use the stock recovery to reset and then try to reboot.
es0tericcha0s said:
It's not uncommon to have to do a factory reset after doing an Odin restore. I'd use it to reflash the latest version and use the stock recovery to reset and then try to reboot.
Click to expand...
Click to collapse
I tried to. i can not flash stock recovery back. it says pass in odin but when it boots up it says custom and gets stuck in a boot lop for sometime then shuts it self down. Am i doing something wrong? Did I flash an outdated stock recovery or something? I wanted to odin NI1 but i couldnt find complete odin files for it just found rooted ones.
Vilthru said:
I tried to. i can not flash stock recovery back. it says pass in odin but when it boots up it says custom and gets stuck in a boot lop for sometime then shuts it self down. Am i doing something wrong? Did I flash an outdated stock recovery or something? I wanted to odin NI1 but i couldnt find complete odin files for it just found rooted ones.
Click to expand...
Click to collapse
I think that update is only available via OTA file. Looks like you should still be able to do NB1. Check here for details on the upgrade path suggested:
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
THANKS! It worked
es0tericcha0s said:
I think that update is only available via OTA file. Looks like you should still be able to do NB1. Check here for details on the upgrade path suggested:
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Click to expand...
Click to collapse
Thank you so much it worked. its running again! Thanks you loads and loads
Vilthru said:
Thank you so much it worked. its running again! Thanks you loads and loads
Click to expand...
Click to collapse
:good::highfive::victory:
Related
I tried to do AdamOutler's unlock bootloader stuff, and when i flashed the unlocked bootloader file in his thread i got a boot loop, so i tried to flash the stock bootloader file also in his thread. now i get the yellow triangle saying i need to take it back to the store. i can still flash with odin and i just tried to flash the unlocked bootloader again and now i get a fail message in odin.
please help!
even if i can get back to the bootloop i'm willing to take it back to verizon at this point. i just dont want to do that with the yellow triangle, i could just make up some something for the bootloop.
Have you tried flashing back with the stock odin image?
fhould oriushe
SirVilhelm said:
Have you tried flashing back with the stock odin image?
Click to expand...
Click to collapse
i am currently downloading that (internet sucks.... 1 hour download -_-), i hope it fixes is, otherwise i think its the bootloader thats throwing the error and ive tried flashing the stock bootloader file Adam gives in his guide with no luck
ODIN will flash the stock bootlooder
znilsson said:
I tried to do AdamOutler's unlock bootloader stuff, and when i flashed the unlocked bootloader file in his thread i got a boot loop, so i tried to flash the stock bootloader file also in his thread. now i get the yellow triangle saying i need to take it back to the store. i can still flash with odin and i just tried to flash the unlocked bootloader again and now i get a fail message in odin.
please help!
even if i can get back to the bootloop i'm willing to take it back to verizon at this point. i just dont want to do that with the yellow triangle, i could just make up some something for the bootloop.
Click to expand...
Click to collapse
the first thing you ever do before flashing anything on your device is have a stock rom to odin back on. second your not following directions. third your device is not bricked...flashing back to stock will bring it back.
I'm having a similar issue. I had followed adam's protocol for rooting and unlocking using CASUAL; once the process was completed I received a notification claiming that my device was now 'rooted and unlocked.' I then proceeded to download ROM manager and flash clockwork recovery and upon reboot receive the 'system software not authorized' message. At this point I attempted to use the official ODIN provided in droidstyle's guide on root/unlock/etc thread. I see a successful flash of the image but still cannot get out of the unauthorized system software error. Any ideas? Thanks in advance.
tehlol said:
I'm having a similar issue. I had followed adam's protocol for rooting and unlocking using CASUAL; once the process was completed I received a notification claiming that my device was now 'rooted and unlocked.' I then proceeded to download ROM manager and flash clockwork recovery and upon reboot receive the 'system software not authorized' message. At this point I attempted to use the official ODIN provided in droidstyle's guide on root/unlock/etc thread. I see a successful flash of the image but still cannot get out of the unauthorized system software error. Any ideas? Thanks in advance.
Click to expand...
Click to collapse
you need to use the pitfile with the stock odin image...check out section1 again!
droidstyle said:
you need to use the pitfile with the stock odin image...check out section1 again!
Click to expand...
Click to collapse
i did! that's why i was a bit surprised that it didn't work. i downloaded both the VRALJB 4.1.1 stock image and pit file, placed them into their corresponding locations in ODIN and flashed away. should i be allowing ODIN to repartition the disk? (thanks for the help droidstyle!)
tehlol said:
i did! that's why i was a bit surprised that it didn't work. i downloaded both the VRALJB 4.1.1 stock image and pit file, placed them into their corresponding locations in ODIN and flashed away. should i be allowing ODIN to repartition the disk? (thanks for the help droidstyle!)
Click to expand...
Click to collapse
Edited:Sorry read your earlier post. Not sure how to help sorry
Hello,
i have a galaxy mega I9205 LTE, three weeks ago i have flashed the original 4.4 KK update from samfirmware, and from that moment i have no more boot logo (the one with the "Galaxy mega" words), and download mode screen. I have done a full wipe (clean cache, wipe data, and kalvin wipe) from CMW and original recovery, tried with CM11 rom, and other 4.4 roms (can't downgrade to 4.2.2 ), nothing, my boot logo don't come out.
I think the fault is the bootloader, but i don't know if it can be restore or something like that.
How can i fix the problem?
Up
Tried another time, wipes on cwm recovery, flash with odin 3.09, no logos. Damn
UP
Did you flash the i9200 KK ROM or the i9205 LTE ROM for the phone?
ianneo said:
Did you flash the i9200 KK ROM or the i9205 LTE ROM for the phone?
Click to expand...
Click to collapse
Obivously 9205 lte like my phone.
UP! :angel:
Same problem : http://forum.xda-developers.com/galaxy-mega/help/enter-odin-download-mode-stock-4-4-2-t2811866
Cmon! Up!
try to use a different odin version, like 1.85.
and/or try another firmware.
i know there are at least 2 versions out there on sammobile, ne4 and nf2.
Flashing I9200XXUDNF3 from sammobile with odin 3.09 didnt slove the problem. Should i try with odin 3.04?? (My phone is GT-I9200)
Yeah. I tried to update to Kitkat and have flashed with almost every version of odin and the results were all the same.
However, I didn't encounter problems like you did.
Only the system (rom), recovery, boot (kernel) were flashed, and the modem (radio) and bootloader weren't registered into the phone.
And since my bootloader was still the old one (Knox-free), I was able to downgrade and did OTA update.
So now, for your situation, I can only think of trying to update with Kies.
DO NOT AND NEVER try what I did since you don't have download mode to confirm whether you have the new Knox bootloader, so you might end up BRICKED.
Again. Try to update with Kies. DO NOT downgrade by odin flash old firmwares (4.2.2).
And if Kies works out for you, let the other member (who's having same problem) know.
jk0l said:
Yeah. I tried to update to Kitkat and have flashed with almost every version of odin and the results were all the same.
However, I didn't encounter problems like you did.
Only the system (rom), recovery, boot (kernel) were flashed, and the modem (radio) and bootloader weren't registered into the phone.
And since my bootloader was still the old one (Knox-free), I was able to downgrade and did OTA update.
So now, for your situation, I can only think of trying to update with Kies.
DO NOT AND NEVER try what I did since you don't have download mode to confirm whether you have the new Knox bootloader, so you might end up BRICKED.
Again. Try to update with Kies. DO NOT downgrade by odin flash old firmwares (4.2.2).
And if Kies works out for you, let the other member (who's having same problem) know.
Click to expand...
Click to collapse
:good:
This is the #1 thing I am seeing members doing, attempting to downgrade from KK 4.4.2 Kitkat. It's becoming a trend so to speak. Although I will say it is sometimes a hardware error/issue, not many are reading before installing/attempting to downgrade.......
To the others.......
Once there, there is no going back. Yes you can flash Custom Roms all you want as long as you do not attempt to successfully downgrade the KitKat Knox Bootloader and pass. The OTA even tells you so and this is on any Galaxy phone you buy, not just the Mega.
If you can get into Recovery, then recover one of your backups, only if you didn't update to the Official KitKat 4.4 with the Updated Knox Bootloader either thru OTA or Odin
If you can still get into download mode then you are somewhat okay and there is still some hope. You can try flashing the Official Firmware to recover. Only flash ( pre KitKat 4.4 ) Official Firmwares thru Odin if you didn't already update to the Official KitKat 4.4 with the Updated Knox Bootloader either thru OTA or Odin.
If you can not get into Download Mode and the phone does not boot up or plugging in the phone to the computer with no battery installed you get the qhsusb_dload mode, then the possibility that you are likely bricked is good.
From here you either send it for JTag or see if someone with the same Phone and Carrier can make you a debrick image for you to burn to a memory card so your phone can be able to boot off it into Download Mode and Odin the Official Firmware. You will need to search for this method.
corrystile said:
Hello,
i have a galaxy mega I9205 LTE, three weeks ago i have flashed the original 4.4 KK update from samfirmware, and from that moment i have no more boot logo (the one with the "Galaxy mega" words), and download mode screen. I have done a full wipe (clean cache, wipe data, and kalvin wipe) from CMW and original recovery, tried with CM11 rom, and other 4.4 roms (can't downgrade to 4.2.2 ), nothing, my boot logo don't come out.
I think the fault is the bootloader, but i don't know if it can be restore or something like that.
How can i fix the problem?
Click to expand...
Click to collapse
UP.
Tried to use odin 3.09, update bootloader, with new Italian firmware, nothing.
Restore the phone through Kies: nothing.
Galaxy MEGA and Download Mode screen don't appear.
What can i do?
Hello guys i got same problem like you after OTA updade to kitkat,
Now i using spirit ron by silesh, what i did is just flash cutom recovery with odin like a blind man!
Just verify you enter download mode.
Turn off your phon( after phone vibrate)
Press vol down+home+power, hold together until phone vibrate and wait about 2sec and then release all button
To verify you enter download mode, please wait about 3minutes if phone not boot to os, you are just one step to download mode, just press and relese volume up to enter download mode
Then connect your phone to pc with odin run in administrator privileges, if odin detect your phone youre ready for rumble LOL
Sent from my GT-I9205 using XDA Free mobile app
So flashing Spirit Rom by Silesh will fix my problem?
corrystile said:
So flashing Spirit Rom by Silesh will fix my problem?
Click to expand...
Click to collapse
No it wont i think this is bootloader issue and custom rom wont change your bootloader so just did like a blind man in download mode, download mode works just only no display. Need new bootloader or bootloader fix for this problem
Sent from my GT-I9205 using XDA Free mobile app
SkyQaz said:
No it wont i think this is bootloader issue and custom rom wont change your bootloader so just did like a blind man in download mode, download mode works just only no display. Need new bootloader or bootloader fix for this problem
Click to expand...
Click to collapse
Flashing using kies didn't solve the problem for me too... "Need new bootloader or bootloader fix for this problem"
Hello,
I have the same problem. I dont have boot logo, i can access to download mode but without any screen.
I tried everything i could but the problem is still here.
When i turn my phone on i have a black screen and nothing else after.
Sometimes the phone boot on the rom i installed but i works 1 times/5.
Someone can help me please, i can't use my phone since i did the OTA on 4.4.2.
Thanks a lot
Just received a phone (Samsung note 3) everything works (sound, led, touchscreen etc..) except the screen is not powering on. (No samsung boot logo)
what is the best thing i can do, trying to recovery by Kies or Odin?
Hi
I am trying to install CM11 on my Galaxy S3 International, but get the following error when I try and update my Recovery and OS
When I boot into Download mode, it shows the Custom Binary counter as "No", which also stops me from adding any custom ROM's or Recoveries via Odin, which doesn't even detect the phone. USB debugging mode has been enabled
When I boot up into Recovery, it immediately shows the little android character on its side with a red exclamation mark, saying that no command was opened or given
This phone was given to me stock, as it wsa used by a family member who never messed around with anything on it except making calls and sending messages. It still has the stock Samsung ROM on it, android v4.3
I have tried sideloading Superuser, Recovery and CM11 to it, but that just gives me a signature verification error as well
View attachment 2907747
View attachment 2907748
linuxson said:
Hi
I am trying to install CM11 on my Galaxy S3 International, but get the following error when I try and update my Recovery and OS
When I boot into Download mode, it shows the Custom Binary counter as "No", which also stops me from adding any custom ROM's or Recoveries via Odin, which doesn't even detect the phone. USB debugging mode has been enabled
When I boot up into Recovery, it immediately shows the little android character on its side with a red exclamation mark, saying that no command was opened or given
This phone was given to me stock, as it wsa used by a family member who never messed around with anything on it except making calls and sending messages. It still has the stock Samsung ROM on it, android v4.3
I have tried sideloading Superuser, Recovery and CM11 to it, but that just gives me a signature verification error as well
View attachment 2907747
View attachment 2907748
Click to expand...
Click to collapse
The screen shot is the normal for download mode it say's no because you have not flashed anything to your device from odin
Please do some more research before you brick your device you can't flash custom roms with odin you need a custom recovery read the basics look here >> http://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 <<
tallman43 said:
The screen shot is the normal for download mode it say's no because you have not flashed anything to your device from odin
Please do some more research before you brick your device you can't flash custom roms with odin you need a custom recovery read the basics look here >> http://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 <<
Click to expand...
Click to collapse
Thanx for the reply tallman, but I have actually done this loads of times before, and am quite familiar with the whole setup. I currently have another S3 I am using with a ported version of MIUI v5, and used to flash CM versions constantly to my phone when I got bored. If you read the first part of my post, you will see that I mentione Odin does not recognize the above mentioned device, so I cant flash a custom recovery to it. Currently I am stuck as I cant flash recovery to it, and its native stock recovery also gives an error when I boot into it. I need to remove/reset the binary counter (have tried Triangle Away...but need superuser....which I cant flash cause it gives signature verification errors) and then see if it wont enable me to load recovery via Odin, and then flash CM via recovery. Any tips as to how I can fix the No option on my Custom Binary Download option?
linuxson said:
Thanx for the reply tallman, but I have actually done this loads of times before, and am quite familiar with the whole setup. I currently have another S3 I am using with a ported version of MIUI v5, and used to flash CM versions constantly to my phone when I got bored. If you read the first part of my post, you will see that I mentione Odin does not recognize the above mentioned device, so I cant flash a custom recovery to it. Currently I am stuck as I cant flash recovery to it, and its native stock recovery also gives an error when I boot into it. I need to remove/reset the binary counter (have tried Triangle Away...but need superuser....which I cant flash cause it gives signature verification errors) and then see if it wont enable me to load recovery via Odin, and then flash CM via recovery. Any tips as to how I can fix the No option on my Custom Binary Download option?
Click to expand...
Click to collapse
Lol I did read the first post but as soon as you mentioned flashing custom roms with odin then this say's to me lack of knowledge
First thing first why are you trying to reset binary counter when it is already set to normal? The screen shot you provided shows a normal download screen.
Your problem is not the binary count it is Odin,have you tried another version of Odin or another recovery like PhilZ what error if any is odin giving?
tallman43 said:
Lol I did read the first post but as soon as you mentioned flashing custom roms with odin then this say's to me lack of knowledge
First thing first why are you trying to reset binary counter when it is already set to normal? The screen shot you provided shows a normal download screen.
Your problem is not the binary count it is Odin,have you tried another version of Odin or another recovery like PhilZ what error if any is odin giving?
Click to expand...
Click to collapse
Lol...okay, I meant for the next part of the sentence to only mean "recovery via Odin"
Anyway, its the newest version of Odin. And while it may seem normal to some, this is not a "normal" load screen according to my previous experience. I bought my own S3, stock, and flashed roms to it almost immediately. The Custom Binary part is supposed to read either 0 (when new and unchanged) or any number after that depending on the amount of custom roms flashed. Odin does not detect the phone when in Download mode. It escapes me now the exact color and description at the top of the Odin window, but its supposed to show both color and text in one of those windows to indicate a succesful connection, which it doesnt
linuxson said:
Lol...okay, I meant for the next part of the sentence to only mean "recovery via Odin"
Anyway, its the newest version of Odin. And while it may seem normal to some, this is not a "normal" load screen according to my previous experience. I bought my own S3, stock, and flashed roms to it almost immediately. The Custom Binary part is supposed to read either 0 (when new and unchanged) or any number after that depending on the amount of custom roms flashed. Odin does not detect the phone when in Download mode. It escapes me now the exact color and description at the top of the Odin window, but its supposed to show both color and text in one of those windows to indicate a succesful connection, which it doesnt
Click to expand...
Click to collapse
No offence about your experience but100% It's supposed to read "no" not 0. Also whatever it say's 1,5,8 this would not stop you flashing with Odin.
I would seriously look at another version of odin or reinstall drivers or have you tried this tool >> http://forum.xda-developers.com/gal...msung-galaxy-s3-unified-toolkit-v8-0-t1703488 << make sure kies is not running on your computer also (if you have it) it can interfere with Odin.
@linuxson Just had a thought you could also try and root with framroot >> http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276 << and if you get it rooted you can flash a custom recovery with mobile Odin here >> https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&hl=en <<
Hi!
Phone finds the update, downloads the 600+ mb then restarts for installation then the Update Failed thingy comes up. And after this, while searching for updates it says " You have the latest version". Went to recovery more, reset the phone, then the same thing happens.
Any suggestions?
Or do I just download the 5.1.1 firmware and flash it with Odin?
Any help would be appreciated!
Halfbaked156 said:
Hi!
Phone finds the update, downloads the 600+ mb then restarts for installation then the Update Failed thingy comes up. And after this, while searching for updates it says " You have the latest version". Went to recovery more, reset the phone, then the same thing happens.
Any suggestions?
Or do I just download the 5.1.1 firmware and flash it with Odin?
Any help would be appreciated!
Click to expand...
Click to collapse
Download the latest stock firmware, and flash it with Odin.
Uzair40 said:
Download the latest stock firmware, and flash it with Odin.
Click to expand...
Click to collapse
Thanks for the reply. I guess that's the only alternative before I root. But there's this message in recovery mode "dm-verity verification failed....Need to check DRK first"
No idea what this is, have googled and it is not related to the problems shown on the web. Phone is not rooted, still official firmware.
So, is it safe to flash the latest firmware through Odin or will it brick my phone?
Halfbaked156 said:
Thanks for the reply. I guess that's the only alternative before I root. But there's this message in recovery mode "dm-verity verification failed....Need to check DRK first"
No idea what this is, have googled and it is not related to the problems shown on the web. Phone is not rooted, still official firmware.
So, is it safe to flash the latest firmware through Odin or will it brick my phone?
Click to expand...
Click to collapse
It's safe.
Uzair40 said:
It's safe.
Click to expand...
Click to collapse
Another obstacle. Odin or Win 10 doesn't recognize my phone in Download Mode. Have tried everything that I know of.....maybe it is win 10?
Halfbaked156 said:
Another obstacle. Odin or Win 10 doesn't recognize my phone in Download Mode. Have tried everything that I know of.....maybe it is win 10?
Click to expand...
Click to collapse
Got it working. Flashed the file..now it's stuck on the Samsung Galaxy S6 edge powered by Android screen.
Have tried factory reset, wipe cache, re-flashed....still stuck on it. Any help please?
Hi i was trying to flash cwm but now when i boot my phone all i see is samsung galaxy note 3 and on the top left it says :
Recovery booting...
recovery is not seandroid enforcing
set warranty bit:recovery
It just keeps rebooting i took out the battery and it still does this! I cant get into download mode or anything please help.
I used the odin root file (like a re-root) to fix this when it happened to me
Yep me too
More details like android version...the recovery filename would help. As others have stated, try flashing the cf-autoroot file for the SM-N900P
My guess is that your recovery isnt there. This happened to me once and I fixed it by reflashing TWRP thru Odin
Sent from my SM-N900P using Tapatalk
jpeery88 said:
I used the odin root file (like a re-root) to fix this when it happened to me
Click to expand...
Click to collapse
Where exactly did you find the odin root file? My phone works perfectly but I can't get into recovery mode to flash any other ROM. Thanks in advance.
mdj8606 said:
Where exactly did you find the odin root file? My phone works perfectly but I can't get into recovery mode to flash any other ROM. Thanks in advance.
Click to expand...
Click to collapse
No such thing as a odin root file, jpeery88 is correct just didn't say it quite right. First odin is software used to install (flash) rom and recovery (files) into your device (phone). ROMS are stock or custom and rooted. You need to get into download mode to install a custom recovery first before you can flash a custom rom. Click on ROM flashing basics in my signature for more info on how to get into download and recovery modes, root your device and more . . .
jimzweb1 said:
No such thing as a odin root file, jpeery88 is correct just didn't say it quite right. First odin is software used to install (flash) rom and recovery (files) into your device (phone). ROMS are stock or custom and rooted. You need to get into download mode to install a custom recovery first before you can flash a custom rom. Click on ROM flashing basics in my signature for more info on how to get into download and recovery modes, root your device and more . . .
Click to expand...
Click to collapse
I have a similar problem. N900p with android 5.0 wont go into recovery or download modes. It displays the message and restarts, repeating the process
nanatheo said:
I have a similar problem. N900p with android 5.0 wont go into recovery or download modes. It displays the message and restarts, repeating the process
Click to expand...
Click to collapse
This was normally a job for a USB jig. I've not found anything for a note 3 though. You might take the battery out over night and try again.
Maybe with the sd card out as well.
Finally I think I've read an attempt with battery out but plugged into power.
after that its punt and buy a "new to you" one on ebay; they're like $140 now a days.