[GUIDE] Everything we know so far for DEVELOPER EDITION NOTE 3

[GUIDE] Everything we know so far for DEVELOPER EDITION NOTE 3 - Verizon Galaxy Note 3 General

Here is a little guide I put together to hopefully help some people (all 20 of us) with developer edition note 3
I TAKE NO CREDIT THIS IS MERELY A GUIDE
WARRANTY IS VOID, KNOX WILL BE 0X1
Part 1: Flashing TWRP onto Developer Note 3
Step 1- Download and install Odin onto Windows PC http://uploaded.net/file/o2xcp01n
Step 2- Download T-Mobile yes T-Mobile TWRP Tar File http://www.techerrata.com/browse/twrp2/hltetmo
Step 3- Flash T-Mobile TWRP Tar File in Odin under the AP Slot ONLY!
BE CAREFUL IF YOU PLACE IN WRONG SLOT DEVICE WILL BE BRICKED WITH NO WAY BACK YET!
Side note phone will now say Set Warranty Bit: Recovery when booting into recovery. Don't worry this is normal. This is showing you what tripped warranty. More about this below later in guide.
Step 4- Flash Superuser (this step may not be required for some. my dev note booted me into recovery and asked me if I wanted to flash superuser. Others have had issues with this) http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip
Step 5- Make a complete backup of EVERYTHING in TWRP. Boot, Recovery, System, Data, Cache ALL OF THEM I have backed up to internal sdcard & external sdcard & even throw a backup on your pc just in case something catastrophic happens since we have no Odin stock files still!
Step 6- (optional) Flash a rom/kernel.
Rom Section: Right now we have a couple roms to choose from over here http://forum.xda-developers.com/verizon-galaxy-note-3/development
Big ups to @beanstown106 and @sbreen94 for cranking out the first roms so far! :good:
Kernel Section: Now while we don't have any Verizon Developer Edition kernels so far we do have T-Mobile ones just like TWRP. Head over here to pick one out. I have tested all of the last night and all work without a hitch so far! http://forum.xda-developers.com/note-3-tmobile/orig-development
Big ups to @Imoseyon and @morfic who i was both in conversation with about kernels! :good:
Step 7- Enjoy!
Part 2: Restoring Boot.img if phone will not boot after rom or kernel install
If you get a kernel that won't run properly or boot loop or a rom like hyper lets say that will not boot on the developer edition without proper boot.img here is how you fix.
Step 1- Boot into TWRP. From phone being off use three finge method of vol up, power and home button to boot into twrp.
Step 2- Restore boot.img from the very important backup in step 5 from part one! This is why you have to have a backup of everything! Restore the boot.img only and reboot!
Step 3- Back to enjoy! lol
I do not take any credit for roms/kernel/recovery just sharing links and what I have done. Hope this guide helps!!

Great job/idea on this guide!
Sent from my SM-N900V using Tapatalk

Reserved.. lol
good guide so far i will be cooking up a flashable tar that should essentially bring us to stock mj7 with the exception of the bootloaders. its not the full thing cuz of no bootloaders but hey its better than what we have now
Ps- i thought i was the only one who knew about imoseyons kernels been testing them for him for a cpl days

Thanks for taking the time and putting this together!

We can install any version of t-mobile twrp tar file right? 2.6.3.0 works the same as 2.6.3.8?
Sent from my SCH-I605 using Tapatalk

untouchablez said:
We can install any version of t-mobile twrp tar file right? 2.6.3.0 works the same as 2.6.3.8?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
As far as i know it should work i am just on the most updated one

Thanks for this thread!
I understand we don't have the recover .tar for the Verizon Developer edition, but one thing I'm confused about is when you mention we don't have a kernel yet, are you still referring to the recover tar?
How different is it from the Kernel.tar.gz file found here?:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SM-N900V
Code:
Kernel.tar.gz 139,510 KB
Platform.tar.gz 773,012 KB
README_Kernel.txt 1 KB
README_Platform.txt 1KB

some kernel input
Edit : This guid rocks, very accurate steps and sufficiently detailed ,
couple of questions: 1- my recovery states that it is unable to mount usb OTG ? i think . did every one else get that message?
2- I had to update update my samsung drivers , again for the millionth time, maybe a post to the newest samsung drivers would be helpful ? The ones included here helped odin finally recognize my phone
==================================
so i tried compulsion and imo's really quick.
Compulsion locked my phone at 2.2 ghz all last night ( i really hope i didnt shorten the life of my processor because of that )
Imos kernel like to sleep, so its a keeper, so far deep sleep was predominant on my phone, four hours of sleep in a 5 hour test .
I know every phone likes a different kernel
Just stating my observation

awesome. thank you for posting this for us Dev Editioners. lol.
:highfive:

@oneandroidnut
someone got bored at work
Good guide, hopefully this helps people who are constantly asking "what should I do with my dev edition"

I wonder since it's knox tripped if any 3rd party would warranty the phone.

keynith said:
@oneandroidnut
someone got bored at work
Good guide, hopefully this helps people who are constantly asking "what should I do with my dev edition"
Click to expand...
Click to collapse
No problem man!!

Very good guide. I particularly appreciate the information on kernels.
Thank you.

cam30era said:
Very good guide. I particularly appreciate the information on kernels.
Thank you.
Click to expand...
Click to collapse
no problem man

keennay said:
Thanks for this thread!
I understand we don't have the recover .tar for the Verizon Developer edition, but one thing I'm confused about is when you mention we don't have a kernel yet, are you still referring to the recover tar?
How different is it from the Kernel.tar.gz file found here?:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SM-N900V
Code:
Kernel.tar.gz 139,510 KB
Platform.tar.gz 773,012 KB
README_Kernel.txt 1 KB
README_Platform.txt 1KB
Click to expand...
Click to collapse
i will have to ask @beanstown106 for sure. i know we have the J3 build but not sure if that is what we need or not. wait for beans to chime in

