[ODIN][TAR] VRUEMK2 Emergency and No-Wipe Odin tars - Verizon Samsung Galaxy S 4

DO NOT FLASH IF YOUR ON MDK AND WISH TO RETAIN YOUR CUSTOM RECOVERY! THIS WILL REMOVE THE LOKI EXPLOIT!
This is a new update for SCH-1545 taking users to VRUEMK2. This is the stock factory image. Also, If you need to go back to stock for whatever reason and this Odin tar doesn't work I suggest using the VRUEMJ7 factory image instead. VRUAMDK, VRUAME7, and VRUEMJ7 stock Odin tars contained 14 partitions over which they would write over, VRUDMI1 wrote over 13 partitions, VRUEMJ7 also contained a pit file. However I've included both the full-wipe and no-wipe Odin tar.md5's for VRUEMK2 and in the no-wipe VRUEMK2, only 12 partitions are wrote over because it doesn’t contain persdata.img.ext4 or sbl1.mbn. The full-wipe (KIES factory image) VRUEMK2 Odin tar contains 14 partitions and its own PIT file as well and will completely wipe your device and re-partition it to factory stock
For the sake of simplicity, I've also included a mirror to the MJ7 "emergency" Full-wipe Odin tar as well. Download it here
Also incase you have MDK here's a link to the full-wipe Odin tar Download it here
@Tomsgt made a great video of the process that can be viewed here
Information:
1. ROOT METHOD here
2. Download Odin 3.09 here (Note: Bootloader = BL , PDA = AP , Phone = CP)
Download: No-Wipe SCH-I545_VZW_1_20131212083410_49ap8w990g.zip
Download: Mirror
MD5: 7C2213EC9542D61B9A6CB164DC0CDB7B
Download: Full-Wipe SCH-I545_VZW_1_20131212083410_mwx72ql56g_fac.zip
Download: Mirror
MD5: c1b8a30d6071f591cc43e85dfc2dd91b
Directions:
No-Wipe
1. Unzip the file and you should have a tar.md5
2. Select the tar.md5 in Odin under PDA (or AP if using Odin 3.09) and keep Odin's default settings
3. Click start and wait for it to say Pass!
Full Wipe ( AKA Emeregency Repair)
1. Unzip the file and you should have a ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
2. Select the tar.md5 in Odin under PDA (or AP if using Odin 3.09) and keep Odin's default settings
3. Extract the PIT file from your phone or Odin tar, also I've uploaded it here just in case.
4. Put the PIT file in PIT and load the the Odin tar.md5 in PDA (or AP if using Odin 3.09) then click start.

Edit:
12/21/13: Included both full-wipe factory image and no-wipe VRUEMK2 Odin tar.md5's

The DL is incredible slow for some reason. Rate of like 50kbps. Everything else on my connection is fine

Topsnake said:
The DL is incredible slow for some reason. Rate of like 50kbps. Everything else on my connection is fine
Click to expand...
Click to collapse
Thanks that reminded me I totally forgot to link the full-wipe main download link lol
Sent from my SCH-I545 using XDA Premium 4 mobile app

Helping reduce the amount of questions asking where the MK2 odin tar thread is.
tl;dr Bumping the thread
Tip: the first result from Googling "vruemk2 odin tar" just so happens to be the correct one.
Sent from my SCH-I545 using XDA Premium 4 mobile app

I just sold my Note 3 and went back to an S4. Thanks for posting. Now, I can root and get back to normal haha : )
Sent from my SCH-I545 using XDA Premium 4 mobile app

What are the dangers of using the no-wipe file? I'm doing this for my gf's phone so I'm not used to the S4, sorry. The phone is currently on ME7, I had previously rooted it and de-bloated the stock rom. I've already unrooted in preparation for updating to MK2. If I can preserve her files in the process that would be great but I'm not sure if my having de-bloated some of the unnecessary system apps will cause any problems. Thanks.

FastEddie422 said:
What are the dangers of using the no-wipe file? I'm doing this for my gf's phone so I'm not used to the S4, sorry. The phone is currently on ME7, I had previously rooted it and de-bloated the stock rom. I've already unrooted in preparation for updating to MK2. If I can preserve her files in the process that would be great but I'm not sure if my having de-bloated some of the unnecessary system apps will cause any problems. Thanks.
Click to expand...
Click to collapse
No-wipe reinstalls the contents of the stock ROM, but does not delete your persistent data or applications. Anything that you deleted from the stock ROM is restored and anything you "froze" is defrosted. In most cases, that's enough to let the OTAs complete.
Dangers? If you unplug during rooting, lose power, or something else happens, the flash can fail. Those circumstances are usually recoverable because it's damn near impossible to overwrite the bootloader so there's always something there to help you recover from an oops.

Worked awesome, thank you

I was directed here from this post http://forum.xda-developers.com/showthread.php?t=2578569&page=2
I did everything for the no-wipe but I got a FAIL. What could I have done wrong?
Thanks,
Derek

