Hello all, I recently got a note 3 (about two weeks ago) and am looking at options for tethering.
Before I go on, my phone's specs are
SM-900P
Stock ROM
Software version ending in -NAB
4.4.2 KitKat
Rooted (KNOX already tripped)
Now, from what I can tell from what I've read up on, there aren't very many options for a stock ROM user on this device. The only one I have read about working is Wifi Tether Router from the market, but I can't even get the SSID to show up on any of my devices when tethering (and at that, I think it was only in ad-hoc, I'd rather infrastructure).
What other options do I have in terms of tethering on stock, if any? And assuming that I don't, what are my options as far as custom ROMs go? (While I am familiar with Android, I have next to zero knowledge about custom ROMs).
Gamemaster1379 said:
Hello all, I recently got a note 3 (about two weeks ago) and am looking at options for tethering.
Before I go on, my phone's specs are
SM-900P
Stock ROM
Software version ending in -NAB
4.4.2 KitKat
Rooted (KNOX already tripped)
Now, from what I can tell from what I've read up on, there aren't very many options for a stock ROM user on this device. The only one I have read about working is Wifi Tether Router from the market, but I can't even get the SSID to show up on any of my devices when tethering (and at that, I think it was only in ad-hoc, I'd rather infrastructure).
What other options do I have in terms of tethering on stock, if any? And assuming that I don't, what are my options as far as custom ROMs go? (While I am familiar with Android, I have next to zero knowledge about custom ROMs).
Click to expand...
Click to collapse
First, congrats on the new device.
Now, as to stock rom options for rooted users, I'm having difficulty understanding how one quantifies that statement, inasmuch as if you go with root only, the world of options are at your fingertips. Put another way, you want to stay stock with root added, it's now your choice as to how much or little you choose to add to your setup.
For instance, you could use Adaway, Titanium Backup, a plethora of themed apps, and thousands of other root-only options (recovery, kernels, clocking apps, Xposed modules, WiFi tethering, & c.).
Now, if you wish to stay on an earlier build (NAB is older than NC5, the latest updated official build), our amazing dev community has provided a standalone flashable zip to add it to your setup.
Go to @JoshBeach website, and grab the zip file labeled accordingly.
http://www.kitkatkiller.eu/index.php?dir=SPRINT+GALAXY+NOTE+3/KITKAT+FILES/MODS/NABD
There's also a 4-1 reboot menu and a hot spot removal zip there for the taking.
Now hie yourself over to the dev section, and shop around. Some of the best devs on XDA are right here.
Choose well. You can't go wrong with any.
You also might donate to the hardworking folks giving these things away for free, if you're so inclined.
I hope this helps.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
First, congrats on the new device.
Now, as to stock rom options for rooted users, I'm having difficulty understanding how one quantifies that statement, inasmuch as if you go with root only, the world of options are at your fingertips. Put another way, you want to stay stock with root added, it's now your choice as to how much or little you choose to add to your setup.
For instance, you could use Adaway, Titanium Backup, a plethora of themed apps, and thousands of other root-only options (recovery, kernels, clocking apps, Xposed modules, WiFi tethering, & c.).
Now, if you wish to stay on an earlier build (NAB is older than NC5, the latest updated official build), our amazing dev community has provided a standalone flashable zip to add it to your setup.
Go to @JoshBeach website, and grab the zip file labeled accordingly.
http://www.kitkatkiller.eu/index.php?dir=SPRINT+GALAXY+NOTE+3/KITKAT+FILES/MODS/NABD
There's also a 4-1 reboot menu and a hot spot removal zip there for the taking.
Now hie yourself over to the dev section, and shop around. Some of the best devs on XDA are right here.
Choose well. You can't go wrong with any.
You also might donate to the hardworking folks giving these things away for free, if you're so inclined.
I hope this helps.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Thanks. This device was a huge jump for me. I got this device after coming from an ICS Moto Razr Maxx. With a phone as old as that, there weren't really a lot of custom ROM options available, it's just something I have never needed to pursue.
I realize there is an astounding amount of resources available for a rooted user, even on stock. But in particular, my first main focus is seeing if I can find an infrastructure tethering option. I'm coming from a world where everything only ever needed root access. Now I'm in a world of DeOdexing, Odexing, custom ROMs, recoveries, bootloaders, aggressive firmware updates patching everything (whereas my previous carrier never updated a single thing from stock) and it's all overwhelming.
I can't say in particular if I want to stay on an earlier build or not. From experiences as far as other devices I've owned are--older is better. The exploits are generally in older firmwares and newer firmwares that patch them seem to offer gimmicky features at best (and you can often get them by rooting an older device and selectively updating anyhow). Unless NC5 has some astounding advantage of NAB, I'd probably just want to stick with NAB.
Now, since I"m relatively new to this, I'm not 100% what it is you linked to me. This Hotspotmod says DeOdexed. I'm still really new to what DeOdexing means, so bear with me. Does that mod require me to have previously DeOdexed the files on my device, or is the mod GOING to DeOdex them? If it is going to DeOdex them, is that all I'm going to need to make use of the wireless hotspot on my device?
I'll definitely look around at the custom ROMs and see if anything catches my eye. They all do seem really interesting. However, I like to make changes to fix what is broken (hence why rooting has always been a go-to for me. But if I can resolve the barriers I'm having now (the only of which seems to be tethering at the moment), I think I'd rather stay stock.
Need the DeOdexed Rom for NAB(D)...
Gamemaster1379 said:
Thanks. This device was a huge jump for me. I got this device after coming from an ICS Moto Razr Maxx. With a phone as old as that, there weren't really a lot of custom ROM options available, it's just something I have never needed to pursue.
I realize there is an astounding amount of resources available for a rooted user, even on stock. But in particular, my first main focus is seeing if I can find an infrastructure tethering option. I'm coming from a world where everything only ever needed root access. Now I'm in a world of DeOdexing, Odexing, custom ROMs, recoveries, bootloaders, aggressive firmware updates patching everything (whereas my previous carrier never updated a single thing from stock) and it's all overwhelming.
I can't say in particular if I want to stay on an earlier build or not. From experiences as far as other devices I've owned are--older is better. The exploits are generally in older firmwares and newer firmwares that patch them seem to offer gimmicky features at best (and you can often get them by rooting an older device and selectively updating anyhow). Unless NC5 has some astounding advantage of NAB, I'd probably just want to stick with NAB.
Now, since I"m relatively new to this, I'm not 100% what it is you linked to me. This Hotspotmod says DeOdexed. I'm still really new to what DeOdexing means, so bear with me. Does that mod require me to have previously DeOdexed the files on my device, or is the mod GOING to DeOdex them? If it is going to DeOdex them, is that all I'm going to need to make use of the wireless hotspot on my device?
I'll definitely look around at the custom ROMs and see if anything catches my eye. They all do seem really interesting. However, I like to make changes to fix what is broken (hence why rooting has always been a go-to for me. But if I can resolve the barriers I'm having now (the only of which seems to be tethering at the moment), I think I'd rather stay stock.
Click to expand...
Click to collapse
OK, first off, I did fail to remember that the hotspot mod to which I linked is for DeOdex only.
So, if you want to stay as close to stock as possible, you'll need to be on @freeza stockish DeOdex NADB rom build, which has Knox removed.
You'll also need proper recovery.
So, flash TouchWiz KitKat recovery from PC Odin (version 3.07 works fine).
Unzip that file, then run it from your PC, first right-click on the exe file, choose run as administrator, then open PC Odin.
Now, power off your phone in it's entirety, and then go into bootloader mode (Volume Down + Home + Power, then volume up once past the caution screen...if you're rooted, you should already have tripped Knox, so that is my working premise). Making sure you have the latest Samsung drivers installed, plug your phone into the PC, and...load the recovery file below into the PDA slot within PC Odin:
TWRP Recovery V.2.7.0.1
Then, dump the following zip file onto your device's internal memory:
Stockish NABD DeOdex ROM
Check your MD5 to make sure you get a clean download, using this tool here:
MD5 Checker
Then compare it with this code (copy/paste into the appropriate box on the MD5.exe program I lined):
7d0749d2362d872ca8db7c524d25bf40
Now reboot your phone, and flash the zip to which I linked.
Good luck! And I can only imagine the boost in performance you must be experiencing.
As to your observation about older=more reliable (forgive my paraphrasing if I'm off), that is your opinion, and perhaps one harbored by many. I would suggest that others may not share your belief.
micmars said:
OK, first off, I did fail to remember that the hotspot mod to which I linked is for DeOdex only.
So, if you want to stay as close to stock as possible, you'll need to be on @freeza stockish DeOdex NADB rom build, which has Knox removed.
You'll also need proper recovery.
So, flash TouchWiz KitKat recovery from PC Odin (version 3.07 works fine).
Unzip that file, then run it from your PC, first right-click on the exe file, choose run as administrator, then open PC Odin.
Now, power off your phone in it's entirety, and then go into bootloader mode (Volume Down + Home + Power, then volume up once past the caution screen...if you're rooted, you should already have tripped Knox, so that is my working premise). Making sure you have the latest Samsung drivers installed, plug your phone into the PC, and...load the recovery file below into the PDA slot within PC Odin:
TWRP Recovery V.2.7.0.1
Then, dump the following zip file onto your device's internal memory:
Stockish NABD DeOdex ROM
Check your MD5 to make sure you get a clean download, using this tool here:
MD5 Checker
Then compare it with this code (copy/paste into the appropriate box on the MD5.exe program I lined):
7d0749d2362d872ca8db7c524d25bf40
Now reboot your phone, and flash the zip to which I linked.
Good luck! And I can only imagine the boost in performance you must be experiencing.
As to your observation about older=more reliable (forgive my paraphrasing if I'm off), that is your opinion, and perhaps one harbored by many. I would suggest that others may not share your belief.
Click to expand...
Click to collapse
That is a very detailed and useful explanation, thank you.
As far as the reliability statement, I actually mean reliability in terms of unreliability (for exploitations). I have a Nintendo 3DS and PS3 on older firmwares and both times the older firmware has proven invaluable.
Gamemaster1379 said:
That is a very detailed and useful explanation, thank you.
As far as the reliability statement, I actually mean reliability in terms of unreliability (for exploitations). I have a Nintendo 3DS and PS3 on older firmwares and both times the older firmware has proven invaluable.
Click to expand...
Click to collapse
You're welcome.
Again, welcome to our little portion of XDA, and I hope you have fun.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
You're welcome.
Again, welcome to our little portion of XDA, and I hope you have fun.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I already have and will certainly continue to. I followed through all the information you gave me and would like to report back with this little tidbit from my computer. Link.
Gamemaster1379 said:
I already have and will certainly continue to. I followed through all the information you gave me and would like to report back with this little tidbit from my computer. Link.
Click to expand...
Click to collapse
Nice. Congrats!
Sent from my SM-N900P using Xparent BlueTapatalk 2
Related
My stats: Fairly comfortable with computer and other forms of tech, but have only recently began diving into the Android system. I have limited development/programming experience, however, I'm not a novice or noob to it but definitely not advanced. Importantly for those willing to help I understand most terminology and can follow instructions. Thanks in advance.
Phone Stats: AT&T Samsung Galaxy Note SGH-i717
Android Version: 2.3.6 (Gingerbread)
Baseband Version: i717UCLF6
Kernel Version: 2.6.35.11
Build number: GINGERBREAD.UCLA1
Root Access: Yes
Stock Rom: Unsure, bought online.
Carrier/Service Provider: Straight Talk (U.S.) Phone was previously used on the AT&T network exclusively, and done so with an AT&T provided SIM card. After I purchased it, I ordered a new SIM card from Straight Talk (U.S.) and reprogrammed the APN settings under their instruction in order for my phone service to work correctly, and have had no problems with that.
I can't stand being on Gingerbread any longer. I guess, since my phone is an AT&T phone but I'm using it through Straight Talk I can't get any of the OTA updates. I've tried downloading the OTA's several times, both, prior to and post Root access without success in either case.
So here are my questions:
1. Am I doing something incorrectly which might be keeping me from getting OTA updates? Please remember, I've tried downloading the OTA's several times both with and without Root Access and the conclusion is the same each time: "No Updates Available At This Time. Your Phone Appears To Be Up To Date. Try Again In 24hrs."
2. Is my only option at this point to manually update to a newer firmware? If so, should I update to a newer STOCK version or a custom ROM version?
3. If a manual update is the option, after reading my above outline of my own experience with the Android system, what would be way to go? Simple, not overly complex yet doesn't assume the user is either a complete moron or can write code in his sleep. I've checked into a couple of options. Rom Manager seems like it would be a nice route to go, but in the Recovery Setup portion I basically get told I can't use that application because my specific device isn't supported.
I checked out GooManager and, unless it's just me, it seems like it's an app that likes to do all the work without telling you what it's doing exactly, but when it does ask me or tell me information, I'm not always sure how to answer or react to it's warnings.
Plus, I've noticed that sometimes when downloading a ROM, sometimes I have to "flash" the gapps myself and other times I don't.
4. Is it easier to download everything separately and apply them one by one, for example the ROM then gapps then Kernal...etc? Or look for something that has it all in one package?
I have a laptop in which I can download/transfer programs and apps between it and my Note so download space and internet access isn't a problem.
Also, it most likely isn't information that is going to help in anyway, but I live in Oklahoma, United States of America.
Thanks for all the feedback...UnluckyOnion
I'm not answering these in any specific order,
As I kinda just sped read thru most of it...
Since you're rooted, or know how to, goomanager is superior to Rom manager.
It supports this device and has a current version of twrp to install, instead of an outdated cwm.
Just use it to install recovery, then boot your device into recovery and use that. Not the app. You'll be provided with much more information and this is the preferred way of flashing.
Official Updates are always "manual" either with a less than user friendly program called kies, or with a less annoying way (which you may be familiar with seeing as you've rooted) ODIN. Both pc programs used with the phone in download mode connected with usb cable.
Gapps are only needed to flash separately with an aosp based Rom as it's against Google's T.o.S. to include them in am entirely aftermarket compiled firmware, however if it's a Modified version of a stock based Rom (in this case TouchWiz) they can be, and thusly are, included within.
Official or custom is up to you really.
If official..just grab the .tar and flash it with Odin.
If custom, obtain a custom recovery either the way i mentioned above or downloading a .tar of twrp and use Odin to flash that.
Once you have a custom recovery, you'll simply be able to flash a Rom from there.
Roms include a kernel, if you want to use a different one than what is included, that would be flashed after the Rom.
After flashing you'll have to input your carriers apn settings in again.
studacris said:
I'm not answering these in any specific order,
As I kinda just sped read thru most of it...
Since you're rooted, or know how to, goomanager is superior to Rom manager.
It supports this device and has a current version of twrp to install, instead of an outdated cwm.
Just use it to install recovery, then boot your device into recovery and use that. Not the app. You'll be provided with much more information and this is the preferred way of flashing.
Official Updates are always "manual" either with a less than user friendly program called kies, or with a less annoying way (which you may be familiar with seeing as you've rooted) ODIN. Both pc programs used with the phone in download mode connected with usb cable.
Gapps are only needed to flash separately with an aosp based Rom as it's against Google's T.o.S. to include them in am entirely aftermarket compiled firmware, however if it's a Modified version of a stock based Rom (in this case TouchWiz) they can be, and thusly are, included within.
Official or custom is up to you really.
If official..just grab the .tar and flash it with Odin.
If custom, obtain a custom recovery either the way i mentioned above or downloading a .tar of twrp and use Odin to flash that.
Once you have a custom recovery, you'll simply be able to flash a Rom from there.
Roms include a kernel, if you want to use a different one than what is included, that would be flashed after the Rom.
After flashing you'll have to input your carriers apn settings in again.
Click to expand...
Click to collapse
Thanks for all the information and help...more importantly, thanks for taking the time. I have ODIN on my laptop and have always used it when needed but I saw a highly rated and positively commented Mobile version of ODIN in the Play Store that claims you can do everything from the convenience of your phone which sounds appealing, however it's kinda pricey, especially if it doesn't work. Would you recommend the mobile version or PC version? Also, I have been doing a lot of ROM and Root research as of late, and wondered something...Why so many different Galaxy Note's? It seems as though I have the least popular version with the most popular being from the Galaxy Note "N" series, specifically the N7000. If I download and use an application that says it's meant for the Galaxy Note N7000 and I use it on my Galaxy Note SGH-i717, what will happen? Nothing, something, brick, work perfectly, etc...?
The N series is not carrier branded and sold internationally, so naturally it's more popular compared to a north American variant.
DO NOT FLASH ANYTHING FOR THE N7000
IT WILL BRICK YOUR PHONE.
The international version has a different cpu, gpu and antenna, for north American LTE bands to work those key components needed to be different.
So I say again just to stress:
DO NOT FLASH ANYTHING FOR THE N7000
IT WILL BRICK YOUR PHONE.
As for Odin, you're either going to flashing a stock firmware, or if you choose a custom Rom, you'll only need Odin once to flash TWRP. Then all the rest will be done in recovery on the phone itself. No need for it after you've either manually updated to the latest stock rom, or flashed a recovery for use of custom roms
So... imo mobile Odin, though being nifty, is a bit pricey for how little you'll need it, whereas it's free on pc.
I don't think mobile Odin is even available for the i717. It's not listed in supported devices.
I tried installing mobile odin and it's not supported
Thanks for the reply. And an even bigger Thanks for downloading the app and checking. I admire sacrificing your own work just to help me out. So what about yourself? Would you suggest, advise or heed caution to anymore of my questions?
By the way, what are you two running?
As long as you read the op of threads and all other important posts that follow BEFORE ever touching your phone, I'd say try a custom Rom...if you decide you don't like any of them, you can Odin flash the stock jellybean firmware at any point.
I myself am running unofficial aokp compiled and posted by a fellow team member BlownFuze.
Oh yeah, how's it running? Nice and stable or crawling with bugs? Any key selling points?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I'm on the stock 4.1.2 release and rooted.
Everything works, no bugs, but battery sucks. Even after removing and freezing useless processes a stock rom will never be as light and battery friendly as a custom rom.
I just upgraded to the same version. Planned on rooting over weekend. Any success since your last post? Do you nave preferred Root method?
Thanks
Unlucky Orion
Use Odin to flash twrp
Newest version of twrp "should" Sr that you're not rooted and ask if you would like to do so within recovery before booting back into the os.
If not, there's links to an su.zip to flash in twrp for root.
studacris said:
Use Odin to flash twrp
Newest version of twrp "should" Sr that you're not rooted and ask if you would like to do so within recovery before booting back into the os.
If not, there's links to an su.zip to flash in twrp for root.
Click to expand...
Click to collapse
Hey man, thanks, it worked like a charm. I appreciate the help from both you.
The only thing I want to do and can't make work is the Wifi Hotspot (I used FoxFi on my old phone and I loved it and have already paid for the license, if using it is possible)
My concerns in order of importance to me:
Stability is critical.
I don't want to own a $700 brick.
I need to be able to use my unlimited data plan to create a hotspot several times a week.
Not voiding warranty.
If the advice is to root to achieve this function, what is the safest rooting process, with the most reliable outcome for my above 4 concerns?
kjinmn said:
The only thing I want to do and can't make work is the Wifi Hotspot (I used FoxFi on my old phone and I loved it and have already paid for the license, if using it is possible)
My concerns in order of importance to me:
Stability is critical.
I don't want to own a $700 brick.
I need to be able to use my unlimited data plan to create a hotspot several times a week.
Not voiding warranty.
If the advice is to root to achieve this function, what is the safest rooting process, with the most reliable outcome for my above 4 concerns?
Click to expand...
Click to collapse
Every Rom I've flashed for this phone has been at least as stable as stock if not more so.
The rooting process for this phone is simple as can be, I haven't seen any reports of bricks.
Hotspot working in pretty much all the TW Roms, not sure about CM
Rooting voids warranty, Sprint will "USUALLY" fix it anyway
Chainfire's one click root is the best way to go, all that does is give you root and you can stop there if you want to stay stock with root privileges. If you want a custom recovery so you can flash new Roms, that's another very simple step. Chainfire's thread gives you all the instruction you need. Hope this helps.
Agree with number three ^^
Do it, and if you run into issues, plenty of people here to help you... When all else fails, search out The Mic...
Sent from my SM-N900P using Tapatalk
Is it a safe guess, that rooting wipes the phone?
Kj
Samsung Note 3, unmodified
I used cf auto and it didn't wipe. (Lol)
kjinmn said:
Is it a safe guess, that rooting wipes the phone?
Kj
Samsung Note 3, unmodified
Click to expand...
Click to collapse
Not at all. It injects stock kernel (I believe, may be recovery) and superuser app. That's it.
Sent from my SM-N900P using Xparent BlueTapatalk 2
I tried everything to get it to work and I was rooted.
Only after I installed a custom rom did it work.
At first I rooted with kingo to keep knox 0x0, eventually I said screw it and installed TWRP and now I'm 0x1. I have not read of anyone that has been denied by sprint for warranty work, or at least tried a different store and was successful.
bobturismo said:
I tried everything to get it to work and I was rooted.
Only after I installed a custom rom did it work.
At first I rooted with kingo to keep knox 0x0, eventually I said screw it and installed TWRP and now I'm 0x1. I have not read of anyone that has been denied by sprint for warranty work, or at least tried a different store and was successful.
Click to expand...
Click to collapse
There are a few reports of it here on these forums, but you are correct in that a bit of tenacity seems to have paid off for most.
Irrespective, if you are happy with your choice, then you made the right call.
I believe many here sort of held their breath either before or during the Knox tripping deed.
Some early adopters of the device were left with few tools even to take an upgrade. Thank goodness for the dev community.
Just be thankful that they are here. When KitKat drops, we're gonna need them a heck of a lot more than they need us. Perhaps throw your favorite dev some jingle. It's not like they are making mad money. And the mouth-frothing types with which they are confronted from time to time alone makes it worth the doing.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Not at all. It injects stock kernel (I believe, may be recovery) and superuser app. That's it.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Which root method do you use?
Is that what you'd recommend for my situation? If not, which would you suggest?
micmars said:
There are a few reports of it here on these forums, but you are correct in that a bit of tenacity seems to have paid off for most.
Irrespective, if you are happy with your choice, then you made the right call.
I believe many here sort of held their breath either before or during the Knox tripping deed.
Some early adopters of the device were left with few tools even to take an upgrade. Thank goodness for the dev community.
Just be thankful that they are here. When KitKat drops, we're gonna need them a heck of a lot more than they need us. Perhaps throw your favorite dev some jingle. It's not like they are making mad money. And the mouth-frothing types with which they are confronted from time to time alone makes it worth the doing.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I am ready to root today (finally). I got the OTA KITKAT update pushed out to me from Sprint. I have not installed it, and want to root before I do. Can you recommend a ROM to download & install?
Kj
Samsung Note 3, unmodified
Got to Upgrade Then Root...
kjinmn said:
I am ready to root today (finally). I got the OTA KITKAT update pushed out to me from Sprint. I have not installed it, and want to root before I do. Can you recommend a ROM to download & install?
Kj
Samsung Note 3, unmodified
Click to expand...
Click to collapse
If you are NOT rooted, then you must upgrade first, then root. If you do not wish to upgrade to KitKat, then you may root now, but the upgrade will not install. Samsung's syscope service will check the status of your phone (official/custom), and your ability to install the update will be nullified if you root whilst on MJ4.
So...upgrade then root. If you need help with rooting, write back. As to preference of ROM, I am a TouchWiz guy that loves inverted apps. Others like AOSP and swear by it. Just select the direction you want and hit the dev forum. There are many good ROMS from which to choose.
Good luck!
micmars said:
If you are NOT rooted, then you must upgrade first, then root. If you do not wish to upgrade to KitKat, then you may root now, but the upgrade will not install. Samsung's syscope service will check the status of your phone (official/custom), and your ability to install the update will be nullified if you root whilst on MJ4.
So...upgrade then root. If you need help with rooting, write back. As to preference of ROM, I am a TouchWiz guy that loves inverted apps. Others like AOSP and swear by it. Just select the direction you want and hit the dev forum. There are many good ROMS from which to choose.
Good luck!
Click to expand...
Click to collapse
These were my main concerns:
kjinmn said:
My concerns in order of importance to me:
Stability is critical.
I don't want to own a $700 brick.
I need to be able to use my unlimited data plan to create a hotspot several times a week.
Not voiding warranty.
Click to expand...
Click to collapse
#1 & #3 are what I need for function on a daily basis. I have never rooted before or flashed a ROM. I will gladly accept any advice you would offer.
Kj
Samsung Note 3, unmodified
Then...
kjinmn said:
These were my main concerns:
#1 & #3 are what I need for function on a daily basis. I have never rooted before or flashed a ROM. I will gladly accept any advice you would offer.
Kj
Samsung Note 3, unmodified
Click to expand...
Click to collapse
Then if 1 & 3 are critical, and you understand that tripping Knox will make life more difficult inasmuch as you will not be sending your phone to Sammy for repairs, then root, install recovery, and install the Stockish DeOdex ROM from freeza's thread. There's a hotspot mod that is DeOdex that Josh Beach has made available on his Website for the entire community running KitKat.
Ultimately I cannot advise as to whether tripping Knox should be a concern for you. However, if it is your phone and not one provided for you by a company, and you're not going against an employer's policy against rooted devices, then tripping Knox is less of a big deal than some may make of it. I thought it was a terrible deal, and didn't buy this phone until I made the conscious decision to say screw it, tripping Knox is fine for me. I then, and only then, bought the phone.
There are a ton of ways to get your phone repaired, none of which require sending it to any manufacturer. I have 2 Sprint stores within 10 miles of me. Both will repair the phone or exchange it if I have a dysfunctional phone that has been rooted. Others on these forums have reported Sprint techs denying them service if Knox has been tripped. You need to make your own choice on this one.
I hope this helps.
Good luck!
micmars said:
Then if 1 & 3 are critical, and you understand that tripping Knox will make life more difficult inasmuch as you will not be sending your phone to Sammy for repairs, then root, install recovery, and install the Stockish DeOdex ROM from freeza's thread. There's a hotspot mod that is DeOdex that Josh Beach has made available on his Website for the entire community running KitKat.
Ultimately I cannot advise as to whether tripping Knox should be a concern for you. However, if it is your phone and not one provided for you by a company, and you're not going against an employer's policy against rooted devices, then tripping Knox is less of a big deal than some may make of it. I thought it was a terrible deal, and didn't buy this phone until I made the conscious decision to say screw it, tripping Knox is fine for me. I then, and only then, bought the phone.
There are a ton of ways to get your phone repaired, none of which require sending it to any manufacturer. I have 2 Sprint stores within 10 miles of me. Both will repair the phone or exchange it if I have a dysfunctional phone that has been rooted. Others on these forums have reported Sprint techs denying them service if Knox has been tripped. You need to make your own choice on this one.
I hope this helps.
Good luck!
Click to expand...
Click to collapse
I have made my peace with the idea of voiding warranty. I talked to a Sprint store tech, and he said no one in the store even cares about Knox. If it breaks, bring it in, and they will fix it.
So my plan is to:
1)Upgrade via the OTA. File
2) root via one-click method
3) install the Stockish DeOdex ROM from freeza's thread
4) Install the hotspot mod that is DeOdex from Josh Beach's Website.
Sound good?
Kj
Samsung Note 3, unmodified
Close, but Sligthly Altered...
kjinmn said:
I have made my peace with the idea of voiding warranty. I talked to a Sprint store tech, and he said no one in the store even cares about Knox. If it breaks, bring it in, and they will fix it.
So my plan is to:
1)Upgrade via the OTA. File
2) root via one-click method
3) install the Stockish DeOdex ROM from freeza's thread
4) Install the hotspot mod that is DeOdex from Josh Beach's Website.
Sound good?
Kj
Samsung Note 3, unmodified
Click to expand...
Click to collapse
You're close; I would amend it slightly (my comments as to what each stop give you as an outcome are adjacent each numbered item); also, the files you will need are embedded in the links below, so grab them prior to doing any of this)
1. Upgrade via OTA, since you're status is official
-->Let phone do it's stupid updating system garbage, blah blah, don't waste your time dialing in your GMail address, &c because you're going to be doing this again shortly
-->Gives you stock, unrooted phone up to the latest Sprint build for our phone
2. Install TWRP recovery for this phone version 2.7.0.0, flash via PC Odin (Version 3.07 is here if you like, works just fine)
-->Gives you the ability to flash a root file, or flash a pre-rooted rom, back up your phone setup, flash mods like the hotspot hack, &c.
-->Instructions basically are to power off your phone, take any casing off of the phone, right-click on the Odin.exe file, select run as administrator, hit OK/Yes from Windows User Account Control prompt, load the tar file I linked in the PDA slot of Odin, put your phone in download mode (Home + Volume Down + Power), plug the phone into the USB port on your computer that you've used in the past (this way the Samsung drivers for that device won't be loading while you're trying to get recovery on your device), have the phone in the palm of your hand, have your fingers ready to hit Home + Volume up, then hit start on Odin, once file flashes and phone starts to power cycle (like in 5-10 seconds after hitting start), hit those two buttons, you're in recovery
3 Download freeza's Stockish DeOdex NABD ROM from this link, put it on your phone's internal memory AFTER you've taken the upgrade to KitKat, check the MD5 of the file download using this tool, unzip onto your PC, execute the file named "MD5.exe," copy the MD5 for the ROM I linked into the top portion of the program (you'll see it, the button "Paste" is adjacent the text box), MD5=7d0749d2362d872ca8db7c524d25bf40, copy that and paste it into the MD5 file and make sure you have a clean download
-->You now have a ROM that you can fully set up your phone, import your contacts, download programs, flash mods, anything you want that is compatible
4. Flash the Hotspot Mod provided by Josh Beach at his K3 site, under MODS for NABD, hotspot link on this page
-->Gives you the hotspot mod you want
Have a blast!
micmars said:
You're close; I would amend it slightly (my comments as to what each stop give you as an outcome are adjacent each numbered item); also, the files you will need are embedded in the links below, so grab them prior to doing any of this)
1. Upgrade via OTA, since you're status is official
-->Let phone do it's stupid updating system garbage, blah blah, don't waste your time dialing in your GMail address, &c because you're going to be doing this again shortly
-->Gives you stock, unrooted phone up to the latest Sprint build for our phone
2. Install TWRP recovery for this phone version 2.7.0.0, flash via PC Odin (Version 3.07 is here if you like, works just fine)
-->Gives you the ability to flash a root file, or flash a pre-rooted rom, back up your phone setup, flash mods like the hotspot hack, &c.
-->Instructions basically are to power off your phone, take any casing off of the phone, right-click on the Odin.exe file, select run as administrator, hit OK/Yes from Windows User Account Control prompt, load the tar file I linked in the PDA slot of Odin, put your phone in download mode (Home + Volume Down + Power), plug the phone into the USB port on your computer that you've used in the past (this way the Samsung drivers for that device won't be loading while you're trying to get recovery on your device), have the phone in the palm of your hand, have your fingers ready to hit Home + Volume up, then hit start on Odin, once file flashes and phone starts to power cycle (like in 5-10 seconds after hitting start), hit those two buttons, you're in recovery
3 Download freeza's Stockish DeOdex NABD ROM from this link, put it on your phone's internal memory AFTER you've taken the upgrade to KitKat, check the MD5 of the file download using this tool, unzip onto your PC, execute the file named "MD5.exe," copy the MD5 for the ROM I linked into the top portion of the program (you'll see it, the button "Paste" is adjacent the text box), MD5=7d0749d2362d872ca8db7c524d25bf40, copy that and paste it into the MD5 file and make sure you have a clean download
-->You now have a ROM that you can fully set up your phone, import your contacts, download programs, flash mods, anything you want that is compatible
4. Flash the Hotspot Mod provided by Josh Beach at his K3 site, under MODS for NABD, hotspot link on this page
-->Gives you the hotspot mod you want
Have a blast!
Click to expand...
Click to collapse
I want to thank you. This is the first easy-to-follow simple guide to rooting I have had to follow. It all went flawlessly. Stable as ever, and wireless works great!
Thank you very much!
micmars said:
You're close; I would amend it slightly (my comments as to what each stop give you as an outcome are adjacent each numbered item); also, the files you will need are embedded in the links below, so grab them prior to doing any of this)
1. Upgrade via OTA, since you're status is official
-->Let phone do it's stupid updating system garbage, blah blah, don't waste your time dialing in your GMail address, &c because you're going to be doing this again shortly
-->Gives you stock, unrooted phone up to the latest Sprint build for our phone
2. Install TWRP recovery for this phone version 2.7.0.0, flash via PC Odin (Version 3.07 is here if you like, works just fine)
-->Gives you the ability to flash a root file, or flash a pre-rooted rom, back up your phone setup, flash mods like the hotspot hack, &c.
-->Instructions basically are to power off your phone, take any casing off of the phone, right-click on the Odin.exe file, select run as administrator, hit OK/Yes from Windows User Account Control prompt, load the tar file I linked in the PDA slot of Odin, put your phone in download mode (Home + Volume Down + Power), plug the phone into the USB port on your computer that you've used in the past (this way the Samsung drivers for that device won't be loading while you're trying to get recovery on your device), have the phone in the palm of your hand, have your fingers ready to hit Home + Volume up, then hit start on Odin, once file flashes and phone starts to power cycle (like in 5-10 seconds after hitting start), hit those two buttons, you're in recovery
3 Download freeza's Stockish DeOdex NABD ROM from this link, put it on your phone's internal memory AFTER you've taken the upgrade to KitKat, check the MD5 of the file download using this tool, unzip onto your PC, execute the file named "MD5.exe," copy the MD5 for the ROM I linked into the top portion of the program (you'll see it, the button "Paste" is adjacent the text box), MD5=7d0749d2362d872ca8db7c524d25bf40, copy that and paste it into the MD5 file and make sure you have a clean download
-->You now have a ROM that you can fully set up your phone, import your contacts, download programs, flash mods, anything you want that is compatible
4. Flash the Hotspot Mod provided by Josh Beach at his K3 site, under MODS for NABD, hotspot link on this page
-->Gives you the hotspot mod you want
Have a blast!
Click to expand...
Click to collapse
thanks for this thread OP and for this answer micmars. too bad i rooted before updating and now its blocked
Greatness83 said:
thanks for this thread OP and for this answer micmars. too bad i rooted before updating and now its blocked
Click to expand...
Click to collapse
No problem at all. Actually, the answers to your setup are answered here as well, but this was tailored to someone whom hadn't rooted and could take the update
I see on your thread that someone got you running, which ultimately is what we like to hear (ie, you have what you want, and nothing less).
Congrats!
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
No problem at all. Actually, the answers to your setup are answered here as well, but this was tailored to someone whom hadn't rooted and could take the update
I see on your thread that someone got you running, which ultimately is what we like to hear (ie, you have what you want, and nothing less).
Congrats!
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Thanks. Indeed. It just kind of pointed me in the right direction. Now off to find a good kernel!
First, a HUGE thanks goes to @garwynn for being my partner through all of this and then to @sfhub for teaching me how to create an Odin One-Click.exe, @Skunk Ape1 for posting the original TAR this is based off of, @MoHoGalore for helping test and put together so many of these one-clicks and to everyone else in our community who makes this possible!
Second, I was asked to make this one-click to help simplify the process of restoring a stock factory build for our Note 3 users. I do not own a Note 3 so I have not been able to test this as I would normally prefer to do before releasing. I do however feel comfortable that it should work as designed. Due to the fact that we do not have a Note 3 to be testing it on, at this time neither myself or Garwynn are planning on releasing a rooted One-Click. There is a lot more risk involved when building the rooted versions and we don't want to take that risk with other people's phones.
This Odin One-Click.exe contains the Stock SM-N900P MJ4 Bootloader, Kernel, Modem and ROM for the Sprint Samsung Galaxy Note 3 (SM-N900P). 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 MJ4 experience, similar to a factory restore and it will probably 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 MJ4 Stock ROM One-Click.
SM-N900P MJ4 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 "SPH-N900P MJ4 Full Restore (Unrooted).exe" was saved upon extract from the 7Zip archive.
Double-click on "SPH-N900P MJ4 Full Restore (Unrooted).exe". *On Vista or newer, you may need to right-click on the file and 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.
Android Instructions:
Download and install ZArchiver on your phone. Use it to unpack the Odin One-Click 7zip self-extracting exe file (long press on the 7zip exe. Select "Open As Archive". Select the One-Click.exe and then select Extract). Use Mobile Odin to Open File on the "SPH-N900P MJ4 Full Restore (Unrooted).exe". FYI - Modem will not flash with Mobile Odin.
The boot process will take slightly longer than usual during which time you'll see the Sprint 4G logo screen.
Congratulations! You've flashed the Factory Restore MJ4 build!
XDA:DevDB Information
[ROM][ODIN] SM-N900P MJ4 (MJ4 Modem/Kernel/Bootloader/ROM - Full Restore - Unrooted), ROM for the Sprint Samsung Galaxy Note 3
Contributors
rwilco12
ROM OS Version: 4.3.x Jellybean
Version Information
Status: Testing
Created 2015-02-10
Last Updated 2015-02-10
Download Link: http://www.rwilco12.com/forum/showthread.php?tid=94
Additional Resources:
7-Zip v9.20
Odin3 v3.04
ZArchiver
Mobile Odin Lite
Samsung USB Drivers
Thank you so much for this
Sent from my SM-N900P using Tapatalk
I'm confused on the android steps. I've completed the PC part with the phone in download mode, I have the zarchiver installed, but where do I find the file I need on my phone?
Please help, thanks!
groovdafied said:
I'm confused on the android steps. I've completed the PC part with the phone in download mode, I have the zarchiver installed, but where do I find the file I need on my phone?
Please help, thanks!
Click to expand...
Click to collapse
someone correct me if im wrong. but if you have completed the pc steps. you should be done. the android verison of this is doing what you just did on the pc but on your phone.
but as noted on orginal post. using thru android it doesn't come with modem so u would have to search the xda thread for the stock mj4 note 3 modem. and also flash that. a harder process but once you get the hang of it can really helps while on the fly.
but also today I unrooted my phone back to stock mj4 to see if the update has came out for my phone yet. if you get an error that you was unable to do a system update because of the phone being modified. online it tells you to go to stock recovery and do a factory reset. this didn't help for me. but what did was using odin again and flashing tht stock tar again. then I was back to official and able to check for my system update. But no update yet for me? :crying:
Can this be used once you have updated to NAB ? Or is there no going back once updated to kitkat ?
Sent from my SM-N900P using xda app-developers app
chumpalunski said:
Can this be used once you have updated to NAB ? Or is there no going back once updated to kitkat ?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
No going back once you are on 4.4 firmware... At least not yet anyway.
Sent from my SM-N900P using Tapatalk 2
The SM-N900P MJ4 Full Restore Unrooted (Compressed Archive).exe will not run for me on Windows 8. The error message says that it isn't for my pc.
Am I missing something?
Worked flawlessly for me. Did u run the file as an administrator?
Sent from my SM-N900P using Tapatalk
rpenrod23 said:
No going back once you are on 4.4 firmware... At least not yet anyway.
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
Really wish I would have read that first before spending an hour troubleshooting why it wouldn't install. Guess I'm stuck on Kit Kat now.
not to beat a dead horse kor but this "Going back to 4.3" has been TALKED about all over the forums. Hence the reason why most of the kit kat rom threads are so short..not many activity on them..Most people are going AOSP for their 4.4.2 thrills cause you can easily nandroid back to 4.3 rom..I'm definitely not officially kitkating until there's a sure method of going back (If ever possible) to 4.3 ..Kit kat just looks so UGLY in my honest opinion..LOL..Good luck with it though..
Yes..It Has Been Talked About...
3.0VTEC23 said:
not to bea a dead horse kor but this "Going back to 4.3" has been TALKED about all over the forums. Hence the reason why most of the kit kat rom threads are so short..not many activity on them..Most people are going AOSP for their 4.4.2 thrills cause you can easily nandroid back to 4.3 rom..I'm definitely not officially kitkating until there's a sure method of going back (If ever possible) to 4.3 ..Kit kat just looks so UGLY in my honest opinion..LOL..Good luck with it though..
Click to expand...
Click to collapse
I appreciate your post, and find it to be a good launch-point for some observations of my own. What is to follow was merely sparked by what you wrote, and is not by any means a response to it. Free association if you will.
Sprint Note 3 TouchWiz KitKat has been talked about for more than 7 weeks...
It started 52 days ago here on 30 January 2014, with the NA4 leak engineering build...yet no one would blame a dev or themer whom did not want to dive into the hard work of rom development with a leak. Kind of like doing restoration work on a house you are renting...seems like wasted effort.
It then obtained an official tar release on 20 February 2014, 21 days later, or 31 days ago, which was simultaneous with the ROM's official push from Sprint.
It was also DeOdexed and Odexed on that same date, which by my measuring stick is the official date that development work began. The base stock thread from which all TouchWiz ROM development work springs began 6 October 2013, with the DeOdex and Odex versions of MI5; it is now 137 pages/1360+ posts and counting, with the official NABD rom base being deployed on page 49, so thus 70% of the thread is KitKat, 30% is Jellybean...quite a feat in one-month's period.
Since 20 February 2014, we've attained...
-->Hotspot
-->4-1 reboot
-->Boot animations
-->Themes for stock roms that work well and look stunning to some
-->Mature, stable roms that are each unique in their own way, either by look, performance, or both
***IMHO, more roms does not mean better....it is the quality of the roms on-hand that I highly value
-->Native call recording that does not yield static but actually records calls (something our dev community seems to have accomplished in faster time than most)
-->Ported roms
***XNote
***I'm personally testing as of this writing a ported T-Mobile rom that is blazing fast and is a wonderful experience overall
-->Universal porting script for this phone (not unique to XDA by any means, but surely unique to this device)
-->ROM that actually performs settings behind the scenes during install, much the way the carriers release rom updates en masse, something truly groundbreaking, the significance of which we can only imagine, but it is a major milestone
***And so much more to come
When I look at the trajectory of development for this phone's version of KiKat, I am proud of both our devs and also our users.
Compare it further to the days of MJ4, and the full host of stable roms from the first DeOdex release, and I'd say we are running ahead of schedule (we are, just have a look for yourself).
So while the hard work is being lain by the folks here doing the heavy lifting, I highly encourage all to make a choice that is right for them. One individual's undesirable-ugly rom may be another's must-have. I'll defer to each user as to whether they may choose to upgrade. I personally started 54 days ago, when I could go back, and yet I wouldn't go back if you paid me.
I would add that some of those short-length threads to which you allude are deceiving, inasmuch as half of the discussion of the KitKat version of a given rom was being discussed in the MJ4/JB 4.3 version of same.
I choose not to imbibe AOSP 4.4.2, though I admire them greatly, and yet comparing it to TouchWiz KitKat seems rather an apples-to-oranges endeavor. One will not experience KitKat on the Note 3 as it was intended unless one takes in the manufacturer's version of same. They are just different. I'm unclear how thrilling AOSP is to some, or if one could aver with any degree of certainty if the majority has chosen not to upgrade.
In a few weeks, it is not a choice, as the phones will be leaving the stores already loaded with KitKat (upgrade already pre-installed). And for them, they ain't going back. And they will be here, hopefully as thrilled as I with the wide variety of options gifted to us by the incredible creativity of our fine community.
Lol®
Mic, you're a Brilliant person, very very very well said/explained and you have actually opened up my eyes a bit with kitkat..Even though, I will not be taking the plunge still..
Mind=Blown
#Micmars #IncredibleInsights
Sent from my SM-N900P using XDA Premium 4 mobile app
Does this also reset knox, and the counter?
eskion said:
Does this also reset knox, and the counter?
Click to expand...
Click to collapse
It doesn't. Sorry!
Damn, any word on that being done?
eskion said:
Damn, any word on that being done?
Click to expand...
Click to collapse
I don't think that's gonna happen, my friend, so far I heard from many trusted devs, once you trip knox there's not going back, you'll need a new board
Sent from my SM-N900P using Tapatalk
Excellent! This is definitely an easy way to flash back to stock on those days when you just don't think and do something stupid that fubars your Note 3. I did have an issue... once I flashed and rebooted, my Note 3 got stuck at the Sprint logo screen. Reflashed and same problem... Did the vol up + home + power, then pressed volume down to reboot phone, same issue. I decided to go into recovery and wipe dalvic cache, then rebooted phone... it worked, the ol Note 3 booted up and started initial setup. Don't know if there was coincidence involved, but I thought I'd throw that in there just in case somebody else runs into the same problem.
When I open up the exe file for MJ4, the odin is blank....attached it a screenshot. Is it supposed to be?
Also, will this get my recovery back?
I experienced spontaneous reboots, & I use Safestrap 3.65 & I noticed that SS was missing in the Stock slot. I'm rooted & running HyperDrive 10.2 & Android OS 4.2.2 - or was....
I d/l'ed SS3.65 & to be sure I used the app to remove the recovery & then reinstalled the recovery on the Stock side & rebooted & recreated slot 1 w/HyperDrive 10.2 via a nand backup.
However, I kept getting spontaneous reboots, so I tried to do a full factory reset on the Stock side & when I tried to reboot the only thing that shows is the "Custom" warning & it doesn't move from there.... I have to remove the battery to turn off the phone.
I did some homework & looking back at it, I shouldn't have done the full factory reset before removing the recovery...
I do NOT have nor do I know ADB, but I need to get back my S4 if possible, I would greatly appreciate any help.
I am in New York City, so if there are any locals that can help, but need to look at it; I can get around to the 5 boros.....
Thanks very much in advance, Oldwolf
If you know what your original build was you could use Odin to get back to stock.
Sent from my NCC-1701 using Tapatalk.
Riker, tnx so much for ur tip! I was on MI1, can I just Odin that?, or do I need the version that was 'native' to the phone.
Also, I need input on how to get into the mode needed for Odin to work- I forgot the button-press sequence… also, please tell me where to find the required driversto get my new PC (Win7) to 'see' the S4.
Unfortunately, most of my hacking b4 has been on the Moto platform; so I'm still 'Green' w/the Sammy stuff…
Thanks again! oldwolf
oldwolf613 said:
Riker, tnx so much for ur tip! I was on MI1, can I just Odin that?, or do I need the version that was 'native' to the phone.
Also, I need input on how to get into the mode needed for Odin to work- I forgot the button-press sequence… also, please tell me where to find the required driversto get my new PC (Win7) to 'see' the S4.
Unfortunately, most of my hacking b4 has been on the Moto platform; so I'm still 'Green' w/the Sammy stuff…
Thanks again! oldwolf
Click to expand...
Click to collapse
You should be able to recover easily. It's not a hard brick by all means.
First, follow this link http://forum.xda-developers.com/showthread.php?t=2301259 and donwload the MI1 odin file. It should come as a zip but you unzip it and then you get a .tar file.
Then, download odin 3.09. A simple google will give a link.
Then, put phone in download mode. From a power off state, hold home button+volume down+power button. To get it powered off, you may have to pull battery and reinsert. Plug in usb cable into cpu and phone.
Then in odin, leave everything the same, click AP, choose the mi1 tar file.
Run odin
Done! :good::good:
Richard, thanks so much for your clear steps. What about rooting once I get MI1 up & running? It feels funny; in the Moto world I wouldn't have to ask… but so far in the Sammy world I've only rooted & Odin'ed once a long while back…
Also, what about taking an OTA update?, from what I've seen, it is not a good idea b/c of tougher security fm Sammy- but I heard there is an NC5 image that is rootable & you can even roll back… anybody have any ideas?
I'm also considering a diff ROM, but suggestions would be welcome- I've been spending a lot of time on my PC…
thanks in advance to all, Oldwolf
To All, never mind about the re-rooting question. I didn't know the link in the prev answer provided guidance for this.
I really appreciate getting timely responses & people being willing to help me get into the Sammy side of hacking…
Custom ROM suggestions?
What is the feel about taking the OTA update once I have MI1 Stock - it seems that there are more updates for HyperDrive available for 4.3 or 4.4x, or even Lollipop- but t_ere were reports of probs w/diff things, Wifi I believe & now that VZW has enticed me to give up unlimited data (for a sweethevrt deal on unlimited talk & text) I can't afford yo be w/out wifi…
regards, Oldwolf
oldwolf613 said:
Richard, thanks so much for your clear steps. What about rooting once I get MI1 up & running? It feels funny; in the Moto world I wouldn't have to ask… but so far in the Sammy world I've only rooted & Odin'ed once a long while back…
Also, what about taking an OTA update?, from what I've seen, it is not a good idea b/c of tougher security fm Sammy- but I heard there is an NC5 image that is rootable & you can even roll back… anybody have any ideas?
I'm also considering a diff ROM, but suggestions would be welcome- I've been spending a lot of time on my PC…
thanks in advance to all, Oldwolf
Click to expand...
Click to collapse
My personal, non-richard, suggestion would be to odin to nc5, towelroot, get safestrap 3.75, then download either eclipse, hyperdrive or a safestrap compatible google play edition rom. This is because nc5 is simply a newer version and MI1 doesn't give you any special tweaks that nc5 doesn't have.
there are many threads around these forums discussing each step of the process that I've listed. Try searching for them first. I like to simply type in google " towelroot s4 xda" for example. If you can't find a thread that helps, i'll be happy to assist you.
p.s. I'm not richard.
Raymond, er, um, uh?!
Sorry about calling you that other name.... guess I was distracted... you know, w/my S4 sitting corrupted on the table & all.... & it looks like I gotta get more sleep.....
I noted in the thread you mentioned SafeStrap 3.75 & Towel Root, & a SS-compatible Google Play Edition Rom.... mine is a retail VZW S4, I'm guessing if you mentioned it that it'd be OK. BTW, I thought that Eclipse is no longer being developed for the S4... just older versions made for earlier versions of the Android OS.... via updates fm Eclipse's author...:laugh:
Also, do you know any issues related to Hyperdrive for NC5? I'd given up on updating b/c I heard about wifi issues & I must have wifi....
Also, can you go directly fm a soft-bricked MI1 to NC5 just thru Odin, or are there intermediate steps. I ask b/c I've seen postings in my email box w/forum updates - even if I haven't been involved in the forums... & someone posted a non-data-wiping image to go to NC5, but you had to be on M2 first....
Another point- I saw in a referred thread that being stuck on the Sammy logo means data corruption & it seems that I'd need a ready-for-Odin wiping image; do you have anything on that?
Anyway, thanks for the search tips, I haven't been good at internet searching, I guess that I will have those skills improved also...
Thanks again for the non-Richard help, Raymond- Oldwolf
oldwolf613 said:
Raymond, er, um, uh?!
Sorry about calling you that other name.... guess I was distracted... you know, w/my S4 sitting corrupted on the table & all.... & it looks like I gotta get more sleep.....
I noted in the thread you mentioned SafeStrap 3.75 & Towel Root, & a SS-compatible Google Play Edition Rom.... mine is a retail VZW S4, I'm guessing if you mentioned it that it'd be OK. BTW, I thought that Eclipse is no longer being developed for the S4... just older versions made for earlier versions of the Android OS.... via updates fm Eclipse's author...:laugh:
Also, do you know any issues related to Hyperdrive for NC5? I'd given up on updating b/c I heard about wifi issues & I must have wifi....
Also, can you go directly fm a soft-bricked MI1 to NC5 just thru Odin, or are there intermediate steps. I ask b/c I've seen postings in my email box w/forum updates - even if I haven't been involved in the forums... & someone posted a non-data-wiping image to go to NC5, but you had to be on M2 first....
Another point- I saw in a referred thread that being stuck on the Sammy logo means data corruption & it seems that I'd need a ready-for-Odin wiping image; do you have anything on that?
Anyway, thanks for the search tips, I haven't been good at internet searching, I guess that I will have those skills improved also...
Thanks again for the non-Richard help, Raymond- Oldwolf
Click to expand...
Click to collapse
Don't sweat the Richard thing! Haha, I'm just fooling around. But I still don't know where you got Richard from.
~Eclipse works very well for nc5 even though the last update was in June. Its still a perfectly good rom.
~If you set up everything correctly, Hyperdrive will work fine for you. No bugs for me.
~As long you can get to download mode, you're set for odin. You can always odin to a official new version, just not a older one.
Raymond, I'm on my old Razr = small scrn; but I'll be sure to give you official forum props for all of your help when I get back to my PC.
I do like HyperDrive, but once upon time I saw that some of the versions in earlier teens had probs w/wifi & that's crucial to me… I also missed screen rotation since HD 10.2 for viewing pix & reading text/books but it was stable… & I have to admit I was a little worried
about having to go back & forth recovering fm Sammy hacking errors as its still new to me… if I were rich I wouldn't care, but I have to update my PC as well as other expenses, so spending a lot on phones is not on my horizon.
I suppose your help will crank things up a notch for me, there's nothing like experience w/a more experienced person pointing you in the right direction.
Which version are of HD are you on?
Which version of safestrap is needed for NC5? If I can find an official image to flash, I may want to go directly there, but I vlso heard that newer OTAs fm Sammy are harder if not impossible to root & I like root too!
BTW, your demeanor & willingness to help twigged me to the fact that you weren't all that upset at the slip w/your name, & I actually got a laugh out of how you reacted.
All the best, Oldwolf
Raymond,
Great news! Success on the first try.... I did have some minor blips, but all seems to be working. I tested first via wifi & then contacted VZW to re-attach my service back to my S4 & so far so good.
BTW, since I had a nand backup of MI1, I just restored that version via Odin b/c I wasn't sure if a nand made on an older version of the Android OS would work on a newer version of the OS & I needed to be back up & running quickly.
Of course, if using a nand backup made on MI1 can be restored to a device running NC5... I now feel comfortable about going ahead based on this experience you helped me to gain & I would just Odin NC5 & restore fm my old MI1-based nand b/u set -
I also anticipate that there might be a problem if the nand backup was made on SafeStrap 3.65 & one wanted to restore it on a device running SS 3.75....
One of the blips was that after running the tar.md5 for DeLaVega root, the last 2 items of that driver installation failed; but root worked & so far so good.
I am very excited to be back on the S4, & you can know that much more than the forum thanks I put on your post here, I am appreciative.
All the best, Oldwolf
DEPRECATED
This firmware is old and deprecated.
See the below link for new firmware and a better root method.
https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
You can just flash the BL_ tarball if you don't want to install a new system
but want the better screen and modem drivers.
PART 2: FIRMWARE RELOADED
I have done extensive research into the issues reported by those of you who are still experiencing screen issues.
I was unable to reproduce the screen issue on my then-current firmware with this update.
Not being content to leave people with buggy screens, I learned as much as I could about the s8 firmware.
This is what I did with that information.
Flashable Custom Firmware Package For ALL SM-G950U/U1 ON US CARRIERS
If you have a non-us G950U and want to install this pm me or ask in the thread and ill make one. Its very simple but I wanted to get this out to everyone else ASAP
NOTICE!
This an UPDATE (and More) to the Green/Garbled Screen Issue firmware.
There is NEW firmware to download below, and everyone who is rooted should read on, even if you installed the previous version.
Background
At the core of the issue with the garbled screen, modem panics, and sd card issues are two central themes: Bugs, and Incompatibilities. The S8 family of phones was fraught with issues early in its release, including the infamous "Red Tint', Fingerprint scanner malfunctions, mysteriously poor battery life, and surely a bunch of smaller others. Many of these bugs were caused by issues in the device's underlying firmware. Like most devices, Samsung has worked to fix these bugs and improve device performance throughout the phones lifetime for sale in public.
Root Bugs
The problem was unfortunately worse for users of one of the rooting methods for the S8. The biggest reason for this is that in order to relax security constraints enough to make rooting possible, a "non-user oriented", "factory" combination firmware was used. This firmware, being designed apparently for configuration/repair processes inside a factory, was not tuned to the normal level as the public firmware, likely did not go through the same testing, and ultimately any bugs unique to this "Combination" firmware that did not directly affect basic functionality or also stock were probably largely initially ignored.
This is where most of the issues that you all have had come from.
Finding a Solution
As I was unable to reproduce the issue on my device without resorting to the original firmware shipped out with the root method I used, I decided to think about what made my device different than the other devices reporting these issues. While sure we may have slightly varying hardware and that may contribute to these issues as well. What I am absolutely certain of is that most of us have different releases of software from each other. Not only have people essentially ad-hoc upgraded from the original firmware they rooted with until now, many have not upgraded at all or, only partially upgraded (such as with the pervious version of this).
While I could have simply packaged up my firmware/bootloader flashfire backup, I decided to take it a step further.
THE GOODS
Without further ado, I present to you:
S8Root Improved: A SM-G950U1 Custom Firmware Package for Root Users
This package contains a custom mix of the latest AQH3 STOCK (not combination) firmware used wherever possible with the Necessary boot/kernel images from the combination firmware necessary to keep root working with permissive SELinux. It contains all of the improvements from the previous version, and many more.
RESULTS
I can only speak for myself, but the results I experienced were amazing:
- Better UI Responsiveness.
Things surprise me how they move
- Sharper/brighter screen colors
I thought it couldn't get better than the last version but it has! Everything just looks crisper and are super bright without being oversaturated like with the Adaptie Mode.
- POSSIBLY Improved LTE network connectivity.
Note I said POSSIBLY. I personally regularly experienced 8-10Mb/s download bumps and 2-3Mb/s upload bumps in LTE while moving back and forth from this new firmware. I have my LTE radio locked to a specific channel (there are two i pick up at my place and one is terrible) and I carefully measured -107 to -112 dBm RSRP and -13 to -14 dB RSRQ prior to each measurement. I almost left this out but I figured it would be better to give you the information with no conclusion either way. It ABSOLUTELY could be Atmospheric changes, Traffic level changes, or any other of a million thins. YMMV
- Could POTENTIALLY still any remaining fix long-standing SDCard issues
I did not experience this, but had a few reports from users that did. The same pieces used in that version that would touch SDcard usage are used here, so that fix/improvement will carry over.
DISCLAIMER
Unfortunately proving beyond any shadow of a doubt that this package fixes the issue was impossible . I have TRIED AND TRIED AND TRIED to trigger the screen issues, including tweaking on and off every setting (auto brightness, multiple DPIs, different graphs modes, etc) I could get my hands on and it just was not happening. I used every software/systems trick I could think of to break this again, and I was completely unable to tickle the bug on this firmware, despite being able to reliably trigger it almost on command using my previous firmware.
The only thing left to do is either:
- Get the source from samsung, fix the bug myself, and get them to sign my new kernel image with their key so our locked bootloaders would allow it (HAHA I DOUBT IT)
- Acquire a large fleet of S8s (and S8+s) to run distributed integration testing (like the kind Android use at Google). Well if someone wants to buy me a few dozen s8s and s8+s (each) sure I'll take a month off work and squash this, but otherwise not gonna happen either.
If it STILL happens for you, I'm sorry.
I have done everything I can think of, and if it happens to you and you have suggestions, I'm all ears.
BUT HEY, but this is XDA right? Land of mods like Xposed which will brick one persons device and work flawlessly on the identical one next to it. And we love Xposed don't we?
Despite absolutely hilarious comments to the contrary, this package absolutely meets the (aka "BugFix") as well as just about any android update ever does, given the wide variety of environments, usecases and software configurations out there. I surely hope that this works for you.
Instructions
1) Download the package from the link above.
- Here it is Again for good measure.
2) Reboot into download mode and flash using Comsy Odin
Thats it! I packaged this in a way to make the process as smooth as possible.
There is NO reinstall, NO wipe of any kind, nor ANY further work on your part needed to install and use this.
The file size is small so the download is fast, and again, there is NO WIPE or config change needed.
if (for some inexplicable reason) you want to roll back, or go to 100% stock sans root, that process should not be made any more difficult as well.
Legacy Information
If you were here before and either looked at or downloaded the previous version, AND YOU HAVE NO QUESTIONS you can skip this part.
If you have questions, please read through to the end of the post before asking them, as I tried to answer as many as I could before hand and all of this information still applies.
WHAT IT IS NOT:
I wanted to outline a few things it is NOT about, to make a valliant effort to stem off the flow of questions before they begin (ha!):
NOT: A new Stock ROM for Your Phone
THIS IS NOT A FULL OS BUILD! DO NOT DOWNLOAD THE WHOLE THING AND FLASH IT EXPECTING AN ENTIRELY UPGRADED OS.
There is no full stock AQI1 image I have found. Believe me I looked a bunch of places after I found it
NOT: Oreo Early Preview
Given the predictions that the next release from Samsung would likely be Oreo, there was some initial over excitement. This wound up being NOT the case and if you read at least current Samsung Oreo projections they are predicting AQB now.
NOT: A Fix for the 80% Battery Issue
I know this is completely futile to hope for but:
THIS DOES NOT FIX THE 80% BATTERY ISSUE!!!!
NO WE DO NOT HAVE A FIX FOR THAT OR ONE COMING ANY TIME SOON!
YES SOME PEOPLE ARE STILL TRYING!
PLEASE DO NOT ASK! OFF TOPIC FOR THS THREAD
NOT: Currently Tested by ANYONE but ME
Since the moment I installed this I have not had ONE SINGLE screen issue, where previously I would have them several times throughout the day (at least 3 sometimes upwards of 6). For the case of ME and MY device, I am confident in declaring that this boot ROM does not have the same kernel bug that was causing the issue on the boot.img provided as part of your traditional root method.
NOTE: This is for the s8 G950 US Snapdragon models ONLY! Do NOT Flash this on your exynos, your Chinese/HK S8, your N8, your MOTO RAZR flip phone, whatever else you have. Kernels/boot.img files are very device specific and you will surely break it if not completely brick it.
DISCLAIMER:
YOUR WARRANTY IS ALREADY VOID if you are paying attention and are doing this to fix bugs with the existing sampwnd root.
HOWEVER IT IS EVEN VOIDER NOW. FLASH THUS TO YOUR DEVICE AT YOUR OWN RISK!
and if you break it I AM NOT RESPONSIBLE! FLASH AT YOUR OWN RISK!
As I said I have not tested this anywhere but my phone as I dont have any other s8s nor do I have access to any locally. I hope it works for you as well as it has for me.
STEPS
Download Boot Image
Use the URL here to Download the AQI1 boot.img file: Go Download the New Hotness
Prepare Phone for Flashing in FlashFire
If you did not download it on your phone, copy it somewhere FlashFire can see it.
Flash it
Open up FlashFire
Hit the "+" button
Select the "Flash Firmware Package" option, NOT the "Flash Zip or OTA" option!
You should see a popup window thing that has a checkbox next to the word BOOT, with "boot.img, 22MiB" underneath.
Make sure the checkbox is checked.
Make sure that it says BOOT above boot.img.
I have no idea if its possible for this to get messed up, but BOOT implies flashing the BOOT partition so if it says something else you are headed towards brick town, abort immediately.
Press the Check mark at the top right corner once you have confirmed the two things above.
MAKE SURE EVER ROOT IS DISABLED!!!
Click on the "Reboot" box, and choose "Recovery". MAKE SURE PRESERVE RECOVERY IS NOT CHECKED!
Back at the main menu, click the lightening bolt next to the word FLASH. Confirm.
Wait for FlashFire to do its thing. Sometimes it takes a minute for FF to wake up and start flashing. Occasionally for me it never happens, if this happens DO NOT PANIC ITS FINE. Hold down power+volDown until you eventually wind up in upload mode, then just reboot normally and everything will come back fine.
When FlashFire finishes (it will go really fast, the image is only 22MB we arent flashing a 5GB system here), it will auto-reboot your device into the recovery men
Select Wipe Cache and Confirm
This will wipe cache which is fine and safe. Again maybe not needed, feel free to skip if you know what you are doing. If you mess up and accidentally click factory reset instead, please tell me so I can laugh at you.
Reboot into a Clear New World
Select reboot and boot the system normally. If you formatted the cache partition above, it will take a little longer to start your phone. This is just the first time per normal.
Thats it! Welcome to the world of clear screens and bright colors. It could be a total placebo effect but I actually think this kernel drives the display better sometimes.
Please let me know what you think, and if this works for you. I wi;; be here for a while to answer questions or fix anything i typoed above or whatever.
FYI: A s8+ thread is coming too, as I sprung for purchasing both downloads to be an equal opportunity XDAer (at least with US flagship Samsung devices lol) but since I have an s8 and thus had the files locally already I made this one first
@jhofseth for nerding out with me the last few nights on trying crazy **** to get a bootloader unlock which prompted me to dig at this in the first place
Most of all, all of the tons of you who have made so many aewesome mods, themes, apps, what have you that I use every day and that make me enjoy my device all the more. I could not be happier to have the opportunity to give back a little.
Here is the restof the s8 combo firm if you are interested, but don't just flash this as its not a full OS:
EDIT: DOWNLOAD THE NEW ONE ABOVE
Can I Get The Link To The S8+ Boot im willing to try it
Mark805 said:
Can I Get The Link To The S8+ Boot im willing to try it
Click to expand...
Click to collapse
Coming very soon I promise! 10m max
Ok thanks
Mark805 said:
Can I Get The Link To The S8+ Boot im willing to try it
Click to expand...
Click to collapse
Its up now! https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673815
whats the bootloader verison? it can be found by booting into download mode manually.
Cameron581 said:
whats the bootloader verison? it can be found by booting into download mode manually.
Click to expand...
Click to collapse
This isn't a bootloader change, it's boot.img which is the kernel and root filesystem essentially
Hey, btw this does not void warranty. I understand it's a standard disclaimer but it doesn't void it. It doesn't trip knox, so warranty is still very intact.
mweinbach said:
Hey, btw this does not void warranty. I understand it's a standard disclaimer but it doesn't void it. It doesn't trip knox, so warranty is still very intact.
Click to expand...
Click to collapse
Uh just because their service does not catch you does not mean that technically you are not violating your warranty contract thus making using technically illegal
That would be like saying "it's not murder if you leave no forensics!" Lol
wildermjs8 said:
Uh just because their service does not catch you does not mean that technically you are not violating your warranty contract thus making using technically illegal
That would be like saying "it's not murder if you leave no forensics!" Lol
Click to expand...
Click to collapse
i mean legally a warranty can not be void through software modifications unless it causes physical damage to the device. Since the efuse was not tripped no physical damage has been caused and no warranties have legally been void.
I had the green screen/graphics corruption after flashing this still...
goliath714 said:
I had the green screen/graphics corruption after flashing this still...
Click to expand...
Click to collapse
Apparently this happens to some people. I am fairly certain it is a firmware combination issue but I haven't been able to track it down. One thing you can do to eliminate it if you have the issue still (please let me know if this does not work) is to disable auto brightness.
wildermjs8 said:
Apparently this happens to some people. I am fairly certain it is a firmware combination issue but I haven't been able to track it down. One thing you can do to eliminate it if you have the issue still (please let me know if this does not work) is to disable auto brightness.
Click to expand...
Click to collapse
I have auto brightness off and still get it here and there.
goliath714 said:
I had the green screen/graphics corruption after flashing this still...
Click to expand...
Click to collapse
Please check out the OP again and download/flash the new version. Rather than just a few files, its a whole new entire bootloader/kernel package that I assembled piece by piece to have as much latest stock firmware as possible while maintaining what we need for root.
My primary suspect for why some people experience this regression is having older parts of their system. Rather than push everyone to upgrade, I made a painless upgrade process for all of their firmware instead
This includes the Radio drivers and bootloaders, kernels and flash layer libraries. Its all either latest stock or its AQI1 Combination because it was absolutely necessary.
wildermjs8 said:
Please check out the OP again and download/flash the new version. Rather than just a few files, its a whole new entire bootloader/kernel package that I assembled piece by piece to have as much latest stock firmware as possible while maintaining what we need for root.
My primary suspect for why some people experience this regression is having older parts of their system. Rather than push everyone to upgrade, I made a painless upgrade process for all of their firmware instead
This includes the Radio drivers and bootloaders, kernels and flash layer libraries. Its all either latest stock or its AQI1 Combination because it was absolutely necessary.
Click to expand...
Click to collapse
We flash the tar in the AP slot correct?
CloudyxVision13 said:
We flash the tar in the AP slot correct?
Click to expand...
Click to collapse
Yep
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Seems to be running better to me. Thanks bro
CloudyxVision13 said:
We flash the tar in the AP slot correct?
Click to expand...
Click to collapse
It actually does not matter, as Odin will do the right thing no matter what.
Sorry I should have made that clear. I will update the op to make that clear
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
AngelIsL33T said:
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
Click to expand...
Click to collapse
Nope, only need the tar file bud. The old boot.img file is just basically the previous version of this.
AngelIsL33T said:
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
Click to expand...
Click to collapse
The old image is actually part of the new tar, do you will have it anyway . I packaged it in Odin this time because there are some pieces of firmware FF either can't or warns against using it for. Plus one clean simple tar seemed easier, no?
Do you see the boot.img in the op? I thought I nixed all the instances of the link but I may have missed one.
I almost rewrote all the old text to reflect now but it felt like editing history so I tried to preserve what made the most sense still. It sounds like it's still a little confusing sobrskr another crack at it shortly.
Please let me know if you have any trouble! I'll be here to help all evening