There's probably other threads on this somewhere, but how do you root a N3 with 4.4.4, from what I gather the newest updated fixed TowelRoot's crash exploit. Also can someone explain exactly the difference between voiding the warranty and the Knox Counter?
Thanks!
TheNewGuy14 said:
There's probably other threads on this somewhere, but how do you root a N3 with 4.4.4, from what I gather the newest updated fixed TowelRoot's crash exploit. Also can someone explain exactly the difference between voiding the warranty and the Knox Counter?
Thanks!
Click to expand...
Click to collapse
The sure-fire way of rooting is by using this method. That being said, this will trip your KNOX Counter.
Now, onto Voiding Warranty vs. Tripping KNOX Counter.
Official Samsung Warranty. This document is obviously written in a legalese manner. I am not a lawyer, but have read through the warranty very carefully and feel like I have a grasp on what it covers/doesn't cover.
In my opinion, the most critical part of the warranty (as it applies to our conversation) is the following:
This Limited Warranty does not cover: ...
(g) defects or damage resulting from improper testing, operation, maintenance, installation, service, or adjustment not furnished or approved by SAMSUNG, including but not limited to installation of unauthorized software and unauthorized root access, both of which shall void this limited warranty
Click to expand...
Click to collapse
This clearly states that rooting the phone will void your warranty. Please note that this is regardless of whether KNOX is tripped. Using Towelroot (on previous versions) to gain root access technically would void your warranty just as much as using other methods. The issue is whether Samsung knows about it. That's where KNOX comes in.
KNOX is primarily Samsungs way of knowing if you've modified the software on the phone (root access or some other tampering). At startup, KNOX checks for custom low-level operating system components (bootloader, recovery, kernal, etc.). If any of these are custom, it'll trip KNOX. TowelRoot had exploited a way to obtain root access without modifying any of those items, but as you mentioned, it no longer works in 4.4.4. As far as I'm aware, all other rooting methods include using ODIN to briefly modify one of the low-level operating system components, which invariably trips KNOX.
Now, back to the main point of your questions: will voiding the warranty (by obtaining root access) screw me over? The answer is: probably not. Samsung has been known to not really care about KNOX being tripped when servicing phones. This especially is true in cases where you are claiming someone not software related. From a common-sense perspective, having root access would in no way affect the performance of the power button, so if you're claiming issues with the power button, having a tripped KNOX shouldn't affect your claim status. Although, legally, they have covered this by saying the warranty is completely voided by having root access (not just the software part of the warranty).
I would recommend, however, that before sending any phone in, that you use ODIN to revert back to the stock android. KNOX will still be tripped, but it won't technically have root access anymore.
I hope this answers your questions.
-Topher
topherk said:
The sure-fire way of rooting is by using this method. That being said, this will trip your KNOX Counter.
Now, onto Voiding Warranty vs. Tripping KNOX Counter.
Official Samsung Warranty. This document is obviously written in a legalese manner. I am not a lawyer, but have read through the warranty very carefully and feel like I have a grasp on what it covers/doesn't cover.
In my opinion, the most critical part of the warranty (as it applies to our conversation) is the following:
This clearly states that rooting the phone will void your warranty. Please note that this is regardless of whether KNOX is tripped. Using Towelroot (on previous versions) to gain root access technically would void your warranty just as much as using other methods. The issue is whether Samsung knows about it. That's where KNOX comes in.
KNOX is primarily Samsungs way of knowing if you've modified the software on the phone (root access or some other tampering). At startup, KNOX checks for custom low-level operating system components (bootloader, recovery, kernal, etc.). If any of these are custom, it'll trip KNOX. TowelRoot had exploited a way to obtain root access without modifying any of those items, but as you mentioned, it no longer works in 4.4.4. As far as I'm aware, all other rooting methods include using ODIN to briefly modify one of the low-level operating system components, which invariably trips KNOX.
Now, back to the main point of your questions: will voiding the warranty (by obtaining root access) screw me over? The answer is: probably not. Samsung has been known to not really care about KNOX being tripped when servicing phones. This especially is true in cases where you are claiming someone not software related. From a common-sense perspective, having root access would in no way affect the performance of the power button, so if you're claiming issues with the power button, having a tripped KNOX shouldn't affect your claim status. Although, legally, they have covered this by saying the warranty is completely voided by having root access (not just the software part of the warranty).
I would recommend, however, that before sending any phone in, that you use ODIN to revert back to the stock android. KNOX will still be tripped, but it won't technically have root access anymore.
I hope this answers your questions.
-Topher
Click to expand...
Click to collapse
Thank you! It does, so essentially rooting period will void the warranty (as seen in the legal jargon) whether you trip the counter or not, and you can always restore it to stock if you need to turn it back in. I was wondering the same thing, we took my gf's S4 in yesterday, and all they did was run a Sprint diagnostic and then replace the hardware, not sure if they even checked to see what she was running (although it is stock).
Any other threads you recommend, I'm still fairly new to it, been reading up on it since I had the Transformer that wouldn't update to Froyo ha, but back then there was too much coding involved, I didn't want a bricked phone because I forgot a "/" in the code somewhere. Almost everyone I know uses Cyanogenmod, also what's the deal with Titanium Backup and Safestrap?
TheNewGuy14 said:
Any other threads you recommend, I'm still fairly new to it, been reading up on it since I had the Transformer that wouldn't update to Froyo ha, but back then there was too much coding involved, I didn't want a bricked phone because I forgot a "/" in the code somewhere. Almost everyone I know uses Cyanogenmod, also what's the deal with Titanium Backup and Safestrap?
Click to expand...
Click to collapse
Thankfully, it's not nearly as easy to brick a Note 3 (at least compared to the S3... man it was tough helping people with that phone, so many bricks!).
It's considered bad form to link specific ROMs in a Q&A thread, since each ROM is catered to a different demographic (and some people might get in a huff if you neglect their favorite ROM). What I will do, however, is let you know the steps I've taken whenever I root and install a new ROM.
I'll explain how to install a custom ROM and some common things to think about/check prior to installing anything:
Installing a Custom ROM
Step 1 - Gather Information
First off, you need to know what version of Android your phone currently is running. This is easily done by looking in the Settings Menu -> General -> About Device.
The Main things we are looking at on this screen are Software Version, Model Number, Android Version, and Baseband Version. I'll explain these (to the best of my knowledge) below:
Software Version:
This is the "type" of Android that you're running. Rather than quoting the entire name, we typically only refer to the last 3 characters (MJ4, NAB, NC5, etc.). Stock Note 3 devices will (most-likely) be running one of 3 different versions of TouchWiz (TW):
MJ4 - This is the last Jellybean version of TW for the Sprint Note 3NAB - This is the first KitKat TW version for the Sprint Note 3NC5 - This is the second KitKat TW version for the Sprint Note 3NH7 - This is the latest KitKat TW version for the Sprint Note 3
The reason that we are concerned with the Software Version is that between the MJ4 and NAB versions, there were major changes. So if you're running MJ4, you will have to do additional steps before flashing a custom ROM based on a newer version. And if you're on NAB or NC5, you will not be able to go back to MJ4, so beware what you're flashing.
For the most part, if you're on NH7, you can flash either a NH7 or NC5 custom ROM, but just read the ROM's FAQ to see if there are any issues with doing so.
Model Number:
Most people don't worry about this, but I always do when looking at a new ROM. The Sprint Note 3 is different from the Verizon Note 3, which is also different from the International Note 3. It's always best to double-check that the ROM you're trying to install is truly meant for your device. This simple check will prevent a LOT of potential issues you'll get when installing a ROM.
Android Version:
This is just an additional check to the Software Version. Always best to know.
Baseband Version:
The Baseband is, unless I'm mistaken, the "kernal" for the phone's cellular and 4G radios. Sometimes upgrading (or downgrading) the Baseband can help with signal strength and reception. Some users have noted that they got better reception on older Baseband versions. I haven't personally looked into it and the reports from other users seem somewhat anecdotal, but it's good to know which Baseband you're on.
The Baseband is independent from the ROM version, so you can run an older Baseband (MJ4 or NAB) on a newer ROM (NC5), and vice-versa.
The last bit of information you need to know is the Bootloader Version. The way to find this information is to reboot your device. When you see the text on the screen, you should look for the Bootloader Version. It'll be a long string of characters, but you're only looking for the last 3 (MJ4, NAB, or NC5).
Once you have all the above information, you should be ready to start the fun process of preparing your phone to flash your first ROM.
Step 2 - Backup your Media
First thing: Backup all of your media to your computer. If there's pictures/music/videos/recordings you don't want to lose, back them up. It's just good practice. Don't lose all your cat pictures because you flashed something and it somehow erased your internal storage. I tend to keep everything of importance on the External Storage, but there are times where even external storage can be wiped, so it's best to back up everything to a PC.
Step 3 - Upgrade your Phone to the latest Stock ROM (NH7)
This only is a MUST applies if you're running an older version and want to install a NH7 ROM. Most continually-developed ROMs are either NC5 or NH7 now, so the first things first: Update your phone to NH7.
Go over to micmar's thread and download the One-Click File. It will remove Root, but don't worry, because when you install a new ROM, it will automatically include root access.
Follow the instructions in his thread and your phone will now be fully upgraded.
At this point, your "About Device" should show the following:
Software Version: N900PVPUCNH7
Android Version: 4.4.4
Baseband Version: N900PVPUCNH7
Reboot your phone and let it sit for a minute so it can get it's bearings.
Step 4 - Install a Custom Recovery
So far, we've been flashing everything in ODIN. Now, we're going to use ODIN one last time to flash a custom recovery, so that you can flash custom ROMs without the need of a computer.
The most-commonly used Custom Recovery is TWRP (XDA Link). You'll want to use the latest version, 2.8.0.
Flash this in ODIN. You should use the "PDA" or the "AP" Slot.
Reboot your phone to make sure it works correctly.
Step 5 - Make a Nandroid Backup of your device
If you don't know what a Nandroid backup is, don't worry. It's basically just taking your phone as is and making a backup of it. In case you make a mistake or flash a bad download of a ROM, this allows you to restore your system. I always keep my backups on the External Storage (microSD Card), so in case I have to wipe my internal storage, it's not a big deal. You can also copy the files over to your PC, just to be more paranoind about your nandroid backups (rhyming is fun!).
You do this by restarting into Recovery (power down device, hold down home button and volume up while powering on phone).
Once in TWRP, go to "backup." Make sure the storage selected is "external storage." This screen will have various options of what to backup. I typically choose everything except external storage. Typically, backups range from 1-2 Gigs.
For me, backups typically take 5-10 minutes to do. In my opinion, this is totally worth it, since I can always restore a backup with no issues.
Step 6 - Install a Custom ROM
Once you choose your custom ROM from the Development Section, follow the instructions on the original post to install it. I'll give a general outline of what I do whenever installing a new ROM, but sometimes a custom ROM will have specific instructions, so you want to make sure to read the posts carefully.
Generic Instructions for Installing a ROM:
Download ROM and check the md5
Internet being spotty in my area, I always check the md5 to make sure that the file downloaded correctly. You can check the md5 using this windows program or using a file explorer on your phone like ES File Explorer. I always copy the ROM zip file to my external SDcard.
Reboot to Recovery
Wipe Data, System, Cache, and Dalvik Cache
This is called a "Clean Wipe," meaning it will wipe out your installed Apps and the data associated with them. Some people will claim that "Dirty Flashing" (i.e. not wiping the above) is OK, but I've seen too many apps Force Closing (FC-ing) when dirty flashing. Also, if you dirty-flash and encounter an issue with a ROM, the first piece of advice is to do a clean install. Might as well do that initially and hopefully not run into any issues.
Install the Custom ROM
Pretty straight-forward on how to do this... just click "Install" and then browse to the place your copied the ROM zip file.
Reboot your phone and run through the typical initial start-up information (google account, etc).
Once you get your phone set up the way you like (apps, accounts, wifi passwords, etc), I'd make another Nandroid backup, just so you have one where it's setup with everything you need. This will make any issues less painful, since you'd restore a backup that's already setup.
Step 7 - Further Considerations
If you ever want to try a new ROM, all you have to do is repeat step 6. Beware, though, people easily become flashaholics when they first figure this stuff out.
If you were paying attention to my "Generic Instructions" when installing a ROM, you'd notice that every time you do a Clean Install of a ROM, you lose all your apps... All of your Angry Birds 3-Star levels are gone!
Well, there are ways to get prevent losing that data... One is by "Dirty Flashing" (Not wiping the "system" or "data" partitions before flashing a ROM in TWRP). This is common practice among users here on XDA, but is typically frowned upon by ROM devs. I've noticed that a good number of issues on ROM threads stem from people Dirty Flashing. It typically causes more problems than it solves.
The other way of backup up and restoring app data (prior to wiping) is by using Titanium Backup. I could write up a long post on how to use Titanium Backup (TiBu), but the main things to remember are the following:
White line items are fine to be restored (both Data and Apps).
Restoring Yellow line items is typically OK (Data only).
Restoring system apps or data (red line items in TiBu) is typically a bad idea.
I've been using TiBu for the past 2-3 years and it's typically worked like a charm. Sometimes, when there's a major Android Update (like from JellyBean to KitKat), it can become broken, but the Developer is really responsive and gets it to work within a few weeks. If you upgrade to PRO, you can schedule automatic app backups (I backup all my user apps every night at 3am). You can also restore apps/data from Nandroid Backups (which is great if you do a Nandroid backup but had forgotten to update your TiBu backups).
In Summary
Whew, that was a lot to write... I'm a Structural Engineer, not a Software Engineer, so I don't know the technical side of things like bootloaders or basebands, but hopefully none of the information I provided was false.
Anyways, let me know if you have any problems with the install. I appreciate any feedback!
Topherk,
Thanks for the reply, and sorry about the bad Juju for mentioning a specific ROM. In other news, I am probably going to re-read your article step by step, and it really puts things in perspective. I have that same build, and I also have Sprint like the video, which I didn't know that the carrier made such a big difference. I'm glad I asked before I started! I will keep you updated on what I decide to do, appreciate the help!
TheNewGuy14
:good:
*new question*
I don't remember where I read this, and I found the option on my phone. If I uninstall KNOX will that eliminate the counter, and other minor issues with KNOX?
TheNewGuy14 said:
I don't remember where I read this, and I found the option on my phone. If I uninstall KNOX will that eliminate the counter, and other minor issues with KNOX?
Click to expand...
Click to collapse
No worries about the mention of CyanogenMod (I myself am running a ROM based off of it)... I was talking from the perspective of someone giving advice. If I give you advice towards a specific ROM or two (or even a list of ROMs), it could be considered a slight towards the excluded ones.
As far as I'm aware, there are two aspects of KNOX: The low-level trigger and the system app. The low-level trigger works like I described in my previous post. I honestly don't know how the system app works, but I believe it only affects Enterprise users whose corporations require secure phones (and have their own systems in place which interact with KNOX). I beleive it was Samsung's way of trying to secure some of Blackberry's business-class users. I may be way off on this, but that's what I understand about KNOX.
Cheers!
-Topher
I think you're right they want to maintain they are the most secure phone.
Check out their official statement for Towelroot, although I can't post the link because I'm still a n00b quick Google search will bring it up though.
Sent from my SM-N900P using XDA Free mobile app
TheNewGuy14 said:
There's probably other threads on this somewhere, but how do you root a N3 with 4.4.4, from what I gather the newest updated fixed TowelRoot's crash exploit. Also can someone explain exactly the difference between voiding the warranty and the Knox Counter?
Thanks!
Click to expand...
Click to collapse
Yes, if you root 4.4.4 NH7 at this time with the available rooting formats, you will trip Samsung's KNOX Counter, and void the device's warranty with Samsung. So, are you going to send the device directly back to Samsung ? No, you are going to take it to a sprint service center, or ship it in to sprint. Sprint handles the warranty ? KNOX is a program that creates secure encrypted containerization of DATA so it can be sent to another location. Check this out http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
TheNewGuy14 said:
There's probably other threads on this somewhere, but how do you root a N3 with 4.4.4, from what I gather the newest updated fixed TowelRoot's crash exploit. Also can someone explain exactly the difference between voiding the warranty and the Knox Counter?
Thanks!
Click to expand...
Click to collapse
Hey OP, I have rooted my N3 using CF-Auto Root on NH7 without any problems.
It should be a walk in the park, and yes you will trip knox, but It's all good.
Now proceed with your rooting
Related
I have solved this problem I think last night by updating to XXEMB1 on Kies last night - I have of course lost root for the moment but will get back to that later when I have more time
I have an international galaxy gt19300
It had begun to restart itself a few times a day and then would run for days with no issues
I eventually decided to root it when I found the new toolkit on here which seemed to work a treat
I now had superuser installaed titanium back up and ROM Toolboxand paid for pro versions of this and toolkit
to be honest apart from doing one back up using the toolkit the only other thing I did was to disable the auto scanning on start up to speed up booting the phone. A day or two after this the problems started again but this time with it no rebooting but just freezing. Eventually I took out the sd card as I remembered I had an sd card problem with my old S2 - though this is a new samsung sd card. At first I thought that was it but then a bit later it froze while i was browsing the app store and has done so periodically, though today it ran all day without freezing onvce. Then suddenly it froze again for no reason - I was just swithcing screens and it froze part way through the process
As far as I can see I have three options
1) Flash a new ROM (for the moment I am still using the stock rom having only just rooted it using Toolkit.exe from here) but not sure which one I should use so need reccommendations
2) Use the toolkit to download a stock odin flashable rom (but dont I have this already?) and then 3 reset the flash counter using triangle away (seems risky to me) install the stock rom , undo root (if necessary) and then return the phone to Samsung
3) go to Kies and install the latest update in the hope that the problem will go away - though if S User pro doesnt manage to keep root I wiill presumably have to re-root all over again.
What attracted me to S3 Toolkit was that it packaged up all sorts of options into one easy package - on the other hand this may have made me a little over confident with rooting. If I hadnt rooted it the earlier problem, though not as bad, would still have been there but I could easily have sent it back to Amazon UK or Samsung UK for repair and replacement.
My biggest worry at the moment is that whichever process I go for - or even a third option suggested here - there must be a risk that the phone might lock up during flashing or upgrade - probably not likely as it didnt when I restored the back up I had done (didnt help either) and the touch wiz ui wont be running
Anyway would really appreciate some help guys - even if it is only what you would do in the same circumstances. I guess I should have tried to have the problem fixed but earlier I put that down to maybe having too many apps and crapware and thougth rooting would help me solve it. I have unintstalled every app that I dont regularly use but it is still happening
gbswales said:
...
Click to expand...
Click to collapse
First of all you have to be aware of the fact that rooting & flashing ROMs is always a risk, toolkit or not.
The safest way is to stay un-rooted stock if you do not know why you need root in the first place. If you know you need root, and actually also before, read the guides & information in the stickies under the General section as they explain you in detail how to root, un-root, use triangle away etc.
As for your situation, I would try to 1) flash another kernel than the stock one, if this does not work, 2) flash the most up-to-date stock ROM (you can get it here on XDA or sammobile.com) via Odin or Mobile Odin, not the toolkit (Odin is as simple as the toolkit if you follow the how-to), if this also does not work 3) try a custom rom, and if it also does not work 4) return back to stock and give it to Samsung service centre.
I wish you good luck!
Thanks for your advice
chrismast said:
First of all you have to be aware of the fact that rooting & flashing ROMs is always a risk, toolkit or not.
The safest way is to stay un-rooted stock if you do not know why you need root in the first place. If you know you need root, and actually also before, read the guides & information in the stickies under the General section as they explain you in detail how to root, un-root, use triangle away etc.
As for your situation, I would try to 1) flash another kernel than the stock one, if this does not work, 2) flash the most up-to-date stock ROM (you can get it here on XDA or sammobile.com) via Odin or Mobile Odin, not the toolkit (Odin is as simple as the toolkit if you follow the how-to), if this also does not work 3) try a custom rom, and if it also does not work 4) return back to stock and give it to Samsung service centre.
I wish you good luck!
Click to expand...
Click to collapse
Firstly the good news is that it turned out to be a problem with the last XXELLA upgrade - I found a new one on KIES ran the update and it is fine
Of course I lost root access but expected that anyway.
I do enjoy tinkering with Systems and although I know my way around Windows I have not tried with Android until now - this is my second Galaxy so was naturally wary of bricking it if I rooted. Christmas time I bought myself a galaxy tab 2 10.1 with the express aim of rooting it and was prepared to take the risk - after a few false starts I got it rooted fine - was still wary of the phone but once the kit came out the benefit that has for me is the way you have to check things step by step systematically as you do things - my problem with doing stuff from instructions on line is that I find it is all to easy to skip a step (which I did with the tab first time around) Also with it being a system I haven't explored before I like having a step by step approach which is the same way that I learned DOS way back in time.
I do want to try some different ROMs on it to see what they offer and I would really have liked to have got some apps running from my external SD card and I also like having a complete image back up (as I have for Windows 8) so that in the event of a serious issue it is easy to wipe all and restore from new (I keep several images which I make on a weekly basis so that I don't have to re-install everything.
I confess to playing with computers and devices as a hobby - evidence of this was the 350 apps I had installed before I started purging them in case that was the cause of the problem. I pretty nearly try every new app I find just to see what it does and so there being a whole range of apps that I couldn't install without root access upset me. I am not going to rush to root again and will at least wait until the current version has been on the phone a while - just to make sure the XXEMB1 version is stable now - it has a lot of new admin features to keep me amused for a while!
Two things that disappointed me about root were that it looked as if I couldn't overclock the device to improve speed - the main CPU bar was already on max (though I didn't have time to explore more than that) and that it still seemed pretty hard , if possible at all on the hardware, to run apps from the external SD card -- as I do now with windows (using a smaller SSD ) I will have to be a bit more prudent about uninstalling the apps I find I don't really use.
I guess deep down the main reason why I want root is I don't like any manufacturer telling me what I can and cannot do with the device I paid for - one thing I did try was installing Linux but that didn't quite get finished before I lost root access.
Your advice however is very sound for people who don't like or enjoy tinkering or taking risks and I don't think I would recommend any normal phone user to root their device.
Thanks again
Just to add quickly....to overclock you need to flash a kernel that supports it.....And know what you are doing before doing it
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!
I do not want to brick this device. Could someone give/list me steps that would root it using the 'safest' (aka hardest to mess up), install TWRP, and maybe then install a good ROM (CM13?)
Also, fire os 4.5.5
ADB works.
GameExpertNetwork said:
I do not want to brick this device. Could someone give/list me steps that would root it using the 'safest' (aka hardest to mess up), install TWRP, and maybe then install a good ROM (CM13?)
Also, fire os 4.5.5
ADB works.
Click to expand...
Click to collapse
Starting from 4.5.5 you can not install 'native' twrp or unlock the bootloader. Nor is their any path to allow this due due anti-rollback protections. Your safest path (which still holds risks) is to rollback to 3.2.8, upgrade to 4.5.2, root, install Safestrap v4 followed by one of two kitkat based roms: Nexus v4 or CM11. At present you can not install CM12 (lollipop) or CM13 (marshmallow) under Safestrap v4.
There are many posts detailing the above process; a few recent ones can be found here, here and here. Scroll through the entire thread for other examples along with a diary of user experiences.
Key points:
- be sure to keep wifi off (airplane/flight mode engaged) while passing through 3.2.8 and 4.5.2 until OTA is block. Receiving an update on 3.2.8 will brick your device. The consequences on 4.5.2 are less severe but still unpleasant.
- suggest downloading everything you need to your device in advance; put each component into a separate folder to be extracted/renamed as needed
- read, read and read some more before attempting anything. Ask questions as needed; never guess or assume. Make sure you know the expected outcome, potential consequences and fallback options for each step before executing
- Kindles in general and HDX models in particular are unforgiving relative to other devices. Tough to mod, easy to brick, nearly impossible to recover. If not 100% confident in your abilities enjoy your device as is (or be mentally prepared to toss it in the trash).
Davey126 said:
Starting from 4.5.5 you can not install 'native' twrp or unlock the bootloader. Nor is their any path to allow this due due anti-rollback protections. Your safest path (which still holds risks) is to rollback to 3.2.8, upgrade to 4.5.2, root, install Safestrap v4 followed by one of two kitkat based roms: Nexus v4 or CM11. At present you can not install CM12 (lollipop) or CM13 (marshmallow) under Safestrap v4.
There are many posts detailing the above process; a few recent ones can be found here, here and here. Scroll through the entire thread for other examples along with a diary of user experiences.
Key points:
- be sure to keep wifi off (airplane/flight mode engaged) while passing through 3.2.8 and 4.5.2 until OTA is block. Receiving an update on 3.2.8 will brick your device. The consequences on 4.5.2 are less severe but still unpleasant.
- suggest downloading everything you need to your device in advance; put each component into a separate folder to be extracted/renamed as needed
- read, read and read some more before attempting anything. Ask questions as needed; never guess or assume. Make sure you know the expected outcome, potential consequences and fallback options for each step before executing
- Kindles in general and HDX models in particular are unforgiving relative to other devices. Tough to mod, easy to brick, nearly impossible to recover. If not 100% confident in your abilities enjoy your device as is (or be mentally prepared to toss it in the trash).
Click to expand...
Click to collapse
So, from my assumptions, there are 2 major ways to mess up
1. OTA update.
2. Low battery
And IF I ever do this, I will click the 'forget' button on the wifi network AND set it into airplane mode, and also have it fully charged overnight and STILL plugged in,
What are some other risks that I can try to "eliminate"
GameExpertNetwork said:
So, from my assumptions, there are 2 major ways to mess up
1. OTA update.
2. Low battery
And IF I ever do this, I will click the 'forget' button on the wifi network AND set it into airplane mode, and also have it fully charged overnight and STILL plugged in,
What are some other risks that I can try to "eliminate"
Click to expand...
Click to collapse
There are risks throughout the process - a comprehensive detailing would never be complete. Your best defense is carefully reading instructions, understanding what is suppose to happen at each step (expected outcomes) and avoiding 'gotchas' which are well documented. Most disasters are the result of poor preparation, impatience and experimentation. Like anything else the work is relatively easy with manageable risk if do your homework. Keep reading until comfortable.
Add to your list:
- using files obtained from sources other than listed in the relevant threads (eg: stock 3.2.8 vs rollback file)
- performing a native factory reset (from the stock recovery menu) unless recommended by an experienced contributor
- performing a native factory reset after Safestrap v4 is installed (instant brick)
- activating/using secondary slots in Safestrap v4 and then attempting to swap backup images between slots
- flashing unsupported roms in Safestrap v4 (CM12/CM13, stock FireOS, etc)
- manually twiddling file permissions or messing with build.prop after obtaining root (there's an app for that if needed)
Davey126 said:
There are risks throughout the process - a comprehensive detailing would never be complete. Your best defense is carefully reading instructions, understanding what is suppose to happen at each step (expected outcomes) and avoiding 'gotchas' which are well documented. Most disasters are the result of poor preparation, impatience and experimentation. Like anything else the work is relatively easy with manageable risk if do your homework. Keep reading until comfortable.
Add to your list:
- using files obtained from sources other than listed in the relevant threads (eg: stock 3.2.8 vs rollback file)
- performing a native factory reset (from the stock recovery menu) unless recommended by an experienced contributor
- performing a native factory reset after Safestrap v4 is installed (instant brick)
- activating/using secondary slots in Safestrap v4 and then attempting to swap backup images between slots
- flashing unsupported roms in Safestrap v4 (CM12/CM13, stock FireOS, etc)
- manually twiddling file permissions or messing with build.prop after obtaining root (there's an app for that if needed)
Click to expand...
Click to collapse
I bricked a nextbook tablet with that last way (build.prop messing)
Will factory resetting from a custom ROM brick my device?
And don't worry, I won't be flashing stock fire OS.
Also, sorry if i'm asking too much, but since I don't see a place where the info is all together in one thread and not links to many others, could you either link me to a step-by-step tutorial or list them out yourself? Thank you
GameExpertNetwork said:
I bricked a nextbook tablet with that last way (build.prop messing)
Will factory resetting from a custom ROM brick my device?
And don't worry, I won't be flashing stock fire OS.
Also, sorry if i'm asking too much, but since I don't see a place where the info is all together in one thread and not links to many others, could you either link me to a step-by-step tutorial or list them out yourself? Thank you
Click to expand...
Click to collapse
As previously mentioned never do a factory reset from the native Kindle Fire recovery menu with Safestrap v4 installed. It will destroy the Safestrap environment and everything running within it regardless of rom.
Post #3 contains several links that should prove helpful. You'll need to do some reading.
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
Hello, until now I avoided to root my device (SGP612 / Stock Marshmallow), because I did not want to risk to lose the drm-keys or do other damage.
Besides that, there some apps, which will not run on rooted devices as netflix (at least I suppose so).
Now working on Tasker and other tools the demand of root is increasing more and more. But still I want to take it restrained and looking for a way to limit the root via ADB. I'm not sure, if that is possible, but I think, that would be a good compromise. Online I found a huge amount of guides and threads "how to root", but all of them, at least it looks like that, ending with an unlocked bootloader, TPRP, SuperSU and so on. I did not read all of them, because that would take years and these guides may also be outdated or even worse incorrect.
Therefor I'm here to ask you about yours assessment.
My main goal would be to:
- Make a full backup
- Protect the DRM-Keys and other irreversible stuff
- No app should be able to detect that the device has been rooted respectively modified on system-level
- Void a reset of the current setup
- Install some apps to system via adb and grant some permissions, uninstall few oem-apps
- Tweak a few settings via adb
Is that possible? And if so, are there some good and simplified guides, which I should read?
Wrong forum. This is for Z3 Compact phone. What you want is https://forum.xda-developers.com/z3-tablet-compact
You can root the phone without unlocking the bootloader, so I would assume that you can do the same with the tablet. You have to flash with an older ROM/kernel first, though, but it is doable.
temporary2010 said:
Wrong forum. This is for Z3 Compact phone. What you want is https://forum.xda-developers.com/z3-tablet-compact
You can root the phone without unlocking the bootloader, so I would assume that you can do the same with the tablet. You have to flash with an older ROM/kernel first, though, but it is doable.
Click to expand...
Click to collapse
I will ask the moderation to move my thread, thanks for the hint.
That sounds complicated to flash an older ROM, especially if no suitable instructions are known to me.
BTW. I prefer to stay at stock.
I am pretty sure you posted in the right forum. Everything you mention is possible, except making a full backup. I wouldn't know how without root or twrp. You can backup your TA partition with a special tool to save your drm keys. It uses the 'dirty cow' exploit so you may need to downgrade first (which wipes your data).
I think root via ADB requires a custom rom. You need to unlock your bootloader, which wipes all data. Alternatively, you can root your device with Magisk. It can hide itself from detection for a set of apps that you select.
M1chiel said:
I am pretty sure you posted in the right forum. Everything you mention is possible, except making a full backup. I wouldn't know how without root or twrp. You can backup your TA partition with a special tool to save your drm keys. It uses the 'dirty cow' exploit so you may need to downgrade first (which wipes your data).
I think root via ADB requires a custom rom. You need to unlock your bootloader, which wipes all data. Alternatively, you can root your device with Magisk. It can hide itself from detection for a set of apps that you select.
Click to expand...
Click to collapse
The thread has been moved by now, so that should be ok.
But still, I do not want any custom-rom. My experience with such on other devices in the past was very frustrating and a waste of time. Had always stability issues on driver-level and other misbehavior. On one samsung device I tested around ten or more roms and all of them was quite ****ty...
And until now it sounds like, I need to install a custom before I even can start to make backups and such. But I want a backup of the status quo, to which I could always rollback, if things gets ugly.
I like the current stock, is a good and stable base, a few tweaks and it would be perfect for me. Of course, I did not test any customs on my current device to be able to make some substantiated conclusion on that but I'm to distrustful to follow this path, especially not when there is no way back.
I miss any imagination what is possible and what is not, or what effect a particular measure entails. Therefor I can't estimate the accuracy of any guide and there are hundreds of them out there, and it looks like the approach is sometimes different. I started reading some of them, but stopped it because I could not retrace the content.
Can you recommend a good guide, which could work out for me and whats the name of the tool to backup the drm-keys? Thanks...
Check here for the TA backup https://forum.xda-developers.com/cr...rsal-dirtycow-based-ta-backup-t3514236/page47
I am very happy with this rom, the developer recently issued a Pie alpha (which I haven't tried yet)
https://forum.xda-developers.com/z3...m-aicp-android-ice-cold-project-o8-1-t3731197
There's a guide for rooting + recovery @ https://forum.xda-developers.com/z3...to-rooted-lollipop-locked-bootloader-t3083980
Be sure you follow the instructions very carefully, since you are flashing (the system partition) with the ROM from a Z3 phone.
The process is similar to the Z3 phones:
- flash to an older ROM
- root
- install custom recovery
- using custom recovery, flash with a prerooted, updated ROM
No need to unlock bootloader and no need for custom ROMs.
Asides from that, I don't know how to do the rest of the stuff in your list.
(I'm debating on getting a used Z3t, which is why I'm researching root possibilities .)