Database Users

[GUIDE] How To Restore A Stuck Samsung Galaxy SI, SII and SIII

Restoring A Stuck Samsung Galaxy SI, SII and SIII​
Is your phone stuck like this?
{
"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"
}
Then read on! If not, this may only be useful for those who want to go back to the original Samsung Firmware.
Introduction
Too many people are getting stuck on the Samsung logo so I decided to make a tutorial on how to
get yourself off it. It is a simple tutoiral and noob friendly, but it will take time and patience because
the stock firmware is not just 300mb but can go into 1GB and more. This should on Samsung
Galaxy SI, SII, SIII. They are all tested and working, you may experiment on other phones if you
wish and you have no other choice. Read on for the downloads and instructions.
Downloads
Odin v3.07 - Click Here
Your Firmware - Find Here
Instructions
1. Go here and select your phone and its correct version's official firmware here: http://samsung-updates.com/latest-firmware/
2. Download Odin v3.07
3. Turn phone off completely and put it into download mode (Down Volume, Home Button and Power Button together).
4. After downloading the official firmware extract it and open Odin.
5. Select Auto Boot and F. Reset and put that .md5 file in the PDA section. NOTE: There should be COM: (PORT NUMB) in the first box.
6. Click Start and wait. If it succeeded then it will say PASS in green.
NOTE: This has worked for me and other people have confirmed it working for them after testing.
But if something more happens to your phone, I am not responsible.
Good luck.

Will be attaching more tutorials soon.
Sent from my GT-I9300 using xda premium

This is just a stock firmware flash via Odin as per multiple guides on the forum .
Its not getting off a stuck logo its re flashing full firmware in many cases a factory reset should be the first step or a reflash through recovery of the custom rom .
Multiple exact same guides in my view only confuse noobs .
jje

JJEgan said:
This is just a stock firmware flash via Odin as per multiple guides on the forum .
Its not getting off a stuck logo its re flashing full firmware in many cases a factory reset should be the first step or a reflash through recovery of the custom rom .
Multiple exact same guides in my view only confuse noobs .
jje
Click to expand...
Click to collapse
Got me off stuck on a logo.
Sent from my GT-I9300 using xda premium

AndroidPlant said:
Got me off stuck on a logo.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
A wipe data often fixes that too, if you have custom recovery,a dalvik/cache wipe could potentially fix it.
A re-flash of the Rom could fix it
.....indeed many things "could" fix it........I know your intentions are good, but could you refrain from posting links to this thread every time a problem comes up, because often the solution is much easier

There doesn't seem to be any i9300 firmwares on that site.

Hi, im doing everything as it says but gives me this
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-m0-m0xx-gti9300.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please help me

Try different USB cables and USB ports. Try flashing the latest stock ROM from sammobile.com.

help plz
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGOF1_I9300OXXGOF1_I9300XXUGNB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Cant pass this part.

audit13 said:
Try different USB cables and USB ports. Try flashing the latest stock ROM from sammobile.com.
Click to expand...
Click to collapse
Yes, i've already done that still nothing.
Could it be hardware related issue?

You confirmed the model # in download mode? It fails with the original Samsung usb cables too?

Blocked on Start (Firmware upgrade encountered an issue..)

Hi Guys .. Can you help me please? i have a problem with my Sprint Galaxy S4..
I tried to install a custom Rom and now is BLOCKED "Firmware upgrade encountered..." when i start Phone..
Now the only one solution is flashing with Odin right? But why Odin always FAIL ? I installed Drivers , i tried a lot of Firmwares .. From sammobile .. No one works ..
Also I tried this ROM http://forum.xda-developers.com/showthread.php?p=49213024#post49213024
LOOK some logs on ODIN when it FAILSSS
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Please help me .. How can i flash with ODIN ?

