Database Info

[App] Root Toolkit for Android™

.
Market link: Android Root Toolkit (free)
Root Toolkit for Android™
I wrote this little root utility for myself to help consolidate and automate some root functions that are available in various other apps, but nowhere all together.
Note: this utility does not root your Android device--it assumes that your device is already rooted.
If you are having problems or issues with it, please send me an email at [email protected] with as much detail as you can provide.
FEATURES:
display current root, /system and root (/) mount status, and root save status; will also display bootloader lock status for the Samsung Galaxy Nexus
reboot options (normal, recovery, bootloader)
power off device
remount rootfs (/) and/or /system in read-write or read-only mode; note: remount behavior changed in Android 4.2 and higher that causes remount effect to not be usable by apps other than the one that initiated the remount
save (protect) / restore root function; for 4.2 devices with ext2/3/4 /system partitons, a copy of su binary can be saved and later restored; for 4.3 devices, I've implemented Pau Oliva's 4.3+ "OTA rootkeeper" functionality (i.e., via keeproot.sh)
freeze (disable) or thaw (enable) an application (use caution when freezing a system app!); you can select showing user and/or system apps in the Freeze/Thaw Display Options in the Preferences/Settings menu
display system (getprop) property values
Galaxy Nexus and Nexus 7 (1st gen) only options:
flash a stock recovery
flash various custom recoveries
make recovery "stick" (keep stock recovery from overwriting your custom recovery)
identify currently installed recovery
bootloader lock, unlock, status (Galaxy Nexus only)
option to turn confirmation mode on / off (defaults to on)
option to turn "safe mode" on for the app to prevent any su or flashing operation from occurring
Warning / disclaimer: the author of this app is not responsible for any loss or damage caused by or related to its use.
If you are not comfortable with or knowledgeable about the proper use and functionality of this app, please discontinue its use and uninstall.
Click to expand...
Click to collapse
PERMISSIONS:
INTERNET - for downloading recoveries from the internet
WRITE_EXTERNAL_STORAGE - this is for the downloaded recoveries and work files used to identify which recovery is currently installed
ACCESS_SUPERUSER permission to support interaction with SuperSU
Keywords: root status, root checker, mount status, flash stock recovery, flash custom recovery, reboot recovery, reboot bootloader, power off device, remount system, make recovery stick, identify recovery, save root, restore root, freeze app, disable app, thaw app, enable app,
bootloader lock, bootloader unlock, bootloader status, getprop, system properties
Screen shots:
{
"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"
}
--------------------------------------
Android is a trademark of Google, Inc.

Version 1.3 just uploaded to the Market:
[version 1.3 - 22-April-2012]:
- support freezing (disabling) or thawing (enabling) applications
..(take care before deciding to freeze a system app)
These updates weren't as easy or straight-forward as I had imagined it would be--no wonder there's so few apps out there that have the freeze/thaw feature .

interesting and important tool
I am very interested in this tool and will have a try for sure. Number of questions:
1. Can your tool save current recovery as a blob, which is either cwm flashable or dd flasable(flash through "dd if=/sdcard/recovery_blob_backup of=/dev/block/mmcblk0p4"). My ASUS TF101 is rooted with stock recovery, I would like to try cwm recovery, but I want to save my stock recovery so that I can switch back to stock recovery when OTA is coming.
2. The most important features are those marked as "Galaxy Nexus only options". Is it harmful to try these on other devices such as ASUS transformer.
3. Does it work to use cwm recovery to flash official firmware package without any repacking. How about your tool?
Thanks in advance
---------- Post added at 03:51 PM ---------- Previous post was at 03:30 PM ----------
Two more questions:
4. The su backup made by Voodo rootkeeper is not "immutable", it can be revoced by "chattr -i" and then "rm". how about your backup?
5. If superuser.apk is removed or disabled, does your root protection tool
still work?
Thanks

