Related
I searched all yesterday and today and cannot re-root after upgrading from 4.1.2 to 4.3. I always do a ton of searchs no matter what forum I'm on because I don't want to seem lazy like some others out there but this is beyond me. I registered so I could make a thread and this is what I have and the situation:
Samsung Galaxy S3 SCH-R530U
US Cellular
upgraded from 4.1.2 to 4.3
kernel 3.031-2025306 [email protected] #1
baseband version R30UVXUBMJA
build number JSS15J.R530UVXUBMJA
SE for Android status Enforcing SEPF_SCH-530U_4.3_0010
hardware version R530U.01
Previously rooted using Odin, SuperSU, Titanium Backup Pro, ODIN_CWM6.tar.md5
I took the phone back to stock using unroot through SuperSU and upgraded from 4.1.2 to 4.3 OTA with no problems. I've been trying to re-root using numerous combinations (ODIN3 v3.07) and no matter what I do the Samsung Security notice blocks rights to SuperSU (beta v1.76) and Titanium Backup Pro so it won't root. This is the message I get:
"Security notice - unauthorized access to a secured area has been blocked. Tap to learn more."
The most recent md5 file I've tried is CF-Auto-Root-d2usc-d2usc-schr530u.tar.md5 but nothing else has worked either. I'm at my wits end and my brain is about ready to explode. I just need to be able to access Titanium Backup Pro so I can shut off a few programs and processes. Any help is VERY VERY much appreciated. Thanks!!!!!
TTT for some help please.
jguenther said:
I searched all yesterday and today and cannot re-root after upgrading from 4.1.2 to 4.3. I always do a ton of searchs no matter what forum I'm on because I don't want to seem lazy like some others out there but this is beyond me. I registered so I could make a thread and this is what I have and the situation:
Samsung Galaxy S3 SCH-R530U
US Cellular
upgraded from 4.1.2 to 4.3
kernel 3.031-2025306 [email protected] #1
baseband version R30UVXUBMJA
build number JSS15J.R530UVXUBMJA
SE for Android status Enforcing SEPF_SCH-530U_4.3_0010
hardware version R530U.01
Previously rooted using Odin, SuperSU, Titanium Backup Pro, ODIN_CWM6.tar.md5
I took the phone back to stock using unroot through SuperSU and upgraded from 4.1.2 to 4.3 OTA with no problems. I've been trying to re-root using numerous combinations (ODIN3 v3.07) and no matter what I do the Samsung Security notice blocks rights to SuperSU (beta v1.76) and Titanium Backup Pro so it won't root. This is the message I get:
"Security notice - unauthorized access to a secured area has been blocked. Tap to learn more."
The most recent md5 file I've tried is CF-Auto-Root-d2usc-d2usc-schr530u.tar.md5 but nothing else has worked either. I'm at my wits end and my brain is about ready to explode. I just need to be able to access Titanium Backup Pro so I can shut off a few programs and processes. Any help is VERY VERY much appreciated. Thanks!!!!!
Click to expand...
Click to collapse
I have same phone. Recently went to Slimbean (4.3.1). I have Triangle Away and it couldn't access root. I also used CF-Auto-Root. Used a root check app, it says I am rooted. Odin also said device passed. Super User says I am missing a binary and I need to root manually. Trying to find that info
If you find anything out please let me know. A root checker says I'm rooted but I can't access SuperSU or Titanium backup as the S3 is blocking it.
Did you get the Slimbean 4.3.1 for USCC and if so where?
There was just a new SuperSU update and it granted me access to everything. I asked if I wanted it to disable KNOX and I said yes. Titanium Backup works and so does Triangle Away. I think I'm good to go.
How did you update?
jguenther said:
There was just a new SuperSU update and it granted me access to everything. I asked if I wanted it to disable KNOX and I said yes. Titanium Backup works and so does Triangle Away. I think I'm good to go.
Click to expand...
Click to collapse
How did you update to 4.3? Did you use the simple update you can download to computer, or did you use Kies? I'm not having any luck with either. I chatted twice with a Samsung Tech person, but neither one had any help for me. Just thought I'd check to see if you could help me. It's not easy finding someone else on here with US Cellular. Any help would be appreciated. Thank you.
smithar said:
How did you update to 4.3? Did you use the simple update you can download to computer, or did you use Kies? I'm not having any luck with either. I chatted twice with a Samsung Tech person, but neither one had any help for me. Just thought I'd check to see if you could help me. It's not easy finding someone else on here with US Cellular. Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
I tried to download the simple update but my phone wouldn't update to the 4.3 so I did it over the air. You probably know but the OTA software update is in "about device." We have four S3s in our home and only one of them hasn't been able to get the download OTA yet. The only bug that I've found is when you start the phone it will show numerous downloads in the notifications and they will come back even if you clear them. The way to get rid of them is to go to the download icon (green arrow) and clear all the downloads and restart. Hope this helps.
jguenther said:
I tried to download the simple update but my phone wouldn't update to the 4.3 so I did it over the air. You probably know but the OTA software update is in "about device." We have four S3s in our home and only one of them hasn't been able to get the download OTA yet. The only bug that I've found is when you start the phone it will show numerous downloads in the notifications and they will come back even if you clear them. The way to get rid of them is to go to the download icon (green arrow) and clear all the downloads and restart. Hope this helps.
Click to expand...
Click to collapse
I have downloaded the simple update, but get an error msg while trying to install to computer. (1152: error extracting) whatever that means. I uninstalled all Samsung anything from my computer, restarted, shut off firewall & Norton, downloaded again, but same thing while trying to install to computer. I updated to 4.1.2 this way, but keep getting an error on 4.3 update.
I tried to go through Kies. It updated Kies to 2.6, it said Kies3 was for 4.3. When I tried to hook into Kies, it refuses to accept my IMEI #. Says its incorrect. wth. The Samsung Chat Tech told me USCellular 4.3 update wasn't available yet through Kies OTA.
When I tried to get the 4.1.2 update through the phone, it would never give it to me. Even though I unrooted and used Triangle Away, it still knew my sg3 was modified. Maybe I'm doing something wrong. Do you have any suggestions ? I'm not very tech savvy when it comes to these phones.
I'm sorry to bother you with this, but it's rare to find someone with USCellular on here. Thank you so much for your time.
I got the error message too so something is wrong with the download from Samsung/USCC. Just keep trying to do the OTA update and maybe it will go through. My GUESS is that Samsung and USCC stopped doing the update because of a couple bugs or issues. The reason I say that is I updated mine one day (worked), my wife's the next (worked), my son's the next days later (worked) and tried my other son's a couple days later and no update for him. I unrooted mine before the update without doing triangle away so I don't know if that really has anything to do with it at all. However, it does have to be unrooted if you do the OTA. Good luck!
I used Triangle Away, then unrooted. My phone still says 'modified' even though counter no longer says 2. When I try OTA through the phone, it constantly sticks on 'checking for updates'. I'm sure it's because it still says modified. I tried using Kies, my phone will not connect. Keeps saying my s/n is incorrect. I understand my IMEI has been corrupted.
I have started a thread on here for some help in how to get the 4.3 update.
Thank you so much for trying to help me. I will be eligible for an upgrade soon. I just may have to wait to have anything more than 4.1.2.
Again, thank you.
Samsung
jguenther said:
I searched all yesterday and today and cannot re-root after upgrading from 4.1.2 to 4.3. I always do a ton of searchs no matter what forum I'm on because I don't want to seem lazy like some others out there but this is beyond me. I registered so I could make a thread and this is what I have and the situation:
Samsung Galaxy S3 SCH-R530U
US Cellular
upgraded from 4.1.2 to 4.3
kernel 3.031-2025306 [email protected] #1
baseband version R30UVXUBMJA
build number JSS15J.R530UVXUBMJA
SE for Android status Enforcing SEPF_SCH-530U_4.3_0010
hardware version R530U.01
Previously rooted using Odin, SuperSU, Titanium Backup Pro, ODIN_CWM6.tar.md5
I took the phone back to stock using unroot through SuperSU and upgraded from 4.1.2 to 4.3 OTA with no problems. I've been trying to re-root using numerous combinations (ODIN3 v3.07) and no matter what I do the Samsung Security notice blocks rights to SuperSU (beta v1.76) and Titanium Backup Pro so it won't root. This is the message I get:
"Security notice - unauthorized access to a secured area has been blocked. Tap to learn more."
The most recent md5 file I've tried is CF-Auto-Root-d2usc-d2usc-schr530u.tar.md5 but nothing else has worked either. I'm at my wits end and my brain is about ready to explode. I just need to be able to access Titanium Backup Pro so I can shut off a few programs and processes. Any help is VERY VERY much appreciated. Thanks!!!!!
Click to expand...
Click to collapse
it looks to me like samsung are finally making a stand against rooting although i do not agree with this as i use an app called freedom and when i open it i get a security issue from Samsung
The only reason i left iphone for samsung was because i felt like they had something other apple with hardware and i was happy to do this as i could get root access but for now i see that this might not be possible for a while.
i recommend installing a normal superuser.apk and that might work but i cannot check this right now as i am out
i hope this little bit of information did help in anyway
I'm completely new to rooting. I plan on rooting my Galaxy SII using the Cyanogenmod Installer. However, I want to know how to return to stock.
I found this FAQ online and want to know if it's the correct way of doing it or if there's some easier way out there.
http://www.samsung.com/us/support/faq/FAQ00052690/61265
I would also like to know if Triangle Away works with the Hercules? Thank you.
Hero746 said:
I'm completely new to rooting. I plan on rooting my Galaxy SII using the Cyanogenmod Installer. However, I want to know how to return to stock.
I found this FAQ online and want to know if it's the correct way of doing it or if there's some easier way out there.
http://www.samsung.com/us/support/faq/FAQ00052690/61265
I would also like to know if Triangle Away works with the Hercules? Thank you.
Click to expand...
Click to collapse
Well I first would do a superwipe on TWRP before anything, and download ODIN and your SAMSUNG drivers. I have included a nifty .zip file with everything you would ever need, with all of the firmwares, drivers and ODINs. After you run that superwipe, go on download mode by plugging in your USB cord on your computer, then on your phone. Hold down both volume keys and proceed to turn on your phone. Then, you should see a screen that says volume up to install custom firmware, and volume down to restart. Press volume up. Open ODIN, and click on the PDA or AP (which ever one it says) proceed to go to one of the three files, I have included either 4.0.3, 4.0.4 and 4.1.2. Pick which file you want to restore to and press start. Let it do it's thing and you're done. To root, just go back to ODIN, point it at your root folder and double click on the TWRP file. I have included the upgrade .zip as well to put it to the latest TWRP that works correctly. Enjoy! (The link is huge because it has EVERY SINGLE Stock ROM from ICS and up).
Download to everything: https://mega.co.nz/#!AJ83jQzD!PjrpkBxbFAuQucYEnVcH7yWHagcy3z9Q_3sQ8ZBK980
Also, I have not tried triangle away, but from what I know I've flashed so many times but I haven't even tripped the counter yet.
I'm bumping this with the intent of thanking you.
I followed your instructions to the dot and returned my phone to stock in preparation for the Note 3 I'm getting tomorrow. I feel like this thread should be stickied or included in some sort of master list so as to help the rest of the community.
A word of advice though. If Odin fails to recognize your SGH-T989, you must uninstall and then reinstall your Samsung Drivers. Once again, thank you!
★ |[How-To]| | ROOT NK3 | KEEP KNOX 0x0 | The EffortLess Way | Rooting | 26NOV14 ★
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you do not care about KNOX and want a custom recovery or custom ROM installed in addition to root- Go to my other thread here! A custom ROM or custom recovery WILL trip your KNOX to 0x1 (this is irreversible and KNOX will cease to function on your phone forever and ever and ever) :crying:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
************************************************** ************************************************** ************************************************** ************************************************** **************************************************
Welcome to ROOT with KNOX 0x0 the EffortLess Way!!This is a quick and easy way to root the N900T T-Mobile Note 3 with the full stock N900TUVUENK3 update installed!
This guide will assist you in rooting full stock N900TUVUENK3 without tripping KNOX (preserving 0x0)
************************************************** ************************************************** ************************************************** ************************************************** **************************************************NOTE: You will need to be updated to the full stock N900TUVUENK3 firmware before proceeding!
If you need to update to N900TUVUENK3 and are on a stock firmware that has not been rooted yet:
Use the built-in Over The Air (OTA) software updater in your phone settings to check for an update then follow the instructions to update.
After booting up, check for an update again and confirm there are none and that you are on firmware N900TUVUENK3 before proceeding to the "EffortLess Rooting Guide" below.
If you are updating from any prior rooted stock firmware (basically, you've used this guide before but need to update) you will need to follow these steps:
Download EffortLess ROM Prep.zip and Full Stock NK3.zip
Unzip both files
Turn off your phone and then hold the Volume Down, Home Button, and Power Button at the same time, when the phone vibrates, let go of Power Button. Press Volume Up to continue past the "Warning!!" screen.
Open the EffortLess ROM Prep folder and double click on EffortLess Odin.exe
Connect your phone to the computer via USB cable (one of the boxes under ID:COM in Odin will fill with a com number and turn baby blue meaning it can communicate with your phone.. if it does not, unplug your phone and run EffortLess Odin USB Driver.exe from the EffortLess ROM Prep unzipped folder. Now plug your phone in again and it should load the driver and the box should turn baby blue and display a com number)
Click the PDA button and navigate to the unzipped Full Stock NK3 folder, click on N900TUVUENK3_N900TTMBENK3_N900TUVUENK3_HOME.tar.md5 and click Open
Wait for the file to load properly in Odin, it will take a minute and you'll see a check-mark to the left of the PDA button and the system path of the NK3 file to the right.
Now click start and wait, don't touch anything until after your phone restarts.
Now go to menu, settings, General tab, and click About device and verify the Baseband version AND Build Number are N900TUVUENK3
************************************************** ************************************************** ************************************************** ************************************************** **************************************************EffortLess Rooting Guide
This method will revert the kernel back to the Samsung stock NE6 kernel (that is vulnerable to the towelroot method). Then you will use towelroot to root. Finally, you will flash back the NK3 kernel and enjoy root on your stock NF3 phone!
This process should take approximately 5 minutes and will not erase any files on your phone.
First download and install towelroot on your phone]:
Navigate to towelroot on your phone (once at the site, click the main center logo) and install the downloaded app (do not open the app and click make it ra1n yet).
Then download EffortLessRootPrep.zip on your Windows computer and unzip it.
Flashing NE6 Kernel
Turn off your phone and then hold the Volume Down, Home Button, and Power Button at the same time, when the phone vibrates, let go of Power Button. Press Volume Up to continue past the "Warning!!" screen.
Open the EffortLess Root Prep folder and double click on EffortLess Odin.exe
Connect your phone to the computer via USB cable (one of the boxes under ID:COM in Odin will fill with a com number and turn baby blue meaning it can communicate with your phone.. if it does not, unplug your phone and run EffortLess Odin USB Driver.exe from the EffortLess Root Prep unzipped folder. Now plug your phone in again and it should load the driver and the box should turn baby blue and display a com number)
Click the PDA button and navigate to the unzipped EffortLess Root Prep folder, click on N900TUVUDNE6_KERNEL.tar.md5 and click Open
Wait for the file to load properly in Odin, it will take a minute and you'll see a check-mark to the left of the PDA button and the system path of the root file to the right.
Now click start and wait, don't touch anything until after your phone restarts.
Running towelroot
Once your phone boots up, open the towelroot app and click "make it ra1n".
Wait ten seconds and then reboot your phone. (I know it says reboot is not required, do it anyway)
Open SuperSU (if it's not in your app drawer, download it from the play store) and if it asks to update the binary, choose the normal method. (if it says installation failed, just try again or try again after you flash back to NK3, it's normal and it'll be updated)
When it mentions disabling KNOX, click ok (this will not trip KNOX, it will simply disable it for the time being.. If you want to use KNOX while rooted, don't disable it in SuperSU). NOTE: if it hangs disabling KNOX don't worry. Turn off your phone and proceed to the next step. After flashing the NK3 Kernel back, open SuperSU and disable KNOX and it should work within a few seconds.
Flashing NK3 Kernel back
Turn off your phone and then hold the Volume Down, Home Button, and Power Button at the same time, when the phone vibrates, let go of Power Button. Press Volume Up to continue past the "Warning!!" screen.
Open the EffortLess Root Prep folder and double click on EffortLess Odin.exe
Connect your phone to the computer via USB cable (one of the boxes under ID:COM in Odin will fill with a com number and turn baby blue meaning it can communicate with your phone.. if it does not, unplug your phone and run EffortLess Odin USB Driver.exe from the EffortLess Root Prep unzipped folder. Now plug your phone in again and it should load the driver and the box should turn baby blue and display a com number)
Click the PDA button and navigate to the unzipped EffortLess Root Prep folder, click on N900TUVUENK3_KERNEL.tar.md5 and click Open
Wait for the file to load properly in Odin, it will take a minute and you'll see a check-mark to the left of the PDA button and the system path of the root file to the right.
Now click start and wait, don't touch anything until after your phone restarts.
You can uninstall the towelroot app after you're are finished.
If this helped, please click the "Thanks" button! :good:
| Let me know you like it :highfive: Donate to show your support |
Thanks to:
@geohot for making towelroot
and special thanks @toastito for getting me the stock Odin flashable kernels!
This worked for me! Followed your steps and I now have root with Knox counter 0x0. Thank you for the guide! The only issue I had was while updating the Super SU binaries I received an "installation failed" message after updating and disabling knox, but after flashing back to the NF4 kernel I had root and Super SU works fine. You might want to add something to the guide so people know this is normal. :good:
_bhaves_ said:
This worked for me! Followed your steps and I now have root with Knox counter 0x0. Thank you for the guide! The only issue I had was while updating the Super SU binaries I received an "installation failed" message after updating and disabling knox, but after flashing back to the NF4 kernel I had root and Super SU works fine. You might want to add something to the guide so people know this is normal. :good:
Click to expand...
Click to collapse
Thanks for the feedback _bhaves_! I'll be adjusting the guide as I get more feedback. I was only able to test this twice as my phone is already KNOX 0x1 and I had limited time with the KNOX 0x0 phone. I concentrated on ensuring KNOX would stay 0x0 during my testing. I had different results than you regarding installing the binaries. Now I feel that running SuperSU and updating it and disabling KNOX should be done after flashing back to NF4 kernel. I feel the reboot clears stuff up and enables SuperSU to function more fluidly. I'll change it to that and await further feedback.
Thanks for the guide! I was on NF1 and used your guides to successfully go to NF4 with no issues and still have not tripped KNOX...thank you good sir.
effortless said:
************************************************** ************************************************** ************************************************** ************************************************** **************************************************
Welcome to ROOT with KNOX 0x0 the EffortLess Way!!This is a quick and easy way to root the N900T T-Mobile Note 3 with the full stock NF4 update installed!
This guide will assist you in rooting NF4 without tripping KNOX (preserving 0x0)
Only proceed with this guide if you want root and do not want a custom recovery or custom ROM installed!
NOTE: You will need to be updated to the full stock NF4 ROM before proceeding!
If you need to update to NF4, use the EffortLess Guide and stop after the "For full N900TUVUDNF4 stock:" section, steps 1-8. (DO NOT proceed to root or flash a custom recovery in that thread) then come back here.
This method will revert the kernel back to the Samsung stock NE6 kernel (that is vulnerable to the towelroot method). Then you will use towelroot to root. Finally, you will flash back the NF4 kernel and enjoy root on your stock NF4 phone!
This process should take approximately 5 minutes and will not erase any files on your phone.
************************************************** ************************************************** ************************************************** ************************************************** **************************************************
First download towelroot (once at the site, click the main center logo) on your phone and install the app (do not click make it ra1n yet).
Then download EffortLessRootPrep.zip on your Windows computer and unzip it.
Rooting NF4 (Flashing NE6 Kernel)
Turn off your phone and then hold the Volume Down, Home Button, and Power Button at the same time, when the phone vibrates, let go of Power Button. Press Volume Up to continue past the "Warning!!" screen.
Open the EffortLess Root Prep folder and double click on EffortLess Odin.exe
Connect your phone to the computer via USB cable (one of the boxes under ID:COM in Odin will fill with a com number and turn baby blue meaning it can communicate with your phone.. if it does not, unplug your phone and run EffortLess Odin USB Driver.exe from the EffortLess Root Prep unzipped folder. Now plug your phone in again and it should load the driver and the box should turn baby blue and display a com number)
Click the PDA button and navigate to the unzipped EffortLess Root Prep folder, click on N900TUVUDNE6_KERNEL.tar.md5 and click Open
Wait for the file to load properly in Odin, it will take a minute and you'll see a check-mark to the left of the PDA button and the system path of the root file to the right.
Now click start and wait, don't touch anything until after your phone restarts.
Rooting NF4 (Running towelroot)
Once your phone boots up, open the towelroot app and click "make it ra1n".
Wait ten seconds and then reboot your phone. (I know it says reboot is not required, do it anyway)
Open SuperSU (if it's not in your app drawer, download it from the play store) and if it asks to update the binary, choose the normal method. (if it says installation failed, just try again or try again after you flash back to NF4, it's normal and it'll be updated)
When it mentions disabling KNOX, click ok (this will not trip KNOX, it will simply disable it for the time being.. If you want to use KNOX while rooted, don't disable it in SuperSU). NOTE: if it hangs disabling KNOX don't worry. Turn off your phone and proceed to the next step. After flashing the NF4 Kernel back, open SuperSU and disable KNOX and it should work within a few seconds.
Rooting NF4 (Flashing NF4 Kernel back)
Turn off your phone and then hold the Volume Down, Home Button, and Power Button at the same time, when the phone vibrates, let go of Power Button. Press Volume Up to continue past the "Warning!!" screen.
Open the EffortLess Root Prep folder and double click on EffortLess Odin.exe
Connect your phone to the computer via USB cable (one of the boxes under ID:COM in Odin will fill with a com number and turn baby blue meaning it can communicate with your phone.. if it does not, unplug your phone and run EffortLess Odin USB Driver.exe from the EffortLess Root Prep unzipped folder. Now plug your phone in again and it should load the driver and the box should turn baby blue and display a com number)
Click the PDA button and navigate to the unzipped EffortLess Root Prep folder, click on N900TUVUDNF4_KERNEL.tar.md5 and click Open
Wait for the file to load properly in Odin, it will take a minute and you'll see a check-mark to the left of the PDA button and the system path of the root file to the right.
Now click start and wait, don't touch anything until after your phone restarts.
You can uninstall the towelroot app after you're are finished.
If this helped, please click the "Thanks" button! :good:
| Let me know you like it :highfive: Donate to show your support |
Thanks to:
@geohot for making towelroot
and special thanks @toastito for getting me the stock Odin flashable kernels at short notice while I was away from my workstation!
Click to expand...
Click to collapse
I really wish this had came out when started rooting my Note. I had to send my phone out to Samsung and had to pay to have it fixed
N900TUVUDNE6_KERNEL.tar.md5 is not present in the folder. Only a CF root file is there and a recovery file.
Towelroot states the device isn't supported.
Knox Warranty Void 0x1
conchchowder said:
N900TUVUDNE6_KERNEL.tar.md5 is not present in the folder. Only a CF root file is there and a recovery file.
Towelroot states the device isn't supported.
Click to expand...
Click to collapse
You're mixing my how-to threads and files. You didn't download the EffortLessRootPrep file... you downloaded the EffortLess ROM Prep.zip which is used to install a custom recovery and custom rom (both of which will trip your KNOX if flashed).
Also, the whole purpose of this thread is to downgrade to the NE6 kernel which supports towelroot (before running it). I specifically mention not to run it (until after you downgrade to the NE6 kernel), because it's not compatible with NF4.
[emoji15]
Sent from my SM-N900T using Tapatalk
worked perfectly for me !!!
I would like to thank OP and other developers for all their efforts, it worked like a charm.
But I do have a quick question: I stayed on 4.3 until now due to SD card access being broken and fix requiring root access, that trip Knox.
Of course this solution solved Knox worry and therefore I went ahead updating, however I don't seem to have any SD card issues yet, even before I applied the fix. I just would like to know why?
1. Is it because Google or Samsung fix it in later release?
2. Is it because all the apps I use were already updated?
3. is it because ROMs were somehow fixed either by rooting, or by the people posting the ROM.
Or maybe it's not fixed? When I use ES explorer, I see the folders, but many appear empty, like titanium backup for example.
Now this would be the most stupid thing, if all those folders showing empty weren't, since I always delete empty folders as a rule.
So are SD Card access restrictions fixed in NF4 or not and if not which fix is working well, since I came across some posts that claim broken BT, after applying the fix.
TIA
pete4k said:
I would like to thank OP and other developers for all their efforts, it worked like a charm.
But I do have a quick question: I stayed on 4.3 until now due to SD card access being broken and fix requiring root access, that trip Knox.
Of course this solution solved Knox worry and therefore I went ahead updating, however I don't seem to have any SD card issues yet, even before I applied the fix. I just would like to know why?
1. Is it because Google or Samsung fix it in later release?
2. Is it because all the apps I use were already updated?
3. is it because ROMs were somehow fixed either by rooting, or by the people posting the ROM.
Or maybe it's not fixed? When I use ES explorer, I see the folders, but many appear empty, like titanium backup for example.
Now this would be the most stupid thing, if all those folders showing empty weren't, since I always delete empty folders as a rule.
So are SD Card access restrictions fixed in NF4 or not and if not which fix is working well, since I came across some posts that claim broken BT, after applying the fix.
TIA
Click to expand...
Click to collapse
This is a copy and paste of a previous statement I've made about this topic:
A lot of people are very confused on the SD card changes. YOU DO NOT LOSE SD CARD access! The change was that if an app created a folder on your SD card to store stuff, another app cannot access and make changes to it (Which is how it should have been from the beginning). There are many reasons as to why this is the better way (many security related as well as programming related scenarios).
This means that each app can create and write changes to SD card folders it creates and no other folder. The app has to be the creator of the folder it's making changes to.. that makes sense right?! You can still put all the music and pictures and documents you want on the SD card and they will still work like in the past. A few apps had to be updated because they were doing things the old way, but that's been done and you shouldn't have any issues that people had when the change first was done.
4.4 adds a host of new features, bug fixes, network efficiency enhancements and security patches (some are very serious and if you're still on 4.3, your phone is at risk daily). I highly suggest everyone upgrade. If you have any particular issue, private message me and I will help you address it!
To address your current questions though, the change wasn't something that was broken by Google. It shouldn't have been called an SD Card Fix either (like I said, it didn't break), but there were changes in the way Android Apps interacted with the SD card. You can still do this SD Card Fix manually or just use an app in the play store to make the changes for you. There are still certain situations where the "SD Card Fix" is useful, but if it's working for you, then leave it the way it is. Most problems initially were due to needing updates for apps at the time.
effortless said:
This is a copy and paste of a previous statement I've made about this topic:
A lot of people are very confused on the SD card changes. YOU DO NOT LOSE SD CARD access! The change was that if an app created a folder on your SD card to store stuff, another app cannot access and make changes to it (Which is how it should have been from the beginning). There are many reasons as to why this is the better way (many security related as well as programming related scenarios).
This means that each app can create and write changes to SD card folders it creates and no other folder. The app has to be the creator of the folder it's making changes to.. that makes sense right?! You can still put all the music and pictures and documents you want on the SD card and they will still work like in the past. A few apps had to be updated because they were doing things the old way, but that's been done and you shouldn't have any issues that people had when the change first was done.
4.4 adds a host of new features, bug fixes, network efficiency enhancements and security patches (some are very serious and if you're still on 4.3, your phone is at risk daily). I highly suggest everyone upgrade. If you have any particular issue, private message me and I will help you address it!
To address your current questions though, the change wasn't something that was broken by Google. It shouldn't have been called an SD Card Fix either (like I said, it didn't break), but there were changes in the way Android Apps interacted with the SD card. You can still do this SD Card Fix manually or just use an app in the play store to make the changes for you. There are still certain situations where the "SD Card Fix" is useful, but if it's working for you, then leave it the way it is. Most problems initially were due to needing updates for apps at the time.
Click to expand...
Click to collapse
Thank you for response and again great job on the root.
The reason I used word "broken" was because originally it broke many programs. I would hate not to be able to access DCIM directory created by camera, to view or delete pics with my favorite third party view program, just to give an example, of why limiting access to SD card could create major issues, but it seems to be working fine so far, so I leave it alone for now.
Another quick question: phone status says official, so do I need to worry about future updates breaking the root, or is OTA updates not possible despite official status.
pete4k said:
Thank you for response and again great job on the root.
The reason I used word "broken" was because originally it broke many programs. I would hate not to be able to access DCIM directory created by camera, to view or delete pics with my favorite third party view program, just to give an example, of why limiting access to SD card could create major issues, but it seems to be working fine so far, so I leave it alone for now.
Another quick question: phone status says official, so do I need to worry about future updates breaking the root, or is OTA updates not possible despite official status.
Click to expand...
Click to collapse
Don't accept the OTA updates (you can be notified even when rooted). They will most likely result in a softbrick.
Wait for someone to test it or you might have to unroot and take the update and then perform a similar method to get root back. It depends on what they do to prevent things like this in the future (if anything).
thanks for your quick reply, on my previous root phone status was custom, so no OTA there. I guess I just freeze the update app to be on safe side, kids play my phone sometimes and could update by accident, I remember from the time before root how pesky those update reminders can be and how easy it is to press accept instead of cancel.
Quick question: I am already at NE6, rooted with TowelRoot and KNOX is NOT tripped. Which steps I need to follow to upgrade to NF4?
Or is the steps shown here is not applicable in my case?
lanwarrior said:
Quick question: I am already at NE6, rooted with TowelRoot and KNOX is NOT tripped. Which steps I need to follow to upgrade to NF4?
Or is the steps shown here is not applicable in my case?
Click to expand...
Click to collapse
This guide will work for you. However, you should start from fresh stock NF4 unrooted. Odin stock NF4 and proceed.
It's a lot harder to update a rooted NE6 to all the NF4 files then it is to root NF4 using the NE6 kernel.
effortless said:
This guide will work for you. However, you should start from fresh stock NF4 unrooted. Odin stock NF4 and proceed.
It's a lot harder to update a rooted NE6 to all the NF4 files then it is to root NF4 using the NE6 kernel.
Click to expand...
Click to collapse
I just did an upgrade from NE6 to NF4 following the thread here: http://forum.xda-developers.com/not...udnf4-extracted-stock-firmware-t2834398/page3
But my phone is now hosed - cannot use keyboard ("Unfortunately, Samsung Keyboard has stopped" error) and APN is gone from SIM card. So I am trying to salvage this.
If I Odin NF4 (add the NF4 file to "AP" in Odin), wouldn't this trip KNOX?
lanwarrior said:
I just did an upgrade from NE6 to NF4 following the thread here: http://forum.xda-developers.com/not...udnf4-extracted-stock-firmware-t2834398/page3
But my phone is now hosed - cannot use keyboard ("Unfortunately, Samsung Keyboard has stopped" error) and APN is gone from SIM card. So I am trying to salvage this.
If I Odin NF4 (add the NF4 file to "AP" in Odin), wouldn't this trip KNOX?
Click to expand...
Click to collapse
No.. Knox is only tripped with custom kernel or custom recovery. Flashing stock NF4 in Odin will not trip Knox. Just flash NF4 in Odin and reset your phone through the settings and it will be working fine again.
Don't continue to flash the recovery or root your phone through my other guide as it will trip Knox (If that is something you are avoiding).
effortless said:
Don't continue to flash the recovery or root your phone through this guide as it will trip Knox (If that is something you are avoiding).
Click to expand...
Click to collapse
Oh, I thought this guide refer to rooting NF4? I was reading through the steps and it talks about "downgrading" to NE6 kernel if one already have NF4.
If needed to, I can flash stock NE6, do a system update to NF4, then follow this guide.
Err.. I just realized that my phone still have SU and root still working, even after hard reset. That means system update won't work. I guess flashing stock will wipe out root?
lanwarrior said:
Oh, I thought this guide refer to rooting NF4? I was reading through the steps and it talks about "downgrading" to NE6 kernel if one already have NF4.
If needed to, I can flash stock NE6, do a system update to NF4, then follow this guide.
Err.. I just realized that my phone still have SU and root still working, even after hard reset. That means system update won't work. I guess flashing stock will wipe out root?
Click to expand...
Click to collapse
Sorry for the confusion. I edited it to say my other guide (my other guide is for custom recovery and custom rom).. through this guide is fine. Don't root through Odin, root using the NE6 kernel and towelroot like it says and you'll be ok with Knox.
Hi all
i have tried everything to try rooting my note 2.
I got to the point that Su appears in my apps list but it stops responding and the little grey shield comes up to say unauthorised access was stopped. Also trying to update*
i then tried Cwm and twrp and it has a green pass on doing but it does not give me a new download menu so that I can install multi tools from zip.*
What else can I do to root and/or bypass know? I have hard reset my phone (btw su is still on) and busy downloading a stock 4.3 rom.
must I install stock rom and try again? Or what else can I try?
see details below of my details
http://forum.xda-developers.com/showthread.php?t=2339704
have tried these threads but it all seems to refer to pre 4.3
can I download pre rooted 4.3 firmware from somewhere else?
SIlvRav said:
Hi all
i have tried everything to try rooting my note 2.
I got to the point that Su appears in my apps list but it stops responding and the little grey shield comes up to say unauthorised access was stopped. Also trying to update*
i then tried Cwm and twrp and it has a green pass on doing but it does not give me a new download menu so that I can install multi tools from zip.*
What else can I do to root and/or bypass know? I have hard reset my phone (btw su is still on) and busy downloading a stock 4.3 rom.
must I install stock rom and try again? Or what else can I try?
see details below of my details
Click to expand...
Click to collapse
Option 1: Following process should work for your N7105 phone.
http://forum.xda-developers.com/showthread.php?t=2535015
u have already tried this as exactly told, then you go to option 2
Option 2: Follow Dr. Ketans thread.
http://forum.xda-developers.com/showthread.php?t=2032849
If none of above work, Lastly install stock rom.
Sent from my GT-N7100 using Tapatalk
First things first. I surrender. I'm a noob with android. I had windows phone previously and only now came to android.
Here's the scenario:
1. My z2 force was properly rooted with magisk and twrp. I followed the guide in xda only.
2. My device was brought from India so carriers like sprint, t-mobile are not applicable I think.
What I Did:
0. Wanted to unroot my device. So, I decided to first uninstall the modules in magisk that I had installed.
1. Tried to uninstall magisk modules and rebooted from the magisk application.
2. Got into Boot loop, so went to recovery mod and wiped everything. Hard reset was done.
3. Installed magisk app again and clicked uninstall to remove root. I wanted to install the latest security update. Update kept failing so I decided to unroot. I choose uninstall completely option.
4. Rebooted the phone manually after clicking uninstall in magisk manager. Using the 'root checker' app I checked if unrooting was successful but it said, 'root was not properly installed' or something like that. So, I installed magisk manager again and again uninstalled root completely.
5. Still same issue. Root checker said the same thing again. So, installed magisk manager again and this time I wanted to remove root using ES file manager as I saw in an online guide. But I couldn't give it root permission because it was not properly installed as said by root checker. So, I decided to root my phone properly but stupid me, clicked 'install' in magisk manager and chose the recommended option (don't remember exactly what it was). It downloaded magisk zip and did some changes and asked to reboot. After rebooting, my phone went straight to the black screen with an android icon and 'no command' written below it. It kept going there again and again.
6. I assume that is the recovery mode. I press volume up and power button and choose the wipe everything again(Like I did before) to hard reset phone. Wiping was successful but it still kept booting to that black screen.
Additional Info:
1. Phone wasn't carrier version. It was bought in India. It is running Oreo 8.0.
2. In bootloader menu : (Not stating all)
BL: MBM-3.0-nash_retail-641a15b-180306
Product/Variant: nask xt1789-06 64GB PVT
Console[NULL] :null
Tools Mode Config: DISABLED
Power OK
flashing_unlocked
Software Status : Modified
Transfer Mode : USB Connected.
3. Yes, Bootloader menu is accessible.
4. Choosing recovery mode in bootloader menu reboots phone and takes me to that blank screen I mentioned before.
5. Connecting to USB to my PC when in bootloader menu, it connects as 'Fastboot nash S'. ADB terminal says no devices found.
What I want:
1. Boot into OS.
2. Remove root completely so I can install system update.
Please help or offer suggestions as I do not have a secondary device with me. If I have to absolutely go to a service center, I will.
You should flash it back to stock.
You posted that your phone is nash xt1789-06 64GB PVT, you can grab the latest firmware here.
The flashing instructions are here in post #5, and any question you might have is most likely answered in that thread.
Just download the firmware, boot into bootloader mode, and follow the instructions.
FYI in fastboot mode adb commands don't work, it's fastboot. To verify that you're connected and ready type
Code:
fastboot devices
and you should see your serial# like you do in adb.
That should put you back to stock and good to go.
41rw4lk said:
You should flash it back to stock.
You posted that your phone is nash xt1789-06 64GB PVT, you can grab the latest firmware here.
The flashing instructions are here in post #5, and any question you might have is most likely answered in that thread.
Just download the firmware, boot into bootloader mode, and follow the instructions.
FYI in fastboot mode adb commands don't work, it's fastboot. To verify that you're connected and ready type
Code:
fastboot devices
and you should see your serial# like you do in adb.
That should put you back to stock and good to go.
Click to expand...
Click to collapse
Thank you for the reply. I figured it out and went ahead with it. But now, I'm not seeing the May security update. The device shows it has March update and that no other update is available. Any idea why? Also, root checker still says 'root not properly installed'. How to unroot completely? Thanks a lot!
Sparkzz27 said:
You should flash it back to stock.
You posted that your phone is nash xt1789-06 64GB PVT, you can grab the latest firmware here.
The flashing instructions are here in post #5, and any question you might have is most likely answered in that thread.
Just download the firmware, boot into bootloader mode, and follow the instructions.
FYI in fastboot mode adb commands don't work, it's fastboot. To verify that you're connected and ready type
Thank you for the reply. I figured it out and went ahead with it. But now, I'm not seeing the May security update. The device shows it has March update and that no other update is available. Any idea why? Also, root checker still says 'root not properly installed'. How to unroot completely? Thanks a lot!
Click to expand...
Click to collapse
Did you look to see if the May Security Update has been released for your specific device? When you downloaded the stock firmware did you look to see what month security patch it contained? Have you tried to perform a system update to see if you can OTA to the latest security patch?
Now, if you completely flashed back to stock then root is removed. Root checker says that because root access is not installed at all. Flashing back to stock removes any trace of root, IIRC.
Sent from my Moto Z2 Force using XDA Labs
Don't forget, if you followed the flashing instructions from the other post they were omitting the gpt.bin and bootloader. So if you didn't flash those then that's why you're probably not seeing any updates, you need to be on full stock all matched up. Just reflash the firmware you downloaded in its entirety. @fast69mopar is right, once you flash a new boot.img root is gone, and since you flashed back to stock it's definitely gone.
Sparkzz27 said:
Thank you for the reply. I figured it out and went ahead with it. But now, I'm not seeing the May security update. The device shows it has March update and that no other update is available. Any idea why? Also, root checker still says 'root not properly installed'. How to unroot completely? Thanks a lot!
Click to expand...
Click to collapse
If you flash with factory image you should be unroot completely and root checker will keep telling you "root not properly installed" if you are not rooted just ignore root checker if you not planning to be rooted.
Hi there I have a xt1789-06 I was not getting updates and flashed the first Oreo update from here https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/
My phone now does the updates and everything works fine.
However I did try to flash a custom ROM and root I made a mistake and ended up both a hard brick, because I was on Oreo I thought that flashing the Oreo blank flash would rectify the problem, but it was not working so I tried flashing the N blank flash and it worked.
I've come from using Samsung phones so I'm use to Odin and have not used fastboot commands. After reading many threads I know what I had done was not decrypting my device which ended up with a hard brick I will in the future flash a custom ROM now I know a little bit more.
Blank flash files are here
https://mirrors.lolinet.com/firmware/moto/nash/blankflash/
Then once back to fastboot flash the flash all from the link at the top of my post.
41rw4lk said:
Don't forget, if you followed the flashing instructions from the other post they were omitting the gpt.bin and bootloader. So if you didn't flash those then that's why you're probably not seeing any updates, you need to be on full stock all matched up. Just reflash the firmware you downloaded in its entirety. @fast69mopar is right, once you flash a new boot.img root is gone, and since you flashed back to stock it's definitely gone.
Click to expand...
Click to collapse
Hi, sorry I was busy with work. I managed to use my phone that way. I didn't use the instructions in that post. Instead, I download flashallutilities (In how to return to stock post in xda for z2 force), then ran the batch file which did all the work. I noticed other problems too,
1. My Jio sim(4g LTE) does not show 'enhanced LTE mode' in options. Also when I call someone, it fails immediately saying 'call failed. try another method.' However, internet connection works from the sim. My other sim works fine for calls and data.
2. I'm seeing other keyboards in manage keyboards section. I don't recall seeing google pinyin input, zhuyin input, etc before. What's worse is my office's app shows option to switch to chinese version of the website for logging in. My language and time zone are set correctly though - English India and GMT +5:30.
3. The web browser I used before couldn't be found in the play store anymore. My launcher still shows the icon with a green arrow in left bottom of the icon to direct me to playstore to download it but playstore says item not found. The app name is simply 'browser'. I searched for it on desktop website too (without logging in), still couldn't find it. Guess it's a coincidence,
Also: Herehttps://www.getdroidtips.com/moto-z2-z2-play-z2-force-stock-rom/#Moto_Z2_Force_Android_80_Oreo_Firmware, the carrier global version says 'OCX' instead of 'OPX'. Any idead about that?
Sparkzz27 said:
Hi, sorry I was busy with work. I managed to use my phone that way. I didn't use the instructions in that post. Instead, I download flashallutilities (In how to return to stock post in xda for z2 force), then ran the batch file which did all the work. I noticed other problems too,
1. My Jio sim(4g LTE) does not show 'enhanced LTE mode' in options. Also when I call someone, it fails immediately saying 'call failed. try another method.' However, internet connection works from the sim. My other sim works fine for calls and data.
2. I'm seeing other keyboards in manage keyboards section. I don't recall seeing google pinyin input, zhuyin input, etc before. What's worse is my office's app shows option to switch to chinese version of the website for logging in. My language and time zone are set correctly though - English India and GMT +5:30.
3. The web browser I used before couldn't be found in the play store anymore. My launcher still shows the icon with a green arrow in left bottom of the icon to direct me to playstore to download it but playstore says item not found. The app name is simply 'browser'. I searched for it on desktop website too (without logging in), still couldn't find it. Guess it's a coincidence,
Also: Herehttps://www.getdroidtips.com/moto-z2-z2-play-z2-force-stock-rom/#Moto_Z2_Force_Android_80_Oreo_Firmware, the carrier global version says 'OCX' instead of 'OPX'. Any idead about that?
Click to expand...
Click to collapse
Your Z2 is a xt1789-06 correct? It's an international version, the flashall in the utilities zip from the return to stock thread is for US based phones, TMO and Sprint specifically. What was or wasn't flashed using that flashall I couldn't tell you, I don't have an international phone. That's why I linked to the post that deals with that version of the Z2 and has all the answers and links you need to sort your phone. Others in that thread might be better suited to help you along. This is the thread that deals with the xt1789-06.
As for calling and sim, might be related to how you flashed or simply an apn issue. You can go to network settings, mobile, access point names, and reset those to default. That should pull the apns from your sim so you'll have the correct apns.
As for keyboards and browsers, I don't know what is included in the international stock versions, but they are subject to change based on initial setup/default language and rom version. As for the OCX vs OPX, I'm not sure what the difference is. I know 'O' is for Oreo but for the rest I don't know. Maybe one is gsm one is cdma? I don't know. I do know that the thread I linked to will have more info and be able to help you better since it's for your version of the Z2. Sorry I can't help you more, but post any questions you have over there and they should be able to sort you out.