keennay said:
Thanks for this thread!
I understand we don't have the recover .tar for the Verizon Developer edition, but one thing I'm confused about is when you mention we don't have a kernel yet, are you still referring to the recover tar?
How different is it from the Kernel.tar.gz file found here?:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SM-N900V
Code:
Kernel.tar.gz 139,510 KB
Platform.tar.gz 773,012 KB
README_Kernel.txt 1 KB
README_Platform.txt 1KB
Click to expand...
Click to collapse
This is the open source code for the kernel completely different than what we need we need a full stock Odin recovery tar file for mj3
Sent from my SM-N900V using Tapatalk

Hmmm Knox tripped almost makes the DE pointless especially if bootloader unlock comes out... Presently still waiting for further information ordered 2 hours after it went on backorder.

beanstown106 said:
This is the open source code for the kernel completely different than what we need we need a full stock Odin recovery tar file for mj3
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
its different then stock recovery to flash in odin. but will this work as stock kernel???

When
When and where can I get one?

kjmmarion said:
When and where can I get one?
Click to expand...
Click to collapse
Where = http://www.samsung.com/us/mobile/cell-phones/SM-N900VMKEVZW?from_mobile=true When = Hopefully soon, sold out in a few hours when released.

Related

Flash & Root Question.

As A Noob here im a small bit confused.
Was going to follow this link Complete Noobs Guide but some of the links in that guide dont work anymore.
So then I came across this Video and seems too easy to do
Is the video the same thing as the noobs guide?
If it is, and I follow the video, what Rom is the best one to use.
Just looking for a stable rom, good looking and saves battery.
Thank you, great website.

Rom is your choice, yes it's so simple it takes literally a couple of mins, it took me longer to dl the files needed than to root
Personally i use the rom in my sig - Neo is the dogs bollocks

Thanks for the help.
Think I have everything sorted, last thing is do I need an SD card for this.
Dont think I do but just want to make sure before start.

Nope you can just use internal memory...

As far as I know you don't need an SD card. I rooted mine last night and was really surprised how easy it is. Literally a 5 minute process (including flashing the sensation ROM). After reading up on here I used this thread and this page which has an easy to follow, summarised guide below the video.
It was a lot easier than I expected but to be far the last device I rooted was a HTC and so didn't know what to expect without it being locked.
If you run into any problems just search for the solution as so many people have rooted I'm pretty sure everything will have been covered.

Make sure you have a insecure kernel>use SuperOneClick to root>flash CWM>put ROM on sd>boot in CWM recovery>wipe data & cache & dalvik cache> install from sd>ROM of choice>do it twice just to be safe! You're done. If you need any additional help browse/search xda forums. If you need any additional help let me know!

Ok successfully rooted and placed a kernel on the phone.
Before I put on a new ROM, I wanted to get rid of the yellow triangle.
I found this page but all the files are on mega upload which is currently down at the minute.
Any ideas how I can get a stock kernels to remove the yellow triangle?

I just seen he has updated all the links. Great news.
Just read on the last comments and im now confused.
Does the link in the previous comment fix the yellow triangle?

yellow triangle indicate that you have not a stock kernel on your phone,
normally flash a stock one and the triangle will go away,
I have not searching deep to get rid of the triangle with any kernel but ways seems to be possible.. posts on dev forum answer this
a usb jig is fine and the simple one I think, but you have to make or buy it..

try the V3RTR3MA 4.6 from the android development forum here
its one of the best roms i've ever flashed
Sent from my GT-I9100 using XDA App

Why are you even bothered by it? U only see it on boot up

Because its very easy to get rid of.
All I need is a original Kernel.
I downloaded one and the image file is a MD5 file?
Is that correct?

Yes. 10 ch
Rochey21 said:
Because its very easy to get rid of.
All I need is a original Kernel.
I downloaded one and the image file is a MD5 file?
Is that correct?
Click to expand...
Click to collapse

MistahBungle said:
Yes. 10 ch
Click to expand...
Click to collapse
Sorry probably stupid question but what does that mean?

How to install new ROM ICS on my Galaxy SII
I'm trying to install by boot options but always i select the zip rom i'd received a message that the package cannot by validade. Why ?

Rochey21 said:
Sorry probably stupid question but what does that mean?
Click to expand...
Click to collapse
The minimum message length is 10 characters, so when you just want to say yes or no you as 10chars or other stuff to bump the lenght so it will post.
roguand said:
I'm trying to install by boot options but always i select the zip rom i'd received a message that the package cannot by validade. Why ?
Click to expand...
Click to collapse
You dont have CWM recovery (stock recovery wont flash custom rom zips), go do some more reading before you flash a rom so you understand what you are getting into, FAQ's here.

roguand said:
I'm trying to install by boot options but always i select the zip rom i'd received a message that the package cannot by validade. Why ?
Click to expand...
Click to collapse
Or do you mean signature verification ?

S-ON Kernel Installer v0.57 9-27-12

Now that the new hboot doesn't allow S-ON devices to flash kernels I went ahead and adapted this for the LTE. It's something I started for the Evo 3D back in January, but when a new way to get S-OFF was found I sat it aside and had forgotten about it.
When used it tries to flash the kernel like normal and doesn't do anything special if able to, otherwise it will copy a script to the system partition and install the kernel when the ROM tries to boot up. All that's needed is for a few lines to be added to the updater-script and it can do the rest.
I'll update this with more information at a later time, but for now I just want to say thank you to everyone who has helped contribute ideas and tested. As always, any help with improving it is welcomed.
How To Use It
This is mainly for ROM and kernel devs to use before releasing, but it can easily be added to any that don't normally use it. For more detailed instructions see Page 3.
Download and add the "kernel" folder to your update zip
Edit your updater-script and use the following when you are ready to install the boot.img
Code:
ui_print("Installing Kernel, please wait...");
package_extract_file("boot.img", "/tmp/boot.img");
package_extract_dir("kernel", "/tmp/kernel");
set_perm_recursive(0, 2000, 0777, 0777, "/tmp/kernel");
run_program("/tmp/kernel/install_kernel.sh", "/tmp/boot.img", "/tmp/bootready.tmp");;
ifelse(file_getprop("/tmp/bootready.tmp","kernel.ready") != "READY",(
ifelse(file_getprop("/tmp/bootready.tmp","kernel.ready") == "STARTUP",
ui_print("Kernel Will Be Installed On Startup."),
ui_print("ERROR: Kernel Not Installed!")
)
));
Sign the zip and it can then be installed like normal from any device with a custom recovery
Changes
v0.57
flashboot.sh - Fixed the case statement that verifies the kernel flashed properly
flashboot.sh - Moved the call for DD to save the old kernel so that it always gets used
Downloads/Sources
Kernel Folder on DevHost (MD5: 27eB86aae3562e147d86b8dfe7a04786)
Google Code
Github - All files including the flashboot binary source

