Database Info

[SCRIPT][6/19/2011] Inspirefy 1.1 for CM7 nightly - Delete stuff & Replace stuff

Hello, I wrote this shell script to make the CM7 nightly the way I like. It was a pain to do it manually every time I would flash a new nightly.
NOOB WARNING:
THIS SCRIPT IS FOR CM7 NIGHTLY ONLY. IT MAY WORK FOR OTHER CM7 BASED ROM BUT USE IT AT YOUR OWN RISK. IT DELETE SOME FILES ON THE /SYSTEM/APP AND MODIFY YOUR BUILD.PROP FILE. I'M NOT RESPONSIBLE IF YOU DESTROY YOUR PHONE NOR IF YOUR PET DIES AND THINGS LIKE THAT.​​
This script do this:
1) delete some APKs from /system/app that I don't need
/system/app/Camera.apk - replaced by Miui camera
/system/app/Calculator.apk - I use RealCalc
/system/app/FileManager.apk - I use Root Explorer
/system/app/Music.apk - I use the new Music App
/system/app/BooksPhone.apk - I don't use this
/system/app/Protips.apk - Useless
Click to expand...
Click to collapse
2) replace the boot animation with a sharper and bigger version (file size is bigger too)
The original boot animation size is too small for our screen. Some people could car less for this as you don't reboot your phone that often.
Original boot image:
{
"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"
}
New boot image:
Click to expand...
Click to collapse
3) replace the default camera for a Miui camera
We all know the AOSP camera sucks...
Click to expand...
Click to collapse
4) backup and edit build.prop to display "Inspire 4G" as device name
Some people asked how it affect the market and so far so good for me.
I have no idea if automatic backup/restore from Google is working or not. I use Titanium Backup to restore my apps before I login with my Google account.
Click to expand...
Click to collapse
Things you will need:
1) Scripting Layer for Android (SL4A)
Free app. We will use this to run the script.
Click to expand...
Click to collapse
2) Script and other files - RAR version inspirefy_files_v1.1.rar or ZIP version: inspirefy_files_v1.1.zip
All the files needed for the magic to happen...
VERSION 1.1 UPDATE: If you already have the version 1.0 on your phone you can download the attached zip file from this post to update the script to version 1.1 - Just extract the zip file to /sdcard/inspirefy/ and replace the old 'inspirefy.sh' script.
Click to expand...
Click to collapse
How to install & use it:
1) Extract the inspirefy_files.rar (or inspirefy_files.zip) to the root of your sdcard (/sdcard).
You will have 2 new folders (or just 1 new folder is SL4A was already installed): /sdcard/inspirefy and /sdcard/sl4a
2) Install the sl4a on your phone and run it.
2a) Select "run-inspirefy.sh" from the main screen. If it's your first time running the script you must confirm the super user request.
3) After the script is done (about 2s) you can close SL4A and reboot your phone.
Done
You can edit the file /sdcard/inspirefy/inspirefy.sh with your preferred text editor to make any changes you would like, maybe you want to keep the Tips widget
Have fun!
Thanks to dog77k for the feedback and suggestions and everybody who is using this script.

Good stuff LGSilva. Will let you know how things go after I find a free method to extract the rar (don't use root explorer) or when I get to my desk...

Very cool and glad to see this. Nice job
Sent from my Desire HD using XDA Premium App

Just added a ZIP version for the necessary files in case you want to do this on your phone.

forgive me, but I've never ran a script on android before. I loaded up the folders on the root of my sdcard, installed SL4A and ran it. Superuser didn't ask for permissions. Also, I can't figure out how to run what I need to. Help?

poetofsound said:
forgive me, but I've never ran a script on android before. I loaded up the folders on the root of my sdcard, installed SL4A and ran it. Superuser didn't ask for permissions. Also, I can't figure out how to run what I need to. Help?
Click to expand...
Click to collapse
When you ran the script did you get the terminal window output with something like this?
Code:
Inspirefy 1.0 by LGSilva
Remounting system partition rw...
Deleting apk files and boot animation...
Copying new boot animation and camera...
Setting permitions and ownership...
Backuping build.prop and changing device name...
Remounting system partition as ro...
DONE
.
The text is tiny but you can read it. Is there any error message on the terminal window?
Check the superuser app, sometimes it will have the SL4A marked to deny root...
Edit: Just testing on build 103... looks like SL4A is not happy with this build, time to investigate.

LGSilva said:
Edit: Just testing on build 103... looks like SL4A is not happy with this build, time to investigate.
Click to expand...
Click to collapse
They (nightly forum) are saying that the SU app is jacked on 103...

Nightly build #103 have a problem with Superuser not working right therefor my script won't work either.
To fix this download the Superuser from Rom Manager > Extras, reboot in recovery and install it.

dog77k said:
They (nightly forum) are saying that the SU app is jacked on 103...
Click to expand...
Click to collapse
Yep, you beat me to that, I blame the internet

Two suggestions/hints for the inspirefy.sh code:
"chown root.root /sys..." gave me an unknown user/group error, but "chown 0.0 /sys..." worked for me.
I was getting an error when trying to remount /system as ro that it was still busy so I added a 2 sec pause before trying to remount:
Code:
echo -e "Remounting system partition as ro...\n"
sleep 2
mount -o ro,remount -t ext4 /dev/block/mmcblk0p25 /system
echo -e "DONE.\n"
Otherwise the code worked well for me. Great work LGSilva.

I was having problems with SU thats why lol I'll fix it and try this again and update when I'm done

dog77k said:
Two suggestions/hints for the inspirefy.sh code:
"chown root.root /sys..." gave me an unknown user/group error, but "chown 0.0 /sys..." worked for me.
I was getting an error when trying to remount /system as ro that it was still busy so I added a 2 sec pause before trying to remount:
Code:
echo -e "Remounting system partition as ro...\n"
sleep 2
mount -o ro,remount -t ext4 /dev/block/mmcblk0p25 /system
echo -e "DONE.\n"
Otherwise the code worked well for me. Great work LGSilva.
Click to expand...
Click to collapse
Thank you dog77k for the suggestions.
I've updated the script with them and also added a 2sec pause after mounting it as RW just in case...
Files with version 1.1 updated on the first post, no need to reinstall SL4A.

tested and seemed to run just fine on build 104. thanks for the awesome script! very cool

Thank you!
+1 to both of you, thanks for the great scripting solution.

[MOD]viperMOD Bloat Manager v3.1.4 for HTC Sensation | Updated 8.7.11 |

Welcome everyone to viperMOD Bloat Manager, a wonderful little script that manages bloatware right on your device! No more generic scripts uninstalling whatever they want, choose from different presets or choose any app installed on your phone to enable/disable!
Here is what the script looks like...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I like the colors over the standard blue/white
Updated 8/7
Fixed "permission denied" error on flashable .zip by settings perms in updater-script
Updated 8/6
Fixed coding for /system mount
Edited .bat file to mount system R/W before pushing files from PC
Updated 8/1
Updated for perm root (no more /system not mounted issues)
Removed overclock feature - since there are custom kernels now, no need to insmod.
Still a .bat file. If there is a demand for an update.zip, please post.
Updated 7/19
Fixed Advanced menu for HTC Sensation users
Updated 7/18
Enhanced Overclock feature
--- Added Telstra OC driver (experimental, please test)
--- Auto backup OC settings and prompt to reapply if file detected
Disable custom apps and enable custom apps allows manipulation of individual packages within presets
Minor scripting changes
Updated 7/16
Customizable overclock mod right from your phone! (Advanced menu)
Better support for the HTC Sensation
--- Disable\Enable T-Mobile Apps
--- Remove Sprint references on HTC Sensation
Enable custom apps will show packages and apps by presets and allow you to enable things 1 at a time.
Updated 7/14
Totally reworked with many enhancements and fixes!
Better /system detection
More intuitive UI and easier to use from the phone
5 categories of preset bloat disable\enable
--- *Sprint apps, *HTC apps, *other apps, *Rosie, HTC Widgets, and Live Wallpapers, and *Lockscreen
Moved custom options into "Advanced"
Moved backup/restore into "Advanced"
Added option to enable all custom bloat at one time
Warnings when disabling apps (depending on the menu)
Added count for disabled apps
Descriptions of what will be disabled\enabled before doing so
Added pause until enter button between menus (script was too fast )
Added better detection and action when entering an invalid option in all menus
Updated 7/13 @ 2PM
HTC Sensation support!
Allowed script to continue without R/W /system access with warning
Currently disabled bloat list is now sorted alphabetically and without "package:" in front of it
About info updated
Requirements:
Terminal Emulator (recommend setting to 12pt font)
Root Access (I like this one, personally)
Common Sense - please don't disable everything and wonder why things aren't working.
Features
Disable\Enable bloatware
Disable\Enable HTC Sense and HTC Widgets
Disable\Enable Experimental Apps
See what apps are still enabled or disabled
Ability to disable\enable ANY installed app on your phone!
Ability to backup your settings
Ability to restore your settings
Directions and Information
Apps will STILL BE DISABLED when you reboot - rooted or not!
Just download the .zip, extract, and run the viperMOD_Bloat_Manager_v3.1.1.bat file from your computer.
To run this, go into Terminal and type "su" (without quotes) then "viperbloat" (without quotes) and it will run. You can also set Terminal Emulator to run this right when you run the app by going to Menu > Preferences > Initial Command > Press "Enter" > type "su" (all lowercase, no quotes) > press Enter > type "viperbloat" (all lowercase, no quotes)
You can also run this through ADB on your computer by doing adb shell then ""viperbloat" (all lowercase, no quotes). Much easier to read the app list!
You can MAJORLY screw up your phone by using this! Be mindful of what you're playing with and if you really mess things up, just reboot and reroot.
Here is a helpful link to what some of the apps are.
Known Issues
None!
Download flashable .zip HERE
Download .bat HERE​​​​​
Special Thanks to:
Netarchy for some great shell scripting help!
freeza and ffolkes for their initial thread which I based the script on!
agrabren for getting the E3D rooted!
xdviper for the build.prop info needed for Sensation support!
Let me know if I forgot anyone!

giving this a go now. ill report back ;-)

