Develop Bugs

[GUIDE] Rooting the Samsung Captivate Glide i927/i927r

Finally, the Captivate Glide is successfully rooted.
Credit:
lambgx02 who provided the Carrier IQ free kernel (by Rogers) and the insecure kernel and the Rogers rooted ROM!!!
ardatdat who provided the rooted ROM and the overclocked kernel
samsfirware.com that provided the firmware without which nothing would have been possible
myself, crazy tester who bricked his device
Very easy steps:
If you are on Rogers, no need to flash the kernel, it is already CarrierIQ free​
Download Odin 1.85
Download the CarrierIQ FREE kernel (zip file) or the overClocked version of it.
Download the rooted ROM (AT&T based ROM)
or the Rogers rooted based rom (Unzip with WinRAR not 7zip)
Unzip the file and keep the .tar, that the file you are going to push to your device
Put your phone in Download Mode:
Turn off the phone
Press volume UP and keeping the button pressed, press the power button
a screen should ask you if you wanna continue - press volume up to confirm
Launch Odin
in PDA, select the first kernel downloaded (tar file you just unzipped)
DON'T SELECTor UNSELECT ANYTHING ELSE
Press the start button
Wait for your phone to reboot
This kernel will remove any traces of CarrierIQ, and you are now free from AT&T Spyware
IF AND ONLY IF this flashing fails, try the exact same steps with the insecure kernel
Reboot your device into download mode again (steps above)
Flash the rooted rom
Go to the market and make sure you have the latest version of superuser
go to superuser, check you have "su" updated
You're now rooted!
For any other questions, watch this first PLEASE:

There is already a thread for this... reporting for locking.
Sent from my SGH-I897 using xda premium

b-eock said:
There is already a thread for this... reporting for locking.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
The other thread was about trying to find root access, this is hopefully a thread on the procedure to have it in your phone

b-eock said:
There is already a thread for this... reporting for locking.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
I don't think it needs locked, they need their own subforum. We can put up with them here till they get it, they need a space to develop, too.
And congrats on getting root into the kernel rom!

Is this msg normal after I start? I also get a big red box at the top right which reads FAIL.
<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> SGH-I927RUXKJ5_STOCK_ROOTED.tar
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

clockwork58 said:
Is this msg normal after I start? I also get a big red box at the top right which reads FAIL.
<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> SGH-I927RUXKJ5_STOCK_ROOTED.tar
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Nope, you should get PASS in green color if successfully flashed. Try to open odin as administrator (right click, run as administrator) and make sure your device was detected properly by windows & Odin while it is in DL mode.

Sorry my guide was not complete, the kernel is not rooted, it is a CarrierIQ free kernel but the rom is rooted.
As soon as we have the kernel rooted, I will post it here.

I know that they need their space, I already told others to leave it alone, I was just trying to keep it from being cluttered. I am sorry guys good luck!!!
Sent from my SGH-I897 using xda premium

IlluminatedOne said:
Nope, you should get PASS in green color if successfully flashed. Try to open odin as administrator (right click, run as administrator) and make sure your device was detected properly by windows & Odin while it is in DL mode.
Click to expand...
Click to collapse
I still get the same error and now my phone won't even boot.
It says to use Kies to recover but even that won't recognize the device even though windows does pick up the drivers.
I can get to either the Kies screen asking to restore a bad image or the Custom rom screen and that's it.
HELP Pls.

Hey, wait a minute.. I provided the rooted rom..
But in all honesty, that's the easy part. Those nagging Samsung, the testers risking their devices, and of course, the OP who finally found the stock firmware images deserve the credit. Not to mention sammobile.com / samfirmware.com.

clockwork58 said:
I still get the same error and now my phone won't even boot.
It says to use Kies to recover but even that won't recognize the device even though windows does pick up the drivers.
I can get to either the Kies screen asking to restore a bad image or the Custom rom screen and that's it.
HELP Pls.
Click to expand...
Click to collapse
Do you have rogers or ATT ?

lambgx02 said:
Hey, wait a minute.. I provided the rooted rom..
But in all honesty, that's the easy part. Those nagging Samsung, the testers risking their devices, and of course, the OP who finally found the stock firmware images deserve the credit. Not to mention sammobile.com / samfirmware.com.
Click to expand...
Click to collapse
The rooted rom here is not yours but the one from ardatdat
But does not really matter, you both did a great job!!