How Can I Test It With S-OFF?
If you comment out the dd command that writes the boot.img it will act like your device has S-ON.
Edit install_kernel.sh and change:
Code:
echo "-Trying to write the new boot.img and verify it's MD5"
$BBDD if=$BOOTPADDED of=$BLOCKBOOT; sync
rm -f $BOOTOLD
to:
Code:
echo "-Trying to write the new boot.img and verify it's MD5"
#$BBDD if=$BOOTPADDED of=$BLOCKBOOT; sync
rm -f $BOOTOLD
Where Are The Log Files?
In the recovery it uses: /tmp/recovery.log
On boot it uses: /data/local/bootinfo.txt
What Does This Need To Work?
A custom recovery
A valid kernel already installed with init scripts to start either /system/bin/app_process or /system/bin/netd
What Recoveries Does It work With?
Most of my testing has been done with TWRP, but it should work just as well with any other recovery
Why Did My Phone Reboot Back To The Recovery?
If it is unable to flash the kernel it will leave the old one in place and reboot back to the recovery. If you are able to, please pull the log file from /data/local/bootinfo.txt and send it to me so I can see what needs to be fixed.
What If I Get A Bootloop?
Either the kernel you flashed doesn't work with your ROM or there was an error and it's unable to reboot back to the recovery. If you hold volume down it should bring up the bootloader, from there use the volume and power buttons to select 'Recovery'.
Why Does My Phone Boot Straight To The Bootloader?
You either managed to wipe your boot partition (kernel) or sometimes this will happen when upgrading hboots. If you are S-ON you will need to flash a new boot image from fastboot.

Reserved for later use

Cute

Does this work for AOSP based kernels as well?

-Cupper- said:
Cute
Click to expand...
Click to collapse
Thanks Cupper
sivarticus85 said:
Does this work for AOSP based kernels as well?
Click to expand...
Click to collapse
Yup, it's all the same to it. The only thing it needs to work is for some sort of kernel to already be installed.

good stuff!!!!!!!

Good stuff man. Like always, xhausx contributing genius stuff for all. Thanks. :thumbup:
Sent from my EVO using xda premium

Awesome. Thanks.
via eVo.

implimenting in my next installer

Zarboz said:
implimenting in my next installer
Click to expand...
Click to collapse
Would be a nice setup, aroma choose the way to install, boot.img or anykernel flash
Then you can flash the modules either way...
Thanks for the script. It will definitely get used.

Zarboz said:
implimenting in my next installer
Click to expand...
Click to collapse
ca1ne said:
Would be a nice setup, aroma choose the way to install, boot.img or anykernel flash
Then you can flash the modules either way...
Thanks for the script. It will definitely get used.
Click to expand...
Click to collapse
Let me know if you need any help implementing it. I know the instructions aren't very detailed yet so I'll see about clarifying them some more here in a little bit.

Cool man
Sent from my EVO using xda premium

I don't mean to highjack anyone thread I was ready to do this since meanrom went with the evilz kernal. since I was s-on on the 1.15 boot. I was going to do this till I found a app on the market place called flash image gui which installed the kernal right on the phone.was simple and just plain easy no typeing anthing in just a click of a buttone.

cgrimm9 said:
I don't mean to highjack anyone thread I was ready to do this since meanrom went with the evilz kernal. since I was s-on on the 1.15 boot. I was going to do this till I found a app on the market place called flash image gui which installed the kernal right on the phone.was simple and just plain easy no typeing anthing in just a click of a buttone.
Click to expand...
Click to collapse
Since the kernel is only writeable from the rom this does something similar, except it does it after you flash the rom and it's automatic.
You could look at it as the rom itself installs it's own kernel. That's one of the reasons why it may look so convoluted, but for a rom/kernel dev to actually implement it is easy once you know how it works.
JohnCorleone said:
I used Flash Image GUI on my NS4G all of the time. The last 2 updates were to add this phone and the Nexus 7. It takes about 10 seconds to flash a kernel or recovery img. Its a JoeyKrim app...so you know its legit. It actually saved me last night when testing a N7 kernel overclocked over 1.99. . The kernel somehow made my N7 not boot to recovery no matter what I tried so I stuck a different kernel in that app, flashed it and once it booted I flashed the CWM 6.0.1.0 and I was completely fixed. Money well spent.
Edit..XhausX, I bought my first 2 HTCs ever about 2 weeks ago. They are both s on 1.13 but I need to either return on to full stock or use your rooted stock. I need to help my mother out. She's using a Samsung Moment! Ouch.... I am downloading that now. Is it a simple wipe and flash? If its more difficult, I will gladly shoot a donation your way if you can help me. I think I prefer her to be rooted stock so your odex version is the call...should have mentioned I know squat about the HTC methods. Regaw_Leinard got me where I am now
Sent from my EVO using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
If you no longer need it rooted personally I would get s-off first and then run the latest RUU to restore it to stock. That way you'll always be able to re-root anytime without hassle, but the device can still be completely stock and used normally.

Zarboz said:
implimenting in my next installer
Click to expand...
Click to collapse
+1 on that, where do i add this in the updater and what do we do with Blk21 just leave it or will it work around it.

