Hey guys I've seen that a lot of people have been having trouble getting the bootloader unlock to work I made a tutorial for you to follow so make sure you follow the tutorial before asking questions. I've answered every question I could think of in this video so please watch it first. You must follow the directions! Please
https://youtu.be/ilteTn7EISk
Link to download the latest firmware for your Verizon Galaxy Note 3 to flash in Odin if you need to reinstall it before unlocking (if you have no luck with my instructions you should try flashing the firmware again with Odin so that you have a completely stock phone):
http://www.sammobile.com/firmwares/
How to root the Verizon Galaxy Note 3 on the latest firmware (0F1):
http://forum.xda-developers.com/ver...b6-of1-n900v-note-3-verizon-oneclick-t3333569
Official Verizon Galaxy Note 3 bootloader unlock thread:
http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
All files you will need for unlocking your Verizon Galaxy Note 3:
https://drive.google.com/file/d/0B83noRHOimrRdkhoWWxhR19QWGc/view?usp=drivesdk
Sent from my SM-N900V using Tapatalk
**TWRP AND FLASHING ROMS**
Now that your Verizon Galaxy Note 3 bootloader is unlocked is time to flash some roms. For this you will need TWRP. A simple way to obtain the latest and stay up to date with a couple clicks is TWRP with Flashify. You will not need Odin or a PC at all to do this.
STEP 1:
Download flashify: https://play.google.com/store/apps/details?id=com.cgollner.flashify
{
"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"
}
STEP 2:
Open the app and give it root access permissions when your Super User app prompts you with the regular pop-up.
STEP 3:
STEP 4:
STEP 5:
STEP 6:
Flash roms till you pass out lol. Don't forget to backup your files.
----------------------------------------------------------
**************************************
----------------------------------------------------------
USING TWRP:
*****Yes- Jasmine Rom 6.1 can be flashed with twrp*****
When you flash your first rom after unlocking your bootloader and flashing twrp it's best to start with a clean slate. Make sure you put the rom of your choice on your Micro SD card. Wiping everything ensures that you have as few errors as possible. When flashing completely new roms this is also advised to avoid any errors.
Sent from my SM-N900V using Tapatalk
**Jasmine Rom 6.1**
Official thread:
http://forum.xda-developers.com/showthread.php?t=2760380
Download link for Jasmine Rom 6.1 ZIP:
https://www.androidfilehost.com/?fid=24052804347812398
Sent from my SM-N900V using Tapatalk
i had my vzw note 3 sm-n900v of1 rooted and bl unlock
i reverted back to official stock OF1 with odin.
i noticed that emmc brick debug tool shows my CID as the dev version and not my original cid
i was wondering after i root it again do i need to change my cid back to original before i run "samsung_unlock_n3" or is it ok to run it with the new cid already like it is.
thanks and nice guide here
en11gma said:
i had my vzw note 3 sm-n900v of1 rooted and bl unlock
i reverted back to official stock OF1 with odin.
i noticed that emmc brick debug tool shows my CID as the dev version and not my original cid
i was wondering after i root it again do i need to change my cid back to original before i run "samsung_unlock_n3" or is it ok to run it with the new cid already like it is.
thanks and nice guide here
Click to expand...
Click to collapse
No just run the unlock tool again and you're good to go.
Sent from my SM-N900V using Tapatalk
alexp1289 said:
No just run the unlock tool again and you're good to go.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
i ran the tool with no busybox installed
odin says im developer edition
I tried to do this, but the phone wouldnt boot and it kept booting to a message that said ""system software not authorized by Verizon wireless has been found on your phone"
it also says "recovery is not seandroid enforcing"
nevermind, going back to stock, re-rooting, and re-unlocking the bootloader again seems to have fixed it
well
for some reasons above mentioned method isnt working at all in my case..
after giving all the commands in the terminal this is what it says.
it doesnt go further to the step where cid is displayed and device doesnt go for reboot .
(.)am on 4.4.2
(.)device is rooted
(.)on stock rom..
(.)never ever flashed anything to my device.
(.)i havent set up samsung account yet as a result there is no option in settings to disable reactivation screen but i did disable the lock screen before attempting anything on terminal..
urgent help needed
Sent from my SM-N900V using XDA-Developers mobile app
pakiyoungster said:
well
for some reasons above mentioned method isnt working at all in my case..
after giving all the commands in the terminal this is what it says.
it doesnt go further to the step where cid is displayed and device doesnt go for reboot .
(.)am on 4.4.2
(.)device is rooted
(.)on stock rom..
(.)never ever flashed anything to my device.
(.)i havent set up samsung account yet as a result there is no option in settings to disable reactivation screen but i did disable the lock screen before attempting anything on terminal..
urgent help needed
Sent from my SM-N900V using XDA-Developers mobile app
Click to expand...
Click to collapse
Flash 0F1 firmware the unlock method doesn't work on the firmware version that you're on. Follow my links in the first post to update firmware.
Sent from my SM-N900V using Tapatalk
secure fail: recovery
Followed the instructions, ended up with a soft bricked phone. Back to odin to re-flash OF1 I guess...
Using Flashify to flash TWRP after everything else looked great, rooted, bootloader unlock seemed to take.
Now looks like knox has me locked up and no path but to re-flash.
What did I miss?
tw3ak.
Thanks for the links and turorials. Will the Darklord N5 rom run on the Verizon note 3 after taking these steps?
Thanks.
tw3ak said:
Followed the instructions, ended up with a soft bricked phone. Back to odin to re-flash OF1 I guess...
Using Flashify to flash TWRP after everything else looked great, rooted, bootloader unlock seemed to take.
Now looks like knox has me locked up and no path but to re-flash.
What did I miss?
tw3ak.
Click to expand...
Click to collapse
If you saw a "secure fail: recovery" message you were not unlocked. (You were rooted, which allowed you to flash a recovery, but not unlocked)
If you are unlocked the Odin/Download screen will say "MODE: DEVELOPER" at the bottom of the text block at the top left side of the screen.
It is doubtful you were soft-bricked either. You might have been stuck in a "reboot to recovery every time loop" (which would then give you a secure boot: fail message)
but you can get out of that with the following:
- pull battery; wait a few seconds; reinsert battery
- hold down VolDown+Home+Power to start phone
- choose "Cancel" when the phone gives you the warning pop-up message about using Odin mode.
Sm-n900v (Rooted)
Android 5.0,
Baseband N900VVRUE0B6.
Will the unlock n3.zip work for me?
baabafadil said:
Sm-n900v (Rooted)
Android 5.0,
Baseband N900VVRUE0B6.
Will the unlock n3.zip work for me?
Click to expand...
Click to collapse
Based on my reading, it requires baseband OF1. You also need to do the CID check, to be sure your phone can be unlocked.
I did that already like post suggested n my Cid starts with 15
Related
Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"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"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}
Does automatically install Clockwork recovery?
danthepan124 said:
Does automatically install Clockwork recovery?
Click to expand...
Click to collapse
I believe it flashes TWRP recovery. Thats what I got from reading the change log here http://www.wugfresh.com/nrt/changelog/
Great job this looks awesome thank you for putting this together!
danthepan124 said:
Does automatically install Clockwork recovery?
Click to expand...
Click to collapse
If you check the "flash custom recovery" checkbox under root, then yes.. however it defaults to flash TWRP, unless the user selects CWM in the options menu:
It also will take care of renaming the system files to ensure its sticks, and it will install the busybox installer (free) app by Stericson.
{{ WugFresh }}
Nice. Will be nice to have this as a backup option . Definitely easier to use in terms of UI thank the Nexus 4 Root toolkit by mskip heh.
That backup option - is there a way, once unlocked and rooted, to grab my apps from the backup that were wiped, but not the entire thing? I downloaded about 8GB of apps before rooting, so I have no way to backup, I think. :[
Alright did it, rooted. Used the backup option a couple times trying to get it to work all the way, but for some reason, it only backed up about half of my apps.
The best rooting kit in the land
Sent from my Nexus 4 using xda premium
been waiting for this since the release of nexus 4, much thanks!
I've just added this toolkit to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium
Just unlocked and rooted my N4 with this... great piece of software as always Wug, thanks Donated you some cash.
Hey guys quick two questions:
1) When I was unrooting through this toolkit, it said that there were three files that were not found in the directory, but continued to go through the process regardless, and it appears that I was successful. I can't remember the names as the command prompt ended before I had the chance to screenshot it. Am I okay?
2) If I go through the unrooting process through this toolkit, and then the OEM Lock process, does that basically put my phone back to the way it was when I received it?
Thanks!
Thanks for this, while I know my way around the manual commands okay, this will make everything a breeze for me tomorrow when my Nexus 4 arrives.
Will turn on, get the newest OTA, then unlock and root with your app.
Out of interest, can you still get OTA updates on stock with a custom recovery installed, or do you need to keep the stock recovery? I plan on sticking with stock until the custom ROMs get more stable, so I will stay on a default recovery if I can't use OTA updates. Otherwise I'll just flash a custom recovery with your app and get it done for future use.
This might be a dumb question.. But can I use this to root my Nexus 4 without unlocking the bootloader (thus wiping data)? Or has there not been a way found to do that yet?
BraydenJames said:
This might be a dumb question.. But can I use this to root my Nexus 4 without unlocking the bootloader (thus wiping data)? Or has there not been a way found to do that yet?
Click to expand...
Click to collapse
Have to unlock 1st. Just back up everything to your pc and restore it after.
Was waiting for this, thanks!
Sent from my Nexus 7
Night Galaxy said:
Hey guys quick two questions:
1) When I was unrooting through this toolkit, it said that there were three files that were not found in the directory, but continued to go through the process regardless, and it appears that I was successful. I can't remember the names as the command prompt ended before I had the chance to screenshot it. Am I okay?
2) If I go through the unrooting process through this toolkit, and then the OEM Lock process, does that basically put my phone back to the way it was when I received it?
Thanks!
Click to expand...
Click to collapse
1.) Yes, those are sig files. They are always missing. For whatever reason google doesn't include sig files in their packages and fastboot still checks for them. I guess google doesn't bother because they are redundant considering you need to be unlocked flash stock with fastboot. I can't suppress that output, so it just always will say that.. no worries.
2.) Yes, not basically.. exactly. Everything will be wiped, and you device will be exactly as it was when you received it.
{{ WugFresh }}
Audioboxer said:
Thanks for this, while I know my way around the manual commands okay, this will make everything a breeze for me tomorrow when my Nexus 4 arrives.
Will turn on, get the newest OTA, then unlock and root with your app.
Out of interest, can you still get OTA updates on stock with a custom recovery installed, or do you need to keep the stock recovery? I plan on sticking with stock until the custom ROMs get more stable, so I will stay on a default recovery if I can't use OTA updates. Otherwise I'll just flash a custom recovery with your app and get it done for future use.
Click to expand...
Click to collapse
No, you need the stock recovery. That said, in advanced utilities of the toolkit their is a button just for restoring stock recovery, so you can just do that if you want to when an OTA comes out (assuming you didn't make any other big system mods) if you had previously flashed a custom recovery. Also.. you can use temp recovery whenever you want as long as you have access to a computer with the toolkit.
{{ WugFresh }}
im having trouble unrooting my device....i get to the part where it says press ok to install please be patient, and then a command pops up but nothing happens, it just stays there...
edit: i keep getting to the Flash stock and Unroot screen, but nothing happens at that point! help!
Are these the steps to unlock and root and be able to receive OTA updates?
1. Click on "Full Driver Installation Guide"
2. Connect phone to computer
3. Click on Unlock
4. Click on Root and leave "Custom Recovery" box unchecked.
Then, after OTA updates are installed, re-click "Root" since OTA update will unroot?
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
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).
Hello everyone (Sorry I'm french from Benin so excuse my faults)
I tried to flash the TWRP recovery on my Verizon S4 from Terminal Emulator. But when i tried to reboot into recovery, the phone stucked in a Startup failed screen. But with some chances, i was able to boot my phone back and run my system.
Now i want the stock recovery of my VRUGOF1 firmware so that my Recovery partition table will be filled with the stock one. Please help me to deal with that...
And also there is something very weird about this phone. I bought a used S4 Verizon from someone. But in the phone, it is said that this is the s4 i9500 model but the bootloader version is I545VRUGOF1. So I'm pretty much sure this is an Verizon S4. Am confused. The phone is unlocked so that it support carriers other than Verizon. I was planning to flash the stock latest lollipop update I545VRSGPL1 and see if my phone will come back to his normal state. But the clue is that i'm afraid of losing the carrier unlocking.
Please, help me....
EsperaKing said:
Hello everyone (Sorry I'm french from Benin so excuse my faults). I tried to flash the TWRP recovery on my Verizon S4 from Terminal Emulator. But when i tried to reboot into recovery, the phone stucked in a Startup failed screen. But with some chances, i was able to boot my phone back and run my system. Now i want the stock recovery of my VRUGOF1 firmware so that my Recovery partition table will be filled with the stock one. Please help me to deal with that... And also there is something very weird about this phone. I bought a used S4 Verizon from someone. But in the phone, it is said that this is the s4 i9500 model but the bootloader version is I545VRUGOF1. So I'm pretty much sure this is an Verizon S4. Am confused. The phone is unlocked so that it support carriers other than Verizon. I was planning to flash the stock latest lollipop update I545VRSGPL1 and see if my phone will come back to his normal state. But the clue is that i'm afraid of losing the carrier unlocking. Please, help me....
Click to expand...
Click to collapse
First of all, you can't flash TWRP on an S4 with OF1 firmware because the bootloader is locked up.
If you require the Verizon S4 Stock OF1 firmware, i have them all on the my File Host Account here (just unzip the file):
https://www.androidfilehost.com/?w=files&flid=158750
Good Luck!
~~~~~~~~~~~~~~~
I Am The Egg Man,
They Are The Egg Men.
I Am The Walrus!
Coo Coo Cachoo!
Thanks you @Ibuprophen, I will download the ROM from your link. You're right about the TWRP recovery. But, what do you think I can do in order to flash a custom recovery on my phone so that I can install the S4 S8 WizCyan Rom on my phone? I thought there was an loki bypass method since 2013 that was used to bypass the bootloader lock.
Also, I was asking if flashing the stock rom of the phone won't re-lock the carrier.
Thanks you again. :
EsperaKing said:
Thanks you @Ibuprophen, I will download the ROM from your link. You're right about the TWRP recovery. But, what do you think I can do in order to flash a custom recovery on my phone so that I can install the S4 S8 WizCyan Rom on my phone? I thought there was an loki bypass method since 2013 that was used to bypass the bootloader lock.
Also, I was asking if flashing the stock rom of the phone won't re-lock the carrier.
Thanks you again. :
Click to expand...
Click to collapse
Root then flash ROM with Flashfire. Bootloader is locked, custom recovery cannot be installed. Yes, it probably will "re-lock carrier". Root methods are in the General Section of this forum.
{
"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"
}
bilgerryan said:
Root then flash ROM with Flashfire. Bootloader is locked, custom recovery cannot be installed. Yes, it probably will "re-lock carrier". Root methods are in the General Section of this forum.
Click to expand...
Click to collapse
Thanks you bilgerryan for replying me.
So, I can flash the S4 S8 WizCyan ROM with FlashFire? That's good to know. I'm already rooted with Kingroot.
But, about the carrier lock, I learnt somewhere that it's most likely an hardware lock, so if it's unlocked once, it's means that it won't re-lock after flashing or anything. Because, before this phone, I bought an S4 AT&T i337 which was unlocked and I restored it's Stock rom with odin, afrer that, the carrier was still unlocked so it's worked with an non AT&T network. I was wondering if it'll be the same with this one too (S4 Verizon i545).
Thanks you again...
EsperaKing said:
Thanks you bilgerryan for replying me.
So, I can flash the S4 S8 WizCyan ROM with FlashFire? That's good to know. I'm already rooted with Kingroot.
But, about the carrier lock, I learnt somewhere that it's most likely an hardware lock, so if it's unlocked once, it's means that it won't re-lock after flashing or anything. Because, before this phone, I bought an S4 AT&T i337 which was unlocked and I restored it's Stock rom with odin, afrer that, the carrier was still unlocked so it's worked with an non AT&T network. I was wondering if it'll be the same with this one too (S4 Verizon i545).
Thanks you again...
Click to expand...
Click to collapse
You'll need SuperSU instead of KingRoot to use Flashfire, there's also a guide for that in the General section of this forum.
@bilgerryan @Ibuprophen
Okay, thanks you.
So what are you saying about the carrier. Should I restore? Or not?
EsperaKing said:
@bilgerryan @Ibuprophen
Okay, thanks you.
So what are you saying about the carrier. Should I restore? Or not?
Click to expand...
Click to collapse
You really don't need stock recovery, I wouldn't if I were you. Anything that can be done in stock recovery can be done through Flashfire.
Okay @bilgerryan
1- The system sometimes restarts bt itself and after restart it's stuck on com.android.system has stopped, so I thought that restoring it would fix those problems. Also the phone show model i9500 and bootloader i545, I will attach the screen shot.
2- I tried to replace king root with supersu with SuperSume app, no sucess. I also tried with terminal emulator, it shows failed and it uninstall king root. And permanently pop-up com.android.kinguser has stopped until I restart the phone. After restarting root is gone.
So I want to restore in other to restart all this from fresh stock firmware. But if you have any other ideas, please let me know how to just get root with supersu and use flashfire...
Thanks for replying. ...
EsperaKing said:
Okay @bilgerryan
1- The system sometimes restarts bt itself and after restart it's stuck on com.android.system has stopped, so I thought that restoring it would fix those problems. Also the phone show model i9500 and bootloader i545, I will attach the screen shot.
2- I tried to replace king root with supersu with SuperSume app, no sucess. I also tried with terminal emulator, it shows failed and it uninstall king root. And permanently pop-up com.android.kinguser has stopped until I restart the phone. After restarting root is gone.
So I want to restore in other to restart all this from fresh stock firmware. But if you have any other ideas, please let me know how to just get root with supersu and use flashfire...
Thanks for replying. ...
Click to expand...
Click to collapse
In that case, you'll probably have to restore stock with Odin and start over.
bilgerryan said:
In that case, you'll probably have to restore stock with Odin and start over.
Click to expand...
Click to collapse
Okay, I will restore in a few minutes and let you know.
bilgerryan said:
In that case, you'll probably have to restore stock with Odin and start over.
Click to expand...
Click to collapse
Hi @bilgerryan and all xda members.
I restored the stock rom with Odin and everything goes fine. I rooted then replaced kingroot with supersu succesfully.
The problem now is that after installing supersu, I installed FlashFire and tried a backup of my system. The screen goes black with some blank text. After that, there is nothing else that happens. My phone will stay stucked on a black screen with a blue led on on top. But nothing happens, I have to pull battery and reinsert in other to power on my phone. I can't use Flashfire.
Hope you reply me....Thanks.
EsperaKing said:
Hi @bilgerryan and all xda members.
I restored the stock rom with Odin and everything goes fine. I rooted then replaced kingroot with supersu succesfully.
The problem now is that after installing supersu, I installed FlashFire and tried a backup of my system. The screen goes black with some blank text. After that, there is nothing else that happens. My phone will stay stucked on a black screen with a blue led on on top. But nothing happens, I have to pull battery and reinsert in other to power on my phone. I can't use Flashfire.
Hope you reply me....Thanks.
Click to expand...
Click to collapse
You have to use v.53 of Flashfire. The newer versions don't play nice, also a backup with Flashfire is useless, if you have a bootloop you wouldn't be able to use it anyways. You just Odin stock again if you have any problems.
bilgerryan said:
You have to use v.53 of Flashfire. The newer versions don't play nice, also a backup with Flashfire is useless, if you have a bootloop you wouldn't be able to use it anyways. You just Odin stock again if you have any problems.
Click to expand...
Click to collapse
I'm installing Flashfire v53 right now, so I will make you know if it's working or not. Thanks for responding.
EsperaKing said:
I'm installing Flashfire v53 right now, so I will make you know if it's working or not. Thanks for responding.
Click to expand...
Click to collapse
It has worked like a charm. Thanks you very much. This is the last step of setting my phone. I'm going to install the S8 S4 WizCyan Rom to my phone and let you know. It should work cause I have an Snapdragon S4. I will let you know. Thanks you again
EsperaKing said:
I'm installing Flashfire v53 right now, so I will make you know if it's working or not. Thanks for responding.
Click to expand...
Click to collapse
@bilgerryan @bilgerryan
I flashed the WizCyan Rom and it's finished succesfully I also managed to install add-ons from aroma file.
After reboot it's failed to load with software update failed. Kernel error. I don't why it's not working. The installation goes succesfully. Is it the aroma add-ons that I have installed? Or it's just that the ROM is not compatible with the S4 Verizon.
I don't know how to get that ROM work for me. I'm restoring stock with odin right now. I don't know if I should try again because I learnt on a youtube video that for some people, it might failled with a soft break the first time when we use Flashfire to attempt installing a ROM so we should just restore odin, wipe data and cache from recovery and restart the process and then it'll work.
Thanks you...
EsperaKing said:
@bilgerryan @bilgerryan
I flashed the WizCyan Rom and it's finished succesfully I also managed to install add-ons from aroma file.
After reboot it's failed to load with software update failed. Kernel error. I don't why it's not working. The installation goes succesfully. Is it the aroma add-ons that I have installed? Or it's just that the ROM is not compatible with the S4 Verizon.
I don't know how to get that ROM work for me. I'm restoring stock with odin right now. I don't know if I should try again because I learnt on a youtube video that for some people, it might failled with a soft break the first time when we use Flashfire to attempt installing a ROM so we should just restore odin, wipe data and cache from recovery and restart the process and then it'll work.
Thanks you...
Click to expand...
Click to collapse
That means you didn't follow the directions.
Go into flashfire and select the ROM you're gonna flash.
Select the of1 kernel tar.
Select the of1 WiFi fix.
Select a full wipe. (System, cache, data) and hold down on the wipe so you can swipe it to the top of your list.
Don't flash the addons.
i got pixel 6 and I've been planning to sell it, i tried to lock the bootloader but the commend didn't work i don't know why. After that i was trying to re flash the stock ROM via fastboot mode but for some reason flashing process aborted at particular point and phone wasn't booting, kept in bootloop .. google logo then restart and it went on.
after that i made a mistake which was i attempted to re lock the bootloader while phone was in bootloop and the process completed successfully.
now I'm not able to flash anything via fastboot as bootloader is locked and it's cannot get unloaded ..
is there anything i could do to reflash the stock image in this state? phone now doesn't boot .. only google logo the it restarts it self
{
"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"
}
abdulmajed1 said:
i got pixel 6 and I've been planning to sell it, i tried to lock the bootloader but the commend didn't work i don't know why. After that i was trying to re flash the stock ROM via fastboot mode but for some reason flashing process aborted at particular point and phone wasn't booting, kept in bootloop .. google logo then restart and it went on.
after that i made a mistake which was i attempted to re lock the bootloader while phone was in bootloop and the process completed successfully.
now I'm not able to flash anything via fastboot as bootloader is locked and it's cannot get unloaded ..
is there anything i could do to reflash the stock image in this state? phone now doesn't boot .. only google logo the it restarts it self
Click to expand...
Click to collapse
Try sideloading the OTA. Also, if you still have OEM unlocking enabled in Developer Options you can try using Android Flash Tool.
Lughnasadh said:
Try sideloading the OTA. Also, if you still have OEM unlocking enabled in Developer Options you can try using Android Flash Device not boot
Click to expand...
Click to collapse
Lughnasadh said:
Try sideloading the OTA. Also, if you still have OEM unlocking enabled in Developer Options you can try using Android Flash Tool.
Click to expand...
Click to collapse
Android Flash Tool can't be used on a locked bootloader. That being said, it's the best way to return the phone to stock state.
Sideloading the OTA is the only possibility of restoring the device in this situation. I don't think the Pixel Repair Tool works with the Pixel 6 yet.
Try booting to recovery mode and perform a factory reset.
Lastly...A "bricked" device is completely unresponsive. If the device boots, the screen works, and can be forced into bootloader/fastboot/recovery, it's not bricked.
V0latyle said:
Android Flash Tool can't be used on a locked bootloader. That being said, it's the best way to return the phone to stock state.
Sideloading the OTA is the only possibility of restoring the device in this situation. I don't think the Pixel Repair Tool works with the Pixel 6 yet.
Try booting to recovery mode and perform a factory reset.
Lastly...A "bricked" device is completely unresponsive. If the device boots, the screen works, and can be forced into bootloader/fastboot/recovery, it's not bricked.
Click to expand...
Click to collapse
All you need is OEM Unlocking enabled to use Android Flash Tool. You don't actually have to have your bootloader unlocked. The Flash Tool will do it for you.
Lughnasadh said:
All you need is OEM Unlocking enabled to use Android Flash Tool. You don't actually have to have your bootloader unlocked. The Flash Tool will do it for you.
Click to expand...
Click to collapse
No kidding? I wasn't aware of that!
Doesn't help in this situation, sadly.
V0latyle said:
Android Flash Tool can't be used on a locked bootloader. That being said, it's the best way to return the phone to stock state.
Sideloading the OTA is the only possibility of restoring the device in this situation. I don't think the Pixel Repair Tool works with the Pixel 6 yet.
Try booting to recovery mode and perform a factory reset.
Lastly...A "bricked" device is completely unresponsive. If the device boots, the screen works, and can be forced into bootloader/fastboot/recovery, it's not bricked.
Click to expand...
Click to collapse
I've tried sideloading the latests ota file but then the process got aborted.
it showed: failed to verify whole file signature.
I've tried both latest stable ota " Androd 12 " and beta as well
Lughnasadh said:
All you need is OEM Unlocking enabled to use Android Flash Tool. You don't actually have to have your bootloader unlocked. The Flash Tool will do it for you.
Click to expand...
Click to collapse
I'm not able to reach oem unlocking option since it cannot boot
abdulmajed1 said:
I'm not able to reach oem unlocking option since it cannot boot
Click to expand...
Click to collapse
Sideload the OTA. Make sure your Platform Tools are up-to-date. Make sure you are sideloading the OTA and not the factory image and it's the correct OTA for your device. Try different cables and ports. Re-download in case your original download got corrupted.
Lughnasadh said:
Sideload the OTA. Make sure your Platform Tools are up-to-date. Make sure you are sideloading the OTA and not the factory image and it's the correct OTA for your device. Try different cables and ports. Re-download in case your original download got corrupted.
Click to expand...
Click to collapse
already tried sideloading different ota versions, different ports and cables as well. There's no point
Have you tried the Android Flash Tool?
I don't know if it would work since I believe locking the bootloader also disables OEM Unlocking, but it's worth a try.
hello guys
I fixed the pixel
ٖ:
The problem was mostly from the laptop
I used an Bugjaeger Mobile ADB - USB OTG app and install beta update from adb update recovery
thanks