Hello all! Apologies ahead of time if this post is in the wrong area or breaks any rules!
I currently have a short batch script that can offline root/unroot (including SuperSU install), install GAPPS, toggle Lockscreen ads, and perform many other tweaks in a few short motions. I've tested it on several HD 10 tablets that I own and it has made life easy. After doing a bit of searching I noticed that most of the root guides use Kingoroot (which does some shady operations) or are instructions that I've automated to increase speed and decrease typos / errors.
Would anyone be interested in a polished version of my KFHD10 Multitool? I will gladly release my tools if there is demand for them! I just wanted to ask before I spent the time making a nice interface and adding options to my existing script.
iamz3r0 said:
Hello all! Apologies ahead of time if this post is in the wrong area or breaks any rules!
I currently have a short batch script that can offline root/unroot (including SuperSU install), install GAPPS, toggle Lockscreen ads, and perform many other tweaks in a few short motions. I've tested it on several HD 10 tablets that I own and it has made life easy. After doing a bit of searching I noticed that most of the root guides use Kingoroot (which does some shady operations) or are instructions that I've automated to increase speed and decrease typos / errors.
Would anyone be interested in a polished version of my KFHD10 Multitool? I will gladly release my tools if there is demand for them! I just wanted to ask before I spent the time making a nice interface and adding options to my existing script.
Click to expand...
Click to collapse
I've been working on a similar zip. A tool would probably be easier. Has activating location services been a problem? I've found it to be less of an issue if flashing a zip because Amazon removed com.google.android.gms from the framework. The zip I made replaces the framework with my modded one, that replaces com.google.android.gms.
I haven't played with Location Services just yet. The script I have can root, unroot, install Play Store/Services, swap the launcher, and toggle lockscreen ads. I plan on adding more tweaks as I go.
I've spent the last hour or so rooting and unrooting just to test the success rate, and it's doing very well!
iamz3r0 said:
I haven't played with Location Services just yet. The script I have can root, unroot, install Play Store/Services, swap the launcher, and toggle lockscreen ads. I plan on adding more tweaks as I go.
I've spent the last hour or so rooting and unrooting just to test the success rate, and it's doing very well!
Click to expand...
Click to collapse
I have a fix or two to do in my framework mod. It's version specific, but I can make one for a few versions. If it's a root tool, it would be useful to add and be installed after the play store etc. It just requires location services be turned on before either the play store apps or framework is installed.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
I have a fix or two to do in my framework mod. It's version specific, but I can make one for a few versions. If it's a root tool, it would be useful to add and be installed after the play store etc. It just requires location services be turned on before either the play store apps or framework is installed.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
Hey! If you're offering to add some functionality and collaborate, I'm 100% down with that. Send me a PM with the details of what you have and I'll see how I can fit it into the AIO utility. I'm sure I'm missing some neat options.
Yes, please!
Ill test it please
DragonFire1024 said:
I have a fix or two to do in my framework mod. It's version specific, but I can make one for a few versions. If it's a root tool, it would be useful to add and be installed after the play store etc. It just requires location services be turned on before either the play store apps or framework is installed.
Click to expand...
Click to collapse
Yes this is the problem. I tried to install framework and it bootlooped. Had to side load factory.bin
gerryl432 said:
Yes this is the problem. I tried to install framework and it bootlooped. Had to side load factory.bin
Click to expand...
Click to collapse
Is this a modded framework or the unmodified version? The version I have is older and unmodified but installs and works just fine. I haven't played with all of the settings yet, though.
iamz3r0 said:
Is this a modded framework or the unmodified version? The version I have is older and unmodified but installs and works just fine. I haven't played with all of the settings yet, though.
Click to expand...
Click to collapse
What version?
Sent from my Amazon KFSUWI using XDA Labs
iamz3r0 said:
Is this a modded framework or the unmodified version? The version I have is older and unmodified but installs and works just fine. I haven't played with all of the settings yet, though.
Click to expand...
Click to collapse
i honestly cant remember. but i assume it was the wrong one
{
"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'd gladly let everyone test it out but I'm trying to perfect the auto-root script. I can easily root - that isn't the issue. The issue is the way that the Kindle doesn't prompt for SU requests. You can work around this by changing the default setting in SuperSU to "Grant" but I'm attempting to automate this process. I've gotten it automated by sending touch commands to the device to change the prompt setting but I'd much rather just change the setting manually.
I'm not 100% sure if this will work but I'm trying to:
1. Root using the exploit script (here, thanks retyre)
This works fine. 80% of the time, it quickly roots the device and I can get the SU prompt just fine. I'm able to run about one or two SU commands before anything stops working. Root + SuperSU + Manually setting the prompt config to "Grant" works 100% - obtaining root isn't the issue.
2. Upload a pre-modified SuperSU preferences file
Instead of editing the settings - we might be able to just upload the preferences XML file to the SuperSU data folder before installing SuperSU itself. That way we already have the "Prompt" setting switched to "Grant". We then change the permissions so that SuperSU doesn't modify this file when it is installed.
3. Revert permissions so that edits can be made to the settings in the SuperSU app
I would of course need to change the permissions of the SuperSU preferences XML back to the normal settings so that SuperSU can make changes to it again. This way adjustments in the app actually stick.
----
After running the root exploit script I can get a SU prompt (#) and run a command. I'm not installing SuperSU until the script makes the modification to the preferences file, but as soon as I try to run another SU command after the first - it hangs and everything stops working . I end up having to restart the tablet by holding the power button and I'm unable to get a SU prompt again without installing SuperSU and changing the setting to "Grant".
I think there is a way to make it work but I'm still digging into it. If anyone has any ideas, I'm open to listen!
Related
Description
I wrote a small application to allow easily changing the VM heap size (no more adb pull, edit, adb push). People on CM ROMs may be familiar with a similar option, but here is a little tool for those who are not running CM. As it modifies a variable which can affect the stability of the system, be careful with how you use it More about the VM heap size is written in the application itself. And of course, if I made any mistakes or if something is incorrect please correct me.
Requirements
root
system write
busybox (1.17.x recommended)
Appearing In
Japanese Jellyfish (ZTE Blade/Orange San Francisco)
If you wish to bundle this application in your firmware feel free to, but let me know if you do and please link back to this page
Download (Android Market):
{
"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"
}
Translating VM Heap Tool
English files which can be translated have been attached (txt files), and the following fields which I will mention do not need to be translated. Once you translate something you may just attach the files in your post or add them in code tags. Of course please mention the language that you translated it to so I can appropriately add it to the application and update.
Do not translate: heapSizeUnit, aboutHeap, defaultHeap, currentHeap, version, thread, heapSizeValues. These just hold key values which should not be translated. Also please don't translate "RPLACE" inside the texts, as this is replaced inside the application on run-time.
Values are stored as
Code:
<string name="aboutHeapTitle">What is the heap?</string>
where the string's name is clearly defined, "aboutHeapTitle", and the value which should be translated is inside the <> and </> tags. Values which are used in similar situations will have a common prefix, for example:
"progress..." - used on a progress dialog to display the message
"toast..." - the little grey messages that you get at the bottom of your screen and with which you can't interact
"dialog..." - used as the title on a dialog box
and so on...
Thank you to all those who are willing to help, your contributions will be noted
great app, wont have to manually erstart on droid inc. wont restart when pushing the button.
ACD168 said:
great app, wont have to manually erstart on droid inc. wont restart when pushing the button.
Click to expand...
Click to collapse
Thanks, so the Incredible has the same problem as the Desire then... If you install ROM Manager it will restart. I'm afraid that has something to do with superuser and how the phone is rooted (correct me if I'm wrong), so some devices will restart while others will not. Sadly Google doesn't allow applications to restart the device, so it has to be done in a roundabout way which may not always work...
Awesome, now everyone can break apps by lowering the heap below the expected 24 megs!
khaytsus said:
Awesome, now everyone can break apps by lowering the heap below the expected 24 megs!
Click to expand...
Click to collapse
Yes, but I hope that most people will be smarter and try to use something like 32
The "apply" and "quit" box cover the "new heap size" box on hTC Hero
skymera said:
The "apply" and "quit" box cover the "new heap size" box on hTC Hero
Click to expand...
Click to collapse
OK, thanks for letting me know. I'll see what I can do about it, but for now you can use your trackpad (or w/e it's called) to move the focus on the button and press it.
skymera said:
The "apply" and "quit" box cover the "new heap size" box on hTC Hero
Click to expand...
Click to collapse
Should be fixed now with version 1.1, as well as support for Android 1.6 and above. Apologies that it took so long.
Icon help, anyone...?
Very nicely done!!!
Thanx!!!
The app is force closing on startup on a rooted orange San Francisco (ZTE-Blade) with stock rom.
Andy.
g1dtf said:
The app is force closing on startup on a rooted orange San Francisco (ZTE-Blade) with stock rom.
Andy.
Click to expand...
Click to collapse
Do any other rooted apps crash, such as Root Explorer, ROM Manager, etc?
Rom Manager and System App Remover both run ok, not got Root Explorer so can't try that.
Andy.
martino2k6 said:
Do any other rooted apps crash, such as Root Explorer, ROM Manager, etc?
Click to expand...
Click to collapse
Forced close for me to on ZTE-Blade Stock/Root.
What happens if you write the following two commands in a terminal emulator or adb?
Code:
ls /system/bin/su
ls /system/xbin/su
If you have rooted the san fran with stock rom and this will not work, root again. Worked for me no probs, even if it says you are rooted. Just root again. It appears that when the San Fran is turned off then on, it unroots (with original rom" Well, that is what I have found after testing. I have stock rom rooted and have picked out all the Orange "tat"
Hope that helps.
System Write Required
Just tried running the app, but ran into an error: "System write required". I have root, adb is installed and recognize Android is read only by default, so I assume that I have to change permissions to include write?
Guilden_NL said:
Just tried running the app, but ran into an error: "System write required". I have root, adb is installed and recognize Android is read only by default, so I assume that I have to change permissions to include write?
Click to expand...
Click to collapse
You can't change that without using a rooting method which unlocks NAND on your device. The application already remounted the partition to write, but wasn't able to write to it because you most likely don't have NAND unlocked.
martino2k6 said:
You can't change that without using a rooting method which unlocks NAND on your device. The application already remounted the partition to write, but wasn't able to write to it because you most likely don't have NAND unlocked.
Click to expand...
Click to collapse
Well guess us Slide owners can't use this until we have s-off. No system r/w for us yet
No love on the MyTouch 3G getting NAND unlocked for Write. Ah well, the MT3G is truly a dog so I am not going to spend anymore time with it. It'll do the job for now, and I use the Nexus One as my main phone anyway.
Thanks for the tip though! At least I know where the issue is on this device.
kapslock4 said:
If you have rooted the san fran with stock rom and this will not work, root again. Worked for me no probs, even if it says you are rooted. Just root again. It appears that when the San Fran is turned off then on, it unroots (with original rom" Well, that is what I have found after testing. I have stock rom rooted and have picked out all the Orange "tat"
Hope that helps.
Click to expand...
Click to collapse
Didn't work but used clockwork and installed custom ROM and worked
Sent from my BladeVillain using XDA App
Hello,
This ROM is based on Tim6a and www_apad_tv-ibex-Flytouch-3-Firmware-V8.
I started customizing Tim's 6a ROM for my own use, basically since I wanted to see all apps compatible with FT3 on Google Play and I wanted to use ADW Launcher. Now that my customization is complete, I wanted to share it with the xda-developers community
The ROM is built to mimic a Samsung Galaxy GIO device. This device has a much smaller screen but has an ARMv6 processor like the FT3. So all apps downloaded from Google Play should work, and with good performance since it will be the app's QVGA version. Gameloft games also recognize this device, so for example you can download and play Ice Age Village.
Credits go to Tim for his great custom ROM, Apad.tv for firmware-V8, Axlien for the build.prop ideas, chairshot215 for performance tweaks. Thank you guys!
mod edit
I hope you enjoy this release!
Tolga
INSTALLATION:
Unzip the contents of mod edit] to the root folder of your SDcard, and reboot FT3. When the installation is complete, don't forget to take out the SDcard and remove the installation files.
If Wi-fi is grayed out after installation, it means that your wifi card is not 0803 v1. (default) Try enabling old FT3 or 0803 v2 using Tim's scripts in Gscript Lite.
To view all apps on Google Play, follow these steps after installation:
1. Open Google Play, accept the upgrade and accept TOS.
2. Go to Settings>Applications>Manage Applications and select ALL tab.
3. Go to Google Play, clear cache and force stop (DO NOT CLEAR DATA)
4. Go to Google Services framework, clear data and force stop
5. Open Google Play, and you should get a server error. (This is normal)
6. Restart FT3 and all compatible apps should be visible on Google Play!
mod edit
SCREENSHOTS:
{
"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"
}
FEATURES:
ADW Launcher (InfoTM Home is also included)
Rooted, superuser
Google Play Store v3.5 (Android Market latest version)
Dolphin Browser, Gmail, Youtube, Terminal Emulator, Root Explorer
Development app for enabling USB debugging
Adobe Flash plug-in 10.1
Tim6a scripts for old FT3 wifi fix, 2MP camera fix etc.
Google Play Store fix and Performance tweaks in build.prop
Minimum apps included for smaller download size and performance
KNOWN ISSUES:
Market fix needs to be applied manually after installation.
TO-DO-LIST:
Custom Kernel to enable HDMI Mirroring and Overclocking (Investigating Stragulus FT Kernel Source atm)
CHANGELOG:
v1.0
Initial Release
Click to expand...
Click to collapse
DISCLAIMER: Please use this mod at your own risk, rooting your device and installing custom ROMs may render your device unusable and VOIDS THE WARRANTY.
I will try to ensure that all info about TolgaMOD_FT3 is up to date here, and will do my best to help in case of problems. It's best to report problems by replying to this thread rather than PM, so that the solution can be viewed by all users.
Hmmm.
I'm useing one of Tim's Roms... not sure wich one. The one where the screen is always dark. I tried dling your fixed stuff put it on my sd card it said it updated took out the sd card than turned it back on, but nothing had changed, everything was still the same? I have tryed the Power button+menu+front button to factory reset it, and still tims rom is still there with no changes. I just am at a loss now... really pissed to be honest. I cant even get the thing back to it's original original settings... I want to use your packet, any suggestions?
Anyone? I have just about tried everything and I'm on my last leg. I'm about ready to just rip the case open and K.O. the battery~
Hi billypaul69,
On my FT3, I just push menu+power to do a factory reset. Perhaps you could try that button combination to do a factory reset.
About flashing my ROM: Apparently the update somehow did not complete for you. I suggest you check out this excellent video tutorial from Axlien to flash a ROM to FT3, and see if it helps: http://www.youtube.com/watch?v=w7xdpnoHLeg
Make sure you don't turn off your device, before you see the following message on the screen:
Updating system firmware completed.
Please shutdown your device and remove the installation card!
Automatic shutdown in 1 minute.
Click to expand...
Click to collapse
If you see any other messages such as "not complete", "wrong system file" etc. and not the one above, please report them here. It's possible that either the .zip file you downloaded got somehow corrupted or the SDcard you are using for the update is faulty. In that case try re-downloading TolgaMOD, or formatting your SDcard and try again.
I hope that my suggestions work for you! Thanks for checking out my ROM!
Regards,
Tolga
Thanks soo much i'm going to try all the steps asap.
\billy
Hi
I just installed your new rom file and everything went Ok. The only problem is that my wifi network is not working. I can activate the wifi but it cannot find any network.
I tried using gscript to install on of the wifi patches but I get the following error message
"stderrermission denide" when I run the script.
Any idea as to why this is happening ? Apart from that, you rom is very snappy in operation.
Hi jammertn,
I'm glad you like the speed of my ROM, that was one of my goals indeed. I'm pretty sure one of the wifi scripts will correct the problem. For example my tablet's wifi works with the "old FT3" fix.
The reason you are getting the "permission denied" error is because gscript was not given superuser permissions.
The first time you run gscript, there should be a pop-up screen from superuser application asking for root rights. You should select "Allow" on this window. If you don't allow it or deny root access, the scripts won't work. If you denied root access and selected "remember" the first time, please launch superuser application from the app drawer and change the status of Gscript Lite to "Allow".
Since you have wifi not grayed out I guess your wifi is 0803 v2. Please try running the "Wifi fix:0803 version2" script and then reboot your tablet.
I hope that helps!
Hi and thanks for the quick reply.
From where do I launch superuser?
Click the middle button (the one with white squares) on the dock, you will have access to all installed apps including superuser.
OK I found the application.
One more question, Something happened and now gscript only sees 3 scripts. How can I make it show all the scripts like before.
Excuse all my dumb questions but I'm new at this.
No problem mate, I think the best way is to simply re-install the ROM You can backup your current apps with Titanium Backup.
Nice, thanks a million
I got it working now.
I'll be watching this thread closely.
Keep up to great work
Yay! I'm glad it worked, c ya around.
Hi Tolga
Is there anyway to activate bluetooth on this tablet? I tried using the gscript but cannnot get is to work. Any ideas ?
Hi jammertn,
This tablet doesn't have a bluetooth chip onboard. Tim's scripts are for driving usb bluetooth dongles. I'm not sure which ones work, but maybe the thread below could have more info.
http://www.apad.tv/apadforum/showthread.php?1358-Flytouch-3-Bluetooth-USB-dongle-testing-thread
Hi Tolga
Thanks for the reply, I have seen that thread but it does not have have any useful info in it. I tried it with an external usb/bluetootyh dongle but still no operation.
Hi,
I ran a quick web search and I haven't seen anyone successfully making a USB bluetooth dongle work on FT3. I think Tim included some kernel modules with the firmware for devs and testing purposes. So please don't assume it will work when you simply plug in any USB BT dongle.
Here's the support thread for Tim6a, there might be more info there:
http://www.apad.tv/apadforum/showthread.php?416-Flytouch-3-Hybrid-ROM-(rooted)&highlight=bluetooth
I think I have a USB BT dongle somewhere, I will take a look if I can find it
Regards,
Tolga
has this been posted on Apad.tv or tested on the iBex Flytouch 3 by people on there?
Do you mean if this ROM has been tested or if USB bluetooth dongle has been tested? I'm pretty sure TolgaMOD runs on Ibex Flytouch 3, since it's basically a modified version of Tim6a.
Here is my ROM's thread on apad.tv:
http://www.apad.tv/apadforum/showthread.php?2675-ROM-06-May-2012-TolgaMOD_FT3_v1.0
i installed rom over Tim 6a rom but still nothing changed,, MENU+power reset also tried.. currently my Huawei data stick does not work since some weeks, thats why i need to install a fresh firmware..
merhaba, yükleme yaptim fakat yine eski tim 6a rom yüklü yani hicbir sey degismedi, hard reset yaptim yine ayni.. ayrica önceden calisan Huawei data stick bi süredir calismiyor, birseyler silinmis olmali diyerek yeni rom yüklemek istiyordum, acaba neden calismiyordur data stick?
I love Custom ROMs and Kernels and I'm sure you all do too. It seems that every time I flash my favorite CM ROM which has a built in CM SuperUser found within Settings and then after flashing my favorite kernel, I simply lose root for the ROM and the SuperUser stops working. I want to know how to get the CM SuperUser working again after flashing the zip in recovery.
Here is where my problem seems to be different than others. I can get root back by installing SuperSU and then going to settings and telling it to "Ignore CM Root Settings" and then rebooting, then root access works with SuperSU and the system thinks its doing its job too...but then when I uninstall SuperSU the entire problem comes back.
So my question is, is there a solid method to keeping the built in CM SuperUser found in Settings working as it did before flashing that zip that broke the ROMs root in the first place?
Any help is greatly appreciated! Thanks so much in advance!
I think you are experiencing a similar problem like I did ( http://forum.xda-developers.com/showthread.php?t=2602670 ). Am I right?
My root in CM11 is not working properly. So every time I flash CM11 with TWRP, I have to flash SuperSU right after CM11 and my kernel.
My personal explanation is, that SELinux (enforcing) doesn't work well with CM11 yet.
Cloonix said:
I think you are experiencing a similar problem like I did ( http://forum.xda-developers.com/showthread.php?t=2602670 ). Am I right?
My root in CM11 is not working properly. So every time I flash CM11 with TWRP, I have to flash SuperSU right after CM11 and my kernel.
My personal explanation is, that SELinux (enforcing) doesn't work well with CM11 yet.
Click to expand...
Click to collapse
Yeah, I'm pretty sure we are having the exact same problem seeing that it's CM and you flashed a kernel which broke your built-in root.
Isn't there an update for the built-in SuperUser or something? CM is really popular so I know some people have liked it enough to want to keep the built in SuperUser and not use a halfa$$ workaround. Don't get me wrong, SuperSU is LEGIT, but I want the built-in SuperUser this time because I don't want it sitting in the Settings for no purpose.
Anyone? Thank you in advance!
superuser updated today and fixed the CM breaking root deal.
What's New
- New -cn/--context parameter for su binary (devs: see How-To SU update)
- Handle mksh being switched out for sh
- Daemon forces new session immediately at launch (moved up)
- Fixed reading dynamic properties on 4.4 (update ASAP if 4.4 user)
- Fixed issue where root wasn't granted on CM
- Add support for Samsung 4.4
- Update copyright notices to 2014
- Updated language files
Additional information
Updated
January 20, 2014
I think the latest version of SuperSU (1.91) is supposed to fix that.
mistahseller said:
superuser updated today and fixed the CM breaking root deal.
What's New
- New -cn/--context parameter for su binary (devs: see How-To SU update)
- Handle mksh being switched out for sh
- Daemon forces new session immediately at launch (moved up)
- Fixed reading dynamic properties on 4.4 (update ASAP if 4.4 user)
- Fixed issue where root wasn't granted on CM
- Add support for Samsung 4.4
- Update copyright notices to 2014
- Updated language files
Additional information
Updated
January 20, 2014
Click to expand...
Click to collapse
The problem is imho the built-in superuser by CM (https://play.google.com/store/apps/details?id=com.noshufou.android.su&hl=en or https://play.google.com/store/apps/details?id=com.koushikdutta.superuser&hl=en) not SuperSU. Actually I'm not really sure which one is used in CM.
Cloonix said:
The problem is imho the built-in superuser by CM (https://play.google.com/store/apps/details?id=com.noshufou.android.su&hl=en or https://play.google.com/store/apps/details?id=com.koushikdutta.superuser&hl=en) not SuperSU. Actually I'm not really sure which one is used in CM.
Click to expand...
Click to collapse
cm uses superuser. flashing supersu fixes the issue and rids cm of everything superuser related.
It looks like, at least from all the research I did today, that there actually might be a fix for all this by possibly updating the actual ROMs built-in version of SuperUser.
If you look at this version of the SuperUser app by ClockworkMod on Google Play, you can see in one of the screenshots it shows an app requesting permission from what looks like the exact UI as the built-in SuperUser we see in our CM-based ROMs.
CM Built-In SuperUser App on Google Play:
https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
Screenshot of SuperUser found on Google Play:
{
"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 will report back if I can find a solution or fix!
xnickfx said:
It looks like, at least from all the research I did today, that there actually might be a fix for all this by possibly updating the actual ROMs built-in version of SuperUser.
If you look at this version of the SuperUser app by ClockworkMod on Google Play, you can see in one of the screenshots it shows an app requesting permission from what looks like the exact UI as the built-in SuperUser we see in our CM-based ROMs.
CM Built-In SuperUser App on Google Play:
https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
Screenshot of SuperUser found on Google Play:
I will report back if I can find a solution or fix!
Click to expand...
Click to collapse
You could try to get the .apk of SuperSU or CM's superuser and put it in the "app" or "priv-app" folder of your CM-ROM .zip-file.
I tried to simply replace the su-binary in the xbin folder... Stupid idea though. Didn't work out
Bummer, so I didn't find a solution / fix, but I did find some possibly helpful links.
These are options that I researched very deeply in any and every way possible. Notes for found possibilities are noted below the option, if any.
Opt-1 .) Locate where the files or code for the built-in SuperUser are located within ROM and update / replace them with newest version of SuperUser, and also gain root when re-root is needed.
Opt-2 .) Replace SuperUser found in CM-based ROM's Settings with newest version of SuperSU by either deleting from ROM's Settings somehow or keep it and have SuperSU built in ROM's Settings same as current SuperUser.
I do believe that somewhat of Option #2 might be possible. I don't really know for sure yet, but I found these other 2 links that look pretty interesting.
http://forum.xda-developers.com/showthread.php?t=2033590
http://forum.xda-developers.com/showthread.php?t=1539711
I know you can install SuperSU and pretty much ditch SuperUser for good, but then you still have it sitting in the ROMs settings for no reason at all.
You can remove and hide SuperUser from the ROMs settings but in order to do that you have to completely disable root. You can remove it by going to Developer Options or SuperUser settings and choosing "disable" for SuperUser Access. Unfortunately when doing this SuperSU immediately stops working even when open and closes the first chance it gets.
If anyone else can shed any light at all on the subject, it would be VERY MUCH appreciated! Thank you!
I have spent hours trying to figure out how to get Viper4Android working on my moto X pure edition 2015. There is only one thread in the internet discusses this subject http://bit.ly/1j1Gal7 . I tried all the suggested methods in that thread. But none really worked. The results are V4A works only under compatible mode or works but some features are disabled or doesn't work at all.
I even tried some methods suggested for other lollipop phones with the same results.
After lots of trial and error, I finally found a way to have V4A working perfectly on my MXPE under normal mode with all options enabled.
Note: before we start, I assume that you have not messed up the system files on your MXPE. If you have, uninstall any version of V4A on your phone and completely remove any trace of it. Try your best to revert any modifications in the system files done by other methods you have tried.
Important: before you start, take nandroid backup in case something goes wrong.
Let's get down to business:
1- Disable "Audio Effects" using Apps in Setting or Titanium Backup
Reboot
2- Change SELinux to permissive mode using SELinuxModeChanger app
Reboot
3- In Developer options enable "Use AwesomePlayer (deprecated)"
Reboot
4- Install busybox using this app https://goo.gl/tUIwfj Don't use smart install. Just use the normal install
Reboot
5- Use TRWP to flash the following 3 files in the same order:
V4A_MXP.zip
Viper4A_Soundfix_LibFiles.zip
Viper4A_Build_Prop_Tweaks.zip
Wipe cache & davik cache and reboot
6- Open V4A and install the drivers and reboot
7- By now you should have a working V4A under normal mode but without neon support. Continue with next steps to fix this
8- Open V4A and uninstall drivers and reboot
9- We want now to uninstall V4A but since it's installed as a system app, we need a special app to do this. I used Titanium Backup
Reboot
10- Install the normal Viper4Android apk not the zip Must be installed as a user app not a system app
11- Open V4A and install the drivers. I chose the Power Saving but you can go with Super Audio Quality if you want
Reboot
Congratulation... You have now a perfectly working V4A on your moto X PE/Style 2015 with all the options enabled under normal mode
Glad you took the time to dive into this. In the middle of closing on a house also previous 2 phones were defective. so I didn't time to dive in. Currently using xtreme music mod flawlessly. Will definitely use this on next clean flash. Any issues between stock or cm running using same method. Thanks for your hard work.
Edit... forgot to mention that I'm op from viper confirmed thread.
works great thanks for you time and also to share it with us
Delete
I got it to work a while ago by flashing xtreme music mod but first I installed v4a from their website,installed driver, then flashed xtreme music mod. So I had both and then I disabled v4a from the apk. And kept the one from xtreme music mod and works under normal mode.
But v4a on this phone has issue like gets lost somewhere in ram because sometimes effects are not that strong after I reboot they are stronger.
Sent from my XT1575 using Tapatalk
Got it working, but seems to partially break aux when connecting to a car need to plug in really slow to get it to work (been the same for every V4a I've tried) Thanks for the work.
I have flashed as suggested. Works fine.
I just moved from stock to AICP and this did not work to enable neon but xtrememusic mod won't enable neon as well (did work on stock)
However even with neon off under normal mode I don't see any difference in quality. Maybe it's just me.
elevatorguy said:
Got it working, but seems to partially break aux when connecting to a car need to plug in really slow to get it to work (been the same for every V4a I've tried) Thanks for the work.
Click to expand...
Click to collapse
Works great here with aux. No problems whatsoever.
patt2k said:
I just moved from stock to AICP and this did not work to enable neon but xtrememusic mod won't enable neon as well (did work on stock)
However even with neon off under normal mode I don't see any difference in quality. Maybe it's just me.
Click to expand...
Click to collapse
Tested on stock rom. Not sure about other roms.
Pretty crazy all the hoops to go through to get it working but you're the man...it works. Thanks
Works part of the time using it in my car on audio jack. When listening via Google Play Music, it won't be active and then suddenly the volume drops like a notification is coming through and it pops back up and I can tell that Viper became active. Strange. Followed all the steps to the letter. Even checked 'force Viper' when I noticed this happening and no change, still does it. On stock rom, unlocked.
Somebody try to run this process on MM?
Sent from my XT1575 using Tapatalk
Was just about to ask that myself I'm having trouble getting v4a to work on MM. If anyone could tell me the process if they have this working could you kindly let me know it would be much appreciated
Sent from my XT1575 using XDA Premium HD
k3mik4l said:
Was just about to ask that myself I'm having trouble getting v4a to work on MM. If anyone could tell me the process if they have this working could you kindly let me know it would be much appreciated
Sent from my XT1575 using XDA Premium HD
Click to expand...
Click to collapse
Have you tried this method?
Sent from my XT1575 using Tapatalk
{
"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"
}
Method still working on MM.
Sent from my XT1575 using Tapatalk
I am on MM, rooted. I do not have any eq settings in sound / notification is that normal? Also in Dev options, Use Awesome player (depricated) is not there.
Going to attempt install anyway and see how it goes.
lafester said:
I am on MM, rooted. I do not have any eq settings in sound / notification is that normal? Also in Dev options, Use Awesome player (depricated) is not there.
Going to attempt install anyway and see how it goes.
Click to expand...
Click to collapse
This works great. Thanks!
For anyone having issues with Viper sometimes, and opening the Viper app fixes it, a tasker profile should fix it.
I put a task to run the following shell command whenever my headphones or bluetooth stereo are connected:
am startservice com.vipercn.viper4android_v2/.service.ViPER4AndroidService
Might need to run as root.. not sure.
Also, using App Settings with Xposed and checking Resident should keep it from being killed from memory.
You can find the Lollipop version for App Settings here.
I just flashed xtrememusic mod and to my surprise out of the box neon is not enabled. That would be easiest way to do it. So far everything is good.
Sent from my XT1575 using Tapatalk
much for simplified process
Have an extremely simplified process I have discovered that is at least working on my TruePureX 2.2 install (so Marshmallow deodexed ROM). This method has the MAJOR benefit of leaving SELinux in enforcing, that's what the 4th zip I have added to the process accomplishes! This fix was created by a user named maximumentropy. His original post is here.
http://forum.xda-developers.com/showpost.php?p=61242973&postcount=18854
This script requires the use of SuperSU as your root solution so be sure you have root established with it before continuing (not tested on systemless root)
*Note* Because of this fix it is also possible to leave Viper4Android as system app and it will asked you to install the driver of your choice immediately after flashing it the FIRST time. Saving tons of restarts. Also we can skip enabling awesomeplay as well. (not even possible on Marshmallow from what I gather anyhow)
So without further delay. Here is the updated process
1. Disable "Audio Effects" using Apps in Setting or Titanium Backup. No need to restart
2. Install busybox using the app "busybox" from play store. consider a purchase just to support the dev. Do not use smart install!
NOW Reboot to recovery
3. Use TRWP to flash or sideload the following 4 files in the following order:
a. V4A_MXP.zip http://bit.ly/1O8Mker
b. Viper4A_Soundfix_LibFiles.zip http://bit.ly/1MdLInf
c. Viper4A_Build_Prop_Tweaks.zip http://bit.ly/1NSCCid
d. ViPER4Android-supolicy.zip https://www.dropbox.com/s/k9cnruw2e1t1d4t/ViPER4Android-supolicy.zip?dl=0
Now... wipe just cache (no need to wipe dalvik, takes too long and not needed) and reboot
4. Now Viper4Android will be installed as system app so open it up. Be sure to grant it Root permission via SuperSU prompt, it will ask you which driver you would like to install. Select one of the 3 options I personally use "Super Audio Quality"
Reboot one more time and viola
You now have a fully functional Viper4Android and you have not compromised your kernel security by changing SELinux policy. Again we can avoid the messiness of uninstalling the system app and reinstalling as user app this way saving time. This is fully functional including NEON support!!!
I hope this simplifies the process for everyone, certainly alot quicker this way! If OP would like to update the first post please feel free.
Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"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 read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}
Reserved
*I am big fan of this device. Looking forward to using it as my daily driver, and very happy to extend NRT support*
just added to index
[INDEX] LG NEXUS 5X Resources Compilation Roll-Up
Nice to see you here WugFresh!
Good to see you, glad you've joined us :thumbup:
Hi! Very nice to see you here! You're always been my backup when I screw up something in the past with my nexus devices. I'm know I can always get back to stock with NRT
Verstuurd vanaf mijn Nexus 5X met Tapatalk
@WugFresh
Love your NRT on the Nmmexus 6. Glad you're here. Makes life a lot easier
I couldn't install busybox as mentioned in the instructions provided for "rooting", it's the last step (confirmation for root). It prompted me to change installation directory but system/bin doesn't work as well. And i can't boot recovery as well after the whole rooting process. It just shows me a dead android there
edit: i may have download stock recovery as well, as prompted by your toolkit after rooting.
#2 edit: reflashed twrp to solve my problems, but you may want to mention something to prevent something like that from happening again. Or maybe i'm just dumb
#3 edit: so sorry, it seems that the busybox provided was outdated, update it from playstore and installation will be good to go
imadiu said:
I couldn't install busybox as mentioned in the instructions provided for "rooting", it's the last step (confirmation for root). It prompted me to change installation directory but system/bin doesn't work as well. And i can't boot recovery as well after the whole rooting process. It just shows me a dead android there
edit: i may have download stock recovery as well, as prompted by your toolkit after rooting.
#2 edit: reflashed twrp to solve my problems, but you may want to mention something to prevent something like that from happening again. Or maybe i'm just dumb
#3 edit: so sorry, it seems that the busybox provided was outdated, update it from playstore and installation will be good to go
Click to expand...
Click to collapse
I am having BusyBox issues also.
mmartenn said:
I am having BusyBox issues also.
Click to expand...
Click to collapse
If you tried to install busybox right after you root your phone, as what the Root toolkit tells you to, it will not work like mine. That's because it's outdated. So just go to play store and update that app first before you reinstall any other app. I presume you rooted your device right after you unlock your bootloader which factory resets your device.
I have issue gaining write access to /system, busybox can't install to system/bin or system/xbin, had to install busybox through recovery.
also no /system write access through adb shell, it says system file read only
coolineho said:
I have issue gaining write access to /system, busybox can't install to system/bin or system/xbin, had to install busybox through recovery.
also no /system write access through adb shell, it says system file read only
Click to expand...
Click to collapse
Same problem here. Any solutions?
riceknight said:
Same problem here. Any solutions?
Click to expand...
Click to collapse
Not yet, still waiting ;(
I'm also facing the same issue, can't install busy box. It force closes after it fails to install. I tried updating to 124.1 but that didn't work, I also uninstalled and installed again from the playstore but that didn't work.
I also can't reboot into TWRP, unless I reboot through the NRT updater.
If I try to reboot normally without the updater, then I get the red warning message saying my phone is corrupt, followed by the green android robot with a red warning triangle coining out of it's stomach.
I'm running MDB08L
What I'm doing wrong?
Thanks
Sent from my Nexus 5X using Tapatalk
Install notes:
In options menu disable installing busybox, install busybox from play store after root process.
After root, Flashboot Flash Recovery in Advanced Utilities.
I have had no problems after using these steps.
I followed the steps above and busybox still wouldn't install so I found a 1.24.1 flashable zip flashed it and it worked . just another option to try if all others are not working
Does the "Restore: Flash Stock + Unroot" option completely wipe any trace of unlocking, rooting so that the phone could be sent to Google for repair. (I'm just asking, in case my screen breaks)
Tank87 said:
Does the "Restore: Flash Stock + Unroot" option completely wipe any trace of unlocking, rooting so that the phone could be sent to Google for repair. (I'm just asking, in case my screen breaks)
Click to expand...
Click to collapse
Yup, just did mine to send it back to google for warranty replacement of intermittent power button.
Guys here is a flashable zip. It's busybox 1.24.1 permissive. It's works 100% for me many times. If anyone wants 1.24.1 SElinux just let me know and I'll upload it
https://www.dropbox.com/s/e8tpfd4d8qcsqo5/Busybox-1.24.1.zip?dl=0
Sent from my Nexus 5X using Tapatalk
skulldreamz said:
Guys here is a flashable zip. It's busybox 1.24.1 permissive. It's works 100% for me many times. If anyone wants 1.24.1 SElinux just let me know and I'll upload it
https://www.dropbox.com/s/e8tpfd4d8qcsqo5/Busybox-1.24.1.zip?dl=0
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I just tried flashing this file (through twrp right?). It doesn't look like it worked through TWRP I got an "Updated process ended with error=1, error flashing 1.24.1.zip", and busybox is still not present on the phone when I restarted it. I tried downloading it from the play store directly and it still gives me the "it looks like it was not installed successfully" error message. Should I be flashing this file some other way? Thanks in advance!