dbinnc said:
I was directed here from this post http://forum.xda-developers.com/showthread.php?t=2578569&page=2
I did everything for the no-wipe but I got a FAIL. What could I have done wrong?
Thanks,
Derek
Click to expand...
Click to collapse
Where does it fail at? Download Odin 3.07 then try again also make sure the md5 is right. Otherwise try the full wipe or MJ7 no wipe/full wipe
Sent from my SCH-I545 using XDA Premium 4 mobile app

[/COLOR said:
[/FONT][/SIZE][/SIZE]
Full Wipe ( AKA Emeregency Repair)
1. Unzip the file and you should have a ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
2. Select the tar.md5 in Odin under PDA (or AP if using Odin 3.09) and keep Odin's default settings
3. Extract the PIT file from your phone or Odin tar, also I've uploaded it here just in case.
4. Put the PIT file in PIT and load the the Odin tar.md5 in PDA (or AP if using Odin 3.09) then click start.
5. If all else fails read below...
Alternate Emeregency Repair READ:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Download this 1545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship.zip
If the full wipe fails, but generally this download wont be needed unless your partitions are messed up. The full wipe above should be all thats needed for most if not then download this odin tar Its not the same Odin tar you downloaded earlier. Extract the zip and there will be 4 tar.md5 files and a PIT file. Put them in the appropriate areas in Odin 3.09 and if it goes through and tries to reboot, don't let it reboot the /system instead make it boot to recovery first and wipe cache/factory reset then let it boot up.
This will work better if done with Heimdall. Google how to use Heimdall because I use Heimdall on Linux and don't know how Heimdall works on Windows.
BP AP CP CSC CSC_PIT
Click to expand...
Click to collapse
This will not work for me. :/ The PIT file uploads to Odin fine but when I try to bring in any of the other files, it gives me an "invalid binary" on each one. Bad download?

nickknaack said:
This will not work for me. :/ The PIT file uploads to Odin fine but when I try to bring in any of the other files, it gives me an "invalid binary" on each one. Bad download?
Click to expand...
Click to collapse
I'm probably going to delete the alternative emergency repair directions because it requires you to use Heimdall and to extract the files one by one. The normal full wipe didn't work?
Sent from my SCH-I545 using XDA Premium 4 mobile app

Surge1223 said:
I'm probably going to delete the alternative emergency repair directions because it requires you to use Heimdall and to extract the files one by one. The normal full wipe didn't work?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay, tried the full wipe and it worked great! Thanks!

This worked to get me to mk2 from me7 without a hitch. Thank you muchly.
Sent from my SCH-I545 using XDA Premium 4 mobile app

Edit: Fixed. Just kept trying. Tried all the way back to ME7. Did MK2 before a bunch of times, maybe 5. Finally, on that last try, it made it past system. Woot!
---------
I could use some assistance. My friend's VZW S4 was rooted on MI7. I had done that for him. He wanted to update, so I downloaded the MK2 no-wipe odin file from this thread. I checked the MD5 on the zip (it was good), extracted the tar file, and attempted to flash. At first, Odin kept telling me the phone was being disconnected/reconnected. The cable was good, but it failed regardless. On further attempts to flash the tar, it would get to the end of the system img and fail. I was trying to go from MI7 to MK2, should it shouldn't be incompatible. The MD5 was good. I tried to re-odin MI7, but it's failing with " [auth] ". I'll try going all the way back to ME7 and OTA'ing up to MK2 THEN re-rooting, but in the mean time: how could I have avoided this?

So I have the full wipe ODIN downloaded and I'm using v3.09.. Do I still need to extract the .pit file if I downloaded it seperately or can I just load the .pit file and the .tar file and be fine to start the process?
EDIT: I answered that myself. Process went flawless and my phone went from unusable to working again.

Nice!
Worked great Surge! Thank you for all that you do for this device, it is appreciated!

Do I put my phone into recovery or download mode to odin the fullwipe?
Edit: Nevermind, looks like download mode, thanks for the post! Fixed my phone

No-Wipe
Hi Surge1223
I had a problem with my S4 MK2 SS so I needed to do the No-Wipe Odin.
now everything went fine but when the OS started it keeps restarting and it stops at the Verizon animation screen.
What do you think is the problem?
Thank you.

Related

[Q] Brick: Much searching, but solution not found.

Hi,
With the semester over, I planned on tweaking my S4.
Before I began: MDK, Rooted Stock with Custom Recovery
Right now: Will boot only to Samsung Screen.
I wanted to restore everything to stock factory outta-the-box settings.
First: Flashed with Odin 3.07 the SCH-I545_MDK_562219_Stock_Restore.tar.md5.gz on rwilco repository
Failed, Reboot shows Exclamation Point. Unfortunately I didn't record what the phone or odin said.
I then gave the ME7 firmware a shot, giving me the same result.
In a spate of annoyance, I began firing all cylinders, attempting MIJ, ME7, MJ1 stock firmwares, all giving me the same response. I tried any. (heck what they say about too little sleep... too MUCH sleep is bad for ya )
I get the following messages now when I attempt to ODIN things:
[Odin version, files flashed, Odin Response, Phone response, Restart result]
1. ODIN 3.09, with pit file and MJ7 Firmware: "System.img.ext4 fail" Start [224, 1440] Bar [240, 1440]. Restarting gives exclamation point
2. Odin 3.09, Just Pit file: "Repartition operation failed", Start [224, 1440] Secure Check Fail: Pit. Restart = Samsung Screen
3. Odin 3.07: Just pit file: Res OK (worked) = Samsung Screen
4. Odin 3.07: Pit file and COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5: "Aboot.mbn fail" start [224, 1440] Secure check fail: Pit, SW Rev Check Fail: Fused 5, Binary 3 = Exclamation Point
5. Odin 3.07, COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 only: "Aboot.mbn Fail:AUTH" Start [224, 1440] SW Rev Check Fail: Fused 5, Binary 3 = Exclamation point
6. Odin 3.07, Pit file and ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5: "System img.ext Fail" Start [224, 1440] Bar [240, 1440] = Exclamation
7. Odin 3.07: MDK Kernel only; "NAND write start, Fail (Auth) Start [224, 1440] Secure Magiccode chaco fail: Boot = Samsung screen
8. Same as 7 with the ME7 kernel.
I have also tried the .exe "one touch" file found on rwilco repository: the phone says "Secure Magiccode Check Fail: Recovery"
Am I SOL? Anything to try? Kies does not connect to the phone either. I reinstalled my windows 7 VM, and am doing it on the new one to make sure it wasn't something funky on the old one.
Try this. This is a last resort Odin file. http://forum.xda-developers.com/showthread.php?t=2507253
I had the same issues after a botched upgrade attempt from me7 to mj7.
Thanks to openyoureyes for this one.
Sent from my SCH-I545 using xda app-developers app
I cant believe you didnt ask what to do, youve now locked down your bootloader.
1. Download MJ7 pit
MJ7 pit
2. Flash this in Odin after unzipping
MJ7 full wipe
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
I cant believe you didnt ask what to do, youve now locked down your bootloader.
1. Download MJ7 pit
2. Flash this in Odin after unzipping
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Result:
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On Phone: Start[224,1440] ; BAR [240,1440]
I did this on Odin 3.09, should I be using this Odin?
Whats the md5 of the odin tar? Make sure you put pit in pit and tar.md5 in ap. If that doesnt work download the MK2 full wipe. If that doesnt work I have one more solution so let me know how it goes
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Whats the md5 of the odin tar? Make sure you put pit in pit and tar.md5 in ap. If that doesnt work download the MK2 full wipe. If that doesnt work I have one more solution so let me know how it goes
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will download the MK2 full wipe now. My MD5 for the MJ7 is 406438dc1e3dd51369c25b1057874685
Surge1223 said:
Whats the md5 of the odin tar? Make sure you put pit in pit and tar.md5 in ap. If that doesnt work download the MK2 full wipe. If that doesnt work I have one more solution so let me know how it goes
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The MK2 tar file result:
Re-partition operation failed
Secure Check Fail: Pit
I tried it after putting the mj7 pit file in fresh first.
After trying this on Odin 3.09, I gave it a go on Odin 3.07. The result was slightly different: on modem.bin there was a fail, and the phone said Secure Check Fail: Pit.
The pit file is the same for both mj7 and mk2
Sent from my SCH-I545 using XDA Premium 4 mobile app
I gave the MK2 a shot- no dice. Gives me
START 224,1440; BAR 240,1440
and
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed
Is my goose cooked?
No reboot recovery and wipe cache. Then download heimdall
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
No reboot recovery and wipe cache. Then download heimdall
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got it. Now, according to the README, Heimdall wants a .gz'ed file- should I zip up your MK2 file and use that?
oocytecryo said:
Got it. Now, according to the README, Heimdall wants a .gz'ed file- should I zip up your MK2 file and use that?
Click to expand...
Click to collapse
Confirm the ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 is valid then delete the ".md5" from the end of the tar.md5 and gzip it (you can use 7zip or winrar)
I don't remember if you have to manually create a firmware.xml file and add partitions one by one on Windows or not but if you get an error then manually create a package to flash using heimdalls built in tools.
Sent from my SCH-I545 using XDA Premium 4 mobile app
oocytecryo said:
Hi,
With the semester over, I planned on tweaking my S4.
Before I began: MDK, Rooted Stock with Custom Recovery
Right now: Will boot only to Samsung Screen.
I wanted to restore everything to stock factory outta-the-box settings.
First: Flashed with Odin 3.07 the SCH-I545_MDK_562219_Stock_Restore.tar.md5.gz on rwilco repository
Failed, Reboot shows Exclamation Point. Unfortunately I didn't record what the phone or odin said.
I then gave the ME7 firmware a shot, giving me the same result.
In a spate of annoyance, I began firing all cylinders, attempting MIJ, ME7, MJ1 stock firmwares, all giving me the same response. I tried any. (heck what they say about too little sleep... too MUCH sleep is bad for ya )
I get the following messages now when I attempt to ODIN things:
[Odin version, files flashed, Odin Response, Phone response, Restart result]
1. ODIN 3.09, with pit file and MJ7 Firmware: "System.img.ext4 fail" Start [224, 1440] Bar [240, 1440]. Restarting gives exclamation point
2. Odin 3.09, Just Pit file: "Repartition operation failed", Start [224, 1440] Secure Check Fail: Pit. Restart = Samsung Screen
3. Odin 3.07: Just pit file: Res OK (worked) = Samsung Screen
4. Odin 3.07: Pit file and COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5: "Aboot.mbn fail" start [224, 1440] Secure check fail: Pit, SW Rev Check Fail: Fused 5, Binary 3 = Exclamation Point
5. Odin 3.07, COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 only: "Aboot.mbn Fail:AUTH" Start [224, 1440] SW Rev Check Fail: Fused 5, Binary 3 = Exclamation point
6. Odin 3.07, Pit file and ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5: "System img.ext Fail" Start [224, 1440] Bar [240, 1440] = Exclamation
7. Odin 3.07: MDK Kernel only; "NAND write start, Fail (Auth) Start [224, 1440] Secure Magiccode chaco fail: Boot = Samsung screen
8. Same as 7 with the ME7 kernel.
I have also tried the .exe "one touch" file found on rwilco repository: the phone says "Secure Magiccode Check Fail: Recovery"
Am I SOL? Anything to try? Kies does not connect to the phone either. I reinstalled my windows 7 VM, and am doing it on the new one to make sure it wasn't something funky on the old one.
Click to expand...
Click to collapse
you are toast in going back to mdk.....and the only way to load any rom will be thru safestrap....once you moved from mdk, your bootloader became lockdown
a little reading goes a long way as this has been discuss so many times my head is spinning
Surge1223 said:
Confirm the ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 is valid then delete the ".md5" from the end of the tar.md5 and gzip it (you can use 7zip or winrar)
I don't remember if you have to manually create a firmware.xml file and add partitions one by one on Windows or not but if you get an error then manually create a package to flash using heimdalls built in tools.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, this is downright hilarious if anything- I made the gz of the MK2 tar, and Heimdall didn't like that, so I went to the flash section and stuck all the packages into it, the pit where it belongs, and voila!
Everything is going smoothly until it gets to 100% of "Uploading System". Then, On the screen, I see the progress bar moving beyond it's proper area, and appearing on the opposite side (pac-man style). The text on the phone now says "Invalid percent of drawing download progress bar!" and says it every minute or so, so I have it now bleeding down onto my android download icon!
Any thoughts? I've let the heimdall sit like this (if doesn't seem to have crashed) on system, because I don't want to completely destroy anything.
Damn did you by chance install safestrap ever? Sit tight I'm making you a file to flash
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Damn did you by chance install safestrap ever? Sit tight I'm making you a file to flash
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, I never did.
Slowbalt said:
Try this. This is a last resort Odin file. http://forum.xda-developers.com/showthread.php?t=2507253
I had the same issues after a botched upgrade attempt from me7 to mj7.
Thanks to openyoureyes for this one.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
:laugh: Worked magical for me ! Thanks
oocytecryo said:
No, I never did.
Click to expand...
Click to collapse
Ok download this 1545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship.zip
Its not the same odin tar you downloaded earlier. Extract the zip and there will be 4 tar.md5 files and a pit file. Put them in the appropriate areas in Odin 3.09 and if it goes through and trys to reboot don't let it reboot the /system instead make it boot to recovery first and wipe cache/factory reset then let it boot up.
BP
BP_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Click to expand...
Click to collapse
AP
AP_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Click to expand...
Click to collapse
CP
CP_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Click to expand...
Click to collapse
CSC
CSC_VZW_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Click to expand...
Click to collapse
PIT
MSM8690.pit
Click to expand...
Click to collapse
Surge1223 said:
Ok download this 1545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship.zip
Its not the same odin tar you downloaded earlier. Extract the zip and there will be 4 tar.md5 files and a pit file. Put them in the appropriate areas in Odin 3.09 and if it goes through and trys to reboot don't let it reboot the /system instead make it boot to recovery first and wipe cache/factory reset then let it boot up.
Merry Christmas! Do you have the md5s for the individual files? The MD5 for the zip file checks out, but Odin says each of the files inside has an invalid binary. Am I missing something silly?
Edit: I removed the .md5 so that each were tar files, and tired that with Odin. Odin crashes and windows gives me the following information: Problem Event Name: APPCRASH
Application Name: Odin3 v3.09.exe
Application Version: 2013.5.24.1
Application Timestamp: 519f55ae
Fault Module Name: Odin3 v3.09.exe
Fault Module Version: 2013.5.24.1
Fault Module Timestamp: 519f55ae
Exception Code: 40000015
Exception Offset: 00133964
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 308b
Additional Information 2: 308ba88846fcea477c0aef5947bf596c
Additional Information 3: 3b65
Additional Information 4: 3b65ba98d7fdf612af8e0a1ef1df3acc
Click to expand...
Click to collapse
I'm MDK on the GS4 and believe me i knew about the whole Verizon/At&t/TMO long time ago (smarter than the average near and able to laugh at people when they do do things like that) ok so my issue i tried updating my recovery earlier to philz 6.08 from just CWM 6.0.44 (?). It soft bricked my phone. I just spent 7 hours getting it back to operational order. I tried everything under the sun, u name it i probably did it, but i kept with Verizon mdk packages only. Trying to find a stock image of MDK is impossible to say the least. Good news though. its up and running again only issue i lost root
Used the no wipe as well as an emergency root with wipe. So needless to say my system was wiped and re partitioned. The whole 9.
Root the first time was simple and maybe took 20 minutes. Now i cant get motochopper or any other exploit to to work. Phone "see's" that a program is trying to get access but does not allow me to accept it, only offers to reboot now or later. Help a man out here.. I'm still on mdk just cant get root back. yes i check usb debug even toggled it a couple times. Verify apps unchecked and unknown checked.. Dang Stock is not good, bur my phone is functional.
I do I have an old backup when root was woeking 9erfectly n the correct pit file. Anyway to use that to flash in Odin?
Sent from my SCH-I545 using Tapatalk