Cant seem to get this to work. i just type viperbloat in adb or terminal emualtor and it says not found. then i type /sdcard/viperbloat and i get permission denied?

ran through terminal emulator and just removed safe bloatware and recommended. no errors and ill report back how it does for my battery life. there is a option that says no recommended and i followed it because i didnt want to start from scratch. So far i give this app a thumbs up.
Thanks for the hard work.

bpear96 said:
Cant seem to get this to work. i just type viperbloat in adb or terminal emualtor and it says not found. then i type /sdcard/viperbloat and i get permission denied?
Click to expand...
Click to collapse
Did you run the .bat file? Run it again.
And I assume you guys have the same deal as the EVO 3D and we are using /vendor for /system (symlink)? That's how I have it setup is to push it to /vendor/bin and chmod. Please let me know.

charlieb620 said:
ran through terminal emulator and just removed safe bloatware and recommended. no errors and ill report back how it does for my battery life. there is a option that says no recommended and i followed it because i didnt want to start from scratch. So far i give this app a thumbs up.
Thanks for the hard work.
Click to expand...
Click to collapse
what exactly did you type in terminal emu?

bpear96 said:
Cant seem to get this to work. i just type viperbloat in adb or terminal emualtor and it says not found. then i type /sdcard/viperbloat and i get permission denied?
Click to expand...
Click to collapse
are you temp rooted already? and when u run the bat file wait till it says press any button to continue than type su in terminal emulator to see if u have permission after that type viperbloat and the app should pop up.

bpear96 said:
what exactly did you type in terminal emu?
Click to expand...
Click to collapse
i typed viperbloat and i got the above screenshot but in white/blue.

charlieb620 said:
are you temp rooted already? and when u run the bat file wait till it says press any button to continue than type su in terminal emulator to see if u have permission after that type viperbloat and the app should pop up.
Click to expand...
Click to collapse
nevermind got it

-viperboy- said:
Did you run the .bat file? Run it again.
And I assume you guys have the same deal as the EVO 3D and we are using /vendor for /system (symlink)? That's how I have it setup is to push it to /vendor/bin and chmod. Please let me know.
Click to expand...
Click to collapse
what app are u using for screenshots? so i can post what i see and what i did....thanks.

bpear96 said:
yes im temprooted. when i type viperbloat in terminial emulator all i get is permission denied?
Click to expand...
Click to collapse
restart your phone. run the final temp root again and than do the viperbloat.bat
you may have made a error so the best thing to do is just start from scratch

I got it to run but my /sytem is r/o

My screenies
Sent from my HTC Sensation 4G using XDA Premium App

Go from my screen shots first line and second line should be diff
Sent from my HTC Sensation 4G using XDA Premium App

bpear96 said:
I got it to run but my /sytem is r/o
Click to expand...
Click to collapse
here too, script fails with the "busybox mount | grep /vendor/system" as there are no /vendor/system on my phone, and the grep finds 'ro' from probably /vendor/firmware ?
in /vendor/ i have bin and firmware directory

Also i cant seem to root now heres what i get in adb http://pastebin.com/gWb0eAsP

Also make sure that the exploit ran to ur Sd card. That may be the cause of the errors.
Sent from my HTC Sensation 4G using XDA Premium App

