Related
Hi all,
Just updated my S4 firmware via odin and now have all sorts of issues, SuperuserSU keeps telling me there is no Superuser binary installed and SuperuserSU can't install it, have tried numerous times re installing SuperuserSU with no luck at all, any suggestions?
Also I keep getting a system message saying "Prevention Information" SuperuserSU has been forced to stop for unauthoriszed attempt to acces system in your device.
Seems this new S4 firmware is a pain in the a**... Some help would be nice folks
germinus said:
Hi all,
Just updated my S4 firmware via odin and now have all sorts of issues, SuperuserSU keeps telling me there is no Superuser binary installed and SuperuserSU can't install it, have tried numerous times re installing SuperuserSU with no luck at all, any suggestions?
Also I keep getting a system message saying "Prevention Information" SuperuserSU has been forced to stop for unauthoriszed attempt to acces system in your device.
Seems this new S4 firmware is a pain in the a**... Some help would be nice folks
Click to expand...
Click to collapse
If it's rooted try to uninstall Superuser and reinstall, if it doesn't work maybe you flashed a broken update?
BillvanHalen said:
If it's rooted try to uninstall Superuser and reinstall, if it doesn't work maybe you flashed a broken update?
Click to expand...
Click to collapse
I have the same issue since the last update from Samsung and the update is not broken. I guess more that the problem is a not 100% working root on this new firmwares like MH5, MH8 and so on. I also installed the officel version from Samsung (MH%, MH( etc.) and with all versions i got the same problems. Root do not work 100% in all cases and at the beginning i also could not use su correct.
Could it be that Samsung made a strange step forward to kick us out of the system and that root maybe will be not so easy as in the past!?!? Apple say hello at Samsung or what
Greetings
s0uli
s0uli said:
I have the same issue since the last update from Samsung and the update is not broken. I guess more that the problem is a not 100% working root on this new firmwares like MH5, MH8 and so on. I also installed the officel version from Samsung (MH%, MH( etc.) and with all versions i got the same problems. Root do not work 100% in all cases and at the beginning i also could not use su correct.
Could it be that Samsung made a strange step forward to kick us out of the system and that root maybe will be not so easy as in the past!?!? Apple say hello at Samsung or what
Greetings
s0uli
Click to expand...
Click to collapse
I got root working via cf auto root, however I can not seem to create a "virtual device" so I am going to flash a new rom and see if that helps, if not then I will be going back to an older version of the firmware!
germinus said:
I got root working via cf auto root, however I can not seem to create a "virtual device" so I am going to flash a new rom and see if that helps, if not then I will be going back to an older version of the firmware!
Click to expand...
Click to collapse
not if you have the new bootloader you won't... You can't go to firmwares lower than the one which has the new bootloader. You are stuck with a large amount of people who also updated and now regret it...
ultramag69 said:
not if you have the new bootloader you won't... You can't go to firmwares lower than the one which has the new bootloader. You are stuck with a large amount of people who also updated and now regret it...
Click to expand...
Click to collapse
Well I have just flashed an old ROM and all is good now
germinus said:
Well I have just flashed an old ROM and all is good now
Click to expand...
Click to collapse
Please let me knolw which ROM you have installed because all my trys to go back to a older ROM ends in no sound or other bad troubles.
Thx
souli
germinus said:
Well I have just flashed an old ROM and all is good now
Click to expand...
Click to collapse
Did the rom you flash have the new bootloader?
There have been a few released without KNOX or the bootloader and if you havern't actually upgraded the stock firmware you can go back to old firmwares...
ultramag69 said:
Did the rom you flash have the new bootloader?
There have been a few released without KNOX or the bootloader and if you havern't actually upgraded the stock firmware you can go back to old firmwares...
Click to expand...
Click to collapse
It was the latest Omega rom.
germinus said:
It was the latest Omega rom.
Click to expand...
Click to collapse
Yep, no new bootloader in that rom. If you had flashed the stock MI1 rom then it would have the new bootloader and you wouldn't be going to a lower firmware... It also has KNOX disabled or completely removed.
As for anyone who has upgraded the STOCK firmware to MI1 or MH8 then you can't downgrade the firmware by flashing through ODIN or CWM...
Sorry if this is a newbie question, but if I root my Galaxy Note 3 (N9005, Vodafone Australia), will it still get OTA updates?
I ask because I used to have a HTC Desire HD, and after rooting and installing Cyanogenmod, I tried to put the Nandroid backup of the stock rom back on, which was fine but for some reason wouldn't install the OTA updates. It would tell me there was an update and download it, but would fail to install.
Thanks!
gnoted said:
Sorry if this is a newbie question, but if I root my Galaxy Note 3 (N9005, Vodafone Australia), will it still get OTA updates?
I ask because I used to have a HTC Desire HD, and after rooting and installing Cyanogenmod, I tried to put the Nandroid backup of the stock rom back on, which was fine but for some reason wouldn't install the OTA updates. It would tell me there was an update and download it, but would fail to install.
Thanks!
Click to expand...
Click to collapse
I think no.It may receive,but it'd fail to install.
GamingDj said:
I think no.It may receive,but it'd fail to install.
Click to expand...
Click to collapse
If it does install you will loose root... But I believe if the system is found to be custom in any way it will fail on install of OTA or will actually tell you that the phone has been modified and no updates available for you
ultramag69 said:
If it does install you will loose root... But I believe if the system is found to be custom in any way it will fail on install of OTA or will actually tell you that the phone has been modified and no updates available for you
Click to expand...
Click to collapse
Thanks for the reply. Just out of curiosity about the HTC Desire HD that has since been given to a less tech-savvy relative, is there a way to unroot so the OTA update will work??
I rooted my N3 3 days after buying and then tried to get an OTA update. It didn't download first, as my phone was set to custom. After using Wanam's setting to "reset" the custom status, I could download the OTA update but couldn't install it.
Basically, with root you can still check if there's an official update available, but you can't install.
Mikegrmn said:
I rooted my N3 3 days after buying and then tried to get an OTA update. It didn't download first, as my phone was set to custom. After using Wanam's setting to "reset" the custom status, I could download the OTA update but couldn't install it.
Basically, with root you can still check if there's an official update available, but you can't install.
Click to expand...
Click to collapse
Anyone know how it actually tells if the phone has been rooted? Surely there's a way to reset it to unrooted/non-custom state so OTA updates work again...
gnoted said:
Anyone know how it actually tells if the phone has been rooted? Surely there's a way to reset it to unrooted/non-custom state so OTA updates work again...
Click to expand...
Click to collapse
The boot loader and the os itself scan for certain things such as modified kernel/recovery or installation of busy box.
The Samsung's aren't so bad, you can just flash back the stock rom and factory reset to start getting ota updates again. On htc phones you have to unlock the boot loader to root and its a one way process. Once unlocked you can never get ota updates again.
Sent from my SM-N9005
i have the same problem here, i would like to update MK2 but i cant.
used wanam exposed for fake > failed @ installation.
do i have to unroot or factory reset for update?
i dont want to install a cwm at the moment.
thx
Once you have rooted, the system partition has been modified so Samsung doesnot allow you to OTA update. It checks MD5hash for the consistency. Factory reset doesn't help because it only format userdata partition.
If you r rooted, better go to sammobile.com, download the latest firmware version, copy it to sdcard and flash via Mobile Odin Pro. This way you can keep the old bootloader so you can fallback (downgrade) to the older firmware later.
Thank you.
what is when i tripped the knox count?
Its 0x1 now. I was on new bootloader before.
Gesendet von meinem SM-N9005 mit Tapatalk 2
gnoted said:
Sorry if this is a newbie question, but if I root my Galaxy Note 3 (N9005, Vodafone Australia), will it still get OTA updates?
I ask because I used to have a HTC Desire HD, and after rooting and installing Cyanogenmod, I tried to put the Nandroid backup of the stock rom back on, which was fine but for some reason wouldn't install the OTA updates. It would tell me there was an update and download it, but would fail to install.
Thanks!
Click to expand...
Click to collapse
OTA update works on rooted note 3. My Note 3 rooted and just yesterday it OTA update to MK2.
and see this http://forum.xda-developers.com/showthread.php?t=2519103
chemcup said:
OTA update works on rooted note 3. My Note 3 rooted and just yesterday it OTA update to MK2.
and see this http://forum.xda-developers.com/showthread.php?t=2519103
Click to expand...
Click to collapse
I have tried the steps mentioned in that thread but it still wont let me OTA update.
Ive faked official status with wanam and still nothing.
vinokirk said:
I have tried the steps mentioned in that thread but it still wont let me OTA update.
Ive faked official status with wanam and still nothing.
Click to expand...
Click to collapse
Ok you have to downlaod the original stock rom and flash with odin.
After that root it again. Everything fine now. knox trigger 0x1 at the moment.
BUFUMAN said:
Ok you have to downlaod the original stock rom and flash with odin.
After that root it again. Everything fine now. knox trigger 0x1 at the moment.
Click to expand...
Click to collapse
I need to keep Knox at 0x0.
There must be a way of updating.
A couple of people have mentioned downloading from SamMobile and flashing back to stock. If I do this, what happens to twrp?
If twrp stays, I don't want it conflicting with a non-rooted phone (due to flashing stock) and being bricked
U can get upgrade with kiss not OTA but u must install wanamp exposed n change system into official. Its work on rooted stock rom.
Sent from my SM-N9005 using XDA Premium 4 mobile app
The why
A lot of this has been said in other threads, however I decided to gather all the up-to-date (as of Jun 17, 2014) instructions and info in this thread to alleviate fears of the infamous 'KNOX WARRANTY VOID 0x1' and help people with the process. People with tripped KNOX can of course use this as well, however it won't untrip their devices, duh.
The cheers
First of all big cheers for Pinkie Pie (person who discovered the Linux kernel vulnerability that makes rooting without tripping KNOX possible), geohot (person that used the vulnerability to make a rooting app), chainfire (developer of SuperSU), rovo89 and Tungstwenty (developers of Xposed). Go and donate to these guys if you can!
The what
This post will tell you how to upgrade your P605 to 4.4.2, if you haven't already. And how to install SuperSU and Xposed all the while keeping your KNOX counter at 0x0, CURRENT BINARY: Samsung Official and SYSTEM STATUS: Official!
Note: The versions in this text are just for reference - telling you what versions already worked. New ones will surely also work, so you should usually download the newest available.
The how
Firmware
4.4.2 NEE P605XXUCNE2 (any of the current 4.4.2 firmwares should be fine, although Samsung might use an updated kernel for the future versions, disabling towelroot)
From http://forum.xda-developers.com/showpost.php?p=53092676&postcount=1
Simple instructions available here http://www.sammobile.com/firmwares/3/?download=30325 (you can also download the firmware from here, but download is slow for free accounts)
Root
From http://towelroot.com
No special instructions (it's a 1-click root)
SuperSU
Version 1.99.rc5 from http://download.chainfire.eu/448/SuperSU/
Extract Superuser.apk (in 'common') from the zip, install and run
Answer yes to the Disable KNOX prompt (don't worry, KNOX will not be tripped)
Xposed
From http://repo.xposed.info/module/de.robv.android.xposed.installer (version 2.6.1)
No special instructions
The victory
Congrats! Now you should be on a rooted, SuperSUed, Xposed KitKat with warranty left intact! However before sending it to Samsung, e.g., for repairs, you should flash your original firmware, of course.
Can this be made to work with the SM-P600 on Android 4.3 unrooted? Any help will be appreciated. This would be a dream.
no.0ne said:
SuperSU
Version 1.94 from Google Play (Jun 17, 2014)
Answer yes to the Disable KNOX prompt (don't worry, KNOX will not be tripped)
At the end it will say it failed, however it will be working!
If you are annoyed by the 'failed' message for some reason, download an updated version from http://download.chainfire.eu/448/SuperSU/ (you'll have to flash it manually though) which supposedly fixes it.
Click to expand...
Click to collapse
Just Download specified zip and extract superuser.apk from common folder and install as normal program, don't download play version
İ am gonna try and write my appreciate ) thanks in advance
It did work . Thanks to you and that steps i have rooted kitkat knox is 0*0 what i was waiting for last 5 months. Thank you so much now i can use my tablet in full capacity
iPhone 'den Tapatalk aracılığı ile gönderildi
Eudeferrer said:
Can this be made to work with the SM-P600 on Android 4.3 unrooted? Any help will be appreciated. This would be a dream.
Click to expand...
Click to collapse
It seems that so far people have had no success using towelroot on P600. Wait and hope it will change...
Hello, i want to do this on clean tablet, so i want to do clean install , how can i clean it all had before, from odin? And is nee nordic kitkat rom suitable for all p605 , i am frightened about boatloader problem and soft brick before i done i wanted to ask. Thanks in advance.
yararli said:
Hello, i want to do this on clean tablet, so i want to do clean install , how can i clean it all had before, from odin? And is nee nordic kitkat rom suitable for all p605 , i am frightened about boatloader problem and soft brick before i done i wanted to ask. Thanks in advance.
Click to expand...
Click to collapse
You can wipe the tablet from recovery:
Turn tablet off
Turn it on holding Volume Up + Power Button until you see something on the screen
Wipe data/factory reset
Reboot
NEE will be fine for all P605, however I don't know if it works with something like P605V (US Verizon).
no.0ne said:
You can wipe the tablet from recovery:
Turn tablet off
Turn it on holding Volume Up + Power Button until you see something on the screen
Wipe data/factory reset
Reboot
NEE will be fine for all P605, however I don't know if it works with something like P605V (US Verizon).
Click to expand...
Click to collapse
Should i do this before or after kitkat installation ? And where can i find usb installation of p605 when it is taken into download mode for pc to recognize the tablet.
I have no windows pc now im gonna do that on thursday ı was waiting this topic for 4 months thank you so much
iPhone 'den Tapatalk aracılığı ile gönderildi
yararli said:
Should i do this before or after kitkat installation ? And where can i find usb installation of p605 when it is taken into download mode for pc to recognize the tablet.
I have no windows pc now im gonna do that on thursday ı was waiting this topic for 4 months thank you so much
iPhone 'den Tapatalk aracılığı ile gönderildi
Click to expand...
Click to collapse
First you wipe then you flash
You can download the driver from the Samsung website, e.g., http://www.samsung.com/us/support/owners/product/SM-P605VZKEVZW (don't worry that it is on the US page, the driver is the same for all Samsung devices)
Glad I can help. I waited for root quite long myself :victory:
In the thread discussing towelroot on P605, people claimed installing xposed would change your binary to custom. That's holding me back for now, can you confirm that it stays official?
Matthias.ja said:
In the thread discussing towelroot on P605, people claimed installing xposed would change your binary to custom. That's holding me back for now, can you confirm that it stays official?
Click to expand...
Click to collapse
It only makes it custom inside of the ROM. In download mode it shows Official. You can also use the Wanam xposed module to change it back to Official in the ROM.
valexi said:
It only makes it custom inside of the ROM. In download mode it shows Official. You can also use the Wanam xposed module to change it back to Official in the ROM.
Click to expand...
Click to collapse
alright, thanks!
so if i have some warranty issues, wiping everything from recovery or re-flashing the unrooted stock ROM would make everything official again, right? I know I sound like a scared little girl, but I just really don't want to risk my warranty on this rather expensive device
Heyy its wonderful i did it but there is a problem about kitkat rom i saw a little lags and the biggest problem is whatsapp says it is not compatible with this device also twitter in playstore what should i do thnx for your all help
iPhone 'den Tapatalk aracılığı ile gönderildi
valexi said:
It only makes it custom inside of the ROM. In download mode it shows Official. You can also use the Wanam xposed module to change it back to Official in the ROM.
Click to expand...
Click to collapse
So i just tried and installed xposed, and funnily enough, my system status stayed official, even inside the ROM. I won't complain though..
Hello i should restore system defaults how should i do directly by using recovery mode can i clean systam cache and ... Or before it should i unroot from su?
iPhone 'den Tapatalk aracılığı ile gönderildi
To make sure; unroot and then factory reset
Matthias.ja said:
So i just tried and installed xposed, and funnily enough, my system status stayed official, even inside the ROM. I won't complain though..
Click to expand...
Click to collapse
As long using stock recovery and it will stay Official. Just custom recovery will give custom.
dt33 said:
As long using stock recovery and it will stay Official. Just custom recovery will give custom.
Click to expand...
Click to collapse
No it doesn't. You dont seem to understand difference between "system status" in Download mode or inside of the ROM.
Here is couple of pictures to make you understand.
In the picture below you can see system status official. This will change, if you install CUSTOM ROM or CUSTOM RECOVERY. Towelroot does not change any of these data here:
In the picture below you can see Device status "custom". This can change to custom if you ROOT the device and/or install SuperSU or Xposed framework. This has NOTHING to do with the status in the Download mode as seen in the first picture.
I hope that people wouldn't mix these things, because they are rather easy to understand. Talking about things that you dont really understand will cause confusion and makes people asking more stupid questions.
Thank you!
valexi said:
No it doesn't. You dont seem to understand difference between "system status" in Download mode or inside of the ROM.
Here is couple of pictures to make you understand.
In the picture below you can see system status official. This will change, if you install CUSTOM ROM or CUSTOM RECOVERY. Towelroot does not change any of these data here:
In the picture below you can see Device status "custom". This can change to custom if you ROOT the device and/or install SuperSU or Xposed framework. This has NOTHING to do with the status in the Download mode as seen in the first picture.
I hope that people wouldn't mix these things, because they are rather easy to understand. Talking about things that you dont really understand will cause confusion and makes people asking more stupid questions.
Thank you!
Click to expand...
Click to collapse
Pls, explain how come it stays Official after rooted with towelroot, installed SuperSu and Xposed?
http://forum.xda-developers.com/showpost.php?p=53452193&postcount=33
dt33 said:
Pls, explain how come it stays Official after rooted with towelroot, installed SuperSu and Xposed?
http://forum.xda-developers.com/showpost.php?p=53452193&postcount=33
Click to expand...
Click to collapse
I'm not quite sure, but it seems that in some cases the ROM can detect if it's rooted.
For me it changed to "Custom" after rooting with towelroot and SuperSU installation. I changed it back to Official with Wanam xposed.
Hello everyone,
After getting my S5 yesterday one of the first things I did was try to root it via towelroot. Unfortunately it said phone not currently supported which is weird seeing as I found out it worked for others.
Anyway is it because I'm running too updated firmware or anything else of which I am not yet aware. If so I'd love to find out which version I need to flash and where I can find it. I also tried the automated towelroot with EasyRootToolkit(v12) and others but it got stuck on creating VM.
If anyone could help out I'll greatly appreciate it.
lyubor said:
Hello everyone,
After getting my S5 yesterday one of the first things I did was try to root it via towelroot. Unfortunately it said phone not currently supported which is weird seeing as I found out it worked for others.
Anyway is it because I'm running too updated firmware or anything else of which I am not yet aware. If so I'd love to find out which version I need to flash and where I can find it. I also tried the automated towelroot with EasyRootToolkit(v12) and others but it got stuck on creating VM.
If anyone could help out I'll greatly appreciate it.
Click to expand...
Click to collapse
If your firmware is ANGx Towelroot doesn`t work. Downgrade to an older version like ANE2 or follow this method http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044.
..
Sorry about that, I was trying to find out more general information before going into specifics.
Anyway, my model's information's below
Model: SM-G900F
Version: 4.4.2
Build: KOT49H.G900FXXU1ANG9
Kernel: 3.4.0 ~ Fri. Jul 25 2014
..
I have the same problem.
I purchased mine a few days ago, and the kernel is from August. The model is 901F. It doesn't look like there's any older version to download.
How can I root it?
HippyBob said:
I have the same problem.
I purchased mine a few days ago, and the kernel is from August. The model is 901F. It doesn't look like there's any older version to download.
How can I root it?
Click to expand...
Click to collapse
Maybe Towelroot will be updated to a newer version for the NGx kernels in the future, for now there is only CF Auto Root for root which will trip the KNOX void warranty flag. Check if the 901F is supported by CF Root first.
gee2012 said:
Maybe Toewlroot will be updated to a newer version for the NGx kernels in the future, for now there is only CF Auto Root for root which will trip the KNOX void warranty flag.
Click to expand...
Click to collapse
Ah I see. As long as I can use the phone with the rom of my choice, along with having root access, I don't need the Knox void warranty flag to be intact. I had a look around yesterday, and CF Auto root didn't support 901F iirc. Would it still be safe to try without bricking it?
Edit: Ah I see you edited your post. Will just have to wait I guess.
HippyBob said:
Ah I see. As long as I can use the phone with the rom of my choice, along with having root access, I don't need the Knox void warranty flag to be intact. I had a look around yesterday, and CF Auto root didn't support 901F iirc. Would it still be safe to try without bricking it?
Click to expand...
Click to collapse
I would wait on Chainfire for a file suited for your device, you can (soft) brick a phone with the wrong file. You could also Google around for a compatible custom recovery for your device and then flash the latest superSU.zip file for your device to get root.
..
fffft said:
You didn't look very hard. There are firmware builds going back to May.
Use Odin to write an older firmware version, then Towel root will prevail.
.
Click to expand...
Click to collapse
Well I searched for firmwares for 901F. I found ones for other models such as 900F. Would I be able to use a 900F firmware on a 901F model?
..
fffft said:
You attached your post to a thread discussing the 900F and Towel root. Instead of hijacking someone else's thread, you should start your own. Particularly because you have a different, derivative model further confusing the subject under discussion.
The 900F has firmwares dating back to May. Your 901F doesn't. An extended search is your best option. As a very recent model and running 4.4.4 as well as a new kernel build you will have to see what exploits are found for your device. You might want to post some information in the CF-Autoroot thread to see if your device can be accommodated. Or you can wait it out and see what Chainfire, Geohot, et al can do with your model.
.
.
Click to expand...
Click to collapse
Ah sorry, just didn't want to add more threads when the subject would be pretty much the same. Will create one next time. I will play the waiting game and just endure TouchWiz.
HippyBob said:
Ah sorry, just didn't want to add more threads when the subject would be pretty much the same. Will create one next time. I will play the waiting game and just endure TouchWiz.
Click to expand...
Click to collapse
Or install Nova, Apex or any other launcher and a different icon pack from Play and turn off apps/widgets you don`t use
Hi,
I had very same problem with GS3. I solved problem with a Windows based Kingo ROOT software. No need ti downgrade etc. Everything went so smoothly and easy.
I've tried just about every major root app, various versions of Odin, ADB won't flash TWRP.... I've tried everything. This is my firmware version: g950usqs7dtb1. I realize it's a binary 7 because I've never had the option to turn off the auto software update. Am I screwed with a binary 7 firmware for a while?
Also, another question: I installed a combination file, and had to frantically search to get my firmware package back. Eventually found it on some semi-shady site, and had to pay about ten bucks for it. Is it possible for it to have a trojan? Some things are not working correctly, like I can't get my weather app to recognize the GPS and the swiftkey can't download a language pack.
Edit: Forgot to mention, ATT is the carrier. Not sure if that matters. Also, any help would be so much appreciated. Thanks in advance.
See my other posts. Locked bootloader no twrp for you
TheMadScientist said:
See my other posts. Locked bootloader no twrp for you
Click to expand...
Click to collapse
Ok, I appreciate your help. Are you saying I need to flash other firmware which will remove the locked bootloader? The trouble is I have to flash binary 7 firmware and that's hard to find. Or are you saying I'm just screwed? Please tell me clearly. Sorry man, I'm pretty new to all this.
uberdad said:
Ok, I appreciate your help. Are you saying I need to flash other firmware which will remove the locked bootloader? The trouble is I have to flash binary 7 firmware and that's hard to find. Or are you saying I'm just screwed? Please tell me clearly. Sorry man, I'm pretty new to all this.
Click to expand...
Click to collapse
You are screwed. If you look in the syndicate thread below. You can root 7.0 on bit 7. But as for custom ROMs,kernels. Actual twrp your screwed. This devices bootloader is permanently locked and is not unlockable
You can gain SU based system only root. To add things live viper for android. Some system debloat. But that is it. You are also limited to nougat. No root for oreo or pie. No los based ROMs if you are looking for custom you need a F model or a different device.
TheMadScientist said:
You are screwed. If you look in the syndicate thread below. You can root 7.0 on bit 7. But as for custom ROMs,kernels. Actual twrp your screwed. This devices bootloader is permanently locked and is not unlockable
You can gain SU based system only root. To add things live viper for android. Some system debloat. But that is it. You are also limited to nougat. No root for oreo or pie. No los based ROMs if you are looking for custom you need a F model or a different device.
Click to expand...
Click to collapse
Wow, that sucks. Thanks for the feedback.