Failed 4.3 Odin

I downloaded the full 1.7GB N2 MJ9 md5 for odin, after I flashed the phone would just flash NOTE 2 logo over and over.I tried to re-flash it again in odin but it just fails, and now in download mode I see 4.3 stuff.
I keep trying to use odin 3.09 to reflash stock but it fails at NAND WRITE START
nxneko said:
I downloaded the full 1.7GB N2 MJ9 md5 for odin, after I flashed the phone would just flash NOTE 2 logo over and over.I tried to re-flash it again in odin but it just fails, and now in download mode I see 4.3 stuff.
I keep trying to use odin 3.09 to reflash stock but it fails at NAND WRITE START
Click to expand...
Click to collapse
Mine did this exact same thing. I later found out that you have to run Odin again and only use a pit file. Basically bring up Odin, put your phone into Odin mode, connect it, on the right hand side of the Odin screen instead of clicking PDA, click PIT. Then point to your file and click start. The file name is sch-I605-16gb.pit. Only thing is that I am unsure where I downloaded it from. There is a video on youtube on that describes exactly how to do this and I think the links to the files are on that video.
StricIX said:
Mine did this exact same thing. I later found out that you have to run Odin again and only use a pit file. Basically bring up Odin, put your phone into Odin mode, connect it, on the right hand side of the Odin screen instead of clicking PDA, click PIT. Then point to your file and click start. The file name is sch-I605-16gb.pit. Only thing is that I am unsure where I downloaded it from. There is a video on youtube on that describes exactly how to do this and I think the links to the files are on that video.
Click to expand...
Click to collapse
the pit file failed, too.
Verizons SUA ended up working with restoring device.
I got the same issue. my phone was rooted with TWRP 2.6.3.2 and flashed to customized MJ9 in this thread, http://forum.xda-developers.com/showthread.php?t=2578458&page=14
Later I would like to restore to factory default, so downloaded this firmware http://terafile.co/2146204d7383 and flashed using odin. the flash was successful, however, after it finished, it started to have the exact problem as you described.
nxneko said:
I downloaded the full 1.7GB N2 MJ9 md5 for odin, after I flashed the phone would just flash NOTE 2 logo over and over.I tried to re-flash it again in odin but it just fails, and now in download mode I see 4.3 stuff.
I keep trying to use odin 3.09 to reflash stock but it fails at NAND WRITE START
Click to expand...
Click to collapse
---------- Post added at 03:03 AM ---------- Previous post was at 02:26 AM ----------
nxneko said:
I downloaded the full 1.7GB N2 MJ9 md5 for odin, after I flashed the phone would just flash NOTE 2 logo over and over.I tried to re-flash it again in odin but it just fails, and now in download mode I see 4.3 stuff.
I keep trying to use odin 3.09 to reflash stock but it fails at NAND WRITE START
Click to expand...
Click to collapse
I just did Section 1B according to this thread:
http://forum.xda-developers.com/showthread.php?t=2024207
Worked like a charm
nxneko said:
I downloaded the full 1.7GB N2 MJ9 md5 for odin, after I flashed the phone would just flash NOTE 2 logo over and over.I tried to re-flash it again in odin but it just fails, and now in download mode I see 4.3 stuff.
I keep trying to use odin 3.09 to reflash stock but it fails at NAND WRITE START
Click to expand...
Click to collapse
nxneko said:
the pit file failed, too.
Verizons SUA ended up working with restoring device.
Click to expand...
Click to collapse
Did you take 4.4.2 OTA?
Well have you tried rebooting into stock recovery(UP BUTTON, HOME BUTTON, POWER) and doing a factory reset..then reboot?
You should always flash a image or tar in Odin WITH the pit file..bc if no pit the image could end up anywhere(rare)..
So this is what I would do..
pull battery
un plug phone
reboot into Download Mode
plug phone into different USB port
ODIN see it?
If so good!
Try to reflash WITH pit file