Is it possible to get a mirror of the Dev-Host file? The 'drivers are currently being updated', and I wanted to try adding this to my stock 2.13.651.1 ROM so as to avoid the inevitable questions from noobs that are S-ON about why the ROM won't boot .

Evolutionmods said:
+1 on that, where do i add this in the updater and what do we do with Blk21 just leave it or will it work around it.
Click to expand...
Click to collapse
Usually it's best to run it last so everything else is already in place. It will also check the recovery for the mount point, so that line won't be needed with it.
For your paranoid android rom you could use something like this: http://pastebin.com/rGVDKK2u
I'm not able to test it atm though so you'll probably want to verify it's good first.
Captain_Throwback said:
Is it possible to get a mirror of the Dev-Host file? The 'drivers are currently being updated', and I wanted to try adding this to my stock 2.13.651.1 ROM so as to avoid the inevitable questions from noobs that are S-ON about why the ROM won't boot .
Click to expand...
Click to collapse
mirror: https://dl.dropbox.com/u/18734200/kernel-installer-v0.56.zip

xHausx said:
Usually it's best to run it last so everything else is already in place. It will also check the recovery for the mount point, so that line won't be needed with it.
For your paranoid android rom you could use something like this: http://pastebin.com/rGVDKK2u
I'm not able to test it atm though so you'll probably want to verify it's good first.
mirror: https://dl.dropbox.com/u/18734200/kernel-installer-v0.56.zip
Click to expand...
Click to collapse
And of course the Dropbox link is now dead too .

[Q] Take OTA update?

Just picked up my note 3 running 4.3 an hour ago and have not unlocked/rooted/custom recovery it yet, still 100% stock. There is an OTA available and I was wondering if I should take it before rooting?
Thanks in advance

You can either, accept the ota and then root(which I never liked accepting a ota cause Im cautious of downloads being corrupt.) Or you can download a odin version of kitkat and flash thru odin then root(which is what I did)

Thank you very much for your answer MrWicked! One more question if I may ... I just came from US Cellular with the Note 2 to Sprint with the Note 3 - we had very little development there compared to here. I have read a ton of topics on here today about Knox, NAB engineering bootloader, Odin ... etc. and I understand that and how to follow instructions, but I see several different ways. I was wondering which method you used or would suggest? All I am trying to accomplish at this point is root, custom recovery, a (close to) stock rom, (hopefully) not trip the Knox trigger, and run titanium backup (which I read there are issues with that I have to fix afterwards).

Ok couple things, no matter what root method you chose once you flash a recovery it will trip knox. So that being said you have a couple options......
1. You flash via odin the kitkat update and use the "kingo" root method which I personally have not tried and can't give much input on. It is not supposed to trip knox it leaves you rooted but with your stock recovery. Once you flash a recovery you trip knox. But you are stuck with a stock rooted rom in which you could use titanium backup.
2. You flash the kitkat via odin, and you use Chainfire's method(which is what i did personally) I have always had good luck with Chainfire's root methods. but then it trips knox and you can flash a recovery and flash what ever roms you like. But at this time technically you warranty is voided with Samsung.

str8nitro said:
Just picked up my note 3 running 4.3 an hour ago and have not unlocked/rooted/custom recovery it yet, still 100% stock. There is an OTA available and I was wondering if I should take it before rooting?
Thanks in advance
Click to expand...
Click to collapse
I would wait on kitkat. I have been running it on a stock n3 for about a wk now and I'm not liking it at all. my bluetooth for my car is very buggy, stock email is buggy and I'm getting a 3rd less battery out of it. I would have 70% left at the end of my day now I'm lucky if I have 50%. I would wait for kitkat until they work out the bugs.

rcjunky said:
I would wait on kitkat. I have been running it on a stock n3 for about a wk now and I'm not liking it at all. my bluetooth for my car is very buggy, stock email is buggy and I'm getting a 3rd less battery out of it. I would have 70% left at the end of my day now I'm lucky if I have 50%. I would wait for kitkat until they work out the bugs.
Click to expand...
Click to collapse
Obviously it varies per phone but what are you running? I had the opposite effect Bluetooth in car is wayyyyy better and battery life is great. But I'm running Sacs v1 KitKat so that might be why we are having different experiences also.
Sent from my SM-N900P using Tapatalk

rcjunky said:
I would wait on kitkat. I have been running it on a stock n3 for about a wk now and I'm not liking it at all. my bluetooth for my car is very buggy, stock email is buggy and I'm getting a 3rd less battery out of it. I would have 70% left at the end of my day now I'm lucky if I have 50%. I would wait for kitkat until they work out the bugs.
Click to expand...
Click to collapse
Thanks for the advice on this, may I ask what Rom you are on?
MrWicked1 said:
Obviously it varies per phone but what are you running? I had the opposite effect Bluetooth in car is wayyyyy better and battery life is great. But I'm running Sacs v1 KitKat so that might be why we are having different experiences also.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Been reading up on Sacs v1 and it looks like I wouldn't have a problem if I go this route since I am on mj4. It looks like I can follow the instructions completely from rlmiller here http://forum.xda-developers.com/showpost.php?p=50794223&postcount=20 and do my root and everything in one stop shopping. Also from what I have read once I go to kit kat I can't go back to jelly bean ... I would assume there would be no reason to back up my stock rom after rooting since I can't go back ever.

str8nitro said:
Thanks for the advice on this, may I ask what Rom you are on?
Been reading up on Sacs v1 and it looks like I wouldn't have a problem if I go this route since I am on mj4. It looks like I can follow the instructions completely from rlmiller here http://forum.xda-developers.com/showpost.php?p=50794223&postcount=20 and do my root and everything in one stop shopping. Also from what I have read once I go to kit kat I can't go back to jelly bean ... I would assume there would be no reason to back up my stock rom after rooting since I can't go back ever.
Click to expand...
Click to collapse
Yep

MrWicked1 said:
Yep
Click to expand...
Click to collapse
I have used TWRP before but mostly CM, I am not familiar with PHILZ at all, Is one better than the other? I really appreciate your time and advice here as I am sure others with the same questions will as well. Thanks!