malefiCz said:
Hi Guys .. Can you help me please? i have a problem with my Sprint Galaxy S4..
I tried to install a custom Rom and now is BLOCKED "Firmware upgrade encountered..." when i start Phone..
Now the only one solution is flashing with Odin right? But why Odin always FAIL ? I installed Drivers , i tried a lot of Firmwares .. From sammobile .. No one works ..
Also I tried this ROM http://forum.xda-developers.com/showthread.php?p=49213024#post49213024
LOOK some logs on ODIN when it FAILSSS
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Please help me .. How can i flash with ODIN ?
Click to expand...
Click to collapse
What was your baseband before starting this process?

mattzeller said:
What was your baseband before starting this process?
Click to expand...
Click to collapse
Now i tried to FLASH latest version from sammobile
take a look at this SS
{
"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"
}
Please help me guys .. is 1 week now since i'm trying to fix this S4

malefiCz said:
Now i tried to FLASH latest version from sammobile
take a look at this SS
Please help me guys .. is 1 week now since i'm trying to fix this S4
Click to expand...
Click to collapse
Try a different cable or port on the computer

bilgerryan said:
Try a different cable or port on the computer
Click to expand...
Click to collapse
I tried 5 cables .. i tried all PORTS + Used another PC ...
What's the problem ... I Don't understand ..

malefiCz said:
I tried 5 cables .. i tried all PORTS + Used another PC ...
What's the problem ... I Don't understand ..
Click to expand...
Click to collapse
Did you give Odin Administrator permissions? Right click on it and hit Run As Administrator.

bilgerryan said:
Did you give Odin Administrator permissions? Right click on it and hit Run As Administrator.
Click to expand...
Click to collapse
OF COURSE bro ! .... Still nothing .. unbelievable !

Your screenshot of Odin says your PIT Partition is missing. Sorry, I missed that earlier because it didn't show up in Tapatalk. I thought I saw somebody post the PIT file recently, try searching for it.

SN-j500FN not booting into twrp recovery

Hello
I want to jump on the Cyanogenmod train and i installed a custom recovery. However when i try to boot my device into recovery i get this weird screen that keeps getting darker. Pictures below.
{
"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"
}
Does anyone know how to fix this and what is causing this problem?

bcoudi said:
Hello
I want to jump on the Cyanogenmod train and i installed a custom recovery. However when i try to boot my device into recovery i get this weird screen that keeps getting darker. Pictures below.
Does anyone know how to fix this and what is causing this problem?
Click to expand...
Click to collapse
U will have the wrong twrp buddy

bcoudi said:
Hello
I want to jump on the Cyanogenmod train and i installed a custom recovery. However when i try to boot my device into recovery i get this weird screen that keeps getting darker. Pictures below.
Does anyone know how to fix this and what is causing this problem?
Click to expand...
Click to collapse
Cm12.1 built from source(based on 5.1.1) or cm13 ported (based on 6.0.1) ?
If cm12.1 built from source:
1) Are you on 5.1.1 Lollipop?
2) Did you flash correct TWRP recovery? http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844
If cm13 ported:
1) Are you on 6.0.1 Marshmallow?
2) Did you flash correct TWRP recovery? http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960

The recovery is fixed, i can acces it now. Wich cyanogenmod versions are you guys using?

bcoudi said:
The recovery is fixed, i can acces it now. Wich cyanogenmod versions are you guys using?
Click to expand...
Click to collapse
Cm12.1 is working flawless.
Cm12.1 thread: http://forum.xda-developers.com/gal...m-cyanogenmod-12-1-samsung-galaxy-j5-t3468830 . Some people experienced random reboots with latest release, so if you experience too, then do this:
1) Download this zip: http://forum.xda-developers.com/showpost.php?p=69375277&postcount=334 . Ignore that is for J500H, it worked for my J500FN.
2) Open the zip and remove build.prop from system folder.
3) Now flash the zip in TWRP recovery and reboot.
4) Open build.prop from /system/ with some editor and add following lines at the end of it:
Code:
# GPS
persist.gps.qc_nlp_in_use=1
persist.loc.nlp_name=com.qualcomm.location
ro.qc.sdk.izat.premium_enabled=0
ro.qc.sdk.izat.service_mask=0x0
ro.gps.agps_provider=1
ro.pip.gated=0
5) Reboot and you are done.
CREDITS: @akasharif for this fix.
If you wonder why there isn't a new release with fix included, it's because Nick and Ganesh are working on cm13.
Personally I did this right after I flashed latest cm release and I didn't have any problem.

