[ROM][ODIN]SM-G900P ND2 (ND2 Modem/Kernel/Bootloader/ROM - Full Restore - Unrooted) - Sprint Galaxy S 5 Android Development

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. He is the man!
Second, thanks to @vinman12 for posting the TAR here.
This Odin One-Click.exe contains the Stock ND2 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 ND2 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 ND2 Stock ROM One-Click.
SM-G900P_ND2_Full Restore_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_ND2_Full_Restore_UNROOTED.exe was saved upon extract from the 7Zip archive.
Double-click on SM-G900P_ND2_Full_Restore_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 ND2 build!
View attachment 2799603
XDA:DevDB Information
[ROM][ODIN]SM-G900P ND2 (ND2 Modem/Kernel/Bootloader/ROM - Full Restore - Unrooted), ROM for the Sprint Samsung Galaxy S 5
Contributors
rwilco12
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2015-02-10
Last Updated 2015-02-10

Download: http://www.rwilco12.com/forum/showthread.php?tid=787

Great work as usual. Your hard work is appreciated!
{
"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"
}

Hopefully i will never need to use this but thanks for your work!!

Nice to have this ty
Sent from my SM-G900P using Tapatalk

Will this restore knox to 0x0?
Sent from my SM-G900P using XDA Premium 4 mobile app

g.armour said:
Will this restore knox to 0x0?
Sent from my SM-G900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately it doesn't. It does reset system status to official but no change to Knox.
Sent from my SM-G900P using Tapatalk

So if this doesn't reset Knox is the phone warranty still void? Or is it good enough to use for warranty work?
Sent from my SM-G900P using XDA Free mobile app

Dgsaxhitman84 said:
So if this doesn't reset Knox is the phone warranty still void? Or is it good enough to use for warranty work?
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
Not yet, so far stock will not reset counter, warranty still voided.
---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------
I think stock rom far better versus modded roms. Feels more responsive especially for calling app which is mandatory for me and I'm sure for you too.
---------- Post added at 01:07 PM ---------- Previous post was at 01:07 PM ----------
rwilco12 said:
Download: http://www.rwilco12.com/forum/showthread.php?tid=787
Click to expand...
Click to collapse
What's this link?

Thanks for this rwilco12, great to have you here with us
Enviado desde mi SM-G900P mediante Tapatalk

HD-man said:
What's this link?
Click to expand...
Click to collapse
That's the link to my site where got can download the files from.
Sent from my SM-G900P using Tapatalk

Was pretty cool didn't even change the ROM and for some reason I didn't get the Sprint bootloader back.

Knox counter
will flashing this stock rom trip my knox count? my phone was rooted with towel root but having some issues with my phone. now i want to return it back to full stock

Thank you so much man! I wiped my phone clean of an O/S like a d*** and this helped out a lot. I know it wasn't much but I had to give you a little $ for that. Again, thank you!

Back to stock
Hi,
I currently have rooted S5, running MOAR with philz recovery. My phone has been running a bit wonky with quite a few problems and I think starting fresh as if I just opened the box with my shiny brand new S5 (instead of normal factory reset when flashing rom) would be the way to go. I have been searching and reading and to be honest, my head is spinning. I think this procedure is what I need to accomplish my goal :fingers-crossed: but just wanted to confirm. Appreciate any help!!

andee39 said:
Hi,
I currently have rooted S5, running MOAR with philz recovery. My phone has been running a bit wonky with quite a few problems and I think starting fresh as if I just opened the box with my shiny brand new S5 (instead of normal factory reset when flashing rom) would be the way to go. I have been searching and reading and to be honest, my head is spinning. I think this procedure is what I need to accomplish my goal :fingers-crossed: but just wanted to confirm. Appreciate any help!!
Click to expand...
Click to collapse
This is exactly what you need. However, I would suggest flashing TWRP and wiping internal storage before flashing. That way you are 100% brand new.

rwilco12 said:
This is exactly what you need. However, I would suggest flashing TWRP and wiping internal storage before flashing. That way you are 100% brand new.
Click to expand...
Click to collapse
Do you mean flashing TWRP and wiping internal storage before this procedure or after but before re-rooting and flashing rom? I would love to go back to using TWRP all the time but had heard there were issues if you ever needed to do a recovery so that is why I use philz, But I guess if you are referring to before this process then I could flash philz again after re-rooting.
Thanks so much for your assistance!

andee39 said:
Do you mean flashing TWRP and wiping internal storage before this procedure or after but before re-rooting and flashing rom? I would love to go back to using TWRP all the time but had heard there were issues if you ever needed to do a recovery so that is why I use philz, But I guess if you are referring to before this process then I could flash philz again after re-rooting.
Thanks so much for your assistance!
Click to expand...
Click to collapse
I would do it before and wipe data and internal. Then immediately boot to download mode and flash the one-click. You can root and flash Philz after that.

rwilco12 said:
I would do it before and wipe data and internal. Then immediately boot to download mode and flash the one-click. You can root and flash Philz after that.
Click to expand...
Click to collapse
Oakie dokie, that is what I will do. I do have one last question. When I rooted with CF Auto-Root and installed philz with Odin, you select the tar file in one of the boxes in Odin and then press start. Here it says to double click on exe, put phone in download mode and then press start in Odin. You don't need to select a file within Odin before pressing start? Hopefully not a completely dopey question.

Not a dopey question at all! The difference between this and most Odin packages is that this is in fact a One-Click Odin package. We have selected all the options and set everything up so that all you need to do is hit start and wait for the flash. No more accidentally loading something to the wrong slot or hitting the wrong button and having your device blow up in your hands. Ultimately it is the same process but simplified.

Related

[GUIDE] How to remove warning triangle w/ Mobile Odin