I'm on Rogers. I'm using the lambgx02's Tar file.
I also just got my phone to recover following the other thread
http://forum.xda-developers.com/showthread.php?t=1357369
about going into 3e recovery mode and doing a reboot and it started fine.
I think the first time I tried, I didn't have kies installed with all the proper drivers.
Should I give it another go?
Update: Tried again, same Fail error. Maybe I'll try using my computer at work instead of my older home laptop.
Recovered again using 3e.

clockwork58 said:
I'm on Rogers. I'm using the lambgx02's Tar file.
I also just got my phone to recover following the other thread
http://forum.xda-developers.com/showthread.php?t=1357369
about going into 3e recovery mode and doing a reboot and it started fine.
I think the first time I tried, I didn't have kies installed with all the proper drivers.
Should I give it another go?
Update: Tried again, same Fail error. Maybe I'll try using my computer at work instead of my older home laptop.
Recovered again using 3e.
Click to expand...
Click to collapse
Let us know I tried twice to make sure everything was ok and it is.
if you are on Rogers you dont need to flash the kernel it is already CarrierIQ free!

CarpeNoctem said:
The rooted rom here is not yours but the one from ardatdat
But does not really matter, you both did a great job!!
Click to expand...
Click to collapse
Oh, I'm sorry ardatdat and Carpe! I didn't even notice!
Must have been a close race!

lambgx02 said:
Oh, I'm sorry ardatdat and Carpe! I didn't even notice!
Must have been a close race!
Click to expand...
Click to collapse
I promise you no race. Just happy to be rooted and have my device back to life thanks to you
Sent from my GT-P1000 using xda premium

Maybe tonight I'll see what I can do with the kernel linked in the OP.
Note I do not own a Glide so I won't be able to test.
Sent from my SAMSUNG-SGH-I897 using XDA App

I hate to ask a newb question, but thats what I am when it comes to things like this. Will rooting using this method factory reset the phone as well?

shatteredzman said:
I hate to ask a newb question, but thats what I am when it comes to things like this. Will rooting using this method factory reset the phone as well?
Click to expand...
Click to collapse
Nope; it only flashes /system. Your data partition stays in-tact.
Of course, any time you mess with the device internals, there's a risk, so I'd highly recommend backing up anyway.

We can have an ezroot kernel if we either set the /system partition. As rw (read/write) instead of read only or set in the default.prop the following: ro.secure=0 & persist.service.adb.enable=1, then there's root in "adb shell" to remount the system partition as rw.
Is it a boot.img or initram packed zImage we're dealing with?

