[TASKER] tRUE - Tasker Recovery User interfacE - AUTODL CM7 NIGHTLY! | V2.1.2 - 8/16 - Android Apps and Games

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.

Related

[ROM]VIPERrom [TRiNiTY v2.0] EXT4-RFS Dual DK28 4.0.4 - 02/17/11!

..::Team Viper Official Sites::..
Team Vipers Official Site
Team Vipers Official Wiki
Team Vipers Official Ticket System
--------------------------------------------------------------------------------------------------------------
Rodderik's 1.2GHz Overclocked Kernel
Genocide_1.2GHzOC_EB13_Kernel_v0.2a.zip
Genocide_1.2GHzOC_EB13_Kernel_v0.2a.zip Mirror
Give Rodderik a thanks and buy him a beer, He paved the way for the Kernels with the first OC!!
--------------------------------------------------------------------------------------------------------------
..::Thanks::..
Thanks to ACS for the DK28 leak. Thanks to mysteryemotionz for some of the images.
--------------------------------------------------------------------------------------------------------------
..::Changelogs::..
ViperROM [TRiNiTY v2.0] EXT4-RFS DK28 Dual 4.0.4
Added New Theme
Added ViperWheelWidget - Custom Viper Widget
Added ViperPad - Custom Viper App Pad (Based of the Palm's SwipePad App)
Removed A Few Scripts Causing Issues
Returned The Artificial Intelligence Sounds
Added TTS Back Into The ROM
Google Nav Works Again
New Boot Animation
Governor Killer Baked In
AOSP Lockscreen Added
Added New App Icons
Moved Data/Tweaks To System/Bin/Tweaks
Optimized More For Speed & Battery
Changed Browser Start Page - Team Vipers Official Site
Added Wallpaper, Wifi Tether, And Launcher Pro To SDCard (VIPERaddons)
Modified Hosts File
Modified Build.prop
Modified Android.policy.jar
Modified MMS.apk
Themed Dialer
Modified SettingsProvider.apk To Always Allow 3rd Party Apps Install
Added ViperComm Widget
Modified A Lot Of Images
New Sounds
ViperROM [FRoZeN] EXT4-RFS DK28 Dual 4.0.3
New Theme
New Shutdown Animation
New Transition Animations
Removed Some Scripts
Added Data/Tweaks
Governor Killer Baked In
Added A Few New Scripts
Modified For Speed
Modified For Battery Life
New Boot Animation
Custom Sounds - By Team Viper
--------------------------------------------------------------------------------------------------------------
..::ROM Downloads::..
ViperROM [TRiNiTY v2.0] EXT4-RFS Dual DK28 4.0.4
ViperROM [FRoZeN] EXT4-RFS DK28 Dual 4.0.3
--------------------------------------------------------------------------------------------------------------
..::Videos::..
ViperROM 4.0.4 Benchmark Scores
ViperROM 4.0.4 Features
--------------------------------------------------------------------------------------------------------------
..::Screenshots::..
COMING SOON!
SDCARD Partitioning Tutorial.
I know that with EXT4, partitioning the sdcard can be a hassle. Here's a little workaround to help you get it partitioned the easiest way I know without having to mount systems and such in Terminal Emulator. This way makes you flash 2 seperate recoveries, but I would rather do this than the other methods which could take upwards of a half hour or even longer. I've seen people that were working on it for a couple hours. Without further adieu:
NOTE: If you are running RFS, just follow step 1. and you'll be done. If you are running EXT4, skip right to step 2. and follow from there.
1. If you are running RFS, then you do not need to follow any other steps. In the green CWM2.5.5 recovery, just go to "advanced" in recovery and choose the Partition option. It's going to give you two questions for sizes that you want. The first size is going to be the ext size. For this it will give you a few options, but I don't recommend choosing anything below 512. You will see all the options when they pop up, just choose what you feel most comfortable with. The next thing it's going to tell you to select is the swap size. I again don't recommend choosing anything below 128 for this option. You will again see a list of options, so choose what you feel most comfortable with.
2. If you are running EXT4, then follow these steps and you'll be up and running with your new partition very soon. First thing you need to do is gather all the tools you're going to need. Here are the list of tools you will need:
A. One Click Root & Recovery 2.5.5
B. One Click Root & Recovery 3.0.0.6
Quite the long list huh? lol ...I told you it's gonna be simple lol.
Download both of these files (if you don't have one or the other already) and extract them to an easy to find location on your computer somewhere.
3. Ok, you're going to do this just the same as you would if you were rooting your phone from a stock state. And to answer your question that's running through your head right now, No, this will not return you to RFS. You will still be on EXT4 the entire time, so there's not real need to backup your sdcard or worry about having to sit through the backup&restore again. Once again, to be very clear... Even though you are flashing cwm2.5.5 recovery, you will REMAIN EXT4. So let's continue. Make sure USB Debugging is on and plug your phone into your computer. Do NOT mount the sdcard, just have the phone plugged in. Open the One Click Root & Recovery 2.5.5, and run the program. When it's finished, your phone will reboot. Do NOT unplug it until the script is complete. The script will say "Operation Complete. Hit any button to continue" or something along those lines. Just hit a button and the script will automatically close. You can now reboot into recovery and you will see the 2.5.5 recovery with the green letters. If you don't have the green letters, then you didn't run the right One Click, and you should start over using the correct one lol . For those that successfully flashed the 2.5.5 recovery, move on to step 4.
4. If you have the green letters, then we'll continue, if not, repeat step 3. with the correct one click lol. Now that you have the green letters, revert to step 1. When you're finished following the same instructions from step 1, move on to step 5. If you have any issues with anything from step 1. (which you shouldn't, but if you do) click here to go to Mibbit's irc chat website. Along the top left side you will see 2 tabs labeled "Home" and "Connect". Make sure you are on the tab that says "Home". When on the tab labeled "Home", you will see the box in the middle of the page. Right beside the letters "IRC:" is a dropdown box. You're going to click on the dropdown arrow and select "EFNET". Next, you're going to enter your nickname, and finally, beside "channel:" type "#viper" and select "Go". That will bring you to Team Vipers chat where one of us will be able to help you.
5. Now that you are partitioned, it's time to restore the EXT4 recovery. If you do not restore the EXT4 recovery, you will not be able to flash any new ROM's or Kernels, so you MUST restore the correct recovery. To do so, you simply do the same steps. Make sure USB Debugging is turned on and plug your phone in. You do NOT need to mount. Now you simply run the 3.0.0.6 One Click Root & Recovery. Let it run through it's process and it will reboot itself. Do NOT exit out of the command prompt until it says "finished, press any key to continue". Once your phone reboots, you can then reboot into recovery and you will see that you have the orange letters again. When you see the orange letters, you now have a partitioned sdcard and you are back on the correct recovery.
**ONCE THE KERNEL IS RELEASED (Which should be within the next 24 hours as long as my testers don't see any issues) THEN MOVE ON TO STEP 6.**
6. Now that you're partitioned, the only thing left to do is flash the kernel. Connect your phone to your computer and copy the Kernel to your sdcard if you have not done so already. To flash it, just choose "Install zip from sdcard" followed by "Choose zip from sdcard" and simply navigate to where you stored it on your sdcard. That's all. It's quite quick and painless and you should be able to do it all within 10-15 minutes.
VIPERrom Store where everything is FREE!
**Cleaned up post 13 January**
**If you want mods and addons download viperstore from the market**
NOTE: stuff is still being ported to the new edify scripting required for clockworkmod 3.0.0.5 so if something doesn't work submit a ticket from our website and we will get it ported over as soon as we can. For now you can access the store's contents that have been converted here.
VIPERchat in your browser chat.efnet.org (enter your nickname and #viper for the channel name)
VIPERchat Downloadable Version VIPERchat.zip (3.38 MB)
Voice Apps were removed in 3.0.3 to save space but if you want them Voice Apps **UPDATED FOR NEW CLOCKWORK**
Stock Sprint Apps (install .apk like normal):
SprintDK28_Navigation.apk (5.6 MB)
SprintDK28_Nascar(updated).apk (385 KB)
SprintDK28_NFLMobile(updated).apk (510 KB)
SprintDK28_SprintTV.apk (879 KB)
SprintDK28_SprintTVWidget.apk (84 KB)
SprintDK28_SprintZone.apk (367 KB)
First to post on this thread besides u
But yea ill look into the link for you right now
if i find it ill give to u
Edit: Here is the link http://forum.xda-developers.com/showthread.php?t=724171
not sure if that will help will look for some more
Reserved.. always wanted to say that.
Nice and clean separate thread me like...
Do i sense a 3.0.1 update to be sweet! or is the current 3.0 this version?
Hi BT. Thanks for the great ROM. I am using 3.0 right now. What is the difference between 3.0 and 3.0.1? Thanks. Keep up the great work! And one quick question. When I try to install lagfix, everythiing works besides the last step, installing viperspeed. It says I cant install it because I dont have enough room. but I have 185MB free. any ideas?
Link? I hope it's not there or else I'll feel more jerky than usual. Oh and super-thanks for those file names on the battery mods, so important... I have a mess of files like GREENBATMODTHISTHAT with no versions or anything and I guess I didn't realize that I needed to keep mods organized by ROM.
azichek said:
Hi BT. Thanks for the great ROM. I am using 3.0 right now. What is the difference between 3.0 and 3.0.1? Thanks. Keep up the great work!
Click to expand...
Click to collapse
3.0.1 is just a new name for it so if we make updates there's less confusion... It's still the same as 3.0, but hopefully this will eliminate some questions in the thread lol.
3.0.1 = 3.0 ...No new updates yet.
BUT!!!
Rodderik did make the battery mods!, check them out!
azichek said:
Hi BT. Thanks for the great ROM. I am using 3.0 right now. What is the difference between 3.0 and 3.0.1? Thanks. Keep up the great work!
Click to expand...
Click to collapse
I think 3.0.1 is just the updated version of 3.0.
3.0.1 does have the aosp lock screen the 4g is fixed
and couple other things... At least that i think lol
Hope that helps
Added A2SD (Download Terminal Emulator, And type "start a2sd" followed by "launch a2sd" and it will back everything up on your sdcard)
Click to expand...
Click to collapse
Can you please clarify this for me, because I tried earlier and it gave an error when trying to install the terminal. Also I have used linux before but never used a terminal on a phone before lol...can you write down a few steps for us newbies
Again Thank you for your work and to your team
Hey BT there is a app called WidgerLocker Lockscreen which lets you put any widget/app i believe on you lock screen that might be helpful i think..
Just installed it and brought back the aosp lock screen might wanna check it out... Send me a pm of ur email so i can send u the apk cause its a paid app
Another quick question BT, what are the other options for in the lagfix? Are they for future upgrades or not necessary at all?
Hey BT I just want to thank you for all your hard work and your great rom. I hope this hasn't been answered but is it necessary to remove my original root before flashing any of your roms? I have flashed most all of them and I have not deleted it. I'm not having any problems with 3.0. Thank you....
hemi dart said:
Hey BT I just want to thank you for all your hard work and your great rom. I hope this hasn't been answered but is it necessary to remove my original root before flashing any of your roms? I have flashed most all of them and I have not deleted it. I'm not having any problems with 3.0. Thank you....
Click to expand...
Click to collapse
nope you don't have to...just wipe 3x, wipe cache 2x, and wipe dalvik cache ONCE and flash the rom then you are good to go (assuming you are using the correct modem and if not then flash it first with odin)
DAVenom said:
Hey BT there is a app called WidgerLocker Lockscreen which lets you put any widget/app i believe on you lock screen that might be helpful i think..
Just installed it and brought back the aosp lock screen might wanna check it out... Send me a pm of ur email so i can send u the apk cause its a paid app
Click to expand...
Click to collapse
Widget locker is good, I installed it and then moved it to system apps. Works perfectly
Sent from my frozen epic4g
neuton said:
Another quick question BT, what are the other options for in the lagfix? Are they for future upgrades or not necessary at all?
Click to expand...
Click to collapse
2.2 is for the vibrant, minfree is setting the phones task killer settings (I recommend doing this), restoring the boot animation gives you a new boot animation, you can set a schedule if you want, and of course all the uninstall options
Sent from my VIPERrom [TRiNiTY] DK28 3.0
BThomas22x said:
3.0.1 is just a new name for it so if we make updates there's less confusion... It's still the same as 3.0, but hopefully this will eliminate some questions in the thread lol.
3.0.1 = 3.0 ...No new updates yet.
BUT!!!
Rodderik did make the battery mods!, check them out!
Click to expand...
Click to collapse
Haha thanks for clearing that up. I also sent you a pm about a weird lag fix problem i'm having. Thanks BT. The ROM is great.
Rodderik said:
nope you don't have to...just wipe 3x, wipe cache 2x, and wipe dalvik cache ONCE and flash the rom then you are good to go (assuming you are using the correct modem and if not then flash it first with odin)
Click to expand...
Click to collapse
I have the correct modem and 3.0 is working great. I have tried most of the other roms and yours have been the best by far. I thank you guys for that.
When I restore data from cockwork it broke lagfix. Anywork around?
Sent from my SPH-D700 using XDA App
Bt, awsome work, wish I had you for a neighbor. Question, scince going to 3.0 my usb tether stopped working, is it not supported in 3.0 ?

[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Changelog: See our website!
FAQ:
Install as a Flashable Zip? [RECOMMENDED]
Download flashable zip from the OP and rename it "PG06IMG.zip" (without the quotes)
Place in the root of the sdcard
Power off phone (make sure you turn off hot boot or pull the battery when it's off)
Power on the phone holding power and volume down
Follow the prompts to flash it
Delete .zip (PG06IMG.zip) after booting
Enjoy
How to install with Fastboot:
Download the fastboot binary for your computer from HTC
Connect your phone and boot it into fastboot
Run fastboot with the command
Code:
fastboot flash recovery path/to/recovery-twrp-speedy-1.1.0.img
Does this back up Wimax partition?
That is an option if you chose. Recommended to make at least one backup of just wimax and store that somewhere safe.
The screen went black after doing [insert random function]. What is the issue?
When testing the recovery early on we noticed fastboot wasnt a stable way to flash the recovery. Random issues would arise after using the method. As a result and a solution, flashing the recovery via the PG06IMG.zip is recommended to avoid such issues. Please try this as a solution.
I found a bug! What do I do?
Well you're probably going to want to post here and see if other people are having the same issue. We're also going to start tracking bugs on Github along with our project. This will let you see what issues we are aware of. You can submit a bug here: https://github.com/TeamWin/Team-Win-Recovery-Project/issues Be sure to include how you came about the issue as well as list your device and how you installed twrp.
Have a great new feature idea for TWRP?
Submit it on our Github page! It'll help us track it and notify you of the progress. https://github.com/TeamWin/Team-Win-Recovery-Project/issues
Why should I use this over ClockworkMod?
While all three recoveries offer roughly the same abilities (backup, restore, flash) we feel like ours adds a bit more in addition to the basics as well as blend some of the more useful features. A few differences to hightlight:
USB Mass Storage mode (Not in CWM)
Re-organized menus with most commonly used features on top
Saveable settings for all preferences selected
Date and battery display (configurable timezones)
Ability to auto-reboot after flashing
Color themes
Capacitive button support
Go a head and give it a try! You've got nothing to lose. If you don't like it you can always roll back to whatever recovery you want. Of course, shift might go all Emo Pony on us, but he'll get over it.
Sweet! First post! Time to get rid of rom manager!
Teleported from my Shifty Speedy using Tapatalk
Nice! Congrats on the release on the evo shift!
Thank you for this amazing recovery teamwin! Way way better then anyone ever expected! CWM will prolly never be used again lol
Supremely Shifted
ZOMFG!!
yeah, i'm pretty sure this is wood i'm sporting
Yeah, been using this since last night, it is awesome. And clockwork did have USB storage mode, its in the advanced settings, not that it matters anymore.
Found bug....
Rom: CM7 nightly 214(latest)
Kernel: PershootV9
Twrp install method: bootloader
Bug: whenever I go to fix permissions, the green progress bar will go all the way to them end and then freeze... I did it twice to make sure, but i needed to pull the battery both times
Teleported from my Shifty Speedy using Tapatalk
thronnos said:
Found bug....
Rom: CM7 nightly 214(latest)
Kernel: PershootV9
Twrp install method: bootloader
Bug: whenever I go to fix permissions, the green progress bar will go all the way to them end and then freeze... I did it twice to make sure, but i needed to pull the battery both times
Teleported from my Shifty Speedy using Tapatalk
Click to expand...
Click to collapse
Same thing here.. Had to do a battery pull.
Sent from my PG06100 using Tapatalk
Haha... You can still use RM to reboot to TWRP recovery and when I tried to backup my ROM (through RM) (just to see what would happen) it just sends me to TWRP recovery as well...
from the "CRACKED" Speedy EVO Engine...
thronnos said:
Found bug....
Rom: CM7 nightly 214(latest)
Kernel: PershootV9
Twrp install method: bootloader
Bug: whenever I go to fix permissions, the green progress bar will go all the way to them end and then freeze... I did it twice to make sure, but i needed to pull the battery both times
Teleported from my Shifty Speedy using Tapatalk
Click to expand...
Click to collapse
Are you sure you just didn't give it enough time? I've noticed that the progress bars actually bear no relation to the actual progress. I'm fixing permission in terminal now and I can tell you, it takes foreffingever. Haven't tried in recovery yet but I know not to believe the progress bar.
EDIT: In terminal it took 8min 24secs.
good job man. . .thank you
jesusice said:
Are you sure you just didn't give it enough time? I've noticed that the progress bars actually bear no relation to the actual progress. I'm fixing permission in terminal now and I can tell you, it takes foreffingever. Haven't tried in recovery yet but I know not to believe the progress bar.
EDIT: In terminal it took 8min 24secs.
Click to expand...
Click to collapse
Not doubting you! But with CWM it took barely a minute.
Teleported from my Shifty Speedy using Tapatalk
jesusice said:
Are you sure you just didn't give it enough time? I've noticed that the progress bars actually bear no relation to the actual progress. I'm fixing permission in terminal now and I can tell you, it takes foreffingever. Haven't tried in recovery yet but I know not to believe the progress bar.
EDIT: In terminal it took 8min 24secs.
Click to expand...
Click to collapse
I waited a good 5 minutes after the "end" of the progress bar and finally did a battery pull. I was able to fix permissions through terminal, just didn't work through recovery.
Sent from my PG06100 using Tapatalk
noob question but will this also restore backups made from cwm?
hoesnaps said:
noob question but will this also restore backups made from cwm?
Click to expand...
Click to collapse
No. You'll need to make fresh backups
Sent from my PG06100 using Tapatalk
Sweet new recovery. Does it support partitioning of sdcard yet? I think I'll wait for TWRP 2.x
Sent from my PG06100 using xda premium
sparksco said:
Sweet new recovery. Does it support partitioning of sdcard yet? I think I'll wait for TWRP 2.x
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
It has the option to partition but I haven't tried it yet... anyone?
Sent from my PG06100 using Tapatalk

[ROM] Androot-N7p-rom for Nextbook 7 Premium

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

[APP] Boot Manager Pro - Dual boot unlimited ROMS! [WIP]

Hola peoples!!! Ok so I just thought I'd create my own thread on this matter. Mustangtim started one in apps and themes (and here is the link to that thread) but since I'm taking over this project it was brought to our attention that this should be in the dev section as its no longer just an app.. I am actually tearing .imgs apart trying to figure out what the deuce.
FIRST OFF THIS IS A WORK IN PROGRESS, WE ARE NOT YET FULLY SUPPORTED. HOWERVER I'M DOING MY BEST TO CHANGE THAT.
Secondly if you want to help get this started please visit the market and grab the app here. Its a $3 dollar app for unlimited amount of roms, based on your SD card storage capacity anyway. And speaking of which you need AT LEAST a class 4 or better SD card to make this run smoothly.
Also feel free to visit the forums at http://forum.init2winitapps.com/
Ok so here it is, Boot Manager Pro. Its been a long time coming for the g2x to dual boot. First off let me say long story short, I currently have a bootable SD Rom, known as ROM1. I have yet to be able to recreate my findings tho. But it works and it doesnt brick at all. However it is a bit laggy on my class 4 SD card. Luckily I've already done my research on this project as there are many threads of such awesome info so I'm just going to be lazy about it and quote the good people of xda versus re-writing it based off of their info.
ChrisDDD said:
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of its own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, & boot. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flash able backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So basically upon installing the app you need to setup your phone so that way you can properly install a ROM, follow these steps:
1. Go into the supersu(or superuser app) and then go to settings then disable logging or click none.
2. Then go into the BMP app and press the menu button on your phone, not the app, and go to settings. Once in settings put a check mark in force large boot.img, screen on during install, and then go into variables, leave tegra alone but change the sdcard block to show mmcblk1p1. Then press finish and let the app restart. By the way I didnt change any of the sizes of the .imgs but feel free to do so. But be warned do not decrease the size of the system.img only increase it, if desired.
3.Then after you've done the above you need to setup the phone rom. Click on 'Setup Phone' under phone rom and follow that process to setup your phone rom.
4. Once your phone rom is setup you may begin to install a zip to rom1 or rom2 or whatever slot you want. This is the tricky part. I have done tons of reading and most people say that if your using CWM, which us g2x'ers do, then you will probably have a better chance of getting a bootable rom by restoring from a nandroid backup you did versus installing new.
5. So after you decide which path you will take, nandroid backup or fresh rom install, choose install. If you choose a fresh rom, wipe system, data, and cache right away. If nandroid, then wipe after the install.
6. Now once you have clicked install put your phone down, DONT MESS WITH YOUR PHONE AT ALL! PUT IT DOWN AND WALK AWAY OR SOMETHING! Don’t mess with it, text from it, xda from it, dont even use the screen as a mirror!!!! lol seriously the app is picky and while under the .img creation process you want nothing to mess that up or you will not get it booted. You may however drag down the notifications bar to follow the progress of the install.
7. Once its complete, tap the install complete notification in the notification bar and let the app do its thing to finalize the install and get you back to your rom selection screen. Now if you did a nandroid back up here is where you click 'manage slot' and then factory reset the backup you did. Just do it, dont ask why.
7.1 Also so if you desire to install gapps and/or possibly a different kernel, now would be the time to do so while your here. I have read mixed reviews of doing this process right after the rom installs. However when I set up my rom1, I booted into it first all happily then realized I had no gapps. So I had to reinstall BMP on rom1 then boot back to phone rom and then I installed GB gapps and had no issues booting back into rom1.
8. Once the above steps are done if your feelin lucky go ahead and tap on boot the rom you installed, and if all goes well it will boot up.
9. If it boots up you need to post confirmation here!!! Provided info such as phone rom and the info on the sd rom you used and slot number and such.
Hopefully it will just work for you. I have done all the above steps using HFP 2.1 as my phone rom and only been able to get 1 bootable rom. Being it was for testing I used HFP as my phone rom and as well as my rom1.
So if the above steps dont wortk out for you and your boot lopped or what ever, then turn your phone off and reboot into cwm. You have 2 options to resolve the boot issue you just created. 1, you may go to restore then advanced restore then restore your boot. Or 2. select install a zip and nav to the bootmanager folder then phone rom then flash the update zip there.. then reboot and you should be back at your phone rom.
Here is a basic run down of everything that I have done so far:
When I first started working on this project I wasn’t doing any dev'ing to change any of the stuff in the boot.img. I just changed settings in the app per all the research I did. So when all was said and done I restored HFP 2.1 to ROM1 and it actually booted!! And it works lovely btw.. I can still boot into this rom today. I then decided to pass the word and ways that I created the working rom1, well I nor anyone else I passed the info to was able to get it working. Only one other person was able to confirm that rom1 works but only after I copied all my rom1 info and sent it to him for testing.. and he was able to boot into my created rom1… As I see it, it was a blue moon event that I have yet to repeat. So I thought eff it lets do some dev'in so I unpacked the boot.img from rom1 then compared that to the unpacked boot.img from rom2 that I created in my trial and error experiences. So in doing so I noticed 4 differences; 1, the mount points obviously, 2, in the sbin folder had a ueventd file from the working rom1 was a text file viewable by gedit in ubuntu. In rom2 it was just a non-readable file. 3, in the init.rc file was also missing a chmod command for system, (the command is in rom1 but not rom2) and 4, there was a ueventd.tegra file that was in rom1 that wasn’t in rom2, but everything else is the same. So I decided to plug and play with the differences to see if she boots and no go. I don’t understand why its boot looping because I am using the same rom as phone rom as for rom1 and rom2. So it boot looped. So I had to restore my boot.img many times in cwm.
So then I said eff it lets do some more research, then I noticed in the .zips folder plus the individual rom folder there are .zips that will let you flash via cwm if you get boot loops and 'should' get you booting to your desired sdrom. I then tried that way and no go.. so then I opened up the zip and had a look at the internals.. first there is the moveboot.sh file that the app runs in cwm flash the given boot.img. I then checked out the meta-inf and opened up the updater-script thinking that the app wasn’t actually flashing the boot.img which is why it loops... Well I think im half way right. However the script itself is lil dodgy... first thing I noticed was at the end of the script they have a command to cp the log from /tmp to /sdcard/bootmanager well the command was wrong so it never copied the log. So I fixed that. I also saw that the assert command was pointing to ‘boot’ instead of mmcblk0p5, so I changed that too. Then I decided to do away with the assert command and the moveboot.sh file they have going on to utilize the same functions that the kernel zips use, which is a kernel folder that holds the boot.img and a run_program that dd's the boot.img to 0p5. plus I even updated the update-binary that the file uses. I used the one from the g2x nullifier as I know that one was made for our phone and should have no issues.. plus there was a noticeable difference in the sizes of the provided binary to that replaced binary. So with the updated.zip file I then rebooted into cwm to flash that being that I was using a different command to flash the boot.img as well as the other changed stuff and still it boot looped. So as of now the only thing I don’t think ive done was grab the boot.img from rom1 then change the mount points, only change that, and then use that for rom2 and see if it boots. I don’t think I’ve done that yet. But every dam process I do I get boot loops. So basically I have came to the conclusion that it’s now NOT a boot.img issue being that I have done everything to change the boot.img and to make sure it flashes, which it does indeed and now creates the log too… I think maybe it has issues with the system.img as that’s what comes next in the boot process. But that’s just my hypothesis. I won’t be able to confirm this till I liberate rom1’s boot.img then change the mount points to point to rom2 and then see if it boots.. if it don’t work then that would mean to me that there is an issue with system.img created. But that’s just my hypothesis…
What I don’t understand is why the eff when I didnt hack the app I got a working sd-rom, but when I do change some stuff with it still don’t work!!???!! I guess maybe ill just edit/hack the apk to see what’s up.. This is getting way more complicated than it needs to be, since it worked prior to all my major changes to the script its using for flashing and the boot.img and what not. Anyone have any ideas feel free to add them.
My next steps are to edit rom1 boot.img one last time to change the mount points to point to rom2 and then if that’s a no go then it’s got to be the system.img that’s getting created. By the way this whole process I have only been restoring my nandroid backup for HFP 2.1. I have not attempted to flash new as with thru my research more times than not people would get a bootable rom via restoring versus flashing new.. so if anyone wishes to experience an sd rom let me know, ill send you a link to download my rom1 to get it going. Mind you that its not perfect and you need a class 4 or better sdcard. Everything works but it just takes a bit longer to load things and get things cached as its on the sdcard and not nand. Also if you have any input or are wishing to help pm me I need more heads to get this sorted as I can’t be the only one who knows how to edit scripts and unpack imgs and such. Either way I will continue to do this until I get it right damit!!! Oh and I just ordered a class 10 sdcard to help with this process…
That was copied from the other thread that mustangtim started. Last night when I went home the first thing I did was change the mount points on rom1 to reflect rom2, I changed nada else, then I tried to boot it... it boot looped. So maybe its a permissions issue or the system.img.
So just as a proof of concept and before anyone calls bs on my work/findings Here is the link to my rom1 that boots and is HFP2.1. *Update, 'm just going to
leave it on my DB for now till I find something better I guess. xda wont let me attach the file since its 233MB. Oh well here is the link :
Code:
[URL="http://db.tt/eBZwrOrs"][U][B]Here it is, my Rom1 HFP 2.1[/B][/U][/URL].
I have also attached my updated script file to flash back to rom1, for now.
The boot.img points to rom1 instead of phone rom, ill add to phone rom
as well, just not the now. :) Feel free to flash this via cwm versus
restoring...
Also this is part of the this: the ‘.zips’ folder you need to replace the file in
that folder as well. It’s an update file for rom1 to flash the boot.img.
..
If you’re going to use this you need install a random rom to rom1 then replace those created files in rom1 with these files in the 7z file..
So I am doing this new thread to get the devs or people with know how to help me out with my findings. I have edited the boot.img so much I could pretty much re-write everything in there by now including using magic to create to my own kernel eff!! lol jk but seriously I need people with knowhow to provide confirmation of go or no go. Basically I have people whom have helped out but It seems that I'm the only one who has dug this far into this app(unless i've been misinformed) and I have no one on my level to talk with except the init2winit devs. Which are very helpful btw.
And lastly:
Conap said:
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Click to expand...
Click to collapse
or post here or PM me, I'm always down to help out.
Also thanks go to the init2win team, Gflam and Conap as they started this app. and as well to Mustangtim as he brought me into the light of BMP.
So you got all that???!!!??? Now lets get this party started and get full support for dual booting. I will not rest until I get this working. Thanks for your time and possible assistance.
Ok so since I have a book above I thought this is a good place for links and such...
So just incase anyone is curious, here is the Official Boot Manager Manual
Here is a nice link for Tips and Tricks while Installing ROM's that so far has good info to help you watch via adb what the BMP is doing in its creation process.
Some FAQs:
When should I set up my phone ROM?
Set up your phone ROM EVERYTIME you install a new ROM to your phone so you can get back to your phone ROM and won't get stuck on your SD ROM.
My SD ROM seems to lag how can I fix this?
SD ROM lagging may be due to a few things which all have easy fixes. First fix is that most of you have class 2 cards which are what usually come with your phones. These have a much lower read/write then cards of a higher class, we recommend a class 6 card or above. Another easy solution is overclocking merely install a better kernel and use CPU Boost (or any other overclock app) to overclock your phone.
Can I nandroid my SD ROM slots?
Yes and no you can't nandroid them in the traditional sense of the word using recovery but this app works as a recovery for your SD ROM slots and you can back up your ROM slots within the app in the Manage Installed ROMs section which works as a nandroid for your slots by fully backing up your slots to your sdcard which can later be restored.
What if I want to change the sizes of my images, how may I determine the individual sizes easily?
Easiest way is to open up terminal emulator in your app drawer. Type 'su', then grant permissions if need be, then type 'df -h' and it will display such information. You may also use adb in the same fashion. Connect via usb, open up command prompt/terminal and get adb connected and then type 'df - h' again and the same info will show. I will say this again just because, do not decrease the size of your system.img ever! Unless you want mad issues!
Here is the changlog link and just for heck of it the info based on that link:
Code:
V3.2.6
Fixed DroidX/Droid2 Install issue
Fixed UI theme issues
Fixed issue with spaces in name of pic when selecting photo for screen shot
V3.2.5
Fix to allow continue of install if no boot.img is found.
V3.2.4
Added support for HTC Rezound
Added support for rom's with multiple boot.img's
Added support for rom's made for multiple phones
AutoDetect sdcard for usb mounting
Fix for installing ICS gapps
Optimized SDRom Install process
Added support for Motorola RAZR
Added install queue
V3.2.3
Fixed issues with rom's not showing when on emmc on Droid Incredible
Fixed issues with not showing correct booted rom in app
More improvements to sms sync(all rom's will need updated app for changes to apply)
Fix issues with loader
Fixed issue with switching to backup server when main server goes down
Fixed 1x1 widget to show unlimited rom slots
Added 2x2 widget that works with unlimited rom slots
V3.2.2
Fixed force close for img's over 1Gb when resizing
Fixed current booted rom displaying correctly on gnex
Fixed issue with wrong busybox downloading on gnex which should fix alot of install/boot issues
V3.2.1
Fix for errors causing installs to fail.
Fix for some of the licensing stuff.
Removed sdbooster prefs from Galaxy Nexus(Since they don't have sdcard).
V3.2
Changed 4 sd slots to infinite slots!
Galaxy Nexus Support
Sms and Call Log synced between ROMs (you choose what ones too also requries updating boot manager in all slots)
License Check extended to a week
ROMs do not need market installed for boot manager to run (requires updating boot manager in all slots)
Hide su toasts (superuser elite only)
Fix for force close when setting screen shot in MIUI rom's
Thunderbolt defaulted to force large boot.img
Fixed unsupported device using a key
Manually setting variables only accepts numbers
V3.1.1
Fix for various force closes in rom installs and Nand restores
V3.1
Added su binary check
User selectable colors for everything
Better navigation (press title for quick action)
Added compatability for new twrp backups
Better compatiblitlity with memory tweak scripts(i.e. supercharger script and liquids default scripts)
Fix for install process being killed by android
Fix for some themes erasing img's
Fix more force closes during install
Force smaller boot.img option in settings(Fix for some phone's who's boot.img won't fit on the phone after BootManager edit's it)
Improved gapps checker
Improved security
Boot Manager now accepts keys pay for by paypal (see http://init2winitapps.com/stories/BootManager.html)
Added Evo 3d GSM Support
Added notifcation sound/vibrate for finished install (turn on in settings)
Improved data check
V3.0.3
Fix some force closes
V3.0.2
Added backup server (Sorry our server dropped out)
Fixed some force closes
2nd init fixes for Liquid's ROMs
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
V2.0
Install now runs from the foreground (status bar)
Restore Nandroids to slots also in the foreground
User can cancel installs as they run
4 new themes added including one by apophis9283
Some phones such as tb moved to new install code (Fix for some sense rom's)
V1.3
Added third theme to app (Red Theme)
Added 4x1 widget and new widget styling
Fixed in app messenger
Added support for Htc Evo 3D
Added support for Htc Sensation
Added Support for Htc Incredible 2
Added Support for Htc Incredible S
Added Support for Htc Desire S
Added support for LG Ally
V1.2
Added option to reboot to phone rom to install gapps in license check dialog
Better error checking and error logging
Automatically install's ext2 libs if not present
Moved Set Names to Manage rom's
Fix for add-on's not installing correctly
Better compatiblility for rom's that use data2ext or apps2sd(user must set larger img's in manual variables)
Trash cleaner added to extras
Better Fix for WiFi issues on Droid 1
Added display to show what rom you are booted into
Fix for updater-script not found errors
Added support for Htc NexusOne
Added support for Htc MyTouch4G
More compatiblity for ext4 support
V1.1
Fix WiFi issues on Droid 1
Fix bug in rom installer for setting permissions correctly
Fix bug for cache size not setting correctly in setting variables manually
Fix for decimals entered into partition sizes causing force close
Fix force close in widget
Fix force closes in installer
Added Wipe data/Factory reset to Manage Rom's section
Added code to show what file's are being unzipped in dialog
Added support for rom's that extract files to sdcard so the files actually end up on your sdcard
Added support for Htc Desire (apps2sd and data2sd rom's support is experimental. Please email if you test it and it works/doesn't work)
Added support for Htc Inspire4g
Added support for Htc DesireHD
Added option to use ext4 filesystem if rom's support it-Experimental Won't work with all rom's.
Added log.txt file to sdcard to log errors during install
V1.0
Initial Release
YEZZZ
glad to finally see this here!
jookdakang23 said:
glad to finally see this here!
Click to expand...
Click to collapse
indeed... hopefully it wont be before too long that I get this app fully supported for us!
This app will be extremely useful for G2X owners and makes the G2X more versatile and desirable.
da-pharoah said:
indeed... hopefully it wont be before too long that I get this app fully supported for us!
Click to expand...
Click to collapse
idk how you get it booted. lol i keep getting bootloops
jookdakang23 said:
idk how you get it booted. lol i keep getting bootloops
Click to expand...
Click to collapse
Are you using the files I supplied or the ones that BMP created for you?
Woo hoo good job bud
Sent from my LG-P999 using xda premium
x0xhellx0x said:
Woo hoo good job bud
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
LOL thanks bro.... Go Team Hellfire!!!!
da-pharoah said:
Are you using the files I supplied or the ones that BMP created for you?
Click to expand...
Click to collapse
i remember requesting the files but think you ever sent them
jookdakang23 said:
i remember requesting the files but think you ever sent them
Click to expand...
Click to collapse
no we had a miscommunication due to our avail times and GB's lacking ability to utilize two accounts on gtalk.... I have posted those files in the op however...
First, I want to thank everyone who has helped with us on this app. Second, I know I picked the right man for the job, did you see that OP! All kidding aside, a lot of you know I write for ACS under screen name artifintel. I just had too much on my plate to give this project the attention and direction it needs. The right guy is in charge, he's a stand up person and very knowledgeable with this app. Good luck everyone!
[email protected]
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Rafase282 said:
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Click to expand...
Click to collapse
what rom are using as phone rom? and you installed to rom1?
da-pharoah said:
what rom are using as phone rom? and you installed to rom1?
Click to expand...
Click to collapse
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Rafase282 said:
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Click to expand...
Click to collapse
and no bootloop you say?? well then it may be the stock rom your using... The app is very picky and if you get a bootloop, I feel that those can get booted with tweaks... but stuck on lg screen is just no bueno.. Try a different rom... maybe one that has its partitions at ext3 format just to try it.. I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
hands down, a badass app...
SiL3nTKiLL said:
hands down, a badass app...
Click to expand...
Click to collapse
lol +1 for sure!
da-pharoah said:
I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
Click to expand...
Click to collapse
positive on ext4

[FP8A][Rom][Cwm]Tweaked Lite 1.0

Hi again Well it took me a bit, but as there was another OTA, it seems I finally got around to getting a new build together. Now up front it should be noted the slight tweak to the name... This stems from the fact that the newest build is in a way a step back from those that came before it, at least in two very large ways:
1) I did not personally carry over all of the themes that had been made for earlier versions of Tweaked (I did bring over the base Black and Blue by @stranula though)
2) I did not invest the time into porting in all of the lockscreens again
My apologies for not doing these things (at least up front, who knows what the future holds), but time is not what it used to be for me so I felt the sacrifice worth it (hopefully folks agree!).
Now that we all understand the meaning behind the name... let's move on to the usual stuff
I AM IN NO WAY RESPONSIBLE FOR ANYTHING THAT HAPPENS (GOOD OR BAD) AS A RESULT OF FLASHING OR ATTEMPTING TO FLASH WHAT IS POSTED HERE! It seems that there is considerable variability across our phones, so as always YMMV!
If there is anything you would like to see (or wish wasn't there), let me know. I can't promise I'll do anything about it, but such requests keep me motivated and learning - and thats been the driving force behind this ROM since it began.
You will need to have CWM Recovery already installed on your phone - it should work fine on any of the more recent variants but I've had great luck with the most recent one or two (version 5.0.2.7 can be found here or here) - note that some report issues with nandroids, but I tend not to use them so I haven't experienced any issues. Also, I would strongly recommend doing a data wipe/factory reset within CWM before flashing any of the non-update CWM .zips (that's what I've been doing at least and I have had no problems).
As far as kernels are concerned - there is currently only the stock fp8 kernel. Hopefully that changes at some point, but options are limited.
MY GENERAL RECOMMENDATION:
ODIN back to stock EP4D BEFORE you flash anything (which can be found here). Then either flash the three update .zips that are floating around or (likely easier) take the three OTAs to get to stock FP8A. It just makes for far fewer problems.
CWM Installation instructions:
- Backup your current setup/data
- Download file and place on sdcard
- Boot into CWM recovery
- If flashing full ROM package, its recommended to wipe data/factory reset in CWM recovery
- If flashing update package, its recommended to at least wipe cache/dalvik in CWM recovery
- MAKE SURE TO MOUNT /system IN CWM RECOVERY (it should say "unmount" after system)
- Select and install the .zip you put on your sdcard
Download links can be found further down. Let me know if there are any suggestions/issues/etc - happy flashing!
---CHANGELOG---
Code:
Version 1.0 Lite - 8/30/13
- Hacked camera
** can take pics/vids using power/search buttons, when low power, in call; also +2 sharpness as default
- Volume music skip w/ screen off capability
- Added mod version to settings > about phone
- Hacked webcore.so for gif support
- Extended power menu
** cleaned up a bit on this as well
** redid screenshot implementation to use stock apk
- Ported over stranulas Black and Blue theme
- Added in terminal emulator, appwidgetpicker, dlcrutch, playmusic, tweakpapers, LatinIME
- Replaced TW Browser w/ AOSP Browser
- Debloated some things (needs more...?)
- Added in SuperSu v1.51
- Updated Gmail, Maps, Talk/Hangouts, VoiceSearch, Street, PlayStore
- Accurate battery mod (like FP5)
- Custom .png-based shutdown animation support
- .bak-ed poweron and shutdown sounds
- Added in updated tweaktools - should have access to FP8 things now
- Brought over the few build.prop tweaks from FP5
- Swipe-away notifications like in FP5
- Removed samsung setup wizard to use aosp-ish skippable one
- Hid a few annoying notifications here and there
- Recreated same TouchWiz30Launcher edits from FP5
- Added in radiooptions binary
- init.d support
- busybox v1.22 thanks to imnuts
- zipaligned
- TSMParts things
** CRT on/off/both/none
** stay awake
** aosp/stock lockscreens (face still works as well)
** custom lock carrier and text color
** enable vol wake
** enable/disable lockscreens
** custom lock timeout
** custom toggles - like FP5
**** edited swagger and flashlight though - made them better
** same FP5 clock/signal/battery/pulldown/carrier/icon hide/colorizing options
**** no icon flip though
**** actually cleaned up a bunch of code in this process
** steady ring on/off
** on/off for full/low batt notify
** select music pause key when listening w/ screen off
**** NOTE - this kills the wakelock, so it will not turn the music back on
** on/off for screen on w/ unplug/plug
** on/off longpress back to kill
** volume song skip on/off
** on/off lockscreen torch
THANKS GO TO:
imnuts - far too many reasons to list
stranula - for the great theme work
jt1134 - far too many reasons yet again
tonsit - hosting of files, and more importantly creating the awesome tweaktools utility
sbrissen - even more smali tips
jheide44 - for getting me going on the FP8 build, help with tweaktools, and being a tinkering web monkey for TweakedROM.com
cujo6801 - extreme tester, screenshot producer, and rabble rouser
Endless2232 - layout (and general) xml guidance
PaulN64007 - great boot/shutdown animation and icon/widget work
MidnightNinja - image repairs and theme work
fitti28 - rom namer, tester, and theme porter
gunnermike53 - pointers, wallpapers, and touch-ups
chopperthedog - for hooking me up with file hosting stuffs
sircrazy (IRC) - for playing idea raquetball with me
nitsuj17 - tips, advice, useful info, and tireless stifling
crypted for an edited gps.conf file found here - the Google-specific v3.1 version in particular
***** I highly recommend you throw a little cash his way, as this gps.conf is so good due to utilizing network services he provides!
dSlice for all the tweaks research and implementation help
All of TeamSbrissenMod
All the folks on IRC
Anyone else I likely forgot
Beyond the contributions of the above individuals, there were a number of guides found on xda or via google that were used along the way. Some representative samples include:
Swipe-away notifications
ICS animations
Disable low battery notification
Remove clock from statusbar
Extended power menu
Screenshot in extended power menu
build.prop tweaks
A bunch of others that have become buried in my browser history...
[size=+1]TWEAKTOOLS[/size]
Now tweaktools is a bit limited compared to FP5 as there are no themes and a number of the CWM mods were scrapped. That being said, there are some goodies to be had and it can always improve
Here is an edited recap of the FP5 overview of Tweaktools:
Getting started
First off, while you can use adb to run tweaktools from a computer, I'm not going to discuss this route (for those with the knowledge it's totally doable). For those going about things on their phone, here is what you need to do:
1) Open the Terminal Emulator app, then type "su" (without the quotes) at the $ prompt and hit enter
2) At least the first time you do this you'll get a prompt for superuser access - allow this of course
NOTE: If a message appears saying su could not be found, go into the Superuser app - you should see a prompt saying update su binary, which you should agree to, and then all should be well
3) Now at a # prompt, type "tweaktools" (again without quotes) and hit enter
4) You are now in tweaktools - read the screen, make selections, and have a good day.
Installing themes via tweaktools
NOTE: THERE ARE NO THEMES AVAILABLE CURRENTLY!!!
1) Start tweaktools
2) Select the themes option
3) Select a theme you are interested in
4) Here you can choose to view a screenshot (this should open it up in your browser on your phone), just DL the theme, just flash the theme if already DLed, or do a combination DL/flash.
NOTE: Themes are best experienced when flashed over the default black and blue theme - if you are not currently on that theme (or aren't sure what you are on) you should first flash back to that - THEN go through and select the new theme you are interested in. If you do not, there WILL be problems (either aethetic or functional)!
Installing debloated/selected system apps via tweaktools
1) Start tweaktools
2) Select the applications option
3) Choose what you would like to do, which includes:
- Looking through a number of debloated/preselected system apps available through tweaktools and installing
- Removing any of the system apps that have been installed via tweaktools
- Install/remove system apps from your sdcard
NOTE: Remember - these are apps that are going to /system/app - which is different than installing an apk from the play store for example.
Installing CWM-flashable mods via tweaktools
1) Start tweaktools
2) Select the CWM Mods option
3) Choose a general category to look through
4) Select an option. Here you can choose to just DL the mod, flash the mod if already DLed, or simultaneous DL/flash. Also, for boot animation/shutdown options you can choose to view a preview gif of the animation, which will open in your phones browser.
Installing "tweaks" via tweaktools
1) Start tweaktools
2) Choose tweaks menu
3) Select between init.d and non-init.d based tweaks
- REMEMBER: Many of the tweaks require init.d support, which should work on Tweaked Lite
4) Select the option you would like to install
NOTE: For more information on a number of the init.d-style tweaks, check out this thread, which is where tonsit pulled a number of these from, as well as this thread dSlice put together.
Updating rom via tweaktools
1) Start tweaktools
2) Select the Check for Updates option
3) Here tweaktools will check what rom version you are and let you know if there is an update available on tweaktools
4) If there is, choose "y" to install the update
[size=+1]Tweaktools FAQ[/size]
Q: I can't connect/get into tweaktools - what gives?
A: Sometimes servers get busy, so there will be occasions where DLs will be slow, not work, etc. The best bet is to just give it some time and try again in a little bit.
Q: So I am in tweaktools, but my app/theme/cwm mod doesn't seem to stick/flashes REALLY fast?
A: Most situations can be resolved by simply clearing downloads, exiting tweaktools, and going back in after a little time has passed. Another thing to try is to make sure the phone is NOT connected to your computer once the phone reboots to go into recovery. Something else that I have noticed is that If a problem still persists, you can just download the file then manually go into CWM recovery and flash it there.
Q: When I start tweaktools it says there's an update... now what?
A: Well you should update - the only time updates are made available is when something is fixed or some new functionality is added. There are technically two things that can be updated - the launcher (this update will require a reboot into recovery), and the menu (this does NOT require a reboot). You should definitely keep these up-to-date.
Q: Where can I find more information on tweaktools?
A: More information on all that can be done with this incredibly useful utility can be found here or here!
[size=+1]FREQUENTLY ASKED QUESTIONS[/size]
Q: I'm getting a "can't mount /sdcard" in CWM recovery - what should I do?
A: While this doesn't seem to happen often, you can download the ADBsdcardFix.zip here - then extract the folder (should be fine to extract it to your desktop) and attach your phone to the computer via USB (I did this while the phone was already in CWM). Open the newly-extracted ADB folder, and then double-click on the CWMsdcardFix.bat - something should pop up on the screen for a brief second, which is completely normal. After double-clicking the .bat file, on the phone go to mounts and storage, then select mount /sdcard - and it now should work!
All the .bat file does is the following code:
Code:
adb shell
umount /sdcard
rm -f /sdcard
mkdir /sdcard
exit
Q: Hangouts gives me a can't-sign-in error when I first sign in to the phone (i.e. after data wipe, flashing rom, etc.)... WHY YOU BREAK IT?!?!
A: Yeah I'm unsure what the cause is for this (my thinking is with so much initial syncing going on it just gets irritated), but if you reboot your phone (or even just wait a while) the issue will resolve itself.
Q: I'm having overlap issues with statusbar icons and center clock - what should I do? Also notifications aren't clumping like they were before with center clock - what gives?
A: Yup - things may overlap, so you will have to change settings to avoid the issue, or deal with it. And yup, now that center clock is more "true" center, notifications will not clump as they did before.
Q: I set my statusbar to be transparent... but I don't see my wallpaper under it. What gives?
Q: This is more a launcher issue than anything else. I actually edited the TW launcher to make it viewable - and unfortunately behavior of this will vary across launchers.
Q: After first flashing, my statusbar is missing - what do I do?
A: This occasionally happens - it clears up with a reboot. It also clears up after anything activates the statusbar ticker - so doing things like usb connecting your phone to your computer, downloading/installing an app from play store, getting a text - all these things make the statusbar reappear. Note that this only happens after the initial flash.
Q: What the hell is TSMParts?
A: A huge slew of mods and tweaks - here are some notes on them:
Most of the tweaks start at stock-ish defaults.
The statusbar icon tweaks all require a little effort on your part for changes to take effect. All changes can be elicited with a reboot, BUT for most there are other ways:
- Bluetooth/vibrate-silent/alarm icons -- just change their state (on/off or vibrate/sound, etc)
- E911 -- Go into Settings > Location and security... you don't need to do anything else, you should see the change
- Battery/signal -- these just take time... I have yet to figure out a way to get around that - seems a Gingerbread thing...
Q: Why don't you mention blah blah blah in your FAQ? It would be helpful!
A: Because you hadn't told me yet! If you feel something should be added, PM me with exactly what you would have liked to see in the FAQ (so both the Q and the A, and with details) - I of course reserve final editing rights but if I feel the addition is warranted I will add it as close to the original PM as possible.
---DOWNLOAD LINKS - CWM---
Tweaked Lite 1.0 ROM only
md5: 2A352436A8505ED9EC09A555618B90EC
---EXTRAS---
FP8A Deodexed System Apps
NOTE: This is NOT CWM flashable!
NOTE2: You can also use the tweaktools script to obtain a number of these...
md5: F5451D81795EB77EC869F5F484B5BA78
Empty CWM file
NOTE: This is to flash system apps from the above file ONLY - simply take whatever apps you want to flash from the above .zip and put them in the app folder that can be found in the system folder in the empty cwm file .zip. Also, if you select an app that is already on your phone, it WILL overwrite it. What does that matter? If it was modded or themed... well, it won't be any more. It'll be stock. You've been warned.
NOTE2: Again - the tweaktools script can handle this for you. Check it out!
md5: C82269938192B795EAEEE6198F0B9CED
Stock FP8A Files
NOTE: This thread contains a number of useful stock FP8A links
See here and here for earlier iterations of Tweaked, and here for even earlier iterations of TweakStock.
Please let me know if there are any problems/issues.
--------------------------------------------
Here's the screenshot I used before... images all the way back to TweakStock LOL!!!
{
"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"
}
Thank you!
Thank you for taking the time to put this together. Your efforts are much appreciated!
Also, thanks for putting up with all my questions and helping me learn about Android...
EDIT:
End of Support notice posted to my WIFI Only FP8 Beta Project Thread, HERE.
I also left some Tweaked Lite 1.x TweakTools enable WIFI Only Option breadcrumbs!
If you want, feel free to continue to run WIFI Only Media Player Q/A over there... or not.
...that is all...
agreed, nice work. thanks!
I can confirm that everything is in great working order (even installed the wifi only tweak thanks to Jheide).
just to share my process with others:
was on tweaked 3.2 FP5 (with the FP8 modem updaterizer provided by dwith).
backed up everything via TiBu
rebooted to recovery
mounted system
wiped cache/dalvik
wiped data/factory reset
installed tweakedliteFP8
rebooted
reinstalled apps via play market
installed wifi only tweak via terminal emulator (system did not reboot, but a reboot is necessary, so be sure to do so after exiting TE)
restored data via TiBu
a couple of observations:
- I don't get that screeching noise on video playback on videos taken with this phone - YAY!!!!
- some apps such as Google Earth will NOT download b/c the app says my system is not supported (no worries though, as I can restore the app via TiBu)
- Google Hangouts works completely (even tested video chat, and got audio)
Good to see people (dwitherell especially) are supposing the Charge. Haven't been using mine for anything more than a desk clock, but I know there are some people out there still using it and appreciating the work put into it.
A job well done by all of those involved and dwith.
I am extremely grateful for this. :good:
Thank you very much sir. My 3 charges will receive this on sunday when im back from vacation if I can pull the phones away feom my kids long enough to do it. Damn Minecraft....anyway your awesome thanks again
Sent from my SCH-I605 using Xparent BlueTapatalk 2
what lockscreen style does this one actually have?
Not sure yet if I'll install this because I'm not sureif I want to go through the hassle of restoring my phone again but thanks for all your work.
Finally I'm intrigued by your "Empty ZIP" Could I concievable take apks from TiBu and place them in that folder to get a flashable zip?
swing4thefence said:
what lockscreen style does this one actually have?
Not sure yet if I'll install this because I'm not sureif I want to go through the hassle of restoring my phone again but thanks for all your work.
Finally I'm intrigued by your "Empty ZIP" Could I concievable take apks from TiBu and place them in that folder to get a flashable zip?
Click to expand...
Click to collapse
Flash and restoration took less than 30 minutes.
Sent from my XT907 using xda app-developers app
swing4thefence said:
what lockscreen style does this one actually have?
Not sure yet if I'll install this because I'm not sureif I want to go through the hassle of restoring my phone again but thanks for all your work.
Finally I'm intrigued by your "Empty ZIP" Could I concievable take apks from TiBu and place them in that folder to get a flashable zip?
Click to expand...
Click to collapse
Conceivably yes, but in order to truly work it would need a little more (things in /data as opposed to /system primarily) - I would advice NOT using it for this purpose, though it could be a base to use that you could modify to do so with a little research (and trial and error... actually mostly trial and error, at least in my experience lol).
This has two lockscreens - the two I had to do nothing for to add into the rom (beyond allow the one to be accessed). Those would be the usual circle stock one and then sliding-tab AOSP one seen in the screenshot.
apps not working
Iinstalled everything as per directions but I cannot login through Gmail,any ideas?
codelinx said:
Iinstalled everything as per directions but I cannot login through Gmail,any ideas?
Click to expand...
Click to collapse
Need a bit more info... Is there an error or something that comes up? Do you have a data/wifi connection? What if you skip the setup after initial boot and try to add the account after - maybe even after a reboot? I don't have vzw service so I have to skip the initial account setup, then connect ro wfif and add the account after connected.
apps not working
Well I installed the tweaked. Lite Tom 1.0 , withkernel and radios, but do I need to manually install the systems Apps? I cannot access Gmail even with 4g and wifi it immediately states that my email and password do not match. I also have 2 step verification on,would that be the issue with this version of Gmail? The info is correct,ie password and login. Name.
codelinx said:
Well I installed the tweaked. Lite Tom 1.0 , withkernel and radios, but do I need to manually install the systems Apps? I cannot access Gmail even with 4g and wifi it immediately states that my email and password do not match. I also have 2 step verification on,would that be the issue with this version of Gmail? The info is correct,ie password and login. Name.
Click to expand...
Click to collapse
Ah, so you are ok to do things like go into playstore, yes? And the issue is just GMail? There may very well be sonething you need to do to make the 2 step verification stuff happy, but I am not aware of what it is unfortunately. Sorry for the troubles!
apps not working
No playstore, but I'm going to try and remove the 2 step verification.
---------- Post added at 12:03 PM ---------- Previous post was at 11:54 AM ----------
On older androids With 2 step verification you need to generate a unique one time password under manage application specific passwords under >settings >security
Ending on a page labeled :
Authorized Access to your Google Account
Thanks for the update
Hopefully this will keep running strong for a while. Typically in the past when the slow-down-over-time problem happened, reflashing ROM usually fixed it for a bit of time, right?
I've gone through some times where I wanted to toss this phone at the wall.
codelinx said:
No playstore, but I'm going to try and remove the 2 step verification.
---------- Post added at 12:03 PM ---------- Previous post was at 11:54 AM ----------
On older androids With 2 step verification you need to generate a unique one time password under manage application specific passwords under >settings >security
Ending on a page labeled :
Authorized Access to your Google Account
Click to expand...
Click to collapse
I had the 2 step verification for a while also and it was more trouble than it was worth. I had the same issue as you and once I removed it everything was back to normal again. GL
Sent from my SCH-I605 using Xparent BlueTapatalk 2
LockheedX said:
Hopefully this will keep running strong for a while. Typically in the past when the slow-down-over-time problem happened, reflashing ROM usually fixed it for a bit of time, right?
I've gone through some times where I wanted to toss this phone at the wall.
Click to expand...
Click to collapse
Yeah a reflash usually fixed it. There were a few things I did in the past that I sought to avoid this time around with the thought that they were related... only time will tell though

Categories

Resources