i changed
systemcheck=$(busybox mount | grep /vendor/system | cut -d \( -f 2 | cut -d \, -f 1)
to
systemcheck=$(busybox mount | grep /system | cut -d \( -f 2 | cut -d \, -f 1)
and got rw
then when disable bloat, i get
/vendor/bin/viperbloat: line 402: pm: not found
/vendor/bin/viperbloat: line 402: pm: not found
/vendor/bin/viperbloat: line 402: pm: not found
/vendor/bin/viperbloat: line 402: pm: not found
/vendor/bin/viperbloat: line 402: pm: not found
repeated maybe 20-30 times

bpear96 said:
Also i cant seem to root now heres what i get in adb http://pastebin.com/gWb0eAsP
Click to expand...
Click to collapse
Are u using the temp root final? I was getting errors as well in the beginning before this mod and I just rebooted my phone and everything worked
Sent from my HTC Sensation 4G using XDA Premium App

charlieb620 said:
Are u using the temp root final? I was getting errors as well in the beginning before this mod and I just rebooted my phone and everything worked
Sent from my HTC Sensation 4G using XDA Premium App
Click to expand...
Click to collapse
yes im sure.. the older v. actually works for me i get root. but the final doent work at all

[BETA][TOOL] adb_bak2computer [MAC & LINUX][UPDATED: 11/15/2012]

BETA TESTERS NEEDED!!
DESCRIPTION: adb_bak2computer.sh
- tool (set of scripts) to backup d2vzw (SCH-I535) partitions directly to a users computer.
{
"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"
}
PROGRESS:
- Beta5 - Now in two flavors, Mac and Linux!!
- Fully functioning tarballs are attached to the OP (as always)
TO-DO/KNOWN BUGS
- Re-wrote the code so it actually works on Linux now. (See the _Linux tar)
- All known bugs fixed. Unless someone points one out.
- To Do: Add functionality to wrap backups into a flashable zip (it'll be a big zip, but its one file to keep track of instead of blobs or sets of img files) This should be the first restore option I explore.
- To Do: Automate a standard backup (include: System, Boot, Data)
- To Do: Automate a set of backups that are compatible with TWRP. Why TWRP, cause I like it, and the differential backups that CWM does will be problematic for this tool. (I may need some help on this one.)
WARNING USE AT YOUR OWN RISK
I am not responsible if this tool destroys your soul, or your phone, or it makes a rainbow rhinoceros shoot out your bum.
NOTE: We all know the risks of doing stuff like this by now right? But the warning is still par for the course I guess. Is there a standard warning file I could link to, and make it all fancy and legal? Kinda like creative commons license only creative warning instead? Moving on...
PREREQUISITES
YOUR DEVICE MUST BE ROOTED
Linux or Mac operating system (maybe Cygwin might work, but I haven't tested it)
If you are on Linux you must have xterm installed (gnome-terminal or konsole alone won't work)
Must have the android SDK installed, and "platform-tools" must be in your $PATH
Process Viewer, "pv", must be installed
NOTE: To check if you have Process Viewer installed run pv --version in your terminal, if its not there download from here and install.
INSTRUCTIONS:
Download the appropriate tar for your OS
Extract it to a folder named "adb_bak2computer" in your $HOME directory.
Chmod everything so its all executable (chmod -Rf 777 ~/adb_bak2computer ).
Make sure your SGS3 is plugged into your machine via USB, and that you have USB debugging enabled.
If you are on CM10 or some other AOSP based ROM check the preference that keeps the screen on while plugged in.
If you are on a TouchWiz ROM use something like Wake Lock - PowerManager and force a full wakelock so your device doesn't go to sleep and or lock out adb debugging.
Run adb_bak2computer.sh from the terminal.
Pick a number
ALL CREDIT GOES TO:
das7982 - for ODIN guide here:
http://forum.xda-developers.com/showpost.php?p=28876440&postcount=1
scandiun - for "nandroid" backup directly to computer guide here:
http://forum.xda-developers.com/showpost.php?p=29862574&postcount=1
(and whomever they credited in their guides as well)
Feel free to fork, download, mod, make it all pretty, whatever you want. Its all open for sharing.
REPOS:
http://github.com/ALQI/adb_bak2computer-Mac
http://github.com/ALQI/adb_bak2computer-Linux
PM me if you want to help me with this tool, or just want to have a nice cup a tea.
Ta,
ALQI
REFERENCE THREADS:
El Grande Partition Table Reference -- E.V.A
Unlock Bootloaders -- AdamOutler
Android Kitchen -- dsixda

Look's kinda cool. Can't wait till this is finished!

Why not just use "rsync for android" from the market?
Sent from my Galaxy Note 10.1 using Tapatalk 2

blulite said:
Why not just use "rsync for android" from the market?
Sent from my Galaxy Note 10.1 using Tapatalk 2
Click to expand...
Click to collapse
That's for file based backups, which is great and I love rsync and ssh, but its not what I'm looking for. I want full on partition images going directly from my phone to my laptop (hopefully at USB2.0 speeds). So far the only way that I have seen that can do this is with scandiun's guide here:
http://forum.xda-developers.com/showpost.php?p=29862574&postcount=1
It works. I've tried scandiun's original directions and it does produce viable iamges. What I want to do is automate/simplify that process.
So far, I haven't had a chance to figure out how to get adb to play nice with spawning subprocesses in bash scripts.
like :
Code:
#!/bin/bash
function1(){
echo "function is running"
adb forward tcp:5555 tcp:5555
adb shell /system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd bs=4096 if=/dev/block/mmcblk0p17
}
function2(){
echo "function2 has to finish execution before either function can exit"
adb forward tcp:5555 tcp:5555; cd ./Cache_Test; nc 127.0.0.1 5555 | pv -i 0.5 > ./mmcblk0p17_cache.img
wait
echo "function2 is done"
}
function0(){
(function1)&
(function2)&
wait
exit
}
function0
wait
exit
This code doesn't work though. And I'm pretty sure its because adb needs actual separate terminals (not subprocesses) to run the two instances of adb forward.
This means I need a portable way to spawn new terminals. I've tried xterm -e [command] and that kinda works on linux but not on mac and I doubt it would on cygwin/windows. I may have to re-write this in python, but I'd rather use bash cause not everyone has python installed or is comfortable using it. Also, I'm lazy and I don't want to have to re-write what seems to be perfectly viable code.
Ta,
ALQI
FYI - I thought the cache partition would be a small safe partition to play around with, but its like 800MB on my device. I'll pick another for my next test/example.

Eureka (I think)
Ok, so I have a set of scripts now that can do what I need. That is execute in new terminal windows and play nice with adb.
This script (which can be .sh file), calls the other two .command files and actually backs up my cache partition.
Code:
#!/bin/bash
cd ./adb_bak2computer
open ./cache_bak1.command
sleep 2
open ./cache_bak2.command
wait
echo "cache should be backed up."
Here's the first command file:
Code:
#!/bin/bash
cache_bak1(){
echo "cache_bak1 is running"
adb forward tcp:5555 tcp:5555
sleep 2
echo "/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd bs=4096 if=/dev/block/mmcblk0p17" | adb shell
wait
}
cache_bak1
Here's the second one:
Code:
#!/bin/bash
cache_bak2(){
cd ./adb_bak2computer
echo "cache_bak2 is running"
adb forward tcp:5555 tcp:5555
sleep 2
nc 127.0.0.1 5555 | pv -i 0.5 > ./mmcblk0p17_cache.img
wait $!
echo "cache_bak2 is done"
}
cache_bak2
For some reason I to pipe in an echo of the command I wanted to run in "adb shell".
Also, depending on your terminal settings, the windows for the two command files will stay open even when they are done. To fix that, just make sure your preferred terminal emulator is set to close when a process is complete.
I'd still like to get subprocesses (from post #4) to work but its stating to look like adb no likey.
I'll try and have the rest of the code for all the paritions up within the next few days, I still have some things to figure out though. I can use a menu to seperate the dd instances or loop/wait for the pid's of each instance to quit before moving on to the next partition, I'm on the fence as to whether I want everything to run consecutively or to give users the option to pick each partition they want to back up. Maybe I can do both, but that will take longer for me to finish.
Please excuse the crap typing as I'm doing this all in my "spare" time, which means I should be sleeping.
Ta,
ALQI

Why not just make scripts pull each partition? Adb can simply pull them......
Sent from my SCH-I535 using xda app-developers app

tonu42 said:
Why not just make scripts pull each partition? Adb can simply pull them......
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
IIRC, adb pull is for files only. It can't pull full partition images.
I'm getting full partition images that can be (hopefully) used for Odin restoration and maybe nandroid or cwm restore.
Thanks for the input.
Ta,
ALQI
Sent from my SCH-I535 using xda app-developers app

ALPHA Version
OP is updated with fully functional alpha release of the tool.
Ta,
ALQI

Going to have to check this out over the weekend when I can sit down and read first.
Thank you for providing us with an alternative backup solution.
Sent from my SCH-I535 using Tapatalk 2

ok, so backing up the data block is HUGENORMOUSBIG
maybe mmcblk0p15 is including the internal sdcard because of that /data sub folder link to the sdcard?
I dunno for now, I'm going on 45mins and 6Gigs. I'll have to take a look in teh morning

Just wanted to let people know that this is not abandoned.
I only have one last hurdle. And that's getting an img file for /data without backing up /data/media (which is essentialy your internal sdcard). I can't really do a block dump cause mmcblk0p15 (am I even close there) is all userdata including /data/media.
Any ideas would be helpful? (Hint Hint)
Ta,
ALQI
Sent from my SCH-I535 using xda app-developers app

update ready to roll for Beta testers
alquimista said:
Just wanted to let people know that this is not abandoned.
I only have one last hurdle. And that's getting an img file for /data without backing up /data/media (which is essentialy your internal sdcard). I can't really do a block dump cause mmcblk0p15 (am I even close there) is all userdata including /data/media.
Any ideas would be helpful? (Hint Hint)
Ta,
ALQI
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I got /data backup working (yay me).
OP updated!!

alquimista said:
- Thread title updated with your American way of noting the date
Click to expand...
Click to collapse
My American way of noting the date is an ISO standard... YYYY-MM-DD

OP updated with new beta2 version of the tool.
Github commited as well.
ALL mmc blocks are set for backup now, check in the "CRAZY BACKUP OPTIONS" menu for the crazy backup options.
Next up:
Fix the echo [command] | adb shell scripts not exiting without CTRL+C
Option to have the basic backups turned into an "update".zip
Ta,
ALQI

Beta3
OP Updated with Beta3
Android side adb hang bug is fixed. Yay me.
GitHub updated as well.
Ta,
ALQI

HAAAAALLP!!!
I'm struggling a bit with creating a flashable zip with the files I get using my tool.
Basically I can pick whatever partition I want, but lets just say I want a standard backup and I've run my tool pulling the following:
Code:
boot.emmc.img
cache.ext4.img
data.ext4.tar
recovery.emmc.img
system.ext4.img
Actually, ican name them whatever I want and use whatever I want, so lets simplify that even greater and just go with:
Code:
boot.img
data.tar
system.img
The updater-binary and accompanying updater-script is pretty straight forward for the boot.img and system.img, the script would have something like:
Code:
write_raw_image PACKAGE:system.img SYSTEM:
write_raw_image PACKAGE:boot.img BOOT:
That's a bit of an over simplification depending on the updater-binary I wind up using, but its the right idea (some of the wording might change a bit but the "write_raw_image" part is whats important).
But what do I do with data.tar? Can I unpack that tar directly to "DATA:"? Something like:
Code:
package_extract_dir PACKAGE:data DATA:
I don't know if the updater-binary supports this with a tar??
I could unpack the tar file before creating the zip, but then I have to set all the permissions, which should have been preserved in the tar. Or can I just write a little script to go inside the zip that will essentially "tar -xf /tmp/data.tar /data" and unpack the tarball while in recovery?
I dunno, any ideas??
This would be alot easier if I could workout a way to dd a data.img without including the internal sdcard.
Ta,
ALQI

Beta4
OP Updated with Beta4
Github as well
Added funtionality to backup internal and external SDCards.
Ta,
ALQI

Important: Mac only
I just realized that this code probably won't work on Linux.
I'm on a Mac for most of my work, so I've been making all this on a Mac (OS X Lion 10.7). The "open" command probably won't work on linux or Cygwin.
I just need to add a quick check for for the OS and then use "xterm" instead of "open" for the .command files.
Actually, since I'm doing alot of cleanup and such, I will probably remove file extensions for most of the scripts.
Anyway, sorry for any confusion. I haven't been awake for most of this. But its definately a great big FAIL on my part. Well at least until I fix it.
Ta,
ALQI

BETA5 - Now works on Linux!!
OP Updated (as well as new repos) for new linux version.
Had to seperate out a version for linux cause Macs are dumb and can't open new terminal windows without the "open" command.
Tars are attached to the OP!!

[DEV] - Dual-boot Linux on the Asus Infinity TF700t - JB-4.2[Thread closed]

This was the development thread for the "Dual-boot Linux on the Asus Infinity TF700t - JB-4.2" (now called "Kexecboot Linux on the TF700t").
Any and all developments are in Kexecboot Linux on the TF700t here
JoinTheRealms source is up here https://github.com/JoinTheRealms/TF7...oot-stockbased.
Recovery flashable Kexecboot and Kernels Installer
I have made a flashable zip to do the work for me(and you). This zip is a modified version of _that's kernel installer. It will install the kexec blob, boot.cfg, and the Andriod kernel of your choice - CROMi-X, that10 or CROMBi-KK, that-cm112. The that10 installer also includes the needed modules (I will see what is needed for CROMBi-KK at a later date).
Flash the proper zip file below using the newest TWRP:
Please make sure you have a BACKUP (also dd backup your mmcblk0p5 partition for safety) and have either the stand alone that10 kernel installer or CROMi-X/CROMBi-KK ROM's on your tablet as a safety net.
I am including the md5's on these files until I figure out how to sign them... :silly:Done, thanks _that!
CROMi-X 5.4 - kexecboot_installer_for_CROMBi-X5.4_v1.0_Signed.zip -
CROMBi-X - kexecboot_installer_for_CROMBi-KK_v1.0_Signed.zip -
Change log:
5/23/2014
v.1.0 Installs kexec blob, boot.cfg, Android kernels (that10 and that-cm112) and modules(that10 only)
Click to expand...
Click to collapse
Manual kexec blob, Android and Linux kernel install info
1. Android Kernel
You must have a fully stable CROMi-X 4+(TWRP 2.5+) or CROMBi-KK (trwrp_that-2.6.3 or TWRP 2.7) install to use any of the following (See this forum, here, for ROM details)
(If you are on stock rooted only, see rabits old thread as this is your only option, here).
The example boot.cfg is usable as is (if you read the file and have use of any of the common choices it describes.)
---CROMi-X (Remember this is only for _that stock. No f2fs,rom2sd or data2sd)
1)From Android "Terminal Emulator" mount /system r/w and make dir /system/boot and extract that9oc-kexecboot-android-05082014.zip or that10-kexecboot-android.zip to /system/boot/
The following assumes you copied or downloaded that9oc-kexecboot-android-5082014.zip to the Download folder
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
mkdir /system/boot
cd /system/boot
unzip /data/media/0/Download/that9oc-kexecboot-android-5082014.zip
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
2) Reboot into TWRP
3) From TWRP, flash kernel-10.6.1.14.10-that9-oc.zip or kernel-that10.zip and reboot to Android (See _thats thread for kernel details)
4) Back in Android, mount mmcblk0p5 as root and copy your this example boot.cfg into /mmcblk0p5/multiboot -
BIG RED WARNING - Do not mess with any other files on this partition or you will most likely have yourself a paperweight...
The following assumes you downloaded or copied boot.cfg the the Download folder
Example Code:
Code:
su
cd /data/media/0/Download
mkdir kexectemp
mount -t vfat /dev/block/mmcblk0p5 kexectemp/
mkdir kexectemp/multiboot/
cp boot.cfg kexectemp/multiboot/
umount kexectemp/
---CROMBi-KK (Remember this is only for _that stock. No f2fs,rom2sd or data2sd)
1) From Android "Terminal Emulator" mount /system r/w and make dir /system/boot and extract that-cm112-kexecboot-android-4272014.zip to it
The following assumes you copied or downloaded that-cm112-kexecboot-android-4272014.zip to the Download folder
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
mkdir /system/boot
cd /system/boot
unzip /data/media/0/Download/that-cm112-kexecboot-android-4272014.zip
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
2) Mount mmcblk0p5 as root (ex. mkdir somewhere/temp, mount -t vfat /dev/block/mmcblk0p5 temp/) and copy your this example boot.cfg into /mmcblk0p5/multiboot -
BIG RED WARNING - Do not mess with any other files on this partition or you will most likely have yourself a paperweight...
The following assumes you downloaded or copied boot.cfg the the Download folder
Example Code:
Code:
su
cd /data/media/0/Download
mkdir kexectemp
mount -t vfat /dev/block/mmcblk0p5 kexectemp/
mkdir kexectemp/multiboot/
cp boot.cfg kexectemp/multiboot/
umount kexectemp/
2. Linux Kernel - This step is only needed if you aren't using one of the example rootfs below.
Be sure to read the readme files included in the zip file by conago.
1) Mount your Linux .img file or extract your rootfs as root on your Linux PC to a temp directory
2) Extract linux-kernel-tf700-kexec-that10-cogano3.zip ,by conago,to a temp directory
3) Copy the /boot and /lib folders to the root of your rootfs
4) Unmount the image or zip up your rootfs files.
Hint: Running the following commands will result in a new rootfs.tar.lzma that can be installed with the rootfs only installer above.
1) cd into partition mount
2)arch - sudo tar cp --exclude=lost+found --exclude='proc/*' --exclude='proc/.*' --exclude='sys/*' --exclude='sys/.*' --exclude='dev/*' --exclude='dev/.*' --exclude='tmp/*' --exclude='tmp/.*' --exclude='var/cache/pacman/pkg/*' $excludes . | lzma -9 > ../imgagename.tar.lzma
or
ubuntu - sudo tar cp --exclude=lost+found --exclude='proc/*' --exclude='proc/.*' --exclude='sys/*' --exclude='sys/.*' --exclude='dev/*' --exclude='dev/.*' --exclude='tmp/*' --exclude='tmp/.*' --exclude='var/cache/apt/archives/*.deb' $excludes . | lzma -9 > ../imgagename.tar.lzma
Click to expand...
Click to collapse
3. Flashing the kexecboot kernel blob - (done from Android using "Terminal Emulator") with 10 second time out by conago
1) Extract kexec-host-2014-05-22.zip to a temp dir, cd into it and then carefully type the following as root:
Again - BIG RED WARNING - Type carefully or you will leave your tablet unbootable or WORSE. And please read the README file in the zip.
Code:
dd if=blob of=/dev/block/mmcblk0p4
Reboot and profit!
Post install
Now included in the menu driven Android kexecboot Installer
Use the following script from Android AFTER you have a working install to modify the
boot.cfg file to your setup. It helps to rename the labels to something you can remember.
Extract to your favorite place and see the readme file.
modify_boot.cfg_v1.0.zip
Old, Old thread content here:
Great kexecboot tutorial by @cogano (here) - This gives some good background for the regular installer as well.
For those running CROMBi-KK w/_that9-oc+(modded for cm112 by @lj50036 ), I have a quick rundown of what you need to do and the necessary files (ie cm112 android kernel) here
Disclaimer! This is very experimental and may damage your device.
Suggested Requirements - TWRP 2.5+ and CROMi-Xenogenisis 4+
If you are on CleanROMv3x see rabits old thread - http://forum.xda-developers.com/showthread.php?t=2014759
Known issues:
1) Try to start or restart lightdm and it says - read-only filesystem. You need to fix this from Android, terminal emulator
Code:
su
Code:
e2fsck /data/media/linux/rootfs.img
This happens when you force restart or shutdown linux sometimes
You will find links below to the latest (still beta!) installer and some rootfs images.
For both Ubuntu and Lubuntu - Username: ubuntu Password:ubuntu
Lubuntu rootfs:
FYI - The Lubuntu rootfs is a work in progress and has been stripped for YOU to customize. Even though the download size is larger (install is 2.6gb), this runs way faster and uses less ram.
To see what has been installed (not much) or removed (a lot):
Code:
cat /var/log/apt/history.log | less
- The Lubuntu rootfs has the apt lists removed to reduce download size. Run this from lxterminal:
Code:
sudo apt-get update
Lubuntu To Do:
1) Remove xfce4-notifyd to get rid of the multiple notification errors... (Sorry about that one. I like Thunar and that was a dependency...)
2) No shutdown or restart in Lubuntu, also fails to start lightdm (tf700 prompt). Work around is to insert "sudo service lightdm start" (no quotes) into the file /etc/rc.local BEFORE exit0.
3) Version number shows as 12.10, it is really 13.04
4) Remove Unity
5) Update Tegra4Linux Drivers
6) Create updater scripts for version updates (Allows using your current install instead of starting with a fresh rootfs each time I update stuff)
7) Find out what is eating up space - rootfs still too large (734mb download - 2.5gb installed)
8)
Lubuntu Change log:
8-19-2013
- Removed xfce4-notify and Thunar
- Fixed lightdm errors and loads on boot now
- Fixed Lubuntu version number
- Removed overlay scrollbar - Most are usable by touch now.
- Removed password for sudo
- Other little things...
8-20-2013
- Removed Unity
- Added new wallpaper and conky (Thanks kennyMC)
- Cleaned up some clutter and sped things up...On hold...
Turns out that removing Unity did remove something that broke the framebuffer (honestly don't know much about that). I checked the logs and didn't see anything that got removed that should have affected X.
Anyhow, for now I am going to stick with the 8-19-2013 version as a base. I'm going to just spend some time using it and see what I can...
8-22-2013
- Removed Unity (if using v8-19-2013 run this in a terminal window as root - remove-unity.sh)
- Added new wallpaper and conky (Thanks kennyMC)
- Cleaned up some clutter and sped things up... Feels smoother!
- Removed some icon sets (HighContrast, LowContrast, Elementary), saved 100+mb on rootfs
Click to expand...
Click to collapse
Here is the modified .conkyrc and conky-draw.lua and my new wallpaper (definitely amateur).
conky-wallpaper2.tar (Fixed per JoinTheRealms - added - own_window_argb_visual) Just untar in the root of your home directory. (tar xf conky-wallpaer.tar) And use desktop preferences to change wallpaper.
{
"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"
}
Install
1) In Android Terminal Emulator:
Code:
# su
# mkdir /data/media/linux
2) copy installerV6.7.zip and rootfs-ubuntu-12.10-0.8.0.tar.lzma (12.10) or rootfs-lubuntutf700t-8-22-2013.tar.lzma (13.04)
to Dock SDcard (/Removable/SD), MicroSD (/Removable/MicroSD) or /data/media
3) Boot to recovery
4) NANDROID BACKUP!!!
5) Install installerV6.zip
6) READ and follow the aroma installer instructions (it will stop at 90% for as long as an hour or more while it is decompressing the rootfs)
7) Enjoy dual-boot Linux Again...
Files:
rootfs-ubuntu-12.10-0.8.0.tar.lzma (687 Mb) MD5: 6dbf50fe8623ceef3e5771e01ba52938
NEW! - rootfs-lubuntu-tf700t-8-22-2013.tar.lzma (722 MB) MD5: 92399b0541235a53b94844bacb06d866
NEW! 10/2013 - installerV6.7.zip (13mb) MD5: f2961cd02c6770dea369c3728fa13201
conky-wallpaper2.tar (316k)
Dualboot Linux - rootfs only installers.
These NO NOT install the kernels needed for hybrid or kexec dualbooting. These are only for unpacking the rootfs files from above. They are custom Aroma based installers and allow your /home directories to be on mccblk0p8 if you choose.
These are Aroma based installed from recovery:
arch-rootfs-installer-v.1.zip
lubuntu-rootfs-installer-v.1.1.zip
ubuntu-rootfs-installer-v.1.1.zip

