I tried to upgrade to KitKat using this method (http://forum.xda-developers.com/showthread.php?t=2726868). Initially I flashed the AP and CP files as instructed. No errors and the hone rebooted. It was stuck on the boot animation for about 15 mins and the phone was starting to warm up so I powered it down and tried again. Still no luck. In the thread, it mentioned that if boot was unsuccessful, try flashing the CSC file. I tried that and it failed. I can no longer acess anything other than download mode, and trying to reflash just AP and CP no longer work either.
I did get a message about the PIT partition being unavailable. What potential next steps do I have from here?
Flashing the full wipe tar for nc5 in odin might help. I've been in this situation before and this got me out of it. Link for file and directions: http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my SCH-I545 using XDA Free mobile app
UnlinkedEnergy said:
Flashing the full wipe tar for nc5 in odin might help. I've been in this situation before and this got me out of it. Link for file and directions: http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the reply. I was finally able to get it back to being "stable". I managed to flash the AP, CP and CSC files individually and all went successful. It still hangs at the boot screen, but it's a step forward.
I went directly from MK2 (I think) to NC5 via the link above. I didn't need to go to NC2 first did I?
tristanlee85 said:
I went directly from MK2 (I think) to NC5 via the link above. I didn't need to go to NC2 first did I?
Click to expand...
Click to collapse
Nah, I dont think you had to go to nc2 first if you came from mk2
Sent from my SCH-I545 using XDA Free mobile app
UnlinkedEnergy said:
Nah, I dont think you had to go to nc2 first if you came from mk2
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Now I don't remember what I was on. I know I was using Hyperdrive 16. Either way, seems I can't get passed the boot animation for the stock rom. Is there something I can flash back to?
Is it your intention to be able to upgrade and downgrade again or are you wanting to stay at NC5? Root is easy for NC5 and you don't even need a computer. I would still consider doing a full wipe and starting over. Make sure you use the original data cable that came with the phone. The cable and the usb port chosen is often the cause of failures in flashing via oden.
You might be stuck at NC5 now regardless but in case the upgrade didn't take you could start with the MK2 wipe and if that fails, go with the NC5 wipe.
tristanlee85 said:
Now I don't remember what I was on. I know I was using Hyperdrive 16. Either way, seems I can't get passed the boot animation for the stock rom. Is there something I can flash back to?
Click to expand...
Click to collapse
What does it say on odin when u flash the tar file (like <id:0/003> recovery.img
<id:0/003> hidden.img)
It should say stuff like that in an area that says message in the bottom left corner of odin. It would be nice if u could copy and paste the message lines that showed up during the flash unless you already closed odin. Unless u flashed the full wipe tar try recovery booting and wiping cache and factory resetting
Sent from my SCH-I545
My intent is to stay on NC5. I am not looking to go back unless I can't get NC5 to work.
Is this the full wipe file I need to flash using Odin? VRUFNC5 Full-Wipe SCH-I545_VZW_1_20140330160240_8il17ls9o2_fac.zip
Do I flash it using the AP slot? Does CP or CSC matter?
tristanlee85 said:
My intent is to stay on NC5. I am not looking to go back unless I can't get NC5 to work.
Is this the full wipe file I need to flash using Odin? VRUFNC5 Full-Wipe SCH-I545_VZW_1_20140330160240_8il17ls9o2_fac.zip
Do I flash it using the AP slot? Does CP or CSC matter?
Click to expand...
Click to collapse
The file you sre looking for will end in md5.tar. use the link that was provided to you by unlinkedenergy. There will be a rar file ( same as a zip file) that you will have to unzip. You will put it in the ap slot. Yhe post you used for upgrading was actually a post for upgrading with the ablility to downgrade again. This is trickier than just upgrading.
tristanlee85 said:
Now I don't remember what I was on. I know I was using Hyperdrive 16. Either way, seems I can't get passed the boot animation for the stock rom. Is there something I can flash back to?
Click to expand...
Click to collapse
Like Tulsadiver said, the upgrade might of not fully flashed. Flashing the mk2 tar if you are on nc5 will possibly fail in odin. It is probably ok to try it though. You can root nc5 with towelroot, an apk that roots your phone in one click
Sent from my SCH-I545
UnlinkedEnergy said:
Like Tulsadiver said, the upgrade might of not fully flashed. Flashing the mk2 tar if you are on nc5 will possibly fail in odin. It is probably ok to try it though. You can root nc5 with towelroot, an apk that roots your phone in one click
Sent from my SCH-I545
Click to expand...
Click to collapse
I am trying the upgrade again while the full wipe tar downloads. Here is the output from odin:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.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> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> persdata.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> NON-HLOS.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
Sounds like that one flashed fine. Again though, the thread you used was for up and downgrading again.
Did it say "pass" at the end?
Tulsadiver said:
Sounds like that one flashed fine. Again though, the thread you used was for up and downgrading again.
Did it say "pass" at the end?
Click to expand...
Click to collapse
It did say pass once completed. Still just hung at the boot animation so I am flashing the full wipe right now so we'll see...
tristanlee85 said:
It did say pass once completed. Still just hung at the boot animation so I am flashing the full wipe right now so we'll see...
Click to expand...
Click to collapse
Just so you know, the first boot will take several minutes.
Tulsadiver said:
Just so you know, the first boot will take several minutes.
Click to expand...
Click to collapse
Well, that fixed it luckily. So now that I have KitKat on here, I am going to be putting another rom on slot 1 of Safestrap so I don't even worry about configuring the stock. Am I going to be able to get away with flashing Hyperdrive on slot 1 along with the SuperSu patch to keep root, or must I do something on the stock rom to obtain it?
Sorry, I missed your comment about towelroot earlier. I got that on the stock rom, rooted, activated Safestrap and hopefully will be on my other rom soon. Thank you both for the help!
tristanlee85 said:
Well, that fixed it luckily. So now that I have KitKat on here, I am going to be putting another rom on slot 1 of Safestrap so I don't even worry about configuring the stock. Am I going to be able to get away with flashing Hyperdrive on slot 1 along with the SuperSu patch to keep root, or must I do something on the stock rom to obtain it?
Click to expand...
Click to collapse
I think that the root will be kept when you flash onto a rom slot (well at least for me root was kept last time I flashed on a rom slot). If you are running safestrap 3.72 (as opposed to safestrap 3.71) rom slots don't work but you can flash kitkat roms on 3.72
Sent from my SCH-I545
UnlinkedEnergy said:
I think that the root will be kept when you flash onto a rom slot (well at least for me root was kept last time I flashed on a rom slot). If you are running safestrap 3.72 (as opposed to safestrap 3.71) rom slots don't work but you can flash kitkat roms on 3.72
Sent from my SCH-I545
Click to expand...
Click to collapse
I just noticed that. It appears I will have to flash on the stock slot which is fine with me.
tristanlee85 said:
I just noticed that. It appears I will have to flash on the stock slot which is fine with me.
Click to expand...
Click to collapse
Glad you are up and running. Definitely have to use 3.72 and stock slot. Make a backup of your stock rom right off the bat.
If we were any help, don't forget to hit the thanks button!
Happy flashing!!
Related
**** Major Update: Thanks to imnuts and his alternate restore, I'm back on track and unrooted stock again.
For some reason the sboot.bin causes ODIN to fail. If this is just an isolated incident, cool, if not, this could mean getting back to stock out of necessity may be harder than we expected. Something to keep an eye on.
For reference, imnuts' post with the stock restore images:
http://forum.xda-developers.com/showthread.php?t=2040264
*** UPDATE: Still can't update with the stock image but I used the root66 stock rooted image and ODIN was able to complete. I'm able to boot the phone normally however it won't activate. I am completely lost here. ***
Was stock rooted no mods, so I flashed back to stock so I could perform the OTA update. That went fine so I installed the update.
Using Adam's new post OTA root the process didn't take so I tried a second time. The process hung and I had to do a battery pull.
Now it either boots into the Plug into Kies for emergency firmware upgrade or the Samsung Galxy Note 2 boot logo and goes no further.
Again attempting to restore to stock I flashed with Odin and here's where it gets interesting.
The process FAILS at the sboot.bin element.
*** Is it posible the OTA update made the stock recovery image incompatable? ***
Using the instructions here: http://forum.xda-developers.com/showthread.php?t=2024207
----- ODIN LOG -----
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----- END ODIN LOG -----
ODIN and Casual see the phone and can talk to it however KIES cannot so I can't do this emergency recovery the phone is telling me to do. KIES says the device is not responding and to reboot it.
I can boot into Download Mode. I was able to get into Recovery Mode but can't now. The error in Recovery Mode was something about /system not being found.
I have no idea what to do. I have tried the process on 2 different computers. Am I Bricked Bricked?
Thanks in advance.
Under the root66 image the phone is only registering 4 gigs of available space.
Junior member, where did you find the alternate restore method?
exmeaguy said:
Junior member, where did you find the alternate restore method?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2040264
Took me a moment to find it. The only difference between the 2 is that the alternate one is without sboot.bin.
Thanks for checking. When I run the first method (3 times now) it fails at the sboot.bin step. I did download the alternate method once from the first site, but it said the file was not a PDA file. How did you get the alternate method file to work? I appreciate the help.
---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------
The file extension ends with XZ, which Odin said was not a PDA file.
exmeaguy said:
Thanks for checking. When I run the first method (3 times now) it fails at the sboot.bin step. I did download the alternate method once from the first site, but it said the file was not a PDA file. How did you get the alternate method file to work? I appreciate the help.
---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------
The file extension ends with XZ, which Odin said was not a PDA file.
Click to expand...
Click to collapse
It has an odd file extension .xz (perhaps meant to be .gz) so I told 7zip to extract it. resulting file ended in .tar.md5. Then it works.
Hope this helps.
Thanks Junior member I will try that.
exmeaguy said:
Thanks Junior member I will try that.
Click to expand...
Click to collapse
I'm curious why you keep calling him junior member?
Sent from my SCH-I605 (AKA NOTE 2)
Oops, sorry rdeckerr, I was looking too quickly at the name and looked at the wring line.
exmeaguy said:
Oops, sorry rdeckerr, I was looking too quickly at the name and looked at the wring line.
Click to expand...
Click to collapse
hahahaha
Wasn't sure if it was a newbie hazing kind of thing. That's funny though. No worries!
I thought I saw on one of your posts that you used root66 (same as me) and that your phone only shows 4gb of space. Did you re-root with root66 or did you use another method?
exmeaguy said:
I thought I saw on one of your posts that you used root66 (same as me) and that your phone only shows 4gb of space. Did you re-root with root66 or did you use another method?
Click to expand...
Click to collapse
Originally I was rooted with Adam Outler's casual / ODIN method (which was flawless first time round). I had tried the root66 this time just to see if it would actually take with ODIN since the stock restore kept failing. I was just desperate to find a rom that would "pass" on ODIN. I just needed to know my phone was still capable of booting fully back into android. Even if it happened to be without radio / activation capability or a wrongly registered internal storage space (which was friggin wierd, couldn't even take a screenshot).
I will re-root with Adam's process, when the kinks are out (say next weekend when I have a couple days it doesn't matter if my phone is dead . I had A.O.'s original root running for a couple weeks and it was great. The implementation was smooth, not requiring reinstalling / restoring anything. I'd backed up of course but it was one of those nice times the backups weren't necessary.
So at the moment for the sake of my job, I'm leaving it stock for the week. I just can't be without a phone for work.
rdeckerr said:
http://forum.xda-developers.com/showthread.php?t=2040264
Took me a moment to find it. The only difference between the 2 is that the alternate one is without sboot.bin.
Click to expand...
Click to collapse
Welli have the same exact issue. I am so lost its riddiculous. I have been working on this for over 20 hours and have gotten no where.
The only thing. Can add is that I attempted to root my device with the method that injects the 1 gig file in the system. Worked fine and installed cwm. Restarted and bricked with the unauthorized by verizon message. Downloaded the stock file without bootloader first and worked fine. I then tried every sinfle methodand trick I coild find to no avail.
Every time I try to install the baseline bootloader so I can unlock it fails at the end. If itry to put a full stock image on it fails at the beginning.
They both fail when tryinf to do the sboot.bin. so its obviously with that.
I need some ind of fix but no one seems to have it. I cant be doomed to a uncustomized device!
I am thinking of seeing if my verizon store will take it back and give me a fresh one so I can do the original exploit method.
It might work. Ive had the phone for less than a month.
Don't you need to flash a pit file if you're not doing so when you run into sboot.bin issues?
universexda said:
Don't you need to flash a pit file if you're not doing so when you run into sboot.bin issues?
Click to expand...
Click to collapse
No it fails at sboot because the ll4 boot loader is set to block any writing of a boot loader at all. That's why you need the alternate restore because it didn't write sboot.
Sent from my SCH-I605 using Tapatalk 2
rdeckerr said:
**** Major Update: Thanks to imnuts and his alternate restore, I'm back on track and unrooted stock again.
For some reason the sboot.bin causes ODIN to fail. If this is just an isolated incident, cool, if not, this could mean getting back to stock out of necessity may be harder than we expected. Something to keep an eye on.
For reference, imnuts' post with the stock restore images:
http://forum.xda-developers.com/showthread.php?t=2040264
*** UPDATE: Still can't update with the stock image but I used the root66 stock rooted image and ODIN was able to complete. I'm able to boot the phone normally however it won't activate. I am completely lost here. ***
Was stock rooted no mods, so I flashed back to stock so I could perform the OTA update. That went fine so I installed the update.
Using Adam's new post OTA root the process didn't take so I tried a second time. The process hung and I had to do a battery pull.
Now it either boots into the Plug into Kies for emergency firmware upgrade or the Samsung Galxy Note 2 boot logo and goes no further.
Again attempting to restore to stock I flashed with Odin and here's where it gets interesting.
The process FAILS at the sboot.bin element.
*** Is it posible the OTA update made the stock recovery image incompatable? ***
Using the instructions here: http://forum.xda-developers.com/showthread.php?t=2024207
----- ODIN LOG -----
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----- END ODIN LOG -----
ODIN and Casual see the phone and can talk to it however KIES cannot so I can't do this emergency recovery the phone is telling me to do. KIES says the device is not responding and to reboot it.
I can boot into Download Mode. I was able to get into Recovery Mode but can't now. The error in Recovery Mode was something about /system not being found.
I have no idea what to do. I have tried the process on 2 different computers. Am I Bricked Bricked?
Thanks in advance.
Click to expand...
Click to collapse
Is there a fix for this? I have been getting the same error message via odin. Can someone post the fix or link so we can get back up and running...thanks.
kintwofan said:
No it fails at sboot because the ll4 boot loader is set to block any writing of a boot loader at all. That's why you need the alternate restore because it didn't write sboot
Click to expand...
Click to collapse
The alternate restore won't attempt to restore the bootloader to stock right?
universexda said:
The alternate restore won't attempt to restore the bootloader to stock right?
Click to expand...
Click to collapse
That's right. It will restore everything except the boot loader. It's really to restore and keep boot loader unlocked, but add an added benefit let's unbrick the new ota.
Sent from my SCH-I605 using Tapatalk 2
Same problem
I have the same problem as the original post i keep getting stuck at shoot.bin, as it is know my phone is unusable! I was wondering if their is any method to get it back to the original FW.
aka113 said:
I have the same problem as the original post i keep getting stuck at shoot.bin, as it is know my phone is unusable! I was wondering if their is any method to get it back to the original FW.
Click to expand...
Click to collapse
Did you actually read any of this thread? We got his phone working.
Sent from my SCH-I605 using Tapatalk 2
I tried to install a custom ROM on my new Verizon Galaxy S4 and somehow softbricked it. When I try and flash the stock ROM in Odin I get this error message
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> sbl1.mbn
<ID:0/013> NAND Write Start!!
<ID:0/013> sbl2.mbn
<ID:0/013> sbl3.mbn
<ID:0/013> rpm.mbn
<ID:0/013> aboot.mbn
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HELP ME
Youre on me7 trying to flash the mdk firmware. Once on me7 you cant revert back to mdk. You cant install custom roms on me7 or custom recovery. Im guessing you flashed a custom recovery and when you tried to boot into recovery it put you in download mode correct?
Sent from my SCH-I545 using Tapatalk 2
Yeah that's what happened. What are my next steps to have a working phone?
gershonluca said:
Yeah that's what happened. What are my next steps to have a working phone?
Click to expand...
Click to collapse
This is what I did...Battery pull...when you put the battery back in hold the down volume,power and home buttons. as soon as the phone vibrates release the power button and keep holding the other 2. when the prompt comes up"do you really want to do this" or something like that,click no. should boot up normally then.
CatsTide said:
This is what I did...Battery pull...when you put the battery back in hold the down volume,power and home buttons. as soon as the phone vibrates release the power button and keep holding the other 2. when the prompt comes up"do you really want to do this" or something like that,click no. should boot up normally then.
Click to expand...
Click to collapse
That will work but youll have to do it everytime you boot. Flash the me7 image through odin and youll be good to go after that.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
That will work but youll have to do it everytime you boot. Flash the me7 image through odin and youll be good to go after that.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I read that too but I'm not having to do it.
I just tried that but when it reboots it goes to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
CatsTide said:
I read that too but I'm not having to do it.
Click to expand...
Click to collapse
My bad I mis spoke. Everytime you try to get into recovery itll do that. Reflashing me7 is still suggested so you will atleast have a stock recovery. I also suggest checking out the me7 safestrap thread because when its released youll be able to use custom TW roms then.
Sent from my SCH-I545 using Tapatalk 2
So right now there is no way for me to have a working phone?
gershonluca said:
So right now there is no way for me to have a working phone?
Click to expand...
Click to collapse
Flash the stock me7 image through odin. If you have data/apps you dont want removed use the no wipe images.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Flash the stock me7 image through odin. If you have data/apps you dont want removed use the no wipe images.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Can you link me to the file? I can't seem to find it.
gershonluca said:
Can you link me to the file? I can't seem to find it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=43420116 - will wipe user apps/data
http://forum.xda-developers.com/showthread.php?p=41977487 - wont wipe user apps/data
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
http://forum.xda-developers.com/showthread.php?p=43420116 - will wipe user apps/data
http://forum.xda-developers.com/showthread.php?p=41977487 - wont wipe user apps/data
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Thank you so much! How would I go about installing a new mod such as JellyBam?
gershonluca said:
Thank you so much! How would I go about installing a new mod such as JellyBam?
Click to expand...
Click to collapse
Short answer, You can't until safestrap is up and going since you're now stuck with no loki workaround.
Sent from my SCH-I545 using Tapatalk 4
gershonluca said:
Thank you so much! How would I go about installing a new mod such as JellyBam?
Click to expand...
Click to collapse
Like addiso said no romming for the moment. I would look into xposed ( google xposed framework) and the wanam module from the play store. I actually went from custom roms back to a stock deodexed me7 rom using the aforementioned and i love it. Youll atleast be able to make some mods to your phone that way.
Sent from my SCH-I545 using Tapatalk 2
I tried to flash SCH-I545_MD2_423399_Kernel.tar onto my Galaxy S4, and it said boot.img Fail. I have a SCH I545 and I have been looking everywhere for a fix but this is sort of a last resort. Does anyone know what do to? Thanks in advance.
Incaendium said:
I tried to flash SCH-I545_MD2_423399_Kernel.tar onto my Galaxy S4, and it said boot.img Fail. I have a SCH I545 and I have been looking everywhere for a fix but this is sort of a last resort. Does anyone know what do to? Thanks in advance.
Click to expand...
Click to collapse
Was your S4 on the MDK bootloader/release before you tried flashing the MD2 kernel with Odin?
If it was NOT on MDK, then you can't root using that method; you'll need to flash the MK2 Odin tar from here: http://forum.xda-developers.com/showthread.php?t=2578209
And then root using saferoot: http://forum.xda-developers.com/showthread.php?t=2565758
You will not be able to install TWRP/CWM on a non-MDK S4.
bleh
I have already rooted, the problem is that I can't flash and custom ROM's, This is exactly what happens whenever I try to flash anything onto my device.
I will put it in PDA or its specified placement, and make sure everything that is needed to be checked is checked, then I will press start.
Odin will proceed to fail at boot.img, and I will then get frustrated.I can't send you a link to a screenshot yet, so if you want one I might be able to send you it in a private message, just let me know.
Along with the full message that Odin gives me <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Kernel.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I had to use a different MD5, but this is exactly what happens with everything.
When and where did you buy your S4?
I bought it at Verizon about a month or two ago
You can't flash a custom recovery on it at all then, only the first S4s bought around when it was released and then never updated can have custom recoveries.
If your phone won't boot (now or in the future), you'll need to flash the MK2 Odin tar from the thread I linked to restore it to stock.
Your only option for flashing roms will be safestrap, and only TouchWiz-based roms will work.
Safestrap: http://forum.xda-developers.com/showthread.php?t=2441441
Compatible roms: http://forum.xda-developers.com/showthread.php?t=2634408
Any reccomendations? I have never seen these.
Incaendium said:
Any reccomendations? I have never seen these.
Click to expand...
Click to collapse
If you want AOSP, Eclipse is probably the closest (themed) you can get to it: http://forum.xda-developers.com/showthread.php?t=2351840
Otherwise maybe try Bonestock, BajaROM, Hyperdrive... find whatever you like best.
Nevermind again, how do I install a rom using safestrap
Alright so I did a data wipe atempting to open up a rom slot, but I couldent get enough storage open so I just rebooted. Now my phone is stuck on the samsung custom screen that you get after you try to reboot. Did I just brick my phone?
Incaendium said:
Alright so I did a data wipe atempting to open up a rom slot, but I couldent get enough storage open so I just rebooted. Now my phone is stuck on the samsung custom screen that you get after you try to reboot. Did I just brick my phone?
Click to expand...
Click to collapse
You may or may not have bricked it. To me though it sounds like you may just want to start fresh and Odin MK2 back on your phone.. Use Saferoot, then install SafeStrap.
I'd suggest saving anything you don't want to lose and use the full wipe Odin image.
A fresh start sometimes is just the way to go. You can of course fiddle with things and see if that's not needed... But that's what I would do
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
I had mk2 installed with root, stock ROM. I tried to update with OTA with no luck, so I unrooted, still no luck
Any ideas how to get the 4.4.2 stock ota upgrade? I got rid of root, but the bootloader still says custom.
Thanks so much
I have same issue.. But I was running saferoot as well
Sent from my SCH-I545 using XDA Premium 4 mobile app
mikedombo said:
I had mk2 installed with root, stock ROM. I tried to update with OTA with no luck, so I unrooted, still no luck
Any ideas how to get the 4.4.2 stock ota upgrade? I got rid of root, but the bootloader still says custom.
Thanks so much
Click to expand...
Click to collapse
Sounds like you still have something modified on your system from root. You should Odin the no-wipe mk2 odin from here and then try taking to OTA.
Why dint r you just Odin the nb1 and not worry about the update
Sent from my Nexus 5
I had the same custom issue after unrooting. Go back and find the saferoot file you downloaded. ( if you no has go finds again)
Depending where your at you'll need to either re-root and install superuser(let it update) or if you haven't removed SU yet don't do it.
The point is you need to use the uninstall.bat from saferoot to remove the root and then remove root via superuser. reboot (it'l still say custom) and wait 10 mins and then reboot again, should now come up clean.
But from there I still wasn't able to update OTA.
Make sure you didn't have ANY apps frozen via titanium backup or any stock apps deleted. Verizon pulls some crazy sorcery
It will be best to just Odin the no-wope mk2 full tar like I said a few posts up
Sent from my SCH-I545 using Tapatalk
odin flashing failing
so I'm trying odin flashing using both 1.85 and 3.09, and neither work.
Here is the log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUEMK2_I545VZWEMK2_I545VRUEMK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Nevermind - looks like I just had a bad cable
Is nb1 the new 4.4.2 OTA? Where can we get it? Or is that the leak?
One I update to 4.4.2, I lose root. Am I correct?
Sent from my SCH-I545 using xda premium 4 app
Phone: Verizon Galaxy S4
Tablet: Samsung Galaxy Tab2 10.1
swrght13 said:
One I update to 4.4.2, I lose root. Am I correct?
Sent from my SCH-I545 using xda premium 4 app
Phone: Verizon Galaxy S4
Tablet: Samsung Galaxy Tab2 10.1
Click to expand...
Click to collapse
that is correct
Finally got OTA with odin
BruteSource said:
Is nb1 the new 4.4.2 OTA? Where can we get it? Or is that the leak?
Click to expand...
Click to collapse
NC5 is the OTA version, I just got it to work once I used odin.
I got the OTA to succesfully install after using odin as well. Flashed back to a fully stock rom(mk2) and did a factory reset to remove the "samsung custom" bootscreen. Once that finished, I installed the new OTA
joshuabg said:
Sounds like you still have something modified on your system from root. You should Odin the no-wipe mk2 odin from here and then try taking to OTA.
Click to expand...
Click to collapse
I have a question; under build number on my phone it says JSS15J.I545VRUEMK2
Under Step 1 in the link you provided I don't see my build number listed anywhere, so how do I know which factory image to download and flash?
Thanks for any help. I'm an extreme novice at rooting. I rooted my phone for the first time back in December using saferoot/SuperSU and am a real newbie when it comes to stuff like this, so I'd really appreciate any help.
WildKap said:
I have a question; under build number on my phone it says JSS15J.I545VRUEMK2
Under Step 1 in the link you provided I don't see my build number listed anywhere, so how do I know which factory image to download and flash?
Thanks for any help. I'm an extreme novice at rooting. I rooted my phone for the first time back in December using saferoot/SuperSU and am a real newbie when it comes to stuff like this, so I'd really appreciate any help.
Click to expand...
Click to collapse
Flash the one for mk2. What do you want to do? Odin mk2 will put your phone back to a like new condition. If you flash the no wipe version everything on your internal will need preserved.
Sent from my SAMSUNG-SGH-I727
jd1639 said:
Flash the one for mk2. What do you want to do? Odin mk2 will put your phone back to a like new condition. If you flash the no wipe version everything on your internal will need preserved.
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
I'd prefer the no-wipe version, but it doesn't really matter at this point since I have all my stuff backed up and already did a factory reset anyway. I'm just trying to get my phone back to stock so I can do the OTA update.
Again, I know this is probably a real newbie question but when you say "flash the one for mk2", which build file am I supposed to download out of these that are listed in that post you linked me to: VRUAMDK, VRUAME7 or VRUDMI1?
WildKap said:
I'd prefer the no-wipe version, but it doesn't really matter at this point since I have all my stuff backed up and already did a factory reset anyway. I'm just trying to get my phone back to stock so I can do the OTA update.
Again, I know this is probably a real newbie question but when you say "flash the one for mk2", which build file am I supposed to download out of these that are listed in that post you linked me to: VRUAMDK, VRUAME7 or VRUDMI1?
Click to expand...
Click to collapse
If you are already backed up and want to be on mk2 I'd flash the all in one file from here. http://forum.xda-developers.com/showthread.php?p=49687770. Just extract the.tar file from the .rar file using 7-zip
Sent from my SAMSUNG-SGH-I727
WildKap said:
I'd prefer the no-wipe version, but it doesn't really matter at this point since I have all my stuff backed up and already did a factory reset anyway. I'm just trying to get my phone back to stock so I can do the OTA update.
Again, I know this is probably a real newbie question but when you say "flash the one for mk2", which build file am I supposed to download out of these that are listed in that post you linked me to: VRUAMDK, VRUAME7 or VRUDMI1?
Click to expand...
Click to collapse
The MK2 ODIN images can be found here. Don't try flashing anything earlier than MK2 if you're planning to go to NC5 via OTA.
Kiss root good bye for the foreseeable future once you upgrade to KK.
---------- Post added at 06:54 PM ---------- Previous post was at 06:49 PM ----------
swrght13 said:
I got the OTA to succesfully install after using odin as well. Flashed back to a fully stock rom(mk2) and did a factory reset to remove the "samsung custom" bootscreen. Once that finished, I installed the new OTA
Click to expand...
Click to collapse
You do not have to factory reset to remove the "Custom" screen.
Restore a factory stock image. Boot your phone. Wait an hour or so. Now, reboot. It won't show "Custom" any longer.
You just need to leave the phone running long enough for the scanner to figure out that it's now back to stock.
jd1639 said:
If you are already backed up and want to be on mk2 I'd flash the all in one file from here. http://forum.xda-developers.com/showthread.php?p=49687770. Just extract the.tar file from the .rar file using 7-zip
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Ok, cool. And basically, I'm just booting the phone in ODIN mode and then I'm selecting the .tar file under "PDA" on the app on my computer, pressing start and then that's it?
WildKap said:
Ok, cool. And basically, I'm just booting the phone in ODIN mode and then I'm selecting the .tar file under "PDA" on the app on my computer, pressing start and then that's it?
Click to expand...
Click to collapse
That's correct. Just use the default settings that Odin has
Sent from my SAMSUNG-SGH-I727
jd1639 said:
That's correct. Just use the default settings that Odin has
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Awesome. Thanks so much for your help, dude, I really appreciate it!!:good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:03 AM ----------
jd1639 said:
That's correct. Just use the default settings that Odin has
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
OK, I did everything and am getting a fail message in Odin...any idea why?
It says
<ID:04/004> NAND Write Start!!
<ID:04/004> FAIL! (Auth)
<OSM> All threads completed. (succeeded 0 / failed 1)
Sent from my SM-N910V using XDA Free mobile app
Sorry. The phone is on safestrap. I need to unroot it so they can send it back. The guy at Verizon seen it was rooted. Lol
Sent from my SM-N910V using XDA Free mobile app
peppersu812 said:
Sorry. The phone is on safestrap. I need to unroot it so they can send it back. The guy at Verizon seen it was rooted. Lol
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
odin restore back to either mdk or nc5. You can just do a simple google "odin nc5(or mdk) stock tar xda" on Google for instructions.
Raymondlikesroot said:
odin restore back to either mdk or nc5. You can just do a simple google "odin nc5(or mdk) stock tar xda" on Google for instructions.
Click to expand...
Click to collapse
So I have a mdk2 downgrade file. Does it have to be tar
Sent from my SM-N910V using XDA Free mobile app
peppersu812 said:
So I have a mdk2 downgrade file. Does it have to be tar
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
If you are definitely returning it I would recommend you to flash the nc5 full wipe file on this link
http://forum.xda-developers.com/showthread.php?t=2735172. This will remove root, upgrade your base version to a more current one, and wipe your data. Beware though, if you flash nc5 then you won't be able to get your current mdk version back.
Raymondlikesroot said:
If you are definitely returning it I would recommend you to flash the nc5 full wipe file on this link
http://forum.xda-developers.com/showthread.php?t=2735172. This will remove root, upgrade your base version to a more current one, and wipe your data. Beware though, if you flash nc5 then you won't be able to get your current mdk version back.
Click to expand...
Click to collapse
Yea it's definitely going back for sure. The guy at Verizon is just waiting on me to unroot it so we can swap it out for a referbished one for my father in law. Thanks for the help though. Highly appreciated bro.
Sent from my SM-N910V using XDA Free mobile app
peppersu812 said:
Yea it's definitely going back for sure. The guy at Verizon is just waiting on me to unroot it so we can swap it out for a referbished one for my father in law. Thanks for the help though. Highly appreciated bro.
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
my pleasure.
Very much the same problem...
Son is up for renewal and was going to trade his verizon s4 in for the s5 this friday but, cant use ODIN or anything else to get it to take
He had been using the hyperdrive aroma rom and the phone was perfect (we havent upgraded to the latest rom, think he was on 17?) and the phone was fine
only reason we were going to take it back to stock was to trade it in.
Have tried to use various methods (ODIN) on this forum and all have failed.
This is a 32Gb S4 if that makes any difference
The latest was trying to use the Verizon SCH-I545 4.2.2 562219 Stock Restore file and it fails everytime
Have used two different computers, 2 different usb cords (wife has one as well) and various versions of ODIN and tar files...all fail
best I can tell is the custom recovery is gone...however I can get into ASR but, all end in fails.
What am i missing here?
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> ‹¦UœQ
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tarheelbuc said:
Son is up for renewal and was going to trade his verizon s4 in for the s5 this friday but, cant use ODIN or anything else to get it to take
He had been using the hyperdrive aroma rom and the phone was perfect (we havent upgraded to the latest rom, think he was on 17?) and the phone was fine
only reason we were going to take it back to stock was to trade it in.
Have tried to use various methods (ODIN) on this forum and all have failed.
This is a 32Gb S4 if that makes any difference
The latest was trying to use the Verizon SCH-I545 4.2.2 562219 Stock Restore file and it fails everytime
Have used two different computers, 2 different usb cords (wife has one as well) and various versions of ODIN and tar files...all fail
best I can tell is the custom recovery is gone...however I can get into ASR but, all end in fails.
What am i missing here?
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> ‹¦UœQ
<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
Assuming you have good downloads, what version (s) of Odin have you tried? Did you install the correct Samsung drivers? Is USB debugging turned on under settings/more/about phone/developer options? Do you have anti-virus running/active?
Sent from my GT-I9505 using XDA Free mobile app
liljoe727 said:
Assuming you have good downloads, what version (s) of Odin have you tried? Did you install the correct Samsung drivers? Is USB debugging turned on under settings/more/about phone/developer options? Do you have anti-virus running/active?
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
I have tried ODIN 1.85. 3.09 and 3.07 that I know of, may have used some others yesterday not sure..wasted about an entire day trying to fix this screwup.
Yes, installed the drivers a couple of times and also tried to use Kies
I cant get into the settings to check the usb debugging at this time because the phone wont boot after the initial flash yesterday
No av running on the computers I was using during the work
I have tried several of the guides on this site multiple times and nothing is working.
I dont know a whole lot about this stuff, usually I get brought in when he screws something up or its not working but, this one is on me trying to take it back to stock so we can trade it in this Friday....so, whatever was done wrong, I did it this time! lol
Couple things that might help someone who understands this more
If I just turn the phone on to "normal boot"..goes to yellow triangle
ODIN mode
name schi545
cur binary samsung official
sys status custom
knox lock 0x0
knox warranty void 0x0
csb-config-lsb 0x30
write protection enable
emmc burst mode enabled
----------------------------------------------------------------------
going into recovery
i get the custom os can cause critical problems
vol up continue
vol down restart
yellow triangle
name schi545
cur binary samsung official
sys status custom
knox lock 0x0
knox warranty void 0x0
csb-config-lsb 0x30
write protection enable
emmc burst mode enabled
________________________________
Not sure whether that will help or not and again, this is a 32gb S4, not sure whether that matters or not
tarheelbuc said:
I have tried ODIN 1.85. 3.09 and 3.07 that I know of, may have used some others yesterday not sure..wasted about an entire day trying to fix this screwup.
Yes, installed the drivers a couple of times and also tried to use Kies
I cant get into the settings to check the usb debugging at this time because the phone wont boot after the initial flash yesterday
No av running on the computers I was using during the work
I have tried several of the guides on this site multiple times and nothing is working.
I dont know a whole lot about this stuff, usually I get brought in when he screws something up or its not working but, this one is on me trying to take it back to stock so we can trade it in this Friday....so, whatever was done wrong, I did it this time! lol
Couple things that might help someone who understands this more
If I just turn the phone on to "normal boot"..goes to yellow triangle
ODIN mode
name schi545
cur binary samsung official
sys status custom
knox lock 0x0
knox warranty void 0x0
csb-config-lsb 0x30
write protection enable
emmc burst mode enabled
----------------------------------------------------------------------
going into recovery
i get the custom os can cause critical problems
vol up continue
vol down restart
yellow triangle
name schi545
cur binary samsung official
sys status custom
knox lock 0x0
knox warranty void 0x0
csb-config-lsb 0x30
write protection enable
emmc burst mode enabled
________________________________
Not sure whether that will help or not and again, this is a 32gb S4, not sure whether that matters or not
Click to expand...
Click to collapse
So you have not gotten a screen that says "Downloading do not turn off target"?
Sent from my GT-I9505 using XDA Free mobile app
Oh yes, I can get to that screen but when trying to load the files with ODIN it fails.
tarheelbuc said:
Oh yes, I can get to that screen but when trying to load the files with ODIN it fails.
Click to expand...
Click to collapse
You said you were using the 4.2.2 files, this is the firmware version you were on?
Sent from my GT-I9505 using XDA Free mobile app
I am pretty sure thats what the phone came (4.2.2) with when he/we first got it.
Since then, we upgraded it to the hyperdrive rom and I think, not sure, he was on release 17
So, I believe that requires the phone to be at 4.4.2 but I may be mistaken
tarheelbuc said:
I am pretty sure thats what the phone came (4.2.2) with when he/we first got it.
Since then, we upgraded it to the hyperdrive rom and I think, not sure, he was on release 17
So, I believe that requires the phone to be at 4.4.2 but I may be mistaken
Click to expand...
Click to collapse
You can still run Hyperdrive if you are on 4.2.2 in fact, you can flash just about anything because of the loki exploit on the MDK bootloader. Did you use the files found here http://forum.xda-developers.com/showthread.php?t=2751461 and follow the instructions exactly as they are written?
Sent from my Empty Galaxy
Yes, thats actually the first thread I was following to get it done and it failed right off the bat.
Then I was wondering if I had the wrong thread or files so, looked elsewhere.
Phone was working perfectly before I decided to do this and that is where it started..downhill sense then.
I probably did that thread 3-4 times..all ending the same way but I can try it again if you think it will do any good
---------- Post added at 09:30 PM ---------- Previous post was at 09:14 PM ----------
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRUAMDK_NoWipe.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> NON-HLOS.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
--------------------------------------------------------------------
I also tried to run the VRUFNC5 Full-Wipe Verizon SCH-I545 4.2.2 562219 Stock Restore.tar.md5 in 3.07
and now its crashing ODIN..didnt do that before.
Runtime error application has requested the Runtime to terminate it in an unusual way
The VRUFNC5 file might not work if mine is a VRUAMDK? just a guess?
tarheelbuc said:
Yes, thats actually the first thread I was following to get it done and it failed right off the bat.
Then I was wondering if I had the wrong thread or files so, looked elsewhere.
Phone was working perfectly before I decided to do this and that is where it started..downhill sense then.
I probably did that thread 3-4 times..all ending the same way but I can try it again if you think it will do any good
---------- Post added at 09:30 PM ---------- Previous post was at 09:14 PM ----------
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
VRUAMDK_NoWipe.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
NON-HLOS.bin
NAND Write Start!!
aboot.mbn
FAIL! (Auth)
All threads completed. (succeed 0 / failed 1)
--------------------------------------------------------------------
I also tried to run the VRUFNC5 Full-Wipe Verizon SCH-I545 4.2.2 562219 Stock Restore.tar.md5 in 3.07
and now its crashing ODIN..didnt do that before.
Runtime error application has requested the Runtime to terminate it in an unusual way
The VRUFNC5 file might not work if mine is a VRUAMDK? just a guess?
Click to expand...
Click to collapse
You are sure you are on MDK and 4.2.2?
[Edit]: The reason I ask is because it is failing at aboot.mbn which leads me to believe you are not on MDK. To be on MDK would mean you bought the phone in like the very first week of its release and never took an OTA, is this the case?
Sent from my Empty Galaxy
positive on the mdk...pretty sure on the 4.2.2 but, I cannot be sure at this moment
to my knowledge, he never did any other upgrades without me but, that might not be true!
Problem is, there is no way I can determine or check that with the phone in the condition it is right now...correct?
tarheelbuc said:
positive on the mdk...pretty sure on the 4.2.2 but, I cannot be sure at this moment
to my knowledge, he never did any other upgrades without me but, that might not be true!
Problem is, there is no way I can determine or check that with the phone in the condition it is right now...correct?
Click to expand...
Click to collapse
If you are positive you are on MDK then you're on 4.2.2 as well and no, the NC5 files won't work. Try booting into recovery and wiping cache and wipe data/factory reset then try booting into download mode and running Odin again. Or if you have a backup in zip format on your external SD card you could try side loading that through recovery mode just select "install from zip" or whatever it says.
Sent from my Empty Galaxy
Going backwards now...YESTERDAY after this issue arose, I was still able to get into the ASR..today after trying to flash it again, not happening
NOW, yesllow triangle..firmware encountered an issue, please select recovery mode in Kies and try again
Of course trying that with Kies, it doesnt recognize the phone now.
Am I fighting a losing battle here? lol