e154037 said:
I am very interested in this tool and will have a try for sure. Number of questions:
1. Can your tool save current recovery as a blob, which is either cwm flashable or dd flasable(flash through "dd if=/sdcard/recovery_blob_backup of=/dev/block/mmcblk0p4"). My ASUS TF101 is rooted with stock recovery, I would like to try cwm recovery, but I want to save my stock recovery so that I can switch back to stock recovery when OTA is coming.
Click to expand...
Click to collapse
The app will not save a current recovery (not a currently implemented function).
I can tell you I tried copying the currently installed recovery on my GNex using exactly the process you described above. Unfortunately, the flash_image of that copy/backup does not appear to flash properly (and/or I got an error--I think I did get an error when doing the flash and ended-up trying several different versions of the flash_image utility to no avail). The resultant backup/copy of the recovery partition was usually about 12MB vs. approx. 5MB for a "normal" other recovery file that you would flash, so I don't know if its a size issue or limitation with the flash_image utility or not, but flashing a copy of the whole recovery partition did not work for me on the GNex.
I suppose "flashing" via the dd command might / would work, but I haven't yet tried that (dd is scary ).
2. The most important features are those marked as "Galaxy Nexus only options". Is it harmful to try these on other devices such as ASUS transformer.
Click to expand...
Click to collapse
I have product/device checks in the app that should keep those options from even being available to you on the main menu if its not a GNex device. The Setting / Preferences settings will still appear, but if you don't have a GNex, they should not appear on the actual main menu (I'd be very interested to know if they do ).
3. Does it work to use cwm recovery to flash official firmware package without any repacking. How about your tool?
Click to expand...
Click to collapse
My app uses the flash_image utility to flash its recoveries for the GNex. It does not use ROM Manager or ClockworkMod for any flashing operations that it undertakes.
4. The su backup made by Voodo rootkeeper is not "immutable", it can be revoced by "chattr -i" and then "rm". how about your backup?
Click to expand...
Click to collapse
Yep, works exactly the same .
The immutable property is apparently only supported on the ext2/3/4 type of filesystems (I think that's the right list)
5. If superuser.apk is removed or disabled, does your root protection tool
still work?
Click to expand...
Click to collapse
I never specifically tested removing Superuser.apk, but you should/would still be able to re-download that app from the Market and install it to complete the second half of root (the first being restoration of the su binary).
~ ~ ~
You should know that the GNex-only options that I support in the app were basically because I own a GNex and wanted to support some functions that I got tired of doing via other apps. Supporting devices other than the GNex is not currently in my plans since it these things are very device- and recovery-specific and I wasn't comfortable releasing features and functionality that I could not directly test and validate myself.
Cheers!

Thanks for the explanation. Where can I find the flash_image utility, is it device spacifilc? If it is not your self-made component, can you give me a copy of the utility.

e154037 said:
Thanks for the explanation. Where can I find the flash_image utility, is it device spacifilc? If it is not your self-made component, can you give me a copy of the utility.
Click to expand...
Click to collapse
Ah, there's a billion copies of it "out there", but you should be able to extract if from the .apk file of my app if you want.
Just make a copy of .apk file (its really just a .zip file, after all). Then use a file explorer or unzip utility and explore res/raw folder (I think that's where it is).
It should work on all Android devices (I've got/found multiple copies and versions of various ages and sizes that I'm sure are due to the different builds of Android).
The key thing you need to be careful of is making sure you've got the proper partition / area that you are going to be flashing to (i.e., the recovery partition is not located in the same place / name on every device and there's no way (that I'm aware of) to universally describe how to identify it (short of looking in the build code for your specific device)). Flashing a recovery to the boot partition is a quick and easy way to brick your device .
Also, making sure that you've verified that integrity of the file you are flashing (i.e., via and MD5 or SHA1 checksum) is always a good idea. There's no inherent checksum / integrity check done by the flash_image utility--it'll flash anything to anywhere you tell it (or at least try to).
All due caution and a current Nandroid backup is always your best friend .
Cheers!

Thanks.
Stupid me! I should have realized that the tool could be extracted from your apk or for ROM manager.
Question on image file used in flash_image:
Asus official firmware package's zip file contains a file "blob", unpack the blob one can find a number of images, including blob.SOS. This blob.SOS is the stock recovery image. To my knowledge, blob.SOS should be repacked when being flashed with dd.
Is this blob.SOS (witout any repack) the right one goes with flash_image (flash_image recovery /sdcard/blob.SOS)?

e154037 said:
Thanks.
Stupid me! I should have realized that the tool could be extracted from your apk or for ROM manager.
Question on image file used in flash_image:
Asus official firmware package's zip file contains a file "blob", unpack the blob one can find a number of images, including blob.SOS. This blob.SOS is the stock recovery image. To my knowledge, blob.SOS should be repacked when being flashed with dd.
Is this blob.SOS (witout any repack) the right one goes with flash_image (flash_image recovery /sdcard/blob.SOS)?
Click to expand...
Click to collapse
LOL, no worries! (I've had more than my share of those moments )
I'm not familiar with the Asus .zip package formats or the blobs.
But, I would think you could verify that you are talking apples-to-apples (so-to-speak) if you were to calculate the MD5 of a current blob recovery file with an extracted dd dump of the currently installed recovery's MD5 file (i.e., find the published blob that should match what you have installed; if they match, then you are on the right track, otherwise, you'll have to re-evaluate and dig a little deeper).
Cheers!

Says i dont have superuser.apk but i do ..
Sent from my VS910 4G using xda premium

motodroidfreak said:
Says i dont have superuser.apk but i do ..
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Hmm, do you know where it's actually installed (i.e., the full file path)?
My app checks for "Superuser.apk" or "SuperUser.apk" in the /system/app directory.
Lemme know where yours is installed and I'll make a quick tweak .
Cheers and thanks!

Android Root Toolkit: updated to version 2.6
New version just published to the Play Market...thanks!
Here's the most recent change log items:
[version 2.6 - 08-December-2013]:
- support save root for 4.3+ devices (credit/thanks to Pau Oliva (poliva) and Chainfire)
- fix FC caused in some devices that return weird (non-standard) Android version information
- 2012 N7 only: support 4.3 (jwr66y) and 4.4 (krt16s) stock recoveries
- Samsung Galaxy Nexus only: support recent stock recoveries for international and Sprint versions
- address transitory mount behaviour that apparently started in Android 4.2 and up
- display warnings for keeping a pre-4.3 saved root present before installing a 4.4+ OTA
- lots of other minor tweaks, cleanups, and enhancements
Click to expand...
Click to collapse

CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1

CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1​
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.40.1)
https://docs.google.com/uc?id=0B5c3gpyMBJusXzRMMG1tLUxRMWM&export=download
aromafm_beni.zip (v1.91)
https://drive.google.com/uc?id=0B5c3gpyMBJusc204SHRZdTBucHc&export=download
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ Touch Recovery for Galaxy Fit, Tool/Utility for the Samsung Galaxy Fit GT 5670
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-07

:FAQs:​
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.

NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary
commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"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"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root

i tried your recovery by creating a zip update
you should work more on it because the graphic in some aroma installer or aroma file manager doesnt work too good!
and just feels the normal CWM and not Philz recovery !
But any way, Good Job!

Rminsh said:
i tried your recovery by creating a zip update
you should work more on it because the graphic in some aroma installer or aroma file manager doesnt work too good!
and just feels the normal CWM and not Philz recovery !
But any way, Good Job!
Click to expand...
Click to collapse
Aroma File Manager has no LDPI resources. If you want it for LDPI, you can do it, it's an Artist's work. I'm not gonna do it.
Please read the first post carefully. It has no GUI options: So, no themes and all that.
It's not at all like normal CWM in terms of functions. It has got many important functions, atleast for me.
Most important part:
I've worked on this advanced only version for 20-25 days already and made it fully stable.
And...I've worked for almost 2 months on FULL VERSION. Discussed a lot with Phil3759 and finally came to conclusion that it won't work on armv6 unless it's (libtouch_gui) specially compiled for armv6, Which Phil3759 didn't have time and resources for.
So, Be happy with this recovery. No one can give you better philz recovery than this, atleast at present.

Installed your recovery.
Selected clean install ROM option.
Installed a ROM.
Selected Reboot System.
Phone rebooted into your recovery.
Tried various ROMS all rebooted into your recovery and not to the newly installed ROM.
Flashed CWM 6.0.4.6 and installed a ROM and rebooted to installed ROM successfully.
Any ideas what is wrong?
I do like the Aroma FM.
jemail

jemail said:
Installed your recovery.
Selected clean install ROM option.
Installed a ROM.
Selected Reboot System.
Phone rebooted into your recovery.
Tried various ROMS all rebooted into your recovery and not to the newly installed ROM.
Flashed CWM 6.0.4.6 and installed a ROM and rebooted to installed ROM successfully.
Any ideas what is wrong?
I do like the Aroma FM.
jemail
Click to expand...
Click to collapse
Yep...you're correct.
It won't boot into system.
I finally figured out that it is a problem in androidarmv6 sources. You can see change #6205 if you want.
It was maybe fixed just 4-5 days ago by androidmeda and I'll be again making the recovery and give you all for testing.
This is not only problem of your device but it is also there in: tass, gio and beni.

Bhargav97 said:
Aroma File Manager has no LDPI resources. If you want it for LDPI, you can do it, it's an Artist's work. I'm not gonna do it.
Please read the first post carefully. It has no GUI options: So, no themes and all that.
It's not at all like normal CWM in terms of functions. It has got many important functions, atleast for me.
Most important part:
I've worked on this advanced only version for 20-25 days already and made it fully stable.
And...I've worked for almost 2 months on FULL VERSION. Discussed a lot with Phil3759 and finally came to conclusion that it won't work on armv6 unless it's (libtouch_gui) specially compiled for armv6, Which Phil3759 didn't have time and resources for.
So, Be happy with this recovery. No one can give you better philz recovery than this, atleast at present.
Click to expand...
Click to collapse
i read that!
pay attention: the aroma that use in every CWM works fine
but in your recovery it has a bad graphic and kind of blue!
i mean before you create this Philz recovery we had a older version that works perfect!
http://forum.xda-developers.com/showthread.php?t=2483327

Rminsh said:
i read that!
pay attention: the aroma that use in every CWM works fine
but in your recovery it has a bad graphic and kind of blue!
i mean before you create this Philz recovery we had a older version that works perfect!
http://forum.xda-developers.com/showthread.php?t=2483327
Click to expand...
Click to collapse
It works perfect just in the sense: It reboots to system successfully. It lacks Aroma file manager also. And, Aroma file manager with that original green colour doesn't come with armv6 sources nor it will come if you download from original thread.
I'll be fixing reboot to system soon.
That recovery doesn't even have Touch, GUI options and all that.

UPDATE:
-Updated PhilZ sources to 6.23.9 (26.03.2014).
-CM-OTA compatibility fixes.
-Reboot to system bug fixed.
Download link updated in first post.

Bhargav97 said:
UPDATE:
-Updated PhilZ sources to 6.23.9 (26.03.2014).
-CM-OTA compatibility fixes.
-Reboot to system bug fixed.
Download link updated in first post.
Click to expand...
Click to collapse
Thanks for this.
Reboot system is working
Aroma File manager is working
I will test and report any bugs if find them.
Does this version reformat ext4 partitions as ext3 when doing a restore?
jemail

jemail said:
Thanks for this.
Reboot system is working
Aroma File manager is working
I will test and report any bugs if find them.
Does this version reformat ext4 partitions as ext3 when doing a restore?
jemail
Click to expand...
Click to collapse
It reformates the partition to the state in which it was in your backup file. The working of this PhilZ Recovery will be the same way as your CWM 6.0.4.7 works. Nothing different except features.

Tested, worked fine with aroma file manager. Flashed cm 11 has no error.
Keep your work
Here is temporary flashable zip file

As I reported previously in another Clockworkmod thread here, this version also does not restore SD-Ext Ext4 formatted partitions correctly. SD-Ext Ext4 partitions are restored as Ext3 not Ext4.
You can verify this by
1. Create an Ext4 partition on your sdcard using MiniTool Partition Wizard.
2. In CWM create a nandroid backup.
3. Immediatley restore the backup.
4. Check sdcard partition structure in MiniTool Partition Wizard, you will find the partition you created as Ext4 is now reported as Ext3.
Can you confirm this?
Can you remove all background images from your release, maybe except the ClockworkMod Logo. Background images make reading the output from operations difficult.
jemail

jemail said:
As I reported previously in another Clockworkmod thread here, this version also does not restore SD-Ext Ext4 formatted partitions correctly. SD-Ext Ext4 partitions are restored as Ext3 not Ext4.
You can verify this by
1. Create an Ext4 partition on your sdcard using MiniTool Partition Wizard.
2. In CWM create a nandroid backup.
3. Immediatley restore the backup.
4. Check sdcard partition structure in MiniTool Partition Wizard, you will find the partition you created as Ext4 is now reported as Ext3.
Can you confirm this?
Can you remove all background images from your release, maybe except the ClockworkMod Logo. Background images make reading the output from operations difficult.
jemail
Click to expand...
Click to collapse
1) I don't have your device but in my Galaxy 5 it works fine. I make backup (have an sd-ext and has some stuff also inside) and then restore it and everything is still fine. Link2sd still detects it as ext4. Even if it's a bug, it is not related to my PhilZ Recovery but to the androidarmv6 sources and I maybe can't do anything for it (don't have time to submit a patch for review...maybe I don't have that expertise too).
2) Which logo you mean? The one with Big Green Android? I would prefer to keep it that way...don't wanna make it lean more towards an unofficial build. However, I won't be able to do it (even if I want to) right now because my PC is busy and I can't compile on it right now.
Once I get my PC free, I'll make TWRP for your device and provide a final (final for some time) update for PhilZ Recovery (less probability though for PhilZ update).

