Hello.
My Galaxy S4 Gt-I9505 is getting stuck while flashing an Official Rom in Odin 3.09 during System.img.ext4.
<OSM> Leave CS..
<ID:0/007> Added!!
<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> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have done full data / cache wipe and I still get the same problem. Can anyone help ?!
Give us more details. I hope u arent trying to downgrade ur phone
Joku1981 said:
Give us more details. I hope u arent trying to downgrade ur phone
Click to expand...
Click to collapse
The phone is an international GT-I9505. It was previously running 4.2.2.
The software I have chosen to upgrade is the same software I have successfully used to upgrade my other GT-I9505.
I have used the PIT File in order to get access to the recovery mode.
I have tried two different frimware, both downloaded from samfirmware.com.
The phone gets stuck @ system.img.ext4.
I have done this many times before, but this has never happened.
Please tell me exactly what details you need so I can offer you the information in order to help me figure out this mess, it's driving me crazy ....
vBasceanu said:
The phone is an international GT-I9505. It was previously running 4.2.2.
The software I have chosen to upgrade is the same software I have successfully used to upgrade my other GT-I9505.
I have used the PIT File in order to get access to the recovery mode.
I have tried two different frimware, both downloaded from samfirmware.com.
The phone gets stuck @ system.img.ext4.
I have done this many times before, but this has never happened.
Please tell me exactly what details you need so I can offer you the information in order to help me figure out this mess, it's driving me crazy ....
Click to expand...
Click to collapse
Try a different cable/port.
Repulsa said:
Try a different cable/port.
Click to expand...
Click to collapse
If I don't use my laptop's USB 2.0 port, it won't even start the flashing.
To make this easier: I have read most of the basic stuff around the forum (ports, different firmware, wipes, flash pit).
vBasceanu said:
If I don't use my laptop's USB 2.0 port, it won't even start the flashing.
To make this easier: I have read most of the basic stuff around the forum (ports, different firmware, wipes, flash pit).
Click to expand...
Click to collapse
I have some old 4.2.2 as Factory firmware Full Wipe,
MDM Firmware, and some other
I give you them if you need, but you should try a different port
restart your laptop and try
timb3rwolf1973 said:
I have some old 4.2.2 as Factory firmware Full Wipe,
MDM Firmware, and some other
I give you them if you need, but you should try a different port
restart your laptop and try
Click to expand...
Click to collapse
I have got a new USB cable and an SD card so I can apply the update from Recovery Boot.
I would be grateful if you could provide me with the download link to your recover and the information on how to do it.
Regards
vBasceanu said:
I have got a new USB cable and an SD card so I can apply the update from Recovery Boot.
I would be grateful if you could provide me with the download link to your recover and the information on how to do it.
Regards
Click to expand...
Click to collapse
I sent you a private message with a link to my Google Drive - a folder with firmwares
timb3rwolf1973 said:
I sent you a private message with a link to my Google Drive - a folder with firmwares
Click to expand...
Click to collapse
Thanks but it's not needed. AS soon as I tried with a new USB cable, it worked perfectly.
Thanks for your cooperation
vBasceanu said:
Thanks but it's not needed. AS soon as I tried with a new USB cable, it worked perfectly.
Thanks for your cooperation
Click to expand...
Click to collapse
OK
Good Luck
Related
k well let's start by letting everyone know, I have searched EVERYWHERE! for a fix and i CANNOT find one. This is really fustrating me. I am a noob to these forums but i do have little knowledge when it comes to this kind of stuff.
I recently rooted my Samsung S4 GT-i9505 and i wanted to unroot it back to it's original state, In the process of unrooting i don't know what i have done wrong but i get stuck on a screen "Firmware upgrade encountered.. blah blah, NOW i have tried all means to try and fix this by using Odin WITH the original firmware from which i downloaded from the samsung drivers website. Everytime i try too flash it, It always FAILS. There is a type of firmware i can use "I9505XXUAMDE_I9505TELAMD8_I9505DVUAMD8_HOME.tar.m d5", But this particular one installs SU, Which i don't want, It also causes several features on my phone to stop working. Such a the clock and i can't even use my wifi.. I have tried several times, Over and over to try and fix it through Odin, But it will not budge, I can load the phone to download mode, But can't get past that. I am now stuck on the upgrade issue screen and i am literally stuck on things to do.. Any help will be appreciated as i am in desperate need to have my phone back too working order! I have tried Kies, Installing it uninstalling it, Disabling my firewall.. EVERYTHING.. I am trying to install the original firmware "I9505XXUBMG4_I9505XSABMG1_I9505DVUBMG1_HOME.tar.m d5" But Odin will not let me!!
Thankyou in advance to anyone that can help.
These are the details on my screen atm..
ODIN MODE
Product name: GT-i9505
Current Binary: Samsung official
System status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
Write protection: Enable
Here is the error i get from Odin:
<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> SingleDownload.
<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)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hi,
Have you tried a firmware upgrade and initialisation with Samsung Kies?
Insert your phone model (GT-I9505)
Pull out your battery and you see on the battery holding place a S/N code, fill that in.
Reboot in Download Mode and follow the steps.
It takes about 30 - 60min. for the reset.
Hope i helped you.
EDIT: YOU WILL LOSE EVERYTHING ON YOUR PHONE.
Dub2k13 said:
k well let's start by letting everyone know, I have searched EVERYWHERE! for a fix and i CANNOT find one. This is really fustrating me. I am a noob to these forums but i do have little knowledge when it comes to this kind of stuff.
I recently rooted my Samsung S4 GT-i9505 and i wanted to unroot it back to it's original state, In the process of unrooting i don't know what i have done wrong but i get stuck on a screen "Firmware upgrade encountered.. blah blah, NOW i have tried all means to try and fix this by using Odin WITH the original firmware from which i downloaded from the samsung drivers website. Everytime i try too flash it, It always FAILS. There is a type of firmware i can use "I9505XXUAMDE_I9505TELAMD8_I9505DVUAMD8_HOME.tar.m d5", But this particular one installs SU, Which i don't want, It also causes several features on my phone to stop working. Such a the clock and i can't even use my wifi.. I have tried several times, Over and over to try and fix it through Odin, But it will not budge, I can load the phone to download mode, But can't get past that. I am now stuck on the upgrade issue screen and i am literally stuck on things to do.. Any help will be appreciated as i am in desperate need to have my phone back too working order! I have tried Kies, Installing it uninstalling it, Disabling my firewall.. EVERYTHING.. I am trying to install the original firmware "I9505XXUBMG4_I9505XSABMG1_I9505DVUBMG1_HOME.tar.m d5" But Odin will not let me!!
Thankyou in advance to anyone that can help.
These are the details on my screen atm..
ODIN MODE
Product name: GT-i9505
Current Binary: Samsung official
System status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
Write protection: Enable
Here is the error i get from Odin:
<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> SingleDownload.
<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)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
BillvanHalen said:
Hi,
Have you tried a firmware upgrade and initialisation with Samsung Kies?
Insert your phone model (GT-I9505)
Pull out your battery and you see on the battery holding place a S/N code, fill that in
Reboot in Download Mode and follow the steps.
It takes about 30 - 60min. for the reset.
Hope i helped you.
Click to expand...
Click to collapse
Thankyou for your input, I appreciate every little bit of help, Yes i have tried that option, But it fails at around 70%, I even tried reinstalling Kies itself, And the drivers aswell. All with no success.
Dub2k13 said:
Thankyou for your input, I appreciate every little bit of help, Yes i have tried that option, But it fails at around 70%, I even tried reinstalling Kies itself, And the drivers aswell. All with no success.
Click to expand...
Click to collapse
When Samsung Kies fails, do you get a error message why it has stopped on 70%?
BillvanHalen said:
When Samsung Kies fails, do you get a error message why it has stopped on 70%?
Click to expand...
Click to collapse
The error comes up with something like "Firmware upgrade failure" Can't remember off the top of my head.
You have new boot loader so you can't flash those older firmwares. If you download the MJ5 firmware from Sammobile it will flash with Odin and you'll be good to go
Sent from my GT-I9505 using XDA Premium HD app
Obagleyfreer said:
You have new boot loader so you can't flash those older firmwares. If you download the MJ5 firmware from Sammobile it will flash with Odin and you'll be good to go
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Thankyou for your reply, I will give it a go and let you know how it went.
Dub2k13 said:
Thankyou for your reply, I will give it a go and let you know how it went.
Click to expand...
Click to collapse
Goodluck, let us know.
It worked! Thankyou so much for your help, I highly appreciate it. My phone is now back to stock, And everything functioning!
Hello everyone, i have a Note 4 Live Demo Unit with a corrupted Data partition :crying: Anyone knows where i can find the PIT File for the N910X ?
Greetings
mv-testarossa said:
Hello everyone, i have a Note 4 Live Demo Unit with a corrupted Data partition :crying: Anyone knows where i can find the PIT File for the N910X ?
Greetings
Click to expand...
Click to collapse
Does it work fine before? I mean can it register to the mobile network?
I doubt it doesn't as it is a demo unit.
mv-testarossa said:
Hello everyone, i have a Note 4 Live Demo Unit with a corrupted Data partition :crying: Anyone knows where i can find the PIT File for the N910X ?
Greetings
Click to expand...
Click to collapse
Demo units (N910X) are NOT sold to public...!
vndnguyen said:
Does it work fine before? I mean can it register to the mobile network?
I doubt it doesn't as it is a demo unit.
Click to expand...
Click to collapse
It worked fine until i flashed a pit file for the N910F, and since then, the phone stuck at the Samsung Logo, and i cant do a factory reset, it alsways says: E: Data cannot moount.
mv-testarossa said:
It worked fine until i flashed a pit file for the N910F, and since then, the phone stuck at the Samsung Logo, and i cant do a factory reset, it alsways says: E: Data cannot moount.
Click to expand...
Click to collapse
As this model is not widely available public, it is hard to ask for a PIT file.
You can try to flash the N910F firmware again with the N910F PIT file.
Would you mind showing me the info (screenshots) from your device using Phone INFO ★Samsung★ app? I'm very grateful.
I flashed N910F Firmware several times before, didnt help. I cant do a screenshot because the phone stuck at the samsung logo.
is there any other way to recover the data partition ?
mv-testarossa said:
I flashed N910F Firmware several times before, didnt help. I cant do a screenshot because the phone stuck at the samsung logo.
is there any other way to recover the data partition ?
Click to expand...
Click to collapse
Did you use a correct firmware file + correct PIT file for N910F?
And did you tick the Re-Partition option?
What was the error message in the Odin? Can you post the full Odin log here?
vndnguyen said:
Did you use a correct firmware file + correct PIT file for N910F?
And did you tick the Re-Partition option?
What was the error message in the Odin? Can you post the full Odin log here?
Click to expand...
Click to collapse
I dont get any errors on odin, and yes, i also tick re-partition.
I currently have 2 Firmware Files for N910F but only 1 Pit File
that i could found in the whole Internet. Which Pit File do i need ?
I hope anyone can help me bringing the device back to life
Can you post full Odin log while you were flashing the firmware?
Best solution:
Go to a Samsung Service Center: they can repair your phone!
And once again: 910X (demo units) are NOT sold to public!
Thats the full Odin Log.
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1ANIE_N910FVFG1ANI7_N910FXXU1ANIE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> sdi.mbn
<ID:0/008> NON-HLOS.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> modem.bin
<ID:0/008> cache.img.ext4
<ID:0/008> hidden.img.ext4
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
I've solved the problem by flashing the StockROM for N910F again through Odin. Thanks to all they helped me
mv-testarossa said:
I've solved the problem by flashing the StockROM again through Odin. Thanks to all they helped me
Click to expand...
Click to collapse
Do you have the Stock Rom for the N910X?
Yes but it is only a PhilZ Recovery Backup, i can upload it to my MEGA Account if you want it. Buildnumber is N910XXXU1ANJ2_LLK. Maybe there a some Files from me inside the ROM, please delete them immediately.
On my Demo Unit, i just flashed the Stock ROM for N910F (N910FXXU1ANJ4). Works great.
mv-testarossa said:
I've solved the problem by flashing the StockROM again through Odin. Thanks to all they helped me
Click to expand...
Click to collapse
I am also looking for StockROM too ...
shebi said:
I am also looking for StockROM too ...
Click to expand...
Click to collapse
I used the Rom for N910F. I have a PhilZ Recovery Backup of the N910X Rom, i can upload it if anybody need it.
mv-testarossa said:
I used the Rom for N910F. I have a PhilZ Recovery Backup of the N910X Rom, i can upload it if anybody need it.
Click to expand...
Click to collapse
Now that you flashed n910f ROM, do you able to use cellular connection? or it is still WiFi only?
No, it is still Wifi only, you cant use cellular because live Demos dont have a IMEI.
Flash SuperSu and Flashable Busybox (attached below)
then
use adb
adb shell
mke2fs / dev/block/mmcblk0p27
mount-w-t ext4 / dev/block/mmcblk0p27 / data
Click to expand...
Click to collapse
Device is already back to life, but thanks anyway for your response.
hi all
i bricked my phone recently...n910H
i wanted to return my note4 bootlogo by installing BL_PARAM_Joseph- from sixperience thread
and found it contain the wrong bootloader which may be for 910c
pls help iam very disappointed :crying::crying:
Just go on sammobil.com find the firmware for your phone, and follow the instructions with Odin which is provided on the download page
thejunkie said:
Just go on sammobil.com find the firmware for your phone, and follow the instructions with Odin which is provided on the download page
Click to expand...
Click to collapse
i installed via odin:
the massage in odin :
<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> modem.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> sboot.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
i think i had this once, and no matter what i tried, it didnt want to work, but then it was just something stupid, like install odin again, or drivers, or try another usb port.
thejunkie said:
i think i had this once, and no matter what i tried, it didnt want to work, but then it was just something stupid, like install odin again, or drivers, or try another usb port.
Click to expand...
Click to collapse
no nothing wrong here :crying:
i flashed via odin this day in the same manner and there was no problem:crying::crying:
samsung lo said:
no nothing wrong here :crying:
i flashed via odin this day in the same manner and there was no problem:crying::crying:
Click to expand...
Click to collapse
it say on screen Sw rev check fail device 2 binary 1
please help guys pleaase
it dont boot into recovery nor regognized by kies
samsung lo said:
please help guys pleaase
it dont boot into recovery nor regognized by kies
Click to expand...
Click to collapse
I had the same error and fixed it. It often happens due to bootloader and modem, Just download the correct stock firmware for your device, rename it from .md5 to .tar and extract it using 7-Zip, delete or move sboot.bin and modem.bin then make a new 7-Zip archive with .tar extension and install it regulary by Odin
shababik said:
I had the same error and fixed it. It often happens due to bootloader and modem, Just download the correct stock firmware for your device, rename it from .md5 to .tar and extract it using 7-Zip, delete or move sboot.bin and modem.bin then make a new 7-Zip archive with .tar extension and install it regulary by Odin
Click to expand...
Click to collapse
thanks my friend u save me
i will pray for u my friend
love u
samsung lo said:
thanks my friend u save me
i will pray for u my friend
love u
Click to expand...
Click to collapse
you wlcm bro :good:
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Darkboss10 said:
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Click to expand...
Click to collapse
Remove PIT file and try again.
From Edge of Galaxy Seven
Darkboss10 said:
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Click to expand...
Click to collapse
Not knowing WHAT you are flashing, makes it a little harder to determine what is going wrong.
Go HERE and flash this in Download Mode. This is the latest Stock 935A ROM, This will wipe Everything on the device, and it'll be like it came brand new
norbarb said:
Remove PIT file and try again.
From Edge of Galaxy Seven
Click to expand...
Click to collapse
which is the pit file, sorry for dumb question
Darkboss10 said:
which is the pit file, sorry for dumb question
Click to expand...
Click to collapse
If I remember correctly you need to uncheck PIT in odin and this should help. BTW. What are you trying to flash?
From Edge of Galaxy Seven
I have try the stock rom version 935a...pf2 . And any other stock rom i have found for the 935a seeing which will work .
Darkboss10 said:
I have try the stock rom version 935a...pf2 . And any other stock rom i have found for the 935a seeing which will work .
Click to expand...
Click to collapse
If you are currently on a ROM that has v4 boot loader's, part of your problem may be that you are trying to flash a rom with v2, v3 bootloaders
Sent from my SM-G935T using XDA-Developers Legacy app
so i do better go with the v4 bootloader and i will check if the pit file is uncheck, what should i put on the re-partition case of odin active or inactive?
by the way thanks for your help
kangi26 said:
If you are currently on a ROM that has v4 boot loader's, part of your problem may be that you are trying to flash a rom with v2, v3 bootloaders
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
hey i did exactly as you told me , and for first time i guess i have an advance, i still get an error but at least a new error , check it out maybe you know what it is
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<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> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
any idea what can be?
i try to flash the G935a...PI2 rom bot without the CSC which i guess is the pit file right?
When you try to get the device into Recovery, it will appear like it isn't doing it or looks like an "No Command" error and it can take a couple of min to actually get into Recovery.
I would boot into Recovery again, let it sit for a few min. My bet is that it will eventually get into Recovery. Once it does, do a Factory reset, and then reboot into Download Mode, open Odin connect the device to your PC and install all 4 of the items from the Stock ROM thread, don't mess with any of the settings in Odin, just populate the slots with the BL, AP, CP and CSC
kangi26 said:
When you try to get the device into Recovery, it will appear like it isn't doing it or looks like an "No Command" error and it can take a couple of min to actually get into Recovery.
I would boot into Recovery again, let it sit for a few min. My bet is that it will eventually get into Recovery. Once it does, do a Factory reset, and then reboot into Download Mode, open Odin connect the device to your PC and install all 4 of the items from the Stock ROM thread, don't mess with any of the settings in Odin, just populate the slots with the BL, AP, CP and CSC
Click to expand...
Click to collapse
This is what i get . But it doesnt enter recovery at the end. It just shut off ....
Darkboss10 said:
This is what i get . But it doesnt enter recovery at the end. It just shut off ....
Click to expand...
Click to collapse
Looks like the device is just rebooting
Sent from my SM-G935T using XDA-Developers Legacy app
kangi26 said:
Looks like the device is just rebooting
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
if you watch the top corner blue letters it says recovery booting....
Darkboss10 said:
if you watch the top corner blue letters it says recovery booting....
Click to expand...
Click to collapse
I'm at a loss man, I'm sorry. I haven't seen that before, I dont get the "Samsung" part when I enter Recovery
Darkboss10 said:
if you watch the top corner blue letters it says recovery booting....
Click to expand...
Click to collapse
Can you post screen from download mode?
From Edge of Galaxy Seven
norbarb said:
Can you post screen from download mode?
From Edge of Galaxy Seven
Click to expand...
Click to collapse
There you go . By the way i should mention the phone only turns on download mode when plugged.
Darkboss10 said:
There you go . By the way i should mention the phone only turns on download mode when plugged.
Click to expand...
Click to collapse
OK you got bootloader v2. Try to flash some older version of MM in download mode using odin
Like from here: http://forum.xda-developers.com/showthread.php?p=67601581
From Edge of Galaxy Seven
You need to start by using the latest Odin, 3.12.3 for installing the original ROM. If you try to unlock, you need to go get the PrinceComsy version. PrinceComsy won't work for in-bricking a device, and if you have any of the stock versions of the ROM, you need the 3.12.3 version.
norbarb said:
OK you got bootloader v2. Try to flash some older version of MM in download mode using odin
Like from here: http://forum.xda-developers.com/showthread.php?p=67601581
From Edge of Galaxy Seven
Click to expand...
Click to collapse
I try that . Now i got this error but only on the phone screen and odin is stuck at initialization .. any idea what could be
i download the venom stock rom and the odin file he suggest but that odin is v 3.11.2 , so that was the one that trows me the odin protocol error, i try the same rom but with the v 3.12.3 odin , and it start working but it says fail at the on the recovery image, do that has to do something with my problem that the phone can boot into recovery mode?
here are the logs
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<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> boot.img
<ID:0/005> recovery.img
<ID:0/005> FAIL! (Erase)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Evening fellas!
I hope i can get some help over because i am freaking out!
Let me start with what i wanted to achieve. I wanted to go and use Stuff on my phone which wasnt usable due to the SafetyNet API, because i got a custom firmware and root Access. I tried to flash Magisk but it doesnt worked, neither did my SuperSU proberly.
My idea was to unroot and then simply flash the stock firmware via Odin on my phone. 1st couple of tries it didnt work. However, it also didnt affect my phone at all. So i then went into my recovery (TWRP) and did factory reset. Just to clean things up. I tried again to flash and yeah, he actually did it! Just with the minor exception that the flasing failed like 3% before its completion and now i got basiclly a white brick. I ve tried numerous times to flash that firmware again, get some other firmware running - I also tried to flash the Stock Rom completly (which also was able to start the flashing just before it failed in the middle).
I dont find any help on the internet, or at least not help that helps me in my specific situation. I honestly dont know what to do else... I do appreciate any help!
Please help me xda-users, you re my last hope!
Did you try using the original USB cable? Tried different USB ports?
audit13 said:
Did you try using the original USB cable? Tried different USB ports?
Click to expand...
Click to collapse
Yes, i just did. I ve used several USB Ports of my Computer (Haven't tried another computer yet, but that will come too). I also used two different cables. One Original and one third-party cable from amazon, which worked just fine for normal file copying and moving, on the S4 before its brick and the Samsung Grand Prime as well (as i use that in the mean time).
As from yesterday at some random points i was still able to get to flash something for just a second or so, the only messages i get from odin today are these:
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
I dont find any helpful information on that error message either, which is the worst part of it all.
Is Odin assigning a COM port to the phone?
audit13 said:
Is Odin assigning a COM port to the phone?
Click to expand...
Click to collapse
Yes, everything is detected. Odin is detecting the Samsung Grand Prime just as well as the Galaxy S4. I've also tried different version of Odin. v3.12.3 and v3.13.1. They both give me the same output.
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Thread moved to Help & Troubleshooting.
audit13 said:
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Click to expand...
Click to collapse
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
vM44tze said:
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Okay, i don't know whats wrong now - but now i cant even flash back the stock firmware that worked before with odin v3.07. Odin now says:
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: Its not even being detected anymore.
There is no need to split the tar.md5 into 4 parts. In Odin 3.07, you can flash it as a single file in PDA.
You're flashing the latest stock ROM? Is it possible the USB port on the phone is damaged?