Database Info

How to get Samsung Galaxy S 4G into Recovery mode

I messed up my phone trying http://forum.xda-developers.com/showthread.php?t=892297 I can't figure out how to get the phone into recovery now that it just goes to black screen after it boots. I can't turn on debugging mode, and I've tried all the button combination's I could find to boot in recovery.

It is a little tricky but with the phone powered off push and hold the volume up and volume down button at the same time while you push and hold the power button. Keep holding the whole volume button in until it gets into recovery. You will see the splash screen then recovery should come up.

holy hell thank you so much... now how to restore this thing... hmmm

How do I get ADB now?
Can I start ADB while in recovery?

You shouldn't even be in recovery seeing as how there is no recovery yet.
Sent from my SGH-T959V using XDA App

What do you mean.. I'm staring at it now.. appears legit as well:
Android system recovery <3e>
Samsung Recovery Utils
-for BML-
etc...

that's stock recovery. there is no modded recovery to allow backup/restore/rom flashing.
You will need to ODIN if your phone is hosed.

Stock recovery? No, adb pretty much won't work in that.
Sent from my SGH-T959V using XDA App

krylon360 said:
that's stock recovery. there is no modded recovery to allow backup/restore/rom flashing.
You will need to ODIN if your phone is hosed.
Click to expand...
Click to collapse
How exactly do I ODIN.. because its hosed...

aloneinshadow said:
Stock recovery? No, adb pretty much won't work in that.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
I got ADB to work.. however it doesn't allow root.. so pretty much pointless. It was really odd though ADB would work on and off, if it didn't work I would reboot into recovery and try again and it would work, if I rebooted back into recovery it wouldn't work until I rebooted back into recovery again.

adb reboot download
grab ODIN 1.7
flash the tar located here
http://forum.xda-developers.com/showthread.php?t=978836
the tar needs to go in PDA. DO NOT check any boxes that aren't already checked.
Do Not use a PIT

krylon360 said:
adb reboot download
grab ODIN 1.7
flash the tar located here
http://forum.xda-developers.com/showthread.php?t=978836
the tar needs to go in PDA. DO NOT check any boxes that aren't already checked.
Do Not use a PIT
Click to expand...
Click to collapse
Just to confirm I need ADB reboot download, ODIN 1.7, and [ROM-ODIN]T959VUVKB5 Stock + Root? I'm very new to this sorry, just switched over from an iPhone and learning very quickly Android modding is a lot more dangerous then iOS. Also maybe is there a guide for doing this? I really don't want to mess anything up.

Sario27 said:
Just to confirm I need ADB reboot download, ODIN 1.7, and [ROM-ODIN]T959VUVKB5 Stock + Root? I'm very new to this sorry, just switched over from an iPhone and learning very quickly Android modding is a lot more dangerous then iOS.
Click to expand...
Click to collapse
you are correct.

krylon360 said:
you are correct.
Click to expand...
Click to collapse
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> factoryfs.rfs
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What am I doing wrong?

Sario27 said:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> factoryfs.rfs
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What am I doing wrong?
Click to expand...
Click to collapse
keep trying. ODIN sucks like that.

Thanks everyone! It is now working and I still have root!
Thanks for all your help everyone especially krylon360 for the fixing advice.

New to Android, so please forgive a question that may be obvious to those more experienced.
On entering the recovery console, there are four options:
reboot system
reinstall packages
delete all user data
delete cache data
While the first is pretty clear, the others aren't so much. Any greater clarity would be helpful, as well as how these options differ from the user-land
Settings > Privacy > Factory data reset
which, I assume, returns everything except the SD card to as-shipped configuration, yes? I'm also guessing that there are things like usage counters that aren't reset either, yes?
One of the things I want to do before I go hog-wild with new firmware is to at least get a good tar of the stock configuration.
TIA

