[Q] ZTE Midnight root? (repost, please anyone) - General Questions and Answers

So I have the ZTE Midnight (Z768G) and I am getting the classic "low on space" message and I know what rooting is as I rooted my Nook Tablet 4GB but I can't seem to find a root that will work for my phone so that I can set my default storage to the SD card and I was wondering if someone could help me. Or if there's alternatives to rooting it that would also be nice. I installed an app that can erase cache but it's not doing much for me right now. I can't even update my apps. Any help would be nice!!
-Luciano

any updates?
I have been doing some research (xda and google) about a method on how to root this phone (ZTE Midnight Z768G) The only thing that appears to have worked is an app called "VROOT". It is a chinnese application that you install on windows and connect the phone via usb to root it.
On my phone it says that it is rooted, but any aplicaction that tries to get root privileges gets automatically denied with no prompt asking to allow or deny.
Everything gets denied. A toast message appears and says "[app] has refused to super authority request" thus any app gets denied.
The 'vroot' app installs a chinnese 'superuser' app that is supposed to grant/deny root access but it doesn't work.
So basically something is wrong...
I am able to gain root access via ADB shell and mount the system as read-write. When I type 'su' I even get the prompt "#". However, on the phone, the 'superuser' app does nothing.
If you have any info let me know.

Try installing the app called "SuperSU" from Google Play.
Sent from my Z768G using XDA Free mobile app

Related

[Q] SU permission

I have rooted my phone with Suoer1click and have the SU icon. Then I installed the Barnicle Wi/Fi thether program. I ran the Barnicle program and it stops saying it does not have SU permission. How do i go about granting it permission? I thought the SU would do this automatically.
Normally SU should ask you automatically if you want to give the app the permission...have you already tried it after restarting your phone?
Sent from my GT-I9000 using XDA App
I get this every once in a while. I have seen it being a simple communication thing, where a reboot clears it. But I have also had app's be bad from the market and not communicate. I fixed it by getting the app on applanet, it was probably in an update that broke it. Also go into SU and check all the settings to make sure it allows stuff and give notification.
Can Anybody help ?
http://forum.xda-developers.com/showthread.php?p=13157675#post13157675

Busybox issues gingerbread Samsung galaxy tab

Hello,
Id like to request some support.
I have successfully rooted my galaxy tab (7 inch model, gingerbread) and that seems to be working correctly: I have that super user app install, and every time I launch a root like app (such as shoot me etc..) there's the pop up asking for permission.
Problem comes at the next step: busybox. I have downloaded the busybox installer from the market. Followed the steps... latest message I saw from the app is that everything went smooth, but when I launch apps that require busybox (such as Shark), application says it cant find busybox...
After rebooting, I go again to the busybox installer (I got the two of them now available on the market). Once says I don't have root, which BS, and invites me to go to the super user app and forget the settings about that application. That I do, and doesnt do anything. App request root priveleges, which I grant, but it will still tell me that it doesnt have them.
The second busybox app goes a little further: It gets the root powers (which once again proves my phone is definitely rooted) and it says something like phone is rooted and many copies of busybox were encountered.
Apparently I got more than a single copy. But when I try to "re-install" it, this is what I get: can not install because system is not in read write mode.
And i did remount the system folder with root tools pro but I still get the same message...
So, how could I resolve this situation?

[Q] BusyBox Updater Breaks Root Access

There have been a couple similar posts, but none seem to provide any help, so I apologize for creating a new one if the answer is already out there.
With that said, I recently purchased a new LG Nitro HD and promptly used SuperOneClick to root it. Everything seemed to work fine (on the first try); I rebooted the phone, SU was there, all seemed well. The first thing I tried to use the root access for was to change the LCD Density, and that didn't work - so I tried to update the BusyBox on my phone, using "BusyBox Installer". After I did that, my root access seemed to "break", by which I mean superuser is still installed, and SuperOneClick reports my phone as rooted, but SuperUser cannot authorize apps (or doesn't even try) and attempting to run an app that requires root access simply fails, suggesting that my phone is not rooted. Typically, I would ODIN the SOB and be done with it, but I cannot find any PIT files for the Nitro HD (and I am assuming that would be necessary for me to do anything with ODIN). I've also tried using SuperOneClick to unroot and reroot the device, but now it hangs on step 7 every single time.
Does anyone out there have any suggestions at all?
I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.
Please advise - I am seeing this as well
SolusCado said:
I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.
Click to expand...
Click to collapse
The new MeanROM ICS uses the new SuperUser - however, it breaks root access as you mention. Please advise the corrective action. Send PM if ncessary

ZTE V768 (Concord) and V768G (Midnight) Development