KEXECBOOT with CROMBi-KK
These files are for those who want to kexecboot using CROMBi-KK 4/3, 4/27 or CROMi-X 5.4running on internal sd (NO rom2sd, f2fs or data2sd) with the "stock" _that9-oc+ (cm112 is modded by lj20036). You must have a good running CROMBi-KK install because i am not including the modules needed, only the zImage and initrd.img I extracted from the 4/3 zip file. CROMi-X should also be running stable. You will be flashing _thats newest _that9oc+ using his installer.
THIS IS VERY SIMPLISTIC IT ASSUMES YOU KNOW WHAT ALL THE FOLLOWING MEANS AND HAVE EITHER DONE THE KEXECBOOT WITH EARLIER CROMI VERSIONS OR HAVE COMPLETELY READ COGANO'S TUTORIAL
Also remember DO NOT use the regular rootfs installers. The regular installers will install a JellyBean kernel and render your tablet unusable. Only use the one of the following to extract your rootfs to the tablet:
arch-rootfs-installer-v.1.zip
lubuntu-rootfs-installer-v.1.1.zip
ubuntu-rootfs-installer-v.1.1.zip
All of the following is done on your tablet
1) Android
a) Mount /system r/w and make dir /system/boot​b) - Extract that-cm112-kexecboot-android.zip to /system/boot/ for 4/3/2014 CROMBi-KK Release
- Extract that-cm112-kexecboot-android-4272014.zip to /system/boot/ for 4/27/2014 CROMBi-KK Release
**** FOR CROMi-X flash _thats9oc+ kernel in TWRP and reboot into CROMi-X and then extract that9oc-kexecboot-android-05082014.zip to /system/boot/​c) Mount mmcblk0p5 and modify/copy your boot.cfg in /mmcblk0p5/multiboot to include CROMBi-KK at least to start (at least you will get back into Android ) - Example config - boot.cfg​2) Linuxa) Mount your Linux image and extract _that-linux-kexec.zip to /boot​3) Flashing the kexecboot bloba) Extract kexec-host.zip to a temp dir, cd into it and then carefully type the following as root:​
Code:
dd if=blob of=/dev/block/mmcblk0p4
Reboot and profit!
Credits:
rabits
JoinTheRealms
moreD_cn
_that
lj50036
cogano
and many more

