hi all, i have installed latest firmware (I9195XXUBML1) with Knox but i don't I can not root my 9195LTE
I performed all the steps in the first page but nothing to do ... supersu goes in a loop: asks to update but does not update ..
someone has performed root of I9195XXUBML1 ?
thank you vety much !!
RightClick said:
hi all, i have installed latest firmware (I9195XXUBML1) with Knox but i don't I can not root my 9195LTE
I performed all the steps in the first page but nothing to do ... supersu goes in a loop: asks to update but does not update ..
someone has performed root of I9195XXUBML1 ?
thank you vety much !!
Click to expand...
Click to collapse
KNOX void flag is still tampered!
- delete the old su app, or reflash the stock fw
- get CWM recovery
download this:
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip?retrieve_file=1
reboot into recovery(CWM) and flash it
reboot and start the new superSU app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it will ask (something similar) "KNOX detected do you want to disable?" press yes
now you get root acces
KNOX disable is temporary if you don't dele all knox app from system
regards
j.
RightClick said:
hi all, i have installed latest firmware (I9195XXUBML1) with Knox but i don't I can not root my 9195LTE
I performed all the steps in the first page but nothing to do ... supersu goes in a loop: asks to update but does not update ..
someone has performed root of I9195XXUBML1 ?
thank you vety much !!
Click to expand...
Click to collapse
hi
look here http://forum.xda-developers.com/showthread.php?t=2513740
jodge said:
KNOX void flag is still tampered!
- delete the old su app, or reflash the stock fw
- get CWM recovery
download this:
reboot into recovery(CWM) and flash it
reboot and start the new superSU app
it will ask (something similar) "KNOX detected do you want to disable?" press yes
now you get root acces
KNOX disable is temporary if you don't dele all knox app from system
regards
j.
Click to expand...
Click to collapse
so, in the end, I have to delete the apk 3 of knox...
ok. im back to stock I9195XXUBML1 and i try to flash SuperSU from sd by recovery...
let's see if it works
many thanks
Related
Hi,
I checked many articles on xda about it, but still nothing-
Problem is - when I check root perm. (root checker) it;s say me - cong. your phone have a root perm; ok, but when I want to update binaries via superuser of super su, it's going ok, but then : getting root permission - failure.
Whats there going on, have I to unlock bootloader, than root again?
It's update after OTA
stock: 4.2.2 / 4.18.401.2
kern: 3,1.10-g7f360be
superCID, S-Off
Thanks
elpapagayo said:
Hi,
I checked many articles on xda about it, but still nothing-
Problem is - when I check root perm. (root checker) it;s say me - cong. your phone have a root perm; ok, but when I want to update binaries via superuser of super su, it's going ok, but then : getting root permission - failure.
Whats there going on, have I to unlock bootloader, than root again?
It's update after OTA
stock: 4.2.2 / 4.18.401.2
kern: 3,1.10-g7f360be
superCID, S-Off
Thanks
Click to expand...
Click to collapse
OTA Kills ROOT...
You will have to uninstall supersu and flash it again using a custom recovery...
desmond1303 said:
OTA Kills ROOT...
You will have to uninstall supersu and flash it again using a custom recovery...
Click to expand...
Click to collapse
Thanks
I dont want to make new thread, therefore I write here;
after rooting - I can't pull down status bar ; I've cleared cache, dalvik , factory reset, still the same.. anybody can help?...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just received a S4 Mini i9195 and still unsure of the best method to root and install a custom recovery having read several threads.
Currently:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any advice?
Thank you :good::cyclops:
Use Kingo root app. Far easiest method.
I'm assuming you do not have a KNOX firmware installed so that's great for you - do NOT perform any software updates from Samsung!
The best method is still using the original method. Remember to flash the kernel if you are staying with the Samsung rom after the root.
http://forum.xda-developers.com/showthread.php?t=2364980
Or if you do not feel up to the slightly more technical challenge then you can use the app as mentioned above
Whosat said:
I'm assuming you do not have a KNOX firmware installed so that's great for you - do NOT perform any software updates from Samsung!
The best method is still using the original method. Remember to flash the kernel if you are staying with the Samsung rom after the root.
http://forum.xda-developers.com/showthread.php?t=2364980
Or if you do not feel up to the slightly more technical challenge then you can use the app as mentioned above
Click to expand...
Click to collapse
How do I check if KNOX firmware is installed?
Boot into download mode.
If there is a line that shows KNOX in it while in download mode then you have a KNOX firmware.
Whosat said:
Boot into download mode.
If there is a line that shows KNOX in it while in download mode then you have a KNOX firmware.
Click to expand...
Click to collapse
Great, there is no KNOX! :cyclops::good:
Is there a way to flash newer official firmware without including KNOX any other precautions I should take before rooting and flashing a custom recovery?
Kind Regards
smsmasters said:
Great, there is no KNOX! :cyclops::good:
Is there a way to flash newer official firmware without including KNOX any other precautions I should take before rooting and flashing a custom recovery?
Kind Regards
Click to expand...
Click to collapse
Yes u can flash newer firmware and don`t include Knox bootloader
Read this guide : http://forum.xda-developers.com/showthread.php?t=2549357
Thank you all for the help!
If I ever flashed firmware with KNOX, does it mean I can never remove KNOX?
For now - yes
..
I have a Samsung Galaxy S III that is an SPH-L710. It is currently not activated. I am rooting using the CF-Auto-Root method:
This isn't my first time rooting an S III, but this is the first time that I ran into this problem.
What I did:
1) Factory Reset the phone.
2) Rooted using Odin and CF-Auto-Root. Odin says Pass!
3) SuperSU is not installed.
4) Installed Root Checker and it says that the device is not rooted.
5) Install SuperSU through the Play Store and states that there is not a SU binary installed.
I have tried to push it through multiple times, with and without USB Debugging, and still the same issue. Also when I try to enter the Boot Recovery Menu I get CF-Auto-Root going through again.
Thank you in advance.
spry7 said:
I have a Samsung Galaxy S III that is an SPH-L710. It is currently not activated. I am rooting using the CF-Auto-Root method:
This isn't my first time rooting an S III, but this is the first time that I ran into this problem.
What I did:
1) Factory Reset the phone.
2) Rooted using Odin and CF-Auto-Root. Odin says Pass!
3) SuperSU is not installed.
4) Installed Root Checker and it says that the device is not rooted.
5) Install SuperSU through the Play Store and states that there is not a SU binary installed.
I have tried to push it through multiple times, with and without USB Debugging, and still the same issue. Also when I try to enter the Boot Recovery Menu I get CF-Auto-Root going through again.
Thank you in advance.
Click to expand...
Click to collapse
Look for SuperSu zip file and save it 2 yer SDcard and flash SUPER as zip file n see if that helps
Or you can install Philz Recovery, it has a Root Injector in Philz Settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please can someone tell me why this's happening ? Everything is going fine i installed Twrp recovery
twrp-3.0.2-0-hima.img and SuperSu SR2-SuperSU-v2.79-SR2-20170103215521 and everything installed fine, when it say reboot system i press reboot after that the phone keeps looping more than 20 times it won't work any idea ? software is marshmallow 6.0 Unlocked Bootloader.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AssyrianHero said:
Please can someone tell me why this's happening ? Everything is going fine i installed Twrp recovery
twrp-3.0.2-0-hima.img and SuperSu SR2-SuperSU-v2.79-SR2-20170103215521 and everything installed fine, when it say reboot system i press reboot after that the phone keeps looping more than 20 times it won't work any idea ? software is marshmallow 6.0 Unlocked Bootloader.
Click to expand...
Click to collapse
Hello,
I will move your thread to the correct section, where experts might be able to assist you.
Regards
Vatsal,
Forum Moderator.
Vatsal said:
Hello,
I will move your thread to the correct section, where experts might be able to assist you.
Regards
Vatsal,
Forum Moderator.
Click to expand...
Click to collapse
Thanks dude!
AssyrianHero said:
Please can someone tell me why this's happening ? Everything is going fine i installed Twrp recovery
twrp-3.0.2-0-hima.img and SuperSu SR2-SuperSU-v2.79-SR2-20170103215521 and everything installed fine, when it say reboot system i press reboot after that the phone keeps looping more than 20 times it won't work any idea ? software is marshmallow 6.0 Unlocked Bootloader.
Click to expand...
Click to collapse
The M9 is very finicky about SuperSU. The only two that can be reliably flashed are v2.65 and v2.79 SR1 - it looks like SR2 is what you flashed and why you're having issues.
I recommend uninstalling SuperSU ([EDIT]I'm not sure this is actually possible or necessary, please pardon my confusion[EDIT]) and then downloading & flashing 2.65 or 2.79 SR1. Once you've flashed either (I'd go with 2.79 SR1 personally), you can update the binary via the SuperSU app from within Android. The stickied HTC M9 readme thread's 4th post has links to the SuperSU install files you'll want.
Hi all, I have rooted my pixel 6 pro since day 1 and always used the magisk way of patching and restoring images for updates, since the February update Google tells me updates are no longer supported on my device per screenshots, anyone else had this issue and know how to resolve it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You might want to backup, uninstall magisk in the app, reboot. Then full reset/wipe and reboot. Then manually update to the latest May 2022 version using adb or the android flash tool. Something has gone awry with your software. Better to be safe than sorry.
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Gytole said:
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Click to expand...
Click to collapse
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
zamarax said:
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
Click to expand...
Click to collapse
Nope! Quite the opposite if I get stuck in a bootloop I just use the flash tool to fix it. No loss of data, but you need to re-boot the magisk boot image then reflash in magisk afterwards as it will completely remove magisk
So I did what you suggested and now my device is stuck in a boot loop with corrupt data, I did however patch the boot.img previously when I tried to send it to the device via ADB so I'm going to try to push that now and see what happens. Here are the options I selected for Android Flash Tool.
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
zamarax said:
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
View attachment 5608917
Click to expand...
Click to collapse