upgraded with kies . mhl is fixed. I rooted with the hispasian kernel from Shinyside but that broke mhl probably because the kernel is based on the fof6 firmware . so I again flashed with kies installed twrp and ran the debloater from muniz_ri . This update seems to be a huge improvement so far.
here is a fast download link to the odin flashable tar
https://mega.co.nz/#!5QVz2AaT!9dV7WFKcf12-9Pn3OeiNvXbAceNJRIChi3Vixzdp2tw
if the tar file does not work for you here is the zip . extract it first and then flash
https://mega.co.nz/#!8NtB2aAA!bxVTbiS-P8IOej5_1d0T7iouU8GGHszG5AcZpACCXl4
this is the debloat script i used created by muniz_ri. this is the older script that does not require root.
https://mega.co.nz/#!Rd0C1JhY!fiKMIzkPszlF5JvEooWrBQoIdrurUKLsEtDTEZOouHY
instructions for the script can be found in the second post of this thread here http://forum.xda-developers.com/tmo.../g900tof6batchdebloater-customizable-t3147293
After update, I have screen pinning under security section. So far I haven't found a changelog. But my phone feels snappier, could be placebo though.
Sent from my SM-G900T using XDA Free mobile app
Sweet! Would you be able to run one of the stagefright detectors to see if this patches the exploit as well?
Received the update OTA this morning. Installed the update and Lookout's Stagefright Detector now shows the S5 as NOT vulnerable. I checked before updating, and the device WAS vulnerable at that time.
Well hispasian kernel is gonna have to wait for the source to be released. But the trap kernel will be updated as soon as I download the firmware
Derp- I'll have to wait for the source for trap kernel too haha I forgot about the enforcing sh!t. Time to start emailing samsung
---------- Post added at 01:48 PM ---------- Previous post was at 01:06 PM ----------
Start emailing them asking for release of the FOG6 source code
opensource.samsung.com/reception/receptionSub.do?method=inquiryView
fill out the crap, select release of source in the drop down
haha i was thinking that too . anyway sending request now
I've also submitted a request.
ashraf sharif said:
upgraded with kies . mhl is fixed. I rooted with the hispasian kernel from Shinyside but that broke mhl probably because the kernel is based on the fof6 firmware . so I again flashed with kies installed twrp and ran the debloater from muniz_ri . This update seems to be a huge improvement so far.
here is a fast download link to the odin flashable tar
https://mega.co.nz/#!RI0GCQpb!9dV7WFKcf12-9Pn3OeiNvXbAceNJRIChi3Vixzdp2tw
Click to expand...
Click to collapse
Glad to hear that MHL is fixed! Thanks for sharing.
Edit: The issue I encountered below was fixed by chaging the extension *.tar[1].md5 to *.tar.md5 which I overlooked at first.
I am getting a "MD5 error! Binary is invalid" after I clicked on PDA / AP and browsed to the .tar.md5 I downloaded from the link in this thread. I used the Unified Android Toolkit, which starts ODIN v3.09 to Flash the ROM. In Odin the message is "MD5 Hash value is unvlaid."
Note that I just carried it out a a factory reset (using also the advanced option and wipe system, data, ...) Not sure if it was appropriate. Anyhow, I restated in Downloading mode (ODIN MODE, UDC START, Knox Warranty Void: 0x1 (4)) so I skipped straight to Flash Rom, which started Odin.
Any suggestions?
Thank you
just updated but my baseband version is still G900TUVU1F0F6
dpluigi said:
Edit: The issue I encountered below was fixed by chaging the extension *.tar[1].md5 to *.tar.md5 which I overlooked at first.
I am getting a "MD5 error! Binary is invalid" after I clicked on PDA / AP and browsed to the .tar.md5 I downloaded from the link in this thread. I used the Unified Android Toolkit, which starts ODIN v3.09 to Flash the ROM. In Odin the message is "MD5 Hash value is unvlaid."
Note that I just carried it out a a factory reset (using also the advanced option and wipe system, data, ...) Not sure if it was appropriate. Anyhow, I restated in Downloading mode (ODIN MODE, UDC START, Knox Warranty Void: 0x1 (4)) so I skipped straight to Flash Rom, which started Odin.
Any suggestions?
Thank you
Click to expand...
Click to collapse
Thanks for pointing that out. It took me several tries to successfully upload the file to mega. I changed the filename in my cloud drive just now so the filename should work fine.
That's strange, how did you update? Kies?odin?ota?
kies
thats strange maybe try samsung smart switch or try kies again? you can odin flash it too.
dpluigi said:
Edit: The issue I encountered below was fixed by chaging the extension *.tar[1].md5 to *.tar.md5 which I overlooked at first.
I am getting a "MD5 error! Binary is invalid" after I clicked on PDA / AP and browsed to the .tar.md5 I downloaded from the link in this thread. I used the Unified Android Toolkit, which starts ODIN v3.09 to Flash the ROM. In Odin the message is "MD5 Hash value is unvlaid."
Note that I just carried it out a a factory reset (using also the advanced option and wipe system, data, ...) Not sure if it was appropriate. Anyhow, I restated in Downloading mode (ODIN MODE, UDC START, Knox Warranty Void: 0x1 (4)) so I skipped straight to Flash Rom, which started Odin.
Any suggestions?
Thank you
Click to expand...
Click to collapse
Im still getting that "Binary is invalid" message in odin
Sent from my SM-G900t using XDA Free mobile app
fdavila17 said:
Im still getting that "Binary is invalid" message in odin
Sent from my SM-G920F using XDA Free mobile app
Click to expand...
Click to collapse
Try removing md5 off the end
ShinySide said:
Try removing md5 off the end
Click to expand...
Click to collapse
that did the trick.... but it failed when it was about 90% done.... tried 3 times with no luck
fdavila17 said:
that did the trick.... but it failed when it was about 90% done.... tried 3 times with no luck
Click to expand...
Click to collapse
Failed on what?
ShinySide said:
Failed on what?
Click to expand...
Click to collapse
in odin... when it starts installling the system... it says failed in odin...
ashraf sharif said:
Thanks for pointing that out. It took me several tries to successfully upload the file to mega. I changed the filename in my cloud drive just now so the filename should work fine.
Click to expand...
Click to collapse
Thanks. The ROM flashed easily and after the initial setups I am trying to Root my phone. The Recovery-TWRP-2.7.1.0-KLTE.tar was sinatalled, Busibox Root zip files were pushed to be flashed, I think it rebooted to TWRP... not it is stuck when booting to Android, i.e. white text "Samsung Galaxy S5" over black background. I tried a couple of time to force reboot, now it freezes at T..Mobile in Red with white background display.
Another details, in the Unified Android Toolkit, I selected Samsung S5 / TMobile / Build 5.0 (the only choice besides 4.4.1 and 4.4.1).
Also, I thought your ROM was already rooted but initially I haden't set the usb debug mode, just the Developer mode (tapping 7 times on Build number).
I am a newbie, do you have a suggestion of what went wrong.
thanks,
Donat
Related
I have rooted gs3 with CWM, i can se that is available one OTA update, but when I try to update, its says failed. How I can unroot and go back to stock rom without deleting any thing?
Sent from my Galaxy S3 using xda premium
cukiwap said:
I have rooted gs3 with CWM, i can se that is available one OTA update, but when I try to update, its says failed. How I can unroot and go back to stock rom without deleting any thing?
Sent from my Galaxy S3 using xda premium
Click to expand...
Click to collapse
You can`t, you have to flash a stock rom with Odin and do a data/factory reset afterwards. Backup your files first to your pc.
cukiwap said:
I have rooted gs3 with CWM, i can se that is available one OTA update, but when I try to update, its says failed. How I can unroot and go back to stock rom without deleting any thing?
Sent from my Galaxy S3 using xda premium
Click to expand...
Click to collapse
Upload the update.zip for me to download and I will convert it to a CWM flashable ota and you wont lose root or recovery or need to reset to factory. You will find the ota update.zip in '/cache/fota'. Which stock ROM are you currently on? I have a BLG6 to BLG8 in this thread LINK
I flashed my GS3 via Odin with stock firmware
XXALE8
Firmware Info
PDA: XXALE8
Phone: XXLE8
Date: 13/05/2012
Android Version: 4.0.4
that was the same version before, but now is not coming any OTA update, I have checked via Kies, but Kies says your device does not support software upgrading via kies
Now my question is: do my phone will get update 4.1 when is ready, or I need to reflash with other version?
cukiwap said:
I flashed my GS3 via Odin with stock firmware
XXALE8
Firmware Info
PDA: XXALE8
Phone: XXLE8
Date: 13/05/2012
Android Version: 4.0.4
that was the same version before, but now is not coming any OTA update, I have checked via Kies, but Kies says your device does not support software upgrading via kies
Now my question is: do my phone will get update 4.1 when is ready, or I need to reflash with other version?
Click to expand...
Click to collapse
I think your GS3 is branded
---------- Post added at 05:47 PM ---------- Previous post was at 05:43 PM ----------
cukiwap said:
I have rooted gs3 with CWM, i can se that is available one OTA update, but when I try to update, its says failed. How I can unroot and go back to stock rom without deleting any thing?
Sent from my Galaxy S3 using xda premium
Click to expand...
Click to collapse
How to uninstall
This is by no means an extensive guide for unrooting, but if you want to sell or warranty your device, I advise the following procedure:
- Use Triangle Away to reset the flash counters, and pull the battery immediately after rebooting starts
- Boot into recovery and perform a wipe, and pull the battery immediately after rebooting starts
- Go to SamMobile and get the stock firmware for your region
- Flash that stock firmware on your device
- Let Android boot, go through device setup (without doing any logins) until Android is fully usable again
- Reboot
- Wait at least 10 minutes
- Check Settings->About device->Status and make sure Device status is not "Modified"
- Perform another factory reset
- Boot into download mode and make sure the flash counter and system status are all set to official
Source: http://forum.xda-developers.com/showthread.php?t=1695238
I don't think so, I bought this phone in Saturn in Belgium, is not branded
Casanoaa said:
I think your GS3 is branded
---------- Post added at 05:47 PM ---------- Previous post was at 05:43 PM ----------
How to uninstall
This is by no means an extensive guide for unrooting, but if you want to sell or warranty your device, I advise the following procedure:
- Use Triangle Away to reset the flash counters, and pull the battery immediately after rebooting starts
- Boot into recovery and perform a wipe, and pull the battery immediately after rebooting starts
- Go to SamMobile and get the stock firmware for your region
- Flash that stock firmware on your device
- Let Android boot, go through device setup (without doing any logins) until Android is fully usable again
- Reboot
- Wait at least 10 minutes
- Check Settings->About device->Status and make sure Device status is not "Modified"
- Perform another factory reset
- Boot into download mode and make sure the flash counter and system status are all set to official
Source: http://forum.xda-developers.com/showthread.php?t=1695238
Click to expand...
Click to collapse
Hi,
I recently bought a second hand GS3. It was rooted when i bought it but now that I'd like to update it via Kies i want unroot it.
I have tried following your steps and many others for that matter.
the programs i have downloaded so far are
-Triangle Away
- Odin
- 2 seperate stock firmwares from http://samsung-updates.com/ for my region (ireland)
- 7 zip
I am still stuck though
I Open the firmware zip, to reveal two files, a .tar.md5 file and a .dll file
From here i believe i should be able to open the md5 file on Odin, however trying to open this file as a pda in Odin doesn't work because Odin can't even seem to recognise that the file even exists.
I have tried extracting the md5 file, this leaves 5 img files, i then extracted them using a program i found on xda called sgs2toext4
At this point i am really lost as to what I am doing wrong. I know i need to flash the rom i've downloaded but how do i get odin to recognise the file?
I am a pretty serious noob in need of some pretty serious help.
To flash with ODIN...
tekkr said:
I am still stuck though
I Open the firmware zip, to reveal two files, a .tar.md5 file and a .dll file
From here i believe i should be able to open the md5 file on Odin, however trying to open this file as a pda in Odin doesn't work because Odin can't even seem to recognise that the file even exists.
I have tried extracting the md5 file, this leaves 5 img files, i then extracted them using a program i found on xda called sgs2toext4
Click to expand...
Click to collapse
The .tar.md5 file and the .dll file should be together to avoid a freak mishap (but that is just me being paranoid), don't extract/unzip/f-up anything beyond that point... go to odin, click on PDA and select the .tar.md5 file you got, THAT is the firmware file, after that, click start and let it do it's job, BTW, make sure the only TICKED options are Auto Reboot and F. Reset Time, everything else will brick the device if you don't know what you're doing (which you probably don't anyway, so don't try anything)
Be aware you need the drivers that COME WITH KIES to make ODIN able to recognize your device (if it does, you'll see an "Added!!" message in the left message box of ODIN and a "COM3/4" yellow rectangle light up in the top left square of the upper row
If you need more help reply to this and i'll help you... but you can also watch some tutorial vids on youtube or something, i'm pretty sure somebody here already did one to avoid long posts
Long gone note date of last post will save your ink .
jje
DerFeniks said:
The .tar.md5 file and the .dll file should be together to avoid a freak mishap (but that is just me being paranoid), don't extract/unzip/f-up anything beyond that point... go to odin, click on PDA and select the .tar.md5 file you got, THAT is the firmware file, after that, click start and let it do it's job, BTW, make sure the only TICKED options are Auto Reboot and F. Reset Time, everything else will brick the device if you don't know what you're doing (which you probably don't anyway, so don't try anything)
Be aware you need the drivers that COME WITH KIES to make ODIN able to recognize your device (if it does, you'll see an "Added!!" message in the left message box of ODIN and a "COM3/4" yellow rectangle light up in the top left square of the upper row
If you need more help reply to this and i'll help you... but you can also watch some tutorial vids on youtube or something, i'm pretty sure somebody here already did one to avoid long posts
Click to expand...
Click to collapse
How long does this take? Odin is just kid of staring at me - all 3 keys are greyed out and it says SetupConnection. I should have chose PDA - yes? not PHONE???
I was flashing a rom onto my galaxy s4 and I've noticed that it couldn't receive OTA updates before but I never updated so it didn't affect me much until today when I tried flashing a rom and the code turned red and it says SW REV. Check FAIL: fused:5. Binary: 3, I also tried using odin downloader to flash VRAUME7 back onto it but said it encountered a error in line 27. After I tried using Kies downloader to update the software but it says firmware upgrade encountered an issue please select recovery mode in Kies but when I used recovery mode in keis it says it encountered a problem while updating, I'm out of ideas could someone please help
af_nm said:
I was flashing a rom onto my galaxy s4 and I've noticed that it couldn't receive OTA updates before but I never updated so it didn't affect me much until today when I tried flashing a rom and the code turned red and it says SW REV. Check FAIL: fused:5. Binary: 3, I also tried using odin downloader to flash VRAUME7 back onto it but said it encountered a error in line 27. After I tried using Kies downloader to update the software but it says firmware upgrade encountered an issue please select recovery mode in Kies but when I used recovery mode in keis it says it encountered a problem while updating, I'm out of ideas could someone please help
Click to expand...
Click to collapse
Fused 5 means you need to flash either mj7 or mk2 .
I'd do the full wipe at this point. If one doesn't work right at first... Try the other. Do you recall which your phone was on prior to this?
Sent From My Verizon S4
af_nm said:
I was flashing a rom onto my galaxy s4 and I've noticed that it couldn't receive OTA updates before but I never updated so it didn't affect me much until today when I tried flashing a rom and the code turned red and it says SW REV. Check FAIL: fused:5. Binary: 3, I also tried using odin downloader to flash VRAUME7 back onto it but said it encountered a error in line 27. After I tried using Kies downloader to update the software but it says firmware upgrade encountered an issue please select recovery mode in Kies but when I used recovery mode in keis it says it encountered a problem while updating, I'm out of ideas could someone please help
Click to expand...
Click to collapse
so what is your base build number?
what rom were you trying to flash
are you loki'd or safestrap?
decaturbob said:
so what is your base build number?
what rom were you trying to flash
are you loki'd or safestrap?
Click to expand...
Click to collapse
Yea I don't know either.. I just saw that Odin error then I saw me7. Figured op tried flashing the wrong one. It is a bit confusing though with no actual info to go on.
Sent From My Verizon S4
decaturbob said:
so what is your base build number?
what rom were you trying to flash
are you loki'd or safestrap?
Click to expand...
Click to collapse
Verizon SCH-I545
a rom called premium but I didn't even get to download it before the red code started
and lastly I rooted using loki'd, sorry for the lack of info
af_nm said:
Verizon SCH-I545
a rom called premium but I didn't even get to download it before the red code started
and lastly I rooted using loki'd, sorry for the lack of info
Click to expand...
Click to collapse
OK well if you can get back into download mode then flash the MDK tar . I'm not really sure if you were flashing a rom in Odin or a custom recovery but in any case if all else fails.... Odin mdk
Sent From My Verizon S4
With the new knox security trying to flash a prior firmware will trip the flag so it's advised to be careful when flashing images via Odin. Flash an earlier version that doesn't take and you'll lose the warranty on your phone.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
would reinstalling the pit files work?
odin mdk
Mistertac said:
OK well if you can get back into download mode then flash the MDK tar . I'm not really sure if you were flashing a rom in Odin or a custom recovery but in any case if all else fails.... Odin mdk
Sent From My Verizon S4
Click to expand...
Click to collapse
I ended up trying to flash using odin mdk and even that refused to work is there anything else I can try
af_nm said:
I ended up trying to flash using odin mdk and even that refused to work is there anything else I can try
Click to expand...
Click to collapse
I have to admit, I am really confused by your posts. I have no idea what you were, or are, trying to do. Are you SURE you were on MDK? If you weren't on MDK, you need to Odin back to the build you were on.
Sent from my NCC-1701 using Tapatalk 4
riker147 said:
I have to admit, I am really confused by your posts. I have no idea what you were, or are, trying to do. Are you SURE you were on MDK? If you weren't on MDK, you need to Odin back to the build you were on.
Sent from my NCC-1701 using Tapatalk 4
Click to expand...
Click to collapse
same here, I'm not sure what he has or what he has done........
decaturbob said:
same here, I'm not sure what he has or what he has done........
Click to expand...
Click to collapse
I know it... It we can know exactly where you were before. Like did you have this s4 since new when they shipped with mdk? Did u root it yourself then Loki? Install cwm or twrp? Things are kinda confusing. Just figured you were on mdk but I've seen stranger posts on here when in the end the op actually didn't have mdk or wasn't even on e Verizon s4.
Sent From My Verizon S4
Mistertac said:
I know it... It we can know exactly where you were before. Like did you have this s4 since new when they shipped with mdk? Did u root it yourself then Loki? Install cwm or twrp? Things are kinda confusing. Just figured you were on mdk but I've seen stranger posts on here when in the end the op actually didn't have mdk or wasn't even on e Verizon s4.
Sent From My Verizon S4
Click to expand...
Click to collapse
The OP says that it said "Fused:5" means he is on MJ7 or MK2. It may have been on MDK and Loki'd at one point, but it's now MJ7/MK2 and needs to be recovered using one of those ROM images - NOT MDK.
k1mu said:
The OP says that it said "Fused:5" means he is on MJ7 or MK2. It may have been on MDK and Loki'd at one point, but it's now MJ7/MK2 and needs to be recovered using one of those ROM images - NOT MDK.
Click to expand...
Click to collapse
Yea good call I think I was actually confusing posts when I was responding earlier. Forgot about the fused 5. Thanks .
Sent From My Verizon S4
riker147 said:
I have to admit, I am really confused by your posts. I have no idea what you were, or are, trying to do. Are you SURE you were on MDK? If you weren't on MDK, you need to Odin back to the build you were on.
Sent from my NCC-1701 using Tapatalk 4
Click to expand...
Click to collapse
No it was shipped with vruame7 and I was never able to update after I rooted so it's always been on vraume7 I used loki'd when I rooted. Ive tried using mj7 and mk2 and used this http://forum.xda-developers.com/showthread.php?t=2507253. when I ran it in odin it ran until it stopped at system.img.ext4 followed by complete(Write) operation failed and on the top left of my phone it says START [224,1440] and BAR [240,1440]
af_nm said:
No it was shipped with vruame7 and I was never able to update after I rooted so it's always been on vraume7 I used loki'd when I rooted. Ive tried using mj7 and mk2 as well but I can't find one that will work
Click to expand...
Click to collapse
If it came with VRUAME7 then you didnt use the Loki method to root. If you want help you should post more logs/info. Like your last sentence "Ive tried using mj7 and mk2 as well but I can't find one that will work" can you elaborate on that? Saying you cant find one that works suggests you've found ones that dont work. But what does "don't work" consist of? It could be "write error", md5 mismatch, "PIT partition not found", "SW Rev check fail..", wrong file etc.
Check that the Odin tar file name says "VRUEMJ7" or "VRUEMK2" in it and ends in tar.md5 and make sure the md5 matches. If that fails then post back with logs/info that will actually assist us in helping you troubleshoot
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
If it came with VRUAME7 then you didnt use the Loki method to root. If you want help you should post more logs/info. Like your last sentence "Ive tried using mj7 and mk2 as well but I can't find one that will work" can you elaborate on that? Saying you cant find one that works suggests you've found ones that dont work. But what does "don't work" consist of? It could be "write error", md5 mismatch, "PIT partition not found", "SW Rev check fail..", wrong file etc.
Check that the Odin tar file name says "VRUEMJ7" or "VRUEMK2" in it and ends in tar.md5 and make sure the md5 matches. If that fails then post back with logs/info that will actually assist us in helping you troubleshoot
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No I converted my SD card to EXFAT and downloaded the root onto the rom so I was mistaken I didn't use loki sorry. I just ran this factory image which is for mj7 http://forum.xda-developers.com/showthread.php?t=2507253. I confirmed it was for mj7 after the MD5 file downloaded and ran it using odin, it went fine until it got to system.img.ext4 followed by complete(Write) operation failed and on the top left of my phone it says START [224,1440] and BAR [240,1440] in red and the flash failed. I hope this is more helpful
af_nm said:
No I converted my SD card to EXFAT and downloaded the root onto the rom so I was mistaken I didn't use loki sorry. I just ran this factory image which is for mj7 http://forum.xda-developers.com/showthread.php?t=2507253. I confirmed it was for mj7 after the MD5 file downloaded and ran it using odin, it went fine until it got to system.img.ext4 followed by complete(Write) operation failed and on the top left of my phone it says START [224,1440] and BAR [240,1440] in red and the flash failed. I hope this is more helpful
Click to expand...
Click to collapse
Yes thats much better, gives a lot more info that we can use to help Follow the directions I give here and download and use the pit file I uploaded in this thread, you can find it towards the bottom under the "Full-wipe" directions. Post back and let us know if it worked or if you need more help. Hope this helps.
Surge1223 said:
Yes thats much better, gives a lot more info that we can use to help Follow the directions I give here and download and use the pit file I uploaded in this thread, you can find it towards the bottom under the "Full-wipe" directions. Post back and let us know if it worked or if you need more help. Hope this helps.
Click to expand...
Click to collapse
So I followed the directions to flash the system.img.ext4 file and I already extracted it and am uploading it using heimdall. I have the pit file ready and I put the system.img.ext4 in under SYSTEM, added then removed it but it won't let me flash once it's removed and if I do flash with it on there it says ERROR: Failed to access device. libusb error: -12. I have deleted kies and reinstalled Samsung drivers, any ideas
af_nm said:
So I followed the directions to flash the system.img.ext4 file and I already extracted it and am uploading it using heimdall. I have the pit file ready and I put the system.img.ext4 in under SYSTEM, added then removed it but it won't let me flash once it's removed and if I do flash with it on there it says ERROR: Failed to access device. libusb error: -12. I have deleted kies and reinstalled Samsung drivers, any ideas
Click to expand...
Click to collapse
Driver issue 99% of the time make sure you've uninstalled all Samsung drivers. Use windows' control panel option to uninstall programs and make sure all kies, samsung, and verizon related stuff is uninstalled. Then reboot the pc, let your phone install the drivers for your pc, and try using a different usb port with the stock oem cable. Also make sure adb isn't running in the background
Sent from my SCH-I545 using XDA Premium 4 mobile app
First, thank you to the anonymous source who provided us with this build and thank you to @garwynn for posting it here.
This Odin One-Click.exe contains the Stock NI3 Bootloader, Kernel, Modem and ROM for the Sprint Samsung Galaxy S5 (SM-G900P). Yes, that means this comes with the full Knox Bootloader.
There has been no change to the ROM from the initial build released by Samsung.
This will NOT trigger the Yellow Triangle NOR will it increment the Odin flash count.
This one-click resets your whole phone to the stock NI3 experience, similar to a factory restore and it may wipe all data. It also contains the full bootloader and Knox.
Instructions:
1: Backup anything important and Disable any PINs.
During this process your phone's software will be returned to the Stock setup. All system data will be lost. To be safe, it is best to archive your backup off your phone, ie on your PC or Dropbox.
2: Install Samsung USB/Android drivers (if necessary).
Samsung Drivers Download Link
3: Download the NI3 Stock ROM One-Click.
http://www.rwilco12.com/forum/showthread.php?tid=938 (Resets user data)
4: Unzip One-Click ROM using 7zip (this package is a self-extracting exe you should just be able to double-click on it after download and it will do the rest).
5: Start the Odin One-Click.
Navigate to the location where the SM-G900P_NI3_Stock_Unrooted.exe was saved upon extract from the 7Zip archive.
Double-click on SM-G900P_NI3_Stock_Unrooted.exe. *On Vista or newer, you may need to right-click on the file and select Run as Administrator.
6: Place phone in Download Mode.
- Power phone completely off.
- Press and hold Volume Down, Home and Power buttons, all at the same time.
- Release the buttons only when the ‘Warning!!’ message appears.
- Press [Volume Up] to enter Download mode.
7: Connect USB cable to PC and phone.
Odin should show a yellow COM port in the second column. If you do not see a yellow COM port, you may need to run the Odin One-Click as Administrator and/or unplug/plugin the USB cable after starting Odin One-Click.
8: Start Odin flash process.
Press [Start].
9: Complete - PASS!
Status should change to green PASS! At this point your phone should automatically reboot.
The boot process will take slightly longer than usual during which time you'll see the Sprint 4G/Spark logo screen.
Congratulations! You've flashed the Factory Restore NI3 build!
XDA:DevDB Information
[ROM][ODIN][OC] SM-G900P NI3 (Modem/Kernel/Bootloader/ROM - Full Restore - Unrooted), ROM for the Sprint Samsung Galaxy S 5
Contributors
rwilco12
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2015-02-10
Last Updated 2015-02-10
Download: http://www.rwilco12.com/forum/showthread.php?tid=938
Could you post just the bootloader tar
Sent from my SM-G900P using XDA Free mobile app
@rwilco12
Been doing a lot of reading/research as I'm new to the Samsung game. But I've been every else besides Sony. I read your unpack tutorial on your website, and jumped all over reading unpacking how-to's. Seems to me the recommended an easiest way to create a "no-wipe" package is via SplitFUS2. Most of what I've read is for older devices, and I was wondering if that's the way you recommend doing it, and if you know whether or not it works with S5 packages?
Will normal root process work on it. I'm tempted to do it only cause I want the modem
AOD_Corwin said:
Will normal root process work on it. I'm tempted to do it only cause I want the modem
Click to expand...
Click to collapse
+1
AOD_Corwin said:
Will normal root process work on it. I'm tempted to do it only cause I want the modem
Click to expand...
Click to collapse
rhyme187 said:
+1
Click to expand...
Click to collapse
Chainfire's autoroot does work but I don't believe Towelroot does.
gokart2 said:
@rwilco12
Been doing a lot of reading/research as I'm new to the Samsung game. But I've been every else besides Sony. I read your unpack tutorial on your website, and jumped all over reading unpacking how-to's. Seems to me the recommended an easiest way to create a "no-wipe" package is via SplitFUS2. Most of what I've read is for older devices, and I was wondering if that's the way you recommend doing it, and if you know whether or not it works with S5 packages?
Click to expand...
Click to collapse
My guess is you're referring to my tutorials on how to build your own flashable TAR?
Honestly I've never used the SplitFUS2 utility so I can't give you a 100% answer there. However, what I can tell you is that Samsung devices use one of two methods to wipe a device when flashing a TAR. Generally the method involves wiping a partition and overwriting it with a partition file included in the TAR. There are several different partitions and each of them governs a different aspect of the device's functionality. There is generally a specific file that governs the data partition, once you extract the TAR you would then recompile it without the data partition file and flash the final resulting TAR.
The other is script based and that area I'm not an expert on. My BFF @garwynn is pretty good though and might be able to walk you through fixing the scripts if necessary.
Now one other thing to keep in mind is that this thread is for a one-click not the actual TAR. There are ways to decompile an Odin one-click but I would recommend just using the original TAR which can be downloaded in @garwynn's original TAR thread at http://forum.xda-developers.com/showthread.php?goto=newpost&t=2885005
Good luck!
rwilco12 said:
My guess is you're referring to my tutorials on how to build your own flashable TAR?
Honestly I've never used the SplitFUS2 utility so I can't give you a 100% answer there. However, what I can tell you is that Samsung devices use one of two methods to wipe a device when flashing a TAR. Generally the method involves wiping a partition and overwriting it with a partition file included in the TAR. There are several different partitions and each of them governs a different aspect of the device's functionality. There is generally a specific file that governs the data partition, once you extract the TAR you would then recompile it without the data partition file and flash the final resulting TAR.
The other is script based and that area I'm not an expert on. My BFF @garwynn is pretty good though and might be able to walk you through fixing the scripts if necessary.
Now one other thing to keep in mind is that this thread is for a one-click not the actual TAR. There are ways to decompile an Odin one-click but I would recommend just using the original TAR which can be downloaded in @garwynn's original TAR thread at http://forum.xda-developers.com/showthread.php?goto=newpost&t=2885005
Good luck!
Click to expand...
Click to collapse
Thanks for the reply. I was talking about your "How-To" on your site, and I replied there too. It was very helpful and informative. I found Splitfus2 doesn't seem to work with KitKat, only JB and before. After getting everything ready to go to try your method, extracting the files from the TAR, etc. I found the Kitkat file names differ a bit from the JB ones, according to the TAR BALL flashing order you have listed on your site. Which shouldn't matter since all I need to make is a stock system and recovery TAR. Assuming I use the method you have posted, only making a separate system and recovery TAR, a data wipe shouldn't happen......correct? Only other thing I'm not sure of is after extracting the files from the original TAR, the system is in system.ext4.img...... I assume I leave that the way it is, correct? Only time I've seen it that way is when extracting a system.img and converting it to a flashable rom.
When is the script wipe used? I'm pretty good with scripts. Thanks for your time and help, it's greatly appreciated!
Unrooted/Rooted
rwilco12 said:
Chainfire's autoroot does work but I don't believe Towelroot does.
Click to expand...
Click to collapse
Just wondering if anyone has done this and then rerooted phone WITH NO REPERCUSSIONS ? And how is everything running with the rom?
localpagefirst said:
Just wondering if anyone has done this and then rerooted phone WITH NO REPERCUSSIONS ? And how is everything running with the rom?
Click to expand...
Click to collapse
I flashed, then rooted with cfroot. My Knox was already tripped before flashing this. Not sure what you mean by repercussions, but flashing this should not trip Knox, its the cfroot part that would.
localpagefirst said:
Just wondering if anyone has done this and then rerooted phone WITH NO REPERCUSSIONS ? And how is everything running with the rom?
Click to expand...
Click to collapse
When you say "no repercussions" what exactly are you looking for?
"no repercussions"
rwilco12 said:
When you say "no repercussions" what exactly are you looking for?
Click to expand...
Click to collapse
Meaning problems after the rom has settled Like System UI, Context Issues,ECT.
Rwilco12 I fully trust your work and thank you and all whom have helped . I am as one could say very apprehensive about changing complete systems. Roms and modems. I was in no way referencing this to and thing bad.
---------- Post added at 05:52 PM ---------- Previous post was at 05:47 PM ----------
Bottom line is I am going for it even though Android "L" will be here first week of November.
Been following you since the Epic Touch days..... anywho, any chance of getting some love for the S5 Sport? Thx!
For anyone that has installed this...Any noticeable difference in the radio?
Sent from my SM-G900P using XDA Free mobile app
Jay5583 said:
For anyone that has installed this...Any noticeable difference in the radio?
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
Service at my house literally went from 1 bar to 2, YMMV. I did switch to the bmfr cm11 build a day after flashing this, service has remained the same.
recovery
thanks so much for posting this - been trying to find an easy way to odin back to stock after trying a few ROMs.
Will this also take us back to stock recovery or does it only do the system/rom part? if not, do you know how to get back to stock recovery?
thanks so much!
hi is there a ni3 modem with out system i can flash?
Serious Problem
i downloaded this on my dads new s5, just an hour old.
Flashed in odin, now im getting the "firmware upgrade encountered an issue" error message.
i tried going on to sammobile and downloading sprint stock firmware and flashing that, but odin is rejecting it.
theres also a bunch of versions on sam mobiles site, so im downloading 2 more versions, 1 from april and 1 from june (NCD & NE5)
could it be because im running odin on windows xp vmware thats making odin not take the tar file?
also, i dont know what version im coming from, the only thing i remember seeing when i allowed it into developer mode is that it was on 4.4.2.
please help!!!!
XP under VMware. Yeah, probably asking for trouble.
I was able to downgrade from the NG6 update released a few days ago back to NC5.
Knox Warranty Void: 0x0
I used the info and tut from this post
I used the full wipe method, I'm unsure if the no wipe one works
Information:
1. ROOT METHOD can be found here
2. Otherwise, Download Odin 3.09 here (Note: Bootloader = BL , PDA = AP , Phone = CP)
Download: VRUFNC5 No-Wipe SCH-I545_VZW_1_20140330160240_yni63xq6zh.zip
MD5: 71d1c7ea58d2ba81ccadd965b54a2215
Download: VRUFNC5 Full-Wipe SCH-I545_VZW_1_20140330160240_8il17ls9o2_fac.zip
MD5: 8a22dd4a47c2c5f890227fd952657d38
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_VZW_I545VRUFNC5_I545VZWFNC5_1151670_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.
Click to expand...
Click to collapse
Just confirming that this downgrade from ng6 worked for me too. im back to nc5 and yet to see if there will be no more reboots that everyone is having issues with on ng6.
Is there a way to do this with out using odin on a computer?
Im trying this right now via odin..... wish me luck.
brewer15650 said:
Im trying this right now via odin..... wish me luck.
Click to expand...
Click to collapse
Good Luck!!
Let everyone know how it went. I don't intend to take this update, but others will and will, undoubtedly, need to take the path you are now on...
snickerzz said:
I was able to downgrade from the NG6 update released a few days ago back to NC5.
Knox Warranty Void: 0x0
I used the info and tut from this post
I used the full wipe method, I'm unsure if the no wipe one works
Click to expand...
Click to collapse
No-Wipe works fine.
jwhistler said:
Good Luck!!
Let everyone know how it went. I don't intend to take this update, but others will and will, undoubtedly, need to take the path you are now on...
Click to expand...
Click to collapse
Worked like a charm. I did the full wipe and repartion(PIT). Took me a 1st timer using odin maybe 30mins to do.
npjohnson said:
No-Wipe works fine.
Click to expand...
Click to collapse
I am having a hellish time with no-wipe. Constant errors prevent input of even the lockscreen PIN. I've tried different cables, ports, running Odin as administrator and not... Ideas?
posaune76 said:
I am having a hellish time with no-wipe. Constant errors prevent input of even the lockscreen PIN. I've tried different cables, ports, running Odin as administrator and not... Ideas?
Click to expand...
Click to collapse
turn on usb debugging in the settings and turn off the lock code
snickerzz said:
turn on usb debugging in the settings and turn off the lock code
Click to expand...
Click to collapse
Damn. That probably was the thing that was killing me. After the first attempt, though, I could barely fight through the errors to a home screen, let alone change settings (delete corporate account to get rid of PIN, turn on dev mode, etc.). Ended up doing full wipe. Thanks for the thought. Lesson learned in case there's a next time.
Using Odin 3.09 for the no-wipe method, I load the NC5 .md5 file, and select it as instructed, but once I hit start, I get message stating "All threads completed. (succeed 0 / failed 0) " instantaneously without anything actually happening. I have both developer mode and USB Debugging enabled.
Am I missing something?
Ignore all of that. I loaded the .md5 file up before the phone was connected in Download Mode. Re-loading it fixed everything.
I flashed NC5 over NG6. constant ERROR!! process.acore HELP
It flashed successfully via ODIN. MD5 checker matched. So no corrupt rom. After booting, i keep getting non-stop android.process.acore & android.process.media stopped working every 1 sec, and hitting ok keeps bringing it back and I cannot do anything !!! This is so frustrating. I specifically wanted no wipe. Please tell me i dont have to Full Wipe it. How did it work for you, tell me the step by step. My NG6 was rooted, should I have unrooted first. Tell me what to do!!!
I tried to do this method,but I have had no luck. My phone returned the error "fused 6 binary 5" - What is it that I'm missing?
i keep getting errors
Going to try it.
fyi, after error upon error I tried a different cable using a different USB port. Worked like a charm!
I did the no-wipe method and got the android.process.acore & android.process.media errors. I ended up doing a full wipe and it worked fine. Unfortunately my Titanium Backup I ran the night before didn't run quite right ><. Live, learn and check backups!
NG6
Was NG6 released with a new update from VZ, or was this ported from the S5?
jwhistler said:
Good Luck!!
Let everyone know how it went. I don't intend to take this update, but others will and will, undoubtedly, need to take the path you are now on...
Click to expand...
Click to collapse
Is there a way unrooted to stop the update??
I had to take the wipe method but no biggie.
rfd177 said:
Is there a way unrooted to stop the update??
I had to take the wipe method but no biggie.
Click to expand...
Click to collapse
Are the problems with NG6 isolated to rooted phone, custom roms, or both at the same time?
Hello all.
I have made a firmware only file for the DOB1 version of software for those that want to upgrade with the mobile/pc odin way.
That way you can upgrade a knox 0 and keep knox 0 and root.
Just need to run mobile odin with the stock tar that is available and inject mobile odin and su
for reboot options have it go into download mode
then flash this firmware only file to complete the upgrade and then let it boot up.
Should be good to go.
Download the file from box here:
https://app.box.com/s/ihdqlrozzhyv2jmyqrhbcgkfvr27dl6b
Thought I've read in many places that lollipop doesn't work with mobile Odin.
What happens here is you dont get the full version of lollipop, so technically you are still on 4.4.4. You will still be on the kitkat kernel. Plus the possibility of errors and such.
I would just wait till the dev have a way to root the full version of lollipop.
The kernel is written though with aboot in the firmware only file that you flash with Odin no?
TheArtiszan said:
The kernel is written though with aboot in the firmware only file that you flash with Odin no?
Click to expand...
Click to collapse
No the kernel is boot.img, which is missing from you file. mobile odin can flash this but it is not recommended, also there is a bunch of necessary files that are not able to be flashed with mobile odin. That is the reason i came up with a way to root without tripping knox. Have you tried your method yet? if you did can you post a screen shot of your about phone.
The best way to get it done efficiently is pc Odin back to official 4.4.2 then take a two updates that will be waiting in line the Volte update then the 993mb Lollipop OTA putting you on stock 5.0.
MOBIL ODIN will screw you up if you try to flash the download able update .
I tried to cheat and go the easy way by reflashing stock 3e recovery with cf auto then I tried to use wannam xposed security hack to Enable custom to officiall status .
After I uses mobile Odin to flash the file from samfirm I was stuck in a boot loop .
Finally just full tar Odin flashed back to 4.4.2 then took Ota.
4.4.2 cf auto will root 5.0 just for reference nothing changes
Sent from my SM-G900T using XDA Free mobile app
Wait...
You had steps for updating?
I didn't find any when I looked.
I haven't yet tried this on my device but a friend that has it said these were the steps he did and it worked. I uploaded firmware and radio file since I didn't find it here. I can also make one that is the boot img in it to flash in regular Odin. Mobile Odin only injects in system I believe.
Do you have a link to your dob1 steps?
galaxyuser88 said:
No the kernel is boot.img, which is missing from you file. mobile odin can flash this but it is not recommended, also there is a bunch of necessary files that are not able to be flashed with mobile odin. That is the reason i came up with a way to root without tripping knox. Have you tried your method yet? if you did can you post a screen shot of your about phone.
Click to expand...
Click to collapse
Last post was for above. Didn't quote for some reason.
TheArtiszan said:
Wait...
You had steps for updating?
I didn't find any when I looked.
I haven't yet tried this on my device but a friend that has it said these were the steps he did and it worked. I uploaded firmware and radio file since I didn't find it here. I can also make one that is the boot img in it to flash in regular Odin. Mobile Odin only injects in system I believe.
Do you have a link to your dob1 steps?
Click to expand...
Click to collapse
Yeah i had steps for updating and rooting on kitkat not lollipop. I had gotten rid of my s5 2 days before lollipop came out. :crying: But a friend has the s5 and he tried to do your steps on his phone and said that it did not work and was getting errors and the kernel was still on 4.4, But he did say that after he pc odin back to stock and took the official lollipop update he was able to use cf auto root to root his device on lollipop. He unfortunately tripped knox doing it with cf auto root. I told him to wait and stop by my house so that i can test some methods that will root without tripping knox, but he couldnt wait and took the plunge. He also said that mobile odin crashed when he tried to use it with lollipop, lucky for him that when it crashed it did not mess his phone up.
The best bet here is to see if you can take the official update, use pc odin to flash ne6 kernel, then use towel root and then pc odin the stock 5.0 kernel back to see of you still have root and not trip knox..
Be careful when you try your method with the kernel added to your package and using mobile odin. Anything related to kernel can cause you to trip knox. I am still having my friend come over so that i can verify a couple of things before i update my thread on rooting.
Okay.
I have found a process for this that works perfectly.
At least on my device.
This is starting with a towelrooted NK2 version with knox 0x0
I went and downloaded the full DOB1 image from SamFirmware and copied that to the internal memory of the phone.
Then I installed mobile odin pro on the phone.
I then in mobile odin pro open the stock firmware from above and had it set to boot into download mode.
I flashed and let it open in download mode.
I then used Odin 3.09 to flash the firmware radio file with no reboot.
Then flashed the kernal in a seperate file.
Rebooted the phone into recovery to let it complete steps.
Then rebooted the phone normally.
Everything seems to have loaded up okay for me now.
Will try for a few days and report back. But is seems to have worked okay.
So you're rooted in DOB1 with knox at 0x0?
Chuki82 said:
So you're rooted in DOB1 with knox at 0x0?
Click to expand...
Click to collapse
Yup
Just a bit of trial and error going back and forth to find something that worked.
Only problem I am running into is that I can not update Su Binary with the app so far.
But it is giving me root access and everything seems to be working.
Okay I take that back.
I have su binaries and everything on it but it won't function and I can not update it for some reason.
I wonder if it is due to the mobile odin injecting ones that are too old.
I made some changes to mobile odin so it has the newer supersu apk and binary from 2.46
Will try and flash back and upgrade again and see if that makes a difference.
im getting an invalid md5 in pc odin. have you been able to flash this?
---------- Post added at 07:28 AM ---------- Previous post was at 06:36 AM ----------
TheArtiszan said:
Okay.
I have found a process for this that works perfectly.
At least on my device.
This is starting with a towelrooted NK2 version with knox 0x0
I went and downloaded the full DOB1 image from SamFirmware and copied that to the internal memory of the phone.
Then I installed mobile odin pro on the phone.
I then in mobile odin pro open the stock firmware from above and had it set to boot into download mode.
I flashed and let it open in download mode.
I then used Odin 3.09 to flash the firmware radio file with no reboot.
Then flashed the kernal in a seperate file.
Rebooted the phone into recovery to let it complete steps.
Then rebooted the phone normally.
Everything seems to have loaded up okay for me now.
Will try for a few days and report back. But is seems to have worked okay.
Click to expand...
Click to collapse
where do you get the kernel file? also the firmware only file you made is getting rejected in odin 3.09. what are you using to extract?
---------- Post added at 07:59 AM ---------- Previous post was at 07:28 AM ----------
ok I got the firemware only file to flash in odin but I had to rename the file from .tar.md5 to .tar.
TheArtiszan said:
Okay.
I have found a process for this that works perfectly.
At least on my device.
This is starting with a towelrooted NK2 version with knox 0x0
I went and downloaded the full DOB1 image from SamFirmware and copied that to the internal memory of the phone.
Then I installed mobile odin pro on the phone.
I then in mobile odin pro open the stock firmware from above and had it set to boot into download mode.
I flashed and let it open in download mode.
I then used Odin 3.09 to flash the firmware radio file with no reboot.
Then flashed the kernal in a seperate file.
Rebooted the phone into recovery to let it complete steps.
Then rebooted the phone normally.
Everything seems to have loaded up okay for me now.
Will try for a few days and report back. But is seems to have worked okay.
Click to expand...
Click to collapse
Please post a screen shot of your about phone, showing all the file infos,
Thanks
I got it rooted just now but the root doesn't not work properly busybox is n ot installing correctly and rootchecker is hanging BUT cupid says it is rooted
ashraf sharif said:
im getting an invalid md5 in pc odin. have you been able to flash this?
ok I got the firemware only file to flash in odin but I had to rename the file from .tar.md5 to .tar.
Click to expand...
Click to collapse
That's probably because the OP renamed the file after repacking it. You really don't want to remove the .md5 and flash like that if at all possible, because that md5 checks the file's integrity.
Not, trying to hijack your thread @TheArtiszan but I have the Recovery, Kernel, Bootloader and Modem already repacked here:
aaricchavez said:
I know @The Sickness extracted and posted the modem.bin and NON-HLOS.bin already, but i've repacked the Modem, Bootloader, Kernel and Recovery separately as Odin flashable .tar's for anyone who needs them.
I've tested them all out and they work correctly for me, use at your own risk though. For G900T ONLY
Also, consider this: Warning flashing Bootloader/Modem/ FULL FIRMWARE LOLLIPOP
Bootloader/BL:
Bootloader
Phone/CP:
Modem
PDA/AP:
Kernel
Recovery
Also, not to be off topic. Just saw alot of people asking about them!
Thanks @AxAtAx for all the hard work you do, as always!
Click to expand...
Click to collapse
Will this work with Mobile Odin? The one found in the market? I'm currently traveling and don't have a PC and would love to pass time and upgrade to lollipop.
Sent from my SM-G900T using XDA Free mobile app
lightninbug said:
Will this work with Mobile Odin? The one found in the market? I'm currently traveling and don't have a PC and would love to pass time and upgrade to lollipop.
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
You will need a computer to flash the bootloader.
Sorry.
No way around that at this time.