str8nitro said:
I have used TWRP before but mostly CM, I am not familiar with PHILZ at all, Is one better than the other? I really appreciate your time and advice here as I am sure others with the same questions will as well. Thanks!
Click to expand...
Click to collapse
Personally I love twrp but it doesn't always seem to go as smooth with it. Philz is a modified version of Cm. Philz is rpetty much the go to for least amount of problems.

MrWicked1 said:
Personally I love twrp but it doesn't always seem to go as smooth with it. Philz is a modified version of Cm. Philz is rpetty much the go to for least amount of problems.
Click to expand...
Click to collapse
I will give it a go then, I thought I read something about "NAB engineering bootloader" with Philz, is this something I need to read up on more or self explanatory once I get into it?

Haven't used the Engineering one personally to me it didn't give me any benefits for now for me to flash it

MrWicked1 said:
Haven't used the Engineering one personally to me it didn't give me any benefits for now for me to flash it
Click to expand...
Click to collapse
SOrry for so many questions, but I saw that a few people has issues. Hopefully last question and I will be golden ... For Philz I see to downloads in the link provided by rlmiller - philz_touch_6.12.9-hltespr.tar.md5 and philz_touch_6.12.9-hltespr compared to just one file for TWRP - TWRP KITKAT hltespr-recovery-4.4.img. To use Philz do I need just one file or both? The reason I ask is because in the instructions it says "And lastly....
Now powerdown phone and start up in download mode again.
start odin and plugin phone again.
now click in phone slot and browse to TWRP file
you now click start and wait until it says pass and reboots. Unplug and wait for startup"
But it does not give instruction for Philz, which is 2 different files that are not the same as the TWRP.

str8nitro said:
SOrry for so many questions, but I saw that a few people has issues. Hopefully last question and I will be golden ... For Philz I see to downloads in the link provided by rlmiller - philz_touch_6.12.9-hltespr.tar.md5 and philz_touch_6.12.9-hltespr compared to just one file for TWRP - TWRP KITKAT hltespr-recovery-4.4.img. To use Philz do I need just one file or both? The reason I ask is because in the instructions it says "And lastly....
Now powerdown phone and start up in download mode again.
start odin and plugin phone again.
now click in phone slot and browse to TWRP file
you now click start and wait until it says pass and reboots. Unplug and wait for startup"
But it does not give instruction for Philz, which is 2 different files that are not the same as the TWRP.
Click to expand...
Click to collapse
No just flash the stock....let it load up....reboot into dl again...odin cf autoroot....boot up....then reboot dl mode again then you can flash which ever recovery you like twrp or philz.....then load up reboot to recovery I would make a backup then flash Sacs rom....then you should be all good to go. And no prob on the questions it's better to ask then not.

MrWicked1 said:
No just flash the stock....let it load up....reboot into dl again...odin cf autoroot....boot up....then reboot dl mode again then you can flash which ever recovery you like twrp or philz.....then load up reboot to recovery I would make a backup then flash Sacs rom....then you should be all good to go. And no prob on the questions it's better to ask then not.
Click to expand...
Click to collapse
Sorry, I think I didn't explain well. I am going to go with Philz because it worked well for you, but my question was which Philz file:
philz_touch_6.12.9-hltespr.tar.md5
or
philz_touch_6.12.9-hltespr
do I use in whe I get to the TWRP area of the instructions:
Now powerdown phone and start up in download mode again.
start odin and plugin phone again.
now click in phone slot and browse to TWRP file <----------------------------------- here
you now click start and wait until it says pass and reboots. Unplug and wait for startup

Yeah instead of the twrp file you use the philz tar.md5

str8nitro said:
Thanks for the advice on this, may I ask what Rom you are on?
Been reading up on Sacs v1 and it looks like I wouldn't have a problem if I go this route since I am on mj4. It looks like I can follow the instructions completely from rlmiller here http://forum.xda-developers.com/showpost.php?p=50794223&postcount=20 and do my root and everything in one stop shopping. Also from what I have read once I go to kit kat I can't go back to jelly bean ... I would assume there would be no reason to back up my stock rom after rooting since I can't go back ever.
Click to expand...
Click to collapse
I am stock no root at this time. ota update.
---------- Post added at 04:44 PM ---------- Previous post was at 04:40 PM ----------
MrWicked1 said:
Obviously it varies per phone but what are you running? I had the opposite effect Bluetooth in car is wayyyyy better and battery life is great. But I'm running Sacs v1 KitKat so that might be why we are having different experiences also.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I am stock no root at this with the ota update.

[GUIDE] Noob guide to access root on NC5 from NC5 OTA