[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?

[Q] Flashed the wrong software, bricked... soft I hope

Was updating my Note 2 and accidentally hooked up the Note 3 instead, needless to say it failed. I was running 4.3 and here is what is on my download screen
ODIN MODE
PRODUCT NAME: SM:M900T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK 0X0
KNOX WARRANTY VOID 0X1
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: ENABLE
Okay I know I did a really dumb thing, but it happens.... is this fixable?
Kies does not recognize it in recovery mode
all I have is download mode, will boot no further.
I have been reading a bit about PIT files but all the 4.3 PIT file links I find are dead.
When trying an Oden flash I get
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sbl1.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
And in download mode shows
SW REV CHECK FAIL : [sbl1] Fused 2 > Binary 1
Thanks

If you can get into download mode and into odin then odin back to stock
Sent from my SM-N900T using XDA Premium 4 mobile app
---------- Post added at 04:59 PM ---------- Previous post was at 04:44 PM ----------
http://forum.xda-developers.com/showthread.php?p=50869474
Sent from my SM-N900T using XDA Premium 4 mobile app

Rich3077 said:
SW REV CHECK FAIL : [sbl1] Fused 2 > Binary 1
Click to expand...
Click to collapse
This part tells the whole story. You're going to have to flash kit kat. Why? The Fused value is higher than 4.3. Grab the latest 4.4.2 for the n900t from sammobile and flash that and you should be OK.
Sent from my leanKernel 2.4 powered stock 4.4.2 SM-N900T

toastido said:
This part tells the whole story. You're going to have to flash kit kat. Why? The Fused value is higher than 4.3. Grab the latest 4.4.2 for the n900t from sammobile and flash that and you should be OK.
Sent from my leanKernel 2.4 powered stock 4.4.2 SM-N900T
Click to expand...
Click to collapse
Thanks, looking for the right version for my phone and unable to find it..looking now.
Found it.. downloading now.. thanks

my note 3 is doing this now. out of the blue. DLing the newest firmware from sam mobile. im really hoping heimdall/odin can fix it cuz atm nothing is working. -___- CRAP

Solved, thanks toastido, the factory ROM worked like a charm. Phone working just fine.

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.

Help Soft Bricked Cant Go back to stock

Hello,
So I installed the Rainbow 7 rom and it worked great for 2 days. Next thing I know Im stuck at the Samsung note 2 screen. Im like OK lets open TWRP and restore from Backup. Some how I manage to erase the OS and now I can't even return to Stock. When I try to flash tar I get failed. Phone does go into download mode fine and recovery. TWRP shows my sd and internal as (0) MB but when I use my ext sd card on pc all files are there so cant flash via recovery. Kies does not work either I tried the latest version of TWRP via Latest version of ODIN nothing file is good then I get The Below with OH3
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
With NE2 STOCK in Odin I GET note 2 re-partition operation failed.............
I have always been able to restore my backups or flash back to stock but this time in Stuck. Any Thoughts?
TWRP states no OS found even if I wiped all of the system and data files Should I not be able to go back to stock ? I've tried NE2 and OH3
I have searched and searched and tried but nothing seems to work. If it boots to download mode and recovery it's not a hard bricked it ??
FYI I have tried 2 pc's using different ports and different cables also

When you boot into recovery does it show failure to mount any partitions (system, data, cache)?
Sent from my LG-D851 using XDA-Developers mobile app

cidxtc said:
When you boot into recovery does it show failure to mount any partitions (system, data, cache)?
Sent from my LG-D851 using XDA-Developers mobile app
Click to expand...
Click to collapse
Hello
Yes All of them that your saying. I tried usb on the go and it appears it will install but then same thing error signal 9 and failure to mount any partitions.
Thank you For looking

any suggestions ?
Thank You

travieso1208 said:
any suggestions ?
Thank You
Click to expand...
Click to collapse
I seen a few other users with same issue. Only way that I have seen it fixed is by replacing the main board. Sorry to give bad news.
Sent from my LG-D851 using XDA-Developers mobile app

Ahhh okay thank you

Would you know if switching out the board is just plug and play ?

You could always try to Odin back to stock. Since you can get into recovery i imagine you can get into download mode.Its worth a shot before you order a board and open the phone. Link for the process I was suggest the PC version
http://forum.xda-developers.com/showthread.php?t=2780984
Edit: fixed link to reflect the correct bootloader.
Sent from my SPH-L900 using XDA-Developers mobile app

beansnorice said:
You could always try to Odin back to stock. Since you can get into recovery i imagine you can get into download mode.Its worth a shot before you order a board and open the phone. Link for the process I was suggest the PC version
http://forum.xda-developers.com/showthread.php?t=2780984
Edit: fixed link to reflect the correct bootloader.
Sent from my SPH-L900 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks I'll Give it a shot but it has failed in the past

I dont know if this matters but according to the rainbow 7 install instructions I was supposed to have bootloader of 4.3 or newer.. if i didnt could. This be the cause of everything. I can't believe there isn't a way to fix this without changing the board.

It could very well be why it fails the link above was to the 4.4.2 bootloader if it doest help or fail I have no idea about swapping out the board. I've replaced antanneas and ifixit has a complete teardown of the phone https://www.ifixit.com/Device/Samsung_Galaxy_Note_II hope you figure it out. Sorry I wasn't much more help
Sent from my SPH-L900 using XDA-Developers mobile app

beansnorice said:
It could very well be why it fails the link above was to the 4.4.2 bootloader if it doest help or fail I have no idea about swapping out the board. I've replaced antanneas and ifixit has a complete teardown of the phone https://www.ifixit.com/Device/Samsung_Galaxy_Note_II hope you figure it out. Sorry I wasn't much more help
Sent from my SPH-L900 using XDA-Developers mobile app
Click to expand...
Click to collapse
Okay Thank You I'll Def Try this

travieso1208 said:
Okay Thank You I'll Def Try this
Click to expand...
Click to collapse
Hope it helps
Sent from my SPH-L900 using XDA-Developers mobile app

So I got a clean logic board. Just have to install it and The phone should work fine ?
Thank You

Yes a new logic board should fix your issues. Just remember you'll have to activate that one because it's a totally different meid/esn. I had to swap one on an s3 because of a bad port. Sure it's similar too since it's Samsung.
Sent from my SPH-L900 using XDA-Developers mobile app

travieso1208 said:
Would you know if switching out the board is just plug and play ?
Click to expand...
Click to collapse
Yeah its pretty simple... lol except for the try not to lose all the tiny screws part