When I was flashing a rom with aroma (miui v4 to be precise) its showed me get.prop errors.
Saying that my device is not beni and not 5670
And this happened only on this recovery and only with roms with aroma installer, rest of the roms work fine.
And for the TWRP version, TWRP cannot flash memory scripts (like cronmod's int2ext)
Can something be done for that?

Harpratap said:
When I was flashing a rom with aroma (miui v4 to be precise) its showed me get.prop errors.
Saying that my device is not beni and not 5670
And this happened only on this recovery and only with roms with aroma installer, rest of the roms work fine.
And for the TWRP version, TWRP cannot flash memory scripts (like cronmod's int2ext)
Can something be done for that?
Click to expand...
Click to collapse
Aroma installer's dev OR miui rom's dev is lazy to update the update-binary. KitKat requires new update-binary because Google changed the way getprop worked uptil Jellybean.
TWRP? I don't think I've made a TWRP for Galaxy Fit yet.
I wanna tell you only one thing: You are using everything from latest KK branch: PhilZ Recovery and TWRP (maybe you're talking about the one of Galaxy Mini), so please take some time to read on: What all Google changed in recovery with KitKat. Your int-ext script is suffering from old update-binary for sure.

MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusVmZUN2UxdHFtaWs/edit?usp=sharing

Awesome!
All gui and touch functions work properly.
Flashed a zip and everything works fine except reboot system and power off.
Both of them simply reboot into recovery.
Will report other bugs if found.
And nice job :good:

A little bug. Fixed it.
https://drive.google.com/file/d/0B5c3gpyMBJusSk41Q002c3lneUk/edit?usp=sharing
Give me feedback. Everything else like: screenshot double-tap shortcut for aroma fm (read first two posts to understand), GUI options, etc are especially needed for testing. Post some screenshots also.

BLU DASH 5.0 D410a Stock ROM Images + Root + TWRP

STOCK ROM IMAGES BLU DASH 5.0 D410a V27-GENERIC Android Kitkat 4.4.2 MT6572 Chipset (no UBIFS)
PLEASE READ THE INSTRUCTIONS BEFORE FLASHING YOUR PHONE SO THAT YOU WON'T BRICK IT.
EDIT: 14 January 2015. Updated the TWRP 2.8.2.0 download link. Fixed the problem where ADB and MTP was not functioning in TWRP. Added backup support for a few other partitions including the Baseband.
EDIT: 19 January 2015. Changed method of rooting and added flashable zip with modified kernel to add init.d support (that was tested and is functioning properly.)
STEP 1
BACKUP YOUR MEDIATEK DEVICE
Prerequisites
All of the software is for Windows.
Download and Extract the MTK USB Drivers and the SP Flash Tool found closest to the top of the list at:
http://mtk2000.ucoz.ru/
Press the play button to the right of the file to start the download.
Download MTK Droid Root & Tools
Latest version can be found by following the link of the following post.
http://forum.xda-developers.com/showpost.php?p=38320254&postcount=1
Hint: Click the show content button to see the link to another forum with the download link
Direct Download Link of MTK Droid Root & Tools if you are having problems getting the link.
http://depositfiles.com/files/ne1gnposp
You will need Winrar to extract the files.
That can be downloaded from: http://www.rarlab.com/download.htm
READ HERE ON HOW TO BACKUP: http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
Thanks to @rua1 for the instructions and software.
NOTE: I WOULD RECOMMEND BACKUPING UP THE USRDATA PARTITION AS WELL TO DO THAT USE HEX "0X96B40000" AS THE LENGTH DURING READ BACK IN SP FLASH TOOL
To flash the DASH 5.0 you need to use the Preloader to do it.
STEP 2
Installing the Preloader Driver (READ this section entirely before trying)
Open Device Manager
Start -> Run
Type:
Code:
devmgmt.msc
Press Enter
Turn off the phone until it is completely shut down with nothing plugged in the USB port. You will see the screen go black and shortly afterwards it will vibrate.
With Device Manager open, connect the USB cable to the phone without turning it on.
You will see the MT65XX Preloader appear (see 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"
}
Quickly double click MT65XX Preloader before it disappears, if it disappered, just unplug and plug back in the cable and try again.
Under the Driver tab, click Update Driver, click Browse my computer for driver software.
Using the Browse button find the MTKUSBAll folder you extracted and click on "New inst. win 7&8x64" and click OK
Click Next
If you get the message "Windows can't verify the publisher of this driver software", just click "Install this driver software anyway"
Click Close
Click Close
After the driver is installed you can unplug the phone.
STEP 3
Uploading the image files to the phone{/B}
WARNING: The BLU-DASH-5.0_141022_BLU-D410a-V27-GENERIC_FOR_SP_FLASH_TOOL.zip file has all of the necessary images but do not flash them unless you trying to recover from a brick.
DO NOT FLASH THE PRELOADER.BIN AS IT MAY BRICK YOUR PHONE.
THE ONLY FILES I HAVE PERSONALLY TESTED ARE boot.img, factory_NONmodified_recovery.img and system.img
Download BLU-DASH-5.0_141022_BLU-D410a-V27-GENERIC_FOR_SP_FLASH_TOOL.zip from here:
http://d-h.st/3L9G
See Step 5
Extract the SP Flash Tool.
Extract the system.img and MT6572_Android_scatter.txt (and/or boot.img and factory_NONmodified_recovery.img, if you wish)
Open the SP Flash Tool
Click the Download tab
Click the Scatter-loading button and select the MT6572_Android_scatter.txt file.
Click the location of ONLY the parition(s) you are going to flash: ANDROID = SYTEM partition (system.img), BOOTIMG = KERNEL (boot.img) and RECOVERY=RECOVERY (factory_NONmodified_recovery.img or custom recovery file)
Select the image file (e.g. system.img or system_rooted.img)
MAKE SURE ALL OTHERS ARE NOT TICKED
Click the Download button.
Plug in the phone or unplug and plug it back in to start flashing the images to the phone.
Note: This can also be done with the battery removed.
Your phone will have root.
STEP 4 - Adding TWRP
First we need to rename the file recovery-from-boot.p found in the /system folder.
Using a File Manager with root permissions rename
Code:
recovery-from-boot.p
to
Code:
recovery-from-boot.bak
OR
From an adb shell, rename the file
Code:
su
cd /system
mv recovery-from-boot.p recovery-from-boot.bak
Now turn off the phone and with SP Flash Tool flash TWRP 2.8.2.0. Download link below.
NOTE: Select only the RECOVERY partition to flash. TWRP themes are supported as well as the Aroma File Manager.
http://d-h.st/aQmt
STEP 5 - Rooting and adding init.d support
Go to http://download.chainfire.eu/supersu
Download the latest SuperSU.
Go to http://d-h.st/AJQ
Download the init.d support zip file.
Boot to TWRP while connected to a PC with adb tools run the command
Code:
adb reboot recovery[/url]
OR
Hold down the power select Reboot and hold down the volume up button until you see the TWRP logo.
Via the install menu, flash the SuperSU zip and inti.d support zip.
ALL DONE!
THANKS:
[user=631273]@Chainfire[/user] for SuperSU
[user=5119815]@rua1[/user] for MTK Droid Root & Tools and instructions on how to use SP Tools
[user=4478781]@yuweng[/user] for creating the tool to make TWRP for MediaTek devices
[user=912474]@Dees_Troy[/user] for TWRP

I will give a brief explanatoin and will elaborate more when I have the time.
For Root:
Thanks to @Chainfire
I basically mounted the system.img in a Linux OS and copied the files from the SuperSU v2.36 zip file and placed them in their relevant directories added the relevant permissions, etc.
For init.d scripts
Thanks to @alireza7991
See his thread: http://forum.xda-developers.com/showthread.php?t=2287540
I modified the kernel to boot and created a flashable zip that adds busybox to /system/xbin and creates the necessary folders then flashes the modified kernel.
For TWRP:
Thanks to @yuweng
I used Easy Magic TWRP Installer for MTK. See http://forum.xda-developers.com/showthread.php?p=53752834#post53752834
It worked but changed my partition information for some reason even though the size fit my paritition size. I wiped my phone and lost my baseband and recovered it. Posted a new thread on how to do that. See http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
That is why I posted the image file so no one has to face that problem too. I tested it and it is functioning without any problems.
You can follow yuweng's thread to make it smaller if your partition size is smaller than 6MB for some phones, at a cost of course.

Anyone looking for baseband files can check http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
For anyone wanting to use Link2SD on this, I have created a flashable zip to use with a custom recoveery that adds init.d support, installs Link2SD as a system app and adds a modified mount script that functions properly.
Requires root and a SD card with the second partition formatted as EXT4.
Download -> http://d-h.st/Dcgh

After flash this rom only get Blu screen, wipe and cache reset and the same, trun to V14 again and power on ok, this v 27 in the 2 variants, stock and rroted not start.

jorgefar said:
After flash this rom only get Blu screen, wipe and cache reset and the same, trun to V14 again and power on ok, this v 27 in the 2 variants, stock and rroted not start.
Click to expand...
Click to collapse
What procedure did you use to flash it?

SP_Flash_Tool_exe_windows_v5.1420.00
Scatter File from V27
selected only:
Recovery: non modified...
Boot: boot.img
Android : System.img or System Rooted
Flashed OK
Only Blu screen and restar...
Im currently on V14 Ok

jorgefar said:
SP_Flash_Tool_exe_windows_v5.1420.00
Scatter File from V27
selected only:
Recovery: non modified...
Boot: boot.img
Android : System.img or System Rooted
Flashed OK
Only Blu screen and restar...
Im currently on V14 Ok
Click to expand...
Click to collapse
Your phone is a BLU Dash 5.0 D410a and NOT the 5.0+ or 5.0 Studio right?
It sounds like your kernel (boot.img) is not booting the /system partition. Try flashing the /system and recovery partitions only for now and see what happens. Do not flash the boot.img

Thanks for you le answer! Thats right, is a Blu Dash 5.0 D410a, I try on Monday the suggested and post results!!!

Hi again, flashed system and recovery only, stuck on Blu screen again, try wipe and reset cache, stuck on screen Blu,any recomendation??

Added a flashable zip to add init.d and install LInk2SD with a modified mount script to run properly on this phone, BLU DASH 5.0 D420a running V27 Android 4.4.2.
See post #3

dechronic said:
Your phone is a BLU Dash 5.0 D410a and NOT the 5.0+ or 5.0 Studio right?
It sounds like your kernel (boot.img) is not booting the /system partition. Try flashing the /system and recovery partitions only for now and see what happens. Do not flash the boot.img
Click to expand...
Click to collapse
I'm having the same problem as Jorgefar. Mine is on v24 instead of v14 though after the factory update to 4.4.2. I rooted it with kingroot, but I would like to have twrp recovery. I've done everything you instructed him, but mine gets stuck in the bootloop as well. I thought i could just flash the recovery, and did the rename on the recovery file, but that didn't work still had factory recovery. After that I did the entire procedure and got the bootloop.

Sexyr said:
I'm having the same problem as Jorgefar. Mine is on v24 instead of v14 though after the factory update to 4.4.2. I rooted it with kingroot, but I would like to have twrp recovery. I've done everything you instructed him, but mine gets stuck in the bootloop as well. I thought i could just flash the recovery, and did the rename on the recovery file, but that didn't work still had factory recovery. After that I did the entire procedure and got the bootloop.
Click to expand...
Click to collapse
After installing TWRP you need boot into TWRP before booting into Android and install the latest SuperSU. The install-recovery.sh will replace TWRP with the stock recovery on the first boot if SuperSU is not installed, which renames it.
After flashing TWRP with the Smart Phone Flash Tool, disconnect the cable, press the power button and then hold the volume up button to enter TWRP.

dechronic said:
After installing TWRP you need boot into TWRP before booting into Android and install the latest SuperSU. The install-recovery.sh will replace TWRP with the stock recovery on the first boot if SuperSU is not installed, which renames it.
After flashing TWRP with the Smart Phone Flash Tool, disconnect the cable, press the power button and then hold the volume up button to enter TWRP.
Click to expand...
Click to collapse
Cool got it and am on v27 now. thanks..... now if ony there were other roms for it ah well, at least i'm rooted again with recovery.

can i flash this on BLU Dash 5.0 D400a

dechronic said:
Anyone looking for baseband files can check http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
For anyone wanting to use Link2SD on this, I have created a flashable zip to use with a custom recoveery that adds init.d support, installs Link2SD as a system app and adds a modified mount script that functions properly.
Requires root and a SD card with the second partition formatted as EXT4.
Download -> http://d-h.st/Dcgh
Click to expand...
Click to collapse
This say file no longer available..could it be downloaded elsewhere?

Does this work on 5.0+?

Stiffymeister said:
Does this work on 5.0+?
Click to expand...
Click to collapse
Don't think so but I think I have a 5.0+ image. Anything in particular you looking for? I should be able to provide it tomorrow

i have tried everything as you said but after using the flash too and b4 installing recovery it says my phone is not rooted so it wont let me rename the recovery file. should i have a rooted system image in the scatter file cause i dont see one in the files i extracted. p.s. i downloaded all the files you linked so if im missing something can someone please point me in the right direction. thanks
blu dash 5.0 d410a v27

dlongnasty said:
i have tried everything as you said but after using the flash too and b4 installing recovery it says my phone is not rooted so it wont let me rename the recovery file. should i have a rooted system image in the scatter file cause i dont see one in the files i extracted. p.s. i downloaded all the files you linked so if im missing something can someone please point me in the right direction. thanks
blu dash 5.0 d410a v27
Click to expand...
Click to collapse
I probably need to redo the steps for a couple of the posts.
Download the TWRP at http://d-h.st/aQmt
Upload it to the phone. Make sure that only recovery is ticked in the Smart Phone Flash Tool (SP Flash Tool) and select the file you downloaded. You should be able to figure out the rest based on my instructions.
Flash SuperSU which can be downloaded from http://download.chainfire.eu/supersu
It will rename the file that would put back the original recovery.
That should be it.

got it working thanks. are their any custom roms for the d410a?

[SCRIPT][DUAL-BOOT][I9305] db

(Sorry for english !!)
!! Some problems with Android 5.1.x installed on External.
[Dual-Boot] I9305 [SCRIPT]
Hi. Because i dont find any kernel/script for I9305 with Dual-Boot, i try to make this script for test roms (but can be use day by day without problem).
This script help to patch .zip rom/kernel/gapps (and other i think) for install him on SDCARD. (without touch your internal rom).
How can you do this? Need to repartition your sdcard in 3 parts
1. With your sdcard data (files/music..etc)
2. external System (for system rom)
3. external Data (for data rom)
What you need to know !!!!
- Thanks on @Nicene Nerd for this App. I'm inspired from him.
- I'm not a developer.
- I don't now so much about linux (so, script not have a best optimization)
- This script is better good for people who test roms (like Lollipop).
- If you dont try this script, don't say anything. (only if you have some problem/stucks)
- Install on Internal roms like: Amcha / N4 / ..etc (big roms)..because i try to install on external rom and dosen't work
- Rom like Nameless / RR / ..etc can be install on external
- Anyone who want help me to make this script better, say here where need to edit (with what) and who can code help
- Say here what rom/kernel/script work or dosen't work to install on external. For modify script
What you need.
MiniTool Partition Wizard (or other program to repartition sdcard)
USB Cable (for repartition)
A phone (i9305 of course)
SDCARD 16gb (or more) Class 10 (if you have class 4 or other..your external rom run slow)
Backup your sdcard data (for safe)
Backup your phone (for safe)
ROM with root permision.
Water (because is good for your health)
First time you need to repartition sdcard
First partition: FAT32 (split memory from this..is good option)
Second: 1600 mb (1,6 gb) for system
Third: 2500 mb (2,5 gb) minimum memory for data
How can do this:
On MiniTool show your sdcard (like this)
{
"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"
}
1. Right click on him > Split
2. On New Partition Size you need to have minimum (system + data) 1600 + 2500 = 3600 mb (3,6 gb)..If you want more memory on data, you can type more than 3600 mb (i need more so i split 7000 mb)
After write your value, press ok
Now look like this
3. Right click on new partition (H on me) > Delete
Now you have unallocated partition
4. Right click on unallocated partiton > Create > Ok (on warning)
5. On box you need to edit:
Create As: Primary
File System: Ext4
Partition Size: 1600 (because is system partition)
After this. Press Ok
6. Right click on unallocated partition > Create > Ok (on warning)
Create As: Primary
File System: Ext4
Partition Size: dont modify
After this. Press Ok
7. Before press Apply, check if look like this
Now you can press Apply and wait
Good
After sdcard was partitioned, go to next step
Put my script on your SDCARD
(Why in sdcard? because internal/external rom view the sdcard everytime)
(internal/external rom have separated 'internal memory')
1. Unrar on desktop (right click on archive > extract here)
2. Copy 'db' folder to your sdcard
3. Check if 'db' folder is on your sdcard
4. With file explorer (i use Root Browser), go to db folder and install 'terminal.apk'
5. After install run him
On terminal:
Type: su (for superuser permision)
Type: cd /mnt/extSdCard/db (or anywhere is db folder location..on LolliPop is: cd extSdCard/db)
Type: sh db.sh
Now you are in script menu
Option: 1 -> Save Internal BOOT.IMG
Option: 2 -> Flash Internal BOOT.IMG and Reboot phone (if not reboot, try to reboot manualy)
Option: 3 -> Mount Internal partitions on root direcotry (/.dbSystem & /.dbData)
Option: 4 -> Clean Internal partitions (use this if you are in External rom)
Option: 5 -> Save External BOOT.IMG
Option: 6 -> Flash External BOOT.IMG and Reboot phone (if not reboot, try to reboot manualy)
Option: 7 -> Mount External partitions on root direcotry (/.dbSystem & /.dbData)
Option: 8 -> Clean External partitions (use this if you are in Internal rom)
Option: 9 -> Patch file for External rom (file like rom/gapps/pa-gapps/kernel..etc)
Option: 0 -> uMount /.dbSystem & /.dbData
Option: fb -> Flash manualy BOOT.IMG file
Option: ie/ei (hidden command) -> I'm work on this.. Is a experimental function. Don't use it
Patch files for external rom:
1. Copy on 'db' folder rom who want to patch, gapps archive and kernel your need
2. Run script on terminal
3. Need to save your Internal boot.img (Option 1 on menu)
4. Option 8 to clean your external partitions (if was used before with other rom).
5. Option 9 to patch
6. Type rom/gapps/kernel..etc archive name like: my_rom.zip > And press enter
7. Wait to patch (all patched files have pre name ext-
NOTE: If you patch rom/kernel (with boot files), you need to watch if script modify any fstab file. If no, external rom not work!
8. After you patch all you archive need..go to recovery (i use TWRP 2.8.5.0) and flash him but need to kep order:
- First ROM zip
- Second GAPPS (or PA-GAPPS) (or without this)
- Third KERNEL (if is need)
- .. other patched scripts
9. After flashing, reboot and wait to new external rom start up
(if you have any error (boot loop/other) you can flash internal boot stored in "sdcard/db/.db/.imgs/boot-int.zip")
10. After your external rom is ON, install 'terminal.apk' from sdcard
11. Run script on terminal
12. Save your External BOOT.IMG (Option 5)
13. Enjoy with your external rom.
(To switch rom you have option 2 and 6 or flash manualy .zip stored in "sdcard/db/.db/.imgs/boot-*.zip")
I forgot something?
Another explain: http://forum.xda-developers.com/showpost.php?p=59570171&postcount=11
Changelog
Version 1.3:
+ Removed experimental (duplicate partitions)
+ Removed rsync
+ Add check "Where i am now" for check what system mounted (internal/external) for optimized script
+ On start, check if rom/kernel changed and you can save new rom much easy
+ Disabled some options from menu (depend where are you (internal/external) rom)
+ On mount/ckeab internal/external partitions, now check if is mounted property
+ Terminal updated at last version
Version 1.2:
+ Some bug fixes (major bug fixes)
+ Add rsync for Duplicate Partition (ie/ei command. hidden command because not work now
+ Patch init. files from kernel (work with pureSTOCK / pureCM kernel) (i'm not tested, but you can flash now a big rom (like Amcha/N4 Lite) in external rom)
Version 1.1:
+ Some bug fixes
+ Mkdir folder check after create
Version 1.0:
+ It's alive !

thanks fro this script, but i have a question:
if I understand how it works, every time I have to save the rom I'm using...it creates a backup of rom in flashable zip format.
to switch from one to another rom I have to flash the zip saved...so what is the difference with a nand backup/restore?
and what are the performance and the lag of a rom thst run on sd card?

LeoDeos said:
thanks fro this script, but i have a question:
if I understand how it works, every time I have to save the rom I'm using...it creates a backup of rom in flashable zip format.
to switch from one to another rom I have to flash the zip saved...so what is the difference with a nand backup/restore?
and what are the performance and the lag of a rom thst run on sd card?
Click to expand...
Click to collapse
Script was patched a .zip file for install on External partitions (system/data).
And modify boot.img (mounts).
Difference on nand backup/restore and this is time and to swich internal to external is much faster. (only flash boot.img for swich)
I make a Benchmark and score is 30k with Nameless (0303 version).. When you copy some file in sdcard (with usb) or you install a apk file (depend so much what sdcard you have).. have some lags..but if i use day by day i dont have lag.
I dont now if i explain so good how script works because i dont now so much english..
Look at uploaded image. How much time need to change rom from ..3 minutes..all i need is to flash boot.img (for internal/external) and reboot..
This is a good option in my opinion

il3gal said:
Script was patched a .zip file for install on External partitions (system/data).
And modify boot.img (mounts).
Difference on nand backup/restore and this is time and to swich internal to external is much faster. (only flash boot.img for swich)
I make a Benchmark and score is 30k with Nameless (0303 version).. When you copy some file in sdcard (with usb) or you install a apk file (depend so much what sdcard you have).. have some lags..but if i use day by day i dont have lag.
I dont now if i explain so good how script works because i dont now so much english..
Look at uploaded image. How much time need to change rom from ..3 minutes..all i need is to flash boot.img (for internal/external) and reboot..
This is a good option in my opinion
Click to expand...
Click to collapse
ok understand...
but i'm not still sure of utility of the external boot.
foe example: i can flash stock rom on internal and save boot.img...
after i flash aosp rom always on internal and save boot.img with another name.
in this case the time to switch one to another rom is the same 3 minutes.
i wrong?

LeoDeos said:
ok understand...
but i'm not still sure of utility of the external boot.
foe example: i can flash stock rom on internal and save boot.img...
after i flash aosp rom always on internal and save boot.img with another name.
in this case the time to switch one to another rom is the same 3 minutes.
i wrong?
Click to expand...
Click to collapse
hmm..but system files and data files where is? same in internal? You cant..
You need other partitions for system / data if you want another rom
For internal partition mount points is mmcblk0p13 (system) and mmcblk0p16 (data)
For external is mmcblk1p2 (system) and mmcblk1p3 (data)
Hm..understand?

il3gal said:
hmm..but system files and data files where is? same in internal? You cant..
You need other partitions for system / data if you want another rom
For internal partition mount points is mmcblk0p13 (system) and mmcblk0p16 (data)
For external is mmcblk1p2 (system) and mmcblk1p3 (data)
Hm..understand?
Click to expand...
Click to collapse
maybe i explain wrong.
so i try to repeat well.
1) flash stock rom on internal.
2) backup stock rom (option 1 of your script)
3) full wipe and flash aosp rom always on internal.
4) backup aosp rom (always with option 1 of your script)
(if i'm not wrong we will have 2 backup zip file)
5) switch rom (option 2 of your script)
its possible?

LeoDeos said:
maybe i explain wrong.
so i try to repeat well.
1) flash stock rom on internal.
2) backup stock rom (option 1 of your script)
3) full wipe and flash aosp rom always on internal.
4) backup aosp rom (always with option 1 of your script)
(if i'm not wrong we will have 2 backup zip file)
5) switch rom (option 2 of your script)
its possible?
Click to expand...
Click to collapse
aaaaaa...no..