So i basically bricked my phone when messing with it. I tried to flash the stock rom trough odin but it doesn't work. I think its because i need to enable usb-debugging but i can't because i can't acces my phone. Anyone knows how i can fix this?
this is the message i get trough odin:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> J500FNXXS1APE5_J500FNVFG1APC4_J500FNXXS1APE4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> boot.img
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Ext4)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

bcoudi said:
So i basically bricked my phone when messing with it. I tried to flash the stock rom trough odin but it doesn't work. I think its because i need to enable usb-debugging but i can't because i can't acces my phone. Anyone knows how i can fix this?
this is the message i get trough odin:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> J500FNXXS1APE5_J500FNVFG1APC4_J500FNXXS1APE4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> boot.img
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Ext4)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You don't need to enable usb debug to flash stock rom as far as I know.
I got same problem when i tried to install first Marshmallow update, it was failing at hidden.omg.ext4.
Try this: https://www.youtube.com/watch?v=2uTHilnRsWw. Credits to @pacower for sharing that video. Also try to use newer Odin version (I used 3.09 or so all the time though).

Thanks! i've found the video and i can boot my android device again.

bcoudi said:
Thanks! i've found the video and i can boot my android device again.
Click to expand...
Click to collapse
Nice one

2 things, no need for 2 archiving programs. 7zip is more than capable of extracting tar archives, right click and select extract. No need to rename to md5.

Note 4 SM-N910F can't decrypt storage??

I wrote the title like this because else it would be much more. This is only one of many problems im currently having with my note 4. And im pretty sure its no duplicate because i only found single problems of all the problems i listed below but not all together...
I can't boot the phone (no rom installed) anymore.
I can't flash any ROM because i get many errors saying "Can't mount /system" or /data or /cache or anything really. It can't even mount my external sd card so i cant even install a ROM from my sd card with twrp. The rom i'm trying to install is the stock rom i used 6 months ago to flash but now its not working anymore so i downloaded some newer ones but with odin i only get errors saying i cant write to the phone and it fails everytime when writing the system img. Maybe because it cant mount anything?
I tried to change the filesystem with TWRP to something other than ext4 but that didnt work because it needs to mount many things.... Also it says /system is 0MB /data is 0MB and so on...
I can't wipe or format it because i get the error "Can't mount blabla" like 10 times+.
I flashed TWRP because I couln't falsh anything else.
I can only boot into bootloader/fastboot and recovery mode
I maybe found a solution but for that i need fastboot to work. I think it can't find or mount anything because it is encrypted but it can't decrypt the filesystem? This reddit post says: /r/Nexus6P/comments/3qnzz0/twrp_unable_to_mount_data/ -> "fastboot format userdata" should fix it.
I have all drivers installed and adb works and everything is fine but when i enter fastboot/download mode and connect it to my pc via usb then my pc reconigzes it as "SAMSUNGS Mobile USB Modem" ???? My other phone in fastboot mode is instantly recognized as such.... My note 4 is completly empty. it only has the twrp i think because i cant see anything. no files...
I think this is what i should fix but maybe im missing something and theres an easier solution to this? I really need help for this. i tried everything i found for 2 days straight. Im sitting infront of that stupid phone like 10hours today and still cant fix it.
I can connect it with adb and used commands there. Can this or anything be done with adb? Or only possible with fastboot? Really any help would be much appreciated! Hope you understand me
My Phone is a Samsung Galaxy Note 4 SM-N910F trltexx o2 germany. If that helps in any way...
Thanks if you read it to this point.

I'm still in need of help for this... please

bump...

EDIT:
 @.slowdown