I guess it depends on what you did to your system. if you messed it up and want to get back to a clean stock system, follow krylon360 post top of this second page. get the tar file and odin 1.7 (that's the one that is working mostly for everyone) Shut down your phone. pull the battery out. connect your tether cable to the phone and USB to computer. start oden put tar file in PDA box. don't change any other settings. Put your phone in download mode by pressing both up/down volume buttons and insert the battery. once in download mode, click on Start on oden. wait for it to finish and the phone will reboot when successfull tranfer is complete. give the phone time to boot up and you should be good. note: you need to make sure that the samsung USB drivers are installed in your computer properly for this to work. ( I assume they are if you got this far) Good Luck.

nwpro3 said:
I guess it depends on what you did to your system. if you messed it up and want to get back to a clean stock system, follow krylon360 post top of this second page. get the tar file and odin 1.7 (that's the one that is working mostly for everyone) Shut down your phone. pull the battery out. connect your tether cable to the phone and USB to computer. start oden put tar file in PDA box. don't change any other settings. Put your phone in download mode by pressing both up/down volume buttons and insert the battery. once in download mode, click on Start on oden. wait for it to finish and the phone will reboot when successfull tranfer is complete. give the phone time to boot up and you should be good.
Click to expand...
Click to collapse
you'll also have better results if you remove your SD and sim as well.

Well Crap
After reading a lot of the post on this forum, it is clear that I'm an idiot. Since I seem to be the only one who screwed this up. I installed Gingerbread on my Galaxy S 4g. I was successful in that endeavour. However, I went looking for a root and screwed that up. Now my phone just says, "firmware upgrade fail! Try using recovery mode." The problem is that I can't get into recovery mode the same way anymore. I can't get into download mode either. Can anyone offer any help.

*[HELP]* Need help unbricking Galaxy Note 10.1

Hi guys,
My galaxy note 10.1(2013) is was on <Stock> Android Kitkat .
Out of curiosity of rooting, i flashed CF Auto Root using odin.
The device restarted, and features seemed fine with new Root App too.
In few minutes however, device rebooted.. and went into a bootloop. :crying:
which still is, as long as device is on - has battery.
SUMMARY:
1. Recovery mode is not accessible now - device goes into recovery mode and restarts.
2. Normal boot is going into bootloop.
3. Download mode - HOWEVER is available !
PROBLEM :
-on trying to reflash stock rom/any Tar File for my device using odin,
odin fails with message :
NAND WRITE START
FAIL
----------------------------------------------------------------------------------------------------------------
Please help solve.
I do not want my beloved<soft bricked> device to die a sudden death .
Will appreciate you guys putting life back in it !

Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.

chrismin13 said:
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
Click to expand...
Click to collapse
Having the exact same problem.
Tryed:
Flashing a 4.0.4 stock rom trough odin: sucess flash but still bootloop
Flashing a 4.0.4 stock rom trough odin + pit file for 8010 4.0.4: sucess flash but still bootloop
Flashing CWM and TWRP trough ODIN with auto-reboot and without autoreboot checked: sucess flash but still bootloop and no access do recovery
Flashing 4.1.2 or 4.4.2 stock: same error as OP
Getting pretty desperate now

chrismin13 said:
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
Click to expand...
Click to collapse
will get back with update tomorrow.

glorifiedg said:
Having the exact same problem.
Tryed:
Flashing a 4.0.4 stock rom trough odin: sucess flash but still bootloop
Flashing a 4.0.4 stock rom trough odin + pit file for 8010 4.0.4: sucess flash but still bootloop
Flashing CWM and TWRP trough ODIN with auto-reboot and without autoreboot checked: sucess flash but still bootloop and no access do recovery
Flashing 4.1.2 or 4.4.2 stock: same error as OP
Getting pretty desperate now
Click to expand...
Click to collapse
.. mine is not exactly the same.
you are able to write/flash onto NAND .. odin success for you.
My nand write itself fails.
End result is same, true there.

Anand.prashar said:
.. mine is not exactly the same.
you are able to write/flash onto NAND .. odin success for you.
My nand write itself fails.
End result is same, true there.
Click to expand...
Click to collapse
'Cause you probably didn't try the 4.0.4. I have nand write fail with the most recent versions also :S

Suggestion to no avail
chrismin13 said:
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
Click to expand...
Click to collapse
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNE6_N8000ODDDNE4_N8000DDUCNE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing OS failed.
What could be hindering or preventing NAND write ?

Anand.prashar said:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNE6_N8000ODDDNE4_N8000DDUCNE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing OS failed.
What could be hindering or preventing NAND write ?
Click to expand...
Click to collapse
You have the N8000. Correct? If you're working on a desktop try plugging the tablet in the back ports of your pc without using a USB hub or a usb 3.0 port. It sounds weird, I know, but that was the problem multiple times for me because the front ports of the computer use a usb hub that sometimes creates issues. And if you flash twrp what happens? I hope that it's not the chipset that's damaged. Also, what does download mode say? Does it write in binary status official? If yes, then flash stock frimware and recovery and try going it for warranty replacement. They won't understand what has happened I believe. And if all of this doesn't do anything try a different computer and a new usb cable. A computer with an OS older than Windows 8 would be great and without usb 3.0 ports. You can also try re-downloading all the files. Have you seen zedomax's video about unbricking our tablet? It covers everything I told you and much more so here's a link. http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware. Another idea is to use a toolbox for our device. Just tell me if anything of all of these methods works. I hope something does the trick!
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Wow. Have you realized how many people have issues with kitkat? So many people report broken devices and they all run kitkat. That's wierd.

[/COLOR]
chrismin13 said:
You have the N8000. Correct? If you're working on a desktop try plugging the tablet in the back ports of your pc without using a USB hub or a usb 3.0 port. It sounds weird, I know, but that was the problem multiple times for me because the front ports of the computer use a usb hub that sometimes creates issues. And if you flash twrp what happens? I hope that it's not the chipset that's damaged. Also, what does download mode say? Does it write in binary status official? If yes, then flash stock frimware and recovery and try going it for warranty replacement. They won't understand what has happened I believe. And if all of this doesn't do anything try a different computer and a new usb cable. A computer with an OS older than Windows 8 would be great and without usb 3.0 ports. You can also try re-downloading all the files. Have you seen zedomax's video about unbricking our tablet? It covers everything I told you and much more so here's a link. http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware. Another idea is to use a toolbox for our device. Just tell me if anything of all of these methods works. I hope something does the trick!
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Wow. Have you realized how many people have issues with kitkat? So many people report broken devices and they all run kitkat. That's wierd.[/QUOTE
same problem here but i thing we need to clear all those built up cache in order to proceed right? but no boot recovery just the Odin downloading image. now if we can find a way to clear all those cache i'm sure'll work but don't know how to clear it from the "downloading do not turn off target" unless somebody figure this out.
Click to expand...
Click to collapse

* Serious issue awaiting resolution *
chrismin13 said:
You have the N8000. Correct? If you're working on a desktop try plugging the tablet in the back ports of your pc without using a USB hub or a usb 3.0 port. It sounds weird, I know, but that was the problem multiple times for me because the front ports of the computer use a usb hub that sometimes creates issues. And if you flash twrp what happens? I hope that it's not the chipset that's damaged. Also, what does download mode say? Does it write in binary status official? If yes, then flash stock frimware and recovery and try going it for warranty replacement. They won't understand what has happened I believe. And if all of this doesn't do anything try a different computer and a new usb cable. A computer with an OS older than Windows 8 would be great and without usb 3.0 ports. You can also try re-downloading all the files. Have you seen zedomax's video about unbricking our tablet? It covers everything I told you and much more so here's a link. Another idea is to use a toolbox for our device. Just tell me if anything of all of these methods works. I hope something does the trick!
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Wow. Have you realized how many people have issues with kitkat? So many people report broken devices and they all run kitkat. That's wierd.
Click to expand...
Click to collapse
Sorry for delay, work kept busy.
You have the N8000. Correct?
-Yes
If you're working on a desktop ?
-No
- On laptop :
same laptop i used to root my tab using CF-Auto Root.
and have flashed ones in past on the older rom for this tab.
- Port : used USB 2.0
TWRP recovery ?
- Getting same error on odin as stock Rom.
<< I am attaching 3 snapshots >>
- Odin desktop Software in work
- Download mode of device
- Texts on download mode screen of device
<i believe it says custom, coz i had already 'seemingly' rooted stock rom>
------------------------------------------------------------------------------------------------------------
It would be worthwhile to mention the last flashing trial.
- it was upgraded to Kitkat released for this device
2 months ago : using Odin [as i had rooted the previous Default firmware too]
- having gotten bored with non-SU controls,
i flashed CF Auto Root
that would give me "SuperSU app" control without changing existing Firmware.
- Device rebooted after flashing (hopefully correct steps, i think)
"Super SU" app was available for me.
- Note : Upon opening app, i was prompted with a message
"KNOX has been detected on this device... would i like to remove/disable ?"
- I hit Yes.
Got a popup soon, that KNOX was successfully removed.
- and then, it went FINE for about an hour.
AND THEN CAME THE BOOTLOOP all of a sudden.
------------------------------------------------------------------------------------------------------------
Summary:
I am not able to figure out what could have caused this...
flashing/knox/ anything else ?

I have the same problem except that I can get too Recovery mode, but it's useless. It's been since April, so far no hope.

ayeladawy said:
I have the same problem except that I can get too Recovery mode, but it's useless. It's been since April, so far no hope.
Click to expand...
Click to collapse
Did you already tried to flash the 4.4 leaked version with the 5 files over odin?
And also the pit file provided there.
That solved my problem a couple of months ago.

ayeladawy said:
I have the same problem except that I can get too Recovery mode, but it's useless. It's been since April, so far no hope.
Click to expand...
Click to collapse
hey,
what do you mean by "useless" ?
please explain clearly.
i just got one of these the other day,gt-n8013, maybe it's possible to whip up a fix.
a thought i have is that a boned odin install may take on the same behaviour
as a certain kernel function where a temporary kernel to be booted to
may be being stored into ram, meaning when you reboot to odin mode
you basically pick up where you left off. poweroff your tab and then plug in
your charger like normal. if your battery image shows up then, your kernel is intact or mostly so.
if that's the case maybe running your battery dead or disconnecting it will
work like pulling the cmos battery in a pc to correct a bad bios configuration.
meaning after the power is finally and truly off then ram will clear completely and when
you recharge and reboot back to odin you will be at baseline again.
the above approach has worked with some lower end tabs i've owned
including the galaxy tab 2 7.0
m

Hey, I ran the battery dead on it and when plugged there no charging indictor but instead it power back on but blank black screen no boot logo or nothing what does that mean?

dough30i said:
Hey, I ran the battery dead on it and when plugged there no charging indictor but instead it power back on but blank black screen no boot logo or nothing what does that mean?
Click to expand...
Click to collapse
okay, try for odin now, but try recovery first.
@dough30i
going back through this thread if you did the same thing with cf-root-crap you may have
damaged you bootloader. which is very not good. if you've gotten recovery up let me know.
you will need to get adb running and just for verification i need your model i.d.

No recovery but I can get into Odin.see I done try all the step and every step no go. It something got to do with NAND FILE it won't write or something...

dough30i said:
No recovery but I can get into Odin.see I done try all the step and every step no go. It something got to do with NAND FILE it won't write or something...
Click to expand...
Click to collapse
okay, are you trying to write a full firmware image or just a recovery or boot tar.md5?
or is it flat out no go?

Full Firmware..oh i forget to mention at the beginning I had recovery boot logo, but then my stupid ass just had to mess with it more in the Odin to PC thing while I was trying to fixed it -_- my dumb ass got to anxious so I thought that when "NAND file not writing" I figure ohh maybe I needed to clear cache right so in the Odin I check repartition and I think that's why I have no samsung logo and recovery and now I back to somewhat square if u call it that. -__-

dough30i said:
Full Firmware..oh i forget to mention at the beginning I had recovery boot logo, but then my stupid ass just had to mess with it more in the Odin to PC thing while I was trying to fixed it -_- my dumb ass got to anxious so I thought that when "NAND file not writing" I figure ohh maybe I needed to clear cache right so in the Odin I check repartition and I think that's why I have no samsung logo and recovery and now I back to somewhat square if u call it that. -__-
Click to expand...
Click to collapse
okay,
first, we do not put ourselves down. technology is unnatural, we make mistakes.
second, we do not panic or act rashly.
that being said if you can still get into odin, all is not yet lost. while i am pulling the pit file from
my device you will need to look up the correct way to write it to your device using odin.
i will be back in about 10 - 15 minutes.
use the force.
m

@dough30i
okay,
this is the pit file pulled from my n8013 . what i've read it should do the trick.
however, let's be clear.
1 you are in a bad situation, with nothing to lose.
2 this may not work but, then again it might.
3 you are the the final say as to wether or not you will attempt this
4 you have secured the correct knowledge on applying the pit file and writing in odin.
if yes to all of the above, download the attached file and remove the .txt extension
m
this is the thread i pulled the information from
http://forum.xda-developers.com/showthread.php?t=2268735

ODIN Flashable Lollipop Bootloader and Modem N9005

What is the advantages with this Odin flashable file containing only the lollipop bootloader and modem?
- It means you can flash it in ODIN, without having to wipe your beloved custom ROM or Recovery to get the Lollipop Bootloader and Modem
The firmware I extracted the modem and bootloader from is the Polish XEO version.
Info from Sammobile.com:
Model SM-N9005
Model name GALAXY Note 3 LTE
Country Poland
Version Android 5.0
Changelist 3643614
Build date Wed, 25 Feb 2015 12:57:23 +0000
Product code XEO
PDA N9005XXUGBOB6
CSC N9005XEOGBOA4
Please follow these steps if you would like to flash:
1. Completely turn of your phone, usb cable must me disconnected.
2. After the phone is turned off, remove the battery for 5 seconds
3. Put the battery back in and boot directly in to download mode (vol down + home + power) then press vol up 1 time to enter download mode.
4. Open ODIN on your PC and put the downloaded file in the AP section (Odin v3.09)
5. Now connect your phone to the pc via USB
6. When you can se that the phone is connected to Odin, press start and just let Odin do its thing.
7. Check on your phone if the bootloader and modem has updated. I use an app called Phone Info Samsung from the play store.
8. Profit
When I did the flash as described above everything went perfect.
I have read that some people haveing issues getting the modem to stick, if that happens:
1. Untic auto-reboot in ODIN before you flash.
2. When the flash is finished in ODIN force a new direct reboot in to download mode (vol down + home + power)
3. Then tick back the auto-reboot tab, flash the file one more time and let the phone autoreboot. Hopfully the modem will have sticked.
Please flash at your own risk, I take no responsebility for bricked devices etc.
Download link: http://www.filedropper.com/hltelollipopbootloadermodemtar

What is the point exactly to flash only the bootloader? I can't find it using the search function, sorry for asking

mantiyeah said:
What is the point exactly to flash only the bootloader? I can't find it using the search function, sorry for asking
Click to expand...
Click to collapse
The point is, if you are on a custom ROM.
You can flash this file and get the latest lollipop bootloader and modem without installing the full stock firmware and wipe your ROM.
Why?
Because some lollipop based custom kernels and roms needs the lollipop bootloader and modem to function properly.
One example is arter97 great custom kernel v5 and up needs lollipop bootloader and modem to work.
Hope it helps

But the bootloader makes other problems. Recovery have bugs with this.

Schrotty35 said:
But the bootloader makes other problems. Recovery have bugs with this.
Click to expand...
Click to collapse
Can you please enlighten me what type of bugs?
Im asking because I am curious since my recovery seems to work very well on lollipop bootloader.
Im using philz_touch_6.48.4
Thanks in advance

Whene you format cache or data/media this is very very slow. With kitkat is very fast. Whene you install a asop rom and will install later a custom stock rom this not work and many other problems but with twrp there is the same problems too. Only wipe is on twrp faster.

Schrotty35 said:
Whene you format cache or data/media this is very very slow. With kitkat is very fast. Whene you install a asop rom and will install later a custom stock rom this not work and many other problems but with twrp there is the same problems too. Only wipe is on twrp faster.
Click to expand...
Click to collapse
I just formatet cache and it went just as fast now as it used to go with KitKat bootloader.
I also installed Temasek CM12 Unofficial v8.9 and that went fast too.
I even booted in and out of recovery from CM boot menu and also enterd in to recovery from a "cold" boot to se if there were any issues getting in to the recovery.
No issues what so ever. I made a nandroid backup just to have tried that too, also worked like a charm.
Cant say Im having your issues with the lollipop bootloader. For me everything works the way it should do.
I hope you get the Lollipop bootloader to work for you in the future

Nice to see you have posted bootloader and modem. Unfortunately found it out after I have downloaded full original LP, installed it, softbricked my phone, recovered from that, wiped out everything, installed Temasek's ROM, restored applications so finally ready to install Arter's kernel You can imagine how much time it took instead of option you have provided

Kuratko said:
Nice to see you have posted bootloader and modem. Unfortunately found it out after I have downloaded full original LP, installed it, softbricked my phone, recovered from that, wiped out everything, installed Temasek's ROM, restored applications so finally ready to install Arter's kernel You can imagine how much time it took instead of option you have provided
Click to expand...
Click to collapse
Yes I can imagine
Thats why I desided to post it, so maby I could save some people from the hassle you went through
But I`ll guess Arter97`s kernel was worth the hassle anyway, just an amazing kernel for the Note 3

just ask can i update lollipop bl & m over my custom rom super fast v8.0 4.4.2 & it will work without any prob ?

Hi iketil
I just used your file to flash latest bootloader and modem to my N9005 and it worked perfectly
No need for me to flash a second time to make the bootloader stick.
I did have an older version of CWM which went into boot loop when I tried to enter recovery, but flashing the latest TWRP fixed that.
Thanks for taking the time to make this, saved me a bunch of time :good:

There is no persist file but this need it to.

how big is this file supposed to be? the filehost keeps cutting me off during the download and it fails the MD5 checkes.
---------- Post added at 08:12 AM ---------- Previous post was at 08:05 AM ----------
6. When you can se that the phone is connected to Odin, press start and just let Odin do its thing.
Click to expand...
Click to collapse
At which stage should i consider that Odin has done its thing? Below is the log of the flashing thus far, but the phone is still on the screen with "Samsung GALAXY Note3 SM-9005" logo after 10 mins.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> hlte_lollipop_bootloader_modem.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> hlte_lollipop_bootloader_modem.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> hlte_lollipop_bootloader_modem.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Added!!
Click to expand...
Click to collapse

cojak72 said:
just ask can i update lollipop bl & m over my custom rom super fast v8.0 4.4.2 & it will work without any prob ?
Click to expand...
Click to collapse
Thats what I did on Temasek CM12 Unofficial ROM.
I had no problems at all. But I cant give you any insurance that you wont have any.
Just follow the instructions carefully and it should work if you have the sm-n9005 (hlte).

3XTR3M1ST said:
how big is this file supposed to be? the filehost keeps cutting me off during the download and it fails the MD5 checkes.
---------- Post added at 08:12 AM ---------- Previous post was at 08:05 AM ----------
At which stage should i consider that Odin has done its thing? Below is the log of the flashing thus far, but the phone is still on the screen with "Samsung GALAXY Note3 SM-9005" logo after 10 mins.
Click to expand...
Click to collapse
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 ?

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

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 keep getting a file thats 56.6MB everytime I download the file. Is this safe to flash. Odin passes the md5 check...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

3XTR3M1ST said:
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
Sorry to see you are having problems with your phone :\
I have read your thread and as others have suggested, flashing the official samsung firmware downloaded from sammobile.com would be the way to go.
Seems like your phone is in a bad state, really hope that you have not recievd a fake\clone
And my file does not include the recovery, but if you flash the original samsung firmware it should bring back the original recovery and restore your phone to a working condition.
Hope you mange to fix it Good luck!

shiverz07 said:
I keep getting a file thats 56.6MB everytime I download the file. Is this safe to flash. Odin passes the md5 check...
View attachment 3223697
Click to expand...
Click to collapse
If you check the size of the file you downloaded in windows file manager it should be 58 041 KB (thats what mine is)
I put the 58 041 KB big file in my ODIN just to check and mine ODIN says the binary size is 56,7, that is the same number your ODIN shows in the picture
I think you can flash safely, if the file is corrupted it simply should not pass the md5 check

iketil said:
If you check the size of the file you downloaded in windows file manager it should be 58 041 KB (thats what mine is)
I put the 58 041 KB big file in my ODIN just to check and mine ODIN says the binary size is 56,7, that is the same number your ODIN shows in the picture
I think you can flash safely, if the file is corrupted it simply should not pass the md5 check
Click to expand...
Click to collapse
I just flashed it and it worked. Thanks a million man. You saved me a ton of time, effort and data. :good:

Galaxy s6 bricked?

Hello guys,
so usually i get my stuff to work again if i was the one who broke it... But today is the day i have to admit i'm lost. never wrote a thread before but now it's the time.
So i was about to install the Carhd rom for my s6. After i forgot to do a factory reset before installing i got a really messed up system with my apps and stuff but the new rom. But it was really unstable. So i went back in recovery mode and did a wipe.. unfortunately i forgot that this will wipe the rom too. Soo then everything started. I know how to push files via adb or sideload. The problem is my Phone doenst get recognized in recovery mode. Not at all. On the other hand if i connect it in download mode then it's shown perfectly fine. With name and manufacturer and so on. Next i tried to flash a stock rom with odin.. But there i got some error Messages right at the start. Something about NAND :S.(will look it up later when i'm on my pc again)
I hope my phone isnt hardbricked :s.
Thanks for the help in advance.
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Thats the odin error.
and on the phone an error shows up: SW REV. CHECK FAIL. DEVICE: 3, BINARY: 2

Try Smart Switch emergency initialization as mentioned in this post:
http://forum.xda-developers.com/galaxy-s6/help/help-plz-s6-bootloops-t3303822
If you are stuck at logo afterwards, you may need custom kernel, e.g. unikernel (trips knox)

brenner650 said:
Try Smart Switch emergency initialization as mentioned in this post:
http://forum.xda-developers.com/galaxy-s6/help/help-plz-s6-bootloops-t3303822
If you are stuck at logo afterwards, you may need custom kernel, e.g. unikernel (trips knox)
Click to expand...
Click to collapse
Knox is triggered already anyways. I had an custom Rom installed before. Does Smart Switch recognize Phones in Download mode? otherwise, as stated, my Pc doesnt detect my Phone..
Cant try it now. But when i am getting home from work i will. Before, i will try to Flash another stock Rom, one that is more up to date then the one i used. because i think that maybe the rom caused the Odin error.

hsrye said:
Knox is triggered already anyways. I had an custom Rom installed before. Does Smart Switch recognize Phones in Download mode? otherwise, as stated, my Pc doesnt detect my Phone..
Cant try it now. But when i am getting home from work i will. Before, i will try to Flash another stock Rom, one that is more up to date then the one i used. because i think that maybe the rom caused the Odin error.
Click to expand...
Click to collapse
if you do the emergency recovery at smart switch it will ask you to go to download mode so no problem

Sboot fail is coused trying to flash an older firmware than phone already have... Do you see logs.. Wtf dude... Download newest firmware and flash

lummujaj said:
Sboot fail is coused trying to flash an older firmware than phone already have... Do you see logs.. Wtf dude... Download newest firmware and flash
Click to expand...
Click to collapse
ok, i'm home now. Need to download the rom and then we will see . But thats what i suspected already too, but download failed over night so couldnt try it this morning. Hopefully it will stay as easy as that .
Edit: Thank god it worked . The newest firmware flashed just fine after the second try

Samsung S8+ wont boot.

Hello, i have recenently tried to root my samsung s8 (did not know it was a stupid idea at that time) after i succeeded i wanted to start installing some roms
So i went and booted TWRP installed the roms, but my phone wouldn't boot anymore.
So i reinstalled the original OS through Odin, and my phone was back and working again , but being the stupid idiot I am, I tried to root it, again only this time without succes.
The phone is stuck on the device info (the samsung text with "Samsung Galaxy S8+" and "powered by android") and wont boot further or into android
When i try to once again reinstall the original OS with Odin it gives me the following error msg:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I can't boot into recovery mode on my phone either, just download mode nothing else.
i've treid booting recovery mode on my phone from my pc but when i use "adb devices" it won't detect the device (while in download mode) I'm not sure if it should detect it as I am in download mode, it does however detect the device in device manager, maybe USB debugging is disabled as i installed a fresh copy of android, I however only have a year of android experience so I really don't know if adb should even be possible from download mode.
Anyhow after 3 days of internet troubleshooting, I'm really running out of options.
Hope someone can point me in the right direction.

FluitGeluid said:
Hello, i have recenently tried to root my samsung s8 (did not know it was a stupid idea at that time) after i succeeded i wanted to start installing some roms
So i went and booted TWRP installed the roms, but my phone wouldn't boot anymore.
So i reinstalled the original OS through Odin, and my phone was back and working again , but being the stupid idiot I am, I tried to root it, again only this time without succes.
The phone is stuck on the device info (the samsung text with "Samsung Galaxy S8+" and "powered by android") and wont boot further or into android
When i try to once again reinstall the original OS with Odin it gives me the following error msg:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I can't boot into recovery mode on my phone either, just download mode nothing else.
i've treid booting recovery mode on my phone from my pc but when i use "adb devices" it won't detect the device (while in download mode) I'm not sure if it should detect it as I am in download mode, it does however detect the device in device manager, maybe USB debugging is disabled as i installed a fresh copy of android, I however only have a year of android experience so I really don't know if adb should even be possible from download mode.
Anyhow after 3 days of internet troubleshooting, I'm really running out of options.
Hope someone can point me in the right direction.
Click to expand...
Click to collapse
There is a S8+ forum, you'll likely get more assistance from there.

I'm getting the same problem one by one. please help

Critical Detox said:
There is a S8+ forum, you'll likely get more assistance from there.
Click to expand...
Click to collapse
when device reboots on its own after failed error press bixby vol down and power button. let it boot into download mode again now flash rom or whater ever. it would work on 2nd attempt.

rehanraza said:
when device reboots on its own after failed error press bixby vol down and power button. let it boot into download mode again now flash rom or whater ever. it would work on 2nd attempt.
Click to expand...
Click to collapse
I have tried that also, but keep getting the error above

same problem here. i had stock dbt tw rom. root with magisk. then i wanted to flash new BL and modem from new dbt fw update. after this i only got working DL mode left. couldnt flash back to another fw no matter which source i tried. btu too. i also got the same error as described above. after whole night of odin flashing trys, for myself i thought sth of internal memory chip is broken so i ordered a new phone. but now i see the second thread describing my problems maybe i was wrong with my thoughts

I fixed it!
With the help of Nameless i managed to fix my problem, here is his post regarding this issue: https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
I see other people are experiencing this issue as well, hope this helps!
here is the AQF7 bootloader I used: https://www.androidfilehost.com/?fid=889764386195911671,
For a full flash of the AQF7 version, I recommend you to use this website: http://updato.com/firmware-archive-select-model
Fill in the model of your S8 or S8+ select your country then look for the one that ends with XXU1AQF7 under the tab PDA
Best of luck!

FluitGeluid said:
With the help of Nameless i managed to fix my problem, here is his post regarding this issue: https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
I see other people are experiencing this issue as well, hope this helps!
here is the AQF7 bootloader I used: https://www.androidfilehost.com/?fid=889764386195911671,
For a full flash of the AQF7 version, I recommend you to use this website: http://updato.com/firmware-archive-select-model
Fill in the model of your S8 or S8+ select your country then look for the one that ends with XXU1AQF7 under the tab PDA
Best of luck!
Click to expand...
Click to collapse
Worked like a charm thanks FluitGeluid....
You save me :angel: