Develop Bugs

[Q] [Q/A] Please Help Unrooting

I installed
Frankensteins Ego 5.1 perfectly fine, now i'm trying to unroot my phone to complete stock rom.
using http://theunlockr.com/2012/03/28/how-to-unroot-the-sprint-galaxy-sii-epic-4g-touch-sph-d710/
During using the odin, it's getting stuck on
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_SPH-D710_CL852097_user.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> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> Sbl.bin
<ID:0/007> zImage
<ID:0/007> factoryfs.img
<ID:0/007> hidden.img
<ID:0/007> recovery.bin
<ID:0/007> modem.bin
<ID:0/007> RQT_CLOSE !!
Won't go any further from this, can someone please help me.

Are you wanting to go back to stock el29 and unroot or what?
Sent from my SPH-D710 using XDA

peanut1596 said:
Are you wanting to go back to stock el29 and unroot or what?
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Yeah trying to get back to stock rom, i just noticed i didn't have samsung kies installed on my pc could this be a reason its getting stuck?

disit said:
Yeah trying to get back to stock rom, i just noticed i didn't have samsung kies installed on my pc could this be a reason its getting stuck?
Click to expand...
Click to collapse
Maybe. If Odin recognizes your phone then you should be good. Gimme a sec and I'll find the magical link to solve your issue.
Sent from my SPH-D710 using XDA

Ok. Just do as this thread says and you should be ok.
http://forum.xda-developers.com/showthread.php?t=1678631
Sent from my SPH-D710 using XDA

peanut1596 said:
Ok. Just do as this thread says and you should be ok.
http://forum.xda-developers.com/showthread.php?t=1678631
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
The links are dead in that post

disit said:
The links are dead in that post
Click to expand...
Click to collapse
Ooohhh bummer. Ok hang on.
Sent from my SPH-D710 using XDA

peanut1596 said:
Ooohhh bummer. Ok hang on.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I think you can also use sfhub's one-click back to EL29 and use the autoroot tool to unroot.
http://forum.xda-developers.com/showthread.php?t=1433101

Lol esoteric beat me to it. But that was my next link.
Sent from my SPH-D710 using XDA

Esoteric68 said:
I think you can also use sfhub's one-click back to EL29 and use the autoroot tool to unroot.
http://forum.xda-developers.com/showthread.php?t=1433101
Click to expand...
Click to collapse
Does that mean just download this http://forum.xda-developers.com/showthread.php?t=1342728
and run the uninstall root?

disit said:
Does that mean just download this http://forum.xda-developers.com/showthread.php?t=1342728
and run the uninstall root?
Click to expand...
Click to collapse
Use the one-click method to get you back to EL29, since you're coming from an ICS ROM back to GB you should use the full rather than the no-data. One you've done that, then download and extract the autoroot tool and follow the prompts to get you to the unrooting. Make sure you have USB debugging turned on before using autoroot.

Esoteric68 said:
Use the one-click method to get you back to EL29, since you're coming from an ICS ROM back to GB you should use the full rather than the no-data. One you've done that, then download and extract the autoroot tool and follow the prompts to get you to the unrooting. Make sure you have USB debugging turned on before using autoroot.
Click to expand...
Click to collapse
I've already tried using odin and the first method i tried is failing, so i can no longer turn the phone on, i can only get in download mode :\

disit said:
I've already tried using odin and the first method i tried is failing, so i can no longer turn the phone on, i can only get in download mode :\
Click to expand...
Click to collapse
When you plug the phone in while in Odin mode, are you getting the yellow highlighted box with COMxx in it to indicate the computer is recognizing your phone?
Another possible path is to pop out your sdcard, put it into the computer and load up some files that can be flashed via recovery (if you have recovery installed) then reinsert the card, hold power and volume up button to boot into recovery and flash a new build that way.

I've been trying to use the one click option, my phone is recognized but it won't proceed to completetion, i guess it's bricked. Is there anything i can do?

So let me get this straight. You put your phone into Odin/download mode, start the one click, and it fails? Does Odin notice your phone while in Odin/download mode?
Sent from my SPH-D710 using XDA