Installer/ kernel guide
Ill be keeping this post updated as much as possible with the latest stuff to save people crawling through multiple threads
-Installer-
The installer is an Aroma package responsible for extracting the linux distros filesystem(compressed into a .lzma file) into a virtual image (.img), you can define the size of this image with the installer. It also prepares and flashes a kernel and initrd based on the preferences you define within the installer.
Downloads:
Version 6.5: https://www.dropbox.com/s/oksatawl4wxo290/installerV6.5.zip (Hunds 3.3.6 based)
Version 6.8: https://www.dropbox.com/s/0q01ijw1vkbokw1/installerV6.8.zip (Stock based, patches from _thatv5)
Note:
Code:
-As of 03/10/2013 the kernel in the installer is up to date, i wont be updating the kernel inside the installer anymore.
-Only Stock based ROMs are supported in the installer (Stock, Cromi 4.x, Cromi 5.x etc).
-Kernels-
We now have a flashable .zip (I stole _that's), To flash a .blob file the best method is using dd. From terminal emulator or adb shell, run "dd if=*name of blob* of=/dev/block/mmcblk0p4" (obviously without quotation marks and replace *name of blob* with the file name:silly
Downloads:
Stock based(blobs):
--Stock/ _that https://www.dropbox.com/s/86o9vt3b10digqr/blob04 0.4
--Hundsbuah https://www.dropbox.com/s/h2waysfz3bzaqy4/blob04 0.4
Stock based(zip)
--Stock/ _that https://www.dropbox.com/s/ndasx56839hsoud/kernel-Linux-that_based2.zip 0.4
--Hundsbuah https://www.dropbox.com/s/nh6s3yvmk1uszng/kernel-Linux-hunds_based2.zip 0.4
Changelog:
Code:
Version 0.1
-enabled cleancache
-testing cm10.2 dualboot
Version 0.2
-Added a repair (e2fsck)to main init menu
Version 0.3
-Another initrd update, better repair, streamlined the kernel selection, added a option to choose
the default OS, started adding support for kexecboot.
Version 0.4
-Some more init tweaks and updated kexecboot binary
Source:
https://github.com/JoinTheRealms
https://github.com/moreD
-MISC-
Some fixes and improvements
Suspend Workaround
http://forum.xda-developers.com/showpost.php?p=44764722&postcount=6
Backlight Control
Code:
sudo add-apt-repository ppa:indicator-brightness/ppa
sudo apt-get update && sudo apt-get install indicator-brightness
Overclock Management(only for Hundsbuah kernels)
https://www.dropbox.com/s/hkqhog4gjqw0lef/overclock.tar.gz(extarct to /home)
Install XBMC
https://www.dropbox.com/s/e21vys5a0c11u0e/installxbmc.sh
Credits
rabits (For his original init scrits and installer)
Hundsbuah (For his kernel and help)
_that (For his kernel and help)
moreD_cn (For fixing everything)
workdowg (for his rootfs's)
And lots more+

Hey guys you're doing great jobs! :good:
since there's a dev thread and i've got enough posts to reply here I think I'll reply here from now on
As i won't have much time for at least a month, I'll focus on building a kexec kernel for linux.
@JoinTheRealms mentioned that after removing wakelocks screen left blank while waking up. I looked into it yesterday but didn't find any solution it seems to relate to something about tegradc and earlysuspend I tried disabling and then re-enabling tegradc.0 (the one for LVDS) the issue appeared with wakelock support. but i cannot figure out how to resolve it.
another thing is bcmsdh_sdmmc keeps waking up my device regularily even without wakelock. however if I use rfkill to block wifi and bluetooth before suspending it works fine. it suspended for over 30k seconds without waking up last night
since we're having problem disabling wakelock, I have an idea that should we just leave it enabled and write a pm daemon for linux to control power state? actually i've implemented a basic one and it works as expected.

moreD_cn said:
Hey guys you're doing great jobs! :good:
since there's a dev thread and i've got enough posts to reply here I think I'll reply here from now on
As i won't have much time for at least a month, I'll focus on building a kexec kernel for linux.
@JoinTheRealms mentioned that after removing wakelocks screen left blank while waking up. I looked into it yesterday but didn't find any solution it seems to relate to something about tegradc and earlysuspend I tried disabling and then re-enabling tegradc.0 (the one for LVDS) the issue appeared with wakelock support. but i cannot figure out how to resolve it.
another thing is bcmsdh_sdmmc keeps waking up my device regularily even without wakelock. however if I use rfkill to block wifi and bluetooth before suspending it works fine. it suspended for over 30k seconds without waking up last night
since we're having problem disabling wakelock, I have an idea that should we just leave it enabled and write a pm daemon for linux to control power state? actually i've implemented a basic one and it works as expected.
Click to expand...
Click to collapse
Are able to post your pm daemon? Id love to give it a try, any attempts of me writing c code usually end in disaster .
Im still trying to fully understand this wakelock stuff ( when im daring enough im gonna start reading this), im guessing something in the linux userspace is holding wakelocks, explaining why it immdatly wakes up again?
I actually successfully got the system to suspend then wakeup with a script with wakelocks enabled, it simply put the device to sleep and 30 seconds later echo'ed on > /sys/power/state like 20 times with a 2 second delay lol no idea how this worked.

JoinTheRealms said:
Are able to post your pm daemon? Id love to give it a try, any attempts of me writing c code usually end in disaster .
Im still trying to fully understand this wakelock stuff ( when im daring enough im gonna start reading this), im guessing something in the linux userspace is holding wakelocks, explaining why it immdatly wakes up again?
I actually successfully got the system to suspend then wakeup with a script with wakelocks enabled, it simply put the device to sleep and 30 seconds later echo'ed on > /sys/power/state like 20 times with a 2 second delay lol no idea how this worked.
Click to expand...
Click to collapse
My daemon depends on a patch which providing "current power state" so i've modify it a bit. I think it's easy to understand.. but with very limited functions. note that press power button over a sec for force wake up.
looks like that sometimes it was kept from suspending by userspace wakelocks but it also occured that a wifi interrupt wake suspended device up. still don't know why but disable wifi before suspend seems to resolve it.
EDIT: seems i've made a mistake:silly: please redownload source file...
EDIT2: I've re-uploaded one that supports lid open/close event

To Do:
- Modify installer for rootfs only - workdowg?
- Kexec
- Multiboot?

@JoinTheRealms - CROMi-X 5 is right around the corner... Are we going to be ok with the kernel. I have to check but I think sbdags stock and Hunds are using a new base... I may just try CROMi-X beta3 to see what's up (if it boots with yours). I'm kind of looking forward to checking out the fixed dock power drain issue and trying the cache2sd though, so I may stick to his stock for a couple days...

workdowg said:
@JoinTheRealms - CROMi-X 5 is right around the corner... Are we going to be ok with the kernel. I have to check but I think sbdags stock and Hunds are using a new base... I may just try CROMi-X beta3 to see what's up (if it boots with yours). I'm kind of looking forward to checking out the fixed dock power drain issue and trying the cache2sd though, so I may stick to his stock for a couple days...
Click to expand...
Click to collapse
Kernel should be fine, I cant find any new kernel source from Asus. I doubt they changed much that would affect us, but we will see

workdowg said:
@JoinTheRealms - CROMi-X 5 is right around the corner... Are we going to be ok with the kernel. I have to check but I think sbdags stock and Hunds are using a new base... I may just try CROMi-X beta3 to see what's up (if it boots with yours). I'm kind of looking forward to checking out the fixed dock power drain issue and trying the cache2sd though, so I may stick to his stock for a couple days...
Click to expand...
Click to collapse
Can you elaborate on this dock power drain issue? I'm curious if it describes a problem I've been having since upgrading to 4.2.

yoda-sama said:
Can you elaborate on this dock power drain issue? I'm curious if it describes a problem I've been having since upgrading to 4.2.
Click to expand...
Click to collapse
Anytime you plug or unplug the tablet from the dock while in android (maybe linux), the dock discharges quickly to keep the tab charged. This is supposedly fixed in the new Asus jb base.
Sent from my ASUS Transformer Pad TF700t - CROMi-X 4.7.0 ODEX

JoinTheRealms said:
Kernel should be fine, I cant find any new kernel source from Asus. I doubt they changed much that would affect us, but we will see
Click to expand...
Click to collapse
Boots fine. HORRIBLE Quadrant scores... 3500 in performance.... Don't knowhow real world use feel yet.
Sent from my ASUS Transformer Pad TF700t - CROMi-X 5-Beta3-DEODEX

workdowg said:
Boots fine. HORRIBLE Quadrant scores... 3500 in performance.... Don't knowhow real world use feel yet.
Sent from my ASUS Transformer Pad TF700t - CROMi-X 5-Beta3-DEODEX
Click to expand...
Click to collapse
strange, didnt you report good scores on cromi 4.7? i wonder whats changed. Hope nothings broken on the linux side

JoinTheRealms said:
strange, didnt you report good scores on cromi 4.7? i wonder whats changed. Hope nothings broken on the linux side
Click to expand...
Click to collapse
Yeah, I got 6000. Might need to let the rom "settle" a bit before trying this testing. I also enabled the cache2sd which may have muddled with the results. Like I said I'll put it though some real world tests. I seems way snappier now.
Sent from my HTCEVOV4G using Tapatalk 4

@JoinTheRealms - Is there an easy way to compile the kernel for VT support (tty0). Xorg in Android is complaining about no tty0, which of course there isn't. Don't bang your head on this because it is for my pet project, using Linux Deploy to run my rootfs chrooted in the framebuffer under Android. This would help a lot when I don't have a pc in front of me to search out things while developing the rootfs....
Edit - or @_that your stock Android kernel?

@moreD_cn In the previous kexec kernel is posted with wakelocks disabled, we had an issue with the screen remaining blank after a suspend (although the backlight functions normally)
This might not having as be as an issue as i thought and hoping you can help me If i suspend the tablet and wake it up again (the screen is blank at this point) i can ssh into it and if i run "sudo service lightdm restart" and the display returns! so we have a semi-functioning native suspend it seems xserver(or something) isn't re-initialising LVDS1 properly, but im at a loss on how to fix (my linux knowledge still isn't great) but i feel our options expanded.

JoinTheRealms said:
@moreD_cn In the previous kexec kernel is posted with wakelocks disabled, we had an issue with the screen remaining blank after a suspend (although the backlight functions normally)
This might not having as be as an issue as i thought and hoping you can help me If i suspend the tablet and wake it up again (the screen is blank at this point) i can ssh into it and if i run "sudo service lightdm restart" and the display returns! so we have a semi-functioning native suspend it seems xserver(or something) isn't re-initialising LVDS1 properly, but im at a loss on how to fix (my linux knowledge still isn't great) but i feel our options expanded.
Click to expand...
Click to collapse
I have looked into it and don't know how to fix neither. But if we can get display back by restarting X, it's great progress. I'll try again!
btw how is multiboot going? I spent some time last days to port something called kexecboot and it has replaced rabits' one on my pad. Still have some problems but it works, mainly..

