Tried to Unroot now bricked - T-Mobile Samsung Galaxy S 4

I had Cynagenmod 4.4.4 on my S4. I wanted to unroot it as the release is buggy. So I went to a link on how to unroot at S4 phones and followed the steps and now I cant get it to unroot and its now stuck in a boot loop. I have tried ODIN multiple times and this is what I get.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Removed!!
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Please help. My phone is a paperweight right now.

Its also giving me a check fail on the phone itself.
Start [224,1140]
SW Rev. Check Fail: 4, Binary : 1

Snakedoktor said:
Its also giving me a check fail on the phone itself.
Start [224,1140]
SW Rev. Check Fail: 4, Binary : 1
Click to expand...
Click to collapse
Your trying to flash the wrong firmware? What was your phone BEFORE you rooted? 4.2.2? 4.3?

The Sickness said:
Your trying to flash the wrong firmware? What was your phone BEFORE you rooted? 4.2.2? 4.3?
Click to expand...
Click to collapse
It was December of last year. I dont honestly remember. I know I was at 4.4.4 when it was rooted. Just looked it up November of last year was 4.3

Snakedoktor said:
It was December of last year. I dont honestly remember. I know I ad 4.4.4 when it was rooted.
Click to expand...
Click to collapse
If you got it in Dec then it was 4.3. If it was 4.4.4 when you rooted meant you took a OTA?

The Sickness said:
If you got it in Dec then it was 4.3. If it was 4.4.4 when you rooted meant you took a OTA?
Click to expand...
Click to collapse
It was an update via cynogen mod that updated it to 4.4.4. It does look like it had 4.3 like you said. Did I download the wrong file?

Snakedoktor said:
It was an update via cynogen mod that updated it to 4.4.4. It does look like it had 4.3 like you said. Did I download the wrong file?
Click to expand...
Click to collapse
Yes you DL the wrong file. Im not too familar with Cynogen. So if it did update you to 4.4.4, you need to Odin the Official 4.4.4 Firmware

Cyanogen 4.4.4 won't require you to flash stock 4.4.4 because it does not update firmware If you had official 4.3 firmware when you flashed cm then you need to flash at least 4.3 firmware. That's why you are getting the error, you were trying to flash 4.2.2. You have the option of flashing 4.3 MK2, 4.4.2 NB4, or 4.4.4 NH7. You might as well flash NH7

One other thought: Just because the CM you are running has some bugs, perhaps another ROM would be a better experience than the bloated Samsung stock.
I'm very happy on Dirty Unicorns, but I've been thinking to try a very basic Slimkat or something like that, then theme it with Themer, and add any apps/functions needed.
Maybe something like that would work for you?
Marc

Related

[Q] Help Flashing Note 2 N7100 through Odin3