il3gal said:
aaaaaa...no..
Click to expand...
Click to collapse
ok thanks

LeoDeos said:
ok thanks
Click to expand...
Click to collapse
I make now how i use this script ..with images..

Not meaning to rain on the parade here but it basically seems to be similar to just backing up and restoring like nand. It may not be exactly the same but it seems to be a similar thing.
Unfortunately it looks like it can't perform a proper dual boot.

Explain 2
I made a tutorial how i use this script. Skip the repartition step because is easy (repartition need to make one time..not everytime want you install external rom)
On my rom (N4 Elite Lite v5).
1. Copy what files need to patch in db directory (where is script). In my case (pa_gapps-modular-pico-5.0.1-20150221-signed.zip & nameless-5.0.2-20150318-i9305.zip)
2. Run script.
3. First time need to save your internal boot.img (kernel). (for swich roms)
(because script modify kernel (mount point on kernel) and when you swich rom, all who make script is to flash kernel for internal/external rom)
4. After you save internal kernel, go back to menu and type option 9 to patch zip rom/gapps/kernel..etc
(if rom have a included kernel, watch if script find a fstab.* file and if can be edited. If not edited, external rom not work)
(all rom/kernel/gapps..other script need to modify updater-script or update-binary (pa-gapps use this)..if not edited, you cannot install rom on external partitions
5. After i patch rom file, i need and gapps because i use Google Play Store, so, i patch and gapps (go in menu, option 9 and type gapps file name)
(Now my db directory look like this)
6. All good. Now i want to be sure about my external partitions is clean, and i go to option 8 to clean him
7. After clean, reboot in recovery and flash ROM (ext-nameless-5.0.2-20150318-i9305.zip) and after GAPPS (ext-pa_gapps-modular-pico-5.0.1-20150221-signed.zip)
8. Reboot phone and wait to rom boot complete..(first boot may during a time)
(At Total Memory, is total memory allocated on 'data' partition (from repartition) (third partition))
9. After boot is complete..install 'terminal.apk' from db folder (script folder)
10. Run script from terminal.
11. Option 5 (for save this external boot.img)
12. Voila..now i have 2 separated roms..installed in 2 separate partitions (internal system/data and external system/data)
To swich i have 2 option. From terminal (script). (example) If i'm in internal rom and i want to swich, open script an type option 6..For flash external kernel and reboot phone to boot in external rom.
From recovery: flash manualy .zip files stored in sdcard/db/.db/.imgs/boot-*.zip
Now is good explication?
djb77 said:
Not meaning to rain on the parade here but it basically seems to be similar to just backing up and restoring like nand. It may not be exactly the same but it seems to be a similar thing.
Unfortunately it looks like it can't perform a proper dual boot.
Click to expand...
Click to collapse
Is not same. Do you know dual windows on pc?
Partiton C have Windows 7 (example)
and partition D have Windows 8.1 (for example)
If you boot pc, have a question "Who windows want to boot" 7 or 8.1..and you choose.
My script is same, but for 'choose', need to flash a kernel (external/internal..depend what you want to boot)
hmm.
This script is same with http://forum.xda-developers.com/showthread.php?t=2639112 ...but is not app..and dont have some options like "backup"..

Tested with:
ROM
- AICP 8.0
- Resurrection Remix® LP
- NamelessROM
- Cyanogenmod 12
- SlimLP
KERNEL
- Boeffla 3.0-alpha9
Changelog
Version 1.1:
+ Some bug fixes
+ Mkdir folder check after create
I see some people was download script. Can give me feedback? (db_1.0.rar - [Click for QR Code] (1.11 MB, 32 views))
What rom is work and what not? (i dont have time to test all roms)

Abandoned.

il3gal said:
Abandoned.
Click to expand...
Click to collapse
why?

LeoDeos said:
why?
Click to expand...
Click to collapse
Because i dont have feedback..
I continue use this but i dont post update..
32 downloads / 0 feedback..
I think people don't understand how it works ..hm
I'm bad to explain this

il3gal said:
Because i dont have feedback..
I continue use this but i dont post update..
32 downloads / 0 feedback..
I think people don't understand how it works ..hm
I'm bad to explain this
Click to expand...
Click to collapse
i think you should leave the download link.
it could help for someone.
when i'll time and an sd card bigger i want try your method

LeoDeos said:
i think you should leave the download link.
it could help for someone.
when i'll time and an sd card bigger i want try your method
Click to expand...
Click to collapse
ok. i remove and [abandoned] .
just wait. now i try to add some things on script.

il3gal said:
ok. i remove and [abandoned] .
just wait. now i try to add some things on script.
Click to expand...
Click to collapse
thanks

+Tested with:
ROM
- AICP 9.0 (test version)
Changelog
Version 1.2:
+ Some bug fixes (major bug fixes)
+ Add rsync for Duplicate Partition (ie/ei command. hidden command because not work now
+ Patch init. files from kernel (work with pureSTOCK / pureCM kernel) (i'm not tested, but you can flash now a big rom (like Amcha/N4 Lite) in external rom)

+Tested with:
ROM
- N4 Elite Lite v7 (but i don't now how much fast is) (when i have time, i will tested)
Changelog
Version 1.3:
+ Removed experimental (duplicate partitions)
+ Removed rsync
+ Add check "Where i am now" for check what system mounted (internal/external) for optimized script
+ On start, check if rom/kernel changed and you can save new rom much easy
+ Disabled some options from menu (depend where are you (internal/external) rom)
+ On mount/ckeab internal/external partitions, now check if is mounted property
+ Terminal updated at last version
Who know a universal reboot command for any rom? Because reboot not work on N4 Elite Lite rom

OTA update bootloop fix [S-ON] [BU] [Stock Rooted ROM]

Hi, I found a way to fix this bootloop which happens after you flash the latest ota update if you have unlocked and rooted your stock rom.
I own a HTC E8 China Unicom [M8Sw - dual sim], but I think it will work on other variants.
It is the SU binary/files which are preventing the phone from updating correctly.
You can also restore a clean unrooted TWRP backup and do the OTA update.. it will work just fine.
This tutorial is for those who don't want to lose their app data and modifications.
To be able to update... you need to fully unroot the phone before. Well, this was previously not possible due to system write protection.
(There are also other methods of unrooting. (deleting the SU files manually with the file manager of TWRP recovery) This doesn't work, I have tried it myself..often cause bootloops.)
But now we have a custom recovery mod which enables us to write to the system partition and thus can fully unroot with SuperSU app itself.
Requirements:
-some expertise with adb/flashing/twrp recovery management will be needed.
-stock firmware.zip, inside the OTA zip file, where you will find you stock recovery,boot image, etc
-Stock ROM, rooted with no modified existing system files
-TWRP Recovery from @Captain_Throwback works fine. I used the 2.8.6.0 one. http://forum.xda-developers.com/one-e8/orig-development/recovery-twrp-touch-recovery-t3060188
-untouched Stock Kernel Modules (IMPORTANT)
-SchKernel Extra 3.3, to gain write permission to /system http://forum.xda-developers.com/one-e8/general/schkernel-extra-3-3-t3200090
[UPDATE: SchKernel Extra has been updated to 3.5 and the old one is not available for download on the other thread. You can find attached at the bottom of this section ver3.3 which I had used. Please don't use ver3.5 as a user has reported having bootloop with that.)
-Battery +80 charge recommended...the process gonna demand a lot of power.
-Patience... loads of it....
Disclaimer: I am not responsible if you brick or damage you phone!!
Before you flash anything, be sure to have a working twrp full backup of you phone! In case anything goes wrong.
STEPS:
1. Copy the untouched kernel 'modules' folder [found in system/lib/ in your phone] to another location ( for e.g. to your internal phone memory), you're gonna need it later.
2. Flash the twrp recovery if you haven't already and boot into TWRP recovery.
3. flash SchKernel Extra 3.3 kernel mod. It will launch the aroma installer. There will be options as overclocking/underclocking etc..
I left everything on STOCK option, disabled Swipe2sleep, unselected the everything in the optional addition page. Then went to install it.
4. Reboot, and open SuperSU app, go into setting, tap the FULL UNROOT option, this might take a while. The first time, when the unrooting notice shows and it seems that the app is not doing anything, you might be required to exit the app by pressing home button. Then open the app again and redo FULL UNROOT option. If you exit the app and when re-opening it, the "unrooting notice" is still there, then it means it is working. This might take a bit of trial and error.
5. Ultimately, SuperSU app will close. Then you will need to reboot. You will see that SuperSU is gone and that you have no root access.
6. Now, turn it off again to go to fastboot. Connect to PC and flash the stock boot.img via adb to restore the stock kernel.
8. Then, in twrp recovery, mount /system partition and got to advanced >> file manager..
9. Now browse to /system/lib/ and delete the 'modules folder'.
This is because the SchKernel Extra 3.3 kernel mod flashed previously has modified your kernel modules and when you will try to update the OTA, the stock recovery will report that the kernel modules (xxxxx.ko) has be modified and it will stop the OTA update process.
10. Remember the previous untouched stock 'modules' folder you copied previously, now move it to /system/lib/HERE , to replace the deleted folder.
[DO STEP 9 BEFORE - Don't try to overwrite the folder, it won't be possible. It said operation failed for me. ]
Optional: You might also want to delete su.d folder in \system and init.d folder in system\etc
these files were for the custom kernel and won't be needed anymore.
11. Reboot into fastboot mode, connect to PC (if not already), flash stock recovery.
12. Now, you're good to flash the OTA updates. :good:
-Download it, if not already done.
If ever you have downloaded from PC and copied it to phone, and for whatever reason the phone is not detecting the zip file and asking for install.
Just move it to you exeternal SD card and rename it to "ptt.zip" , go into stock recovery and go down the list to "apply update from SD card"
and it should flash the zip file. When done, select the reboot option and it will say reboot to flash firmware.zip and the will boot. :fingers-crossed:
When booting it will take some time (3 to 8 mins), and then go to the "Android is updating - optimizing apps" screen. This might take a lot of time if you have a lot of apps installed. The phone might get really hot during this process.
When the OS finally boot completely there will be an "HTC" screen and an exclamatin mark in the notification bar. NO WORRIES, it is the just the update working. It will go away when the update is fully processed.
After OTA update is done, you can make a twrp backup of the unrooted system, so that you can restore it for future OTA updates.
If some steps are confusing, feel free to ask for any clarification
Hope I helped you. Don't forget to hit thanks

problem
hi after i flashed SchKernel Extra 3.3 my phone just turned off and won't turn on. what should i do?

neekless said:
hi after i flashed SchKernel Extra 3.3 my phone just turned off and won't turn on. what should i do?
Click to expand...
Click to collapse
how did you flash it exactly?
Did you flash it thought TWRP recovery?
also...what variant of HTC e8 are you using?

Thank you for this guide. :good:
For the newbies, here are exact instructions for each step. TWRP is required; presumably you have this because you've rooted your phone. (If you haven't rooted your phone, what are you doing here?)
Note that rebooting to TWRP can be accomplished in several ways:
Long-press the power button; when prompted choose Reboot. When the screen goes black, press and hold the Volume Down key. This will take you to hboot; from there choose Recovery.
Enable developer mode from settings, plug in to a computer, and issue the command adb reboot recovery.
Also note that it is prudent to do a full TWRP backup to external storage (microSD, USB OTG) before anything else, so you have a good recovery point if things go wrong.
To copy the system/lib/modules directory, you can use a root-enabled file explorer or TWRP. To do it in TWRP:
Reboot to TWRP.
In TWRP, select Mount. Make sure that system is checked.
Back to the main TWRP menu, select Advanced.
In the advanced menu, select File Manager. Then navigate to /system/lib/modules.
Tap on Select, then Copy Folder. Navigate to a new location - I used /sdcard/Backup - and tap Select again. Don't use your external SD or USB-OTG, they may not preserve permissions correctly.
To flash the SchKernel Extra, copy the ZIP file to your device, reboot into TWRP, and select Install. From there, navigate to where you copied the ZIP file and select it; then follow the prompts as sanijsnj specified.
Removing SuperSU works exactly as described. Don't forget to reboot at the end (although it may not be necessary).
To flash the stock boot, in a cmd window where you have the Android SDK, typically in the sub-folder platform-tools enter: fastboot flash boot boot.img (boot.img from the OTA ZIP).
To delete and restore /system/lib/modules, follow the steps above, starting of course from your saved 'modules' directory and copying to /system/lib.
To flash the stock recovery, again in the cmd window enter: fastboot flash recovery recovery.img (recovery.img from the OTA ZIP).