moreD_cn said:
I have looked into it and don't know how to fix neither. But if we can get display back by restarting X, it's great progress. I'll try again!
btw how is multiboot going? I spent some time last days to port something called kexecboot and it has replaced rabits' one on my pad. Still have some problems but it works, mainly..
Click to expand...
Click to collapse
Yeah its strange,after i restart x, input devices stop working, also when i run lightdm from ssh it wont start, just falls back to terminal. I havnt had much time too play with it, but atleast its seemingly not a display driver issue.
Multiboot should be very easy to port over(Im all talk, since i have zero experience doing that kinda thing ) The developer has recently put alot of work into making it easy to port to other devices. Now that we have nvflash, i feel a bit safer experimenting.
kexecboot looks awesome! in fact ive been planning a grub-like multiboot, using twrp or cwm, im trying to figure out how to strip all the recovery stuff off it and just use it as a multiboot interface, and have boot from kexec. I need linux booting from a directory first though..... lol

Hmm just updated my source with the latest Asus kernel source, and im not getting framebuffer console..... I know they patched the motochopper root exploit hopefully it didn't affect the fb patch.
---------- Post added at 01:56 AM ---------- Previous post was at 01:24 AM ----------
Either im doing something really dumb or Asus broke fb console.... its V10.6.1.14.10 with _thats pmc and ril patches and the fb patch. After splash screen it stays blank for about 5 seconds before booting straight into android