Currently, we only have root access on these devices. I am currently working on a recovery build, and I have plans for CM7 and CM9 builds in the future. Here's how to consistently and easily get root access on the Tracfone V768G and almost certainly V768 (I have a V768G):
Root
The only functional root exploit I have found is via an obscure Chinese program called VROOT. While there is much speculation in other threads as to the nature of this program (and potential for malware), I have had success with it on multiple occasions where no other tool I tried worked. I have seen no evidence that it installs anything other than its strange app market (as an easily-removable user app!) and a superuser program called KingRoot (as a system app, where it should be). While it appears entirely benign and functional, I personally prefer to use superSU. Therefore, the below instructions will include the removal of KingRoot and installation of SuperSU in its place. It is assumed that you have ZTE's preloaded drivers installed and that you have confirmed adb is working.
Unfortunately, VROOT is a Windows-only application, though it works perfectly in a Windows virtual machine (that's how I use it!).
Download VROOT and the newest SuperSU
Install and run VROOT. It might take more than one try to succeed.
Confirm that KingRoot is installed, and uninstall the 100% Chinese app that is also present. At this point, your device is rooted. You can simply keep KingRoot, but I would advise continuing to install superSU.
Extract "common/Superuser.apk" from the downloaded SuperSU zip and install it on the device via adb or the file manager.
Open SuperSU and grant it root permissions when KingRoot prompts you. Swipe over to the settings pane and select "Switch superuser app".
Follow its instructions. After rebooting the device, simply install SuperSU again, open it, update the su binary when prompted, and select "Install SuperSU inte /system" from the settings pane. You're done!
VROOT installs a app "Superuser.apk" not Kingroot
Hi, thanks for the info.
When I install VROOT via windows, it installs an app called 'Superuser' which I suppose it is to manage root access permissions for other apps. I see no 'KingRoot' app as you mentioned. I only see this 'Superuser' app and a Chinese app.
Either way, this 'Superuser' app appears to not working properly because I am not getting any prompt to either deny or grant root acess to apps like TitaniumBackup or even Root Checker.
I can get root acess via ADB Shell with the su command, but on the phone the 'Superuser' app from VROOT is not prompting me to allow/deny root access.
Any suggestions?? Thanks!!
abmx7 said:
Hi, thanks for the info.
When I install VROOT via windows, it installs an app called 'Superuser' which I suppose it is to manage root access permissions for other apps. I see no 'KingRoot' app as you mentioned. I only see this 'Superuser' app and a Chinese app.
Either way, this 'Superuser' app appears to not working properly because I am not getting any prompt to either deny or grant root acess to apps like TitaniumBackup or even Root Checker.
I can get root acess via ADB Shell with the su command, but on the phone the 'Superuser' app from VROOT is not prompting me to allow/deny root access.
Any suggestions?? Thanks!!
Click to expand...
Click to collapse
I was working on getting a custom recovery,but then I ended up getting a Nexus 4 (and then later a nexus 5) and abandoned it. Ill take another look at it. Now that I dont need the phone its less of an issue if I brick it,so I can be a little more agressive.
Try this thread. This is what worked for my V768
http://forum.xda-developers.com/showthread.php?t=2217810
pflatlyne said:
I was working on getting a custom recovery,but then I ended up getting a Nexus 4 (and then later a nexus 5) and abandoned it. Ill take another look at it. Now that I dont need the phone its less of an issue if I brick it,so I can be a little more agressive.
Try this thread. This is what worked for my V768
http://forum.xda-developers.com/showthread.php?t=2217810
Click to expand...
Click to collapse
anything i can help with getting a recovery working?
ultravioletnanokitty said:
Currently, we only have root access on these devices. I am currently working on a recovery build, and I have plans for CM7 and CM9 builds in the future. Here's how to consistently and easily get root access on the Tracfone V768G and almost certainly V768 (I have a V768G):
Root
The only functional root exploit I have found is via an obscure Chinese program called VROOT. While there is much speculation in other threads as to the nature of this program (and potential for malware), I have had success with it on multiple occasions where no other tool I tried worked. I have seen no evidence that it installs anything other than its strange app market (as an easily-removable user app!) and a superuser program called KingRoot (as a system app, where it should be). While it appears entirely benign and functional, I personally prefer to use superSU. Therefore, the below instructions will include the removal of KingRoot and installation of SuperSU in its place. It is assumed that you have ZTE's preloaded drivers installed and that you have confirmed adb is working.
Unfortunately, VROOT is a Windows-only application, though it works perfectly in a Windows virtual machine (that's how I use it!).
Download VROOT and the newest SuperSU
Install and run VROOT. It might take more than one try to succeed.
Confirm that KingRoot is installed, and uninstall the 100% Chinese app that is also present. At this point, your device is rooted. You can simply keep KingRoot, but I would advise continuing to install superSU.
Extract "common/Superuser.apk" from the downloaded SuperSU zip and install it on the device via adb or the file manager.
Open SuperSU and grant it root permissions when KingRoot prompts you. Swipe over to the settings pane and select "Switch superuser app".
Follow its instructions. After rebooting the device, simply install SuperSU again, open it, update the su binary when prompted, and select "Install SuperSU inte /system" from the settings pane. You're done!
Click to expand...
Click to collapse
Edit: was able to root with kingoroot my bad.
i need a custom recovery for it please

HELP!!

I rooted my phone with kingroot and while i was using the extra rope, i hung myself. The settings.apk in my phone has become somehow damaged, and will not open. The .apk still exists, but every time i try to open settings (directly or otherwise) it closes with a pop-up saying: unfortunately settings has stopped. I also tried to replace kinguser with superSU and failed leaving myself with confusing root access that is only revealed when certain apps like varied root checkers tell me i'm rooted.
I cannot install non market apps because when settings became damaged, the box was unchecked. All i need is to be able to fix the settings.Apk. I don't have a computer and i can't update superSU binary. I have factory reset my device and tried to find solutions onlinen to no avail. I can access the hidden menu and terminal emulator without root. I need to be able to enable non market installation some how. Can anyone help me?
Sent from my LGMS323 using XDA Free mobile app

Categories

Resources