Is it possible to do a factory reset with Odin? I flashed this rom http://forum.xda-developers.com/showthread.php?t=2268880 on to my phone but it's on M919UVUEMK2. Currently, my phone is soft bricked and I can only go into download mode and I can't install the clockwork recovery mod. My phone will boot to the Galaxy S4 logo and turnoff.
re: odin flash
Trong357 said:
Is it possible to do a factory reset with Odin? I flashed this rom http://forum.xda-developers.com/showthread.php?t=2268880 on to my phone but it's on M919UVUEMK2. Currently, my phone is soft bricked and I can only go into download mode and I can't install the clockwork recovery mod. My phone will boot to the Galaxy S4 logo and turnoff.
Click to expand...
Click to collapse
About the only thing you can do is start all over again and put your phone into download
mode and flash the official stock samsung 4.2.2 MDL odin flash firmware.
After that you can root and odin flash twrp or cwm custom recovery.
Here is a link for the official samsung m919 4.2.2 stock mdl firmware:
http://k0nane.info/rom/M919UVUAMDL_M919TMBAMDL_TMB.zip
After downloading unzip and you will find the .TAR file which you
need to use with Odin in it's PDA slot.
Good luck!
How can I see my modem on my phone. I just want to be sure what the modem I have now.
Sent from my SGH-M919 using xda premium
xperia_88 said:
How can I see my modem on my phone. I just want to be sure what the modem I have now.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
In Settings/More/About device/Baseband
☞ Sent from here☜???
Thanks but it didn't work. Odin keeps say it failed.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<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> 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)
Trong357 said:
Thanks but it didn't work. Odin keeps say it failed.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<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> 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)
Click to expand...
Click to collapse
You're using a stock FW to go from 4.3 to 4.2.2 which is not possible. You have to use a 4.3 stock FW to go back to stock. Once you're on the 4.3 boot loader, you're stuck with 4.3. You can NOT downgrade to a different bootloader.
---------- Post added at 01:09 AM ---------- Previous post was at 01:05 AM ----------
Download the 4.3 FW from here, should be the first link.
Thanks but:"Hotfile has been shudown. A download link to Terafile will be presented as soon as the firmware is uploaded. We are busy uploading all files to the new host. We apologize for the inconvenience."
re: official stock m919 firmware
Trong357 said:
Thanks but:"Hotfile has been shudown. A download link to Terafile will be presented as soon as the firmware is uploaded. We are busy uploading all files to the new host. We apologize for the inconvenience."
Click to expand...
Click to collapse
Here is the identical firmware as found on SamMobile.com
This is the M919UVUEMK2_M919TMBEMK2_TMB.zip
This contains the TAR file for the official Samsung M919 MK2 4.3 stock firmware.
Here is the direct download link: https://copy.com/hzfaqBpWhinn/M919UVUEMK2_M919TMBEMK2_TMB.zip?download=1
This is a much faster mirror than the Hotfile host which SamMobile uses.
Good luck!
Thanks and thank you and to everyone else who helped. The rom installed successfully but when I tried to turn the phone on, it gets to the T-Mobile splash screen and doesn't go on from there. I left it there for nearly 30 min but it didn't load and the phone was very hot. I re-Odin the rom and tried wiping cache partition and dalvik in recovery but the phone never goes past the T-Mobile screen.
Misterjunky, sir. Thank you!. Your link helped me to unbrick. I've a working ROM now. My root is gone, wifi slightly flaky - but hey can make calls etc.!
I am on 4.3 + MK2 now. My warranty is void etc..but really thank u very much!.
Related
Well I was on the 4/10 nightly for CM 10.1, and I wanted to switch back to a stock TW ROM, so I downloaded and flashed PlainJane. Upon reboot my phone demanded that I reset my data because encryption had failed, and I never had my device encrypted, but the only thing I could do was press reset. So I did, and the phone booted into TWRP and flashed a quick message and rebooted to the same screen. I thought oh well no biggie I can restore my backup...NOPE. Looks like my SD card decided to corrupt. Well hey theres Odin right? WRONG AGAIN. I tried the method at
http://www.sxtpdevelopers.com/showthread.php?t=74 and Odin tells me
<ID:0/006> 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/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006> param.bin
<ID:0/006> recovery.img
<ID:0/006> sboot.bin
<ID:0/006>
<ID:0/006>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I cannot boot into recovery because it tells me a firmware update has failed. Please someone help...
When you use ljc it will always fail at sbin it's not going to install the old boot loader use the new tar from This thread
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from my SPH-L900 using Xparent BlueTapatalk 2
Epix4G said:
When you use ljc it will always fail at sbin it's not going to install the old boot loader use the new tar from This thread
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from my SPH-L900 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
THANK YOU SO MUCH! I got TWRP up and running and I'm flashing the stock reset now .
I'm on 4.4.4 AOKP and I accidentally formatted something in recovery and got stuck in bootloop. Downloaded stock TW for S3 but everytime ODIN keeps giving me an error.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Also, can't seem to be able to get CWM or TWRP back on but I can get the stock recovery. Tried Kies but that didn't work. Been looking for stuff for a couple hours and can't seem to find an answer. Any help is appreciated, thanks.
I'm in a similar situation but in my case I have cwm but can't switch recovery or even upgrade it, and flashing roms doesn't stick.
Sent from my SM-N900T using XDA Premium 4 mobile app
TheAccomplisher said:
I'm on 4.4.4 AOKP and I accidentally formatted something in recovery and got stuck in bootloop. Downloaded stock TW for S3 but everytime ODIN keeps giving me an error.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Also, can't seem to be able to get CWM or TWRP back on but I can get the stock recovery. Tried Kies but that didn't work. Been looking for stuff for a couple hours and can't seem to find an answer. Any help is appreciated, thanks.
Click to expand...
Click to collapse
Are you able to boot in recovery? (home + vol up + power) - You could just reflash from there.
Do you know what you formatted in recovery?
I can get to recovery and download mode but I'm on stock recovery and can't flash anything. I must have formatted /system or /data
TheAccomplisher said:
I can get to recovery and download mode but I'm on stock recovery and can't flash anything. I must have formatted /system or /data
Click to expand...
Click to collapse
Have you tried flashing a custom recovery through Odin?
Also, if you're on 4.4.4, chances are that your bootloaders are on 4.3+. You'll need the MJB (4.3) or NE4 (4.4.2) stock to flash through Odin.
Downgrading bootloaders will result in a brick, therefore it's a good thing it's not going through!
I flashed TWRP and got a pass but every time I get into recovery mode I just get a black screen.
Where can I get NE4?
Thanks
TheAccomplisher said:
I flashed TWRP and got a pass but every time I get into recovery mode I just get a black screen.
Where can I get NE4?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2789917
If already on the MJB bootloaders/modem: http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
Since I'm on 4.4.4 I already have the MJB right?
TheAccomplisher said:
Since I'm on 4.4.4 I already have the MJB right?
Click to expand...
Click to collapse
I think so but you only can be sure if you updated your bootloaders to 4.3 (or up to the new NE4 4.4.2).
All right thanks I'll have to try it in a couple hours
TheAccomplisher said:
Since I'm on 4.4.4 I already have the MJB right?
Click to expand...
Click to collapse
The error at aboot.mbn tells me you have the 4.3 bootloader on your phone. By trying to flash a stock Samsung ROM in Odin means Odin will try and downgrade the bootloader to an older version which cannot be done once you are on a stock 4.3 bootloader. Don't keep using Odin to flash a stock Samsung ROM as it may brick your phone.
TheAccomplisher said:
I'm on 4.4.4 AOKP and I accidentally formatted something in recovery and got stuck in bootloop. Downloaded stock TW for S3 but everytime ODIN keeps giving me an error.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Also, can't seem to be able to get CWM or TWRP back on but I can get the stock recovery. Tried Kies but that didn't work. Been looking for stuff for a couple hours and can't seem to find an answer. Any help is appreciated, thanks.
Click to expand...
Click to collapse
Any update on this?
Sent from my SM-N900T using XDA Premium 4 mobile app
Everything is working perfect now and I'm on 4.4.2
TheAccomplisher said:
Everything is working perfect now and I'm on 4.4.2
Click to expand...
Click to collapse
What did you do to fix your problem?
Sent from my SM-N900T using XDA Premium 4 mobile app
Hi, i have a GT-N5100 running 4.4.2 Kitkat
My problem is i can't boot to recovery and it says:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again later.
But i can boot in Download Mode.
My phone keeps blinking and it won't charge, so, I've tried to flash the stock rom via ODIN and it says:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5100XXDNG2_N5100OXEDNG1_N5100XXDNE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> tz.img
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
While flashing the ROM, i saw this code:
Code:
KNOX WARRANTY VOID 0
RP SWREV A1
And I've tried several times, but it always FAILS!
I've tried to go to Recovery mode through Kies,
>Firmware Upgrade and Initialisation >Type the Model Name: and it did not detect the Phone.
Hoping that someone can help me with this. Thanks guys!
rongregoryred said:
Hi, i have a GT-N5100 running 4.4.2 Kitkat
My problem is i can't boot to recovery and it says:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again later.
But i can boot in Download Mode.
My phone keeps blinking and it won't charge, so, I've tried to flash the stock rom via ODIN and it says:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5100XXDNG2_N5100OXEDNG1_N5100XXDNE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> tz.img
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
While flashing the ROM, i saw this code:
Code:
KNOX WARRANTY VOID 0
RP SWREV A1
And I've tried several times, but it always FAILS!
I've tried to go to Recovery mode through Kies,
>Firmware Upgrade and Initialisation >Type the Model Name: and it did not detect the Phone.
Hoping that someone can help me with this. Thanks guys!
Click to expand...
Click to collapse
Use Odin v3.07 and flash in PDA mode. Also, make sure you have the right tar file for your Note and turn Kies off so it doesn't interfere with Odin.
CCallahan said:
Use Odin v3.07 and flash in PDA mode. Also, make sure you have the right tar file for your Note and turn Kies off so it doesn't interfere with Odin.
Click to expand...
Click to collapse
Thanks! I will try that! :good:
Edit: Fail. Did'nt work also. Hmm. I will try kies again.
rongregoryred said:
Thanks! I will try that! :good:
Edit: Fail. Did'nt work also. Hmm. I will try kies again.
Click to expand...
Click to collapse
If you are sure you have the correct file for your device and are using Odin correctly, might try using Heimdall to flash instead of Odin: http://glassechidna.com.au/heimdall/
I had a similar problem with my note 8.0. I can't remember exactly what I did but I managed to get it to reboot. It'll reboot to download but after it booted into download mode my Odin was able to find it.
---------- Post added at 09:19 PM ---------- Previous post was at 09:03 PM ----------
I think maybe holding down the power button should reboot it.
CCallahan said:
If you are sure you have the correct file for your device and are using Odin correctly, might try using Heimdall to flash instead of Odin: http://glassechidna.com.au/heimdall/
Click to expand...
Click to collapse
Tried heimdall, but no work. I think it's because of Knox. It won't flash Stock rom through Odin or heimdall.
BTW, i flashed a recovery through Odin and it works. Now im running a Custom Rom. Thanks for the help guys!
I'm currently in the same situation
What recovery did you flash?
I odin 4.4.4 poland.. it failed, it says Firmware upgrade encountered an issue. Please select recovery mode in Kies
I can't go to recovery, I tried to odin recovery but no luck
and in odin mode it says Secure Download : enabled
EDIT: I use philz_touch_6.48.4-n5100.tar.md5.. and it works
I haven't done any ROM updates for a couple of weeks, and I was sound asleep when the phone rebooted. It sat 'rebooting' for two hours before I woke up.
I'm able to reboot into Download Mode, but have been unable to install anything that has worked. I tried flashing both TWRP2.7.0.0 and the stock ROM, but neither have worked. TWRP is still showing as 2.6.3.1 on my phone, and I get a failure when loading the Stock rom that looks like this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLUFNH2_I747MOYBFNH2_I747MVLUFNH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I'm also able to boot into Recovery mode, but it appears that the phone is encrypted (it asks for a password, even though I've never encrypted it!) and when I try to factory reset or wipe dalvik or anything else, I get: E: Unable to mount '/cache'
Can you help? Phone is a rooted SGS-I7474M on Telus, and was running Slim 4.4.4 build 7.0 Official 5979. I'm using TWRP as my recovery.
Maybe try loading a stock from image using Odin? You can download the stock images from sammobile
Tony_YYZ said:
Maybe try loading a stock from image using Odin? You can download the stock images from sammobile
Click to expand...
Click to collapse
I think that's what I've been doing? I've downloaded this stock firmware: sammobile.com/firmwares/download/34793/I747MVLUFNH2_I747MOYBFNH2_TLS.zip/ and then tried loading it via ODIN?
Perhaps I'm missing something... Appreciate your thoughts!
hardidu said:
I think that's what I've been doing? I've downloaded this stock firmware: sammobile.com/firmwares/download/34793/I747MVLUFNH2_I747MOYBFNH2_TLS.zip/ and then tried loading it via ODIN?
Perhaps I'm missing something... Appreciate your thoughts!
Click to expand...
Click to collapse
Oh, my mistake. That's what I was suggesting. Sorry...I don't know what else to try.
What bootloader is on your phone?
You're trying to alter the bootloader which is causing the error after trying to flash aboot.mbn.
audit13 said:
What bootloader is on your phone?
You're trying to alter the bootloader which is causing the error after trying to flash aboot.mbn.
Click to expand...
Click to collapse
You've lost me... I have no idea. I don't think I've ever touched the bootloader unless that's packaged with Slimkat or TWRP,
How do I find out and what's my next step?
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
The aboot.mbn file is a bootloader that Odin is trying to load onto your phone. but the current bootloader is preventing this because the bootloader your are trying to load is not compatible with your phone or the current bootloader is newer than the bootloader Odin wants to flash.
Does your phone still boot into download mode? You're sure your phone is an i747m (Canadian version of s3)?
If your phone can boot into download mode, I recommend you flash the latest version of Philz Touch for the d2lte, copy a custom ROM to your external SD card, boot into Philz, and flash the custom ROM so you can at least get your phone booted. Once booted, install the Samsung Phone info app. This app will tell you the baseband and bootloader on your phone.
audit13 said:
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
The aboot.mbn file is a bootloader that Odin is trying to load onto your phone. but the current bootloader is preventing this because the bootloader your are trying to load is not compatible with your phone or the current bootloader is newer than the bootloader Odin wants to flash.
Does your phone still boot into download mode? You're sure your phone is an i747m (Canadian version of s3)?
If your phone can boot into download mode, I recommend you flash the latest version of Philz Touch for the d2lte, copy a custom ROM to your external SD card, boot into Philz, and flash the custom ROM so you can at least get your phone booted. Once booted, install the Samsung Phone info app. This app will tell you the baseband and bootloader on your phone.
Click to expand...
Click to collapse
I tried loading I747MVLDLK4_aio.tar.md5 and here's the log from the fail I ended up with:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLDLK4_aio.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Loading Philz also failed.
Are you flashing the latest Philz tar.md5 file? You can't flash the zip in Odin. You should be able to flash the Philz zip in TWRP.
audit13 said:
Are you flashing the latest Philz tar.md5 file? You can't flash the zip in Odin. You should be able to flash the Philz zip in TWRP.
Click to expand...
Click to collapse
I was using Skips Toolkit to try and load Philz... I'll try using TWRP
Flash Philz tar.md5 in Odin or the zip in TWRP. I prefer not to using any tool kits.
audit13 said:
Flash Philz tar.md5 in Odin or the zip in TWRP. I prefer not to using any tool kits.
Click to expand...
Click to collapse
The process all looks good, log:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-d2att.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> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
But still boots with TWRP... despite a PASS in Odin.
Alright i did a major mess up on my phone , Alright so i was rooted and was on CM13 well i decided to go back to stock rom so i downloaded the lastest Firmware and use odin to flash it and while it was flashing it failed . So i pulled the battery and restarted the phone and now i am hit with the ( Your device didn't update succesfully. Use the Verizon Software repair assistant to repair your deivce ) So i did that and it fails at 84% So i tryed reflashing again via odin and i keep getting failed well when i tryed flashing CF-Auto root to just see if it did anything it failed but when i booted the phone up it went stright to the samsung logo and boot looped so i was ok so i went into recovery and tryed to wipe /factory reset but keep getting a error .
So my thing is idk what to do i have tryed flashing via odin and it keeps failing i get this
Code:
<ID:0/007> 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/007> Odin engine v(ID:3.1203)..
<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> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> __XmitData_Write
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
<ID:0/007> Added!!
and that is the lastest firmware from sam mobile
if anyone can help me i really appericate it
pfcland said:
Alright i did a major mess up on my phone , Alright so i was rooted and was on CM13 well i decided to go back to stock rom so i downloaded the lastest Firmware and use odin to flash it and while it was flashing it failed . So i pulled the battery and restarted the phone and now i am hit with the ( Your device didn't update succesfully. Use the Verizon Software repair assistant to repair your deivce ) So i did that and it fails at 84% So i tryed reflashing again via odin and i keep getting failed well when i tryed flashing CF-Auto root to just see if it did anything it failed but when i booted the phone up it went stright to the samsung logo and boot looped so i was ok so i went into recovery and tryed to wipe /factory reset but keep getting a error .
So my thing is idk what to do i have tryed flashing via odin and it keeps failing i get this
Code:
<ID:0/007> 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/007> Odin engine v(ID:3.1203)..
<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> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> __XmitData_Write
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
<ID:0/007> Added!!
and that is the lastest firmware from sam mobile
if anyone can help me i really appericate it
Click to expand...
Click to collapse
I don't know if you tried already, but perhaps you could simultaneously flash a PIT file (hsbadr has a post over this) and a stock firmware image in ODIN. This should fix any borked partitions, if there are any. If this doesn't work, then I'm afraid I can't help you further. You'd have to wait on someone more knowledgeable than me. Or, you can take it into a verizon store or best-buy and ask for help there?
SirLaughsalot said:
I don't know if you tried already, but perhaps you could simultaneously flash a PIT file (hsbadr has a post over this) and a stock firmware image in ODIN. This should fix any borked partitions, if there are any. If this doesn't work, then I'm afraid I can't help you further. You'd have to wait on someone more knowledgeable than me. Or, you can take it into a verizon store or best-buy and ask for help there?
Click to expand...
Click to collapse
Were can i find this post at
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
Alright that actually worked it flashed and did not fail , Thanks alot your a life saver now my second question is When i boot the Phone Up and it shows the picture Samsung Galaxy Note 4 Andriod how do i get the Custom part on it to go off with the lock ?
pfcland said:
Alright that actually worked it flashed and did not fail , Thanks alot your a life saver now my second question is When i boot the Phone Up and it shows the picture Samsung Galaxy Note 4 Andriod how do i get the Custom part on it to go off with the lock ?
Click to expand...
Click to collapse
Is this on first boot go through set up and when your on the home screen power off the phone then power it on and if you were on cm 13 and flashed it with TWRP you tripped Knox so if powering off doesn't work then you can't get rid of it without rooting
Bren123 said:
Is this on first boot go through set up and when your on the home screen power off the phone then power it on and if you were on cm 13 and flashed it with TWRP you tripped Knox so if powering off doesn't work then you can't get rid of it without rooting
Click to expand...
Click to collapse
Yea it shows it on first boot shows a lock that is unlocked
pfcland said:
Yea it shows it on first boot shows a lock that is unlocked
Click to expand...
Click to collapse
OK complete setup when it gets off verizon screen then power it off and power it back on
Sent from my SM-N910V using Tapatalk
Bren123 said:
OK complete setup when it gets off verizon screen then power it off and power it back on
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Ok it is gone thanks alot man
Download this app called Samsung phone info from Google play and look at Knox warranty void if it shows up with 0x1 your warranty is voided I'm not sure if there is a way to reset it back to 0x0.
Bren123 said:
Download this app called Samsung phone info from Google play and look at Knox warranty void if it shows up with 0x1 your warranty is voided I'm not sure if there is a way to reset it back to 0x0.
Click to expand...
Click to collapse
it shows Ox1 but i am not worried about it because my phone is paid off
pfcland said:
it shows Ox1 but i am not worried about it because my phone is paid off
Click to expand...
Click to collapse
Oh OK cool.
Sent from my SM-N910V using Tapatalk
---------- Post added at 04:38 AM ---------- Previous post was at 04:37 AM ----------
pfcland said:
Ok it is gone thanks alot man
Click to expand...
Click to collapse
Your Welcome. [emoji3]
Sent from my SM-N910V using Tapatalk
pfcland said:
Alright that actually worked it flashed and did not fail , Thanks alot your a life saver now my second question is When i boot the Phone Up and it shows the picture Samsung Galaxy Note 4 Andriod how do i get the Custom part on it to go off with the lock ?
Click to expand...
Click to collapse
I'm at the exact point as he was but I haven't been able to try verizon software update assistant yet. However, I'm not able to install the PIT and TAR he used. Here's what I get. Any ideas? Under options I have the first three checked (auto reboot, re partition, f reset time).
<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> 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> 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> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<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)
<ID:0/003> Removed!!
<ID:0/003> Added!!
EDIT 1: Unchecked auto reboot and switched COM PORTS and it worked! THANK YOU!!!
droiddude414 said:
I'm at the exact point as he was but I haven't been able to try verizon software update assistant yet. However, I'm not able to install the PIT and TAR he used. Here's what I get. Any ideas? Under options I have the first three checked (auto reboot, re partition, f reset time).
<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> 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> 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> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<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)
<ID:0/003> Removed!!
<ID:0/003> Added!!
EDIT 1: Unchecked auto reboot and switched COM PORTS and it worked! THANK YOU!!!
Click to expand...
Click to collapse
Do this
Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
1. Extract odin into a desktop folder
2. Extract the tar from the zip and place it in the odin folder .
3. Place the PIT file inside the odin folder
4. Open odin folder
5. Run odin
6. In the left you should see some menues click on the one that says PIT
7. Now browse for thr PIT file and select it
8. Now Click on the AP button and select the TAR file in the odin folder .
9. Wait for it to load
10. Now make sure the re partition is not check marked .
11. Now click start and it should flash succesfully.
It will reboot and show the lock screen but one you reboot again it should be gone
Hope this helps
Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
Bren123 (or anyone who can help), I am having a same type of problem flashing in Odin. I would like to put my phone back to kitkat, back when it was smooth and fast. When I have tried to flash with Odin it failed everytime, however it was an older version of Odin v3.10.7. I have a stock kitkat rom from Sam mobile. Can I load it with the newer Odin and the Pit file you shared links for? Any help would be appreciated!
Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
lugnuttz said:
Bren123 (or anyone who can help), I am having a same type of problem flashing in Odin. I would like to put my phone back to kitkat, back when it was smooth and fast. When I have tried to flash with Odin it failed everytime, however it was an older version of Odin v3.10.7. I have a stock kitkat rom from Sam mobile. Can I load it with the newer Odin and the Pit file you shared links for? Any help would be appreciated!
Click to expand...
Click to collapse
I tried again with the never version of odin and it still does not work for me. This is what I get:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone please help me get my phone back to kitkat???
I can only flash marshmallow, or now lollipop v5.11, after following the instructions above. I still can't get the kitkat firmware to work.
Please help!
Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
thank you, this helped me out when my odin got stuck for 30+ minutes.
I use to have a Note 4 Verizon good cell, but I then change it to a T-Mobile N910T unlock easer to flash them no boot-loaders are blocked, but thats just my saying.
I went through the process ... i have root and i can only install a 5.1.1 rom for the life of me i am unable to flash any 6 or 7 roms ... ideas?
Get write failure
I know this has been a couple years but I am in the same boat . I went through the steps and I get a flash write failure?
It happens after about 40 seconds into
system.img.ext4
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> 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> FAIL! (Write)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)