What's the Odin's error?
Did you try to:
Download SamFirm_v0.3.6.zip
Extract it and run SamFirm.exe
In "Model" write "SM-N910F"
In "Region" write "VIA" for 02 Germany or "DBT" for Germany
Click download and you'll get latest samsung firmware for your phone.
Extract the downloaded .zip file and you'll get a .tar.md5 file.
Download Odin3_v3.10.7
Reboot your phone in download mode (power+home+volumedown) and press volumeup to continue
Run Odin3_v3.10.7.exe
Connect your phone to pc via usb cable
On Odin you should see "<ID:whatever> Added!!"
Click on "AP" and select the .tar.md5 file mentioned before.
Click start.
Once done the phone will reboot and you should be back on stock samsung firmware.

finally someone who answered me. thanks.
I tried what you said and this is what i got.
this is what i get in odin:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Write)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The FAIL!(Write) message is what i was talking about in my OP.

.slowdown said:
finally someone who answered me. thanks.
I tried what you said and this is what i got.
this is what i get in odin:
The FAIL!(Write) message is what i was talking about in my OP.
Click to expand...
Click to collapse
Try adding a pit file in odin. May this thread can help you.
You can find it here

_mone said:
Try adding a pit file in odin. May this thread can help you.
You can find it here
Click to expand...
Click to collapse
thanks for the reply.
I downloaded the pit file and did what the thread said. the odin message was this:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
so everything seems alright. then after the odin message "PASS!" it rebooted and did "installing system update" and then booted into recovery mode.
this is what my stock android recovery now shows me:
{
"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"
}
normaly i got this bunch of cant mounts on my twrp but it seems to be the same on the stock recovery.
well then i continued with the thread and navigated to the wipe data/factory reset. once i pressed ok the screen went black instantly and the only thing i could do is remove the battery after 10 mins or so doing nothing...
i really dont know what the problem for this can be
EDIT: oh yea i forgot to say that after removing the battery and inserting it again, when i hold the power button on the top left it says recovery booting for ~3 secs and then it turns black again and i need to remove the battery again. And when i go into the recovery mode it does the "installing system update" again with the animated android logo. then it turns black again... All this happend after my phone got an samstung system update and now it can't seem to update anything or i dont know

bump

hmm

.slowdown said:
hmm
Click to expand...
Click to collapse
anyone?

A final soution would be, including losing ALL your Data to connect the phone to your PC with Samsung Kies. Then resetting it via kies.

stysupreme said:
A final soution would be, including losing ALL your Data to connect the phone to your PC with Samsung Kies. Then resetting it via kies.
Click to expand...
Click to collapse
I already Tried that and Kies found that a phone is connected but it couldnt recognize it. Reinstalled drivers also. But tomorrow im trying it again because i cant remember if i tried everything with Kies. Maybe also on another Computer. Thanks for the tip and what exactly do i need to install for Kies to work? Samsung driver and Kies APP? Or did i miss something
EDIT: i tried it and it just cant detect my phone... maybe its because the phone can only boot into recovery with many errors on the phone as shown on the pictures.... i really dont know what to do. is there a way to manually detect the phone by hand?

Try using a different USB cable. The PC has to recognize the phone. Sometimes cables break. They charge but can't be used for data. Kies app and the latest drivera should be enough.

stysupreme said:
Try using a different USB cable. The PC has to recognize the phone. Sometimes cables break. They charge but can't be used for data. Kies app and the latest drivera should be enough.
Click to expand...
Click to collapse
didnt work either... my other phone can read the data just fine. i think i cant save the note 4 anymore....

.slowdown said:
didnt work either... my other phone can read the data just fine. i think i cant save the note 4 anymore....
Click to expand...
Click to collapse
Did you found any solution? I have the same problem...

Flashing problem

Hello guys, I bought an older Galaxy S5 (G900F) from my friend. But he had a MIUI 7 ROM installed, I needed stock so I looked for some tutorials and what I did, I downloaded latest stock FW - https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/PHN/download/G900FXXS1CQI6/191506/, put it in Odin (AP), flashed, everything went fine till the end, when this happened -
{
"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"
}
I thought it was a problem of unbranded FW and a PIT size, so I decided to try latest branded FW - https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/TNL/download/G900FXXS1CQI3/191276/, flashed through Odin, but in the end, again, the same error. Now the phone looks like this:
Is there a possibility to fix this? I am completely hopeless and really don´t know what to try. I can get into download mode, but not recovery mode. Any help or suggestion would be extremely highly appreciated. Thank you very much