Complete Noob Guide To Access Root on Android 4.4.2 (NC5)Helpful Guide by Reconde
This guide will thoroughly explain how to obtain root on Android 4.4.2 (NC5)
There is ONLY ONE FILE needed for the entire process, download it here: http://www.androidfilehost.com/?fid=23501681358538076File provided by: @gigilie
Proceed after downloading and extracting the file above.
1. Navigate to /ODINv3.10 > Odin3 v3.10.0 and run it. In Odin, click on the AP slot and navigate to MK2_system_4downgrade_rooting_all_in_one and open it. Before going to the next step, you must put /safestrap flashable files-modules-quickupgrades-supersu onto your SD card, this is important. You will also need to download gogolies-wififix-VZW-retail-NC5-w-modules-SS.zip, and put it into the folder you just put onto your SD card.
2. Now, turn your Galaxy S4 completely off and boot it into Download Mode by turning it on and holding the volume up button at the same time. Once your phone is booted into Download Mode, plug it into your computer and press "Start" in Odin.
3. After the downgrade file has been flashed to your device, let it boot, set it up, and then go to Settings and enable Developer Options (this can be done by going to "About device" in settings, and clicking on "Build Number" several times until the phone says "Developer mode has been turned on"). Open developer options and enable USB debugging.
4. Back on your computer, navigate to the folder /apps-for-android-down-and-upgrades > /saferoot and run install.bat
5. After following instructions given by the command prompt, your phone should now be rooted. Now, transfer Safestrap-JFLTE-3.72-kk-B01 (found in /apps-for-android-down-and-upgrades) to your phone and install it. ***IF PLANNING ON INSTALLING A CUSTOM ROM IT MUST BE ON YOUR EXTERNAL SD CARD BEFORE THIS STEP. IF PLANNING ON KEEPING ROOTED STOCK ROM, VZW_NC5_PREROOTED-gogolie.zip(stock ROM- KNOX FREE) must be on SD card*** In safestrap, click install recovery, and when that is finished click Reboot to recovery.
6. In safestrap, go to Wipe > Advanced and wipe only dalvik and cache. After this, go to Install and install the custom, or stock, ROM of your choice (must be a 4.4.2 ROM) **IMPORTANT: ROM MUST BE INSTALLED ON STOCK SLOT** After installing the ROM you must flash jfltevzw-NC5-modules (found under /safestrap flashable files-modules-quickupgrades-supersu) and add to the queue gogolies-wififix-VZW-retail-NC5-w-modules-SS.zip AND UPDATE-SuperSU-v1.94. Now flash and wipe dalvik and cache again.
7. After installing your ROM correctly, reboot the phone into Download mode in safestrap by going to Reboot > Download. Now open Odin and insert NC5_4.42-ODIN_UPGRADE-FOR-4.3-NO-SYSTEM-NO-BOOTLOADERS-gogolie (found under /odin flashable files-modemhlos-bootimgs) into the AP slot and press start.
8. Reboot your phone into safestrap after Odin has finished. You must wipe dalvik and cache one last time and then flash jfltevzw-NC5-modules again and you are done! Your phone should now be rooted on NC5.
If you have any issues after completing the process, feel free to reply to this thread or send me a PM!
Special thanks to @gigilie for putting the files and other guide together. His thread can be found here.
Make sure to thank this post if this process worked!

Just what we needed for gigilie's method. He does some great stuff but he doesn't write very clearly lol.
Sent from my HTC6600LVW using Xparent Skyblue Tapatalk 2

Okay! First of all I would like to thank you for condensing this and making it bit more understandable. I'm usually really nervous about messing around with rooting (even though it's my second time), so simplified things like this really take the stress off.
the one question I had, is...
In step 7 you say to put "...open Odin and insert NC5_4.42-ODIN_UPGRADE-FOR-4.3-NO-SYSTEM-NO-BOOTLOADERS-gogolie."
Which slot in odin do I place it in? AP like before?

joshm.1219 said:
Just what we needed for gigilie's method. He does some great stuff but he doesn't write very clearly lol.
Sent from my HTC6600LVW using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Yes, it took me about 12 tries to fully understand gigilie's method- his writing is confusing at times!
Roadsigns said:
Okay! First of all I would like to thank you for condensing this and making it bit more understandable. I'm usually really nervous about messing around with rooting (even though it's my second time), so simplified things like this really take the stress off.
the one question I had, is...
In step 7 you say to put "...open Odin and insert NC5_4.42-ODIN_UPGRADE-FOR-4.3-NO-SYSTEM-NO-BOOTLOADERS-gogolie."
Which slot in odin do I place it in? AP like before?
Click to expand...
Click to collapse
Yes, this file goes in AP just like before.
Sent from my SCH-I545 using XDA Premium 4 mobile app

Reconde said:
Yes, it took me about 12 tries to fully understand gigilie's method- his writing is confusing at times!
Yes, this file goes in AP just like before.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wonderful! Thanks so much for the quick response and help with understanding all of this! I'll let you know how my root and custom ROM installation attempts go.
Update: I pulled it off and got my first custom ROM running as well! Might want to consider mentioning how to install the minor parts in step 6, after custom roms (like having to press the three dots and whatnot). that was the only place I had gotten tripped up. All in all, very effective tut. Thank you kindly.

Roadsigns said:
Wonderful! Thanks so much for the quick response and help with understanding all of this! I'll let you know how my root and custom ROM installation attempts go.
Update: I pulled it off and got my first custom ROM running as well! Might want to consider mentioning how to install the minor parts in step 6, after custom roms (like having to press the three dots and whatnot). that was the only place I had gotten tripped up. All in all, very effective tut. Thank you kindly.
Click to expand...
Click to collapse
Did you use this with installing hyperdrive? Since that ROM uses an aroma installer you have to click the three dots and click exit or it will automatically reboot. You don't have to do that with roms that don't use the aroma installer.
Sent from my SCH-I545 using Tapatalk

Reconde said:
Yes, it took me about 12 tries to fully understand gigilie's method- his writing is confusing at times!
Yes, this file goes in AP just like before.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
joshuabg said:
Did you use this with installing hyperdrive? Since that ROM uses an aroma installer you have to click the three dots and click exit or it will automatically reboot. You don't have to do that with roms that don't use the aroma installer.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Oh! Yes I did. Sorry, I didn't know that hyperdrive installed differently than other roms. Good to know, though, and hopefully people who have similar problems can scroll down and find this, as it's probably not worth being in the OP, haha.

In @gigili orginal post, it says if you're on stock rooted 4.3 MK2 to start with step 3. I'm on stock, rooted 4.3 MK2 (I never take OTA update until I know I can root), so on your method do I start from the beginning, start from step 2, or from the middle of step 1 "Before going to the next step, you must put /safestrap flashable files-modules-quickupgrades-supersu onto your SD card, this is important. You will also need to download gogolies-wififix-VZW-retail-NC5-w-modules-SS.zip, and put it into the folder you just put onto your SD card."
Thanks for making it more clear.

where do I find /safestrap flashable files-modules-quickupgrades-supersu?
Edit: nm i figured it out I had a corrupt download and it did not have those files...redownloaded and now im good!

I've tried 3 times so far and each time I get to the end to reboot the final time, it tells me there's no OS.
*I want to keep it stock rooted.