disit said:
I've been trying to use the one click option, my phone is recognized but it won't proceed to completetion, i guess it's bricked. Is there anything i can do?
Click to expand...
Click to collapse
I know this is getting frustrating for you, but have you tried other one-click downloads? EL26 or even any of the ICS ones just to get the phone back on?
I'll see if I can re-route sfhub over here, maybe he knows of something we aren't thinking to try.

Esoteric68 said:
I know this is getting frustrating for you, but have you tried other one-click downloads? EL26 or even any of the ICS ones just to get the phone back on?
I'll see if I can re-route sfhub over here, maybe he knows of something we aren't thinking to try.
Click to expand...
Click to collapse
Idk it sounds like he either had a bad download or possibly didn't put it into Odin mode or something. Just a thought I suppose.
Sent from my SPH-D710 using XDA

Okay thank you, it's recognizing it says [Com3] when i load it up i can't use any mode besides download mode it gives me a software issue if i hold power up and power button

disit said:
Okay thank you, it's recognizing it says [Com3] when i load it up i can't use any mode besides download mode it gives me a software issue if i hold power up and power button
Click to expand...
Click to collapse
Okay if it is recognizing your phone then try downloading another one-click and using it, or even re-downloading the same one you already have.

So even if my device is bricked it will load this, as long as odin recognizes it?

Galaxy S2 Freezes on Start and Won't Flash Anything

I recently acquired an Epic 4G Touch that wouldn't boot into the stock ROM. I thought "Awesome! The ROM must be corrupted. I'll just Odin it back to stock and have a new SG2." Well, I tried Odining it back to stock. I tried the Gingerbread EL29 stock tar image and it hung on the Sbl.bin. I thought maybe my download was just corrupt but after trying 2 other GB odin images it still wouldn't flash. Then I tried flashing CWM recovery through odin and that hung at NAND Write Start. I've switched cables, USB slots and computers. I'm at a loss as to why this is happening. I would really like to get this phone running so I can upgrade my SGS1.
Edit- Just to clarify, I never tried to flash anything through CWM. I tried flashing a kernel that had CWM through Odin.

I put the ROM into the PDA slot. Here's what happened in Odin:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_SPH-D710_CL839620_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> NAND Write Start!!
<ID:0/011> Sbl.bin
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Also tried flashing a PIT file,
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Set PIT file..
<ID:0/011> DO NOT TURN OFF TARGET!!
<ID:0/011> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I wish I would get some sort of response...

Since you can still get into download mode, try this thread.
http://forum.xda-developers.com/showthread.php?p=30996944
:edit: And I failed to mention that this seems to be the 4th thread in the past few weeks and the previous posters didn't fair well.
I hope the best for you.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2

MoHoGalore said:
Since you can still get into download mode, try this thread.
http://forum.xda-developers.com/showthread.php?p=30996944
:edit: And I failed to mention that this seems to be the 4th thread in the past few weeks and the previous posters didn't fair well.
I hope the best for you.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Thank you for the response. I cannot get into my recovery and my phone will not flash anything in Odin without some sort of error. I think it hosed. He mentioned sending it off for a jtag repair? What exactly is that?

xDecapitator said:
Thank you for the response. I cannot get into my recovery and my phone will not flash anything in Odin without some sort of error. I think it hosed. He mentioned sending it off for a jtag repair? What exactly is that?
Click to expand...
Click to collapse
This is very confusing... How are you trying to flash with CWM if you can't get into recovery mode?
What exactly is happening with the device when you try to power it on?
What happens when you try to go into download mode using Vol down+power?
What happens when you try to get to recovery using vol up+power?

graydiggy said:
This is very confusing... How are you trying to flash with CWM if you can't get into recovery mode?
What exactly is happening with the device when you try to power it on?
What happens when you try to go into download mode using Vol down+power?
What happens when you try to get to recovery using vol up+power?
Click to expand...
Click to collapse
Agreed.
Op - You're trying to write to the phone and, my guess is, you're making a bad situation worse since your getting partial writes. Especially that first screen where pit was mapped and partial flash took, such as boot.
Dont know where crawrj is, but try reaching out to Garwynn. He knows A LOT.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2

