As always, a HUGE thanks goes to my partner in crime, @garwynn, for all the hard work he puts in on our site and all that he does for the community.
This Odin One-Click.exe contains the Stock NE5 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 NE5 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 NE5 Stock ROM One-Click.
SM-G900P_NE5_Stock_Unrooted (Compressed Archive).exe (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_NE5_Stock_Unrooted.exe was saved upon extract from the 7Zip archive.
Double-click on SM-G900P_ND2_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 NE5 build!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XDA:DevDB Information
[ROM][ODIN]SM-G900P NE5 (NE5 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 Link: http://www.rwilco12.com/forum/showthread.php?tid=825
Hey Rwilco thank you very much for these one clicks/ tars
I had one question:
What's the difference between these files (besides one being a one-click and the other being the original tar):
SM-G900P_NE5_Stock_Unrooted (Compressed Archive).exe
and
ALL_SPT_G900PVPU1ANE5_G900PSPT1ANE5_1750661_REV00_user_low_ship_MULTI_CERT.tar
Does the original tar contain the stock bootloader as well?
Thanks
Been using your one clicks throughout the last two years with much success so I thank you for that. I've searched and I just need some confirmation that using this one click will leave the Knox warranty bit intact as 0x0 if it's never been tripped? In my knowledge a custom recovery is what trips Knox and wasn't sure if flashing a stock recovery over stock would do the same? Thanks for your time.
fergie716 said:
Hey Rwilco thank you very much for these one clicks/ tars
I had one question:
What's the difference between these files (besides one being a one-click and the other being the original tar):
SM-G900P_NE5_Stock_Unrooted (Compressed Archive).exe
and
ALL_SPT_G900PVPU1ANE5_G900PSPT1ANE5_1750661_REV00_user_low_ship_MULTI_CERT.tar
Does the original tar contain the stock bootloader as well?
Thanks
Click to expand...
Click to collapse
Essentially the TAR and One-Clicks are the same. The primary difference is that the one-clicks use a simplified version of Odin that helps prevent user error.
I always include the stock bootloader unless otherwise specified in the OP.
deafboy said:
Been using your one clicks throughout the last two years with much success so I thank you for that. I've searched and I just need some confirmation that using this one click will leave the Knox warranty bit intact as 0x0 if it's never been tripped? In my knowledge a custom recovery is what trips Knox and wasn't sure if flashing a stock recovery over stock would do the same? Thanks for your time.
Click to expand...
Click to collapse
I honestly don't remember. My Knox counter was tripped within ten minutes of me getting home from the Sprint store.
I don't believe that flashing a 100% stock TAR or One-Click will trip it but I would have to defer to some of our other community members.
Knox still 0x0 for me.
rwilco12 said:
Essentially the TAR and One-Clicks are the same. The primary difference is that the one-clicks use a simplified version of Odin that helps prevent user error.
I always include the stock bootloader unless otherwise specified in the OP.
I honestly don't remember. My Knox counter was tripped within ten minutes of me getting home from the Sprint store.
I don't believe that flashing a 100% stock TAR or One-Click will trip it but I would have to defer to some of our other community members.
Click to expand...
Click to collapse
I had stock rom rooted (w/ Towelroot) and Knox 0x0. Did your One-Click and updated to NE5 with Knox still 0x0. Results may vary. Use as directed. And thanks for making the process so clear and easy!
Serious Issue
Tried flashing auto root and now im getting "firmware upgrade encountered an issue. Please select recovery mode in kis and try again." error message.
Went to sammobile to download firmware and it doesnt load into odin.
Cant get this phone on, can someone please help.
FingerBlastJ said:
Tried flashing auto root and now im getting "firmware upgrade encountered an issue. Please select recovery mode in kis and try again." error message.
Went to sammobile to download firmware and it doesnt load into odin.
Cant get this phone on, can someone please help.
Click to expand...
Click to collapse
Why not flash this one-click? That's what it's for...
OTA to 4.4.4
Should I be able to OTA to 4.4.4 after installing this? Seems I should but I get the "unauthorized" modification message.
Update to Android L from 4.4.2
I have a SM-G900P and it is rooted and I'm not sure if I should use this to be able to update to Android L.
Any help is appreciated.
Trevor1271 said:
I have a SM-G900P and it is rooted and I'm not sure if I should use this to be able to update to Android L.
Any help is appreciated.
Click to expand...
Click to collapse
If look around the forum here that is a Tarbell that would upgrade you to stock lollipop you might have to re-root after which there are direction for.
Update to Android L from 4.4.2
El.Dante565 said:
If look around the forum here that is a Tarbell that would upgrade you to stock lollipop you might have to re-root after which there are direction for.
Click to expand...
Click to collapse
I looked up Tarbell for Galaxy S5 Sprint and nothing came up. Could you possibly link me to the specific forum so I can head in the right direction?
Thank You.
Trevor1271 said:
I looked up Tarbell for Galaxy S5 Sprint and nothing came up. Could you possibly link me to the specific forum so I can head in the right direction?
Thank You.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3022826
Sent from my SM-G900P using Tapatalk
Update to Android L from 4.4.2
elwood said:
http://forum.xda-developers.com/showthread.php?t=3022826
Thank you for the link, but I tried to download it and it doesn't work.
I says that it downloads minutes later with 50 mb done saying that it is complete.
When I open it it just gives me the error that not all of the files are there.
I tried to download it on Firefox and Chrome and they both don't work.
Is it because of my internet because it is pretty bad (8 down).
Click to expand...
Click to collapse
Can anyone help me with a link or point me in the direction to get the stock NE5 kernel only?
Since this does not trip Knox (and void the warranty), can I use this package to downgrade from stock unrooted 5.0 to this 4.4.2?
FireMedic138 said:
Since this does not trip Knox (and void the warranty), can I use this package to downgrade from stock unrooted 5.0 to this 4.4.2?
Click to expand...
Click to collapse
No I dont think you can.
Sent from my SM-G900P using xda premium
I thought it would only trip Knox if you installed a new recovery. Since Odin bypasses the recovery, I thought it doesn't trip knox?
FireMedic138 said:
I thought it would only trip Knox if you installed a new recovery. Since Odin bypasses the recovery, I thought it doesn't trip knox?
Click to expand...
Click to collapse
Yes, you should be fine with Knox as long as you use odin and stay on stock recovery.
FireMedic138 said:
I thought it would only trip Knox if you installed a new recovery. Since Odin bypasses the recovery, I thought it doesn't trip knox?
Click to expand...
Click to collapse
I wouldn't put too much worry into Knox being tripped. I had to send my Tab S in to a Samsung repair center for a warranty repair. It was rooted with Knox tripped. Then didn't say a thing and I got my Tab S back (verified the S/N).
Related
Three new tools have been released or updated by their developers recently that may have a major impact on how we root and flash our phones. I will need to update the Guides with the new information, but first some confirmations are needed.
1) Chainfire has released a tool called Mobile Odin which will flash roms from the phone. There are two versions, Mobile Odin Pro which is available on the market for a small fee, and Mobile Odin Lite which is available free to xda members. Quoting from his thread: Flashing with Mobile ODIN does NOT increase your custom kernel flash counter or make the yellow warning triangle appear. This tool was updated today (November 28, 2011) to work with a host of new phones, including SGH-I777.
2) DooMLoRD has released DooMLoRD's Easy Rooting Toolkit (zergRush Exploit) which is reported to allow permanant rooting of our SGH-I777 phone without installing a custom kernel. This was most recently updated on November 16, 2011.
3) CLShortFuse developed SuperOneClick Root over a year ago, and recently updated it (November 10, 2011) to include the ZergRush exploit and SU 3.0.
With these tools, if they work as advertised on our phone, it will be possible to root and install custom software without incrementing the flash counter. When you have used one or more of these tools, I would appreciate it if you would post your results back here in this thread so I can gather information to update the [GUIDE] How to Flash Custom Binaries Without Ever Incrementing the Flash Counter!!
Thanks.
I have used the new version of SuperOneClick with the zergRush exploit to successfully root my SG2. However I will mention that the Unroot feature of SuperOneClick did not work. I simply used the unroot script DooMLoRD provided in his thread and I was able to unroot successfully. I am currently still unrooted as I have a business app I have to run that will not if it detects root. However, I assume either SuperOneClick or DooM's script will work once again if needed.
Will any of these tools reset flash counter and warning sign on already rooted phone?
I rooted without knowing these problems. Now I'm stuck with it.
Jig may or may not work, so didn't even try yet.
lambition said:
Will any of these tools reset flash counter and warning sign on already rooted phone?
I rooted without knowing these problems. Now I'm stuck with it.
Jig may or may not work, so didn't even try yet.
Click to expand...
Click to collapse
No. At some point we may figure it out to reset it through software, but until then only jigs reset the counter.
Sent from my páhhōniē
I recently noticed after flashing to UnNamed that the caution sign didn't appear. Has the ROM been developed to not trigger it or does it have to do with using the jig? I bought a jig a month ago from mobiletechvideo and I've only used it once. I've flashed CM7, Galnet MIUI and UnNamed since with no caution sign.
These tools will probably provide a new way to flash custom software without incrementing the flash counter. None of them will remove the warning triangle or reset the flash counter, however.
The only two ways to remove the warning triangle, and get the AT&T boot screen back, are 1) jig and 2) flash a stock kernel with Odin or Heimdall.
The only known way to reset the flash counter is with a jig.
The only thing that causes the I9100 boot screen with the warning triangle and increments the flash counter is flashing a custom kernel with Odin or Heimdall. So, you can flash with adb or Android Terminal Emulator or ClockworkMod Recovery, or appearantly with the new Mobile Odin, without incrementing the flash counter.
I'm definitely interested in hearing about peoples results using these tools. That is the main purpose of this thread. Thanks.
I used the DooMLoRD method, which is really easy, and it's been working for several weeks with no issues. I haven't needed to unroot, so haven't tried that yet.
[Edit] I haven't tried flashing a new rom, so I can't comment on the flashing without triangle. I just wanted root for a couple small issues, I'm going to wait to start flashing until some stable releases of ICS start appearing.
I've used SuperOneClick with Zerg to root, then installed Entropy's Daily Driver through Android Terminal then flashed UnNamed through CWM all without tripping any counters.
Love it!
So just confirming, when I get my S II, using your earlier guide that's a sticky, I'll be able to not increment the flash counter AT ALL (flashing Entropy's kernel through adb, then flashing the unNamed Rom via CWM, and also flashing the su package for root)?
Or should I wait a week or so for you to possibly update your guide, with an even more idiot-proof process?
Thanks again!
Thanks for sharing
avidmovies said:
So just confirming, when I get my S II, using your earlier guide that's a sticky, I'll be able to not increment the flash counter AT ALL (flashing Entropy's kernel through adb, then flashing the unNamed Rom via CWM, and also flashing the su package for root)?
Or should I wait a week or so for you to possibly update your guide, with an even more idiot-proof process?
Thanks again!
Click to expand...
Click to collapse
The guide is still good. I'd like to provide all the options though.
At this point, it is clear that rooting with either SuperOneClick or ZergRush will be part of step 2 in the guide, and may be easier than using Odin or Heimdall.
Still waiting for any information on Mobile Odin. If it's easy to use on our phones, it may be an improvement over steps 3 and 4.
Thanks!
Sent from my Nexus S 4G using Tapatalk
Used the zergrush root and then mobile odin to set my friends sgsii up with unnamed and icsrewed theme. Worked great without one issue.
Sent from my páhhōniē
gr8hairy1 said:
Used the zergrush root and then mobile odin lite to set my friends sgsii up with unnamed and icsrewed theme. Worked great without one issue.
Sent from my páhhōniē
Click to expand...
Click to collapse
Did you use lite or pro?
Could you describe using Mobile Odin, setting it up, how the flashkernel works, etc?
I downloaded the zergrush root package from the op. Then went to (edit):
http://forum.xda-developers.com/showthread.php?t=1347899
and downloaded mobile Odin lite.
First downloaded Samsung kies for the proper drivers then downloaded and opened zergrush. When you first open zergrush by opening 'run me' (i think it was called) it will tell you everything you need to have already done before plugging in your phone. It recommends changing your screen timeout to 10. I'm guessing this is for adb use, as adb can not connect to your phone if the screen is off.
I then plugged the phone in and pressed a key for it to start. All in all it took around 5 minutes. Majority of the time was processes coming up that waited 40 seconds. Guessing the phone was doing things that you couldn't see. At no time did I need to press anything on the keyboard or phone.
After that was done I opened mobile Odin lite. It gives you the choice of downloading the file you need or cancel. I already had the kernel I was going to flash, entropy512's dd, but I clicked download file just in case out would load the file for me. Well it didn't. It took my browser to:
http://forum.xda-developers.com/showthread.php?t=1347899
That's great for most users but I already had the zImage I wanted. I hit the back arrow which took me to a black screen, guessing mobile Odin. Hit back again and was at my home screen. Reopened mobile Odin, and after a few tries found out you need to hit cancel to continue on.
That gives you this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that:
The only main option is kennel, and that's all I neededafter choosing it I got:
It was stored on the root of my internal sdcard, so I selected internal and then seen:
It obviously automatically put the kernel at the top by itself. Picked it and then had:
Chose flash kernel, rebooted the phone, and it was done. Downloaded unnamed, used three button hold to get into recovery, sure enough CWM was there, chose unnamed. Rebooted and viola, custom rom. Through this whole process the boot screen never changd to i9100 with the yellow exclamation point or was the flash counter tripped.
Sent from my páhhōniē
(yeah, I typed that all on my phone, talk about a sore hand)
I guess after you open Odin, you pour a Guinness , then download the file you need or cancel?
@gr8hairy1
Nice write up. Very useful. I'll probably get a chance to install this and play around with it tomorrow. Couple questions though.
gr8hairy1 said:
I downloaded the zergrush root package from the op. Then went on the android market and downloaded mobile Odin lite.
Click to expand...
Click to collapse
Did you download the lite version from the market? I only see the pro version on the market, and Chainfire's thread also indicates to download the lite version from his thread.
...
After that was done I opened mobile Odin lite. It gives you the choice of downloading the file you need or cancel. I already had the kernel I was going to flash, entropy512's dd, but I clicked download file just in case it would load the file for me. Well it didn't. It took my browser to:
http://forum.xda-developers.com/showthread.php?t=1347899
That's great for most users but I already had the zImage I wanted. I hit the back arrow which took me to a black screen, guessing mobile Odin. Hit back again and was at my home screen. Reopened mobile Odin, and after a few tries found out you need to hit cancel to continue on...
Click to expand...
Click to collapse
Do you know what Chainfire means in his Mobile Odin thread by flashkernels? Did you have to download one? From your write up, it sounds like you didn't and Entropy's kernel flashed fine.
Thanks.
iainash said:
I guess after you open Odin, you pour a Guinness , then download the file you need or cancel?
Click to expand...
Click to collapse
Yeah buddy! Need to put that step in there.
Though I'm a yengling fan
Edit: lol, just seen my guinness spelling error. Nice to know swype appreciates a good beer
Sent from my páhhōniē
creepyncrawly said:
@gr8hairy1
Nice write up. Very useful. I'll probably get a chance to install this and play around with it tomorrow. Couple questions though.
Did you download the lite version from the market? I only see the pro version on the market, and Chainfire's thread also indicates to download the lite version from his thread.
Do you know what Chainfire means in his Mobile Odin thread by flashkernels? Did you have to download one? From your write up, it sounds like you didn't and Entropy's kernel flashed fine.
Thanks.
Click to expand...
Click to collapse
You're right, I downloaded it from xda. Not sure how I got that mixed up. I'll update my post. Though I had taken a vicodin, alieve, and 2 benedryl around 1am, and it was almost 2am when I posted that. Stupid butt surgery is kicking my butt.
And correct, I did not download his flashkernel. I was tempted to flash it to check out what it did but it wasn't my phone I was working on. I stuck with flashing what I knew would get me cwm, and flashed Entropy512's kernel. Flashed with no issue.
Sent from my páhhōniē
creepyncrawly said:
2) DooMLoRD has released DooMLoRD's Easy Rooting Toolkit (zergRush Exploit) which is reported to allow permanant rooting of our SGH-I777 phone without installing a custom kernel. This was most recently updated on November 16, 2011.
Click to expand...
Click to collapse
First I wanted to say THANK YOU for all your help. I was able to follow your guide to flash my phone with out incrementing the flash counter.
But before I did that I did try DoomLoRD root fix. It worked as advertised and was exactly how the instructions were documented. I had no issues.
Again big thanks to you for all your help!
This technique will not work if you have applied the OTA update from 18January2012. Go here: http://forum.xda-developers.com/showthread.php?t=2118348
This device is now unlocked to the point of development board status. After you finish this process, you will have the ability to destroy your device so make sure you flash CAREFULLY. Using only the files in this guide, there is no way to brick your device. Stay away from Odin once you've finished this process unless you're flashing back to stock.
TLDR version: Put your device into USB Debug Mode. Run CASUAL Injection 9. Flash the Suck It Verizon Bootloader with Odin3 If CASUAL calls you a Noob, flash the PIT and Bootloader Baseline package with Odin.
Introduction
The instructions have changed DRAMATICALLY since initial release. It's super simple. You are expected to be stock running I605VRALJB version of software. If you have modified your device using another procedure previous to this, undo it. This is where you start.
Prerequisites
any I605VRALJB stock bootloader and a stock ROM or a rooted stock ROM.
Downloads (in the order you need them)
The Pit File This is the stock i605VRALJB Pit file. It works to make your device partitions stock again. Flashing this will prepare your device for unlock.
The Bootloader Baseline package - Odin Package This is a stock I605VRALJB bootloader, params, kernel and recovery. Flashing this will prepare your device for unlock and relock your device in a safe manner. *This will reset your device if you screw up during the process so you can start over.
Odin3 is a tool from Samsung used to flash Odin packages.
CASUAL Suck It Verizon Injection 9 CASUAL stands for Cross-Platform ADB Scripting Universal Android Loader. In this case, it deploys the Suck It Verizon exploit. To use CASUAL you must enable "Settings>Developer Options>USB Debugging" on your device. CASUAL is used as an automation tool so that you don’t have to use ADB, watch for results, upload files, download files, make decisions and enter commands. CASUAL will make those determinations for you. This guide is much shorter because of it. Source code for CASUAL can be found at http://android-casual.googlecode.com. The exploit was designed by Ralekdev, packaged, tested and made safe by AdamOutler. --DON'T MIRROR, this is in development.
Suck It Verizon Bootloader 2- Odin Package provides a bootloader which has been modified to ignore all security checks at the highest level possible. This firmware runs every time you turn on your device. The SBoot's job is to validate Download Mode flashes. It also validates and executes the kernel. This bootloader will not validate, only download and execute. It will also allow you to flash anything you like, including firmware packages which will destroy your device. This bootloader replacement is not only a Bootloader Unlock, this is an IROM Unlock... The lowest level unlock possible. The bootloader was developed by Ralekdev, conceptualized by Rebellos, tested and packaged with a Sprint GN2 TWRP Recovery by AdamOutler.
Instructions
If these instructions dont quite make sense, check out the video below.
Part 1: Install the Baseline
Launch Odin or click the "reset" button at the bottom if it's already open.
Place the sch-i605-16gb.pit into the "PIT" section of Odin.
Place BootloaderBaseline2.tar.md5.gz into the "Bootloader" section of Odin.
Click Start
Part 2: Run the CASUAL Exploit
Put your device into development mode. Settings>Developer Options>USB Debugging
You need Java installed to double-click or run with "java -jar path_to_file.jar" Do you have java?
Click the "Root and Unlock Me Now!" button and accept( or continue) any notifications which may pop up on the phone or CASUAL.
When prompted by the phone, press the Volume Up key then continue to Part 2.
Part3: Install Suck It Verizon Insecure Bootloader+Recovery
Start Odin or click the "reset" button at the bottom if it's already open.
Place SuckItVerizon_Odin_Package2.tar.md5.gz into the "Bootloader" section of Odin
Click Start
You may now flash a custom ROM of your choice to your 100% IROM/Bootloader unlocked device. You are now Rooted and have the ability to install any CWM recovery zip with TWRP.
Video instructions
Troubleshooting Windows
Q. Why is CASUAL calling me a noob?
A. You need to Install the "Bootloader Baseline" with odin. We only support ONE bootloader, that's VRALJB.
Put your device into Odin Mode by powering on with Volume Down and Home pressed.
Put the BootloaderBaseline.tgz from above into the "Bootloader" section of Odin.
Click Start.
Q. Why am I bootlooping or the device won't boot?
A. You flashed the wrong thing at the wrong time. Flash the bootloader baseline in Odin, then repeat the instructions above.
Q.Why isn't CASUAL working correctly
A. Try redownloading the latest CASUAL package. Also make sure you're running the latest version of Java.
Q.Why is Odin is failing to open or use the package?
A. The download was damaged. Redownload it.
Q.Other unexplained problems?
A.Try using the proper drivers.
1. Go to device manger right-click and uninstall on the device.
2. Go to add/remove programs, uninstall any driver packages.
3. Unplug your device
4. Install Samsung Kies http://www.samsung.com/us/kies/
Q. How come CASUAL didn't start the first time?
A. Unplug and replug your device, or click CASUAL again and deal with both windows. This is a known issue. I cannot reproduce it in my development environment, it only happens on production compilations in JAR format and affects only Windows. If you'd like to submit a patch, you can get the source and I can add you as a contributor to http://android-casual.googlecode.com.
Q. Why won't CASUAL connect to the device?
A. If you've already installed the PROPER drivers, try disabling any firewalls. ADB uses a network connection to talk to your device. ADB is a network transparent protocol.
Q. I'm STILL having a problem.
A. Did you turn it off and then turn it back on again?
Troubleshooting Device
Q.Why does CASUAL fail to find a rooted device?
A. Check the SuperSU/Superuser Permissions app to verify that you have not inadvertently denied root access to shell.
Q. Why won't my phone start? why is it saying unauthorized software?
A. You unlocked, flashed something, then relocked. You need to flash back to stock VRALJB then repeat the unlock procedure. Use this guide http://forum.xda-developers.com/showthread.php?t=2040264
Q. I'm STILL having a problem.
A. Did you turn it off and then turn it back on again?
Pictures
Heres some pictures to show the newfound capabilities of your device.
TWRP Recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CASUAL
Verizon device running AT&T firmware
Verizon device running International Firmware
Download count of 63 from testing- Note, do not flash any i9300 ROMs.
Conclusion
Congratulations, You're Unlocked. Your Galaxy Note 2 has gone from the most secure device on the market, to the least secure device publicly available. Your device will now accept any flash. Be careful and dont flash with Odin again. Stick to CWM zip packages so as to lower your risk.
Reserved for technical details
Thanks everybody involved! quick question, you say not to odin flash after using this...does that mean we can not odin back to stock after this modification?
Edit* Yes you can odin back to a stock i605 rom only!
Thank you Adam. Really appreciate all your hard work
Sent from my SCH-I605 using Tapatalk 2
Thanks! Will report back downloading now
Sent from my SCH-I605 using xda app-developers app
You Rock!
droidstyle said:
Thanks everybody involved! quick question; you say not to odin flash after using this...does that mean we can not odin back to stock after this modification?
Click to expand...
Click to collapse
Yeah I would like to know that as well.
Can't wait to do thus after school! Can't wait for the roms to start flooding the forums.
Sent from my rooted galaxy note 2... U mad?
Amazing, I am speechless!!! Thanks for all your hard work!
awesome work thanks
Thanks for all your work
FTW
Very cool. Great stuff Adam. Suck it Verizon indeed. :highfive:
Well...2 hours to download the Revision3 file on our crappy work internet (but damned if I'm going to wait until I get home). At least I'll get to watch the successes/failures roll in in the meantime.
Also...you mention to stick to flashable zip packages. If I understand correctly, flashing through recovery will still run the typical recovery checks, but ODIN will not?
Is there any reason I can't use Heimdall?
If we want to relock later, we can just flash a stock bootloader?
I already have my system setup how I like it and would like to not have to overwrite it with Revision. Will CASUAL work anyways as long as I have the dependencies?
Thanks so much Adam and Team!
:good:
awesome!
Thank you everyone involved!
I'm assuming that when running AT&T firmware/international firmware it won't recognize our VZW SIM correct? Awesome work though! Super excited about this.
I just wanna thank all of you for Guinea pigging this (so to speak). I'm gonna wait for droidstyles broke down step by step before i do this. Its probably not as bad as I'm making it out to be but I error to the side of caution.
Has anybody actually done this with no problem yet??
This guy is the f*ckin' man!!!
Thanks to everybody involved! Cant wait, I might just leave work now
Sent from my SCH-I605 using xda app-developers app
Here is a way to gain root if you all ready have the latest NH5 or NK2 firmware on your phone.. This way you dont have to revert back to an older complete firmware. This method also does not wipe out any of setting or mods that you may have done before you decided to root, like ringtones, clock settings, alarm settings, notifications etc.... If you update to the latest firmware and you use wanam or xposed, You will have to re install the framework from xposed to get all you settings restored. Once you install the Xposed framework you will have to restart the phone, all the modules should be restored to the way it was before you did the update.....This method should not trip Knox.
Before you try this method, you should disable Lookout apk and go into settings-general-security and uncheck verify apps, also put a check on unknown sources, then under security policy updates, uncheck the update box, also make sure to uncheck send security reports. This should prevent any hang ups while trying to install super user apk and disabling knox hang.
After you get root and back on NH5 or NK2 you can go back and put those checks back only if you plan on using the Knox security stuff, but it is not necessary if you dont. It does not affect anything you do with your phone anyway. This is up to you to decide. HAPPY ROOTING.. LOL
Thanks goes to @iworkout for pointing it out, as i did not run into the hang under superuser install for i just automatically do this when i root a phone without thinking.
.
.
1. Download these files to your computer and unzip them.. (ATTENTION,,, These boot.tar are not the bootloader.tar that everyone thinks it is. These are just boot.img (Kernels) needed to root and return back to latest stock with root.)
A- NE6 Boot.Tar----- NE6 BOOT.ZIP<<<< This is the kernel to root with.
.
B- NH5 Boot.tar------ NH5 BOOT.ZIP <<<< Earlier firmware before NK2, you only need to use this if you want to stay on NH5 otherwise skip this one..
.
C- NK2 Boot.tar------ NK2 BOOT.ZIP <<<<< This is the latest TMO Firmware as of 11/10/2014.
Download these files to your phone:
.
C- Download Towel Root from here ( TowelRoot ), and SuperSu ( from the Play Store) to your Phone..
2. Once you have the files unziped, Open up PC ODIN 3.09 which you can get here PC ODIN 3.09 .
.
3. Once you have opened up PC odin, click on AP and load the NE6 boot.tar.md5 file into the slot.
.
4. Put your phone into Download mode, By powering off the phone and holding the volume down and home button at the same time and press the power button, once you see the phone start to boot let go of the power button and you phone should go to download mode, Make sure you press the volume up button to enter download mode.
.
5. Connect the phone to the computer, Make sure the PC ODIN sees your phone, (If not make sure you have the latest drivers loaded.) Once PC odin sees your phone and you have the file loaded in the AP slot, you can go ahead and start the flash, this should only take about 30 seconds to complete and the phone should reboot. Once your phone reboots you should have NE6 Kernel loaded onto you phone. You shouldnt have any fc's ( as i did this and did not have any FC's).
.
6. Once your phone reboots click on Towel root and click on " Make it Rain". Your phone should now have root, You can close towel root,
.
7. Open up SuperSu and install the Binarys into your phone, Make sure you click Normal install and not CWM/TWRP. You then will be prompted to Disable knoxs, You click yes, (I clicked disable and have had no side effects.) You will have to reboot to make sure Super user takes effect. You can check to see if you have root by downloading root checker of your choice from the playstore.
7a, If you some reason you get an error saying the super user failed to install, Dont worry, just reboot your phone and and re run super su apk and you will see that it actually did install super user, you can verify by using root checker to verify. You do not need to restore your phone back to stock and start over.
.
8.Once you verified that you have root, You can now go back to step 3 and load the NH5 or NK2 Boot.tar.mds into the AP slot of Odin, and follow steps 4- 5. That is it. You now should be back on the latest NH5 or NK2 kernel and have root. You can check by usng root checker and to see if all your info, you can download Samsung Phone Info from the playstore, and this will show you all the files and knoxs should be 0x0.
.
Here is the full T-Mobile Stock NK2 Rom, Just in case you have to Odin back to stock if you mess up after you root and or want to take the Official update, But be warned that Official updates from any carrier may block Root.
.
Download------ Stock Full NK2 Rom 11/10/2014.
Here is the full T-Mobile Stock NH5 Rom, Just in case you have to Odin back to stock if you mess up after you root and or want to take the Official update, But be warned that Official updates from any carrier may block Root.
.
Download------ Stock Full NH5 Rom.
If you are having issues with odin failing, I would try a different cable, one that is not usb 3.0. I have read on the forums that some people have been having issues with odin failing due to the new usb 3.0 cable that samsung has issued with the Galaxy S5. Most people are using computers that are not able to support 3.0 usb, and this may be an issue for some with odin. This is just an idea so it may or may not work for you. If it still fails i would try a different usb, maybe one on that is on the back of a desktop instead of one in front, and maybe a different computer all together..
.
.
I only use a windows (Currently using Window 7) / linux pc to do most of my work on android. So i know this method and odin works. It seems that some users are having issues with mac and odin, so be carefull. Personally if you plan on working on android you should purchase a cheap windows pc or laptop. Plus you can dual boot a win pc to do linux as well. Linux is what i use to do alot of my cooking of roms with. So if you are using an apple product to do your flashing, than unfortunatly I can not help you with that.. Sorry.
.
Now remember that I am not responsible if you void your warranty or if you break your phone. This method worked for me and i found it easier and quicker this way. If something did not work then you did something wrong or did not read the instruction correctly.
.
If this method helped you in any way please hit the thanks button .. If the Mods would like to make this a sticky, please do. Thanks
Can anyone confirm that this works
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for posting this method - I just got a new S5 that came with NH5 and was about to try it, but the files you linked to don't match the files in your description.
"NE6 BOOT.ZIP" links to a file called "NE6Kernel.zip"
In Step 3, you say it should unzip to "NE6 BOOT.IMG" but instead the file is "boot.tar.md5"
The same goes for your NH5 link & the file inside.
Should I just ignore the mismatched file names and follow the same instructions?
iworkout said:
Thanks for posting this method - I just got a new S5 that came with NH5 and was about to try it, but the files you linked to don't match the files in your description.
"NE6 BOOT.ZIP" links to a file called "NE6Kernel.zip"
In Step 3, you say it should unzip to "NE6 BOOT.IMG" but instead the file is "boot.tar.md5"
The same goes for your NH5 link & the file inside.
Should I just ignore the mismatched file names and follow the same instructions?
Click to expand...
Click to collapse
Yes just ignore the file names and follow the steps. Cause inside the zip they are correct file name--- Boot.tar.md5 is actually a kernel that you are installing to get root. And pc odin does not reconize any other name but boot.tar.md5. I tried to rename the files and odin rejected it. So when you unzip the Boot.Zip, you know whats inside of that folder. Also renamed the files in op to make it less confusing..
.
If This helps you please hit the thanks button..
galaxyuser88 said:
Yes just ignore the file names and follow the steps. Cause inside the zip they are correct file name--- Boot.tar.md5 is actually a kernel that you are installing to get root. And pc odin does not reconize any other name but boot.tar.md5. I tried to rename the files and odin rejected it. So when you unzip the Boot.Zip, you know whats inside of that folder. Also renamed the files in op to make it less confusing..
.
If This helps you please hit the thanks button..
Click to expand...
Click to collapse
Done. It worked exactly as you described. Only hiccup was when SuperSU first attempted to disable KNOX, I got a message in my notification panel, "Security notice: unauthorized actions have been detected - reboot to undo changes."
My phone came with Lookout security installed, so I don't know if that had anything to do with it. I went to task manager and stopped Lookout and SuperSU (which just seemed to be hanging) and ran SuperSU a couple more times. It said KNOX disabled on the 2nd run.
Rebooted & installed root checker, verified root, installed NH5 in Odin and then verified root again. Thanks!
iworkout said:
Done. It worked exactly as you described. Only hiccup was when SuperSU first attempted to disable KNOX, I got a message in my notification panel, "Security notice: unauthorized actions have been detected - reboot to undo changes."
My phone came with Lookout security installed, so I don't know if that had anything to do with it. I went to task manager and stopped Lookout and SuperSU (which just seemed to be hanging) and ran SuperSU a couple more times. It said KNOX disabled on the 2nd run.
Rebooted & installed root checker, verified root, installed NH5 in Odin and then verified root again. Thanks!
Click to expand...
Click to collapse
Yeah i didnt have that issue, as soon as i got the phone i disabled that lookout crap. Also already had the security check also disabled, as when you install apks from outside the playstore, you are told to disable the security checks.
I will have to add that to the op when i get home and at my laptop.
It works
It works as described. Only hiccup was disabling KNOX, SuperSU hung for a minute so I restarted and opened SuperSU again. It asked if I wanted to disable KNOX. I said yes and it disabled it successfully almost immediately..
Works!
nguyener said:
It works as described. Only hiccup was disabling KNOX, SuperSU hung for a minute so I restarted and opened SuperSU again. It asked if I wanted to disable KNOX. I said yes and it disabled it successfully almost immediately..
Click to expand...
Click to collapse
This was my only hangup, as well. Beyond that, everything went smoothly, and I have root access with no Knox trip.
nguyener said:
It works as described. Only hiccup was disabling KNOX, SuperSU hung for a minute so I restarted and opened SuperSU again. It asked if I wanted to disable KNOX. I said yes and it disabled it successfully almost immediately..
Click to expand...
Click to collapse
AndreTheShadow said:
This was my only hangup, as well. Beyond that, everything went smoothly, and I have root access with no Knox trip.
Click to expand...
Click to collapse
Yeah that is something with superuser and not the method. Maybe when they upgrade the supersu apk, it may correct that. But good to see that this helped out to acheive root for ya.
Thx worked like a charm. SuperSu did hang when i tried to disable knox. I just rebooted and used SuperSu again and it disabled with no problems. Now if someone could just point me to the volume boost hack I will be good. I cant find it for the life of me.
So by clicking "Disable Knox" will that prevent me from using ALL the apps like PayPal with FINGERPRINT login & Google Wallet to tap & pay? Isn't Knox also needed for private mode?
On the flip side, what if I click "NO" & keep Knox enabled? Can I still root? Will Knox counter be tripped?
Will this affect my ability to upgrade to Android L via normal stock method?
Does this affect anything like that negatively? I'm having trouble searching the internet for hours about these fine details. Thanks for this awesome bit of info!
Hypoxic1 said:
So by clicking "Disable Knox" will that prevent me from using ALL the apps like PayPal with FINGERPRINT login & Google Wallet to tap & pay? Isn't Knox also needed for private mode?
On the flip side, what if I click "NO" & keep Knox enabled? Can I still root? Will Knox counter be tripped?
Will this affect my ability to upgrade to Android L via normal stock method?
Does this affect anything like that negatively? I'm having trouble searching the internet for hours about these fine details. Thanks for this awesome bit of info!
Click to expand...
Click to collapse
Iam not sure what will not work if disable knox. I dont use anything that might need knox, so i can not help you there. I have had no negative affect from disabling knox.
You can always try it and see what happens. The worst thing you will have to do is odin back to stock and try again. This is how i found disabling knox did not affect my phone or the apks i use in anyway. Yes you can choose not to disable knox and you will still have root.
As far as upgrading, you can do it 2 ways.
1. Odin back to stock and take the upgrade. But be warned that if you take a stock update, you may lose the ability to root, if the update closes the holes.
2. You can wait for one of the great devs to take the update and clean it and post it in xda. This is the safer bet.
Thank you for the quick & informative response! I really do appreciate your time.
Hmm, I took the plunge & CAREFULLY read, re-read, re-read again to be sure of the instructions. It keeps giving me a fail now. When I click START in ODIN, it's like it doesn't wait for the phone to do it & gives me the fail. When looking at the phone, I can see the line/bar thing drawing from left to right & before it is finished "drawing" that line, ODIN gives me the fail. Great...
OK, got it to work by downloading the FULL 1.5GB files from another thread. But I still used YOUR instructions. Whew! What a task.
LOL, wow I messed up. Now I'm back on NH5 & it unrooted. OK, so now I've redone it again & back on a ROOTED NE6. I'm afraid to try the NH5 since it failed before & bricked my phone. Not sure how to proceed.
Hypoxic1 said:
OK, got it to work by downloading the FULL 1.5GB files from another thread. But I still used YOUR instructions. Whew! What a task.
LOL, wow I messed up. Now I'm back on NH5 & it unrooted. OK, so now I've redone it again & back on a ROOTED NE6. I'm afraid to try the NH5 since it failed before & bricked my phone. Not sure how to proceed.
Click to expand...
Click to collapse
Ok why did you go back to ne6? If you all ready were on nh5, than my methods works perfectly, except for a hiccup in su. Seems like you did something wrong. I would load the full factory stock nh5 rom thru odin and try my method again. This only works on a full nh5 stock rom. If you were on some other firmware(older) then trying to upgrade to nh5 with my file will not work. It is only the kernel and not the whole rom. Hence the title.
If pc odins fails before you start, then it sound like the drivers are not loaded correctly, or one of the files you downloaded is corupt. Check to make sure the md5 matches and or redownload the files again, and try to use chrome to download. Afh seems to have issues with other explorers. Dont ask cause i do not have a clue as to why. Also if you continue to have issue, i would try a different usb port, different cable and or a different pc.
I know this method works. For i have done it about 20 times, i like to flash stuff on my phone to see what works.
I did start with a new phone with NH5, but your method didn't take as stated in my prior post. I was extremely careful to follow the directions properly, as well. I just got this S5 brand new from T-Mobile the other day & already had latest NH5 on it.
So to UNBRICK my phone, I had to use the method by ashraf sharif (http://forum.xda-developers.com/tmo...tutorial-towelroot-onlatest-firmware-t2908019). But I'm afraid to proceed to updating to NH5 using his method, hence why I'm on NE6 at the moment.
Hypoxic1 said:
I did start with a new phone with NH5, but your method didn't take as stated in my prior post. I was extremely careful to follow the directions properly, as well. I just got this S5 brand new from T-Mobile the other day & already had latest NH5 on it.
So to UNBRICK my phone, I had to use the method by ashraf sharif (http://forum.xda-developers.com/tmo...tutorial-towelroot-onlatest-firmware-t2908019). But I'm afraid to proceed to updating to NH5 using his method, hence why I'm on NE6 at the moment.
Click to expand...
Click to collapse
If you are afraid to use my method, then purchase mobile odin pro and use that to upgrade to nh5. Read the thread were you got the full ne6 and follow his directions. I honestly can not understand what the issue is that you are having. Cause like i said before, I have done a full odin back to nh5 and used my method with no issues. My phone also came with NH5 from tmo. Sorry.
No, no. Don't be sorry. You're awesome for posting all this & helping me out. I have no idea why it did not work also since I've made no mods up to this point. I carefully read everything & did days of research prior to jumping into this on this phone. This sure isn't as easy as a Nexus device! I basically have OCD when I do this sort of stuff, so I carefully read every word many, many times.
Thanks for the "go ahead" tip on the mobile odin pro. I will do that since you recommend it. I'm just unsure how he states the bootloader needs to be flashed separately. I'm a bit scared of PC odin at this point, lol.
Hypoxic1 said:
No, no. Don't be sorry. You're awesome for posting all this & helping me out. I have no idea why it did not work also since I've made no mods up to this point. I carefully read everything & did days of research prior to jumping into this on this phone. This sure isn't as easy as a Nexus device! I basically have OCD when I do this sort of stuff, so I carefully read every word many, many times.
Thanks for the "go ahead" tip on the mobile odin pro. I will do that since you recommend it. I'm just unsure how he states the bootloader needs to be flashed separately. I'm a bit scared of PC odin at this point, lol.
Click to expand...
Click to collapse
That is why i figured out my method, too many steps with the other thread. I orignally did it his way many times on my phone and it does work, just alot of steps and it takes alot longer to flash and root and then flash again.. The problem with mobile odin pro is it doesnt flash all the files that a stock rom has in it, this is why you need to flash some files with pc odin and then the rest with mobile odin pro..
This came from Sammobile. I downloaded it so I can start working on a rooted ROM. You will need this to update the baseband, etc. anyway, so I figure I post it in case anyone needs it. This is the one to use to upgrade to stock 5.0.1. or return to full stock.
As usual, all at your own risk. Check MD5 before flashing!!
DOWNLOAD HERE
Enjoy...
snovvman said:
This came from Sammobile. I downloaded it so I can start working on a rooted ROM. You will need this to update the baseband, etc. anyway, so I figure I post it in case anyone needs it. This is the one to use to upgrade to stock 5.0.1. or return to full stock.
As usual, all at your own risk. Check MD5 before flashing!!
DOWNLOAD HERE
Enjoy...
Click to expand...
Click to collapse
MAN!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
...just... man.... i soft-bricked and my router was blocking sammobile for some reason. just finished restoring after kicking out bucks for a fast sammoblie download and playing Ethernet games
thanks though
Damn man if i only would have waited instead of making the jump early.....once u flash the or update via ota there's no way of flashing back to kk unless u didnt flash the lollipop bootloader....right?
dinaps86 said:
Damn man if i only would have waited instead of making the jump early.....once u flash the or update via ota there's no way of flashing back to kk unless u didnt flash the lollipop bootloader....right?
Click to expand...
Click to collapse
yeah, that's what happened to me. the boot loader was not having it. my system is still recovering. the boats are burned!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah... in general, if you odin'ed the stock package, which includes the bootloader, you can't go back to KK.
At this point, you guys can root and flash the recovery, and just wait for me to complete the deodexed ROM. At that point, you can just flash the ROM via recovery. You will already have the L bootloader and baseband.
There needs to be a real guide to rooting lollipop
Sent from my SM-N915P using XDA Premium HD app
snovvman said:
Yeah... in general, if you odin'ed the stock package, which includes the bootloader, you can't go back to KK.
At this point, you guys can root and flash the recovery, and just wait for me to complete the deodexed ROM. At that point, you can just flash the ROM via recovery. You will already have the L bootloader and baseband.
Click to expand...
Click to collapse
i accepted the OTA. i should have not done that, now i'm trapped
snovvman said:
Yeah... in general, if you odin'ed the stock package, which includes the bootloader, you can't go back to KK.
At this point, you guys can root and flash the recovery, and just wait for me to complete the deodexed ROM. At that point, you can just flash the ROM via recovery. You will already have the L bootloader and baseband.
Click to expand...
Click to collapse
So your saying you've tried to odin back to kk? Past samsung has always been pretty liberal with going backwards.
Rooting lollipop is the same as kitkat n snovman this .zip u posted can be flashed via recovery? Or u just posted the .tar to be flashed through Odin im goong to try n build a kernel for us to set sulinux to permissive bc i cant take not having viper4android
cvaria said:
i accepted the OTA. i should have not done that, now i'm trapped
Click to expand...
Click to collapse
Not at all. I was waiting for lolly to drop for root.. I just did the chainfire method and you're done.
Rooty
jdidtht said:
So your saying you've tried to odin back to kk? Past samsung has always been pretty liberal with going backwards.
Click to expand...
Click to collapse
I'm saying that based on what I have read and experienced, you *generally* cannot revert to a previous major version. Aside from bootloader issues, you may not be able to flash over the modem. This was the case with the Note 2 and 3. I have not tried with the Edge. If you do, please do report.
dinaps86 said:
Rooting lollipop is the same as kitkat n snovman this .zip u posted can be flashed via recovery? Or u just posted the .tar to be flashed through Odin im goong to try n build a kernel for us to set sulinux to permissive bc i cant take not having viper4android
Click to expand...
Click to collapse
This is the Samsung stock image, so it is not a recovery flashable zip. It is a tar that must be flashed via odin. It contains bootloader, baseband, and system image.
FYI--I am uploading a deodexed/zipaligned PRE-BETA rooted Lollipop as I write this. READ: PRE-BETA.
snovvman said:
FYI--I am uploading a deodexed/zipaligned PRE-BETA rooted Lollipop as I write this. READ: PRE-BETA.
Click to expand...
Click to collapse
Ready to test maybe i get xposed back working
Well, here goes nothing....
http://forum.xda-developers.com/not.../rom-sprint-note-edge-915p-5-0-1-oc8-t3082802
For what it's worth, on the regular Sprint Note 4 you can go back to KK once you have taken the Lollipop ota or odin'd the Lollipop tar. The bootloader is backwards compatible on the regular Note 4. However you cannot run a Lollipop rom using the previous KK bootloader. That definitely causes big problems. Another thing you have to keep in mind is that the Lollipop tar writes carrier partitions and other important partitions so you MUST either odin flash the lollipop tar or have taken the lollipop ota BEFORE you flash ANY stock or custom Lollipop ROM via custom recovery. And before you odin the stock Lollipop rom tar you have to first reboot into custom recovery and do the factory reset several times and also wipe system, cache, dalvic etc several times.Then reboot into download mode and flash the Lollipop tar. Do this first or else you will odin the Lollipop tar and have left over data which I guarantee will cause issues. You would think the rom tar would completely wipe these partitions but apparently this isn't happening because there are reports of left over data from previous roms after flashing the stock Lollipop rom tar. I would assume this would apply to the Sprint Note Edge also. This is just a heads up.
Surf and talk
Quick question. I just bought my edge today and I wanted to verify that If I root it I will be able to surf and talk correct?
platniumrover said:
Quick question. I just bought my edge today and I wanted to verify that If I root it I will be able to surf and talk correct?
Click to expand...
Click to collapse
Sounds like you have some reading to do. Educate yourself before you get started.
primo523 said:
Sounds like you have some reading to do. Educate yourself before you get started.
Click to expand...
Click to collapse
I have done alot of reading, just haven't been able to find much on the forum about it. So its true that the sprint variant only comes with one antenna? But the big question for me is how permanent is it? Because there is a chance of doing voice and data over the one antenna in the future. But I dont know which direction they are going. What are the correct strings to search on xda?
platniumrover said:
I have done alot of reading, just haven't been able to find much on the forum about it. So its true that the sprint variant only comes with one antenna? But the big question for me is how permanent is it? Because there is a chance of doing voice and data over the one antenna in the future. But I dont know which direction they are going. What are the correct strings to search on xda?
Click to expand...
Click to collapse
You can usually find a stock version of any device's firmware. That'll bring it back to unrooted factory condition. HOWEVER, keep in mind that Samsung has included a piece of software called Knox on their newer devices. As soon as you modify the firmware (which you will have to do for root), you will trip a counter that lets Samsung know the device is modified. Basically, your warranty is literally void as soon as you root your phone. There are some apps I've seen that try to undo this, but I'm not sure if they work.
But it really sounds like you don't know enough about root to go messing with it. Do more research first.
Here's a link to a pretty good guide that'll give you an idea of what rooting is for.
http://www.androidauthority.com/root-android-277350/
So I have a SCH-I545 I tried flashing OF1 Deodexed and it failed and now whenever I boot the phone or recovery it says
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is the thing at the top
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: SAMSUNG OFFICAL
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD : ENABLED
WRITE PROTECTION: ENABLED
eMMC BURST MODE: ENABLED
The phone was origanally OF1.
Here is what I tried
Running VZW software
Running Kies 3 (Just left a black screen on kies program)
Galaxyplayerman said:
So I have a SCH-I545 I tried flashing OE1 Deodexed and it failed and now whenever I boot the phone or recovery it says
Here is the thing at the top
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: SAMSUNG OFFICAL
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD : ENABLED
WRITE PROTECTION: ENABLED
eMMC BURST MODE: ENABLED
The phone was origanally OE1.
Here is what I tried
Running VZW software
Running Kies 3 (Just left a black screen on kies program)
Click to expand...
Click to collapse
Are you sure your not meaning OF1? Never heard of OE1 on the I545. That error has came up on me to if installation is interrupted like through Odin or vzw repair assistant. To correct your problem, it would be to simply Odin back to stock of what was on it first hand. Whether it be OC1 or OF1, just be sure you confirm what was on it before flashing anything or you could end up with a hard brick. I think if it is indeed OE1 then I believe you don't have the verizon variant. Ether that or you had the wrong firmware on it to begin with
bjf189 said:
Are you sure your not meaning OF1? Never heard of OE1 on the I545. That error has came up on me to if installation is interrupted like through Odin or vzw repair assistant. To correct your problem, it would be to simply Odin back to stock of what was on it first hand. Whether it be OC1 or OF1, just be sure you confirm what was on it before flashing anything or you could end up with a hard brick. I think if it is indeed OE1 then I believe you don't have the verizon variant. Ether that or you had the wrong firmware on it to begin with
Click to expand...
Click to collapse
Yes sorry I do mean OF1. Also when I got my phone it was originally from KitKat when I bought it and then I updraged it to Lollipop. Does that matter?
Yes it does matter. When you upgrade pretty much at all, your then blocked from downgrading. Meaning if you try to downgrade, you can get a hard brick or if in Odin, you'll get the error fail message. So that being said, do not try to go back to kitkat. To fix your problem, you'll need the get your hands on odin. 3.09 or greater I suggest. Next get the OF1 firmware from sammobile.com. Make sure you do get of1 firmware or you'll get a fail in Odin. Once you get those two things downloaded to your pc. Put your phone in download mode, connect it to your pc, open up odin, click the ap box in Odin and select the firmware of of1 and let it do check the md5 then hit start and let it load through an do it's thing. Then it should be Back to normal. If any problems, I'll upload it myself that contains everything in it for some firmwares leave things out to correct such problems. Let me know your result. Good luck
Alright I got some time and flashed via odin the OF1 Firmware Odexed and now it boots into setup and works for a few seconds then it goes black (like it turned off). Now it just flashes the samsung galaxy s4 logo and turns off (I can still boot into bootloader, no recovery though).
Anyone have any suggestions?
Never mind. Turns out the devices was dead. Now it's working again!
Galaxyplayerman said:
Never mind. Turns out the devices was dead. Now it's working again!
Click to expand...
Click to collapse
Glad to help. I was about to say, flashing stock firmwares corrects nearly all soft bricks. So if that didn't work, I was gonna guess it was hardware related. Anyways, glad to see your up am ruNing again.
bjf189 said:
Yes it does matter. When you upgrade pretty much at all, your then blocked from downgrading. Meaning if you try to downgrade, you can get a hard brick or if in Odin, you'll get the error fail message. So that being said, do not try to go back to kitkat. To fix your problem, you'll need the get your hands on odin. 3.09 or greater I suggest. Next get the OF1 firmware from sammobile.com. Make sure you do get of1 firmware or you'll get a fail in Odin. Once you get those two things downloaded to your pc. Put your phone in download mode, connect it to your pc, open up odin, click the ap box in Odin and select the firmware of of1 and let it do check the md5 then hit start and let it load through an do it's thing. Then it should be Back to normal. If any problems, I'll upload it myself that contains everything in it for some firmwares leave things out to correct such problems. Let me know your result. Good luck
Click to expand...
Click to collapse
im having the same problem. i have the sch i545. and i downloaded this tar file from this rwilco12 site and tried to flash it in odin and it failed cause my phone was on 5.01 and i think i downloaded the software from 2013 and now it says software repair required, use the verizon software repair assistant. and sammobile has their free downloads under maintenance for now lol.
Rhalium said:
im having the same problem. i have the sch i545. and i downloaded this tar file from this rwilco12 site and tried to flash it in odin and it failed cause my phone was on 5.01 and i think i downloaded the software from 2013 and now it says software repair required, use the verizon software repair assistant. and sammobile has their free downloads under maintenance for now lol.
Click to expand...
Click to collapse
i would suggest only getting any firmware from sammobile or a reputable source for if you get it from some random site, the firmware could be tampered with and have spyware or something bad in it. if your on 5.0 then i believe your gonna need OC1. if the OC1 fail in odin then youll need the latest of i believe OF1 which all those can be found on sammobile
bjf189 said:
i would suggest only getting any firmware from sammobile or a reputable source for if you get it from some random site, the firmware could be tampered with and have spyware or something bad in it. if your on 5.0 then i believe your gonna need OC1. if the OC1 fail in odin then youll need the latest of i believe OF1 which all those can be found on sammobile
Click to expand...
Click to collapse
i fixed it a couple weeks ago. had to pay sammobile at the time cause their free downloads were undergoing maintenance. with my phone out of commission i had to pay in order to get the stock rom. it was just me stupidly trying to go from 5.0 to an earlier version that cause the malfunction. i downloaded the stock rom from sammobile and flashed it using odin and everything works great. wat does oc1 mean?
If you were in need of the OF1 firmware I'm sure it's here on xda somewhere. You didn't have to pay for premium to get the firmware. As for oc1, it's just a build that came BEFORE OF1. OF1 is the latest. Both oc1 and of1 firmwares run 5.0 lollipop but even though they do, if your on of1, you can't even go back to oc1 for you will get a hard brick
Top Tip: Check out my debrick thread Could have saved some money.
bjf189 said:
If you were in need of the OF1 firmware I'm sure it's here on xda somewhere. You didn't have to pay for premium to get the firmware. As for oc1, it's just a build that came BEFORE OF1. OF1 is the latest. Both oc1 and of1 firmwares run 5.0 lollipop but even though they do, if your on of1, you can't even go back to oc1 for you will get a hard brick
Click to expand...
Click to collapse
as I said before. my phone was the same as yours shown in the photo where its says please use the verizon software repair assistant. hence, a soft brick. my phone was completely non operational. and of course when I went to the sammobile website to download the correct stock rom, they had a banner on their website that said their free downloads are suspended for system maintenance for the weekend but their paid downloads are fully operational. being that my phone was non functional as yours was in your photo, i deemed that this was an emergency and i wanted my phone back. so i deemed it neccessary to spend the 16 dollars us to sammobile to get my phone back. the stock rom took like 7 or eight hours to download but once i flashed it thru odin to my phone, my phone was fully operational and I could play pokemon go again. lesson learned: never use kingroot again. and never try to root again. and also dont try to downgrade form 5.0 to an earlier version. still dont know what of1 means.
Rhalium said:
as I said before. my phone was the same as yours shown in the photo where its says please use the verizon software repair assistant. hence, a soft brick. my phone was completely non operational. and of course when I went to the sammobile website to download the correct stock rom, they had a banner on their website that said their free downloads are suspended for system maintenance for the weekend but their paid downloads are fully operational. being that my phone was non functional as yours was in your photo, i deemed that this was an emergency and i wanted my phone back. so i deemed it neccessary to spend the 16 dollars us to sammobile to get my phone back. the stock rom took like 7 or eight hours to download but once i flashed it thru odin to my phone, my phone was fully operational and I could play pokemon go again. lesson learned: never use kingroot again. and never try to root again. and also dont try to downgrade form 5.0 to an earlier version. still dont know what of1 means.
Click to expand...
Click to collapse
It's the name of our particular bastard version of lollipop.