Hi everyone. I'm having some troubles with a galaxy note 2. I have one but is with the firmware of China with the JB 4.3.
I've being trying to flash with the firmware of europe, JB 4.1 with odin3 but i can't. It always give an error on sboot.bin.
I've downloaded the stock firmware from sammobile.com.
Tried in different computers and differents USB cables.
Also tried to install two differents USB drivers from differents sources.
Weird thing, i cant root my device by flashing by odin.
Can anyone give me an help?
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_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>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
New Droid said:
Hi everyone. I'm having some troubles with a galaxy note 2. I have one but is with the firmware of China with the JB 4.3.
I've being trying to flash with the firmware of europe, JB 4.1 with odin3 but i can't. It always give an error on sboot.bin.
I've downloaded the stock firmware from sammobile.com.
Tried in different computers and differents USB cables.
Also tried to install two differents USB drivers from differents sources.
Weird thing, i cant root my device by flashing by odin.
Can anyone give me an help?
Click to expand...
Click to collapse
I believe that if it is official 4.3 you cannot downgrade.
Is it a clone?
Sent from my GT-N7105 using xda app-developers app
thedadio said:
Is it a clone?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
If it is a clone is very well disguised, and it have the same SoC (CPU, RAM, Internal Memory, etc)
And it is impossoble to downgrade from 4.3?
New Droid said:
If it is a clone is very well disguised, and it have the same SoC (CPU, RAM, Internal Memory, etc)
And it is impossoble to downgrade from 4.3?
Click to expand...
Click to collapse
You can downgrade from 4.3 but you cannot downgrade the bootloader, that will be stuck
tonylee000 said:
You can downgrade from 4.3 but you cannot downgrade the bootloader, that will be stuck
Click to expand...
Click to collapse
Can you guide me to a post to try please.
I've tried a lot of post but it always fails.
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_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>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Update on first topic
New Droid said:
Can you guide me to a post to try please.
I've tried a lot of post but it always fails.
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_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>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Update on first topic
Click to expand...
Click to collapse
Ah the official stock images will have a bootloader bundled in it. So that maybe where its going wrong. If you install a custom recovery and put a custom rom (arhd19 or wanamlite3.9 are both android 412) that might be the easiest but I would only guess that yhey would work with the mk3 bootloader but it would probably burn the efuse voiding warranty.
....
flash dr ketans knox free bootloader from one of his threads its a downgradable 4.3 bootloader
tonylee000 said:
Ah the official stock images will have a bootloader bundled in it. So that maybe where its going wrong. If you install a custom recovery and put a custom rom (arhd19 or wanamlite3.9 are both android 412) that might be the easiest but I would only guess that yhey would work with the mk3 bootloader but it would probably burn the efuse voiding warranty.
Click to expand...
Click to collapse
I've installed the latest version of CWM Recovery Touch v6.0.4.1 and try to flash the CyanogenMod 10.1.3 to see if it woks.
The_Flashaholic said:
flash dr ketans knox free bootloader from one of his threads its a downgradable 4.3 bootloader
Click to expand...
Click to collapse
Right now I'm on my mobile. Can you send me the link to one post with that please. Thanks
Enviado do meu U9200 através de Tapatalk
The_Flashaholic said:
flash dr ketans knox free bootloader from one of his threads its a downgradable 4.3 bootloader
Click to expand...
Click to collapse
Can the mk3 bootloader be downgraded? I wss under the impression that once upgraded to a mk bootloader you were stuck with it as theyre not downgradable
New Droid said:
Hi everyone. I'm having some troubles with a galaxy note 2. I have one but is with the firmware of China with the JB 4.3.
I've being trying to flash with the firmware of europe, JB 4.1 with odin3 but i can't. It always give an error on sboot.bin.
I've downloaded the stock firmware from sammobile.com.
Tried in different computers and differents USB cables.
Also tried to install two differents USB drivers from differents sources.
Weird thing, i cant root my device by flashing by odin.
Can anyone give me an help?
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_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>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day
exceptionalkhan said:
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day
Click to expand...
Click to collapse
if this is true then it is a great news..we can downgrade to 4.1.2 even with 4.3 bootloader installed...am i right ?
sora9009 said:
if this is true then it is a great news..we can downgrade to 4.1.2 even with 4.3 bootloader installed...am i right ?
Click to expand...
Click to collapse
That MSR version's size is greater than a 1000MBs which means that it has all the required files, which are needed to downgrade from 4.3 to 4.1.2.
So definitely check it out and share the result with us:highfive:
exceptionalkhan said:
That MSR version's size is greater than a 1000MBs which means that it has all the required files, which are needed to downgrade from 4.3 to 4.1.2.
So definitely check it out and share the result with us:highfive:
Click to expand...
Click to collapse
im pretty sure bootloader cannot be downgrade.
sora9009 said:
im pretty sure bootloader cannot be downgrade.
Click to expand...
Click to collapse
Not sure but it worked for me. I had the N7100 made in korea version which is an international version. I upgraded to 4.3 chinese version. Then I wanted to downgrade to 4.1.2, I tried the chinese 4.1.2 version and two others. Which encountered some errors in flashing. Then I tried the MSR version which worked just fine.
Everytime I was flashing the 4.1.2 versions other than the MSR it incremented the binary counter by 2.
exceptionalkhan said:
Not sure but it worked for me. I had the N7100 made in korea version which is an international version. I upgraded to 4.3 chinese version. Then I wanted to downgrade to 4.1.2, I tried the chinese 4.1.2 version and two others. Which encountered some errors in flashing. Then I tried the MSR version which worked just fine.
Everytime I was flashing the 4.1.2 versions other than the MSR it incremented the binary counter by 2.
Click to expand...
Click to collapse
this is really a great news.Thanks
exceptionalkhan said:
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day
Click to expand...
Click to collapse
Sorry man, for me didn't work :S It keeps giving the same error :S
Hi everyone. Finally i could flash the note 2 :victory: but i still dont get it why i cant flash through odin
This is how i do it.
1. Flash the ClockworkMod Recovery through.
2. Flash the TWRP 2.6 Recovery.zip through CWM Recovery. (Don't know i i cant flash this recovery directly on odin
3. Flash a CyanogenMod Nightly ROM
4. Install Odin Mobile.
5. Flash the lastest official rom by Samsung for Europe.
6.Yeh I have a official rom on my mobile :victory:
Now I have one problem, when i try to make a call i cant hear the people on the other side and vice versa. I know the mic and speaker are working, if o try to make a call through skype it works perfectly!
Obs.On every ROM i have this problem, on Stock ROMs by Samsung, Europe and Chinese Version and also on CyanogenMod.
When i try to flash the European ROM on Odin it fails when try to write the modem.bin.
I can flash the Chinese ROM without any problems on Odin.
I'm using the lastest ROM JB 4.3 from Samsung
What is the problem now?
The MSR firmware zip link no longer exists?
I have Chines SN N7100 and screwed with no Google accout
The MSR firmware zip link no longer exists??
exceptionalkhan said:
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day
Click to expand...
Click to collapse
MadR4sta said:
I have Chines SN N7100 and screwed with no Google accout
The MSR firmware zip link no longer exists??
Click to expand...
Click to collapse
Ma Bad...
Bro! the thread is closed, will update that later.
An updated link is Here:https://my.pcloud.com/#page=publink&code=XZgADZWDMzsYh1Xa8uTeOaSPsb2VAn5tb7

SGH-I747 flashed to 4.3 bootloader/modem cannot go back to stock?

I had encryption on my phone due to company emails. I flashed bootloader and modem to 4.3 (I747UCUEMJB) in order to enjoy the latest custom ROMs.
However, after installing 5-6 of custom ROMs, I am always asked to "enter your PIN or password to encrypt the memory". No matter what I enter, the phone always restarts and goes back to the prompt asking me to enter PIN or password.
I did factory reset and cache/etc. wipes every time I flash. I thought encryption should be erased by those resets/wipes. BTW - I use TWRP as recovery.
What I would like to know, is there a way for me to get a stock 4.3 ROM to install using ODIN? Hopefully that will also install the stock recovery, which may be able to help me really do a clean factory reset/data wipe.
Any thoughts? Thanks.
You can find pre rooted stock rom from herehttp://forum.xda-developers.com/showthread.php?t=1739426
hope that helps
BTW, I have tried using ODIN to get back to 4.1.2: I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar file.
However, ODIN is giving "Fail (Auth)" errors. I suppose this is because I have flashed the bootloader and modem to a much higher version and there is no way to go back?
Harsh99132 said:
You can find pre rooted stock rom from herehttp://forum.xda-developers.com/showthread.php?t=1739426
hope that helps
Click to expand...
Click to collapse
Nope. these I747ATTDLK3 images won't work because once you flash these new 4.3 bootloader (I747UCUEMJB), you cannot go back to early stock ROMs. The only way is to find the 4.3 stock ROMs for ODIN, which is no where to find on the internet.
Here is the error from ODIN when I tried the I747ATTDLK3 image:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have run KK ROMs with a stock 4.1.2 bootloader with no problems at all. Updating to 4.3 isn't necessary in my opinion.
AT&T never released a stock 4.3 ROM that can be flashed via Odin. AT&T released 4.3 as an OTA update.
At this point, you may be better off flashing a custom recovery such as Philz Touch and flash a KK ROM.
audit13 said:
I have run KK ROMs with a stock 4.1.2 bootloader with no problems at all. Updating to 4.3 isn't necessary in my opinion.
AT&T never released a stock 4.3 ROM that can be flashed via Odin. AT&T released 4.3 as an OTA update.
At this point, you may be better off flashing a custom recovery such as Philz Touch and flash a KK ROM.
Click to expand...
Click to collapse
Wow. CWM recovery (Philz Touch) + CyanogenMod 10 Nightly Builds for SGH-I747 solved my problem! I can finally use my phone now!
Thank you so much!
zhangla said:
Wow. CWM recovery (Philz Touch) + CyanogenMod 10 Nightly Builds for SGH-I747 solved my problem! I can finally use my phone now!
Thank you so much!
Click to expand...
Click to collapse
That's great. Why stop at CM10? Try some 4.4.2-based ROMs like Cyanfox or Valiudus. Both are great and I love the dark theme for Validus.

[Q] odin downgrade from 4.3 to 4.1.1 error

i have sgh-t999 from t-mobile with
android: 4.3
compilation: jss15j.t999uvuenc2
i am trait downgrade to 4.1.1 for sim unlock, i download
UVDLJA
PDA: T999UVDLJA
CSC: T999TMBDLJA
Version: 4.1.1 JB
Date: Nov. 14, 2012
for use whit odin but when i trait to flash i have this log
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDLJA_T999TMBDLJA_T999UVDLJA_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
what can i do?
Cant be done. You'll have to get a code from T-Mobile or buy one online.
i can unlock this phone?
DocHoliday77 said:
Cant be done. You'll have to get a code from T-Mobile or buy one online.
Click to expand...
Click to collapse
then i can not unlock this phone for other sim using odin or cwm or any other free method?
Nope. Sorry. Once on 4.3 you cannot downgrade your firmware without hard bricking your device. Using a valid code is the only way now.
You might find one for fairly cheap on ebay.
the last question
DocHoliday77 said:
Nope. Sorry. Once on 4.3 you cannot downgrade your firmware without hard bricking your device. Using a valid code is the only way now.
You might find one for fairly cheap on ebay.
Click to expand...
Click to collapse
i can try do any playing with knox??? sorry for my insistence, the problem is so right now i can not pay any unlock code. can you please recommended any site or way in case i can pay de unlock code???
Best I can say is to search ebay for sim unlock galaxy s3. I dont know of any specific sites. I think a few may have been mentioned in the unlock thread, but you'll probably just have to do a lot of reading to find them. Look for posts with links in them.
what if the phone is on a rooted version of stock 4.3?
thejanitor86 said:
what if the phone is on a rooted version of stock 4.3?
Click to expand...
Click to collapse
If you updated to 4.3 via OTA/Odin/Kies it doesn't matter.. If all you did was flash a 4.3 ROM while still on 4.1.2 or below bootloader its still possible to unlock unless you have a T999L then you are out of luck
And root doesn't matter for this. Should work either way.
DocHoliday77 said:
And root doesn't matter for this. Should work either way.
Click to expand...
Click to collapse
I assumed they meant downgrading to unlock but I guess not necessarily.. But yes unlocking by code isn't affected by being rooted

Updating to NF4

I'm running stock bootloader from launch when I got the phone in 2013. Currently running 4.4.2 updated via Mexican firmware leak back in early spring. I need to update to NF4 bootloader. I keep getting error in Odin when I try to flash NF4. Do I need to be on NF1 before I can flash NF4?
re: baseband
llsektorll said:
I'm running stock bootloader from launch when I got the phone in 2013. Currently running 4.4.2 updated via Mexican firmware leak back in early spring. I need to update to NF4 bootloader. I keep getting error in Odin when I try to flash NF4. Do I need to be on NF1 before I can flash NF4?
Click to expand...
Click to collapse
You don't need to be on NF1 or any other baseband version in order to update
to the NF4 baseband.
Here is the direct download link for ODIN in case you need it, this version works
best for me: https://dl.dropboxusercontent.com/u/45687485/Odin85.zip
Be sure you have the latest Samsung USB driver installed which can be found here:
http://tinyurl.com/nlnegmj and be sure to use the original samsung usb cable which
came with your phone for best results.
Good luck!
Misterjunky said:
You don't need to be on NF1 or any other baseband version in order to update
to the NF4 baseband.
Here is the direct download link for ODIN in case you need it, this version works
best for me: https://dl.dropboxusercontent.com/u/45687485/Odin85.zip
Be sure you have the latest Samsung USB driver installed which can be found here:
http://tinyurl.com/nlnegmj and be sure to use the original samsung usb cable which
came with your phone for best results.
Good luck!
Click to expand...
Click to collapse
Thanks I'll try right now. I was using 3.09 which may be causing a problem.
Edit:
I'm getting the following error.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I'm using the N900W (Canadian). Not the N900T. I futhermore I can flash the Canadian Firmware NB7 with no issues.

Unable to Odin stock OB7 or stock NK2.

I don't seem to be able to Odin stock OB7 or stock NK2. When I attempt to Odin either I get this on Odin:
<OSM> N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> NAND Write Start!!
<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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and get this on the download screen:
UDC START
SW REV CHECK FAIL : [tz]Fused 3>Binary 1
[4]eMMC write fail: TZ
Right now I'm running HYBRID_OB7sbl_SPT_N910PVPU4COG5 unrooted. Any potential help with what I've done would be great. Thanks guys.
Cant go back. Period.
Sent from my SM-N910P using Tapatalk
I have the same problem. Updated the phone with the latest from Sprint / Samsung, then tried to root and got into a boot loop. I can get into download mode and recovery. Trying to flash a ROM with CWM recovery fails too.
<OSM> Enter CS for MD5..
<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> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> 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)
Read frezzas stockish thread.
Sent from my SM-N910P using Tapatalk
It's failing because the bootloader is not authenticating. Since you flashed my custom rom odin package I'm surprised it's not letting you flash the official OB7 rom tar. Apparently there's more to this equation than just the bootloader or else you tried or successfully flashed the pre-rooted kernel before you tried to odin the OB7 rom tar. Try flashing my custom OB7/OG5 rom tar again THEN flash the official OB7 rom tar. You need to be bone stock before attempting the odin of OB7. If it still fails then give up because you can't win this battle. Just update to OG5 and don't worry about it.
I'll be honest, there's really no reason why you shouldn't just go ahead and wipe everything clean and flash my custom OB7/OG5 rom tar again or the official OG5 rom tar and let your bootloader update to OG5. I think 5.1.1 is by far the best version of Android to date. I see absolutely no reason to flash older software versions because 5.1.1 is much more responsive in every way and battery life is improved as well. Don't sweat this. If I had any trouble with my OB7 bootloader I'd update mine to OG5 in a second.
After blowing nearly an entire day....
To start off my phone was stock / rooted, I then installed the latest update via Kies (OE1, wanted the Stagefreight patch) and attempted to re-root my phone which I then found was stuck in a boot loop. I got lazy, updates had been going well on the Note 4 and I failed to come to XDA to see if there were any problems rooting it, turns out there is :crying: and I couldn't get Kies to recover it, and factory reset didn't work either. To recover I tried to use ODIN to flash OB7 and received the above results, I tried a few other stock ROMs and got the same problem.
At this point I was about ready to chuck my phone out the door until I noticed a comment saying that once you flash OE1 you can't go back and the only option is to flash an AOSP ROM such as Notirized. I downloaded Notorized, following the OP directions step by step and I now have my phone back! So far I like this ROM, so maybe this was fate
http://forum.xda-developers.com/not...-noterized-rom-super-speedy-reliable-t3099382
Thanks XDA! Now if I only had come here first and saved myself an entire day of grief! (Took away from my time playing Elite Dangerous! lol).
Thanks man. I appreciate the response and the explanation. I thought it was an issue with the bootloader, but I was confused about what I had done. I did wind up wiping everything clean and flashing your custom OB7/OG5 rom tar. Thanks for putting that together. I definitely should have updated everything sooner. I appreciate the advice on the OG5 bootloader as well. Have a great weekend.
tx_dbs_tx said:
It's failing because the bootloader is not authenticating. Since you flashed my custom rom odin package I'm surprised it's not letting you flash the official OB7 rom tar. Apparently there's more to this equation than just the bootloader or else you tried or successfully flashed the pre-rooted kernel before you tried to odin the OB7 rom tar. Try flashing my custom OB7/OG5 rom tar again THEN flash the official OB7 rom tar. You need to be bone stock before attempting the odin of OB7. If it still fails then give up because you can't win this battle. Just update to OG5 and don't worry about it.
I'll be honest, there's really no reason why you shouldn't just go ahead and wipe everything clean and flash my custom OB7/OG5 rom tar again or the official OG5 rom tar and let your bootloader update to OG5. I think 5.1.1 is by far the best version of Android to date. I see absolutely no reason to flash older software versions because 5.1.1 is much more responsive in every way and battery life is improved as well. Don't sweat this. If I had any trouble with my OB7 bootloader I'd update mine to OG5 in a second.
Click to expand...
Click to collapse

Categories

Resources