MoHoGalore said:
Agreed.
Op - You're trying to write to the phone and, my guess is, you're making a bad situation worse since your getting partial writes. Especially that first screen where pit was mapped and partial flash took, such as boot.
Dont know where crawrj is, but try reaching out to Garwynn. He knows A LOT.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
What? When did I say I was flashing through CWM? I've never even been able to boot to CWM. I said I was trying to flash CWM through download mode which failed. When I try to boot, it sticks at the Samsung Galaxy S2 kernel load screen. When I try to boot into recovery it sticks at the Samsung Galaxy S2 kernel load screen.

xDecapitator said:
What? When did I say I was flashing through CWM? I've never even been able to boot to CWM. I said I was trying to flash CWM through download mode which failed. When I try to boot, it sticks at the Samsung Galaxy S2 kernel load screen. When I try to boot into recovery it sticks at the Samsung Galaxy S2 kernel load screen.
Click to expand...
Click to collapse
Sorry. I misread the OP.
Ok. Try this to get into Recovery
Press and hold the vol up+power button until the splash screen shows up
After the splash shows release the power button and then continue to hold the vol up button. It should take you right to recovery.

graydiggy said:
Sorry. I misread the OP.
Ok. Try this to get into Recovery
Press and hold the vol up+power button until the splash screen shows up
After the splash shows release the power button and then continue to hold the vol up button. It should take you right to recovery.
Click to expand...
Click to collapse
I've done this atleast 20 times (21 now after this post) and it just sticks at the Samsung Galaxy S2 screen. I'm sure I screwed it even further by trying to flash CWM recovery. When I first got it, it booted into the recovery screen but wouldn't actually fully load into recovery. I would just get the Android character but no text. These are the weirdest issues I've ever had with an Android device.

xDecapitator said:
I've done this atleast 20 times (21 now after this post) and it just sticks at the Samsung Galaxy S2 screen. I'm sure I screwed it even further by trying to flash CWM recovery. When I first got it, it booted into the recovery screen but wouldn't actually fully load into recovery. I would just get the Android character but no text. These are the weirdest issues I've ever had with an Android device.
Click to expand...
Click to collapse
That is very strange...
Do you have an external SD card installed? If so, remove it and try to boot into recovery again.

graydiggy said:
That is very strange...
Do you have an external SD card installed? If so, remove it and try to boot into recovery again.
Click to expand...
Click to collapse
Still no luck :|

It fails every time it trys to flash files to the NAND memory. Does this mean the internal storage is screwed?

xDecapitator said:
It fails every time it trys to flash files to the NAND memory. Does this mean the internal storage is screwed?
Click to expand...
Click to collapse
That is possible. You can try to call Sprint and tell them you/a friend was trying to update to ICS and rebooted and it wont boot fully. Act dumb and see if they will replace it. Since it won't boot to anything at all, there is really no way for them to tell. Just say that you bought it from said friend. It is worth a shot. I have done it before with AT&T when I screwed up a Captivate doing a hardware mod.
I just told them that I bought it online and tried to update it but after the update, it wouldn't power on. They let me replace it.
---------- Post added at 09:54 PM ---------- Previous post was at 09:52 PM ----------
Either that or try J-Tag. But I don't know if that will fix it.

That and it's 50 bucks and a time to wait..
Sent from my SPH-D710 using Xparent ICS Tapatalk 2

graydiggy said:
That is possible. You can try to call Sprint and tell them you/a friend was trying to update to ICS and rebooted and it wont boot fully. Act dumb and see if they will replace it. Since it won't boot to anything at all, there is really no way for them to tell. Just say that you bought it from said friend. It is worth a shot. I have done it before with AT&T when I screwed up a Captivate doing a hardware mod.
I just told them that I bought it online and tried to update it but after the update, it wouldn't power on. They let me replace it.
---------- Post added at 09:54 PM ---------- Previous post was at 09:52 PM ----------
Either that or try J-Tag. But I don't know if that will fix it.
Click to expand...
Click to collapse
OK I will definetly try that, thanks. If they don't replace it, I will just sell it for parts and keep using my Epic 4G. Thanks for all of your help

