I've always been stock since it's a work phone but...
I was using it like normal and it randomly rebooted (it does this occasionally).
Halfway through the startup sequence it complained about encrypting the file system and needing a reboot or something.
So I click the little "reboot" button (the only option) and now it shows some green text at the top about being unable to find the boot screen png.
After that it boots into recovery where it shows a bunch of red error text below failing to mount /system, /cache, /data, etc...
So I got ODIN and the stock full ROM TAR file. I was able to boot into recovery and it's flashing FACTORYFS right now.
It's been flashing it for nearly 30 minutes without the progress bar moving.
I did not use the PIT file since the instructions with ODIN said it was unnecessary and put the TAR in the PDA slot.
Is it normal to take this long? Is there something else I should try?
Heres the ODIN log so far:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.FF18_CL663858_ROM_PDA.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> factoryfs.img
<ID:0/006> NAND Write Start!!
Almost an hour and still no more bar movement.
Ok, I reset the phone... booted back into download mode and now I'm using the FF18 rooted one click.
I also changed USB cables for good measure.
<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> recovery.bin
<ID:0/006> hidden.img
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> cache.img
<ID:0/006> zImage
<ID:0/006> factoryfs.img
If flashes recovery, hidden, boot, Sbl, parak, cache, zImage... But still gets stuck on factoryfs.
:/
Although your first flash of the tar didn't need the pit file (see your log in post two, as is had the Pit for mapping), try flashing the individual stock tars in pc odin. (kernel, modem then rom)
If you want to have the pit, see the below thread.
Pit File Thread
What does the PIT do anyway?
Regardless... Now when I try to boot into download mode the blue light comes on, goes off momentarily, then comes back on and stays solid.
Black screen... No download mode...
:/
Damn man. Sorry to hear that.
And partition information table. What's/where..
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
It's ok... Hopefully they will repair it or something.
If not I'll just swap back to my Epic 4G (the old sliding keyboard... oh yeah!) until November
PIT is a file that partitions the filesystem on your device. Think of it like a script version of something like partition magic or partition manager along those lines only its preset to the volume sizes, locations and names instead of you controlling those
Sent from my SPH-L900 using Xparent ICS Tapatalk 2
orb360 said:
It's ok... Hopefully they will repair it or something.
If not I'll just swap back to my Epic 4G (the old sliding keyboard... oh yeah!) until November
Click to expand...
Click to collapse
They should.. or send in to Samsung if under warranty and Sprint doesn't for some reason.
Sent from my SPH-L900 using Tapatalk 2
Related
Hello, I recently acquired a note 2 n7100 and I have been trying to restore it. However, every time I try using odin, it gives me the that I the frimware upgrade encountered an issue error. I used the pit, but now it goes to the splash screen but nothing after that... Just a black screen. What should I do? I have been at this for hours and I am losing my mind!
Anyone have a solution? I am dying here!
EDIT: I got to the screen with the android on it and the little spinning ball in him, but then it just keeps booting to the android figure with the spinning globe. Any ideas?
You ll need to be more specific with your problem. Did you aquire the phone in working state? What were you trying to do. What did you do to achieve that? What was the results. What did you do to compansate that ? Etc....
Sent from my GT-N7100 using xda app-developers app
Try rebooting recovery (vol up+home+power)
wipe cache and data
if not works, input full details with complete odin log
and which ROM and pit file you have used
dr.ketan said:
Try rebooting recovery (vol up+home+power)
wipe cache and data
if not works, input full details with complete odin log
and which ROM and pit file you have used
Click to expand...
Click to collapse
Hello doc! I used the n7100 16gb pit you made and I am using the united arab stock rom, that is the only one that allows me to get to the android screen instead of a black screen. I tried the recovery button combo but that did not let me get into recovery.
I can update with my odin log when I get home. It all passes, nothing fails... So I guess I really dont know what is wrong with it.
Ok, try flashing stock recovery (get from here )
if you can flash it correctly then try rebooting in recovery and wipe cache and data.
otherwise post log of odin
dr.ketan said:
Ok, try flashing stock recovery (get from here )
if you can flash it correctly then try rebooting in recovery and wipe cache and data.
otherwise post log of odin
Click to expand...
Click to collapse
Thank you! Where do I find the log? Also if I can get this working I will definitely donate!
minnieman said:
Thank you! Where do I find the log? Also if I can get this working I will definitely donate!
Click to expand...
Click to collapse
The area which shows getting pit for mapping in odin application and all.
Sent from my GT-N7100
Ok, I tried flashing the recovery but that didn't work. I tried flashing the stock rom via odin again and it came up with the connect to kies error until I put the 16gn pit in and now it is back to the android figure with the spinning orb... Enclosed is the log, any other ideas? I am at a loss for words here.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMB5_N7100OJVDMB1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMB5_N7100OJVDMB1_N7100XXDLK7_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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
UPDATE: nevermind, it officially bricked so I am sending it in to be resurrected. Thanks for the help anyways doc!
Well it is flashing normally. Find a rom that will factory reset your phone.
Sent from my GT-N7100
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 updated my i317M (Telus) via OTA and the next day it rebooted and went into boot loop.
I've tried flashing the phone with 4 different stock roms (from 4.1.2 to 4.4.2) but they all fail.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLBMA3_I317MOYABMA3_I317MVLBMA3_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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried flashing Philz Touch recovery but that fails as well.
I've tried to boot it into recovery mode but it shows a dead Android with error logs like "E:failed to mount"
Help?
goyagoyago said:
I updated my i317M (Telus) via OTA and the next day it rebooted and went into boot loop.
I've tried flashing the phone with 4 different stock roms (from 4.1.2 to 4.4.2) but they all fail.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLBMA3_I317MOYABMA3_I317MVLBMA3_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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried flashing Philz Touch recovery but that fails as well.
I've tried to boot it into recovery mode but it shows a dead Android with error logs like "E:failed to mount"
Help?
Click to expand...
Click to collapse
Try flashing with odin again but before flashing open the tar and remove the bootloader out of it.
Hi, thanks for the reply cnote.
Would the bootloader be sboot.bin or boot.img or both?
thanks again
edit: or rather, how do you remove the bootloader and remake the tar file?
goyagoyago said:
Hi, thanks for the reply cnote.
Would the bootloader be sboot.bin or boot.img or both?
thanks again
edit: or rather, how do you remove the bootloader and remake the tar file?
Click to expand...
Click to collapse
I believe it;s both. Just retrieve the tar file only.
sboot is the bootloader boot.img is the kernel .Have you tried the latest NH2 for your phone also maybe try using a pit file
The nh2 you will have to get from sammobile and the pit file can be found here http://forum.xda-developers.com/showthread.php?t=2609871
Also after odin is finished go into factory recovery and do a factory reset or its just going to sit at the boot screen
flashing pit file also gives an error :S
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)
I've searched high, and I've search low for firmware for my phone (only to be led to sites whose download speed is atrocious).
My phone model is: SM-N910P
I've been searching for the .tar files for the firmware updates. The MD5 is either not valid by Odin's standard or something else.
Can someone point me along to a link of the latest Note 4 Stock Firmware update from a site that doesn't take all day to download from? Thanks Kindly.
P.s. Yes, I have gone through website and threads posting link to the correct firmware but all of them have not been MD5 correct or worked at all.
I'm also experiancing frequent crashes/restarts on the phone.
I got this phone from a family friend and its been acting weird in ways that are outside my comphrenension. It's rooted and they need it to factory state but all theses errors, problems, slow downloads, are making it near impossible.
Try downloading stock tar from this thread with your PC. You can and should verify the md5 before flashing in Odin when md5 is provided.
http://forum.xda-developers.com/showthread.php?p=63868221
Sent from my SM-N930P using Tapatalk
I flashed the file you linked to and this is what i got in Odin
<ID:0/009> 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/009> Odin engine v(ID:3.1101)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> sbl1.mbn
<ID:0/009> rpm.mbn
<ID:0/009> tz.mbn
<ID:0/009> sdi.mbn
<ID:0/009> NON-HLOS.bin
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> system.img.ext4
<ID:0/009> FAIL! (Write)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
gordonfrohman said:
I flashed the file you linked to and this is what i got in Odin
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1101)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
FAIL! (Write)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Questions:
Which stock tar did you flash? (see end of this post)
Does the phone frequently reboot or boot to download mode (reporting) failure to normal boot? Any eMMC failures reported?
Things to check or try if non applicable:
Factory reset in stock recovery if no OS is installed. If you can boot OS, make sure that Settings/Security/reactivation lock is disabled and enable developer mode and enable USB debugging.
Verify correct Samsung driver installed on PC or uninstall and reinstall from Samsung support for Note 4.
Use original Samsung Note 4 cable or replace. A good quality USB data cable should work but if replacing, use OEM replacement.
Run Odin in administrative mode. Try the suggested Odin version (3.10.7 or 3.10.6) or latest version from here: http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
(Odd reported issues sometimes result in one of these reported as successful where various others weren't).
Try another USB port, cable or PC
Edit: All KIES and Smart Switch sessions should be killed prior to starting Odin session.
Do not Odin older stock tars; usable stock tars start at OG5 and up.
Sent from my SM-N930P using Tapatalk