deleted media folder on S4, Cant get to Recovery

So, I recently accidentally deleted my /media/ folder and now when trying to boot to recovery it reboot, but will still go into Download mode. How can I fix this? I'm trying to unroot and update, I'm on ME7 - Verizon. Can I use ODIN to fix this?
Odin should do the trick, and you should odin to nc5, it has alot of great roms for safestrap. Just use odin 3.07 and above, and download the full wipe .tar of what version you want, and odin back to stock
bamige1 said:
Odin should do the trick, and you should odin to nc5, it has alot of great roms for safestrap. Just use odin 3.07 and above, and download the full wipe .tar of what version you want, and odin back to stock
Click to expand...
Click to collapse
I was able to get ODIN to do what I wanted, but when I tried to flash NG6 over NC5 to downgrade, it didn't let me, and gave me the fused 6 binary 5 issue. How do I fix this?
I think this could possibly help. Just follow the no wipe instructions and you should be good. http://forum.xda-developers.com/galaxy-s4-verizon/general/downgrade-ng6-to-nc5-t2910933

Lollipop Pre-Rooted TWRP Flash

What we have hare is a TWRP flashable of Lollipop that is pre-rooted, and will only overwrite the "System," "Boot," and "Modem" partitions. I performed a factory reset before performing the backup anyways. It will not overwrite the EFS, data, or cache partitions, so previously installed apps might stay, but no promises, so be prepared to lose all your apps. If your phone doesn't act right, perform a factory restore and wipe your Cache/Dalvik. It is recommended to do a full backup before flashing this image.
To install, install TWRP (if not already), and un7zip (7-zip on PC or ES File Explorer on Android) the folder from the TWRP file link into:
"/TWRP/backups/<device serial number>/" (The serial numbered folder will be present if a backup of something has been made from TWRP.)
Then boot into TWRP and 'Restore' "Sprint Note 3 Lollipop Prerooted."
You can Odin the TWRP file from here:
http://dl.twrp.me/hltespr/twrp-2.8.6.1-hltespr-4.4.img.tar
And here is the TWRP file:
Sprint Note 3 Lollipop prerooted.7z
https://drive.google.com/open?id=0B2iEgzRTFjrQWVVzSkdUMlVMUkk&authuser=0
I forgot to do this before making the image, but this app fixes SD write permissions no problem:
https://play.google.com/store/apps/...sdfix&pcampaignid=APPU_1_yNg1VcDzJLTasAS274Fo
I don't know how much bandwidth Google will allow before flipping people the bird. If this happens, let me know and I'll get another method of sharing worked out.
This looks like it will get me to the latest firmware/modem easily, but don't want to be the Guinea Pig. Anyone else have success with this?
mhoepfin said:
This looks like it will get me to the latest firmware/modem easily, but don't want to be the Guinea Pig. Anyone else have success with this?
Click to expand...
Click to collapse
I'll try this today, thank you!
I flashed the boot and the modem, but baseband still shows as NK4 for some reason
leond said:
I flashed the boot and the modem, but baseband still shows as NK4 for some reason
Click to expand...
Click to collapse
Did you try flashing the System as well? I know mine is OC5
Greaper88 said:
Did you try flashing the System as well? I know mine is OC5
Click to expand...
Click to collapse
As far as my knowledge goes , you cant flash a modem via recovery , no matter what
It has to be done via odin .
so its better to restore the image and then straight away boot in download mode and flash the modem via odin ( if there is available an ODIN image for the OC5 modem ) and then do a reboot
But the rom will work fine with NK4 provided the firmware version is the same that is NK4 as any lower bootloader wont let it boot after the first Reboot.
lord dredd said:
As far as my knowledge goes , you cant flash a modem via recovery , no matter what
It has to be done via odin .
so its better to restore the image and then straight away boot in download mode and flash the modem via odin ( if there is available an ODIN image for the OC5 modem ) and then do a reboot
But the rom will work fine with NK4 provided the firmware version is the same that is NK4 as any lower bootloader wont let it boot after the first Reboot.
Click to expand...
Click to collapse
OK, so how does the ota update flash the modem?
And basically, as long as the bootloader is compatible, it doesn't matter too much?
Greaper88 said:
OK, so how does the ota update flash the modem?
And basically, as long as the bootloader is compatible, it doesn't matter too much?
Click to expand...
Click to collapse
I was referring to the custom recovery. I dont know how ota does that. Butvi am more than 100 % sure that you can't flash the modem with a custom recovery . its a well known fact now .
Sent from THE NOTE 3 .. size matters and so does the battery backup .....
lord dredd said:
I was referring to the custom recovery. I dont know how ota does that. Butvi am more than 100 % sure that you can't flash the modem with a custom recovery . its a well known fact now .
Sent from THE NOTE 3 .. size matters and so does the battery backup .....
Click to expand...
Click to collapse
Actually that is not true. You can flash the modem.bin in recovery. You need the devblock/partition and then add the script to the updater in the zip. You'll need the correct binary as well in order to flash it but you have that already.
I was just looking for some stock note 3 lollipop framework & apk's for some work i'm doing and come upon this thread. I thought i'd give my input on the modem flashable thing while i was here.
tx_dbs_tx said:
Actually that is not true. You can flash the modem.bin in recovery. You need the devblock/partition and then add the script to the updater in the zip. You'll need the correct binary as well in order to flash it but you have that already.
.
Click to expand...
Click to collapse
Can you please elaborate on this? I was looking for TWRP flashable modem for note 3 and did not find one neither for Sprint nor for any other carrier.
I tried to create an ODIN flashable modem. It looks like modem.emmc.win has the same format as modem.bin (at least the same header and similar size) so i just renamed modem.emmc.win to modem.bin then used:
c:\cygwin420\bin\tar -H ustar -c modem.bin > modem.tar
c:\cygwin420\bin\md5sum -t modem.tar >> modem.tar
copy modem.tar modem.tar.md5
info came from this guide: [TUTORIAL] How to repackage ODIN files and then tried to flash resulting file via ODIN , but that failes with : "secure check fail modem"
leond said:
Can you please elaborate on this? I was looking for TWRP flashable modem for note 3 and did not find one neither for Sprint nor for any other carrier.
I tried to create an ODIN flashable modem. It looks like modem.emmc.win has the same format as modem.bin (at least the same header and similar size) so i just renamed modem.emmc.win to modem.bin then used:
c:\cygwin420\bin\tar -H ustar -c modem.bin > modem.tar
c:\cygwin420\bin\md5sum -t modem.tar >> modem.tar
copy modem.tar modem.tar.md5
info came from this guide: [TUTORIAL] How to repackage ODIN files and then tried to flash resulting file via ODIN , but that failes with : "secure check fail modem"
Click to expand...
Click to collapse
I don't know the devblock for the modem on the Note 3 but once you get that you can add a line to your updater-script inside the zip and it will flash the modem in recovery.
The line will be similar to this...
package_extract_file("modem.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem"); Do some searching and maybe somebody has already pulled the devblocks for dev/chef's to use as references. You can make an odin flashable mode but that's a totally different beast. The point of my post was that you CAN do it in recovery easily.
Edit: Here is the mount point for the Sprint note 3 modem...
/dev/block/mmcblk0p2
also you can do it this way... /dev/block/platform/msm_sdcc.1/by-name/modem like i suggested above. If you know how to create flashable zips then all you need to do is put it together and bam... you have a recovery flashable modem. No need to go through all the trouble with creating an odin flashable... that's a lot more unecessary work.
leond said:
Can you please elaborate on this? I was looking for TWRP flashable modem for note 3 and did not find one neither for Sprint nor for any other carrier.
I tried to create an ODIN flashable modem. It looks like modem.emmc.win has the same format as modem.bin (at least the same header and similar size) so i just renamed modem.emmc.win to modem.bin then used:
c:\cygwin420\bin\tar -H ustar -c modem.bin > modem.tar
c:\cygwin420\bin\md5sum -t modem.tar >> modem.tar
copy modem.tar modem.tar.md5
info came from this guide: [TUTORIAL] How to repackage ODIN files and then tried to flash resulting file via ODIN , but that failes with : "secure check fail modem"
Click to expand...
Click to collapse
Here is Just My Lollipop Modem.
TWRP recovery.
https://app.box.com/s/w9cs93h3ftmw2g8tgblmvv81ci0g5ulq
rbeavers said:
Here is Just My Lollipop Modem.
TWRP recovery.
https://app.box.com/s/w9cs93h3ftmw2g8tgblmvv81ci0g5ulq
Click to expand...
Click to collapse
it's a recovery backup not a recovery flashable file. It has already been posted and as before it cannot be flashed
leond said:
it's a recovery backup not a recovery flashable file. It has already been posted and as before it cannot be flashed
Click to expand...
Click to collapse
Unzip put in twrp folder and RESTORE!
I've restored the lollipop backup for the note 3 and a note 4 backup on my note 3 and it ALL worked.
rbeavers said:
Unzip put in twrp folder and RESTORE!
I've restored the lollipop backup for the note 3 and a note 4 backup on my note 3 and it ALL worked.
Click to expand...
Click to collapse
As with previous versions posted n this thread it shows as working but if I check baseband version it's still NK4.
leond said:
As with previous versions posted n this thread it shows as working but if I check baseband version it's still NK4.
Click to expand...
Click to collapse
Your right, tried to duplicate, no go.
Guess We have to wait for the Devs.
rbeavers said:
Your right, tried to duplicate, no go.
Guess We have to wait for the Devs.
Click to expand...
Click to collapse
Something is really wired:
Someone has posted a complete stock odin tar file here (ROM)(ODIN)OC5 stcock firmware tar
most (but not all) people report that after flashing baseband gets updated to OC5. I took the tar and repackaged first to only include modem.bin & NON-HLOS.bin like the rest of the odin modem tars. Now it successfully FLASHes with odin but after reboot it still says NK4 in baseband.
I went even further and created a tar that has everything besides system, cache and recovery - again it flashes successfully but but after reboot it still says NK4 in baseband. It almost loks like the update is done but the version number is not updated somewhere.
i can post links to files if anyone wants to try as well
Ok, I was finally able to update basdeband to OC5. to do so I had to go back to NH7 modem first. For some reason it would not upgrate modem from NK4 to OC5 doesn't matter what i did, but went from NH7 to OC5 in the first try. so here is what i did:
1) Downgrade modem to NK4 using this:
http://www.mediafire.com/download/jk7qevy1swwfw2e/N900PVPUDNK4+MODEM+BOOTLOADER.zip
The link and instructions are provided by this thread: [ROM] kk 4.4.4 [N900PVPUDNK4] NO KNOX [DEODEX]
Download zip above ( NK4 modem and bootloader )
Extract the zip files
Boot into download mode
Use odin 3.07 from zip click PDA box flash modem first (you should be able to use any other version of Odin as well)
I did not FLASH the bootloader. The NK4 odin tar file contains 2 files : modem.bin and NON-HLOS.bin So I prepared the OC5 modem tar with the same files from OC5 stock tar.
Reboot and make sure your baseband now ends with NK4. After a minute or so the popup came up saying system is being updating. Wait until it's done and reboot to download mode again.
2) Download OC5 modem and bootloader zip file from the link below and extract:
https://www.mediafire.com/?6qeh035h9xh60ng
Now you can flash OC5 modem,. reboot in to Download mode again and follow the same steps as above, but select modem-OC5.tar.md5, flash, reboot in to Download mode for the 3rd time and upgrade bootloader using bootloader-OC5.tar.md5 file (in Odin click the bootloader box flash bootloader).
reboot, verify that your baseband is now OC5
reply please
is this a rom that I can flash?
Only if you have a custom recovery. If you don't, or don't know what that is, then you need the "Odin" ROM