Wait oh wait I have a few questions myself lol what odin are you using? Did you try any one clicks? Did you try removing the sd card and then odin? Did you try to leave battery out all night then try odin again with no sdcard?
Sent from my SPH-D710 using xda premium

I tried 2 different versions of Odin;1.x and 3.x. I used multiple one clicks. I pulled the sd card before flashing. I had to buy a battery for it when I got it and the previous owner had kept the battery out of it for at least a month. I really appreciate all answers but I really feel like I've tried everything :|
Sent from my SPH-D700 using Tapatalk 2

It is possible using a pit file would help. The pit file from when this phone came out would be best. Then run a gb rom in odin along with the pit. If you find the pit link it here before you use it. Wouldn't want more problems.
sent from MY BAD A$$ ET4G

patrao_n said:
It is possible using a pit file would help. The pit file from when this phone came out would be best. Then run a gb rom in odin along with the pit. If you find the pit link it here before you use it. Wouldn't want more problems.
sent from MY BAD A$$ ET4G
Click to expand...
Click to collapse
One Click restores are built with the proper pit of 9-16-11. But it sounds like he's already tried multiple builds.
Flashing each component isn't a bad suggestion but with using the pit, I wouldn't necessarily use just a rom, I'd use a tar since it would contain everything needed to restore the bootloader (boot, Sbl, param, recovery..)
Or try flashing an built bootloader to see if he could get back into recovery alone. There are a few already made in RWilco's Repo..

[Q] Phone is dead

rooted my S3 (4.1) and installed clockwork mod.
created a backup of my S3 using clockwork.
installed Jellybomb ROM.
recovered S3 backup using clockwork.
infinite boot....
I can still get into download mode and clockwork recovery but I'm unable to restore my S3.
Odin ( versions 1.83 - 3.09) fails all attempts to install roms, and clockwork is no longer able to read my ext sd card.
Now I have no way of installing anything to the phone.
Any advice?

westnine9 said:
rooted my S3 (4.1) and installed clockwork mod.
created a backup of my S3 using clockwork.
installed Jellybomb ROM.
recovered S3 backup using clockwork.
infinite boot....
I can still get into download mode and clockwork recovery but I'm unable to restore my S3.
Odin ( versions 1.83 - 3.09) fails all attempts to install roms, and clockwork is no longer able to read my ext sd card.
Now I have no way of installing anything to the phone.
Any advice?
Click to expand...
Click to collapse
have you tried using adb push?
look at these steps http://android-revolution-hd.blogspot.com/2013/12/how-to-copy-rom-zip.html
skip 9,10,11,12 because you don't need to create any folders and you are using 4.1.2
I hope that helps

jdelano said:
have you tried using adb push?
look at these steps...
skip 9,10,11,12 because you don't need to create any folders and you are using 4.1.2
I hope that helps
Click to expand...
Click to collapse
Thank you.
At least now I can push roms to the device.
It seems that no matter what rom I attempt to install I get these lines in clockwork:
-- Installing: /sdcard/rom.zp
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried 2 custom roms and Samsungs 4.1 stock Jellybean rom.
Same lines every time.
Am I missing something?

Jessooca said:
Is Odin failing in the middle of flashing a tar file or what is going on exactly.
Did your phone ever reboot or get stuck at the Samsung logo prior to this semi bricked issue?
Any details you can provide will help us better to help you.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Odin begins to write and then fails a few seconds afterwards.
After a failed write of any rom I get the boot error screen with the yellow triangle on the device.
Yes, It did get stuck at the Samsung screen prior to my clockwork mod no longer reading my ext sd card.