bichigo said:
I've tried 3 times so far and each time I get to the end to reboot the final time, it tells me there's no OS.
*I want to keep it stock rooted.
Click to expand...
Click to collapse
From what I can tell the OP is wrong about this step. You don't have a 4.4.2 system on your phone. If you want stock rooted flash this: http://www.androidfilehost.com/?fid=23487008491962465

bichigo said:
I've tried 3 times so far and each time I get to the end to reboot the final time, it tells me there's no OS.
*I want to keep it stock rooted.
Click to expand...
Click to collapse
Which rom are you trying to install?
sent by baja kitkat S4

decaturbob said:
Which rom are you trying to install?
sent by baja kitkat S4
Click to expand...
Click to collapse
i just want stock rooted. but i have another s4 that i want baja 2.2 on.

bichigo said:
I've tried 3 times so far and each time I get to the end to reboot the final time, it tells me there's no OS.
*I want to keep it stock rooted.
Click to expand...
Click to collapse
joshuabg said:
From what I can tell the OP is wrong about this step. You don't have a 4.4.2 system on your phone. If you want stock rooted flash this: http://www.androidfilehost.com/?fid=23487008491962465
Click to expand...
Click to collapse
Yes, you will need to flash the stock ROM if not installing a custom ROM. I do not recommend using this file, though, go back to the first post and I have updated the link in step 5. At this point though you will need to run through the entire process again. I apologize for any inconvenience.

bichigo said:
i just want stock rooted. but i have another s4 that i want baja 2.2 on.
Click to expand...
Click to collapse
ok, so what stock root rom are you trying to flash?

rtfelt said:
In @gigili orginal post, it says if you're on stock rooted 4.3 MK2 to start with step 3. I'm on stock, rooted 4.3 MK2 (I never take OTA update until I know I can root), so on your method do I start from the beginning, start from step 2, or from the middle of step 1 "Before going to the next step, you must put /safestrap flashable files-modules-quickupgrades-supersu onto your SD card, this is important. You will also need to download gogolies-wififix-VZW-retail-NC5-w-modules-SS.zip, and put it into the folder you just put onto your SD card."
Thanks for making it more clear.
Click to expand...
Click to collapse
You will want to do the part in the middle of step 1, and then you can skip to step 3 and go from there.

I followed the original instructions to the end (which said to skip the rom flashing steps for stock ROM). I grabbed I545VRUFNC5-Stock-Root-Odex.zip and can't seem to get the flash to work. Is there a certain step I should go back to?

Does this procedure trip the Samsung Knox flag?

After step 7 got this error on reboot:
E:Error in /cache/recovery/sec_csc.zip (Status 7)
I'm not sure what I did wrong. Any help would be appreciated.

joshuabg said:
From what I can tell the OP is wrong about this step. You don't have a 4.4.2 system on your phone. If you want stock rooted flash this: http://www.androidfilehost.com/?fid=23487008491962465
Click to expand...
Click to collapse
only problem with the above file josh is that KNOX is all over it still. yucky...
gogolie's NC5 Rooted/ KNOX FREE:
http://www.androidfilehost.com/?fid=23329332407590564 is my version with no KNOX was released a little earlier than that other ROM and I didnt publicly put it out there as much as I maybe should have. with all 4.4.2 ROM's you need to flash SuperSu 1.94.zip file after installing ROM or you will probably lose root or not have binaries installed... so be sure and always flash that file after installing a ROM in Safestrap!
also I gave Reconde the okay to start this thread, its endorsed by me and I thank him for giving props and not just copying my stuff Thanks buddy. Sorry about not being the best with words... figuring out how things work is more my specialty. Users feel free to ask any questions in the main thread I will answer or respond still as soon as I'm able you can also keep up with current development for the 4.4.2 as well as ROM's and testing ROM's there in that thread. Thanks guys!
---------- Post added at 05:50 AM ---------- Previous post was at 05:41 AM ----------
bichigo said:
I've tried 3 times so far and each time I get to the end to reboot the final time, it tells me there's no OS.
*I want to keep it stock rooted.
Click to expand...
Click to collapse
try the files i listed just before this post. they will be your answer. and sometimes you will get that no os error depending on what ROM and system your using its totally normal for instance my mk2 AOSP roms say that everytime yet they boot absolutely fine its just an error from Safestrap sometimes not reading the system folder correctly but has no outcome on the booting of the ROM. Ignore that error as long as you think you properly installed it.

[ROM][G986U1]SamPWND.R3.v1 1ZTJA

