{
"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"
}
Boot Box is a boot animation database, manager, creator, and more. The Nexus 5 is supported by Boot Box, this support thread will contain N5 device specific animations that are added into Boot Box, animations that are optimized for the N5's resolution, and device support information.
Boot Box (v2.7) - Open BETA update released
Open BETA testing stage. Expect bugs.
[July 1] Changelog (v2.7)
New! Create a flashable zip backup of your currently installed boot animation.
If you're running a CM-based ROM, you may have trouble with backups.
New! Pre-load GIF previews - this improves the quality and speed of the preview, by far.
New! Polished UI and new app icon.
Updated Scrambler. The randomizer now works better with no simultaneous choices.
New! View animations for all resolutions under one list (lots of duplicates, for now).
Fixed bugs with the latest additions menu. Pending animations won't show unless specified under settings. Explicit animations won't show in this menu.
Attempted to fix a bug where valid ZIP files are erroneously reported as invalid (please test)
More boot animation list sorting methods!
More tiny bug fixes and tweaks.
Reminder: the Boot Box Factory is meant to create animations with up to 10 images.
Some features of the Boot Box App:
Dynamic Database. Animations are fetched and updated dynamically from a database on the Boot Box server.
Categories: show/hide certain animation categories
Upload your boot animations directly from the Boot Box app. The built-in Boot Box Uploader creates the required resources for you, including the GIF Preview.
Scrambler: allows you to play a different boot animation at every boot.
Boot Box Factory: create your own boot animations straight from Boot Box! Creating a static animation will allow you to show your favorite picture on boot up. Creating a Slideshow animation will allow you to display multiple pictures on boot up, each for a set amount of time!
Animations can be previewed via a YouTube video (if the uploader provides a link), via a GIF preview, or via a ZIP preview (the animation is downloaded and played in a simulated environment).
Load up a local animation from your SD Card and preview it, install it, or create a GIF from it (thanks to XDA Developer D4rKn3sSyS).
Flexible boot animation and cache locations for different devices.
Download Boot Box, Play Store Link (FREE):
https://play.google.com/store/apps/details?id=com.overhaulingmod.bootbox
G+ Community: https://plus.google.com/u/0/communities/109587463140312269110
Boot Animations Collection
To add an animation download Boot Box and visit the Boot Box uploader, or post your animation here.
Nexus 5 branded additions to Boot Box and 1080x1920 animations will be posted here.
No Nexus 5 branded animations exist in Bb at this time.
Hexagonal Tunnel by Admiral Potato
GIF Preview (actual animation is stretched to fit):
Download this animation, and more, from Boot Box (Free, easy installation!):
https://play.google.com/store/apps/details?id=com.overhaulingmod.bootbox
or you can get it from here (not flashable! How-to install video by jgandroot).
Follow me on Google+ to receive updates
Does this affect any system files?
Sent from my Nexus 5 using Tapatalk
voryzen said:
Does this affect any system files?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Only the bootanimation.zip file. Boot Box allows you to create as many backups of this file as you want.
Boot Box only needs root access to copy from and to the following directories:
Installation location, can be set manually. Usually /data/local/bootanimation.zip or /system/media/bootanimation.zip (mounting rw)
Cache location, can also be set manually. /sdcard/BootBox by default.
To make sure that all functions will run properly, Boot Box checks for root access before downloading or installing an animation and when the app is launched.
Do you need to root your phone?
TXRaunchy said:
Do you need to root your phone?
Click to expand...
Click to collapse
Of course.
Hi,
I found an ICS boot animation, the apps INFO button says Projected Resolution: 360x640, Image Format JPG, Number of Frames: 77
It previews perfectly. I click "Install Animation", it syas "Error Copying Files", Please make sure the installation location is accessible. It must be its previewing it. The "bootanimation" file is in the "\\DB-NEXUS5\sdcard\$DB$\media\Boot Animations\ICS BOOT ANIMATION" directory.
I don't have trouble installing the apps inbuilt animations.
Thanks for any pointers, really want the ICS animation
dbareis said:
Hi,
I found an ICS boot animation, the apps INFO button says Projected Resolution: 360x640, Image Format JPG, Number of Frames: 77
It previews perfectly. I click "Install Animation", it syas "Error Copying Files", Please make sure the installation location is accessible. It must be its previewing it. The "bootanimation" file is in the "\\DB-NEXUS5\sdcard\$DB$\media\Boot Animations\ICS BOOT ANIMATION" directory.
I don't have trouble installing the apps inbuilt animations.
Thanks for any pointers, really want the ICS animation
Click to expand...
Click to collapse
Hello!
Please try the latest version of Boot Box. Let me know if you still get the same error.
overhauling said:
Please try the latest version of Boot Box. Let me know if you still get the same error.
Click to expand...
Click to collapse
Using the latest version on the play store:
if I use GDRIVE->"Internal Storage" it says "Only .zip files allowed"
Using any other file manager I get an error message mentioning an "unwated space" (I'm assuming "unwanted" was intended). The filename is "bootanimation.zip" (no space), the path has spaces ("\sdcard\$DB$\media\Boot Animations\ICS BOOT ANIMATION").
Moving it to the root directory resolved neither of the 2 problems above. It's happy to preview the animation for the "unwated" space issue.
If I ADD a space to the one in the root directory, it says its removed a space...If I install the animation its thumbs up and I boot. My old animation has been removed, the new one doesn't work.
Bye,
Dennis
Thank you, looks very promising :good::good:
dbareis said:
Using the latest version on the play store:
if I use GDRIVE->"Internal Storage" it says "Only .zip files allowed"
Using any other file manager I get an error message mentioning an "unwated space" (I'm assuming "unwanted" was intended). The filename is "bootanimation.zip" (no space), the path has spaces ("\sdcard\$DB$\media\Boot Animations\ICS BOOT ANIMATION").
Moving it to the root directory resolved neither of the 2 problems above. It's happy to preview the animation for the "unwated" space issue.
If I ADD a space to the one in the root directory, it says its removed a space...If I install the animation its thumbs up and I boot. My old animation has been removed, the new one doesn't work.
Bye,
Dennis
Click to expand...
Click to collapse
The "unwanted space" string has been corrected.
The animation installs successfully from the root directory but it doesn't work? Are you able to install animations that have been cached, or saved in the SD by Boot Box?
Does the animation work if installed manually?
@dbareis @TheEijk thank you for your feedback.
overhauling said:
The "unwanted space" string has been corrected.
Click to expand...
Click to collapse
Apart from the spelling there is at least one more bug, with and without spaces I was getting unexpected behavior.
overhauling said:
The animation installs successfully from the root directory but it doesn't work? Are you able to install animations that have been cached, or saved in the SD by Boot Box?
Click to expand...
Click to collapse
I tried "\sdcard\BootBox\Animations\Tibuk1080x1920.zip" (I'm amazed this is considered explicit), it has the same "Only .zip files allowed" issue but the animation is displayed on booting.
overhauling said:
Does the animation work if installed manually?
Click to expand...
Click to collapse
Probably but not sure how to do so. I tried something just as good though, I used the "Currently installed animation" and it was shown in the preview so its probably its installed OK, just not displaying. I have attached the zip file.
Hi,
I've got a bigger issue now... I used BootBox to create series of slides which previewed OK. This hangs my phone with the 2nd last picture displaying, I feel a vibrate shortly after.
I can get into ADB at this stage but don't know linux commands or Android internals, from Googling I thought this is what I could do:
* ADB SHELL
* su
* mount -o remount rw /system
* cd /system/media
* ls -l
* cp /sdcard/goodbootanimation.zip ./bootanimation.zip
* ls -l
Click to expand...
Click to collapse
I'm not sure "SU" is doing anything, the shell generally just repeats what I type and the googled solution of copy/pasting instead sometimes works. I'm not sure I need it anyway this is my command prompt "255|[email protected]:/ $". (does that mean I have root access already?)
The mount fails with "mount: Operation not permitted". The copy fails with "cp: ./bootanimation.zip: Read-only file system"
I've now worked out how to install the drivers for ADB for recovery, while the driver loads ADB on windows can't see the device:
ADB.EXE shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed
Click to expand...
Click to collapse
I've also Tried Recover->Apply update from ADB", got "device not found".
I'm rooted with unlocked bootloader and stock everything else. I do not wish to factory reset and lose all my configuration..
Help....:crying:
dbareis said:
Probably but not sure how to do so. I tried something just as good though, I used the "Currently installed animation" and it was shown in the preview so its probably its installed OK, just not displaying. I have attached the zip file.
Click to expand...
Click to collapse
Install the animation on /data/local/ instead of /system/media/
If there's an animation in /data/local/, Android will automatically boot that one and ignore any other animation in /system/media/.
dbareis said:
Help....:crying:
Click to expand...
Click to collapse
The slideshow should be working fine. How many images did you use?
Do the following http://forum.xda-developers.com/showpost.php?p=50201803&postcount=11
Please let me know if it works out for you
overhauling said:
Install the animation on /data/local/ instead of /system/media/
If there's an animation in /data/local/, Android will automatically boot that one and ignore any other animation in /system/media/.
Click to expand...
Click to collapse
I don't seem to have access to that directory once the phone has hung on the animation:
c:\ > ADB.EXE shell
Android Debug Bridge version 1.0.31
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ cd /data/local
cd /data/local
[email protected]:/data/local $ ls -l
ls -l
opendir failed, Permission denied
255|[email protected]:/data/local $ cp /sdcard/goodbootanimation.zip ./bootanimation.zip
cp: ./bootanimation.zip: Permission denied
Click to expand...
Click to collapse
Do the following http://forum.xda-developers.com/showpost.php?p=50201803&postcount=11
Click to expand...
Click to collapse
It is not possible for me to follow those instructions due to the issues I described in my previous post
At this stage it doesn't appear to be a driver issue (which I resolved yesterday)
overhauling said:
Do the following http://forum.xda-developers.com/showpost.php?p=50201803&postcount=11
Please let me know if it works out for you
Click to expand...
Click to collapse
I'm documenting what I'm doing in EverNote so this is it so far:
* Boot into Recovery on phone
* You will see an Android with a red triangle and "no command" this is normal
* Volume Down to select "apply update from ADB" and press power button
* You should probably hear/see Windows loading the device
* On windows try "adb get-state" it should respond with "sideload"). The usual ADB commands do not work!
* adb sideload kitkat_Bootanimation.zip (http://d-h.st/4kc)
* sending: 'kitkat_Bootanimation.zip' 100%
* Fails with messages on phone (MD5 matches and also fails with known good "Tibuke1080x1920.zip"):
* Verifying update package
* E:footer is wrong"
* E:signature verification failed
* installation aborted
* Solution to the above:
* ??????????????
Click to expand...
Click to collapse
---------- Post added at 02:23 PM ---------- Previous post was at 02:04 PM ----------
It seems the "kitkat_Bootanimation.zip" gets verified against what is expected so perhaps this one is not from Android 4.4.2?
Anyone know where to get these?
@dbareis flash the stock boot animation, the flash should replace the older animation and all issues should be gone. Here it is: http://d-h.st/users/BrianAllred/?fld_id=29585#files (provided by @BrianAllred)
Sent from my SGH-M919 using Tapatalk
overhauling said:
@dbareis flash the stock boot animation, the flash should replace the older animation and all issues should be gone. Here it is: http://d-h.st/users/BrianAllred/?fld_id=29585#files (provided by @BrianAllred)
Click to expand...
Click to collapse
Thanks but I've already tried that one and it has the same issue (I just confirmed its MD5 to be 100% sure).
dbareis said:
Thanks but I've already tried that one and it has the same issue (I just confirmed its MD5 to be 100% sure).
Click to expand...
Click to collapse
Did you install the Apple Static animation before experiencing this issue?
To fix similar issues I've installed Phillz Touch recovery (or any recovery with a file manager) and then I've used that file manager to delete the bootanimation.zip via recovery.
overhauling said:
Did you install the Apple Static animation before experiencing this issue?
Click to expand...
Click to collapse
No, it may have been somewhat self inflicted through. The app doesn't allow you to modify a generated boot animation (from multiple static images), from what I could see, I thought I should be able to rename and swap 2 of the images, I did that. The preview worked perfectly (it should be using the same logic as the boot process so as to fail if it was going to at boot...).
overhauling said:
To fix similar issues I've installed Phillz Touch recovery (or any recovery with a file manager) and then I've used that file manager to delete the bootanimation.zip via recovery.
Click to expand...
Click to collapse
I used a toolkit to boot into TWRP recovery and that then allowed me to flash the kitkat boot animation. I learnt a lot fixing this
Bye,
Dennis
???
I'm sorry but I am confused.... I made my own bootanimation.zip to try but every time I try to do the local boot animation from storage and pick my zip... It says only .zip are allowed... It is a zip and I know it works since I used before, with the app... Any suggestions? I find this app extremely easy to use and install boot animations... Any help would be appreciated!
Related
{
"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"
}
For anyone interested, below are the steps for getting your device dual-booting with CyanogenMod 10.2.
Why?
I don't want to erase native firmware and want to give a try to CyanogenMod
I want to have both native and CM, because I like native Samsung S-Pen apps, but want to have more fresh Android too
I like experimenting - it's cool!
The Idea
Our Android device has 2 boot partitions - for normal boot, and to boot into recovery. If I want to boot CyanogenMod, I need to place its boot image instead one of those boot partitions. E.g. if I want to have both native firmware and cyanogen - then obviously I need to replace recovery partition. However I can do the backup of recovery and restore it later if needed.
But, I also need to place cyanogen system and data partitions somewhere. Putting it on the external sdcard makes CM working really slow, repartitioning internal memory might be good idea, but it is not so easy and is not necessary for experimenting. Thus I've created 2 image files and put it to native data partition (mmcblk0p12) to media folder, e.g. into internal sdcard, then changed cyanogen boot image to mount those image files on boot as system and data partitions.
Prerequisites:
Rooted Samsung Galaxy Note 10.1 2012 Edition
2GB of free disk space at internal sdcard
Recovery partition backup, because we are going to replace it with CyanogenMod boot image
Clear understanding of what you are doing, because you potentially can break your device
Downloads:
CM 10.2 boot image
CM 10.2 data partition image
CM 10.2 system partition image
Steps
This manual suggests that you are going to do the recovery backup to external sdcard and has native firmware which means that recovery partition is mmcblk0p6, data partition is mmcblk0p12 and internal sdcard is /mnt/sdcard folder (otherwise you need to change the commands appropriately and might need to fix cyanogen boot image too).
Download 3 files by the links above and upload to internal sdcard of your device. Connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to external sdcard to create recovery backup
cd /mnt/extSdCard
dd if=/dev/block/mmcblk0p6 of=./recovery.img
# go to internal sdcard folder
cd /mnt/sdcard
# unpack partition images - each is 1Gb of disk space
gunzip ./system.img.gz
gunzip ./data.img.gz
# write CM boot image to recovery partition
dd if=./cyanogen.img of=/dev/block/mmcblk0p6
# finish
exit
exit
Now you can reboot your device into recovery mode and see CyanogenMod booting.
Restoring native recovery:
If you got tired from CyanogenMod and/or would like to take back your recovery, please use the backup you've done before. Lets say it is placed on your external sdcard, then connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to the folder with recovery backup
cd /mnt/extSdCard
# write recovery image over recovery partition
dd if=./recovery.img of=/dev/block/mmcblk0p6
Please let me know If I missed anything in my steps.
P.S. What I've changed in Cyanogen boot.img to make it using img files instead of partitions in form of patch: View attachment cyanogen_boot_img.patch. It is also necessary to create /host folder in initrd folder tree.
wow!!
it's really hard to be done xD
i thought it will be as easy as it was on my old Galaxy S2
all what i needed to do is to restart the phone and press home to boot to second Rom
i hope it's going to be easier soon
and thank you for you efforts toward our device Development
MoNsTeRmUk said:
wow!!
it's really hard to be done xD
Click to expand...
Click to collapse
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
X-Stranger said:
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
Click to expand...
Click to collapse
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
MoNsTeRmUk said:
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
Click to expand...
Click to collapse
Thanks for kind words Actually you don't need to have the computer to change ROM, you can type commands from terminal emulator directly from Android. I'm also thinking about creating small Android app which can be installed to each ROM and will be able to switch boot partition within one click.
Thanks for this superb work. Can't download last file ?
Please if can make someone flashable zip it would be great I am a noob but I want try this thanks again
Sent from my GT-N8000 using Tapatalk HD
other roms
Can I do this this with another rom
maro_X said:
Can I do this this with another rom
Click to expand...
Click to collapse
It is possible, but your another rom must be specially modified for this.
What rom are you talking about exactly?
Multi-boot solution
I've tired of writing images to boot partition every time I want to switch between native firmware and Cyanogen, so decided to compose a little program that I was talking before. So let me introduce you N8xx Boot Manager!
The idea:
You put your boot images files to some folder on your sdcard, lets say to /mnt/extSdCard/images/boot
And recovery boot images to /mnt/extSdCard/images/recovery
Now you run Boot Manager and select what you want to boot as normal boot or as recovery
As soon as you selected it, the application asks you if you would like to write this image to the appropriate partition (boot or recovery)
After successful writing it will ask you for booting from that partition, e.g. propose to reboot into your another rom or recovery
For sure all the settings like path where to keep images and boot/recovery partition names can be fixed appropriately to your device at the Settings tab
For sure the application requires root permissions, e.g. your device must be rooted. You can also check this from Settings tab
The application file: View attachment bootmanager-1.0.apk - feel free to install it to your device and use posting me bug reports
P.S. The only thing I've forgotten - the button to create native boot image file backup You still need to do it manually, sorry Hopefully in next release, if there be people interested in N8xx Boot Manager
P.P.S. Generally this program can be used for any device - just put correct images and correct boot partition names
P.P.P.S. Why N8xx and not N8xxx or N80xx? Because I've missed one symbol when typed application name in Android Studio and was too lazy to change that later :laugh:
N80xx Boot Manager
Updated version of N80xx Boot Manager: View attachment bootmanager-1.1.apk
Changelog:
Fixed application name
Fixed images path detection when no settings were changes
Added "Backup boot partiton" and "Backup recovery partition" buttons
Thus, now to install CM 10.2 as dual boot you don't need to go to ADB or terminal - just upload 3 img files to your device proper locations, installl boot manager apk, create stock boot/recovery partitions backup, then select what you want to boot and boot to that rom!
P.S. Going to update first post of this thread with steps based on Boot Manager, just would be nice if someone confirm that it works.
swamimahesh said:
Can't download last file
Click to expand...
Click to collapse
Re-uploaded.
I love u man
Finally alittle love for our device :crying:
Do I have to reinstall apps when booting to cm?
edit: I dont really understand the first step when you extract data and system.img. Can you explain more clearly the procedure?
edit2: did anyone do this dualboot successfully?
data.img.gz
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
netj said:
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
Click to expand...
Click to collapse
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment data.img.gz and let me know if it works for you.
muop_92 said:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
Click to expand...
Click to collapse
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
X-Stranger said:
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
Click to expand...
Click to collapse
Where is /mnt ? I saw in my device only /storage/extSdCard
Sent from my GT-I8160 using Tapatalk 2
muop_92 said:
Where is /mnt ? I saw in my device only /storage/extSdCard
Click to expand...
Click to collapse
It's the same. External sdcard is available on both these paths as far as I know. You can change it otherwise in application settings tab.
Ok !
X-Stranger said:
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment 2519204 and let me know if it works for you.
Click to expand...
Click to collapse
Hi,
It's Ok !
Thanks !
I have just modify the paths :
dd if=/dev/mmcblk0p6 of=./recovery.img --> dd if=/dev/block/mmcblk0p6 of=./recovery.img
dd if=./cyanogen.img of=/dev/mmcblk0p6 --> dd if=./cyanogen.img of=/dev/block/mmcblk0p6
:good:
Droid Turbo System Image Tutorial
So I've noticed there isn't yet a guide on how to modify a system image for the Turbo and thought I would write one up. Note that anything you do here can very easily brick your phone, and I'm not responsible for anything that breaks, bricks, catches on fire, causes Skynet to become sentient, or eats your cat.
Here's what you need:
A rooted system image (can be found here)
A linux distro, either running natively or in VirtualBox (Ubuntu is a good choice)
IF YOU'RE USING LINUX NATIVELY:
Put the system image somewhere on an ext4 file system you have access to, such as in your home directory (/home/user)
Make sure loop device support is installed (this will vary by distro but should be installed by default on Ubuntu)
Make sure the loop kernel module is loaded:
Code:
lsmod | grep loop
As long as the command returns text, you're good.
If it is not, load it:
Code:
sudo modprobe loop
Make a mountpoint:
Code:
sudo mkdir /mnt/turbo
And finally, mount the image:
Code:
sudo mount -t ext4 -o loop /path/to/turbo/image /mnt/turbo
And the image will be accessible at /mnt/turbo/. Note that you'll need root permissions to access the files. To open the file manager as root under Ubuntu:
Code:
sudo nautilus
Navigate to /mnt/turbo to access the image and modify whatever you feel like.
IF YOU'RE USING VIRTUALBOX:
Please note that I'm writing these instructions under Linux. YMMV.
You'll have to convert the turbo's system image to something VirtualBox can recognize. To do this:
Code:
VBoxManage.exe convertdd turbo_system.img turbo_system.vdi
Load VirtualBox, but don't start your virtual machine yet.
Right click on your VM and open Settings.
Navigate to Storage and select Add Hard Disk.
{
"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"
}
Select your Turbo's system image in vdi format.
Click OK and close the settings window.
Start the VM.
Once you're all logged in, you can open your file manager and see if the image is already visible in the sidebar for mounting. If so, just click to mount and you're all good, although as above you'll have to be root in order to modify it. To open the file manager as root under Ubuntu:
Code:
sudo nautilus
If the image is not in the sidebar of your file manager, you'll have to mount the image manually. Use blkid to find a list of devices attached to the virtual system; the one we want is of type ext4, and *should* be the last device in the list. You can double check by finding the size of the device:
Code:
sudo blockdev --getsize64 /dev/sdX
where X is the letter of the device. This should return 3 GB or so.
Make a mountpoint:
Code:
sudo mkdir /mnt/turbo
Mount the image:
Code:
sudo mount -t ext4 /dev/sdX1 /mnt/turbo
where X is the letter of the device.
Open your file manager as root and navigate to /mnt/turbo. Under Ubuntu this would be:
Code:
sudo nautilus
Shut down your VM when you're done playing around.
Once you're done modifying the image, you need to convert it back to a raw .img format.
Code:
VBoxManage.exe clonehd turbo_system.vdi turbo_system.img --format raw
And that's it! Try not to break anything too badly. Make sure you unmount the image and/or stop your VM before flashing! This is the first guide I've written, so let me know if there's any questions you have or any improvements I can make.
First off, thanks for putting this tutorial together. I am running Windows 7 and I have downloaded all of the files that are needed to set up my virtual machine as well as the /system image that you linked to. I have, as far as I can tell, successfully added the Ubuntu image but I am stuck at adding the /system image as a HDD. I click the "Add Hard Disk" button followed by "Choose existing disk" then browse to the path that my image is in. With the default settings I can't see the .7z archive that I downloaded or the .img file that I extracted from it using WinRar. Next I tried changing the file type drop down to "All files" which allowed me to see both file types. I tried selecting both of them (at different times) and both files produce the following error when I click "Open":
Failed to open the hard disk file C:\Users\Chris & Kymber\Droid Turbo\Shared VM\xt1254.system.Blur.21.44.12.quark_verizon.rooted.ext4.img\xt1254.system.21.44.12.quark_verizon.rooted.ext4.img.
Could not get the storage format of the medium 'C:\Users\Chris & Kymber\Droid Turbo\Shared VM\xt1254.system.Blur.21.44.12.quark_verizon.rooted.ext4.img\xt1254.system.21.44.12.quark_verizon.rooted.ext4.img' (VERR_NOT_SUPPORTED).
Click to expand...
Click to collapse
I get the same error message whether I attempt to add it as an IDE or SATA drive. Am I doing something wrong or missing a step here?
Ok, I think I may have figured it out. I used the VBoxManage.exe convertdd command to convert the .img file to a .vdi file that VirtualBox can handle. I now have the drive mounted in my VM and using the command "sudo nautilus" (gksudo said it was not installed, I'm guessing this varies between different copies of Linux?) I was able to achieve root access to the drive so that I can modify it. When I'm done, can I simply use the VBoxManage.exe convertdd command from windows to convert the file back from .vdi to .img?
If you are changing things and flash an unbootable system image can you just flash a good image to recover? I would assume so since your reflashing the entire system partition.
thecaptain0220 said:
If you are changing things and flash an unbootable system image can you just flash a good image to recover? I would assume so since your reflashing the entire system partition.
Click to expand...
Click to collapse
Yep, basically flash the image that is in the mofo guide and you're back in action.
Good Idea!
Thanks for this primer on the subject! Would it be possible to please throw us some links on how to install Xposed framework, updated SuperSU Pro, wifi tethering, or remove bloatware? With any luck we can start altering the stock Moto images we have in the Dev section.
BEDickey said:
Thanks for this primer on the subject! Would it be possible to please throw us some links on how to install Xposed framework, updated SuperSU Pro, wifi tethering, or remove bloatware? With any luck we can start altering the stock Moto images we have in the Dev section.
Click to expand...
Click to collapse
You wouldn't want to alter those imaged, as they are not pre-rooted (unless you feel like doing that part yourself). It would be best to modify the image that comes with mofo as a starting point.
brennam7 said:
You wouldn't want to alter those imaged, as they are not pre-rooted (unless you feel like doing that part yourself). It would be best to modify the image that comes with mofo as a starting point.
Click to expand...
Click to collapse
I'm not saying we can't. I'm completely new to this,just trying to wrap my brain around it and participate.
I mounted the image in Linux and removed a few files to test it out. Then I unmounted the image. It seems like the modified image is the same size. Does the image retain its size? Is there a way to compact the image? I am going to try flashing it now and see if my changes are there.
thecaptain0220 said:
I mounted the image in Linux and removed a few files to test it out. Then I unmounted the image. It seems like the modified image is the same size. Does the image retain its size? Is there a way to compact the image? I am going to try flashing it now and see if my changes are there.
Click to expand...
Click to collapse
Yes, the image will retain its size.
BEDickey said:
Thanks for this primer on the subject! Would it be possible to please throw us some links on how to install Xposed framework, updated SuperSU Pro, wifi tethering, or remove bloatware? With any luck we can start altering the stock Moto images we have in the Dev section.
Click to expand...
Click to collapse
I'll look into this later today
cstone1991 said:
Ok, I think I may have figured it out. I used the VBoxManage.exe convertdd command to convert the .img file to a .vdi file that VirtualBox can handle. I now have the drive mounted in my VM and using the command "sudo nautilus" (gksudo said it was not installed, I'm guessing this varies between different copies of Linux?) I was able to achieve root access to the drive so that I can modify it. When I'm done, can I simply use the VBoxManage.exe convertdd command from windows to convert the file back from .vdi to .img?
Click to expand...
Click to collapse
Yes this should work, I'll update the OP to include this information, sorry
Edit: this doesn't work, I'll be working on a solution today, hang tight everyone
Ekkoria said:
[*]Navigate to Storage and select Add Hard Disk.
[*]Select your Turbo's system image.
Click to expand...
Click to collapse
So virtualbox doesnt let you mount an img as a harddrive. I used
VBoxManage.exe convertdd system.img system.vdi
I was able to then add the system.vdi as a harddrive, booted up ubuntu and finished following guide/making changes. (putting in my own hosts file.. 5mb addition)
After shutting down guest, I did the reverse of the above command to get back to an img...
Its 600megs short of the original img, so obviously something isnt right. Mofo says its not a valid ext4 so I did something wrong.
I really just want the modified hosts file working, adaway and adfree modify the hosts at first, and after a while it gets corrupt/reverts, I imagine because it was modified after the phone boots.
Ugh.
ntxct said:
So virtualbox doesnt let you mount an img as a harddrive. I used
VBoxManage.exe convertdd system.img system.vdi
I was able to then add the system.vdi as a harddrive, booted up ubuntu and finished following guide/making changes. (putting in my own hosts file.. 5mb addition)
After shutting down guest, I did the reverse of the above command to get back to an img...
Its 600megs short of the original img, so obviously something isnt right. Mofo says its not a valid ext4 so I did something wrong.
I really just want the modified hosts file working, adaway and adfree modify the hosts at first, and after a while it gets corrupt/reverts, I imagine because it was modified after the phone boots.
Ugh.
Click to expand...
Click to collapse
Odd. Virtualbox may have compressed the image. See if you can turn that off. I'll work on it myself later today, see if I can get it working
http://forum.xda-developers.com/nexus-4/general/diy-manually-installing-xposed-t2369618
Found this guide to install xposed manually will try it out soon
ntxct said:
So virtualbox doesnt let you mount an img as a harddrive. I used
VBoxManage.exe convertdd system.img system.vdi
I was able to then add the system.vdi as a harddrive, booted up ubuntu and finished following guide/making changes. (putting in my own hosts file.. 5mb addition)
After shutting down guest, I did the reverse of the above command to get back to an img...
Its 600megs short of the original img, so obviously something isnt right. Mofo says its not a valid ext4 so I did something wrong.
I really just want the modified hosts file working, adaway and adfree modify the hosts at first, and after a while it gets corrupt/reverts, I imagine because it was modified after the phone boots.
Ugh.
Click to expand...
Click to collapse
Try the following:
Code:
VBoxManage.exe clonehd path/to/turbo.vdi turbo.img --format raw
Ekkoria said:
Try the following:
Code:
VBoxManage.exe clonehd path/to/turbo.vdi turbo.img --format raw
Click to expand...
Click to collapse
Hey! Same size as original now. Thanks, Ill keep moving forward
UPDATE:
Flashed completed, booted normally. Verified the edited hosts file was there, it was. Everything seems to be working how I was hoping! Oddly the system did create (or I did along the way) a second hosts file in the etc folder, "hosts~" which is a default hosts file. However the system doesnt seem to use it, just the edited one so its no big deal but maybe its a permission issue?
ntxct said:
Hey! Same size as original now. Thanks, Ill keep moving forward
UPDATE:
Flashed completed, booted normally. Verified the edited hosts file was there, it was. Everything seems to be working how I was hoping! Oddly the system did create (or I did along the way) a second hosts file in the etc folder, "hosts~" which is a default hosts file. However the system doesnt seem to use it, just the edited one so its no big deal but maybe its a permission issue?
Click to expand...
Click to collapse
Not sure about the hosts deal, but hey, if it works right?
OP updated to include the new information.
Ekkoria said:
Not sure about the hosts deal, but hey, if it works right?
OP updated to include the new information.
Click to expand...
Click to collapse
So i got this going finally. Removed a bunch of bloat, shot the lollipop boot animation in there, as well as some xposed parts. Compiling it back to system.img now, but its sitting at 0% for quite some time. Not sure if thats normal?
EDIT: oh dear christ it just went to 10%. This is going to take some time
EDIT 2: And now it sits at the boot animation but never boots. Not sure why, as i didn't really make any major changes. time to pick this think apart.
hi, have you installed xposed successfully and does it function correctly?
123421342 said:
http://forum.xda-developers.com/nexus-4/general/diy-manually-installing-xposed-t2369618
Found this guide to install xposed manually will try it out soon
Click to expand...
Click to collapse
Haven't seen this mentioned, but might have missed it: can we symlink /system/etc/hosts to /data/data/hosts (before flashing) to maintain write access to the hosts file?
Guide: Getting Xposed RunningThis morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
What you'll need:
A paid copy of Mofo (obviously)
Either a modified system image containing Xposed already, or if you like, you can modify one yourself as described in this tutorial. I've already created a modified system image to include Xposed as well as Wifi Tethering and a modified hosts file for ad blocking.
The Xposed Installer apk
Xposed Installer needs to be installed on your phone
Terminal Emulator and ES File Explorer from the play store need to be installed on your phone
A rooted image flashed to your phone
Before flashing anything, this is what you need to do:
On your computer, find your de.robv.android.xposed.installer_v33_36570c.apk and rename it to be a .zip file.
Open this .zip file and extract /assets/XposedBridge.jar and, if you're modifying your own system image, extract /assets/arm/app_process_xposed_sdk16 as well.
Put XposedBridge.jar somewhere on your phone, I like to use the Downloads folder so I don't lose track of it later.
In ES File Explorer, navigate to /data (NOT SDCARD/DATA)
{
"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"
}
Make sure it doesn't say sdcard > data!
Create a folder called "xposed"
Long press the folder, select properties, and set permissions to 755
Set the owner of the folder to root and the group to shell
Move XposedBridge.jar into the xposed folder we just created.
Make the permissions of XposedBridge.jar 644
As before, make the owner root and the group shell.
Open the Xposed Installer app on your phone.
Open terminal emulator and type
Code:
ps | grep xposed
This will return a pattern like the following. Make a note of the first seven characters, as shown (the first is a lowercase u)
Return to /data/xposed
Create two new files: modules.list and modules.whitelist
Make the permissions on both files 644 as above
Set the owner to the seven characters we noted down earlier and the group to shell on both files
If you're flashing a pre-compiled image with Xposed, you're done here! Go ahead and flash, and enjoy!
If you're modifying your own system image, you've got some more work to do. Take app_process_xposed_sdk16 from the Xposed apk and rename it to app_process.
In your turbo system image, navigate to /bin/ and replace app_process with the one from Xposed Framework. Make sure its permissions are set to 755:
Code:
sudo chmod 755 /path/to/img/bin/app_process
Linux does not allow setting the group of a file to a nonexistent group, so on your pc you'll have to make a shell group:
Code:
sudo groupadd shell
Change the group of app_process to shell:
Code:
sudo chgrp shell /path/to/img/bin/app_process
You're ready to flash!
NOTE: If XposedBridge.jar reports problems, try setting installation mode in the Xposed installer app to recovery (flash manually) and hitting install, then reboot.
You're done! Xposed should show up as installed! Don't use any modules that require system write access, such as replacing system icons, but most modules (ie GravityBox) work fine without it.
Ekkoria said:
This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
Click to expand...
Click to collapse
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
ntxct said:
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
Click to expand...
Click to collapse
Same here! When I finally opened Xposed Installer and saw it read the framework as installed, I've almost never been so excited about something Android.
i dont need it but its a great guide, easy, short and with pictures!
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Thanks so much man, about to flash. Will let you know how it goes.
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
It did not work for xposedbridge.jar
aven1357 said:
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Click to expand...
Click to collapse
Yes, you will need to be rooted first to perform these actions. Apologies for not originally including this. OP updated
savagebunny said:
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
Click to expand...
Click to collapse
Yes please do so. I'd be very interested.
Sent from my XT1254 using XDA Free mobile app
I am having trouble with es file explr it tells me the operation failed when trying to do anything I have root and I enabled root for ES it seemed to work on root browser fine (I reset my device and just installed es so far)
edit checked and the root enhancement options are greyed out?
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
I am having same problem as u smokie
smokie75 said:
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
Click to expand...
Click to collapse
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
Thanks! That worked!
Thanks for this , works great , now we just need one with busybox preinstalled
Stuck at this point any help?[/ATTACH]
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
so will doing this enable gravitybox to work on the turbo?
hmltnjrmy7 said:
Stuck at this point any help?[/ATTACH]
Click to expand...
Click to collapse
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
rayjr13 said:
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
Click to expand...
Click to collapse
Lol the dead droid freaked me out at first, but I'm so happy xposed finally works!!!
***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY***
CLEAR/DELETE DALVIK-CACHE FOLDER FROM "/data/dalvik-cache" IN ROOT EXPLORER OR TWRP AFTER INSTALLING BOOT IMAGE TO ALLOW SYSTEM TO ADJUST
##FLASH THE LATEST SUPERSU ZIP BELOW##
P.S. I NOTICE IT IS NO LONGER SYSTEM-LESS MODE. SO WE CAN TRIM THE SUPERSU SYSTEM-LESS CONTENT FROM THE RAMDISK.
Tweaked the contents of the boot image to allow for faster boot and better runtime performance. I use it as my daily driver. App performance is snappier. Only for the Boost Desire 626s. Unzip and flash with Flashify, TWRP, or your choice of image flasher. I also added some optimization scripts to supplement the boot image. Run them with Smanager, Root Explorer or in the terminal. Also here is a zip 601626SPIEFIX.zip that when flashed in TWRP recovery will allow the system to run non-pie executables and it works great. You'll be able to run custom binaries without any issue or error. All zips in this thread are the latest.
If you have ISSUES WITH DATA SPEEDS in certain areas, especially if you tether, GO INTO THE DIALER and DIAL *#*#4636#*#* then ACCESS PHONE INFORMATION and SELECT CDMA auto (PRL) UNDER SET PREFERRED NETWORK TYPE. LTE seems to be problematic in certain areas with speeds dropping to 150kbps and with this solution you'll be getting about 600 to 700kbps so at least it'll be a gain until you get into an area with better LTE coverage. In a good coverage area, I get download speeds of up to 5 to 7 mbps with LTE on, but in bad areas, CDMA works better. If you want to tether with a wireless third party solution make sure to run in a terminal window or adb shell as root : pm disable com.htc.tetheringguard
DOWNLOAD BOOT IMAGE: http://forum.xda-developers.com/attachment.php?attachmentid=3917986&d=1477604429
DOWNLOAD SUPERSU BETA: https://download.chainfire.eu/1009/SuperSU/SR2-SuperSU-v2.78-SR2-20161029143931.zip?retrieve_file=1
DOWNLOAD SCRIPTS: http://forum.xda-developers.com/attachment.php?attachmentid=3863279&d=1472880351
DOWNLOAD PIE FIX: http://forum.xda-developers.com/attachment.php?attachmentid=3844539&d=1471383163
DOWNLOAD BOOT IMAGE TOOL : http://forum.xda-developers.com/attachment.php?attachmentid=3917995&d=1477605263
DOWNLOAD HTC DRIVERS AND MINIMAL ADB + FASTBOOT: http://forum.xda-developers.com/attachment.php?attachmentid=3868562&d=1473328405
ANDBLOCKDEV.sh from scripts zip will speed up file input and output speeds, its contents have been incorporated into the boot image so the scripts files are for your own archival.
The zip DESIRE626SIMGTOOL.zip contains the android image kitchen and the 6.0.1 Boost Desire 626S boot image contents already extracted into two folders split_img and ramdisk with recent modifications. Enjoy!
http://www.vysor.io/ is a great tool to control your android device from a computer within chrome. You should try it out.
I provided a zip named HTCDrivers.zip containing the installation for both fastboot and adb drivers for the Boost Desire 626S, and minimal adb and fastboot. This will help you connect your device up with Vysor.
COPY the FILES; fastboot.exe, adb.exe, AdbWinUsbApi.dll and AdbWinApi.dll FROM - C:\Program Files (x86)\Minimal ADB and Fastboot - TO - C:\Windows\System32 - AND - C:\Windows\SysWOW64
Once you have installed the drivers for HTC devices,
and copied the minimal adb and fastboot files specified above to both system folders, you should be able to run adb commands without a problem by just opening a command prompt as administrator,
and RUNNING the command:
adb devices
- to start the adb server. This will allow connection with Vysor.
##########
For those who prefer nightbreed813's 6.0.1 slim rom version, I uploaded 601VPNDIALOGSFIX.zip to fix the issue with authorizing VPN clients, but first YOU HAVE TO CREATE /system/priv-app/VpnDialogs in Root Explorer or any other root filesystem browser, then reboot to TWRP recovery and flash the zip.
DOWNLOAD VPNFIX : http://forum.xda-developers.com/attachment.php?attachmentid=3860930&d=1472669879
##########
Also, you can get your MSL/SPC security code easily.........
Use the info in this thread to get your MSL/SPC security code so you can write new values to NV entries in the modem. Some values are locked but you can change the BC config for both LTE and CDMA so that would at least be helpful.
INFO HERE: http://forum.xda-developers.com/spri...k-sim-t3314755
##########
Android settings can be changed in the terminal for three namespaces; system, global and secure.
In the terminal run:
settings list system
settings list global
settings list secure
For each namespace all associated settings and their values will be listed. To change a setting type:
settings put system setting_name_here value_here
settings put global setting_name_here value_here
settings put secure setting_name_here value_here
##########
{
"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"
}
Look now has working VPN......
***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY***
anthonykb said:
Tweaked the contents of the boot image to allow for faster boot and better runtime performance. I use it as my daily driver. App performance is snappier. Only for the Boost Desire 626s. Unzip and flash with Flashify, TWRP, or your choice of image flasher. I also added some optimization scripts to supplement the boot image. Run them with Smanager, Root Explorer or in the terminal. Also here is a zip 601626SPIEFIX.zip that when flashed in TWRP recovery will allow the system to run non-pie executables and it works great. You'll be able to run custom binaries without any issue or error. All zips in this thread are the latest.
Click to expand...
Click to collapse
Will this run on the Metro Variant?
As far as I know no but you can try in case it might.
Enter these commands in a new terminal window:
cd /dev/block/platform/soc.0/7824900.sdhci/by-name
dd if=boot of=/sdcard/backup.img
The backup boot image can be flashed from the sdcard in TWRP recovery if the device fails to boot into the system after flashing the boot image contained in the zip in the attachments.
Is there anyway you would be able to make one for the metro Variant if i upload my boot image?
MetroPCS Boot Image
GotHeart said:
Is there anyway you would be able to make one for the metro Variant if i upload my boot image?
Click to expand...
Click to collapse
Did you try unzipping the boot image and flashing it already? I don't think it could work that way. I would do it if I had the metro version myself.
anthonykb said:
Did you try unzipping the boot image and flashing it already? I don't think it could work that way. I would do it if I had the metro version myself.
Click to expand...
Click to collapse
Thats what im saying.if i upload my metro boot image would you be able to optimize it like you did before with the boost Variant?
GotHeart said:
Thats what im saying.if i upload my metro boot image would you be able to optimize it like you did before with the boost Variant?
Click to expand...
Click to collapse
I meant so you tried the boost version and it wouldn't boot?
anthonykb said:
I meant so you tried the boost version and it wouldn't boot?
Click to expand...
Click to collapse
No i havent tried it yet
GotHeart said:
No i havent tried it yet
Click to expand...
Click to collapse
Backup your kernel boot image to your sdcard and flash the boost version just to make sure.
cd /dev/block/platform/soc.0/7824900.sdhci/by-name
dd if=boot of=/sdcard/backup.img
Then unzip the 601bootimg.zip file with Zarchiver in the Play Store and flash the extracted boot image.
anthonykb said:
Backup your kernel boot image to your sdcard and flash the boost version just to make sure.
Click to expand...
Click to collapse
Okay ill do it now and let you know
The phone booted but it corrupted my sdcard,so i lost everything i had on there.
GotHeart said:
The phone booted but it corrupted my sdcard,so i lost everything i had on there.
Click to expand...
Click to collapse
Flash back the backed up boot image in TWRP and see if the sdcard mounts right. The mount point contained in the boost boot image is probably wrong for the the sdcard/emmc in the metropcs phone.
I did but my sdcard got corrupted so i was forced to format it.
GotHeart said:
I did but my sdcard got corrupted so i was forced to format it.
Click to expand...
Click to collapse
I'm so sorry the process turned out to be a dud for you I have the boost model myself. Hope you can recover your files with one of those forensic data recovery tools.
anthonykb said:
I'm so sorry the process turned out to be a dud for you I have the boost model myself. Hope you can recover your files with one of those forensic data recovery tools.
Click to expand...
Click to collapse
Its nothing important lol.any chance you can share what you did or how?
Use the Android Image Kitchen by osm0sis
GotHeart said:
Its nothing important lol.any chance you can share what you did or how?
Click to expand...
Click to collapse
Use the tool at the link below to unpack the image, make your modifications, and repack the image contents (The ramdisk and split_img folders.) It's available for Windows, Linux and Android. It's a simple process expect for knowing what you'd need to do to the image.
http://forum.xda-developers.com/showthread.php?t=2073775
anthonykb said:
Use the tool at the link below to unpack the image, make your modifications, and repack the image contents (The ramdisk and split_img folders.) It's available for Windows, Linux and Android. It's a simple process expect for knowing what you'd need to do to the image.
http://forum.xda-developers.com/showthread.php?t=2073775
Click to expand...
Click to collapse
My mistake i was in a hurry when i typed that last reply.
Im aware of how to unpack/repack boot images and i appreciate the link,but i was wondering what modifications that were made.if youd prefer not to share,i can upload my boot image if youd like to make the modifications yourself.im just trying to make this compatible with the metro version.
The same modifications done for the Boost Desire 626S might not work well for the MetroPCS version so upload the image you backed up yesterday as an attachment in a reply post and I'll work on it.
Thanks a ton!
MetroPCS Boot Image
GotHeart said:
Thanks a ton!
Click to expand...
Click to collapse
Run busybox top in the terminal on your phone and post some screenshots so I can see what might need to be done. We want to see what processes would be the culprit behind bogging down precious processor time and reducing the snappiness of the device in reacting to realtime input and handling current requests.
Instructions HERE.
TO DO:
- Other things mentioned in the wiki:
https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)
VERSION INFORMATION (CHANGELOG)
A newer MATE image is available to download. Download it here or here.
Notes about this release:
v4.0
- Please read the updated instructions.
- Vast performance improvements overall (because it's using mainline 5.12.8 grate kernel).
- It's trickier to get it working, if you cannot follow the instructions please change to v3.0.
v3.0
- Firmware has to be renamed at first boot.
Do the following command as root or using sudo:
Code:
sudo ash rename-firmware.sh
Those who are migrating from older versions or want to know what this .sh file is:
https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)
Follow the wiki, look into Wi-Fi section.
Reboot and done.
- Bluetooth is working, but only from terminal.
Code:
sudo hciconfig hci0 up
hcitool scan
hcitool pair, etc etc
- Buttons from trackpad are working, mousepad not yet.
- Updated kernel zip. Latest release here: https://github.com/antonialoytorren...rnel_zip/PostmarketOS-kernel-3.1.10-15-r2.zip
v2.0
- Changed icons (https://github.com/vinceliuice/vimix-icon-theme) and GTK (https://github.com/vinceliuice/vimix-gtk-themes) of XFCE. Now it is a modern XFCE.
- Removed second panel to save space.
- The XFCE Whiskermenu does not close when typing in onboard.
· Other things that will be included in the next release:
- Make a desktop shortcut opening a browser linking this XDA thread.
- Try to get trackpad working
v1.0
- Initial Release
Screenshots
MATE 4.0 (mainline PostmarketOS kernel)
See HERE.
https://imgur.com/a/Sf7BbFt
XFCE 2.0
{
"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"
}
XFCE
MATE
JWM
Dual Booting Android and PostmarketOS
You can only dual boot if you have installed postmarketOS in your microSD or SD Card. If not, you (probably) have to wipe your partition where postmarketOS is located for booting Android again.
Well, the easiest way to do dual boot is this:
In the sdcard folder or whatever folder you want, put the Android ROM zip and PostmarketOS' kernel zip.
Note: Be sure to run the TWRP version 2.8.1.1, otherwise Android won't flash.
The Android ROM (I'm using timduru's ROM: https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496) can be downloaded here: https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip
The PostmarketOS' kernel zip can be downloaded here: https://github.com/antonialoytorrens/TF101-linux-images/raw/master/postmarketOS/kernel_zip/PostmarketOS-kernel-3.1.10-15.zip (has some issues with WiFi, flashing the blob using dd and adb is more recommended, https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101))
If you want Android, go to recovery and flash timduru's ROM.
If you want PostmarketOS, go to recovery and flash my kernel zip (please, disable signature verification when flashing)
Reserved
Reserved
aat596 said:
XFCE
MATE
Click to expand...
Click to collapse
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations
be.sign said:
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations
Click to expand...
Click to collapse
Having the PostmarketOS system in internal memory is harder and more difficult. You cannot install it on the bigger partition (the 30 GB one), I once tried and almost bricked my tablet because fails to boot due to media/ symlinks.
Unfortunately, you have to install it on /dev/block/mmcblk0p1 (533 MB partition).
I'm trying to make an usable small desktop image for /dev/block/mmcblk0p1 , XFCE is too big for that.
Nevertheless, you can enter recovery mode, do a Factory Reset and wipe Internal Memory to delete Android; then boot Linux from SDCard and use all available space to store your files.
If you want to make your image yourself, please look at https://wiki.postmarketos.org/wiki/Installation_guide and https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)
be.sign said:
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations
Click to expand...
Click to collapse
EDIT: A mini JWM image is available for download. It has the size to fit in the Asus TF101 first partition (/dev/block/mmcblk0p1). Download here: https://downloads.sourceforge.net/project/tf101-linux-images/postmarketOS/minijwm-postmarketOS-TF101.zip
Then execute exactly the following commands:
Code:
$ unzip minijwm-postmarketOS-TF101.zip
$ cd minijwm-postmarketOS-TF101
$ adb push blob-asus-tf101 /cache
$ adb push minijwm-tf101.img /sdcard
$ adb shell
# dd if=/cache/blob-asus-tf101 of=/dev/block/mmcblk0p4
# dd if=/sdcard/minijwm-tf101.img of=/dev/block/mmcblk0p1
Hello, thanks a lot for your sharing
I have an error with the XFCE image. When in try to boot from an external SDCard, following message occurs : "Initramfs-extras not found".
It work's without any problem when i boot from a custom built flashed on internal storage.
Do you have an idea from the causes ?
Raphzer said:
Hello, thanks a lot for your sharing
I have an error with the XFCE image. When in try to boot from an external SDCard, following message occurs : "Initramfs-extras not found".
It work's without any problem when i boot from a custom built flashed on internal storage.
Do you have an idea from the causes ?
Click to expand...
Click to collapse
This means that initramfs-asus-tf101-extra file is missing from pmOS_boot partition. All files located in this partition are strictly required.
EDIT: Btw, now I have download the XFCE image from sourceforge, flashed it into a new SD Card and boots fine.
aat596 said:
This means that initramfs-asus-tf101-extra file is missing from pmOS_boot partition. All files located in this partition are strictly required.
EDIT: Btw, now I have download the XFCE image from sourceforge, flashed it into a new SD Card and boots fine.
Click to expand...
Click to collapse
I don't understand why it doesn't work with sdcard. I have tried to flash my working build on the sdcard and the same error occurs
No file are missing on the sdcard, very strange.
Raphzer said:
I don't understand why it doesn't work with sdcard. I have tried to flash my working build on the sdcard and the same error occurs
No file are missing on the sdcard, very strange.
Click to expand...
Click to collapse
If it's your own working build then try these steps:
Code:
$ sudo pmbootstrap init (select asus-tf101 device, select [I]none[/I] when prompting graphical interface)
$ sudo pmbootstrap install && sudo pmbootstrap export
$ sudo dd if=/tmp/postmarketOS-export/asus-tf101.img of=/path/of/sdcard status=progress
$ adb push /tmp/postmarketOS-export/blob-asus-tf101 /cache
$ adb shell
# dd if=/cache/blob-asus-tf101 of=/dev/block/mmcblk0p4
And then insert your sdcard and reboot.
Hope this helps. I have extracted it from https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101). The only difference is flashing onto internal memory or the sd card.
EDIT: Are you using a reliable SD Card (Kingston, SanDisk, ...)? It could lead to random errors or not identify it if not.
This is what i did :/
Yep,i used this sdcard on a raspberrypi before.
I think he problem come from partition label name. As i have flash everything on internal memory and sdcard, i have 2 partition named pmos_boot. In the initramfs init script, there is multiple references to label name especially for loading initramfs-extras.
I will do some tests in that way.
Raphzer said:
This is what i did :/
Yep,i used this sdcard on a raspberrypi before.
I think he problem come from partition label name. As i have flash everything on internal memory and sdcard, i have 2 partition named pmos_boot. In the initramfs init script, there is multiple references to label name especially for loading initramfs-extras.
I will do some tests in that way.
Click to expand...
Click to collapse
Yes, it could be the reason. If you run into multiple problems, try to format /system in TWRP and then try it again with only the SD Card.
Btw, what version is your TF101? SBKv1 or SBKv2? I have SBKv1, that could be another problem (but I'm not sure, as the SD Card is partition-independent, and the kernel blob file is compatible for both versions)
Very nice image !
Just tested and looks very promising.
USB mouse and keyboard gets detected but don't work.
oink666 said:
Just tested and looks very promising.
USB mouse and keyboard gets detected but don't work.
Click to expand...
Click to collapse
Yep, that's one of the things mentioned in the TODO list in my guide (look at nearly the end)
We have to compile xf86-mtrack-driver to get it working (there's no such driver in Alpine repos)
I lack a bit of C knowledge to get it working (because it fails when compiling), so help is appreciated
Awesome work.
Any chance of dual boot?
Thank you
riptide981 said:
Awesome work.
Any chance of dual boot?
Thank you
Click to expand...
Click to collapse
You can only dual boot if you have installed postmarketOS in your microSD or SD Card. If not, you (probably) have to wipe your partition where postmarketOS is located for booting Android again.
Well, the easiest way to do dual-boot is this:
In the sdcard folder or whatever folder you want, put the Android ROM zip and PostmarketOS' kernel zip.
The Android ROM (I'm using timduru's ROM: https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496) can be downloaded here: https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip
The PostmarketOS' kernel zip can be downloaded here: https://github.com/antonialoytorrens/TF101-linux-images/raw/master/postmarketOS/kernel_zip/PostmarketOS-kernel-3.1.10-15.zip
If you want Android, go to recovery and flash timduru's ROM.
If you want PostmarketOS, go to recovery and flash my kernel zip (please, disable signature verification when flashing)
XFCE 2.0
A newer XFCE image is available to download. Download it here: https://sourceforge.net/projects/tf101-linux-images/files/postmarketOS/xfce-postmarketOS-TF101-v2.0.zip
A little screenshot:
Notes about this release:
v2.0
- Changed icons (https://github.com/vinceliuice/vimix-icon-theme) and GTK (https://github.com/vinceliuice/vimix-gtk-themes) of XFCE. Now it is a modern XFCE.
- Removed second panel to save space.
- The XFCE Whiskermenu does not close when typing in onboard.
· Other things that will be included in the next release:
- Make a desktop shortcut opening a browser linking this XDA thread.
- Try to get trackpad working
v1.0
- Initial Release
Cool stuff - i tried the latest v2.0 image but ran into some issues:
If I have the keyboard docked it won't boot - it ends up with a blinking cursor top left of the screen and a bunch of errors are shown repeatedly during bootup.
Without the keyboard it boots correctly - keyboard wont work if attaching the keyboard after the system is up.
https://photos.google.com/share/AF1...?key=UUFNdVNfZ3N6X0ZOX054eDJLYWxWd0tPYThCV1dR
Any idea on what I could try to get this going?
gh05tface said:
Cool stuff - i tried the latest v2.0 image but ran into some issues:
If I have the keyboard docked it won't boot - it ends up with a blinking cursor top left of the screen and a bunch of errors are shown repeatedly during bootup.
Without the keyboard it boots correctly - keyboard wont work if attaching the keyboard after the system is up.
https://photos.google.com/share/AF1...?key=UUFNdVNfZ3N6X0ZOX054eDJLYWxWd0tPYThCV1dR
Any idea on what I could try to get this going?
Click to expand...
Click to collapse
I have just redownloaded zip file from sourceforge and I don't have this problem, so I don't know what it could be...
But there are some questions I would like to ask you:
- Does your keyboard work on Android? You can test it by flashing Timduru's Android image (https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip).
- Have you tried to do your own XFCE from scratch? https://github.com/antonialoytorrens/TF101-linux-images#doing-xfce-from-scratch. Hope this works, otherwise a patch for this kernel is needed.
- By the way, what version is your TF101? SBKv1 or SBKv2? I have SBKv1.