Jessooca said:
Try a usb port in the back of your computer and a different cable. I got one from my dollar tree and it's great.
Are you sure you aren't trying to flash an older tar file? Once you update to the newest update you have to flash the newest SPRINT SPH-L710 stock tar, I'm sure you know this already. Perhaps you've inadvertently downloaded the wrong tar!?
I have checked marked everything including wiping the efs in Odin 1.87 and it fixed a data issue someone had
This has to be fixable with Odin. I'd flash flash and try flashing again until Odin finishes without an error.
** also since you're on 4.1 why not try the latest tar file, not md5 and Odin that then root with CF Auto Root?
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 04:15 PM ---------- Previous post was at 03:52 PM ----------
One other thing...
Don't use twrp or cwm, use Philz recovery. Twrp works but on some roms it's flaky
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Thank you for the quick response.
I have tried different cables and usb ports (front and rear of PC case).
I'm also positive that I have the latest stock .tar from Samsung.
Also, I've tried checking "phone EFS clear" in Odin 1.87 as you've mentioned. (I've tried writing roms with all available versions of Odin as well. Versions 1.83 - 3.09 get me the same failed results)
lol, as far as flashing, flashing, and flashing until it works? I've tried. I've become quite desperate.
Here are the lines I get in Odin if it's of any help.
<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> aboot.mbn
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Jessooca said:
** also since you're on 4.1 why not try the latest tar file, not md5 and Odin that then root with CF Auto Root?
Click to expand...
Click to collapse
I'm not clear as to what you mean by this.
Would you please explain this to me?

westnine9 said:
Thank you.
At least now I can push roms to the device.
It seems that no matter what rom I attempt to install I get these lines in clockwork:
-- Installing: /sdcard/rom.zp
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried 2 custom roms and Samsungs 4.1 stock Jellybean rom.
Same lines every time.
Am I missing something?
Click to expand...
Click to collapse
Is there a status # given when it fails?

jdelano said:
Is there a status # given when it fails?
Click to expand...
Click to collapse
No status codes were displayed
Jessooca said:
Download Odin 1.87
Use a download manager to download the latest stock 4.3 TAR file
Put your phone into download mode.
Don't check repartition in Odin and don't use a pit file. Just the tar file in the pda slot.
Let me know where things go wrong this time
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 05:14 PM ---------- Previous post was at 04:59 PM ----------
... here's a link to the tar file
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Aha!
That little package did the trick!
My S3 is now up and running 4.1
Hmm, I still can't put my finger on what was causing the write fails with the standalone Odin and 4.1 rom.
..Maybe I didn't have the latest Samsung rom like I thought?
In any case that's irrelevant now.
Thank you very much Jessooca. :laugh:

I need help with .pit file, thanks!

Anyone out there that can help with the Note 2 SGH-T889 .pit file? Thanks in advance, I'd greatly appreciate it.
Edited: I need the file, a download link would be appreciate it.

http://forum.xda-developers.com/showthread.php?p=48398405
Sent from my SGH-T889 using xda app-developers app

Is this to be used only with heimdall or with a PC and Odin as well? Thanks!

Both heimdall and odin, why do you need this file for ?
Sent from my SGH-T889 using xda app-developers app

Well, I mistakenly flashed a file that was supposed to fix the wifi when in the leaked 4.3 roms a while back, but I flashed the 7100 one, and messed everything up. I was still able to get to them rom and all but eventually was just able to get to the custom recovery and thats it, now it just stays at the logo screen. I think I messed up the efs and some other things

I can still connect to a PC thru Odin and it recognizes the phone just fine, I can get to the custom recovery too and flash roms but it never passes the splash screen of that rom.

You can try emergency recovery through Kies or flash stock ROM and then flash flash whatever you want.
Sent from my SGH-T889 using xda app-developers app

I have flashed countless original Stock Roms, with every file they come with, and still hangs
I think it might have to do with the internal sd partion, Im hoping the .pit file fixes that? Not sure.

slick4mitch said:
I have flashed countless original Stock Roms, with every file they come with, and still hangs
I think it might have to do with the internal sd partion, Im hoping the .pit file fixes that? Not sure.
Click to expand...
Click to collapse
Have you tried a factory reset? Sometimes even after Odin I've had to factory reset. By the way since u flashed the wrong bootloader have you flashed the full stock from Sam mobile?
Sent from my GT-N7105 using xda app-developers app

kintwofan said:
Have you tried a factory reset? Sometimes even after Odin I've had to factory reset. By the way since u flashed the wrong bootloader have you flashed the full stock from Sam mobile?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Is not that I flashed a wrong bootloader, but yes, I have flashed our 4.3 bootloaders, even our 4.1 bootloader and it always hangs. I did a factory reset, I clean the internal sdcard, nothing, still hangs.

I know my EFS is messed up, it says it when I try to mount in the recovery, it even says it in the regular recovery, but it was loading the rom before with a messed up EFS.

I now have a Note 3 but I have taken upon myself to revive my Note 2

I can't get the .pit file to work usin Odin, it always fails, also I believe my system partition is not mounting at all, nor does the preload partition.

I second ciphercodes Kies recovery idea.
Hastily spouted for your befuddlement

Coug76 said:
I second ciphercodes Kies recovery idea.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
I tried it but it won't connect to Kies, but the phones does connects to the PC and its recognized by Odin.

slick4mitch said:
I tried it but it won't connect to Kies, but the phones does connects to the PC and its recognized by Odin.
Click to expand...
Click to collapse
And, just to be clear, that was following the emergency recovery process? There is the kies update, apart from the emergency recovery process. I hate to give up on a device...
Hastily spouted for your befuddlement

It just wont connect to Kies. Remember, I can't load up a rom, so Im trying to connect using download mode. It says connecting and stays like that, I think it might be dead

slick4mitch said:
It just wont connect to Kies. Remember, I can't load up a rom, so Im trying to connect using download mode. It says connecting and stays like that, I think it might be dead
Click to expand...
Click to collapse
Have you made any progress on this? I have a T-Mobile Note 2 also needs reviving.....I can only get it into download mode, can't get it into recovery mode......
I keep getting this error:
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please share what you know. thanks

Bricked my phone...

I accidently wiped /system
1.I've tried Odin, couldn't get it flash AT ALL. I don't know if its the zip or what. But i cant for the life of me get it to work.
2.I've tried sideloading, I'm not sure if that worked or not, after i did that, it wont go past the Samsung Galaxy note 4 screen, just keeps booting then stops and goes the battery charging screen(I'm assuming my OS is back on the phone? i also don't get the NO OS installed! error when booting up)
I'm completely out of ideas on what to do here.

yo try to get the zip from samsung or from a trusted source,that happend to me before (note 5)
Sent from my SM-N920T using Tapatalk

6eral said:
yo try to get the zip from samsung or from a trusted source,that happend to me before (note 5)
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Ive looked EVERYWHERE for a zip. I just took one off here.
Could you by chance link me to the correct zip?

what kind of phone and carrier?
Sent from my SM-N920T using Tapatalk

I thought i would also post the Odin logs
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
6eral said:
what kind of phone and carrier?
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Note 4 sprint

let me see what i can find
Sent from my SM-N920T using Tapatalk

6eral said:
let me see what i can find
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Cool thanks

try this and let me know,it's supposed to work on most Samsung devices
Sent from my SM-N920T using Tapatalk

6eral said:
try this and let me know,it's supposed to work on most Samsung devices
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I don't think you linked me to it..

yo cant send you the link because I'm a new user,well the thing is you have to do it via Kies 3 check on youtube how to unbrick note 4 via kies 3
Sent from my SM-N920T using Tapatalk

6eral said:
yo cant send you the link because I'm a new user,well the thing is you have to do it via Kies 3 check on youtube how to unbrick note 4 via kies 3
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I tried this but I cant get my S / N.

damn,let me see if i can find anything else
Sent from my SM-N920T using Tapatalk

I believe the Odin stock tar you're looking for is OK1 from this link:
http://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
Most likely, the case is, you can't go from reactivation locked bootloader to reactivation unlocked bootloader. It's in the upgrade notes. Also check your phone display in download mode. If you were on one of those updates, your phone should say reactivation lock is disabled or something like that. It means the bootloader will allow a compatible flash. Enabled reactivation status would block even a compatible flash to protect original user from theft if he knowingly or unwittingly chose to enable it. You have to be careful because that's been described as an efuse. It could cripple your main board if flashing with it enabled. Maybe it takes multiple attempts to blow it, IDK but respect it... Try to get in the habit of checking phone display before Odin flashing.
Hopefully, it is not booting simply because there's still no OS. You wiped it and failed to flash because wrong tar was selected. I can say that the OB7 tar you flashed has a non-reactivation locked bootloader. So you cannot go backwards in Odin to it, if that's the case.
If your looking to flash an older ROM in recovery from the reactivation bootloader, it's been reported to be possible if you flash a 5.1.1 kernel after the old ROM flash in recovery. Stability and compatibility may vary by user and ROM. The question was even asked in this forum-KitKat Bobcat ROM IIRC- if possible to flash KitKat ROM and then Lollipop Android Touchwiz kernel and confirmed by at least one user. Nonetheless, no reason to doubt that but I recommend latest custom ROMs for compatibility.
Sent from my SM-N910P using Tapatalk

Bump
Still looking for help.
Tried 0din, and the same error comes up as the post before.
Tried Kies but I need s/n and I don't have my box and no s/n on the back behind my battery.
currently downloading sammoblie rom. Hopefully this works.
the only other thing I can think of is putting a rom on my SD card and installing from TWRP

AnonDreams said:
Bump
Still looking for help.
Tried 0din, and the same error comes up as the post before.
Tried Kies but I need s/n and I don't have my box and no s/n on the back behind my battery.
currently downloading sammoblie rom. Hopefully this works.
the only other thing I can think of is putting a rom on my SD card and installing from TWRP
Click to expand...
Click to collapse
That may work too if you flash the right kernel with it. Well, that applies only if using an older ROM as I mentioned in my first reply... Did you read it yet?
BTW, KIES usually does that for rooted phones. It may only work if you set it up with same phone before root but unsure.
Sent from my SM-N910P using Tapatalk

samep said:
I believe the Odin stock tar you're looking for is OK1 from this link:
http://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
Most likely, the case is, you can't go from reactivation locked bootloader to reactivation unlocked bootloader. It's in the upgrade notes. Also check your phone display in download mode. If you were on one of those updates, your phone should say reactivation lock is disabled or something like that. It means the bootloader will allow a compatible flash. Enabled reactivation status would block even a compatible flash to protect original user from theft if he knowingly or unwittingly chose to enable it. You have to be careful because that's been described as an efuse. It could cripple your main board if flashing with it enabled. Maybe it takes multiple attempts to blow it, IDK but respect it... Try to get in the habit of checking phone display before Odin flashing.
Hopefully, it is not booting simply because there's still no OS. You wiped it and failed to flash because wrong tar was selected. I can say that the OB7 tar you flashed has a non-reactivation locked bootloader. So you cannot go backwards in Odin to it, if that's the case.
If your looking to flash an older ROM in recovery from the reactivation bootloader, it's been reported to be possible if you flash a 5.1.1 kernel after the old ROM flash in recovery. Stability and compatibility may vary by user and ROM. The question was even asked in this forum-KitKat Bobcat ROM IIRC- if possible to flash KitKat ROM and then Lollipop Android Touchwiz kernel and confirmed by at least one user. Nonetheless, no reason to doubt that but I recommend latest custom ROMs for compatibility.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I can type out all the "download" screen info if needed.
But RA lock is off.

AnonDreams said:
I can type out all the "download" screen info if needed.
But RA lock is off.
Click to expand...
Click to collapse
That's OK, don't need it. That confirms you have you a newer bootloader. That tar is blocked in Odin, for you. Best to move forward with Odin rather than backward.
Some stock tars later than OB7 have even been reported to be blocked but being on OK1, I only know I can go back OJ6 in Odin. Didn't try another because of that fact and OJ6 and OK1 are the best lollipop updates, IMO.
Sent from my SM-N910P using Tapatalk

samep said:
That's OK, don't need it. That confirms you have you a newer bootloader. That tar is blocked in Odin, for you. Best to move forward with Odin rather than backward.
Some stock tars later than OB7 have even been reported to be blocked but being on OK1, I only know I can go back OJ6 in Odin. Didn't try another because of that fact and OJ6 and OK1 are the best lollipop updates, IMO.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Dude.. it worked. SO MUCH THANKS.