ENGLISH:
Hello dear members of XDA,
I wanted to flash the Lollipop update on my Galaxy Note 4 via Odin today.
I have the flash process is started then went on error, I suspect it's because I only still had almost 500 MB of memory on the device.
I do not know how I can re-flash the firmware, have someone a PIT file with no warranty problems or other Idears?
Regards,
Daniel
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1BOB4_N910FOXA1BOB4_N910FXXU1BOB4_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> 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> __XmitData_Write
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!
Click to expand...
Click to collapse
GERMAN:
Hallo liebe Mitglieder von XDA,
ich wollte heute das Lollipop Update auf mein Galaxy Note 4 via Odin flashen.
Ich habe den flashvorgang gestartet der dann auf Fehler gelaufen ist, ich vermute es liegt daran das ich nurnoch knapp 500 MB Speicher auf dem Gerät hatte.
Ich weiß nicht wie ich die Firmware nun neu flashen kann, hat jemand ein PIT File bei dem die Garantie bestehen bleibt?
Grüße,
Daniel
Can you start download mode again? Or recovery?
Machiel187 said:
Can you start download mode again? Or recovery?
Click to expand...
Click to collapse
Download Mode is Possible, on Recovery Mode i get the Info:
"firmware upgrade encountered an issue. please select recovery mode in kies & try again."
Then Just start download mode again and flash the rom again. Nothing to worry about. If that fails again. See if kies can help you.
Machiel187 said:
Then Just start download mode again and flash the rom again. Nothing to worry about. If that fails again. See if kies can help you.
Click to expand...
Click to collapse
Both done allready, and in Kies i can't find my phone in the emergency mode .. dont know why. Is it possible that the Rom flashing failing because my phone Storage is full?
danielmm1997 said:
Both done allready, and in Kies i can't find my phone in the emergency mode .. dont know why. Is it possible that the Rom flashing failing because my phone Storage is full?
Click to expand...
Click to collapse
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1BOB4_N910FOXA1BOB4_N910FXXU1BOB4_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> 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> cache.img.ext4
<ID:0/008> hidden.img.ext4
<ID:0/008> modem.bin
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Added!!
Click to expand...
Click to collapse
i restart the process in Odin and the Phone is Booting now.
Good. Have fun with Lollipop
Related
i receive it form customer hanfg on samsung logo , he say he try by odian to upload some file !!!
so i flash it all time error , but just succed on 4.4.2 after flash phone hang on samsung logo
and i can't enter to wipe device or to install stuck rom with sd card ,when i try i get on menu this photo
(recovery is not seandroid enforcing)
hitibiti said:
i receive it form customer hanfg on samsung logo , he say he try by odian to upload some file !!!
so i flash it all time error , but just succed on 4.4.2 after flash phone hang on samsung logo
and i can't enter to wipe device or to install stuck rom with sd card ,when i try i get on menu this photo
(recovery is not seandroid enforcing)
Click to expand...
Click to collapse
Hi,
It seems like you have a soft brick follow this guide
http://forum.xda-developers.com/showthread.php?t=2265477
Make sure you use the right PIT and the right stock rom for your phone
MAX 404 said:
Hi,
It seems like you have a soft brick follow this guide
http://forum.xda-developers.com/showthread.php?t=2265477
Make sure you use the right PIT and the right stock rom for your phone
Click to expand...
Click to collapse
thx for answer
i try still same problem , but itès strange i canèt wite any forware om it he just accept
I337MVLUFNE1_I337MOYAFNE2_I337MVLUFNE1_HOME.tar (4.4.2)
even other 4.4.2 from other provider can't accept it
also try 4.3 !!!!
any other suggestion ?
You need to give us more details. Post the Odin log here.
hitibiti said:
thx for answer
i try still same problem , but itès strange i canèt wite any forware om it he just accept
I337MVLUFNE1_I337MOYAFNE2_I337MVLUFNE1_HOME.tar (4.4.2)
even other 4.4.2 from other provider can't accept it
also try 4.3 !!!!
any other suggestion ?
Click to expand...
Click to collapse
Lennyz1988 said:
You need to give us more details. Post the Odin log here.
Click to expand...
Click to collapse
Hi
As Lennyz1988 said more detail , post log.......
flashed ok still same problem with this version ; I337MVLUFNE1_I337MOYAFNE2_I337MVLUFNE1_HOME.tar
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUFNE1_I337MOYAFNE2_I337MVLUFNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> modem.bin
<ID:0/005> NON-HLOS.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
Click to expand...
Click to collapse
now i try this version with pit file
I337_16GB.pit
I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> NON-HLOS.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
now i try with
I337_16GB.pit
AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> persdata.img.ext4
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Click to expand...
Click to collapse
Hi guys, I'm new here
I'm having problems during the flash of any of these 3 roms:
I9505XXUGNF1_I9505ITVGNF1_I9505XXUGNF1_HOME.tar
I9505XXUGNG8_I9505ITVGNG1_I9505XXUGNG8_HOME.tar
I9505XXUGNJ8_I9505OXXGNK1_I9505XXUGNJ8_HOME.tar
Here is my odin report (I've tried all the odins 1.85, 3.04, 3.07, 3,09)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUGNJ8_I9505OXXGNK1_I9505XXUGNJ8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<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> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> sbl2.mbn
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!
NOTE: The phone was rooted with the I9505XXUGNF1 rom and then flashed a Phoenix ROM using CWM on a SD. I've flashed a modem because I was loosing the carrier often and reading on google that plp have fixed this issue this way, during the flash it stopped and now I'm stuck with odin not flashing any rom and the device stuck with the message that tells you that there was a problem, try with kies (kies is not even recognizing it). I'd like to have the device back with the stock ROM and that bug of the carries fixed if is possible.
Thx, Francesco.
CRY123 said:
Hi guys, I'm new here
I'm having problems during the flash of any of these 3 roms:
I9505XXUGNF1_I9505ITVGNF1_I9505XXUGNF1_HOME.tar
I9505XXUGNG8_I9505ITVGNG1_I9505XXUGNG8_HOME.tar
I9505XXUGNJ8_I9505OXXGNK1_I9505XXUGNJ8_HOME.tar
Here is my odin report (I've tried all the odins 1.85, 3.04, 3.07, 3,09)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUGNJ8_I9505OXXGNK1_I9505XXUGNJ8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<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> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> sbl2.mbn
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!
NOTE: The phone was rooted with the I9505XXUGNF1 rom and then flashed a Phoenix ROM using CWM on a SD. I've flashed a modem because I was loosing the carrier often and reading on google that plp have fixed this issue this way, during the flash it stopped and now I'm stuck with odin not flashing any rom and the device stuck with the message that tells you that there was a problem, try with kies (kies is not even recognizing it). I'd like to have the device back with the stock ROM and that bug of the carries fixed if is possible.
Thx, Francesco.
Click to expand...
Click to collapse
try reading this thread
http://forum.xda-developers.com/showthread.php?p=53275060#post53275060
Zaraee said:
try reading this thread
http://forum.xda-developers.com/showthread.php?p=53275060#post53275060
Click to expand...
Click to collapse
Hi, I've already tried to reinstall the USB drivers, used different usb port, used the laptop... Even tried to flash the right PIT file, which did flashed ok, then it failed onto the same file..
I've succefully flashed on the MODEM, and i've got the Galaxy S4 logo as normal but it was stuck there, so i've tried to flash the last ufficial ROM unj8 something and... failed onto the system image, stuck again...
Anyone?
CRY123 said:
Anyone?
Click to expand...
Click to collapse
the last thing i ever tried when my phone bricked is to use kies..i use that when my download failed and stuck on samsung logo
So i flashed lollipop via odin and i am not very pleased with lolipop because some apps dont support it yet. I tried to flash back to kitkat (with odin, like i did many times before) but i am getting this:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005DBTGNG1_N9005XXUGNG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<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> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> aboot.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> FAIL! (Size)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
wipe before installing, do it and then try again ? Definitely up-to-date installing the rom.
karargahx said:
wipe before installing, do it and then try again ? Definitely up-to-date installing the rom.
Click to expand...
Click to collapse
well now i have an even bigger problem. I flashed lollipop again with odin. It worked. Then i flashed the multix kitkat rom via cwm. When i try to set up my phone it says that my phone has been locked bacause of an abormal factory reset...?
i dont even have a samsung account.
Motawa88 said:
well now i have an even bigger problem. I flashed lollipop again with odin. It worked. Then i flashed the multix kitkat rom via cwm. When i try to set up my phone it says that my phone has been locked bacause of an abormal factory reset...?
i dont even have a samsung account.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2465863&page=3 check
karargahx said:
http://forum.xda-developers.com/showthread.php?t=2465863&page=3 check
Click to expand...
Click to collapse
it didnt work. I downloaded the speech (didnt asked me for account) then i tried to login on the start up screen and it says processing failed
I am trying to flash a stock rom on my Note 4 Exynos Version, with odin I have tried the latest version as well as some older ones. I have tried flashing both kit kat & lollipop but always get the same error. I have usb debugging ticked.
<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)
why is this happening?
Ta
Any help guys?
@home said:
Any help guys?
Click to expand...
Click to collapse
you are facing a locked bootloader as we all are (both exy and snap) the only solution to fix your bootloop is to install apps like phone info then find out what your phone PDA version is then find the exact PDA from Sammobile or if you you are Having an 910C flash latest COJ5 rom or if you are on 910H try installing COJ4 rom (just download and install the latest frimware from sammobile or ... and you will be just fine )
ArmanFGT said:
you are facing a locked bootloader as we all are (both exy and snap) the only solution to fix your bootloop is to install apps like phone info then find out what your phone PDA version is then find the exact PDA from Sammobile or if you you are Having an 910C flash latest COJ5 rom or if you are on 910H try installing COJ4 rom (just download and install the latest frimware from sammobile or ... and you will be just fine )
Click to expand...
Click to collapse
I followed your instructions and this is what I'm getting. Now what I need to do further? Previously I was using Sixperience ROM.
<ID:0/003> 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/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> modem.bin
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
sirius_gamer said:
I followed your instructions and this is what I'm getting. Now what I need to do further? Previously I was using Sixperience ROM.
<ID:0/003> 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/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> modem.bin
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
well , i dont really know what the XmitData_write is , as i havent seen it since my s4 (everything was fine) ..
i think wiping would solve the Prob...
or maybe USB cable or odin version (+drivers)
2. if nothing works around ... try using KIES emergency updating ... its always the sweety
odin3 v 3.12
i have same problem;
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
sdstc said:
odin3 v 3.12
i have same problem;
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
problem is using UN-OFFICIAL USB CABLE
use FACTORY CABLE FIXes problem
sdstc said:
problem is using UN-OFFICIAL USB CABLE
use FACTORY CABLE FIXes problem
Click to expand...
Click to collapse
@sdstc is right you can fix __XmitData_Write with changing the cable
i used an original sammy cable and it didnt work. than i used another sammy cable and then it just worked
my device was a Tab S btw no note 4 or s4
bu arada cok sagol sdstc kardes
TimurAlaskara_TR said:
@sdstc is right you can fix __XmitData_Write with changing the cable
i used an original sammy cable and it didnt work. than i used another sammy cable and then it just worked
my device was a Tab S btw no note 4 or s4
bu arada cok sagol sdstc kardes
Click to expand...
Click to collapse
i all the time face with that error and i forgot use original cable
(ne için teşekkür?)
sdstc said:
i all the time face with that error and i forgot use original cable
(ne için teşekkür?)
Click to expand...
Click to collapse
Sen olmasan telefon hala bozuktu cunku sjsjsj
help plz
sdstc said:
problem is using UN-OFFICIAL USB CABLE
use FACTORY CABLE FIXes problem
Click to expand...
Click to collapse
<OSM> Please wait..
<OSM> N910CXXS2DQG1_N910COXA2DPH1_N910CXXU1DPC1_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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> 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.1210)..
<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> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbnmz
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)can not
help me please my friend.what is it.why i can not install android 5 stock room
help me please
neu
<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> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
qwellen said:
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> 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.1210)..
<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> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbnmz
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)can not
help me please my friend.what is it.why i can not install android 5 stock room
help me please
neu
<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> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Which android you was running before flashing?
I don't know
qwellen said:
I don't know
Click to expand...
Click to collapse
You can flash android 5.1.1 .but you cannot flash android 5.0 it will fail because once you are on 5.1.1 or 6.0.1 you cannot downgrade to 5.0 or 4.4.4 samsung has locked down bootloader to prevent downgrading.
Trex888 said:
You can flash android 5.1.1 .but you cannot flash android 5.0 it will fail because once you are on 5.1.1 or 6.0.1 you cannot downgrade to 5.0 or 4.4.4 samsung has locked down bootloader to prevent downgrading.
Click to expand...
Click to collapse
i"ve tried Lollipop 5.0.1 , Android 5.1.1 ,Marshmallow 6.0.1 fail all of this roms are stock rom for smn910f.
before flashing i was running andrid 6.0.1 . can i install android 5.1.1
in recovery mode write n910g on note 4.
back of note 4 write ist sm n910f.
edit :i found problem- my note 4 is not n910f . its sm n910g thanks.