Related
This post is now irrelevant, Alex put these commands into the main program. See second post for links.
I figured out how to get it fully working. Big thank you to tonyb486 and canteenboy for figuring out that you need to disable adb and usb mass storage for tethering to work. That only left the problem of disk mounting not working after you are tethering. Here are two scripts to get the whole thing running smoothly and without a problem.
First, if you haven't already, install android-wired-tether. Next install GScript Lite (on the Market) which will let us automate toggling the USB function switch.
Create a new script with SU enabled and use this as the code.
Code:
echo 0 > /sys/devices/platform/msm_hsusb/usb_function_switch
That command shuts off usb_mass_storage and adb so everything is disabled and ready for Wired Tether to come in and do its job. Your usb_function_switch will look like this after running the command.
usb_mass_storage:disable
adb:disable
diag:disable
serial:disable
ether:disable
modem:disable
nmea:disable
When you are done tethering, use this command to re-enable adb and usb_mass_storage:
Code:
echo 3 > /sys/devices/platform/msm_hsusb/usb_function_switch
If for some reason you don't use USB debugging (adb), you can use this command to turn on usb_mass_storage by itself.
Code:
echo 1 > /sys/devices/platform/msm_hsusb/usb_function_switch
For those of you new to GScript, you can place shortcuts to scripts on your home screen. To simplify my life, I put them in a folder with Wired Tether so I have everything in one place. It's not an elegant solution, but you won't need to reboot your phone to get SD card mounting to work again. Perhaps someone with more knowledge of GScript can write some code that will automate running the first script, starting Wired Tether, and then running the last script after it notices that tethering has stopped. (Or better yet, get these commands into the actual program itself.)
(Optional)
For completeness, if you use any of the other usb functions listed above, you can use other 'echo #' commands to find the right combination. They don't toggle individual settings, but rather represent entire combinations of settings. I think around 32-33 it cycles back to 0 (everything off), I didn't have time to figure out if there is a pattern. You can find out what each number does by using another script to read out the switches.
Code:
cat /sys/devices/platform/msm_hsusb/usb_function_switch
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Thanks! I'd like to add that the scripts and the patched app are both working great on my Incredible.
O Whoa, Wired Tether works on my stock Eris now Thank You
Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
Same. I was going to try the app on the Eris because the same manual fix works :\
jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
yeah me too cant find it
Wow, I thought nobody gave a **** about this. Here it is, all compiled and ready to go.
Thanks duder, works like a charm...
Sent from my phone.
THANKS!!!!
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
dalstrs said:
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
Click to expand...
Click to collapse
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
striker012 said:
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
Click to expand...
Click to collapse
The problem with that is having to install stuff on the computer. With wired tether you don't have to install anything on the computer.
XevoX said:
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
Click to expand...
Click to collapse
I'm running the same kernel on evio rom and it's working fine for me...
Sent from my phone.
I've been able to make this work on my stock kernel, rooted FroYo Evo, so this is indeed possible and I've narrowed it down to what is necessary. Please star/follow issue 23 in the Google Code tracker for updates.
Unsupported Kernel message...
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Click to expand...
Click to collapse
Hi EindhovenOne, I responded to you on the issue tracker for Wired Tether, but I'll respond here just for some others to know the situation.
I found a fix that worked for me on my stock, rooted FroYo Evo and I coded the change and sent Harald a patch. He incorporated the patch and did the build for Wired Tether for me to test, which I have done (and it does indeed work for me, but does currently have the unsupported kernel dialog*). At the same time, though, it is listed in the downloads (you have to select all and then search), but this is in beta state for the changes (hence the deprecated tag I believe).
* I have fixed the unsupported kernel message and sent Harald a patch on this as well, so when he finds time to build it, that should be corrected, too.
So back to the "it's not working" portion, since I'm not running anything but stock (ROM and kernel), my system won't be the same as everyone's. I have no problem with other variations of ROMs and kernels (Evo's and non-Evo's) trying the 1.3 APK, giving feedback, and I'll try to do what I can (and someone else can step in if more suited than me even).
If you do run into issues, you can tag them in the issue tracker, which I try to follow frequently right now. Also, most importantly, if you can provide as much information as possible (what ROM and kernel you're using, a LogCat run just after the error occurs, any other pertinent information we can use to diagnose the problem, etc.), that helps tremendously in tracking down the problem and identifying a fix.
Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
superevilllama said:
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
Click to expand...
Click to collapse
The beta-in-progress version 1.3 is located here. It still warns about the kernel currently but you can ignore it (simple lapse in patching that as well at the time). It works perfectly for me (starting and stopping), but there are a couple of issues outstanding right now that I'm working through with the users.
If you do run into a problem, though, just let me/us know through the issue tracker preferably, but you can also contact me directly (here, or my email via the issue tracker).
PS: I have patched the kernel message already, but I don't have write access to the project yet and I don't have the build system in place to handle the native code just yet, so I have been handing builds off to Harald who graciously has done the 1.3 so far for me. When he has time to do the one including the kernel warning fix, I'll post again with an update on that.
Hi all -
NOTE: This project is on permanent hold until Tasker 1.1.2 is officially released. There are lots more features that will make it much easier both from a development end and a user end to use tRUE. I regret that I can't work on this now, but there are just too many Tasker limitations to work around that will be dealt with in Tasker 1.1.2. This will hopefully be by the end of the month, but may take into mid-October.
Furthermore, Koush has locked down writing commands to recovery starting with CWM5. If your ROM uses CWM5 for its recovery, it will not be compatible with tRUE.
Introduction
Welcome to tRUE - the Tasker Recovery User interfacE. The main goal of this Tasker profile scheme is to act as a replacement for most ROM Manager Premium features.
Why tRUE? How is it better than ROM Manager?
tRUE replicates ROM Manager functionality by writing commands to /cache/recovery/extendedcommand; these commands get executed upon reboot to recovery, just like ROM Manager. But there's lots more that tRUE can do!
Automatically download and install latest CM7 nightly for your device, at a time or context of your choice! GApps flashed automatically for free!
Bulk update-flash install - great to flash kernels, fixes, and more, along with your nightly!
One-touch and scheduled backup - Click a widget and immediately perform a Nandroid backup! Or, let it run automatically every night!
Free with Tasker - Tasker's the greatest $6 app out for Android, and it can replace lots of apps you typically pay for!
TO DO: Flash profiles: Flash any set of zips you want at any time!
TO DO: One-touch Nandroid restore of latest backup!
TO DO: Simple backup management - automatically delete old auto-backups!
I'm always listening for ideas as well, please contribute to the development of this project!
What's in the ZIP
The following Tasker profiles:
tRUE-nightlywget
tRUE-nightlyMD5
tRUE-nightlyinstall
tRUE-nightlycheck
tRUE-boot
The following Tasker tasks:
tRUE-AddNewZip
tRUE-boot
tRUE-cwm
tRUE-flash_nightly
tRUE-flash_user_zip
tRUE-nandroid
tRUE-NandroidWidget
tRUE-nightlycheck
tRUE-nightlyinstall
tRUE-nightlyMD5
tRUE-nightlywget
tRUE-restorenandroid
tRUE-RestoreWidget
tRUE-SETUP
tRUE-s_volts_scheduler
tRUE-UPGRADE
tRUE-wget_gapps
tRUE-wipe_cache
The folder "tRUE", which contains:
folder "download" - contains gapps-gb-20110729-signed.zip, and will contain your downloaded nightlies
folder "scripts" - contains checkupdate.sh, flashzip.sh, install_nightly.sh, nandroid.sh, wipe_cache.sh, get_CWM.sh, s_volts_scheduler.sh
Requirements
Tasker 1.1+, available on the Android Market or Tasker website
Secure Settings Plugin, available on the Android Market
For now, ROM Manager (free or premium) - I only need this for the directories it creates, I'll do it myself later
Coming from tRUE 2.1.1?
See this post; download the scripts folder and replace yours with this. It corrects some issues if you have a CWM that was both detected by ROM Manager and is not CWM2.x or 3.x.
Installation
Make sure you're already running a CM7-based ROM. tRUE does NOT wipe /data and perform the first-time-install instructions for your device; if you try to do so, you might brick!
In Tasker, click Menu->Preferences->Misc and check the box "Allow External Access". This allows Tasker to pass arguments to the shell scripts run by Secure Settings Plugin.
UPGRADING USERS: Delete all old tRUE profiles and tasks. (Sorry about the tedious installation! It'll be more streamlined in the future.)
Download the attached ZIP. Place the tRUE folder in the root your SD Card. (UPGRADING USERS: it will suffice to replace the scripts folder with the one from the zip.) Place *.tsk.xml in /sdcard/Tasker/tasks . Place *.prf.xml in /sdcard/Tasker/profiles.
Open Tasker, hit the Menu Button->Profile Data->"Import One Task". Import the 19 tasks. (WOW THAT'S ALOT! It's what you get with awesome functionality )
Repeat previous step, but with profiles. Import the 5 profiles.
Exit Tasker by hitting the check-mark. This will save the profiles and tasks.
NEW USERS: Re-enter Tasker, the click Tasks and select "tRUE-SETUP". Click the play button.
UPGRADING USERS: Re-enter Tasker, then click Tasks and select "tRUE-UPGRADE". Click the play button.
Download the GApps package below and place in /sdcard/tRUE/download. Or, run the task "tRUE-wget_gapps"
Edit the "tRUE-nightlycheck" profile to suit your needs - currently it'll fire every day at 4am, if your device is powered.
Setup will try to automatically detect your device's CM7 codename; if it can't, enter the codename (i.e., cdma_droid2, vibrantmtd, glacier, etc)
Create the tRUE widgets - on your home screen, long-press, then click "Widgets"->Tasker->Tasks->tRUE.
Usage
When a new nightly is available, tRUE will automatically wget the zip and leave it in /sdcard/tRUE/download . You can skip this process if you download the zip yourself and place it in that folder. It then performs an MD5 check; if the check succeeds, it writes commands to /cache/recovery/extendedcommand to perform a Nandroid backup; wipe your cache and dalvik-cache; flash the nightly; flash the GApps package; and flash any zip you provide. See below.
Use tRUE-AddNewZip to add update-flashables to your nightly installation. I install Glitch Kernel and my own Software GPS Fix for my Vibrant. tRUE looks at /sdcard/tRUE/toflash.txt and installs zips in order. You can either use tRUE-AddNewZip or manually edit this file.
Limitations and Bugs
Currently tRUE-nightlywget is kind of slow - I tried to provide download percentage so you don't patiently wait wondering how long the download will take, but this seems to actually slow down wget, and sometimes wget actually quits out. I can't replicate this all the time.. I might have to just remove the download percentage indicator. Sorry!
AFAIK, all variants of CM7 run on ClockworkMod3+; I only provide commands to use CWM3+. If you're running CM7 and are on CWM2 or below, please let me know ASAP so I can include functionality.
It seems that if you abort a script via the Secure Settings plugin notification (it fires when I use a script), no more scripts will fire until after a reboot. I am working with the developer of the plugin to see if it's a true bug or an issue between keyboard and chair.
Right now, tRUE-nightlycheck will run the entire download and install process even if it couldn't detect you were on CM7. If you're not running a CM7-based ROM, YOU MIGHT BRICK UPON TRYING TO USE tRUE. FOLLOW THE CM7 FIRST-INSTALLATION INSTRUCTIONS BEFORE ATTEMPTING TO USE tRUE.
To Do
Only enable vibration when user presses the tRUE-nightlycheck widget - this way the user can sleep soundly without his phone vibrating in the middle of the night
Manage deletion of old nightlies - maybe keep 2 or 3, but delete older ones?
Menu-driven interface to more ROM Manager-esque - one widget to access all functions, instead of many
Add "flash profiles" - allows you to quickly go from vanilla CM7 to MIUI to some other CM7-based ROM, while flashing all your extras for you
Add one-touch Nandroid restore widget
on setup, create clockworkmod folders (to store backups) if it doesn't already exist
Add profile to perform automatic Nandroid backups
If I helped improve your CM7 experience, PLEASE hit the Thanks button! Or even better, donate This has been a really fun project for me and I hope my work helps you too!
Changelog
Code:
V2.1.2:
- fixed issue where having CWM that was not version 2 or 3 (e.g. 4) was not detected by shell scripts
V2.1.1:
- fixed wget looping error - had to remove attempted wget workaround for failed downloads
- fixed "typo" - forgot an End If statement in tRUE-installnightly
V2.1:
- Menu-driven UI - single widget "tRUE" to do nightly check, backup, recovery, add to profile
- one-touch backup/restore - perform with tRUE widget
- if S_volts_scheduler detected, save it before flashing a nightly and restore upon boot
- notifications after boot if you just flashed, backed up, or restored
- support for CWM 2.x
- bug fix - /cache/recovery/extendedcommand not always written - fixed by mounting /system before writing (via scripts)
- bug fix - adding zip to flash profile didn't use full pathname; now also makes sure that the file the user selected actually exists (wtf?)
V2:
-initial release of tRUE - a complete rewrite of AutoCM7 with
loads more features and robustness!
Downloads
http://cmw.22aaf3.com/gapps/gapps-gb-20110729-signed.zip GApps package (07/29)
COMING IN NEXT VERSION
I'm going to start using SL4A to do the heavy lifting. Writing for Tasker is exhausting and difficult. No new features will be added until V3, when everything will be written with Perl/bash; Tasker will be used only to support the Perl scripts. This gives me the ability to really use UI (show download progress, list cool menus, etc), and improve my own sanity! I get to write in a real programming language!
V2.1.x will contain bugfixes as reported by the community.
bug fix: S_volts_scheduler not restored correctly on new flash still - workaround in progress
FREQUENTLY ASKED QUESTIONS
Q: Why is the install process so tedious?
A: Tasker was designed to be very extensible, but wasn't designed to be able to run what some might call an app. There is discussion to implement mass-import of tasks and profiles in future versions of Tasker.
Click to expand...
Click to collapse
Q: JESUS CHRIST, 24 DIFFERENT THINGS TO IMPORT!?
A: See above. You're getting what's essentially a ROM Manager Premium replacement for free! If you wanted easy-to-use with no freedom to customize, go buy an iPhone
Click to expand...
Click to collapse
Q: Why do I need Secure Settings plugin? Why didn't you use Locale Execute plugin?
A: With Locale Execute Plugin, running commands as root requires granting permission to every single command that uses it. People got around that by writing all possibly needed commands into a single shell script, then used Tasker to pass arguments back and forth. SSP in the end makes the install process easier for the user. It also lets me look at exit codes and capture STDERR and STDOUT - both tasks are much more difficult than necessary using Locale Execute.
Click to expand...
Click to collapse
Q: Why are the icons so ugly!? Couldn't you pick better ones?
A: I could have - but that requires that users have Tasker icon packs installed, and in the end icon packs are just for aesthetics - I don't think making it a requirement to install more stuff before you get to play with tRUE just to make icons look pretty is worth it. You're free to change the icons, though!
Click to expand...
Click to collapse
Q: Why should I use tRUE instead of ROM Manager Pro!? It seems like a lot of work (both for me to install and you to develop) to replicate a well-known app.
A: Tasker is AWESOME is why. It's $6.50 on the Market (or $5 if you buy it directly from the developer), and that's the best 6.50 you could possibly spend. I replicate so many app functionalities with it, it probably saved me a good $15 in the long run. Contrast to RMP, which is $6 and only manages your ROMs. Not that that's a bad thing! A lot of apps are out there that let you control basic stuff on your phone - but Tasker can replicate the functionality of a LOT of apps out there. This started mostly as an exercise to see how far I could push Tasker.
Click to expand...
Click to collapse
Q: YOU'RE SO AWESOME, PLEASE HAVE MY BABIES!
A: I appreciate the gesture Really all I need from you is to push the Thanks button and post with your experience, questions, comments, bug reports, etc. If you're feeling REALLY generous, hit the donate button I do this in my spare time because it's fun and I love Tasker. I don't expect anything in return for me sharing the work that I would have done anyway.
Click to expand...
Click to collapse
Updated to v1.1. Found a bug where the device name was not being passed correctly to the shell script; also turned on Secure Settings notifications for debug purposes. Please re-download and try it out if you've had problems with V1.
update to v1.2, fixed bug where gapps package was accidentally deleted after new nightly found
Many thanks, this sounds awesome, will give it a go, though I have already purchased the rommanager premium (just for nightlies actually).
Looking forward to seeing more advanced useful profiles, I'm loving tasker as well.
This is pretty neat, I'm testing it on my Droid X right now.
I don't suppose there's any way to implement some sort of progress bar for the download? It's basically a wait-and-find-out process right now.
strictlyrude27 said:
[...] Create a new profile, and set your own contexts. I prefer to have a context of 4AM, if the device has power, and if I'm currently connected to wifi. [...]
Click to expand...
Click to collapse
Care to elaborate please? I'm stuck at point 7 What profile should I create and how. Thanks! Looking forward to testing this.
Sunblood said:
This is pretty neat, I'm testing it on my Droid X right now.
I don't suppose there's any way to implement some sort of progress bar for the download? It's basically a wait-and-find-out process right now.
Click to expand...
Click to collapse
I can't do a progress bar, but I think I can do a toast notification of how much of the file was currently downloaded..
I plan on doing a rewrite with more robust options and capabilities, but it's kind of on the backburner for right now..
Let me know if you run into errors, please! I'm kind of surprised more people aren't using this setup..
mi3x said:
Care to elaborate please? I'm stuck at point 7 What profile should I create and how. Thanks! Looking forward to testing this.
Click to expand...
Click to collapse
In Tasker, just hit the Plus sign on the bottom to start a new profile. Then select the first context you want the download check to fire. Like I said, I have mine set to fire at 4am every day. Then, set CM7_AutoInstall as the task to perform. Finally, long-press the first context once the profile is created to add more. I only want to have downloads happen when I'm power is connected.
Thanks, I guessed that was the way, but just wanted to be sure. Now looking forward to seeing CM7 build 16 today or tomorrow to test this. Will post my results. Many thanks again, nice work.
Another question, does it flash it directly over the existing build, or could you think of something to wipe cache before? I always wipe cache and dalvik as instructed in Q&A in CM thread.
Sent from my GT-I9100 using Tapatalk
Ok, my first report.
First, as a new build was released I tried to test the task directly, but after some minutes, I cancelled the script. Then, I browsed to the CM7 folder and I saw the build 9 downloaded there (I am on 15, and the new one was 16).
I thought it was because I cancelled the script, so I deleted the zip there, and placed instead my actual build i.e 15.
Re-ran the task again, all good, it d\l and flashed the rom on my phone, but instead of having build 16 on my phone, it was the build 9, (from 30/07).
So there must be a bug, I assume.
Just wanted to let you know, hope you'll fix it as I'd love to use it.
Sorry for my English
mi3x said:
Ok, my first report.
First, as a new build was released I tried to test the task directly, but after some minutes, I cancelled the script. Then, I browsed to the CM7 folder and I saw the build 9 downloaded there (I am on 15, and the new one was 16).
I thought it was because I cancelled the script, so I deleted the zip there, and placed instead my actual build i.e 15.
Re-ran the task again, all good, it d\l and flashed the rom on my phone, but instead of having build 16 on my phone, it was the build 9, (from 30/07).
So there must be a bug, I assume.
Just wanted to let you know, hope you'll fix it as I'd love to use it.
Sorry for my English
Click to expand...
Click to collapse
What device do you have? I'll look into it..
Sent from my SGH-T959 using XDA App
Im on Samsung Galaxy S2.
Nice catch. I just looked at the mirror page for your device.. Since 9 is a single digit, it's the last link on the page. I assumed that the last link is always the latest mirror.
If you try again tomorrow or the next day it should work, since eventually Build 9 will be removed from the page. I'll try to work on this this week (along with the rewrites).
Sent from my SGH-T959 using XDA App
The last couple times I tried the script, it will start the download and pop up with "Download completed with errors" a few minutes later (not long enough to actually finish the download) and then reboot and try to install the failed package. CWM fails the hash check and reboots normally.
Droid X (shadow)
Sunblood said:
The last couple times I tried the script, it will start the download and pop up with "Download completed with errors" a few minutes later (not long enough to actually finish the download) and then reboot and try to install the failed package. CWM fails the hash check and reboots normally.
Droid X (shadow)
Click to expand...
Click to collapse
Thanks for the catch. I check the MD5 before I reboot into download mode, and it's supposed to error out if the check fails.
All, I will try to have V2 released this weekend. Life's a bit hectic right now and frankly there wasn't a whole lot of interest in this project from the community before, so nobody tested for me all this stuff.. thanks for the help!
I find it very interesting, so I will gladly help if possible. Thanks again.
Sent from my GT-I9100 using Tapatalk
does this also wipe /data/ after flashing?
XlAfbk said:
does this also wipe /data/ after flashing?
Click to expand...
Click to collapse
I would hope not.
One suggestion: I use Rom Manager Janitor to clean up old backups on boot so I only have ~3 or so, but it specifically looks for the naming system that Rom Manager uses so it doesn't delete manual backups. Could you use the same naming convention or do you just pass the "backup" command to CWM and let it do its own thing?
Otherwise, I'd rather stick with RM's backup and just have this script flash the nightly.
The notifications that SecureSettings throws up (not the ongoing, but the one-off errors and such) don't activate the Clear button in the dropdown window so I have to click it to clear them. It's probably an issue with SecureSettings but I thought I'd let you know.
Finally, I have two gapps zips in the AutoCM7 folder. 20110613 and 201106130. Can I delete one?
Update on my issue: I'm going to try and get a screenshot of the error message that the download spits out. It shows the download hit 100% but the file size keeps increasing until ~102mb, then the md5 check fails. Manually downloading (i.e. via rom manager) works fine.
Screenshots:
http://i.imgur.com/Ix4jo.png
http://i.imgur.com/0BPBJ.png
http://i.imgur.com/a8Vn9.png
As you can see, the download hits 100% about halfway through the actual filesize. The MD5 of the downloaded file actually matches the md5 on the nightly site, but it says the md5 fails. Manually selecting the zip with Rom Manager works just fine.
Welcome to Androot-N7p-ROM for the NextBook 7 Premium *ONLY.
I decided to change up some of the apps and generalize the rom in terms of its boot-animation screen. It runs on LauncherPro (just choose it as the "always"/default upon first instance of it. The Launcher that comes with the device isn't so great, but I left it there just in case.
It's based on the first known rooted ROM for this device: 'DocHoppy's ROM'. Credit for most of this ROM goes to him and to 'Wendal' for his toolset for packing the ROM (into cramfs) for the Nextbook 7 Premium device.
As such, it is a beta/ work-in-progress.
Androot-N7p-ROM v0.2
[ 146 MB ]
download here
Instructions:
*WARNING: FLASHING THIS DEVICE WILL ERASE YOUR DATA AND APPS!!!!*
Download image.
Rename file to update.img
copy file to root of SD card.
Follow on screen prompt asking if you want to run update image.
Disclaimer:
I am not responsible for bricked devices.
Here's my changes..
removed:
-youtube player <- the real youtube app is better
-explorer <- redundant
-slide me app market <- redundant now that Google's Market is installed
-quick search box <- Google Search widget is better IMO
kept/added:
-Market <- the real Google one
-root explorer - an alternative & capable file explorer
-astro file manager <- we all know it well
-quickpic 1.5.2 - a much lighter & more efficient photo organizer/viewer
-3D gallery <- some love it, some hate it
-brightness level 1.0.0 - quicker brightness changes
-ConnectBot 1.6.2 <- for those that need a SSH tool
-Officesuite full <- may as well keep it
-Titanium Backup 4.6.7 <- has some very handy tools aside from backups
-LauncherPro 0.8.6 <- may be old, but it's smooth and capable
-superuser <- because this rom is rooted
-has some of the Google Apps (go ahead and add as you see fit)
-has a custom boot animation.
Click to expand...
Click to collapse
Known Issue:
Apps2sd reports SU Binary out of date. Attemps to update this via superuser fails due to cramfs file system.
It's not perfect, but it does work well and I run it as my daily driver on my N7P.
Please give feedback or suggestions! I trust the pro devs could easily help me out with the little things!
-------------------
here are other threads related to the Nextbook 7
http://forum.xda-developers.com/showthread.php?t=1410862 (dochoppy's rom)
http://forum.xda-developers.com/showthread.php?t=1190990 (rooting talk? )
Since I'm new to modifying/cooking ROMs, here's my
Questions I have for the devs that cook ROMs all the time...
(lol)
Where do I edit the items that show in 'settings > about' in the device?
How do I change the default shortcuts that LauncherPro puts on the dock?
How do I change what icons are default on the home screen?
Where do I put custom wallpapers as part of the rom?
How do I modify Android UI colours?
Can the dialer be removes without losing "contacts"?
How do I create a shortcut to "contacts" without the phone/dialer?
(more to come I'm sure)
Hello, first of all, thanks for your work!
I am having trouble loading this rom. it says there's an invalid image file in my sd card and if I want to delete.
Now, I don't know if my tablet is a never or older version of what you guys have...
Next7p
2.3.1
kernel: 2.6.32.27
build: v2.0.7.....
my serial is also different from alot..it starts with YF0511
any help or tips?
In Dochoppy's original rom/post he mentions that the device will need to have a serial number starting with YF1011. That stands the same for this rom, as it's derived from his.
Having an invalid update.img firmware file could be due to a number of things, but the one I have here works on my device.
I wish I had more of an answer, but by all means try out the tools for repacking the rom.
So after messing around compiling a ROM, I forgot to add a launcher, and now I am stuck in a bootloop. After the girl in the dress is there for awhile, I get a black screen, then reboot. Anyone now how to fix this? I have been searching Google, but can not find anything yet.
Any help would be great!
xxProphecyxx said:
So after messing around compiling a ROM, I forgot to add a launcher, and now I am stuck in a bootloop. After the girl in the dress is there for awhile, I get a black screen, then reboot. Anyone now how to fix this? I have been searching Google, but can not find anything yet.
Any help would be great!
Click to expand...
Click to collapse
I had mine half dead for a short bit until i found i could go into a low level bootloader mode and recover it. I am working on getting a the tool/images i used to recover mine uploaded and such.
Download and extract n7p_rescue_kit.zip
Reboot device using paper clip then quickly press and hold reset until you get black screen with usb plugged in
When windows wants driver give it the respective folder for your os (32bit or 64bit) from Drivers folder from the download
Run RK29update.exe if it says "Found RKAndroid Loader Rock Usb" on bottom you are good but if it shows "No Found RKAndroid rock usb" repeat last step.
Either flash all of the default selected items or do just system (since bootloop is in system)
Hope this helps
P.S. If you pack then unpack your custom one you can flash JUST system using the tool but be sure to use the offsets that are pre-loaded.
use a pin to push the reset button on the back to break out of the boot loop.
If after this your rom still bootloops, try putting a different update.img rom to flash, on to the sd card. Then boot into safe mode by holding all 4 front buttons after boot. the update should be found and installed after that.
Thanks!
I registered just to thank DocHoppy for all his efforts. I have a Nextbook Premium 7 I got for Christmas from Hastings, which fell into the YF09111XXXX batch. I used Wendal Chen's RK29xxImageTools_v2.1 to unpack the firmware upgrade from the nextbookusa site. I then put the Google apks, SuperUser, Rootexplorer, and re-packed it with a custom bootanimation. Because of my serial # I couldn't use DocHoppy rom without getting that "Invalid Update" error, but using their firmware seems to work.
My next goal is to find a way to get the "Accounts & Sync" into the settings! One of my apps is getting an "Error 42" which is an Android Market authentication error... however, other apps have worked without any problems so it's difficult to tell if that's the issue I'm having.
aberrantjots said:
I registered just to thank DocHoppy for all his efforts. I have a Nextbook Premium 7 I got for Christmas from Hastings, which fell into the YF09111XXXX batch. I used Wendal Chen's RK29xxImageTools_v2.1 to unpack the firmware upgrade from the nextbookusa site. I then put the Google apks, SuperUser, Rootexplorer, and re-packed it with a custom bootanimation. Because of my serial # I couldn't use DocHoppy rom without getting that "Invalid Update" error, but using their firmware seems to work.
My next goal is to find a way to get the "Accounts & Sync" into the settings! One of my apps is getting an "Error 42" which is an Android Market authentication error... however, other apps have worked without any problems so it's difficult to tell if that's the issue I'm having.
Click to expand...
Click to collapse
Install "Quick Sync Settings" to get to the hidden settings view.
Also did you use this guide for market? That one worked great for me.
Thanks
Working great for me so far. Thanks sharing your work.
Nice!!!
I have the image as well... Can you tell me how to open it or point me in the direction of a tutorial? I've been looking for weeks and couldnt find any info until this thread I have a yf091... as well. Thanks in advance for any help.
lost enigma 208 said:
I have the image as well... Can you tell me how to open it or point me in the direction of a tutorial? I've been looking for weeks and couldnt find any info until this thread I have a yf091... as well. Thanks in advance for any help.
Click to expand...
Click to collapse
Not sure if this rom will work for you, just guessing by your serial number. If it is to work changing between roms on these tablets is very easy. Just download the image onto the root of your sdcard, rename it update.zip (not update.zip.zip) your tablet will recognize it as an update and ask if you want to proceed. If you say yes then follow the prompts and your in business!
Sent from my NXM726HN using XDA App
Just go this to day and was plesantly suprised to find this rooted rom. Just wanted toy let you know that my S/N is YF12112xxxx and this rom work prefect for me (so far) Thanks for all the work you guys have done here. Also is there anyway to over clock the processor in out tabs?
Thanks for the comments thus far!
I would like to overclock this thing too, but that might be further down the road, as priority is on getting a different file-system for the /system volume.
Version 0.4 is coming next.
FYI:
There will be a larger span of time between updates on this particular rom for the N7p, because I will be using more stable conjumbles of things from other roms for this device. This rom is more of a remix or derivative than an entirely different rom.
Again thanks for all the hard work. I have a few requests. first since we cant change the Adhoc ( using wifi from another android device) on the fly with out RW access can you please add the ability to connect to adhoc wifi in the next build? Also i love google currents app but we cant use is on our device because we don't have map's installed. can that be added as well?
fireproof34 said:
Again thanks for all the hard work. I have a few requests. first since we cant change the Adhoc ( using wifi from another android device) on the fly with out RW access can you please add the ability to connect to adhoc wifi in the next build? Also i love google currents app but we cant use is on our device because we don't have map's installed. can that be added as well?
Click to expand...
Click to collapse
Most of the N7P roms out there now have Market installed and working. Why not just install these apps yourself?
I only suggest so because for the time being, the device is limited to its minimal capacity for apps without full-on apps2SD. Besides, for a tablet like this, you want to keep the system apps to a minimum and de-bloated for performance whenever possible.
sgtfoo said:
Most of the N7P roms out there now have Market installed and working. Why not just install these apps yourself?
I only suggest so because for the time being, the device is limited to its minimal capacity for apps without full-on apps2SD. Besides, for a tablet like this, you want to keep the system apps to a minimum and de-bloated for performance whenever possible.
Click to expand...
Click to collapse
As far air know they can not be installed with out write access. I f they can please let me know how and I will be more then ecstatic to get them both installed.thanks.
Sent from my NXM726HN using XDA App
fireproof34 said:
As far air know they can not be installed with out write access. I f they can please let me know how and I will be more then ecstatic to get them both installed.thanks.
Sent from my NXM726HN using XDA App
Click to expand...
Click to collapse
Oh I was talking about currents and maps. Both of those can be installed via market. I have them both on my tablet.
The ad-hoc networking is something worth putting in a later release though.
good mention.
Runs great
Works great on my
NextBook Premium 7
Serial: YF121121263
Manufactured: Dec 2011
I just joined and know very little about tablets
but this image is better than the rest. I'm 63 retired and would like to learn how to do what you do.
Again, thanks for your hard work.
lrmahon
Welcome. Lots of searching and trial and error ,but this is a great place to start!
lrmahon said:
Works great on my
NextBook Premium 7
Serial: YF121121263
Manufactured: Dec 2011
I just joined and know very little about tablets
but this image is better than the rest. I'm 63 retired and would like to learn how to do what you do.
Again, thanks for your hard work.
lrmahon
Click to expand...
Click to collapse
Sent from my NXM726HN using XDA App
Hi guys,
I wanted to post this here in case it helps anyone else enjoy their device while we wait for kitkat for our device :silly:
There are a few things that I had issues with with the K1T to start off with:
ROOT!
Install Custom Recovery
Slow and inaccurate GPS
Inability to install Xposed Framework
Lack of useful Cyanogenmod features like advanced reboot menu
Expandable volume settings
Volume too loud at lowest setting
Gyroscope not working
GPS being constantly on!
Navigation buttons going dark while screen is on
Auto brightness too bright in dark
Outdated GPS EPO files
OK so to start off with I'm going to assume that you have adb tools installed on your PC and has some idea of how to use it.
I have tested this for the Kingzone K1 Turbo only. Regardless use this guide at your own risk.
All these changes were made on Stock ROM (0502L009_20140815)
1. Root:
This is quite straightforward. Download the attached RootGenius program and follow the simple instructions HERE
2. Install Custom Recovery:
Download my TWRP-based recovery HERE and place it on the root of your SD-Card.
Install MobileUncle from Play Store and choose Recovery Update in the menu after accepting root prompt.
Select the recovery.img file that you have on your SD-Card and follow the prompts.
Done.
3. Fix GPS Issues(could be used for other MTK devices too)
First of all, depending on were you live, you should change the NTP values and additional server values in the gps.conf file since they are set up for China(unless you live in China of course)
Since I live in Europe, I chose the European NTP entries.
I would suggest that you find the entries for your region HERE
This is what my gps.conf looks like(/system/etc/gps.conf):
Code:
NTP_SERVER=europe.pool.ntp.org
XTRA_SERVER_1=0.europe.pool.ntp.org
XTRA_SERVER_2=1.europe.pool.ntp.org
XTRA_SERVER_3=2.europe.pool.ntp.org
DEFAULT_AGPS_ENABLE=TRUE
INTERMEDIATE_POS=1
ACCURACY_THRES=4000
SUPL_PORT=7276
SUPL_HOST=supl.google.com
To you see yours type in adb shell:
Code:
cat /system/etc/gps.conf
To edit yours use something like ES File Explorer and only edit the first 4 lines to match the servers for your region.
Then delete files /data/misc/mtkgps.dat & /data/misc/EPO.DAT
Reboot your device and go outside.
With internet access and some maps application or something open... wait until it gets a fix. It can take a few minutes this first time because it has to regenerate the files that was deleted.
From now on your GPS fix should be quicker but your accuracy still might not be 100% this will be much improved once you DeOdex your ROM in a later step below which I HIGHLY recommend doing.
4. Inability to install Xposed Framework:(could be used for other MTK devices too)
The reason for this is that you need to DeOdex the stock ROM before this would work.
I found an excellent article HERE by @superstone to deodex our device.
I've slightly simplified the steps though since they are not all required.
DO A FULL BACKUP in recovery ...... just in case...
Ensure you are able to use adb. If not google for a guide that shows you how to install adb tools.
Download the attached customized MTK deodex tool from the Unreal Odexer guys as can be seen in THIS thread and extract onto your PC.
Use the tool as per the included instructions to extract and deodex the files from your phone.
Then copy the files from the app and framework folders on your PC to your SD-CARD to /sdcard/done_app & /sdcard/done_framework
Next in command prompt on your PC:
Code:
adb remount
adb shell
stop
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
rm /system/app/*.jex
cp /sdcard/done_framework/* /system/framework/
rm /system/framework/*.odex
rm /system/framework/*.jex
echo dalvik.vm.execution-mode=int:fast >> /system/build.prop
reboot recovery
In recovery wipe Cache and Dalvik-Cache.
Reboot and wait for the first boot to complete. It will take some extra time while recreating the cache.
After this you should be able to install Xposed framework without issues AND much improved GPS accuracy and fix time.
5, 6, 10, 11:(could be used for other MTK devices too)
Install the Gravitybox xposed module after you installed the framework as described above and you will be able to customize ALL of these items so that it is very Cyanogenmod-like.
Go through the options in Gravitybox to find what you would like, I promise you you will like the stock ROM much more after
7. Media volume to high on lowest setting through loudspeaker.(could be used for other MTK devices too)
in mobileuncle tools go to the Engineering Mode(MTK)>Hardware>Audio>LoudSpeaker Mode
Choose Type = Media & Level = 0
Then set the value to something lower.... I chose 120 but this is up to you... you can change the other volume steps here as well but I left it.
8. Gyroscope not working.
This needs to be fixed in the source... I'm still hoping that I'll be able to do this one day
9. GPS constantly being on.
Under the All Apps menu, force-close and disable the weather apps that came with the phone, they are hogging the GPS.
12. Outdated GPS EPO files
I've made a simple app EPO Tools which will when run download the newest EPO.DAT and EPO.MD5 files from epodownload.mediatek.com instead of the under resourced FTP location to a temporary location under /data/data and then copy it to the /data/misc directory where needed.
It also has the ability to automatically and silently download the EPO files on a daily schedule as set by you.
Because you are copying to /data/misc, you need to have root.
It does nothing apart from telling you "EPO updated" when its one.
Would most likely also work for other Mediatek devices that use EPO files.
If there is any interest in a lean ROM based on a DUMP of the changes above, I can see if I can produce something like that.
Anyway I hope this helps someone. If you have any questions then please feel free to ask. :good::good:
How can i see if my gps is always on?
You will see the gps indicator in the status bar when you are not using any Gps related applications.
I don't have a gps logo when i have gps disabled..
Of course you wouldn't because it is then disabled.
Congratulation to your custom recovery! Im still trying/learning to make one myself. I'm currently following the Cyanogen porting guide, but I fear a successful outcome is impossible for the time being with the mtk6592 chipset. Nevertheless I'm learning a lot, so I'll keep trying.
The GPS-Fix can be done without rooting:
Go to your folder where you have adb.exe installed, create a file gps.conf with the content in the first post.
Then open a Terminal in this folder. Type:
Code:
adb shell
mount -o rw,remount -t yaffs2 /sys /system
exit
adb push /system/etc/ gps.conf (<- note the space between /etc/ and gps.conf)
cheeers
Added ad-free EPO DL app.
Nice effort, thank you! I am still hesitating to apply this since I haven't given up hope on the elusive Kitkat update. Will wait until the end of the year and then go for a custom ROM.
gyro not fixed still?
hi I received my k1 turbo today as I wanted a big screen good phone and to use it for google cardboard VR BUT my gyro does not seem to work, ive tried all the sensor test apps and it only seems to work in 1 of them but the rest and most used apps don't find it, BUT I downloaded a few games that require ou to move the phone to play the game and that works, also I downloaded a gyro 3 space planted thing where you move your phone to move around the planted to make it look 3D and that works
google cardboard does not work and non of the apps for that done as when you move your head the game or apps don't move as the gyro does not work, so is there definatly no fix for it that I can do? if not then im going to return it and get my money back as the phone is basically faulty, I really love the build and the screen the camera though is really bad lol there is no way in hell this is a true sony 14mp sensor, all pics look bad, even in good daylight and then when you take one and zoom in a tiny tiny bit to see the details the quality is horrid lol, also in video mode you can not choose the res of the video it only says low or high quality, also every spec list for this phone says it can do 1080p at 60fps or 720p at 120 fps lol which is a lie, though I have a nokia 1020 which is pretty much the best camera phone around so that could be why this k1 camera looks bad to me
I would live with crappy camera if the gyro was working
ALSO did this phone have a gyro problem when it was the android 4.2 or has it always had the problem
You bought the phone for the same reason I did, VR...
Unfortunately no the gyroscope doesn't work and never has in any rom [emoji20]
I will be getting a refund and posting it back then, I have messaged the seller, its obviously a big fault with all the phones so its not acceptable
also I think I may have a battery problem with mine as well, it was 10% so I put it on charge and after about 10-15 mins it was at 95% I took it off charge and it dropped back to 8% within 5 mins, I then left it for 2 hrs and just does the same
this is what you get for buying cheap phones I guess, this is the last time I do it, think I will just pay the extra for a big brand, ive never had problems with big brand phones before lol, it a big shame though as the screen and built is fantastic and id say the best build phone ive every had :/
eben80 said:
You bought the phone for the same reason I did, VR...
Unfortunately no the gyroscope doesn't work and never has in any rom [emoji20]
Click to expand...
Click to collapse
Added a link for my EPO Tools app on Play Store with which you can automatically schedule a daily download of the EPO files to your Mediatek device.
4.4.2 Kit Kat
Now that the KitKat update has come along, do you think you could help me out a little bit with that process? I thought it would be way easier than this. If I at least had an idea of what went where, that would be pretty helpful. I just want to go to the regular Stock 4.4.2 and I'm not sure really if it's done differently than a custom firmware or what.. Thanks!!
Off to a good start with the K1-T
Hi
I just ordered a K1-T last week and am waiting for it to get hear and I want to I guess get off on the right foot, so ware do I start ? Root it, put on recovery and back it up ?
And then move on to a custom ROM ?
I have never had grate luck backing up phones in the past seems that once you wipe it there never the same. and on one S4 I had I did not know that if I updated it that I could not us a custom Roms
and it was realty tough to UN-update it.
and I it looks like on (Need-ROM) a lot of Roms are pre-rooted and recovery I don't know how that works? You need root and recovery to install any thing don't you?
my last PH was a note 3 and it went for a ride on the roof of my truck.
I have been wanting a K1 scene it first came out, and now I just don't want to brick it
my wife is not to understanding about that sort of thing.
So can you please get me on the right track with it thanks –Rick
I have been following all the threads I can about the K1-T on XDA but I don't know my way around
and of if I need to contact any one else. hake, i don't even know ware to look for this reply.
( i am clueless i guess )
Sorry I am a vary poor speller
and if you can email me that this not got though.
Do not update to KitKat, do not flash a custom ROM. Just root. Phone runs best as is. You may miss XPosed at first, but there's a lot can be done with root alone. Just clean China apps.
Poppeye0 said:
Do not update to KitKat, do not flash a custom ROM. Just root. Phone runs best as is. You may miss XPosed at first, but there's a lot can be done with root alone. Just clean China apps.
Click to expand...
Click to collapse
OK , so you are saying if it is not broke don't fix it, once it is rooted uninstall the bloatware ?
what about auto on-line updates, shoud i prevent it from updating its self ?
from what i have seen i looks like a nice OS out of the box, a little plain maybe but nice.
If it comes with JB it will not update itself to KK. Run any updates from OTA, though.
Yes OTA updates are the last thing to worry about when it comes to kingzone [emoji16]
eben80 said:
Hi guys,
I wanted to post this here in case it helps anyone else enjoy their device while we wait for kitkat for our device :silly:
There are a few things that I had issues with with the K1T to start off with:
ROOT!
Install Custom Recovery
Slow and inaccurate GPS
Inability to install Xposed Framework
Lack of useful Cyanogenmod features like advanced reboot menu
Expandable volume settings
Volume too loud at lowest setting
Gyroscope not working
GPS being constantly on!
Navigation buttons going dark while screen is on
Auto brightness too bright in dark
Outdated GPS EPO files
OK so to start off with I'm going to assume that you have adb tools installed on your PC and has some idea of how to use it.
I have tested this for the Kingzone K1 Turbo only. Regardless use this guide at your own risk.
All these changes were made on Stock ROM (0502L009_20140815)
1. Root:
This is quite straightforward. Download the attached RootGenius program and follow the simple instructions HERE
2. Install Custom Recovery:
Download my TWRP-based recovery HERE and place it on the root of your SD-Card.
Install MobileUncle from Play Store and choose Recovery Update in the menu after accepting root prompt.
Select the recovery.img file that you have on your SD-Card and follow the prompts.
Done.
3. Fix GPS Issues(could be used for other MTK devices too)
First of all, depending on were you live, you should change the NTP values and additional server values in the gps.conf file since they are set up for China(unless you live in China of course)
Since I live in Europe, I chose the European NTP entries.
I would suggest that you find the entries for your region HERE
This is what my gps.conf looks like(/system/etc/gps.conf):
Code:
NTP_SERVER=europe.pool.ntp.org
XTRA_SERVER_1=0.europe.pool.ntp.org
XTRA_SERVER_2=1.europe.pool.ntp.org
XTRA_SERVER_3=2.europe.pool.ntp.org
DEFAULT_AGPS_ENABLE=TRUE
INTERMEDIATE_POS=1
ACCURACY_THRES=4000
SUPL_PORT=7276
SUPL_HOST=supl.google.com
To you see yours type in adb shell:
Code:
cat /system/etc/gps.conf
To edit yours use something like ES File Explorer and only edit the first 4 lines to match the servers for your region.
Then delete files /data/misc/mtkgps.dat & /data/misc/EPO.DAT
Reboot your device and go outside.
With internet access and some maps application or something open... wait until it gets a fix. It can take a few minutes this first time because it has to regenerate the files that was deleted.
From now on your GPS fix should be quicker but your accuracy still might not be 100% this will be much improved once you DeOdex your ROM in a later step below which I HIGHLY recommend doing.
4. Inability to install Xposed Framework:(could be used for other MTK devices too)
The reason for this is that you need to DeOdex the stock ROM before this would work.
I found an excellent article HERE by @superstone to deodex our device.
I've slightly simplified the steps though since they are not all required.
DO A FULL BACKUP in recovery ...... just in case...
Ensure you are able to use adb. If not google for a guide that shows you how to install adb tools.
Download the attached customized MTK deodex tool from the Unreal Odexer guys as can be seen in THIS thread and extract onto your PC.
Use the tool as per the included instructions to extract and deodex the files from your phone.
Then copy the files from the app and framework folders on your PC to your SD-CARD to /sdcard/done_app & /sdcard/done_framework
Next in command prompt on your PC:
Code:
adb remount
adb shell
stop
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
rm /system/app/*.jex
cp /sdcard/done_framework/* /system/framework/
rm /system/framework/*.odex
rm /system/framework/*.jex
echo dalvik.vm.execution-mode=int:fast >> /system/build.prop
reboot recovery
In recovery wipe Cache and Dalvik-Cache.
Reboot and wait for the first boot to complete. It will take some extra time while recreating the cache.
After this you should be able to install Xposed framework without issues AND much improved GPS accuracy and fix time.
5, 6, 10, 11:(could be used for other MTK devices too)
Install the Gravitybox xposed module after you installed the framework as described above and you will be able to customize ALL of these items so that it is very Cyanogenmod-like.
Go through the options in Gravitybox to find what you would like, I promise you you will like the stock ROM much more after
7. Media volume to high on lowest setting through loudspeaker.(could be used for other MTK devices too)
in mobileuncle tools go to the Engineering Mode(MTK)>Hardware>Audio>LoudSpeaker Mode
Choose Type = Media & Level = 0
Then set the value to something lower.... I chose 120 but this is up to you... you can change the other volume steps here as well but I left it.
8. Gyroscope not working.
This needs to be fixed in the source... I'm still hoping that I'll be able to do this one day
9. GPS constantly being on.
Under the All Apps menu, force-close and disable the weather apps that came with the phone, they are hogging the GPS.
12. Outdated GPS EPO files
I've made a simple app EPO Tools which will when run download the newest EPO.DAT and EPO.MD5 files from epodownload.mediatek.com instead of the under resourced FTP location to a temporary location under /data/data and then copy it to the /data/misc directory where needed.
It also has the ability to automatically and silently download the EPO files on a daily schedule as set by you.
Because you are copying to /data/misc, you need to have root.
It does nothing apart from telling you "EPO updated" when its one.
Would most likely also work for other Mediatek devices that use EPO files.
If there is any interest in a lean ROM based on a DUMP of the changes above, I can see if I can produce something like that.
Anyway I hope this helps someone. If you have any questions then please feel free to ask. :good::good:
Click to expand...
Click to collapse
I'm sorry but, would you give the video turorial for this? thanks
In case anyone is interested in the internals of this phone :
https://goo.gl/photos/k9nHcDgfyjpLSch77
Sent from my K1_turbo using Tapatalk
Computerfreek274's System Image
for the Verizon Droid Turbo
This image is based on the XT1254 Verizon 21.44.12 rooted stock image with native WiFi tether/hotspot enabled, and is meant to be flashed using MOFOROOT.
Features:
Keep your data! - You will not need to reinstall any applications or lose any data as this method only replaces the phone's system partition.
Stable! - I don't publish images without exhaustively testing them. If you have any issues to report, reply to this post and either myself or the community will rally to help fix the issue.
Much better battery life! - This image focuses on battery savings without compromising performance. Your phone will last much longer while running this system image.
Fast! - Breathe new life into your Droid Turbo, this image is lean, fast, and enhanced for performance. I draw from the well-documented tweaks of the community, including stuff like V6 Supercharger.
No bloat! - All bloat that is available on the Play Store has been removed. Extra files (like help videos and help audio files) have also been removed.
Optional adblocking! - Adblocking via AdAway that can be toggled on and off.
Optional ViPER4Android! - Increase the volume and the quality of audio output from the Droid Turbo by enabling VIPER4Android which comes bundled in this system image.
Enabled for XPOSED! - This system image has been enabled for the XPOSED framework as well as includes BusyBox.
1.5.5A
1.5.5A All in one V4A See Changelog for more info.
Download Here
MD5: e07886cfe0be7348a10627c50a019b7d
1.5.5A All in one Without V4A See Changelog for more info.
Download Here
MD5: 22500511e09451245c92bc15dd926539
1.5.5A All in one V4A With 493 Dpi test build Please see note below.
Download Here
MD5: b8baaf983bf82ed541de2b9d999a267c
This build has a DPI of 493 stock was 640 is gives you a lot more room on the screen also 5 rows on the home page. But this will make the moto display (active display) off-centered!!! this is the black clock screen when you wave your hand over. there is a fix to there you have to use xposed.
Fix for moto display in DPI 493 build.
Install "App Settings" from Xposed repository (or google it)
Set the DPI to 640 for Moto Display app.
Unlock button and clock will be unaffected!
Credits to Dareal and Jaocagomez
1.5.4a + AdAway
Download Here
MD5: 0e1411b1e5be9c580e5ce0e0fe9a9e35
1.5.4a + AdBlock Host Files
Download Here
MD5: b1f25360a939a201b1532762000f708b
1.5.4a
Download Here
MD5: 1cbc6a02e4c4e995f65612039b7965dd
Instructions:
Check your system version. Go to Settings -> System -> About Phone -> System version; make sure that you're on the system version 21.44.12.quark_verizon.verizon.en.US before starting. This is a requirement for using MOFOROOT. If you're not on this most recent version, download and install the Verizon system update by going to Settings-> System -> System updates -> Check for system updates.
Check your operating system. The MOFOROOT method can only currently be ran on Windows and Linux. If you are on OS X, you can set up a virtual machine using VirtualBox running the current (15.04) version of Ubuntu. This tutorial will help you get it set up. If this step applies to you, the rest of the steps need to be completed in your virtual machine, NOT OS X.
Download and install the drivers for your device. You have to make sure that your computer can recognize your phone first. Depending on your operating system, any of these links should be able to get you set up: Motorola, AndroMods, RootJunky.
Download the system image from this thread. Before you try to flash the system image, please cross reference the MD5 hash, or else you may brick your phone!
Ensure you can connect to your device via ADB and fastboot. Download and install Android Debug Bridge (ADB) on your operating system. It is included in the Android SDK. This is an awesome guide to installing fastboot - use it. Once both are installed, plug your phone in and open a command prompt. By either adding adb/fastboot to your path, or navigating to the downloaded directories, run adb devices to see if your computer recognizes your phone. Reboot the phone into bootloader mode by following these directions. Once you've connected your device to your computer while in this mode, try running fastboot devices from the terminal to make sure that your computer recognizes your phone while in this mode (this is the mode you will need to be in when using MOFOROOT).
Ensure that you have Python on your machine. MOFOROOT is written in Python, so Windows users will have to make sure that they have Python 2.7.9 downloaded and installed.
Download MOFOROOT. This system image is meant to be flashed using MOFOROOT. Ensure that you've paid for and downloaded the de-facto rooting method from their website. Please note that this method provides a utility that allows us to flash pre-rooted system images to our phone, but does not turn write protection off. Motorola/Verizon has locked down this device's bootloader and enabled write protection, so any changes made to the system partition outside of this method will be only temporary and disappear after reboot. Development on this phone may feel like we have to jump through so many hoops - that's because we do. You should be able to download and run mofoverify from their site, which will give you a link to be able to pay for and download the mofo utility.
FLASH THE IMAGE! After all of those steps, you can finally connect your phone to your computer in bootloader mode (checking to see that it's recognized using fastboot devices) and run mofo flash path_to_the_downloaded_system.img. This is the original XDA mofo instructions, read and follow them if you have any issues. If you're having problems with using MOFOROOT via VirtualBox[/URL on OS X (using [URL="http://www.ubuntu.com/download/desktop"]Ubuntu as your guest OS), here's a thread where some issues were discussed. If mofo stops on you and doesn't make it to 100%, just press the up arrow and then enter to restart it. Do not plug your phone into a USB 3.0 port as this happens far more on USB 3.0. I have flashed multiple IMGs and some of them stopped and I had to restart it. So just give it time.
CLEAR THE CACHE BEFORE RESTARTING! After you have flashed the system image using MOFOROOT, you MUST wipe the cache before rebooting. You can follow these instructions if you don't know how to do it. Failing to wipe the cache may result in your phone not booting. You should still be able to get to the bootloader menu if you get caught in a bootloop, and clearing the cache should fix your issue.
Reboot and PROFIT! Congratulations! You're finished. The first phone reboot may take about 10 minutes. Do not freak out and just let it finish. The next steps are optional if you'd like to set up ad blocking, ViPER4Android, or XPOSED.
Setup ad-blocking. This system image has AdAway pre-installed (if it doesn't, you can download it). Open AdAway and go into Preferences and click on Target host file and set it to /data/data/hosts from the pop up menu. Go back and hit Download files and apply ad blocking. If Super User asks for permission, grant it. Also say yes to the system link on the first-time setup. Restart your phone. You should now not see most ads! You can disable this at any time by going into AdAway and pressing Disable ad blocking. If you would like to manage ad-blocking on a per-app basis, you can disable AdAway and use MinMinGuard for Xposed. Thank you @pjsockett for the tip.
Setup ViPER4Android. ViPER4Android (V4A) is pre-installed. Open the app and enable it and set it up. Do NOT check the box Force Enable V4A and run V4A in FX Compatible Mode. Without running in FX Compatible Mode, the Facebook app will not play audio on videos. PLEASE NOTE: Enabling V4A will negatively impact battery life.
Setup the XPOSED framework. Download and install the XPOSED framework installer. I have done all the hard work in this image to get the XPOSED framework to work without any extra steps. If XPOSED is not working for you, please follow the first few steps of this guide.
I do my best to support this, but we all have lives that demand our attention. Anyone is free to contribute to this project and discuss development or features right on this thread. The community behind this system image is pretty awesome. Big thanks to @savagebunny for giving me the drive, info, and support to keep working on V4A. Thanks also to @paintba11er89 for the AdAway suggestion and helping me organize this OP. Huge thanks to paintba11er89 for the help with a very clean OP he used his time to rewrite this post to help me and others so please thank him.
This is only the first step to THE NEXT BIG THING!
DISCLAIMER: I AM NOT RESPONSIBLE IF YOU BRICK / RUIN YOUR PHONE IN ANY WAY.
BASIC COMPUTER SKILLS REQUIRED.
Help:
Read the instructions - There's a lot of great guidelines in there that will answer most questions that you have. If you have issues with Google Apps or Services stopping more than once after you've booted, refer to step 9 in the instructions to clear the phone's cache. Additionally, check out this video that may help with this issue. If you're still having issues, you may have to factory reset and format your data partition to start over clean. That's obviously not optimal, but that's the price that we pay for not having a fully unlocked bootloader.
Changelog:
1.5.5A All in one With AdAway system link, xposed, with or without V4A
Fixed GPU 2x faster benchmark for the GPU video.
Fixed the lag on launcher.
Fixed WiFi scan times. Part of the power saving.
Fixed and updated Build.prop
Removed some startup's apps.
I am removing 1.5.5 on OP and going to replace it with 1.5.5A as there was some bugs With the GPU. So please upgrade to 1.5.5A. Sorry I did not see the drop in 1.5.5 in the GPU speed.
Remember if you do not like adaway just do not set it up. Or if your doing an custom host file it place it in /data/data.
i will keep doing an None V4A for now till i find a way to fix the USB audio out. This is used for amps.
Custom paid ver builds will be updated soon and I will PM you all the links soon.
1.5.4a + AdAway
Download Here
MD5: 0e1411b1e5be9c580e5ce0e0fe9a9e35
1.5.4a + AdBlock Host Files
Download Here
MD5: b1f25360a939a201b1532762000f708b
1.5.4a
Download Here
MD5: 1cbc6a02e4c4e995f65612039b7965dd
1.5.3a + ViPER4Android + Ad-Blocking
Download Here
MD5: e9a272b16506ea62067f055151b61886
1.5.3a + ViPER4Android
Download Here
MD5: 944c745d906f85a858608691ec9446ec
1.5.3 + ViPER4Android + Ad-Blocking
Download Here
MD5: 74efbb3f6e4a21c4b3dcfb492dcc6d99
1.5.3 + ViPER4Android
Download Here
MD5: 9d8543abb8a65b0a697c4b504c0224d3
1.52a + Verizon Visual Voicemail + Ad-Blocking
Download Here
MD5 : ce71e58308f5f7e4e727ae0a7bdc9e98
1.52a + Verizon Visual Voicemail
Download Here
MD5: 2750328e905c71d6a4c7ec1dbd27254e
1.5.2a + Ad-Blocking + ViPER4Android
Download Here
MD5: b4c060813dc08ea20ead2400a1c7becb
1.5.2a + ViPER4Android
Download Here
MD5: 77a6a4cef997992cbc8970518d0f0e76
Is this different then the build on the other thread by Ekkoria because that one is working for me right now.
Does this have full root? Or is it the same as the initial release albeit with the hot spot tethering?
Many Thanks
There are those of us who appreciate the all time consuming work you put in for others.
Thanks again :good:
XF1ber said:
Is this different then the build on the other thread by Ekkoria because that one is working for me right now.
Click to expand...
Click to collapse
I used the stock rooted image from here This IMG is for users on Verizon with an unlimited data 29.99. All others with family share plan or other data plan on Verizon you already get hotspot as part of your plan.
Thanks for your work, hope to see more updates to this!
Thank you for this
Thank you for this, a super good start for the situation were in.
If possible could you incorporate a mixer_paths.xml for louder volumes and incorporate adaway? or an updated host file from adaway?
Seems to me one of those ad removal apps had an option in it to symlink a host file? think something like that would work if it were in the system apps dir, but updating to /data somewhere?
thanks again for all your hard work
PS - Remove that damned boot sound maybe?
Slartibartfast_ said:
Thanks for your work, hope to see more updates to this!
Click to expand...
Click to collapse
WiFi tether works ! What else do you plan on doing? I only really wanted tether to work.
GhostRider5666 said:
WiFi tether works ! What else do you plan on doing? I only really wanted tether to work.
Click to expand...
Click to collapse
To be honest, tethering is not even on my list as my employers pay my bill and it includes tethering.
I'm looking for some xposed modules, adaway, titanium backup and other perks of rooting.
Slartibartfast_ said:
To be honest, tethering is not even on my list as my employers pay my bill and it includes tethering.
I'm looking for some xposed modules, adaway, titanium backup and other perks of rooting.
Click to expand...
Click to collapse
I would like more but I have multiple phones I can use.
this gave me wifi tether. however whenever i try to connect to the hotspot it is saying Limited Connection, and I am unable to use.
-Michael_ said:
Thank you for this, a super good start for the situation were in.
If possible could you incorporate a mixer_paths.xml for louder volumes and incorporate adaway? or an updated host file from adaway?
Seems to me one of those ad removal apps had an option in it to symlink a host file? think something like that would work if it were in the system apps dir, but updating to /data somewhere?
thanks again for all your hard work
PS - Remove that damned boot sound maybe?
Click to expand...
Click to collapse
I will look into the audio boosting if someone can pre-edit the XML I can place it in faster.
acetkbez said:
this gave me wifi tether. however whenever i try to connect to the hotspot it is saying Limited Connection, and I am unable to use.
Click to expand...
Click to collapse
Mine works just fine.
You need to turn your phone off and back on go to WiFi hotspot change ssid and password/key . then start it. You got something locked up with your hotspot if you can not change the settings.
acetkbez said:
this gave me wifi tether. however whenever i try to connect to the hotspot it is saying Limited Connection, and I am unable to use.
Click to expand...
Click to collapse
Working fine I have tested it over and over on 2 phones. My guess is it is windows set the password on the phone longer under wifi hotspot settings and reboot windows. it is working i did not do anything to tether just a bypass. So that is on your side. if that don't work connect something other like an tablet or other laptop.
computerfreek274 said:
Working fine I have tested it over and over on 2 phones. My guess is it is windows set the password on the phone longer under wifi hotspot settings and reboot windows. it is working i did not do anything to tether just a bypass. So that is on your side. if that don't work connect something other like an tablet or other laptop.
Click to expand...
Click to collapse
Its working fine on my phone, I changed the network name and everything.
computerfreek274 said:
Working fine I have tested it over and over on 2 phones. My guess is it is windows set the password on the phone longer under wifi hotspot settings and reboot windows. it is working i did not do anything to tether just a bypass. So that is on your side. if that don't work connect something other like an tablet or other laptop.
Click to expand...
Click to collapse
I tried on my tablet and a macbook and it didn't connect either. I'm not able to change the wifi name or password either.
If it matters I had previously installed the rootjunky image and then put your file over it?
Could that be why it isn't working?
I favorited this thread!
computerfreek274 said:
I will look into the audio boosting if someone can pre-edit the XML I can place it in faster.
Click to expand...
Click to collapse
This is the one the moto maxx guys are using with success, credit to them. I just extracted it from their flashable zip
https://www.dropbox.com/s/66wxkjx40bdbbc9/mixer_paths.xml?dl=0
-Michael_ said:
This is the one the moto maxx guys are using with success, credit to them. I just extracted it from their flashable zip
https://www.dropbox.com/s/66wxkjx40bdbbc9/mixer_paths.xml?dl=0
Click to expand...
Click to collapse
if you can write a mini tutorial to flash it on droid turbo Rooted phones i can credit you and include your text.
Jaocagomez said:
if you can write a mini tutorial to flash it on droid turbo Rooted phones i can credit you and include your text.
Click to expand...
Click to collapse
Sorry, I cannot. I don't have access to a Linux box ATM to build it into the img. the creator of this thread was to incorporate it into the img he's building for all of us to flash using mofo root.
If we had write off its as simple backing up the original /system/etc/mixer_paths.xml and dropping in the new one, then setting permissions and your done. But that's not our situation YET.
Sent from my XT1254 using Tapatalk