Hey guys, i originally missed this post, but it seems to have completely fixed the issue with the tablet locking up due to heavy I.O:
pvka13 said:
I was able to solve the random-freeze-during-heavy-I/O issue. The culprit is that large amount of memory is used as buffer cache to hold dirty pages. When the dirty page threshold is hit, all buffer cache is written out at once, without allowing other processes to do much I/O.
The solution is to add the following to /etc/sysctl.conf
Code:
vm.dirty_bytes=2048000
vm.dirty_background_bytes=1024000
The configuration can be reloaded without a reboot by running "sysctl -p" as root
Click to expand...
Click to collapse
With it i was about to extract a 200mb file while installing 100mb of packages while browsing xda many thanks to pvka13

[App] [ 4.0+] [ROOT] Boot Shell - Execute Shell Commands and scripts at Boot [V 3.5]

Boot Shell allows you to save Linux Shell commands and execute them at boot. The Pro version allows to execute complete shell scripts at boot.
{
"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"
}
You can also save your favourite Linux commands and execute them at your will.
It can also eliminate the need of using init.d scripts for basic needs such as setting CPU parameters at boot such as, CPU Frequencies, governors, and also IO Governers,enable/disable Fastcharge, GPU Overclock etc.
REQUIREMENTS -
->ROOT
->BUSYBOX
Pro Version Extras -
-Ability to Execute Scripts at boot
-View outputs and errors after command execution
-Inbuilt Text/Script Editor
For any queries or problems please feel free to E-mail me at [email protected]mail.com
Try not to execute a resource intensive task or scripts at boot, it can slow down your device startup.
Explanation for Permissions -
-> Read/Write USB Storage - Allow the Shell commands to read/write on Device Storage
-> SuperUser Permission - To Execute Shell Commands
-> Run at Startup - To be able to execute Shell commands at Boot
Credits:
-> CMDProcessor Library, for making Root easy, and to @Androguide.fr for sharing it.
-> @nikwen - For being a very helpful and active contributor in the Java for Android App Development section, and for clearing my initial programming doubts.
Changelog-
8/2/14 -
Initial Release
10/2/14 -
Added notification to confirm execution of commands at boot.
Execution of commands at boot time should be faster now.
12/02/14 -
Added option to enable/disable execution of commands at boot.
Added link to XDA thread in settings.
21/02/14 -
Uploaded to play store
Added option to export saved commands as txt file to sdcard
Fixed a command delete bug
Added help documentation
25/02/14-
Fixed up some strings
Added more feedback options in settings
07/03/2014-
Fixed a bug with exporting of commands
Added a cancel option to command edit dialog
Minor code cleanup
21- Mar - 2014
-Major Overhaul
-Ability to Execute Scripts at boot [Pro Version]
-View outputs and errors after command execution [Pro Version]
-Inbuilt Text/Script Editor [Pro Version]
Click to expand...
Click to collapse
Please try to download from Google Play as it will help me to keep record of number of downloads, app crashes, etc.
For those who do not use Gapps download V3.0 from the attachments below.
P.S. - If you are coming from the Beta Version of the app, the signature for the app has changed so you will have to uninstall the old version to be able to install the new one. To backup your commands, please backup app data using titanium backup or helium, uninstall, reinstall from play store and restore app data. I am really sorry for this inconvenience.

Screenies !!!!

