Hello
This my very first post on XDA so be gentle.
Question is I created a pre rooted SGP611_23.1.A.0.690 with PRFCreator flashed it and everything went fine but I am unable to get any write access to root even though its stating its rooted I cant seem to install apps like busybox etc.
My first through was RicDefeat so I tried it all again and this time tried flashing RicDefeat but when I try to flash I get errors, had no problem flashing under Kitkat.
Is there anything i am doing wrong?
My bootloaders locked atm, I can unlock if necessary I have backed up my DRM keys.
Any help would be greatly appreciated.
Im on the same boat as you. So any help would be apreciated.
Use my RICDefeat from here and run it from terminal. Works only if you are rooted. Afterwards you should have r/w access.
lowtraxx said:
Use my RICDefeat from here and run it from terminal. Works only if you are rooted. Afterwards you should have r/w access.
Click to expand...
Click to collapse
It Worked I love you xxxxxx no homo!
Related
Do we know a root procedure that will work after the 4.3 update?
I too am curious to know!
Just root? The old way works. If you want full R/W access to the system folders then as far as I know thats not working right without a customer kernel.
Shane_pcs said:
Just root? The old way works. If you want full R/W access to the system folders then as far as I know thats not working right without a customer kernel.
Click to expand...
Click to collapse
Does it matter if mine is s-off?
Alright, I got mine rooted with no problems.
Just install TWRP, CWM, or CM2 for the recovery and then install SuperSU to get the root.
If you do TWRP like I did, when you go to reboot the system for the first time, it will say that you aren't rooted and ask if you want to run SuperSU to root. Pretty straight forward.
Hi folks,
Ive been having a strange problem with a couple Galaxy Mega I9200. I have rooted both before without any problems using KINGO originally. The i decided to update both of them with version UBUCNA2. When i tried to re root them back, even though the process have run fine a couple times the phone is not rooting. At this point i dont know what else to do to try to root those phones. I have tried every single method around this forum i think not just KINGO this time. And have not been able to reach root the way it should. Titanium backup shows not able to aquire root priviledges, and other root apps also. Can someone please help me on this?? Keep in mind im not a newbie so dont give me the recovery method advice without something new or to use KINGO because ive have done that already. Thanks a lot guys
You upgraded your phones to the latest knox enabled firmware which has the knox bootloader. You cannot go back to an older firmware or flash a custom rom now.
To root, try the directions provided in this thread and use the melius3gxx files instead of meliusltexx.
Silesh.Nair said:
You upgraded your phones to the latest knox enabled firmware which has the knox bootloader. You cannot go back to an older firmware or flash a custom rom now.
To root, try the directions provided in this thread and use the melius3gxx files instead of meliusltexx.
Click to expand...
Click to collapse
Ok thanks, the phones already had the knox apk so my guess was that it was going to be the same thing. Thanks for clarifying that one. And thanks for the advice.
Thanks again, turns out the only thing that is failling root access is when i try to unlock the phone via box. For some reason when its checking for SU access it fails. But thanks anyway i managed to solve the Root problem.
root.
I rooted through Phill touch Recovery.
I'm trying to get use out of this aging tablet. I figured there aren't going to be any updates coming so I would finally like to root the device. However, everything I've read and tried is outdated and hasn't worked. I was wondering if someone could help me root my device. I'm not looking to run any ROM or anything. I'd just like to have root and superuser access so I can uninstall a lot of unwanted apps. Below is my device information. I've just recently done a factory reset and have not installed any drivers on my computer. Starting fresh.
Computer:
- Windows 7 64-bit
Tablet:
- Android Version: 4.1.1
- Build number: 10.4.2.18
Any help would be greatly appreciated.
foster016 said:
I'm trying to get use out of this aging tablet. I figured there aren't going to be any updates coming so I would finally like to root the device. However, everything I've read and tried is outdated and hasn't worked. I was wondering if someone could help me root my device. I'm not looking to run any ROM or anything. I'd just like to have root and superuser access so I can uninstall a lot of unwanted apps. Below is my device information. I've just recently done a factory reset and have not installed any drivers on my computer. Starting fresh.
Computer:
- Windows 7 64-bit
Tablet:
- Android Version: 4.1.1
- Build number: 10.4.2.18
Any help would be greatly appreciated.
Click to expand...
Click to collapse
There is a one-click solution to root that should work on your device if that is all you want to do:
http://forum.xda-developers.com/showthread.php?t=2228613
If you will have some problem send massage I will help you
Restorer said:
There is a one-click solution to root that should work on your device if that is all you want to do:
http://forum.xda-developers.com/showthread.php?t=2228613
Click to expand...
Click to collapse
I tried using Kingo. While the program said it rooted the device, I didn't have root access when I checked the app Root Checker and Titanium Back-up to uninstall all the unwanted apps.
foster016 said:
I tried using Kingo. While the program said it rooted the device, I didn't have root access when I checked the app Root Checker and Titanium Back-up to uninstall all the unwanted apps.
Click to expand...
Click to collapse
Is your device unlocked? If you're not and you don't have any warranty, try unlocking it first then use kingo. It's what I used on several TF201 with no problem, but they were all unlocked so I don't know if being locked would cause the problem.
shatterstar78 said:
Is your device unlocked? If you're not and you don't have any warranty, try unlocking it first then use kingo. It's what I used on several TF201 with no problem, but they were all unlocked so I don't know if being locked would cause the problem.
Click to expand...
Click to collapse
My device is NOT unlocked. How do I go about unlocking it? After I do so, I'll give Kingo another try.
You can disregard! I tried Kingo again, without unlocking, and for some reason it worked this time! I am currently uninstalling all the bloatware. Thank you all for your help.
Hey Guy n Gals need some help, to make a long story short Im on Sony Z Ultra C6806 on KitKat 4.4.4. .108
So I rooted via:
http://forum.xda-developers.com/showthread.php?t=2784900
During the process I was having some trouble getting the program to work, finally it went trough the steps and said it failed, however root checker showed root, and so I figured I would go ahead and instal Super Su, it attempted to update Su Binary and failed, rebooted and it seemed to be working, BUT I cant install Busy Box or Xposed, someone please help me on how to solve this.....thanks guys
Pics
well you need to flash a recovery for locked bootloader then reboot to system.
Now execute the superuser app again. When it prompts that you need to update superSU, choose CWM/TW...whatever its named that weird alien recovery thing. It will now if successfully granted, reboot to recovery and install the right files.
Or and if the above method did not work you can flash the latest from here http://download.chainfire.eu/396/SuperSU/
I did use this method on my dads Z1 and it worked great cause he is unwilling to unlock bootloader! However you can also try this tool below if you have no luck with the first rooting tool
link:
http://forum.xda-developers.com/showthread.php?t=1886460
edit: You need to enable adb root. I do not know where to find this in stock rom. But it has a huge point to stopping other apps for gaining superuser rights if this is disabled.
You can find this on aosp roms in the developer settings around the setting for usb debugging. It might be around the same area on sony stock rom?
In the SuperSU app there is an option in settings you can disable that is named something like "respect kitkat api". This can also help.
Thanks man for taking time out of your day to give me such a detailed response, it is users like yourself that truly make XDA work
HI,
I am unable to mount /system as r/w in root explorer or other apps. When they load it asks SpuerSU for permissions which are granted.
I am trying to install xposed installer which fails and asks (are you root?)
I originally rooted my Z2 when it was first released, then when the 4.4.4 update became available in the UK i restored stock recovery so i could update. When the Phone rebooted I found I still had root. I can get a # prompt in terminal emulator and apps like folder mount work fine.
Has something messed up somewhere? I tried reinstalling SuperSU to no avail.
Thanks
stubbadub said:
HI,
I am unable to mount /system as r/w in root explorer or other apps. When they load it asks SpuerSU for permissions which are granted.
I am trying to install xposed installer which fails and asks (are you root?)
I originally rooted my Z2 when it was first released, then when the 4.4.4 update became available in the UK i restored stock recovery so i could update. When the Phone rebooted I found I still had root. I can get a # prompt in terminal emulator and apps like folder mount work fine.
Has something messed up somewhere? I tried reinstalling SuperSU to no avail.
Thanks
Click to expand...
Click to collapse
Have you tried to downgrade to 4.4.3 and make a rooted flashable zip with 4.4.4??
Might work. Havent tried Root explorer, cuz FileCommander works fine with root...
bjorn96 said:
Have you tried to downgrade to 4.4.3 and make a rooted flashable zip with 4.4.4??
Might work. Havent tried Root explorer, cuz FileCommander works fine with root...
Click to expand...
Click to collapse
I have just run the Easyroot Tool again and this seems to have solved it. :good:
stubbadub said:
I have just run the Easyroot Tool again and this seems to have solved it. :good:
Click to expand...
Click to collapse
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
stonegroover said:
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
Click to expand...
Click to collapse
My bootloader came unlocked on the phone. I bought the phone when it was released. I rooted and when 4.4.4 firmware was released it initially failed to update OTA. I had to remove the dual recovery. The OTA then worked fine and i still had root. However i could not mount the /system folder as R/W/. I just ran easyroot again and this solved it.
stonegroover said:
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
Click to expand...
Click to collapse
NC not working happened to me too. But only in niaboc79's version (and by this I mean the Russian OTA). I also tried the OTA and all was good. But after that I lost my root and tried to restore it (I ran the restore-mount script). This script messed things up. Instead of looking into that, I tried different approaches (niaboc79's / .314+root+script) except check if it was because of the the script .
If you have root now, install the dualrecovery and dirty flash for example shockss pre-rooted .267 and run the script. Stock .267, everything working but pre-rooted. Ow and 4G icon = LTE icon.
stubbadub said:
I have just run the Easyroot Tool again and this seems to have solved it. :good:
Click to expand...
Click to collapse
Thank you, this method worked for me too !
Actually I couldn't run the whole Easyroot tool (got stuck at creating vm) so I just ran the important part which is where it pushes files/installmount.sh with
Code:
adb push files/installmount.sh /data/local/tmp
And then executes it with
Code:
adb shell "su -c /data/local/tmp/installmount.sh"
pec0ra said:
Thank you, this method worked for me too !
Actually I couldn't run the whole Easyroot tool (got stuck at creating vm) so I just ran the important part which is where it pushes files/installmount.sh with
Code:
adb push files/installmount.sh /data/local/tmp
And then executes it with
Code:
adb shell "su -c /data/local/tmp/installmount.sh"
Click to expand...
Click to collapse
Mine sticks at creating the VM too. So the code you've quoted is all you need? I opened up the .bat file to have a look and those lines of code are only 2 of many, and only around half way through the file- I'm looking at it thinking there's got to be more to it than that, it can't be that simple......
stonegroover said:
Mine sticks at creating the VM too. So the code you've quoted is all you need? I opened up the .bat file to have a look and those lines of code are only 2 of many, and only around half way through the file- I'm looking at it thinking there's got to be more to it than that, it can't be that simple......
Click to expand...
Click to collapse
If you only want to fix the system not mounting then yes, it's only this. The rest of the script is an exploit to gain root and install su but you don't need it since you already have it.
If you are looking for a full root method these two lines are not enough. In this case I suggest you try another rooting tool.
pec0ra said:
If you only want to fix the system not mounting then yes, it's only this. The rest of the script is an exploit to gain root and install su but you don't need it since you already have it.
If you are looking for a full root method these two lines are not enough. In this case I suggest you try another rooting tool.
Click to expand...
Click to collapse
I still have 'some root', my Adaway still works but it won't load new/updated hosts, BusyBoxPro won't install, etc. I tried what you did, just ran the two lines of code but it said I didn't have permission when I tried to run the second line. Did you get that error? If you did, how did you get past that?