[ODIN][FULL-WIPE] 5.0.1 Lollipop OC1

Credit goes to surge1223 for this resource as I did not create this file that was made.
This resource allows you to emergency-full wipe your Android system in case you are in a boot loop or stuck.
Download 5.0.1 Full-Wipe
Get Odin 3.0.9 here
Full Wipe ( AKA Emeregency Repair)
1. Unzip the file and you should have a ALL_VZW_I545VRUGOC1_I545VZWGOC1_CL4584173_QB4517016_REV06_user_low_ship_MULTI_CERT.tar
2. Select the tar.md5 in Odin under PDA (or AP if using Odin 3.09) and keep Odin's default settings
3. Extract the PIT file from your phone or Odin tar if you need to.
4. Put the PIT file in PIT and load the the Odin tar.md5 in PDA (or AP if using Odin 3.09) then click start.
mcbeat257 said:
Credit goes to surge1223 for this resource as I did not create this file that was made.
This resource allows you to emergency-full wipe your Android system in case you are in a boot loop or stuck.
Download 5.0.1 Full-Wipe
Get Odin 3.0.9 here
Full Wipe ( AKA Emeregency Repair)
1. Unzip the file and you should have a ALL_VZW_I545VRUGOC1_I545VZWGOC1_CL4584173_QB4517016_REV06_user_low_ship_MULTI_CERT.tar
2. Select the tar.md5 in Odin under PDA (or AP if using Odin 3.09) and keep Odin's default settings
3. Extract the PIT file from your phone or Odin tar if you need to.
4. Put the PIT file in PIT and load the the Odin tar.md5 in PDA (or AP if using Odin 3.09) then click start.
Click to expand...
Click to collapse
Hi mate!
How do I flash a custom recovery like TWRP on this OC1? I want to flash other Touchwiz ROMs. Thanks for your great work..
I am now on OC1. How do I root it?
Nana Ayeh said:
Hi mate!
How do I flash a custom recovery like TWRP on this OC1? I want to flash other Touchwiz ROMs. Thanks for your great work..
I am now on OC1. How do I root it?
Click to expand...
Click to collapse
There's no custom recovery options if you're on OC1 bootloader, but you do have options for root/flashing. OC1 is rootable with KingRoot on the desktop. If you want to flash roms from there (or xposed), you need to use FlashFire.
Thanks for providing this. I was rooted but I wanted to flash the latest stock firmware that would allow me to root again if I change my mind. I attempted to download OC1 from Sammobile but it was taking way too long. In the meantime while waiting for the download I found this post. I downloaded it here, flashed it and went through the initial setup of my phone. At this time the file is still downloading from Sammobile. I'm letting it to continue just to see how long it takes.
Can you post the pit file?
This is what it should look like: https://www.androidfilehost.com/?fid=23269279319199111 You should be able to take the .tar.md5 file and unzip it using 7-zip and pull out the .pit file. You'll need to unzip the tar.md5 anyway so you can get to the PDA(or AP) file.

Categories

Resources