Some useful Shell Commands
USB FAST CHARGE Enable:
Code:
echo 1 > /sys/kernel/fast_charge/force_fast_charge
USB FAST CHARGE Disable:
Code:
echo 0 > /sys/kernel/fast_charge/force_fast_charge
SET GPU CLOCK:
Code:
echo x > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
where x is your desired GPU Frequency or frequency step
SET CPU GOVERNER
Code:
echo interactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
replace interactive with your desired governer
LOAD A KERNEL MODULE
Code:
insmod /system/lib/modules/module_name
TCP CONGESTION ALGORITHM
Code:
/system/xbin/sysctl -w net.ipv4.tcp_congestion_control=reno
replace reno with your desired value
SET CPU MIN FREQUENCY
Code:
echo 350000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
replace 350000 (350 MHz)with your desired frequency
SET CPU MAX FREQUENCY
Code:
echo 1500000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
replace 1500000(1.5 Ghz) with your desired frequency
SET READ AHEAD BUFFER
Code:
echo 1024 > /sys/block/mmcblk0/queue/read_ahead_kb
replace 1024 with your desired value(in KB)
SET I/O SCHEDULER
Code:
echo row > /sys/block/mmcblk0/queue/scheduler
replace row with your desired governer

gh0stslayer said:
mine
Click to expand...
Click to collapse
Boot Shell has stopped....
My system is 4.0.4
you one picture system UI is beautiful,can you sharing me?
:good:

Lumia997 said:
Boot Shell has stopped....
My system is 4.0.4
:good:
Click to expand...
Click to collapse
@Lumia997 :
Sorry about that, a new version has been uploaded , please try it. Thanks
you one picture system UI is beautiful,can you sharing me?
Click to expand...
Click to collapse
sorry I don't understand, what do you want me to share ?

OK, how does this baby work? That is, what executes the commands? When (linux boot, zygote startup, dalvik up and running)??
How does this relate to selinux?
I have scripts in /data/local/userinit.d/ which are supposed to be run by the init.d system. The only one I know that runs is link2sd's script if I move it to there. Others, apparently do not run, even in cm-10.2 with permissive selinux. I have tasker run them, successfully, when it begins its "listening."
The lead question here is critical! If the app must be present at boot (it is an apk, however!), then it needs be on internal storage or better, on system! If the app needs be present only for its UI, it can be on sdcard or linked (link2sd). It is a user app but maybe it needs place something on system or /etc/init.d/ to operate?

Dovidhalevi said:
OK, how does this baby work? That is, what executes the commands? When (linux boot, zygote startup, dalvik up and running)??
How does this relate to selinux?
I have scripts in /data/local/userinit.d/ which are supposed to be run by the init.d system. The only one I know that runs is link2sd's script if I move it to there. Others, apparently do not run, even in cm-10.2 with permissive selinux. I have tasker run them, successfully, when it begins its "listening."
The lead question here is critical! If the app must be present at boot (it is an apk, however!), then it needs be on internal storage or better, on system! If the app needs be present only for its UI, it can be on sdcard or linked (link2sd). It is a user app but maybe it needs place something on system or /etc/init.d/ to operate?
Click to expand...
Click to collapse
The commands saved on this app are executed in the same way they are executed by a Linux Shell Emulator, or a Terminal on a Native Linux system. The only difference is it save the commands you enter and executes them as soon as the device finishes booting. You can also save commands to a favourite list , which will not be executed at boot, but allows you to manually execute them as you wish.
Edit: - Info: - It uses busybox to execute shell commands
The app works fine when placed on the internal storage of the device, though I am not sure about if it will work if placed on SD Card but in theory it should work, no need to place it on the /system partition.
It cannot run whole shell scripts only single commands, but you can save as many commands as you like
Just make sure you enter a valid command and that you kernel or device supports it.

gh0stslayer said:
The commands saved on this app are executed in the same way they are executed by a Linux Shell Emulator, or a Terminal on a Native Linux system. The only difference is it save the commands you enter and executes them as soon as the device finishes booting. You can also save commands to a favourite list , which will not be executed at boot, but allows you to manually execute them as you wish.
Edit: - Info: - It uses busybox to execute shell commands
The app works fine when placed on the internal storage of the device, though I am not sure about if it will work if placed on SD Card but in theory it should work, no need to place it on the /system partition.
It cannot run whole shell scripts only single commands, but you can save as many commands as you like
Just make sure you enter a valid command and that you kernel or device supports it.
Click to expand...
Click to collapse
Thanks for the info. In other words, would work as I use tasker now but with a much easier UI for scripts entry. Not really a substitute for /etc/init.d functionality because would get run later but otherwise, quite nice. Note that current cm-11 ROMs (for my old LG P500 at any rate) are quite slow getting startup services going.

Dovidhalevi said:
Thanks for the info. In other words, would work as I use tasker now but with a much easier UI for scripts entry. Not really a substitute for /etc/init.d functionality because would get run later but otherwise, quite nice. Note that current cm-11 ROMs (for my old LG P500 at any rate) are quite slow getting startup services going.
Click to expand...
Click to collapse
Yup, not really a substitute for complex init.d scripts, and yes quite similar to the way tasker does shell commands at boot.
But it should be more than enough for some simple CPU, I/O and kernel tweaking etc.

gh0stslayer said:
Yup, not really a substitute for complex init.d scripts, and yes quite similar to the way tasker does shell commands at boot.
But it should be more than enough for some simple CPU, I/O and kernel tweaking etc.
Click to expand...
Click to collapse
... and maybe a tasker plugin to execute "favorites" entered to this app?

Dovidhalevi said:
... and maybe a tasker plugin to execute "favorites" entered to this app?
Click to expand...
Click to collapse
Hmmm, I will have to look into it. I have no knowledge about how to develop plugins for tasker :silly: but I can try, no promises though.
But can't you already add commands in tasker and schedule their execution ?

gh0stslayer said:
Hmmm, I will have to look into it. I have no knowledge about how to develop plugins for tasker :silly: but I can try, no promises though.
But can't you already add commands in tasker and schedule their execution ?
Click to expand...
Click to collapse
It is excruciatingly difficult to enter this stuff on the phone's keyboards. So if I have a "favorite"command in this app and later on decide to use it in tasker, I would not be to happy with struggling to enter it a second time
BTW, most of what I have entered as script are in bash script files. Can these be run by the app or only single line commands?

Dovidhalevi said:
It is excruciatingly difficult to enter this stuff on the phone's keyboards. So if I have a "favorite"command in this app and later on decide to use it in tasker, I would not be to happy with struggling to enter it a second time
BTW, most of what I have entered as script are in bash script files. Can these be run by the app or only single line commands?
Click to expand...
Click to collapse
Single line commands only, you can add the next line of bash script as another command .
Edit:
If you wanna use the same command else where , click on the command select edit and copy the command from the textbox. No need to enter it again.
Sent from my Galaxy Nexus using Tapatalk

gh0stslayer said:
Credits:
-> CMDProcessor Library, for making Root easy, and to @Androguide.fr for sharing it.
-> @nikwen - For being a very helpful and active contributor in the Java for Android App Development section, and for clearing my initial programming doubts.
Click to expand...
Click to collapse
Big thanks for that.
In my opinion it's great that you finished your app. Good job. :good:

nikwen said:
Big thanks for that.
In my opinion it's great that you finished your app. Good job. :good:
Click to expand...
Click to collapse
Thank you very much

Hello everyone, Boot Shell is now available on Play Store. Please find it here
https://play.google.com/store/apps/details?id=com.kislay.bootshellcommand
The signature for the app has changed so you will have to uninstall the old version to be able to install the new one. To backup your commands, please backup app data using titanium backup or helium, uninstall, reinstall from play store and restore app data. I am really sorry for this inconvenience.

New version is up-
Changes -
Fixed up strings
Added feedback options (E-mail and Play Store)
There is an easter egg somewhere too

Version 1.2 is now up-
Changes -
-Fixed a bug with exporting commands to SD Card
-Added a cancel option to command edit dialog
-Minor Code Cleanup
Please feel free to drop your feedback/ comments/ ratings
Email if you need any help, guidance or wanna report a bug.

New major update -
Changelog-
Version 2.0 -> 21- Mar - 2014
-Major Overhaul
-Ability to Execute Scripts at boot [Pro Version]
-View outputs and errors after command execution [Pro Version]
-Inbuilt Text/Script Editor [Pro Version]
Pro Version Link - Boot Shell Pro

help
I use that bootshell but need more time for executing ,its that normal because i already w8 for 4 hours