hi. i`m trying to fix my phone(samsung sm-g920f) using odin and i have some isues.
i put the phone into odin download mode, i put the firmware in odin and it is remain stuck here
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
i also tryed with smart switch and the software cannot recognize the phone.
i think the previous software was android 5.1.1 indonesian firmware.
the phone is stuck in logo screen.
the phone was working before, but after i wipe the cache and wipe everything ( factory reset) it doesn`t work.
what should i do next because it pissed me off.
Related
Hi, I just tried rooting my new Samsung Galaxy S3 through Odin, all was going well until the upgrading stopped after getting to:
<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> boot.img
it's like it just froze in the middle of upgrading.
I couldn't add a picture due to the number of my posts.
Would it be safe to remove the usb cable and plug try plugging it through the rear usb slot? On my device's screen it says "do not turn off target!!".
Thanks.
ehrenfest said:
Hi, I just tried rooting my new Samsung Galaxy S3 through Odin, all was going well until the upgrading stopped after getting to:
<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> boot.img
You mean you we`re flashing firmware
Click to expand...
Click to collapse
flashed a rom in a slot instead of stock... so now its all jacked up.. when i try wipe on odin or downgrade i get this (below)
Just tried the nc5 upgrade ap... now it auto boots to recovery and says E: Failed to mount... crap I have work in morning
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Frustratez said:
flashed a rom in a slot instead of stock... so now its all jacked up.. when i try wipe on odin or downgrade i get this (below)
Just tried the nc5 upgrade ap... now it auto boots to recovery and says E: Failed to mount... crap I have work in morning
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
UPDATE: Gf walks in says hey try to flash the upgrade then the downgrade... I do it ... s4 set up is now on my screen.. lmao wtf? weird fix but oh well
Hey Guys. I need a Pit File for flashing the G925FXXU1AOE3 DBT Stock Firmware on my Galaxy. I have a 1&1 Branding and the galaxy need a repartition to switch from XEG to DBT.
pit file
I also need this pit file.
Why can't somebody without branding upload his pit file?
Just delete the hidden ImG..from the firmware and you are done...
Alex-V said:
Just delete the hidden ImG..from the firmware and you are done...
Click to expand...
Click to collapse
I just tried that. I opened the firmware with powerarchiver and deleted the hidden.img file. Than I tried to flash with odin, but it still gets stuck in "NAND Write Start!!".
<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> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
chik0 said:
I just tried that. I opened the firmware with powerarchiver and deleted the hidden.img file. Than I tried to flash with odin, but it still gets stuck in "NAND Write Start!!".
<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> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
Click to expand...
Click to collapse
Maybe your ODIN is to old. Had the same with ODIN 3.9 and 3.10 but it works with 3.10.6 ...
Error with the topic
Should be Samsung Galaxy S6, my bad
I have read a lot of information on this forum about how to install a Stock Rom, I'm new on this and I installed a custom rom and everything was working fine until 2 days ago when I ran out of battery and the phone entered a bootloop, I tried to follow a tutorial and end up deleting the OS with the TWRP, bottomline right now I'm using Odin trying to install a Stock Rom but getting an error:
<ID:0/004> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
I read about flashing the BL before and I extracted the boot.img from the TAR and created a tar.md5 and when trying to use Odin with only the BL I got this:
<ID:0/004> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
I'm running out of ideas at the moment and would like to request your help
You need to make sure you're using the same version of the firmware or newer.
es0tericcha0s said:
You need to make sure you're using the same version of the firmware or newer.
Click to expand...
Click to collapse
I'm using the latest one avaiable in Sammobile
Just double checking, but you're using the one for the correct model? There's a g900"L" and g900"i"...
es0tericcha0s said:
Just double checking, but you're using the one for the correct model? There's a g900"L" and g900"i"...
Click to expand...
Click to collapse
I'm getting it from,
sammobile.com/firmwares/database/SM-G920I
If you have the serial number, you can try Samsung Smart Switch for PC in Emergency Mode. That might get around these issues you are having...
Hi
I have a GT-i9205 which I used to have rooted with megakat (I think) which I gave to a friend, I was given it back in a bootloop state & i would like to try and fix it if possible. Can someone help with the information below?
Boot = Set Warrenty Bit: Kernal & forced reboots
Recovery= Recovery booting Set Warrenty Bit: Recovery & forced reboots
Download Mode: I can enter it & flash but nothing takes effect, I flash CWM recovery or philz_touch_6.48.4-meliusltexx & the process shows pass in odin without errors but i cannot boot into recovery's/stock rom (I9205XXUDOA1)
When device is connected windows recognises it in download mode & is showing in device manager under USB controllers as Samsung mobile USB CDC composite device.
I also tried to flash PIT for i9205 aswell with I9205XXUDOA1 in PDA
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> aboot.mbn
<ID:0/004> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)