Look, SM-G900F has several regional variants of firmware and some of them differ by hidden.img size significantly.
The problem is that:
1. You're trying to flash a firmware without pit-file and Odin cannot repartition the phone, but
2. This firmware does not match the current pit in your phone, hidden.img is bigger than the place for it in the phone's memory.
What to do (variants):
1. Get samfirm program (note: fw.updato.com or sammobile.com won't do) and download any FACTORY firmware for SM-G900F via this program. It contains necessary pit-file.
2. Go to this thread, download all SM-G900F pit-files from the second post and try to apply them one by one with that firmware you already have. At least one of them should work.
3. Open that firmware file bla-bla-bla.tar.md5 with 7-zip archiver and delete hidden.img from it. Save the firmware as bla-bla-bla.tar (remove .md5) and flash in Odin.
There're more variants but I think three will be enough for the moment.
The first variant is the most correct.

bbsc said:
Look, SM-G900F has several regional variants of firmware and some of them differ by hidden.img size significantly.
The problem is that:
1. You're trying to flash a firmware without pit-file and Odin cannot repartition the phone, but
2. This firmware does not match the current pit in your phone, hidden.img is bigger than the place for it in the phone's memory.
What to do (variants):
1. Get samfirm program (note: fw.updato.com or sammobile.com won't do) and download any FACTORY firmware for SM-G900F via this program. It contains necessary pit-file.
2. Go to this thread, download all SM-G900F pit-files from the second post and try to apply them one by one with that firmware you already have. At least one of them should work.
3. Open that firmware file bla-bla-bla.tar.md5 with 7-zip archiver and delete hidden.img from it. Save the firmware as bla-bla-bla.tar (remove .md5) and flash in Odin.
There're more variants but I think three will be enough for the moment.
The first variant is the most correct.
Click to expand...
Click to collapse
Oh man thank you, I thought it will remain dead, now I have some hope. But, I really don´t get HOW TO flash the pit. You mean flash the factory firmware (I have latest PHN), then I downloaded the first PIT from the post you mentioned, and now I don´t get how to flash it afterwards. I just read repartition must be ticked when flashing it

You don't need to flash pit separately.
Pit-file informs Odin how to repartition the phone's memory, it must be applied together with a firmware file.
Just look at Odin's interface carefully: there must be "repartition" option and a place where to insert a pit-file to.

bbsc said:
You don't need to flash pit separately.
Pit-file informs Odin how to repartition the phone's memory, it must be applied together with a firmware file.
Just look at Odin's interface carefully: there must be "repartition" option and a place where to insert a pit-file to.
Click to expand...
Click to collapse
This looks promising:
Found a Solution
First flash the firmware of choice let it fail.
Unplug the device and plug it back in with out rebooting it let it stay in the failed download mode.
Now uncheck the PDA/AP and add the PIT file attached here.
make sure repartion is checked and PDA/AP is not
Flash PIT and the phone will reboot and start up with your new firmware.
Note the PIT is for G900F 16GB EU
My log:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> FAIL! (Ext4)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But it would mean he flashed it succesfully separately, am I missing something?

If you want "PHN" then you'll need this pit-file (attached).

bbsc said:
If you want "PHN" then you'll need this pit-file (attached).
Click to expand...
Click to collapse
I did it! I used first pit file for F version, flashed separately according to the procedure I found and posted above. Worked like a charm. I am so glad. Thank you for help!!

matthew1811 said:
I did it! I used first pit file for F version, flashed separately according to the procedure I found and posted above. Worked like a charm. I am so glad. Thank you for help!!
Click to expand...
Click to collapse
i experienced the same problem. So i followed the procedure above.
The thing is in second step the AP tab didn't recognize the pit file.
Any words?