Hello!
Please forgive me as it's been a long time since I made/posted a stock based ROM as I have been mainly doing security research and dealing more with source code last few years.
Most seasoned Samsung users on here probably already know me and work that I have done so I won't waste time posting any "about me" stuff.
DISCLAIMER:
This ROM is still WIP (although fully functional) and based on Android R Beta 1ZTJA for G986U/U1/W. An unlocked BL is required to flash this ROM!
Features:
- Based on Stock R Beta 3 Build aka 1ZTJA.
- This is a full ODIN flashable tar (got tired of messing with update zips.)
- Disabled vbmeta
- Pretty heavily debloated
- Deknoxed
- Removed pesky recovery-from-boot.p which could cause boot loops.
- Currently only has SPR csc mods (will mod others in next build)
*Native call recording
*App Lock (forgot to push the app though so will fix in next build)
*Few others.. will post more specifics and give creds since I used the csc mod for exynos as a basis..
- Probably forgetting something but thhis is an initial build so will add more as time goes..
Instructions:
Note: The zip contains an instructions.txt that is more detailed.
Note 2: Zip contains the full firmware tar file which includes everything to be fully updated/on ztja. This means all bl files, modem, boot, recovery, super etc. so you can start from and build. Zip also contains files and instructions on how to obtain root.
- Backup your data if you must since this will wipe device!
- Put phone in dl mode and extract zip to pc somewhere.
- Open ODIN (INCLUDED IN ZIP) and in AP slot navigate to SamPWND.R3.v1-G986U1.tar and flash it.
- Device will reboot into stock ZTJA recovery where you will wipe data and reboot.
- Set up device and win?
Root Steps (optional):
Note: Since theres no sources for R yet theres no custom recovery. Also, Q based recovery will not work on R bootloaders as well as R there is no more /sbin so root needs to be flashed at this time.
- After you have flashed rom and everything is set up reboot back into DL mode.
- Open included ODIN and in AP slot navigate to the 1BTIF_BL_Files_and_LOS_Recovery.tar. Make sure auto reboot is NOT selected. Flash it.
- Once thats flashed hold vol down and power until screen turns off then immediately hold vol up and power until LOS recovery loads.
- However you want to flash magisk (I included Magisk.v21.0.zip) flash it.
* I do adb push magisk.zip /... Then select Install Update then install from root and select magisk zip...
- Reboot back into DL mode.
- In ODIn, select AP slot then navigate to 1ZTJA_BL_Files_and_1ZTJA_Stock_Recovery.tar and flash it.
- Device will boot back into ROM and you will now be rooted!
***TWRP RECOVERY***
- Download listed below
- I suggest you follow all the steps above and make sure it's up and running before installing TWRP.
- Basically extract the .tar from the .gz archive and flash in ODIN!
- adb works
- file manager and other tools work
- If follow above steps first as recommended, data will be decrypted.
- mounts work
- flashing works
- backup/restore works
- no issues found so far?
Steps are really quite simple if you have ever used ODIN.
It took a bit to put this together since all we have are update zips so I had to do a bit of trickery as well as had to build some binaries/tools to manually patch from 1BTIF to 1ZTJ3 to 1ZTJA to be able to have all the firmware images.
I will create a Telegram ROM support group soon where you can ask all the questions you want there (I am not at liberty to discuss unlocking bootloader on XDA so questions about this on here will either be ignored or will say I cant discuss. More info as to why will be posted in the support group or you can read the imcluded instructions.txt wink.wink).
ENJOY!
Shout Outs:
@topjohnwu for Magisk of course
@jesec for LOS Recovery
@afaneh92 base TWRP
@Mentalmuso for direction on how to get TWRP to work on R!
More shout outs coming soon!
SamPWND ROM Support and Other Support Telegram Group CLICK HERE
Downloads will be in post 2.

SamPWND.R3.v1-G986U1.tar
G986U/U1 1ZTJA TWRP Recovery
SamPWND ROM Support and Other Support Telegram Group CLICK HERE

CHANGELOG and Other Updates:
10/31/2020 - Added Telegram ROM Support group link to OP and second post as well as cleaned posts up a bit
10/19/2020 - Initial Upload/Post Creation

elliwigy said:
SamPWND.R3.v1-G986U1.tar
https://drive.google.com/file/d/1cm5H-GEEENQAhK0DnKGMjjZWnyONVXCm/view?usp=drivesdk
Click to expand...
Click to collapse
Nice, I'm going to give this a try in a little while.

Misterxtc said:
Nice, I'm going to give this a try in a little while.
Click to expand...
Click to collapse
feel free to use it as a base to work ur rom magic lol! u kno how my roms are.. bare bones lol

elliwigy said:
feel free to use it as a base to work ur rom magic lol! u kno how my roms are.. bare bones lol
Click to expand...
Click to collapse
Thanks, that will be a big help getting me back into building roms again. I haven't had the time at all lately except for some minor phone stuff plus I'm waiting for computer parts to come in and put together a 10th gen Intel system. Then I can get started again.

I can flash this on g9860 device?Great work!
Verstuurd vanaf mijn SM-G9860 met Tapatalk

[email protected] said:
I can flash this on g9860 device?Great work!
Verstuurd vanaf mijn SM-G9860 met Tapatalk
Click to expand...
Click to collapse
dunno.. i wouldnt try it tho.. not sure how g986u bl files will work on a g9860.. might hard brick

Great work. Good to have more choices

so this will work on G988U too?

Smartphones13 said:
so this will work on G988U too?
Click to expand...
Click to collapse
no
it clearly states its for G986U/U1/W if anyone tries it or flashes it to any other device then dont complain if it doesnt work or bricks phone

That being said, how do we get this going for the 988U1? I have root working for R on the 988U1. Although attempting to boot into stock recovery on ZTJA sends it into a boot loop still working on that.

Zavon said:
That being said, how do we get this going for the 988U1? I have root working for R on the 988U1. Although attempting to boot into stock recovery on ZTJA sends it into a boot loop still working on that.
Click to expand...
Click to collapse
i have toake rom for g988u/u1..
and thats bcuz it needs to pull recovery from boot which it xan only do on stock boot.img

Just flashed this last night, seems to be running beautifully, no issues so far, battery is looking good. Removed a dozen more useless apps, root is working great.
Running on a G986W with a Canadian Sim, everything seems to be working fine with my carrier (WiFi calling, LTE+...)
Thanks brother! Keep up the good work

elliwigy said:
no
it clearly states its for G986U/U1/W if anyone tries it or flashes it to any other device then dont complain if it doesnt work or bricks phone
Click to expand...
Click to collapse
I have sm-G986U1 American version will it work or na?

Franzferdinan51 said:
I have sm-G986U1 American version will it work or na?
Click to expand...
Click to collapse
is ur bl unlocked? if not then no.. if it is then yes

Now that the FE has TWRP, any idea if these will work on that?

elliwigy said:
is ur bl unlocked? if not then no.. if it is then yes
Click to expand...
Click to collapse
How do you unlock the BL for the US Variant SM-G981x (S20 5G), is it possible

Superguy said:
Now that the FE has TWRP, any idea if these will work on that?
Click to expand...
Click to collapse
as i stated already a few times the answer is no.. this is for g986u/u1. the rom has g986u/u1 bootloaders and everything.. its not a twrp flashable zip.. if u try and hard brick thats on you.

illiterateBuffoon said:
How do you unlock the BL for the US Variant SM-G981x (S20 5G), is it possible
Click to expand...
Click to collapse
its not allowed to b posted on xda since its a paid service.. if u look around ull be able to find ur way

Better Mobile App

welcome