I posted this in the wrong thread earlier... Apologies
I rooted my Z3v with Kingroot (I'm beginning to think that was a mistake). I seem to have "limited" root capabilities. I cannot install BusyBox because R/W permission fails. I run root checker and get positive results. Also, I cannot make any changes to the phone's root or install a recovery. Is there a way to fix this? If not, how do I start from the beginning and get rid of Kingroot in exchange for SU and a recovery?
Install SuperSU from play store and install it's binary, and uninstall all kingroot apps after and reboot phone. Done.
Binary won't install.
{
"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"
}
Sent from my D6708 using Tapatalk
Same exact issue
Hey, just wanted to say that I'm having an identical issue regarding r/w issues after kingroot and SuperSU Binaries won't install. I'm a newbie to rooting but my Z3v D6708 has no data connectivity through USB Debugging (hardware damage) so this was my only option. I have however been experimenting with doing a kingroot uninstall from within the king user app, then rooting using kingo root (different website entirely from KingRoot) then I rerooted with kingroot (to make it stick? I had to kingo root after every reboot) and that got me some slightly updated SU Binaries that allowed xposed to install and some modules to function. I would love for someone with more knowledge to do some research into this and fix the R/W issue though. Thanks in advance to anyone who tries to help!
Savetheknot said:
I posted this in the wrong thread earlier... Apologies
I rooted my Z3v with Kingroot (I'm beginning to think that was a mistake). I seem to have "limited" root capabilities. I cannot install BusyBox because R/W permission fails. I run root checker and get positive results. Also, I cannot make any changes to the phone's root or install a recovery. Is there a way to fix this? If not, how do I start from the beginning and get rid of Kingroot in exchange for SU and a recovery?
Click to expand...
Click to collapse
I was having read/write issues and believe I solved this with the Advanced Tools App, Settings and Root, SD card write access. Play around with the switches in that section and one of them seemed to do the trick for me.
In SU is there still the "fix permission" option?
Looks as if I didn't remember right, it seems "fix permission" is in the ROM manger etc.... CWM, TWRP.
Savetheknot said:
I posted this in the wrong thread earlier... Apologies
I rooted my Z3v with Kingroot (I'm beginning to think that was a mistake). I seem to have "limited" root capabilities. I cannot install BusyBox because R/W permission fails. I run root checker and get positive results. Also, I cannot make any changes to the phone's root or install a recovery. Is there a way to fix this? If not, how do I start from the beginning and get rid of Kingroot in exchange for SU and a recovery?
Click to expand...
Click to collapse
Better use prerooted firmware by installing recovery
Related
Just got this today
{
"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"
}
Gonna wait it out till I get more info on what it is exactly
Sent from my Nexus 10 using xda app-developers app
Maybe you could connect your N10 to ddms and get the URL of the update file it's trying to load?
Sounds like it's already downloaded.... "restart and install", if rooted, look in /cache and copy out the .zip and the hash file as they will be deleted when installed.....
That's the 4.2 - JOP40C update everyone gets when get their devices... after that you will get one more to update to 4.2.1 - JOP40D
If i'm rooted, what's gonna happen if I install & restart?!
I don't know about the 4.2.1 update but when the first update installed I had to reinstall CWM and root again.
4.2.1 install broke root but I preserved my root with Voodoo OTA rootkeeper before getting the download. After the install was complete and I lost root, went into voodoo and restored root. Super easy. Everything still has access and all new apps that need root access get it.
Ravenbf said:
4.2.1 install broke root but I preserved my root with Voodoo OTA rootkeeper before getting the download. After the install was complete and I lost root, went into voodoo and restored root. Super easy. Everything still has access and all new apps that need root access get it.
Click to expand...
Click to collapse
I am going to download the OA rootkeeper, Thanks for your clarification.
rayki said:
I am going to download the OA rootkeeper, Thanks for your clarification.
Click to expand...
Click to collapse
Your welcome and good luck!!!!
Ravenbf said:
4.2.1 install broke root but I preserved my root with Voodoo OTA rootkeeper before getting the download. After the install was complete and I lost root, went into voodoo and restored root. Super easy. Everything still has access and all new apps that need root access get it.
Click to expand...
Click to collapse
I did the same thing without any issues. However, it did revert my TWRP recovery back to stock. I just went back into the bootloader, connected it to my PC and run "fastboot flash recovery openrecovery-twrp-2.3.2.3-manta.img" to reflash back to the TWRP recovery. It was good to go!! :good:
I have a new dual-SIM phone that announces itself as an ALPS S5 Quad-core, running 4.4.2 Kitkat on an MTK 6582:
{
"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"
}
I've tried rooting with Framaroot 1.9.3, also RootGenius and SRSroot without success.
Can anyone please suggest other tools to try? Or must I wait for a new exploit to turn up?
I really want to root it, not least so I can try remapping the memory as it's already running out of program space!
Thanks.
bryangb said:
I have a new dual-SIM phone that announces itself as an ALPS S5 Quad-core, running 4.4.2 Kitkat on an MTK 6582:
I've tried rooting with Framaroot 1.9.3, also RootGenius and SRSroot without success.
Click to expand...
Click to collapse
I got root/SU for this eventually using Vroot, then installed SuperSU - be warned, Vroot claims to install SuperSu but actually installs some Chinese-language superuser tool.
For some reason, rooting meant that the SDcard went read-only again, so I had to use SDfix again. Everything else works OK after that, but now Titanium Backup claims "insufficient free space" both on the internal and external SD. Most odd!
It Works!
bryangb said:
I got root/SU for this eventually using Vroot, then installed SuperSU - be warned, Vroot claims to install SuperSu but actually installs some Chinese-language superuser tool.
For some reason, rooting meant that the SDcard went read-only again, so I had to use SDfix again. Everything else works OK after that, but now Titanium Backup claims "insufficient free space" both on the internal and external SD. Most odd!
Click to expand...
Click to collapse
It works! Thanks! But the PDAnet driver is really necessary for the success rooting method. And you also should turn app permission manager off.
csakegyuser said:
It works! Thanks! But the PDAnet driver is really necessary for the success rooting method. And you also should turn app permission manager off.
Click to expand...
Click to collapse
That's true, I think it was in the Vroot instructions. I don't know about PDAnet drivers, I just plugged it into the laptop that I keep for all this sort of work, it has HTC and other drivers on, and has reflashed and rooted a bunch of different handsets.
Have you got the Alps/Haipai S5 then? And have you taken a ROM backup of it? I messed up my device after rooting it, only to discover my ROM backup was corrupt... Sigh. So I am looking for another copy of the firmware!
Vroot
Used Vroot can root any type of China Phone/tab ivbeen worked in.
Its install some chinese leanguage apps, but, in general, ivbeen chase good results with Vroot and flashify
Is "ALPS S5" same as "USMART S5"?
I'm wondering whether "ALPS S5" is "USMART S5"? Because I can only find a few info about "USMART S5", and the data stored in my "USMART S5" shows that the manufacturer is ALPS......
Hi there, got myself today a galaxy s6 edge 128GB, SM-G925F with lollipop 5.0.2, LRX22G.G925FXXU1A0D9. I wanted to root it with CF-Auto-Root, but used first a version not compatible with my phone, that, is not for SM-G925F (because I used an Odin placed in a zip for a wrong version, that proposed to me wrong tar, etc... my bad).
Of course, after, rooting failed --> root checker was lauching the su granting window, which was frozen... No other problem. I finally found the good CF-Auto-Root, CF-Auto-Root-zerolte-zeroltexx-smg925f.zip, and retried to root my device, but with the same result as the first time...
Would someone have an advice ? Should I flash a stock rom, and reroot the device with the right CF-Auto-Root-zerolte-zeroltexx-smg925f.zip, or is there a problem with this rooting technique in general ?
Thx in advance;
MEF
MisesEnForce said:
Hi there, got myself today a galaxy s6 edge 128GB, SM-G925F with lollipop 5.0.2, LRX22G.G925FXXU1A0D9. I wanted to root it with CF-Auto-Root, but used first a version not compatible with my phone, that, is not for SM-G925F (because I used an Odin placed in a zip for a wrong version, that proposed to me wrong tar, etc... my bad).
Of course, after, rooting failed --> root checker was lauching the su granting window, which was frozen... No other problem. I finally found the good CF-Auto-Root, CF-Auto-Root-zerolte-zeroltexx-smg925f.zip, and retried to root my device, but with the same result as the first time...
Would someone have an advice ? Should I flash a stock rom, and reroot the device with the right CF-Auto-Root-zerolte-zeroltexx-smg925f.zip, or is there a problem with this rooting technique in general ?
Thx in advance;
MEF
Click to expand...
Click to collapse
Try flash the right one over first and let see!
Sent from my SM-G925F using XDA Free mobile app
junghyun01 said:
Try flash the right one over first and let see!
Sent from my SM-G925F using XDA Free mobile app
Click to expand...
Click to collapse
Ok, I flashed the official naked french rom from here :
http://www.phonandroid.com/forum/fi...lollipop-galaxy-s6-edge-sm-g925f-t119301.html
and it went totally ok. Then I wanted to CF-Auto-Root it, with the correct CF-Auto-Root-zerolte-zeroltexx-smg925f.zip from here :
http://www.droidviews.com/root-samsung-galaxy-s6-edge-sm-g925f-using-cf-auto-root/
and got the very same issue as I had initially : odin went well, with, after several reboot a blue "reset", which finally turned into a green "passed". Then I tried "root checker" which launched the su granting window, which was frozen again...
The Firmware Stock rom G925FXXU1AOD9 I got here has no problem, so I'm starting to ask myself if the cf-root file I got is corrupted or not, but it points to
https://download.chainfire.eu/737/CF-Root/CF-Auto-Root/CF-Auto-Root-zerolte-zeroltexx-smg925f.zip
which is trustwhorty... Any idea ?
PS : i put in attachment the odin mode i have on my phone, maybe there's some info here that someone could exploit the information, as well as results given by root checker pro
{
"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"
}
There's been a few posts talking about this on various forums, but nothing I can see that indicates if anyone's managed to do it.
I wan't to unroot my T95Z 3GB/32GB so I can use various TV apps.
So far I have:
- using the shell, deleted the files "su", "su_daemon" and "sud" in /system/xbin. This removes root, but it still fails the SafetyNet check, presumably because there's some other remnant of root around somewhere which is detected. Should I be deleting anything else?
- installed Magisk (which regains root), but even with the various cloaking functionality enabled it still fails SafetyNet. I'm assuming that's because the stock firmware image (even after removal of the su files) is failing SafetyNet and Magisk can only preserve the SafetyNet status if it originally passed.
Does anyone have instructions to successfully unroot the T95Z Plus 3G/32GB please? ... or alternatively a unrooted firmware image that can be loaded onto it please?
Many thanks.
Andrew17856 said:
There's been a few posts talking about this on various forums, but nothing I can see that indicates if anyone's managed to do it.
I wan't to unroot my T95Z 3GB/32GB so I can use various TV apps.
So far I have:
- using the shell, deleted the files "su", "su_daemon" and "sud" in /system/xbin. This removes root, but it still fails the SafetyNet check, presumably because there's some other remnant of root around somewhere which is detected. Should I be deleting anything else?
- installed Magisk (which regains root), but even with the various cloaking functionality enabled it still fails SafetyNet. I'm assuming that's because the stock firmware image (even after removal of the su files) is failing SafetyNet and Magisk can only preserve the SafetyNet status if it originally passed.
Does anyone have instructions to successfully unroot the T95Z Plus 3G/32GB please? ... or alternatively a unrooted firmware image that can be loaded onto it please?
Many thanks.
Click to expand...
Click to collapse
Search for osmosis unsu zip and try that, also magisk has an uninstall zip which I believe removes root
Sent from my LG-H910 using XDA Labs
idk if it's relative but in boot.img (kernel) su daemon service is written too in init.amlogic.board.rc file
{
"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"
}
Hello,
I'm interested in rooting a Cubot King Kong 3 phone (MT 6763 phone), which features Oreo 8.1, and I hope that I am currently posting in the correct forum category.
For my general understanding, I have a few questions and I really that somebody is so kind to help me shed some light on the following:
1. Is it possible to root any random phone just by unlocking the bootloader with ADB, flashing TWRP and then installing SuperSU in the recovery?
Is this the general approach I can use also on the Cubot King Kong 3? Or do I need a TWRP which is modified / customized for this phone? I would like to clarify this, before I do something and brick the phone.
2. What are some safety measures to take, before trying to root, so that I can reinstate the phone to the original state, if something goes wrong?
3. Do I have to disable any kind of data partition encryption so that I can root the phone? Or can I still root the phone without doing this?
4. What is a scatter file and for what is it used? I've read a lot of guides and it seems to be used only with SPFlash. Does this mean, that I do not need this, if root by going the ADB+TWRP+SuperSU route?
5. If after unlocking the bootloader with fastboot, I am getting the message "Orange State Your devices has been unlocked and can't be trusted. " at boot, then what went wrong and can this be fixed?
6. If after flashing the stock ROM, which Cubot provides on their forum, I get a red text "Not Verify" in the upper right corner of the screen every time the phone is on, then what went wrong and can this be fixed?
I am really thankful for your advice, you can't imagine!
what i did without sucess
Hey, i'm waiting exactly for the same things! I tested some TWPR, but no one worked at all. I cannot found any Magisk binaries who's look works with kingkong 3.
At the end, i was deseperated, so i try some kingoapp and other oneclick root apps, but without success.
I hope one day, someone with knowlegde and talent will helping us ?
As long as OEM/Carrier allows it, phone's Android can get rooted: that's true for all brands/models.
If you flash TWRP Recovery then phone's Stock Recovery gets removed. You have to re-flash phone's Stock ROM to bring it back.
SuperSU doesn't root phone's Android, it's a superuser (AKA root) management tool that allows you to manage which of all of the apps you contain installed gets granted root permission.
A phone's Android is got rooted if su binary ( what is a Linux tool, ~ 100KB ) is present on it's /system partion or any other partition.
{
"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"
}
To reiterate:
The typical way to achieve root access on an Android device is to first unlock the boot-loader, which disables verification of the /boot partition. Once the boot-loader is unlocked, the user can introduce a su binary to the system and also a superuser management app to control which processes have access to root. Unlocking the boot-loader is intentionally disabling one of the key security features on the device, which is why the user has to explicitly allow it to happen by typically enabling a toggle in Android's Developer Options and then issuing an unlock command to the boot-loader. With MediaTek-su, a script especially present for devices based on Meditek chipset, however, the user does not have to unlock the bootloader to get root access. Instead, all they have to do is copy a script to their device and execute it in shell.
Note that the user isn’t the only one that can do this, though. Any app on your phone can copy the MediaTek-su script to their private directory and then execute it to gain root access in shell.
Look also inside here