Gingerbread Guide
Ice Cream Sandwich use Triangleaway
First I would like to thank creepyncrawly!
If it wasn't for his post here, I wouldn't have bothered trying this method or writing this up.
USE AT YOUR OWN RISK!
**MIUI & CM7 USERS SCROLL DOWN**
1. Download Mobile Odin Lite (Download) or Pro (Market)
If using Lite then install this APK next - (Download)
2. Download and copy to device - StockKernel-PDA.tar
3. Open Mobile Odin > select Kernel > StockKernel-PDA.tar
4. Scroll down to FLASH FIRMWARE
It will now reboot, wait a few minutes...
5. After it reboots go back to Mobile Odin and flash Entropy or Siyah kernel using the TAR or zImage file (zips don't work).
MIUI & CM7 Users
1. Boot in recovery and do a Nandroid backup!
2. Wipe everything and restore to 2.3.4 or 2.3.6 based ROM (UnNamed, ShoStock, etc)
3. Download Mobile Odin Lite (Download) or Pro (Market)
If using Lite then install this APK next - (Download)
4. Download and copy to device - StockKernel-PDA.tar
5. Open Mobile Odin > select Kernel > StockKernel-PDA.tar
6. Scroll down to FLASH FIRMWARE
It will now reboot, wait a few minutes...
7. After it reboots go back to Mobile Odin and flash Siyah kernel using the TAR or zImage file (zips don't work).
8. Restore CM7/MIUI from the backup
INSTRUCTIONS FOR TRIANGLEAWAY TO BE POSTED LATER!
If this helped you in anyway please show your THANKS!
Cause we all love pictures.
{
"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"
}
Other than pictures, how does your thread differ from this one that already has a detailed step by step on how to use Mobile Odin?
Red5 said:
Other than pictures, how does your thread differ from this one that already has a detailed step by step on how to use Mobile Odin?
Click to expand...
Click to collapse
That's to avoid the triangle, this is if you have it already and want to do everything without a computer.
LiLChris06 said:
That's to avoid the triangle, this is if you have it already and want to do everything without a computer.
Click to expand...
Click to collapse
Your title says how to remove warning triangle. Avoid, remove... its the same thing. The other thread gives step by step on how to remove, avoid and how to use Mobile Odin all in one shot.
So again, how does this thread differ?
Red5 said:
Your title says how to remove warning triangle. Avoid, remove... its the same thing. The other thread gives step by step on how to remove, avoid and how to use Mobile Odin all in one shot.
So again, how does this thread differ?
Click to expand...
Click to collapse
I guess I missed it but where does it show in that guide how to remove it using Mobile Odin? I see how to flash a new kernel without ever getting the triangle.
His other guide here (which is in the OP), shows how to remove it with a computer.
If its there and I am blind then by all means you can close the thread and I am sorry.
Thanks for the write up!
Sent from my AT&T cellular device.
Are you sure that this removes the warning sign?
Since it's an on-device flash I'd be shocked if it removes it. Only download mode (Odin/Heimdall) flashes trigger changes to the warning screen. That's how we can flash custom kernels on-device without triggering it.
Thanks.. finally that annoying triangle is gone!!!
Just did it following the op's instructions and it does remove the triangle on boot. After flashing entropy's 1/23 release cause it was a tar file there still wasn't a triangle. I then flashed his 1/29 release via cwm and there is still no triangle on boot.
Thanks op for a quick, easy, and painless way of getting rid of it.
Entropy512 said:
Are you sure that this removes the warning sign?
Since it's an on-device flash I'd be shocked if it removes it. Only download mode (Odin/Heimdall) flashes trigger changes to the warning screen. That's how we can flash custom kernels on-device without triggering it.
Click to expand...
Click to collapse
Yup I did it last night if you want I can do a video but that's not till the weekend if I get a chance.
Sent from my SAMSUNG-SGH-I777 using XDA App
Confirmed. Totally got rid of the stupid triangle. Very easy.
Sent from my SAMSUNG-SGH-I777 using XDA App
wilberatilioa said:
Thanks.. finally that annoying triangle is gone!!!
Click to expand...
Click to collapse
NJGSII said:
Just did it following the op's instructions and it does remove the triangle on boot. After flashing entropy's 1/23 release cause it was a tar file there still wasn't a triangle. I then flashed his 1/29 release via cwm and there is still no triangle on boot.
Thanks op for a quick, easy, and painless way of getting rid of it.
Click to expand...
Click to collapse
Karashta said:
Confirmed. Totally got rid of the stupid triangle. Very easy.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Good to know!
Glad I can help this awesome community.
LiLChris06 said:
Good to know!
Glad I can help this awesome community.
Click to expand...
Click to collapse
This is awesome! Thanks a bunch! One more question (probably an ignorant one) - if one flashes a new ROM, lets say CM7 after UnNamed, does the triangle reappear?
AtlanM87 said:
This is awesome! Thanks a bunch! One more question (probably an ignorant one) - if one flashes a new ROM, lets say CM7 after UnNamed, does the triangle reappear?
Click to expand...
Click to collapse
As long as you use CWM from Entropy or Siyah Kernel it should be fine and the triangle wont appear.
Weird... If an internal flash of a stock binary will clear the triangle, that makes things a LOT easier for people.
Worked perfectly on the bus home from high school it never really bothered me but was easy enough so i figured why not do it
Sent from my SGH-I777 using XDA App
Entropy512 said:
Weird... If an internal flash of a stock binary will clear the triangle, that makes things a LOT easier for people.
Click to expand...
Click to collapse
Yup, now nobody should be complaining about the triangle since there is many ways around it.
Nick281051 said:
Worked perfectly on the bus home from high school it never really bothered me but was easy enough so i figured why not do it
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
Could someone please explain this to me.
Facts as I understand them:
Mobile Odin uses a "flash kernel" to flash most of the elements of the software. However, it is possible to use Mobile Odin lite without the "flash kernel" to flash a kernel. The "flash kernel" is actually a version of ClockworkMod Recovery that is loaded by Mobile Odin. My assumption then is that Mobile Odin flashes the kernel internally, and then boots into ClockworkMod Recovery, its "flash kernel", to flash the rest of the software.
We currently understand that anything flashed with ClockworkMod Recovery does not affect the flash counter or the yellow warning triangle, but appearantly, Mobile Odin does not use its "flash kernel" to flash the kernel?
Charifire makes the following statement in the OP of his Mobile Odin thread:
Flashing with Mobile ODIN does NOT increase your custom kernel flash counter or make the yellow warning triangle appear.
Click to expand...
Click to collapse
So, the puzzle and the question is, if flashing a custom kernel with Mobile Odin does not make the yellow warning triangle appear, then why does flashing a stock kernel with Mobile Odin remove it?
Hmm, seems worth a try.
Odin is taking forever "dumping" since this device isn't supported. Weird.

[Q] Cant get in bootloader Help please

I tried to flash resurrection remix rom on my sgs2. But it did not boot after installation.
Now I can't get in my recovery to do a restore. It stuck on the screen which says Samsung galaxy sII
Please help I don't know what to do
Linda90 said:
I tried to flash resurrection remix rom on my sgs2. But it did not boot after installation.
Now I can't get in my recovery to do a restore. It stuck on the screen which says Samsung galaxy sII
Please help I don't know what to do
Click to expand...
Click to collapse
Just a bootloop, give this a go: http://forum.xda-developers.com/showthread.php?t=1108499
You will lose all data although, nothing on external sd card will be lost.
Also, how did you flash the ROM? If you followed the guide step-by-step, you shouldn't have ended up in a bootloop.
I wiped all partitions and then flashed the zip file.
Is it with a bootloop that you even can't get in to recovery? I'm stuck on samsung logo, not on RR logo
Linda90 said:
I wiped all partitions and then flashed the zip file.
Click to expand...
Click to collapse
Ok, well give the thread I linked above a go. You can download stock ROM's from sammobile.com, and flash through Odin. Do you know how to use Odin?
---------- Post added at 10:31 PM ---------- Previous post was at 10:23 PM ----------
Linda90 said:
I wiped all partitions and then flashed the zip file.
Is it with a bootloop that you even can't get in to recovery? I'm stuck on samsung logo, not on RR logo
Click to expand...
Click to collapse
Ah I'm stupid! You need to get into recovery for that thread! You're definitely holding the correct buttons when the phone is fully off (home + power + volume up)?
I think I will give it a go. But the threat says that you should do it from your recovery, or if you are not comfortable with the recovery way you should do it via odin. I can't get in recovery, so maybe I have an other problem..
I'm honestly a little scared of odin.
once I had to do something with odin, but that failed. so I could not get out download mode..
Linda90 said:
I think I will give it a go. But the threat says that you should do it from your recovery, or if you are not comfortable with the recovery way you should do it via odin. I can't get in recovery, so maybe I have an other problem..
I'm honestly a little scared of odin.
once I had to do something with odin, but that failed. so I could not get out download mode..
Click to expand...
Click to collapse
This is taken straight from my rooting guide. It will help you correctly set up Odin:
First off, you need Odin, which is a flashing tool specifically designed for the SGS2: Just type in "Odin 1.85" without quotations into Google and the first result should display "Odin - xdadevelopers - XDA Developers." Click on the link and Odin will download.
Now before going ahead with Odin, download Kies: http://www.samsung.com/us/kies/ ,which is like iTunes for Samsung Devices, the drivers are needed for Odin, but when the drivers have been installed, close Kies, right click on your toolbar at the bottom of your desktop, I'll assume your running Windows 7, and go into Task Manager. Now find anything with Kies running in the Task Manager, right click on them and kill them.
Once you have done this, go to "sammobile.com", sign up and download a stock ROM for the GT-I9100. I'll assume you have the international SGS2, just remove your battery and make sure it isn't the GT-I9100G. Then flash via Odin by connecting your phone, making sure Odin is configured like above, and then putting your phone in download mode, connecting it to your PC and put the file you downloaded in the PDA section and flash.
themadba said:
Ah I'm stupid! You need to get into recovery for that thread! You're definitely holding the correct buttons when the phone is fully off (home + power + volume up)?
Click to expand...
Click to collapse
Yes definitely!
Linda90 said:
Yes definitely!
Click to expand...
Click to collapse
Here is a link to the stock firmware for the GT-I9100 in the UK on my operator: http://www.sammobile.com/firmware/?page=3&model=GT-I9100&pcode=O2U&os=1&type=1#firmware
Scroll up just above the table of firmwares and choose your country and operator if possible.
themadba said:
Here is a link to the stock firmware for the GT-I9100 in the UK on my operator: http://www.sammobile.com/firmware/?page=3&model=GT-I9100&pcode=O2U&os=1&type=1#firmware
Scroll up just above the table of firmwares and choose your country and operator if possible.
Click to expand...
Click to collapse
Oke, so I need to flash an other rom through Odin and everything sould work?
Is it possible to flash a nandroid backup of my previous rom through Odin wich are on my sd?
I'm afraid the square in odin doesn't become green.. :angel:
Linda90 said:
Oke, so I need to flash an other rom through Odin and everything sould work?
Is it possible to flash a nandroid backup of my previous rom through Odin wich are on my sd?
I'm afraid the square in odin doesn't become green.. :angel:
Click to expand...
Click to collapse
Yes, if you can't get into Recovery Mode, a new flash is your only saviour. When you have flashed the ROM and hopefully everything went well, you can root your ROM by using Chainfire's CF-Root. Then you could restore a backup.
I have also a zip-file of my previous rom on my sd-card. That was codename lungo. Can I flash that zip so i don't neet to re-root lik you said?
Linda90 said:
I have also a zip-file of my previous rom on my sd-card. That was codename lungo. Can I flash that zip so i don't neet to re-root lik you said?
Click to expand...
Click to collapse
Do you know what it is/does? Also, the guide I took that segment on setting up Odin was actually written for rooting your ROM with CF-Root.
Oh, its a ROM. My bad! Well, I'm not too sure. I think if you have a backup of it, that would be safer. Rooting is real easy anyway.
Is Codename Lungo not a HTC Sensation ROM?
Oke thank you.
I will download the stock firmware from sammobile, and try to flash it with Odin. I just want it to work again (root or no root) and not have to buy a new phone
Linda90 said:
Oke thank you.
I will download the stock firmware from sammobile, and try to flash it with Odin. I just want it to work again (root or no root) and not have to buy a new phone
Click to expand...
Click to collapse
Don't thank me till it's working! Once new ROM flashed and booted, let me know.
By the way, don't use the .PIT file if one is included in the download, if you get PDA, PHONE and CSC, put in appropriate sections of Odin and flash, if just one file, put in PDA section and flash.
themadba said:
This is taken straight from my rooting guide. It will help you correctly set up Odin:
First off, you need Odin, which is a flashing tool specifically designed for the SGS2: Just type in "Odin 1.85" without quotations into Google and the first result should display "Odin - xdadevelopers - XDA Developers." Click on the link and Odin will download.
Now before going ahead with Odin, download Kies: http://www.samsung.com/us/kies/ ,which is like iTunes for Samsung Devices, the drivers are needed for Odin, but when the drivers have been installed, close Kies, right click on your toolbar at the bottom of your desktop, I'll assume your running Windows 7, and go into Task Manager. Now find anything with Kies running in the Task Manager, right click on them and kill them.
Once you have done this, go to "sammobile.com", sign up and download a stock ROM for the GT-I9100. I'll assume you have the international SGS2, just remove your battery and make sure it isn't the GT-I9100. Then flash via Odin by connecting your phone, making sure Odin is configured like above, and then putting your phone in download mode, connecting it to your PC and put the file you downloaded in the PDA section and flash.
Click to expand...
Click to collapse
Mine is the GT-i9100. Is this bad?
Linda90 said:
Mine is the GT-i9100. Is this bad?
Click to expand...
Click to collapse
That was a HUGE mistype. It is good. It should say that it shouldn't be the GT-I9100G! Good spot!
It worked!
I have a complete stock unrooted sgs2 now
Thanks alot
I'm trying to root my phone again with your rooting guide themadba. But I canot find a maching kernel version?
My kernel nr:
{
"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"
}
Dial *#1234# and post results please.
Sent from my GT-I9100 using xda app-developers app

[HOW-TO] Update to 4.4.2 NAB & NC5 w/Root from MJ4 Rooted without triggering Knox 0x1

[HOW-TO] Update to 4.4.2 NAB & NC5 w/Root from MJ4 Rooted without triggering Knox 0x1
This How-to guide will show you how to update from Jellybean MJ4 Android 4.3 with Root and Knox 0x0 to KitKat NAB Android 4.4.2 with Root without triggering the Knox 0x1 Warranty Bit.
This guide will be useful to those who want to have Root on their phone without triggering the Knox Warranty bit (and losing your warranty) and don't care/mind about flashing custom recoveries, kernels and ROM's. I, for one, only need Root so I can use Root apps like Xposed, Titanium Backup, AdAway, etc.
I also have a Galaxy S4 and a Nexus 5 and I don't use custom kernels and ROM's on those phones either (I just like stock & Root, lol~). And I don't have phone insurance on my Note 3 and S4 so that's why I want to keep Knox at 0x0 just in case. Also, I like the feeling of out-smarting/going around Samsung's ridiculous Knox implementations.
Disclaimer/Heads-Up
You undertake these steps at your own risk to your phone. This method has been used successfully many times by many users to go from Rooted 4.3 to Rooted 4.4.2 without triggering the Knox Warranty bit. Please read the instructions carefully in the entire post and download/install all the files before proceeding.
=============================================================
Now, onto the steps.
Before beginning the process, make sure you have the following installed on your phone and Windows laptop:
1. Samsung USB driver (PC) (So your Windows PC can detect your Note 3 when you plug it in.)
2. Odin v3.09 (PC) (You'll be using this to flash the NAB bootloader. I modified the .ini file for flashing the bootloader correctly. Clicking on the link will lead you to download Odin v3.09 from my Dropbox account.)
3. Mobile Odin Pro v4.0 (phone) (You'll be using this to flash the NAB tar file to update to Android 4.4.2.)
**Please DO NOT use Mobile Odin Lite. It won't work. If you already have Mobile Odin Lite installed, uninstall it & reboot your phone. Then download & install Mobile Odin Pro.
4. The NAB tar file, transferred over to the root directory of your phone (phone) (Thanks to @freeza for getting this for us~!)
5. The NAB engineering bootloader (PC) or stock NAB bootloader (PC). (Again, thanks to @freeza ~!!)
6. Kingo Android Root (I used v1.1.8.1835 to Root MJ4 4.3) (PC) (You can use this, without triggering Knox 0x1, to Root your stock MJ4 4.3.)
7. Stock NAB 4.4.2 CSC.tar file. (PC) You'll need to flash this with desktop Odin in order for your phone to have the correct CSC information as well as important System apps. If you don't flash this, you'll lose the ability to choose GSM/UMTS in the Mobile Network setting and you'll have S-Pen-related app crashes.
8. Odin v3.04 (for flashing the above CSC.tar file) (PC).
** Optional: If you don't like seeing multiple lines of code every time you reboot your phone (b/c of the engineering bootloader that has been flashed), you can flash the stock NAB bootloader prepared by rwilco12 for us.
His One-Click stock NAB bootloader can be downloaded here.
If you want the stock NAB bootloader in tar format, you can download it from my Dropbox here.
Before I began the process, my Note 3 was as follows:
Stock MJ4 Rooted (achieved with Kingo Android Root)
Stock MJ4 kernel
MJ4 baseband
MJ4 bootloader
Knox Warranty Bit = 0x0
{
"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"
}
[1] Backup anything that's important to you first just in case (e.g., app data, pictures, videos, SMS, call log). I like to backup using Helium, MyBackup Pro, Titanium Backup, & SMS Backup & Restore.
[2] Open up Mobile Odin Pro v4.0 and click on "Open file...". Select the NAB tar file. Make sure the following options are checked:
-"Enable EverRoot"
-"Inject Superuser (SuperSU)"
-"Inject Mobile Odin"
[3] Click on "After flash..." and choose "Download Mode."
[4] Finally, click on "Flash firmware." The phone will reboot automatically and MOP will begin flashing the NAB tar. You'll see a screen like this:
(Modile Odin Pro v4.0 flashing the NAB tar)
[5] Once MOP has finished flashing the NAB tar, it'll boot you directly into Download mode.
(Knox Warranty Bit is still 0x0)
[6] Now, open Desktop Odin v3.09 (download from link above). Click on the "BL" button and select the NAB bootloader you downloaded earlier.
-Be sure the following options are unchecked: "Auto Reboot" and "F. Reset Time."
-Also, the "Phone Bootloader Update" box should be checked.
Now, click on the "Start" button. Wait until it reports "Pass."
[7] Hold down the Power button until the phone reboots. Right when the phone vibrates and begins to restart, press and hold down "VOL UP + HOME + POWER" until the phone enters into this screen:
(The screen looks like this b/c the NAB bootloader is the engineering bootloader version. Note that the Knox Warranty Bit is still 0x0.)
[8] Press the Power button until the phone reboots. Right when the phone vibrates & begins to restart, press and hold down "VOL DOWN + HOME + POWER" until you get to this screen:
[9] Press "Volume down" to cancel and restart the phone.
[10] The phone will reboot and start up normally. Your Note 3 may stay at the yellow Sprint screen for longer than you're used to. Be patient.
Next comes the normal Samsung boot animation.
Then the "Android is upgrading..." pop-up will appear and your apps will be optimized.
Let the phone settle for about 5 to 10 minutes. Upon settling down, reboot your phone once.
[11] Now that your phone has settled down, shut it off completely. Then boot into Download Mode (VOL DOWN + POWER + HOME).
[12] Open desktop Odin v3.04 by right-clicking it & choosing "Run as administrator."
[13] Click on the PDA button and select the csc.tar file. Click Start and let the flash finish and auto-reboot your phone.
And now, everything's finished~! ​
Some people have experienced unstableness in the NAB 4.4.2 environment after the flash. It could be because of some apps that were installed in the MJ4 4.3 environment that's causing the problem. If that's your case, I recommend booting into stock recovery and performing a factory reset/data wipe. You'll have to reinstall your apps again but at least you'll have a clean start.
**Warning: If you decide to flash the NAB tar file with Desktop Odin instead, you'll lose Root.
==============================
​ Through this method, I was able to go from Stock Rooted 4.3 to Stock Rooted 4.4.2 while keeping my Knox Warranty bit at 0x0.
You can check on your Knox Warranty Bit status by restarting the phone and going into Download Mode.
Full setting available under Mobile Network
Writing a text message with the S-Pen
Screen write
How to Update from Stock, Rooted NAB 4.4.2 to Stock, Rooted NC5 4.4.2 (Knox stays 0x0)
Files Needed
1. NC5 tar file. You can download the tar file from here:
http://samsung-updates.com/device/?id=SM-N900P
I placed the NC5 tar into my Internal Storage of the phone (not microSD).
2. NC5 CSC file ( <-- Download from my Dropbox)
3. Odin v3.04
4. NC5 modem file ( <-- Download from my Dropbox) (Credit goes to freeza)
5. NC5 stock Bootloader (optional) ( <-- Download from my Dropbox) (Flash with my modified Odin v3.09 & use the BL button).
Flashing Instructions
1. Make sure your copy of Mobile Odin Pro is at version 4.10.
2. Open MOP v4.10 and select the NC5 tar file. You don't need to set up the phone to boot into Download Mode after the flash. Click on "Open file...". Select the NC5 tar file. Make sure the following options are checked:
-"Enable EverRoot"
-"Inject Superuser (SuperSU)"
-"Inject Mobile Odin"
3. After the flash has completed and phone has rebooted, check Settings. Everything should be NC5 except for the baseband.
4. Shut off the phone completely. Then enter into Download Mode by holding down POWER + VOL DOWN + HOME.
5. Flash the NC5 baseband/modem using Odin v3.04 and using the PDA button. Let the phone reboot.
6. Check Settings. Everything should be NC5 now.
7. Reboot the phone into Download Mode again. Using Odin v3.04 and the PDA button, flash the NC5 CSC file.
8. You're done~!! ​
9. (Optional step) Steps 1 through 7 will update your phone to NC5, except for the bootloader. The bootloader will remain NAB. Even with the NAB bootloader, the phone will work just fine after updating to NC5 for everything else.
However, if you would like to have the bootloader version to be NC5 as well, then flash the stock NC5 bootloader via Odin v3.09. Be sure to power down the phone completely and reboot into Download Mode from a cold state in order for the bootloader flash to stick.
​
​
​
​
​
​
Can someone with the phone info app and Knox tripped see if it reports 0x1. I was unaware that the app developer found a way to read the actual bit.
Thank you for this guide! Will try it out when I get home
Sent from my SM-N900P using xda app-developers app
NAE? Where is this coming from?
Sent from my SM-N900P using Tapatalk
MikeyLee said:
NAE? Where is this coming from?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
LOL fixed the title~
Sent from my Nexus 5 using Tapatalk
optimummind said:
LOL fixed the title~
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
lol I was gonna say
First thank you very much for posting this.
I have just one question. Do we have to flash the engineering bootloader?
Porsche928Guy said:
First thank you very much for posting this.
I have just one question. Do we have to flash the engineering bootloader?
Click to expand...
Click to collapse
Yes, until @freeza has the time to release the official NAB bootloader for us to flash.
Sent from my SPH-L720
I'm trying this now, wish me luck! One thing I'd like to mention regarding your step #4. You said, "The NAB tar file, transferred over to the root directory of your phone (phone)". I tried copying the file to the root of my phone and it locked up my phone, probably because it is too big. I had to do a battery pull to get back up. Mobile Odin Pro found the file in a directory on my external card so I would advise copying it there.
Uh-oh, one more thing. I got the NAB tar file flashed with MOP, but in PC Odin 3.09.03 you said, "-Also, the "Phone Bootloader Update" box should be checked." That option is grayed out. How can I enable that? I'll wait for a reply before flashing the engineering bootloader.
JimSmith94 said:
I'm trying this now, wish me luck! One thing I'd like to mention regarding your step #4. You said, "The NAB tar file, transferred over to the root directory of your phone (phone)". I tried copying the file to the root of my phone and it locked up my phone, probably because it is too big. I had to do a battery pull to get back up. Mobile Odin Pro found the file in a directory on my external card so I would advise copying it there.
Click to expand...
Click to collapse
That's interesting that a simple file transfer would lock up the phone. Which app did you use to make the transfer? I used ES Explorer.
Sent from my SPH-L720
optimummind said:
That's interesting that a simple file transfer would lock up the phone. Which app did you use to make the transfer? I used ES Explorer.
Sent from my SPH-L720
Click to expand...
Click to collapse
I used Root Explorer. I assume that it either can't handle 2.2+GB files or the phone didn't have enough space left for the copy.
---------- Post added at 07:44 PM ---------- Previous post was at 07:39 PM ----------
Thought I'd make this a separate post: One more thing. I got the NAB tar file flashed with MOP, but in PC Odin 3.09.03 you said, "-Also, the "Phone Bootloader Update" box should be checked." That option is grayed out. How can I enable that? I'll wait for a reply before flashing the engineering bootloader.
JimSmith94 said:
I used Root Explorer. I assume that it either can't handle 2.2+GB files or the phone didn't have enough space left for the copy.
---------- Post added at 07:44 PM ---------- Previous post was at 07:39 PM ----------
Thought I'd make this a separate post: One more thing. I got the NAB tar file flashed with MOP, but in PC Odin 3.09.03 you said, "-Also, the "Phone Bootloader Update" box should be checked." That option is grayed out. How can I enable that? I'll wait for a reply before flashing the engineering bootloader.
Click to expand...
Click to collapse
Did you download Odin v3.09 from my Dropbox in the 1st post? It's been modified to allow that checkbox to be checked already.
Sent from my Nexus 5 using Tapatalk
optimummind said:
Did you download Odin v3.09 from my Dropbox in the 1st post? It's been modified to allow that checkbox to be checked already.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh sorry, my bad. I had a newer version and thought newer was better. Okay, everything flashed, and I did the two reboots with volume up and volume down as you said. It rebooted and updated apps, and got to the lock screen with a couple notifications in the notification bar.
However, I got a "waiting for connection" message at the bottom of the screen and the screen went black and I couldn't wake it up with the power button. I have rebooted it several times and was able to boot all the way a few times, but the screen times out whether I am using it or not and it won't wake up. I also get a smartcardservices has stopped message and the phone is running quite hot.
Any ideas?
Thanks for this. Exactly what ive been waiting for!
Sent from my GT-N8013 using Tapatalk
JimSmith94 said:
Oh sorry, my bad. I had a newer version and thought newer was better. Okay, everything flashed, and I did the two reboots with volume up and volume down as you said. It rebooted and updated apps, and got to the lock screen with a couple notifications in the notification bar.
However, I got a "waiting for connection" message at the bottom of the screen and the screen went black and I couldn't wake it up with the power button. I have rebooted it several times and was able to boot all the way a few times, but the screen times out whether I am using it or not and it won't wake up. I also get a smartcardservices has stopped message and the phone is running quite hot.
Any ideas?
Click to expand...
Click to collapse
The "Waiting for connection" message should disappear once your phone connects to Sprint via 3G or 4G. My phone did something along the line of "Final connection has completed" thing after first boot.
If you keep getting errors, you might want to do a factory reset/data wipe from within the stock recovery (hope you backed up your files).
Sent from my Nexus 5 using Tapatalk
Does this works (and keeps 0x0) with OTA 4.4.2 ? I mean can I root 4.4.2, flash kernel and 0x0?
Sent from my SM-N900P using xda app-developers app
erik077 said:
Does this works (and keeps 0x0) with OTA 4.4.2 ? I mean can I root 4.4.2, flash kernel and 0x0?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
I don't know whether this engineering bootloader will trip the Knox warranty bit or not when one flashes a custom recovery afterwards. It'd be great if someone could verify for us. It'd be sweet if it didn't so that people can flash custom kernels, recoveries, and ROM's without tripping Knox.
Edit: Sorry for any confusion. I've updated my words in the above paragraph.
optimummind said:
I don't know whether this engineering bootloader will trip Knox or not. It'd be great if someone could verify for us. It'd be sweet if it didn't so that people can flash custom kernels, recoveries, and ROM's without tripping Knox.
Click to expand...
Click to collapse
As of this writing, one will never be able to flash custom recovery, flash kernels or any rom in the dev forum without tripping Knox.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Someone once reported that they had a knox tripped phone they brought in to a sprint store and a guy actually reset his phone to factory, including knox was set back to 0x0. I never heard any other stories like that though so who knows.
Sent from my SM-N900P using XDA Premium 4 mobile app
Okay, I'm officially lost. This guide is about not tripping Knox and the OP says the engineering bootloader must be flashed, but then a few posts above this states they don't know if flashing the engineering bootloader will trip Knox. So does it trip Knox or not? Or is this referring to the comment I made about phone info not reporting everything for our phone correctly?
Sent from my SM-N900P using xda app-developers app
evilvoice said:
Okay, I'm officially lost. This guide is about not tripping Knox and the OP says the engineering bootloader must be flashed, but then a few posts above this states they don't know if flashing the engineering bootloader will trip Knox. So does it trip Knox or not? Or is this referring to the comment I made about phone info not reporting everything for our phone correctly?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
I may hedge on the Knox question, likely will in my prior post, but that does not detract one jot from the utility of this thread.
Sent from my SM-N900P using Xparent BlueTapatalk 2
---------- Post added at 09:17 AM ---------- Previous post was at 09:10 AM ----------
KEYofR said:
Someone once reported that they had a knox tripped phone they brought in to a sprint store and a guy actually reset his phone to factory, including knox was set back to 0x0. I never heard any other stories like that though so who knows.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Either urban legend or maybe true. William of Occam would assert the former, I'll not speak in absolutes and simply state that it were true, more would know about it. The latent desire in having this capability is strong enough to believe that, if it is possible at the Sprint store, the good folks here would've published it.
Sent from my SM-N900P using Xparent BlueTapatalk 2

4.4.4 ( Download Mode )

Check out these images of my downloader before and after I updated to 4.4.4 does yours look like this ?
{
"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"
}
The image on the right with the blue lettering is after the update. Notice the change in text for the KNOX WARRANTY and KNOX KERNEL LOCK is missing. I want back to 4.4.2 twice and got the same results. The first time I attempted to go back to 4.4.2 from 4.4.4 it boot looped on the restart. I was wondering if anybody has tried to go back, and had this problem? I finally got 4.4.2 to stick, but it wasn't easy.
download mode
jimzweb1 said:
Check out these images of my downloader before and after I updated to 4.4.4 does yours look like this ?
The image on the right with the blue lettering is after the update. Notice the change in text for the KNOX WARRANTY and KNOX KERNEL LOCK is missing. I want back to 4.4.2 twice and got the same results. The first time I attempted to go back to 4.4.2 from 4.4.4 it boot looped on the restart. I was wondering if anybody has tried to go back, and had this problem? I finally got 4.4.2 to stick, but it wasn't easy.
Click to expand...
Click to collapse
i am still stuck at boot looped looking at sprint 4g logo, flash back to nc5 from 4.4.4 now i am stuck please help, this is my fourth time of flashing the stock rom 4.4.2 and still stuck
aliabkad said:
i am still stuck at boot load flash back to nc5 from 4.4.4 now i am stuck please help
Click to expand...
Click to collapse
I definitely understand, I was there yesterday !!! This is how I fixed it. I am going to assume you know how to hold the buttons to get into the modes. First, pull the battery then reinsert. Now go to download mode, and reflash the recovery that you where using with 4.4.2 i.e. CWM or TWRP. Now pull the battery then reinsert. Go to the recovery you installed, and wipe the ROM, CACHE, and DELVIK CACHE just like you where going to install new ROM. Use the recovery to boot into download mode or pull the battery and reinstall, and go to download mode. Install drivers on PC and use Odin version 1.85 here is the link http://www.downloadodin.info/download-odin-1-85 flash a fresh copy of NC5 4.4.2 here is the link http://forum.xda-developers.com/showthread.php?t=2712205 this will get you back to 4.4.2, which is where I'm going to stay till they get some of the bugs out. Never could get CWM recovery to stick after updated to 4.4.4, let me know how it goes.
aliabkad said:
i am still stuck at boot looped looking at sprint 4g logo, flash back to nc5 from 4.4.4 now i am stuck please help, this is my fourth time of flashing the stock rom 4.4.2 and still stuck
Click to expand...
Click to collapse
Man, that sounds familiar I did the same thing. After the fourth attempt I realized the baseband or bootloader was corrupt. So I used kind of the back door to go in and WIPE everything, and start over.
jimzweb1 said:
I definitely understand, I was there yesterday !!! This is how I fixed it. I am going to assume you know how to hold the buttons to get into the modes. First, pull the battery then reinsert. Now go to download mode, and reflash the recovery that you where using with 4.4.2 i.e. CWM or TWRP. Now pull the battery then reinsert. Go to the recovery you installed, and wipe the ROM, CACHE, and DELVIK CACHE just like you where going to install new ROM. Use the recovery to boot into download mode or pull the battery and reinstall, and go to download mode. Install drivers on PC and use Odin version 1.85 here is the link http://www.downloadodin.info/download-odin-1-85 flash a fresh copy of NC5 4.4.2 here is the link http://forum.xda-developers.com/showthread.php?t=2712205 this will get you back to 4.4.2, which is where I'm going to stay till they get some of the bugs out. Never could get CWM recovery to stick after updated to 4.4.4, let me know how it goes.
Click to expand...
Click to collapse
i odin flash stock nc5 4.4.2 now am stock at sprint logo
aliabkad said:
i odin flash stock nc5 4.4.2 now am stock at sprint logo
Click to expand...
Click to collapse
Ok, you did use Odin to reinstall the original recovery that you had before you updated to 4.4.4 correct ? Which recovery did you install ? Did you WIPE the ROM, wiping just the cache and delvik cache won't do it. You need to wipe everything. Go through the process again to make sure everything sticks. Also remember it will take a few minutes on the first boot just like it did when the phone was new.
jimzweb1 said:
Ok, you did use Odin to reinstall the original recovery that you had before you updated to 4.4.4 correct ? Which recovery did you install ? Did you WIPE the ROM, wiping just the cache and delvik cache won't do it. You need to wipe everything. Go through the process again to make sure everything sticks. Also remember it will take a few minutes on the first boot just like it did when the phone was new.
Click to expand...
Click to collapse
i first odin flash NC5_OEM_BL.tar.md5 and then odin flash the stock rom i know at this point i no longer have root , booted to sprint logo that is where am at right now waiting for miracles. if i can get new 4.4.4. stock rom to odin i will be fine
---------- Post added at 02:47 PM ---------- Previous post was at 02:36 PM ----------
aliabkad said:
i first odin flash NC5_OEM_BL.tar.md5 and then odin flash the stock rom i know at this point i no longer have root , booted to sprint logo that is where am at right now waiting for miracles. if i can get new 4.4.4. stock rom to odin i will be fine
Click to expand...
Click to collapse
finally got it to work, i just power+home+volume up took me to the stock recovery then i did a factory reset, voila.Thank you jimzweb1, i was in the panic mode again thank you for bringing me back to life, you rock !!!!. peace.
aliabkad said:
i first odin flash NC5_OEM_BL.tar.md5 and then odin flash the stock rom i know at this point i no longer have root , booted to sprint logo that is where am at right now waiting for miracles. if i can get new 4.4.4. stock rom to odin i will be fine
Click to expand...
Click to collapse
I am not familiar with NC5_OEM_BL.tar.md5 you are using. If you are trying to keep the sprint logo you can always change the CSC code. Don't worry about trying to match md5's. Just try and use the links I gave you, the instructions are in the NC5 thread on the how to change the zip into a tar file and Odin will match md5's during the NC5 install. Let me know how its going.
aliabkad said:
i first odin flash NC5_OEM_BL.tar.md5 and then odin flash the stock rom i know at this point i no longer have root , booted to sprint logo that is where am at right now waiting for miracles. if i can get new 4.4.4. stock rom to odin i will be fine
---------- Post added at 02:47 PM ---------- Previous post was at 02:36 PM ----------
finally got it to work, i just power+home+volume up took me to the stock recovery then i did a factory reset, voila.Thank you jimzweb1, i was in the panic mode again thank you for bringing me back to life, you rock !!!!. peace.
Click to expand...
Click to collapse
Awesome !!! I know what that panic mode is like.
aliabkad said:
i odin flash stock nc5 4.4.2 now am stock at sprint logo
Click to expand...
Click to collapse
Did you trip your knox count doing this downgrade
No only when i first rooted 4.4.4 then tripping knox counts
Sent from my SM-N900P using XDA Free mobile app
Guys make sure when using Odin, that you are using a good, usb cord .. Use thr one that came with the phone if you can, or its equal.. DO NOT USE any of those cheepies from the corner store.. They will ruin your day...
Very helpful info. Thx..
caleb2014 said:
Very helpful info. Thx..
Click to expand...
Click to collapse
Thanks, don't see where a flash counter (KNOX) has anything to do with the (KNOX) program which secures data with an encrypted container to send to another location ? So, the most likely explanation is Samsung and the NSA are just gathering a little info for personal use !!! Lol
JimWebz,
Ironically I came across your post. I tried to go from NH7 to NC5 and was stuck in the treacherous bootloop, whoo it was scary especially for a N00B, but I had enough sense to go to my previous posts that you and others have commented on to find Micmars completely stock NH7, followed his instructions and voila! Back in buisness, now forget using Towelroot, going back to NC5 was the biggest pain, and damn near scary! Chainfire here I come!!!!
TheNewGuy14 said:
JimWebz,
Ironically I came across your post. I tried to go from NH7 to NC5 and was stuck in the treacherous bootloop, whoo it was scary especially for a N00B, but I had enough sense to go to my previous posts that you and others have commented on to find Micmars completely stock NH7, followed his instructions and voila! Back in buisness, now forget using Towelroot, going back to NC5 was the biggest pain, and damn near scary! Chainfire here I come!!!!
Click to expand...
Click to collapse
Yes it happens a lot. Going back to NC5 usually ends up in a bootloop, it did for me. The easiest way out of it, is to pull the battery and boot into recovery. If you have a stock recovery the do a factory reset. Then check and see what version of KiKat your on ( i.e. did you make back to NC5 or are you still on NH7 ). If your still on Nh7 use odin to flash again it should take the second time. OR, if you still have a custom recovery then wipe your entire OS, cache, and delvik cache as if you are going to install a new rom. Then power down device completely then boot into download mode and odin flash NC5 again and it take now.
I run Stock Rooted 4.4.2 NC5 with Philz custom CWM version 6.12.9 hltespr. I ran NH7 4.4.4 rooted for about a week, I didn't have any major problems but a lot of other people where. So went back to NC5 which for me has always been rock solid.
Hey Jimwebz,
I have a question, saw this minor detail and wonder if it's the cause of bootlooping. The official Sprint build is N900PVPUDNC5 while the one's on XDA available from those posts are N900PVPUCNC5 PUC instead of PUD. Is there a difference?
Thanks man!
TheNewGuy14 said:
Hey Jimwebz,
I have a question, saw this minor detail and wonder if it's the cause of bootlooping. The official Sprint build is N900PVPUDNC5 while the one's on XDA available from those posts are N900PVPUCNC5 PUC instead of PUD. Is there a difference?
Thanks man!
Click to expand...
Click to collapse
Near as I can figure it's a typo ? Should be N900PVPUCNC5 which is 4.4.2 NC5, and it should be N900PVPUDNH7 which is 4.4.4 NH7. I wish it was the cause, but idone says the cause is not letting the device finish a full install including the stock recovery. I'm not sure, but going back is just a bootloop and it is easy to correct. So I am going to hang out on NC5 it is still a rock solid base for a daily driver, then I can mess around with roms like Priest Punch and some of the cool themes that have come out !!!

[Q] Stuck in TWRP

I just tried to upgrade to Alliance build 30 from build 26. I also loaded TWRP latest version after using CWM for a few years now. I had no idea CWM files would not restore with TWRP. Yes I was stupid but now I cannot install anything or get out of recovery having no working recovery file in TWRP. Do I have to start over with Odin? Can I somehow get back to CWM recovery files and bypass TWRP? I see my counter does not show any custom files and is still at zero. Please help me!
NB2A said:
I just tried to upgrade to Alliance build 30 from build 26. I also loaded TWRP latest version after using CWM for a few years now. I had no idea CWM files would not restore with TWRP. Yes I was stupid but now I cannot install anything or get out of recovery having no working recovery file in TWRP. Do I have to start over with Odin? Can I somehow get back to CWM recovery files and bypass TWRP? I see my counter does not show any custom files and is still at zero. Please help me!
Click to expand...
Click to collapse
When you are in twrp have you tried flashing the cwm recovery zip to switch back yo cwm?
bigmarv31 said:
When you are in twrp have you tried flashing the cwm recovery zip to switch back yo cwm?
Click to expand...
Click to collapse
Yes I did try that too. I was finally able to get Alliance rom to load but it gets stuck at logo never completing. In fact now it put into yellow triangle saying return to Verizon store so even Odin cannot see it.
Thank you for helping anyway
Did you put phone in download mode then try to use odin
I just put it in Odin mode
I guess I need to start all over again
Should I use Adam's thread?
bigmarv31 said:
Did you put phone in download mode then try to use odin
Click to expand...
Click to collapse
where you on stock 4.1.2?
If you were on stock 4.1.2 use odin with the proper files then you can use Adams Casual No You Verizon.
bigmarv31 said:
where you on stock 4.1.2?
If you were on stock 4.1.2 use odin with the proper files then you can use Adams Casual No You Verizon.
Click to expand...
Click to collapse
NB2A said:
Thank you for responding with such detail. It finally started to boot into Alliance logo but never completed. Now it says with yellow triangle phone needs to be returned to Verizon. It does not even work in Odin. I do have an external reader for the card but I guess I am screwed now anyway.I wonder if Verizon will even help me at all back to stock.
Click to expand...
Click to collapse
@NB2A - I see where you have 2 threads on this.... so I'm just going to respond in this thread to avoid confusion.
If you can get into download mode again with Volume Down+Home+Power button combo.... then you should be able to use ODIN to restore the phone to whatever firmware version would be appropriate. Like bigmarv31 said, you should be able to restore back to 4.1.2 as long as you never installed factory stock 4.3 or 4.4.2. If you did install 4.3 or 4.4.2, then your bootloader has been locked and you would have to restore back to one of those firmwares and can't go back to 4.1.2 because of locked bootloader. (I had assumed you were still on 4.1.2 bootloader because you said you had TWRP CWM on the phone). If you can't get into download mode, then do a Google search for tricks to force phone into download mode. I've read where people say you can pull the battery and plug in the phone... or use a special usb jig to get the phone into download mode if the button combo doesn't work anymore. These tricks aren't guaranteed to work, but would be worth a shot.
You can buy a usb jig from eBay for less than $5. (This may be a good one: http://www.ebay.com/itm/MICRO-USB-J...er_Cell_Phone_Accessories&hash=item1e6d6cc865).
Good luck.
PS: If you can get the phone into download mode again, use section 1b of Droidstyle's restore guide to restore the phone ( http://forum.xda-developers.com/showthread.php?p=34891181).
Thank you again
I was able to finally get phone to work using Odin. Now I need to root it and since it is using a 4.3 build My options are only touch wiz apps I am told and can only use safestrap to use another rom. I would be happy to simply be back on what I had working fine in it before this yesterday. I had Beanstown build 26 before Alliance build 30 messed me up. I cannot seem to find root to use now.
Thank you again
mattnmag said:
@NB2A - I see where you have 2 threads on this.... so I'm just going to respond in this thread to avoid confusion.
If you can get into download mode again with Volume Down+Home+Power button combo.... then you should be able to use ODIN to restore the phone to whatever firmware version would be appropriate. Like bigmarv31 said, you should be able to restore back to 4.1.2 as long as you never installed factory stock 4.3 or 4.4.2. If you did install 4.3 or 4.4.2, then your bootloader has been locked and you would have to restore back to one of those firmwares and can't go back to 4.1.2 because of locked bootloader. (I had assumed you were still on 4.1.2 bootloader because you said you had TWRP on the phone). If you can't get into download mode, then do a Google search for tricks to force phone into download mode. I've read where people say you can pull the battery and plug in the phone... or use a special usb jig to get the phone into download mode if the button combo doesn't work anymore. These tricks aren't guaranteed to work, but would be worth a shot.
You can buy a usb jig from eBay for less than $5. (This may be a good one: http://www.ebay.com/itm/MICRO-USB-J...er_Cell_Phone_Accessories&hash=item1e6d6cc865).
Good luck.
PS: If you can get the phone into download mode again, use section 1b of Droidstyle's restore guide to restore the phone ( http://forum.xda-developers.com/showthread.php?p=34891181).
Click to expand...
Click to collapse
NB2A said:
I was able to finally get phone to work using Odin. Now I need to root it and since it is using a 4.3 build My options are only touch wiz apps I am told and can only use safestrap to use another rom. I would be happy to simply be back on what I had working fine in it before this yesterday. I had Beanstown build 26 before Alliance build 30 messed me up. I cannot seem to find root to use now.
Thank you again
Click to expand...
Click to collapse
Cool. Glad you got it restored. If you're on factory stock 4.3, then you can use safeRoot to gain root access. Here's the link to saferoot-- http://forum.xda-developers.com/showthread.php?p=48392009.
---------- Post added at 01:05 PM ---------- Previous post was at 01:00 PM ----------
Oh... and you probably know, but you need to use the modified TWRP called Safestrap in order to run Alliance 26 again.
mattnmag said:
Cool. Glad you got it restored. If you're on factory stock 4.3, then you can use safeRoot to gain root access. Here's the link to saferoot-- http://forum.xda-developers.com/showthread.php?p=48392009.
---------- Post added at 01:05 PM ---------- Previous post was at 01:00 PM ----------
Oh... and you probably know, but you need to use the modified TWRP called Safestrap in order to run Alliance 26 again.
Click to expand...
Click to collapse
This looks like a real PIA to root. Thank you so much.
Saferoot
NB2A said:
This looks like a real PIA to root. Thank you so much.
Click to expand...
Click to collapse
I unzipped that file on that thread and there does not seem to be any install bat file to use for step 5.
NB2A said:
I unzipped that file on that thread and there does not seem to be any install bat file to use for step 5.
Click to expand...
Click to collapse
This rooting process is actually very easy. I just downloaded and unzipped the saferoot zip package, and the batch file is definitely there. (see the below screenshot) It's not named "install.bat" -- just "install" (but you can see which one is the batch file).
{
"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"
}
mattnmag said:
This rooting process is actually very easy. I just downloaded and unzipped the saferoot zip package, and the batch file is definitely there. (see the below screenshot) It's not named "install.bat" -- just "install" (but you can see which one is the batch file).
Click to expand...
Click to collapse
No matter what either saferoot or safestrap does not seem my phone
The drivers are there too when I plug phone
NB2A said:
No matter what either saferoot or safestrap does not seem my phone
The drivers are there too when I plug phone
Click to expand...
Click to collapse
I'm sorry, but I don't really understand what you mean. You mean when you followed all the steps in the saferoot thread, and double clicked on the install batch file.... that the saferoot install script could not see your phone? Did you make sure to enable usb debugging in the developer settings on your phone? When you connect your phone to your computer with the usb cable, open a command terminal screen... then type "adb devices" (without the quotes) into the terminal... does it show your phone's serial number to ensure your phone is being seen by the computer? If not, you probably need to install the stand alone Android SDK tools from here:
( https://developer.android.com/sdk/index.html#Other ).
Also.... I don't understand what safeStrap would have to do with this. SafeStrap is a modified version of TWRP that you would install onto your phone only after you get the phone rooted with safeRoot. You would need to use SafeStrap as the recovery now because the bootloader was locked permanently after you put factory stock 4.3 on the phone... and regular TWRP and CWM won't work with locked bootloaders. After you get Safestrap on there, you would boot into it to flash the Alliance 26 ROM back onto the phone. You'll need to research in the Safestrap thread for the steps, as I am actually still on 4.1.2 bootloader and don't need to use Safestrap.... so I've never used it. As I recall though, you need to make a full backup of your stock ROM first (also backup the efs if you haven't already). Then you have to flash the custom ROM over the stock ROM slot in Safestrap. Here's a link for the Safestrap thread for your reading pleasure : http://forum.xda-developers.com/showthread.php?t=2704992
PS: I see where you're posting in the Alliance Build 30 thread for help. To avoid confusion, make sure they know you're on factory stock 4.3 and your trying to root and install Alliance 30 (which is based on Android version 4.4.2). You're going to end up soft bricking the phone again if you try to install Alliance 30 in SafeStrap with stock 4.3. Alliance 30 is based on 4.4.2 and uses a different kernel than Alliance 26 (which is 4.3 based).
I appreciate your help. One major unexplained problem I had was safestrap or saferoot could not see my device at all using a machine with XP. After switching to a machine with windows 7 both worked and saw device fine. I am now running Beans build 26 and used Safestrap as well. I now ned to make a recovery copy of 26. I did make a copy of the working stock room too just in case. I just need to determine what is the best place to save it off the device too.
NB2A said:
I appreciate your help. One major unexplained problem I had was safestrap or saferoot could not see my device at all using a machine with XP. After switching to a machine with windows 7 both worked and saw device fine. I am now running Beans build 26 and used Safestrap as well. I now ned to make a recovery copy of 26. I did make a copy of the working stock room too just in case. I just need to determine what is the best place to save it off the device too.
Click to expand...
Click to collapse
Save them to your sd card and if u want copy them to your computer just in case you ever need them.
mattnmag said:
PS: I see where you're posting in the Alliance Build 30 thread for help. To avoid confusion, make sure they know you're on factory stock 4.3 and your trying to root and install Alliance 30 (which is based on Android version 4.4.2). You're going to end up soft bricking the phone again if you try to install Alliance 30 in SafeStrap with stock 4.3. Alliance 30 is based on 4.4.2 and uses a different kernel than Alliance 26 (which is 4.3 based).
Click to expand...
Click to collapse
I was one of the guys trying to help over there. It was confusing to say the least. There was never any mention of whether the bootloader was unlocked or not. I assumed it was and made suggestions based on that premise. I'm sorry I didn't ask for more detail before I did.
If I had known it was locked I would have never said a word. I know nothing about SafeStrap. I've been on the unlocked VRALJB Bootloader ever since I've had my phone. Sorry I stuck my nose in where it didn't belong.
Sent from my SCH-I605 using XDA Free mobile app

Categories

Resources