Related
▐▄▀▄▀▌ TUTORIAL CWM roms are the way to go right now!!!
THIS IS A TUTORIAL TO GET CWM ROMS UP AND RUNNING ON UR RHODIUM
SO i felt completely compelled to share my amazing experience and results with my CWM rom!!!!
i almost always try to keep the development process here away from other sites
if you want a REALLY GOOD WORKING version of android on your device without trying NAND ... follow my instructions...
first off i have a ATT Tilt 2 i have been using with this..
to find anything you need to know on android for our phones go HERE
(Neopeek site)
any size card should do for runing CWM builds,,, i however am runnig an 8gb class 4 sdhc and all is well
MY recommended partition sizes... (i set 300mb as all my EXT2 partitions just to make calculating it easier...)
(primary) FAT32 - storage for music videos pics etc... rest of space
(primary) EXT2 - 200-300mb (system) holds rom build... none are over 250mb
(primary) EXT2 - 200-300mb (data) data for android... i believe is the space for app install... so bigger is better..
(primary) EXT2 - 50-100mb (cache) like ram sorta...
with these sizes... worryin about the size of the rom will not matter ..
look on the site link i posted above on how to install and use CWM if you havent before... (dont worry newbs... its easier then everyone makes it seem...)
with CWM builds the standard Gapps are not included...
THIS SITE is the repository to go to... i am using "gapps-hdpi-20101114-signed.zip" but feel free to try others to see if they load...
this is the the most frustrating part of CWM, finding GAPPS that install...
u install them the same way you do a rom... by installing the zip from the sd card...
i do recommend installing gapps zip after you have already installed the rom and booted and restarted android a couple of times
otherwise i recommend THIS ROM as it is the one i use... i know it is only Froyo but it has a themed gingerbread taskbar with black pull down so it still looks nice!!!
lastly
((((technically test kernel.. so not recommended!!... but proven to fix screen not coming on problem...))))
for you crazy tester ppl waiting for the day you brick your phone(im totally kidding dont worry newbs) i use the WIS-Tilt2 kernel the newer test one to be specific...
GO HERE
With this kernel my device goes in to deep sleep with the GReen light and wakes up perfect every time!!!!!
the zip is just modules package and a zImage.. just have to replace and boot...
WARNING... when i updated with the working kernel it looked like it wasnt going to work.. didnt seem to be anywhere enough scrolling text and the boot animation barely played and then the screen went black... i played around with the buttons and found the device to be opperating with out the screen on i kept pressing buttons and the screen finally woke up!!!! be patient!!!! after that it worked perfectly everytime...
other tips... for people experiencing wifi unable to scan problem ..
use the Wifi-nvram.txt trick look it up in xda... once command is entered no need to reboot just turn on wifi and connect!!!
i hope that this has been helpful i couldnt find any where that had all the tips and tutorial in one place to get CWM up and running at least once... had to do it trial and error.. hope my hard work will help you newbs out!!! hahaha
---
Here is the CMW version of the normal FRX06 by arrrghhh. Credits to arrrghhh for the build and to preston74 for making it ready for CMW.
G-apps are already included in this build so you don't have to flash them separate.
http://www.multiupload.com/2VS5ZKUFBA
jellenl said:
Here is the CMW version of the normal FRX06 by arrrghhh. All credits goes to him, I only made it ready for clockwork mod. Gapps are already included so you don't have to flash them seperate with this build.
http://www.multiupload.com/TQSN4TG28U
Click to expand...
Click to collapse
thanks guy...
\
i want to make it as easy on peopl eto get a stable working version of android on their TP2's
Well, i used CWM with an 1GB SD and worked like a charm...
and first time i did it with a 2gb... i just said more cause there is more room for apps... lol
should prolly clarify that...
Trekfan422991 said:
thanks guy...
\
i want to make it as easy on peopl eto get a stable working version of android on their TP2's
Click to expand...
Click to collapse
Yes you are doing a good job
I first made a cmw version of frx06 without gapps, but argghhh told me it was ok if I include the gapps, so I did
You may also integrate my link in your first post, then I'll delete my post.
Forgive me here... I am new to the CWM builds. If I have a CWM build on an SD card, with the appropriate ex2 partitions and all, can I use CWM to put on a different build? That would be a whole lot easier than having to reformat and start over...
Well if you run in to any problems the support here is going to be limited.
On the other hand if you use XDAndroid the support here is maximal.
For testing and dev reasons, I will stay with my current build. I quite like my bluetooth.
For any beginners I would very much recommend that you use 'standard' (see intro to android sticky). Well, at least until you are confident you don't need to be hand-guided through this and know what to do if something goes wrong.
ppcfly said:
Forgive me here... I am new to the CWM builds. If I have a CWM build on an SD card, with the appropriate ex2 partitions and all, can I use CWM to put on a different build? That would be a whole lot easier than having to reformat and start over...
Click to expand...
Click to collapse
It actually is pretty easy - you can backup your current system & data partitions, and throw a new build on - if you don't like it, wipe and revert to the backup.
The only problem is if you have CWM installed, other 'normal' (looped mount) builds will not work - the rootfs will see the partitions and think you want to run from partitions - of course, this results in a failure to boot... I like having many builds on my card at one time so I can flip between them - this also makes testing a heckuva lot easier, so heads up folks!
Nice tutorial and thanks for putting my build in it,but you should put proper credits as Neopeek(and his team) made cwm and i made the build you linked(you can avoid doing this)
And it's gingerbread like themed and the theme name is minimal green..
You can avoid doing 300 mb system as almost all the builds are less than 100 mb,so doing it 150mb is good
CWM and loopmounted builds can co-exist.
arrrghhh said:
The only problem is if you have CWM installed, other 'normal' (looped mount) builds will not work - the rootfs will see the partitions and think you want to run from partitions
Click to expand...
Click to collapse
To avoid this you can just add the "no_partitions" (without the quotes) switch to your cmdline on your startup.txt of the loopmounted build and you should be good to go.
It may depend on your rootfs, but I'm using F22's rootfs and it works like a charm.
i'm trying cwm with frx6 and it keep saying fail rootfs., what am i doing wrong?
Do you followed the tutorial on how to set up your sd-card for cmw? I think you are using a wrong rootfs. As far as I know you need the rootsf from neopeek's cmw.
jellenl said:
Do you followed the tutorial on how to set up your sd-card for cmw? I think you are using a wrong rootfs. As far as I know you need the rootsf from neopeek's cmw.
Click to expand...
Click to collapse
i"ve gotten into CWM but now its telling cand find the zip find even after scroll down to the update. do need to just rename update_frx6 to just plain update. It say installation aborted. I'm using update-frx6
drynaps said:
To avoid this you can just add the "no_partitions" (without the quotes) switch to your cmdline on your startup.txt of the loopmounted build and you should be good to go.
It may depend on your rootfs, but I'm using F22's rootfs and it works like a charm.
Click to expand...
Click to collapse
Damnit, hyc even told me about this - and I forgot about it.
Thanks for mentioning it!
villa15 said:
i"ve gotten into CWM but now its telling cand find the zip find even after scroll down to the update. do need to just rename update_frx6 to just plain update. It say installation aborted. I'm using update-frx6
Click to expand...
Click to collapse
I think you are choosing the wrong item in cmw, you need to choose 'Install zip from sd-cart' and then 'choose zip from sdcard'. Don't choose 'apply sdcart/update.zip' or something like that.
And if that doesn't work, maybe try another build. There is a (really small, because I tested it myself) option that the frx06 cmw build doens't work well.
jellenl said:
I think you are choosing the wrong item in cmw, you need to choose 'Install zip from sd-cart' and then 'choose zip from sdcard'. Don't choose 'apply sdcart/update.zip' or something like that.
And if that doesn't work, maybe try another build. There is a (really small, because I tested it myself) option that the frx06 cmw build doens't work well.
Click to expand...
Click to collapse
No thats not it. i did just just what u are saying. I even tried the CherryPieV3 and it still installation aborted. I'm using CWM 1.8 could that be the problem
If you already have CWM files on your phone, then do not just install the CherryPieV3.zip file. You must extract the zip file which has another zip file inside that you should use to install in CWM.
bleuleon said:
If you already have CWM files on your phone, then do not just install the CherryPieV3.zip file. You must extract the zip file which has another zip file inside that you should use to install in CWM.
Click to expand...
Click to collapse
Yes, you´re right. But he said that he also tried frx06, and that doesn´t worked for him too, and with the frx06.zip bundle, you don´t need to extract it first (if i'm right ;p)
jellenl said:
Here is the CMW version of the normal FRX06 by arrrghhh. All credits goes to him, I only made it ready for clockwork mod. Gapps are already included so you don't have to flash them seperate with this build.
Click to expand...
Click to collapse
I tried to install your CMW version of he Arrghhh FRX06 build but it fails on installing.
I have followed all the steps closely but still can't get it installed.
In the CWM tool when I choose Install zip from SD card and then choosing the FRX06 update the install process starts and within a few seconds aborts.
This is what I see on my screen:
Installing: // sdcard/npkboot/update-frx06.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted
Using the FRX06 CWM build from this thread with the WIS-Tilt2 kernel.
Does anybody have a clue about why this is not working?
Since it would of been alot to type out I made a video and to show the problems.
---> Video
I also tried running CM7 off a SD and it was a no go as well. The only thing that will boot off a SD is CWM.
Thank you for your help.
Novalis31 said:
Since it would of been alot to type out I made a video and to show the problems.
---> Video
I also tried running CM7 off a SD and it was a no go as well. The only thing that will boot off a SD is CWM.
Thank you for your help.
Click to expand...
Click to collapse
use this link and carefully follow directions-it will fix your problem if you can boot sdcard with these instructions
you will return to stock 1.4.0 factory - better than unusable
good luck!
I forgot the link - http://forum.xda-developers.com/showthread.php?t=1470910
Here it is.
Can someone give me detailed instructions on how to install cyanoboot on emmc please
Sent from my Nook Tablet using xda premium
scotthall1515 said:
Can someone give me detailed instructions on how to install cyanoboot on emmc please
Sent from my Nook Tablet using xda premium
Click to expand...
Click to collapse
The easiest way is to install cm9 alpha 0 (although it is an alpha, so be prepared for issues with the OS itself, plus remember that as an anti-profiteering measure it expires. read the full thread for more info....). When you use cyanoboot on emmc, you need to move the contents of boot.img and recovery.img so that they start at block 512. You can use dd or fastboot to put them on emmc...
See the original CyanoBoot thread as it talks about the above in a lot of detail, tho probably more than you need.
I read your post like five times I've flashed many Roms and did many things with phones and tablets. But I don't know what you mean by putting it at 512 or something I'm still a noob know how to flash move some things but when it comes to this I'm kind of lost
Sent from my PG86100 using xda premium
scotthall1515 said:
I read your post like five times I've flashed many Roms and did many things with phones and tablets. But I don't know what you mean by putting it at 512 or something I'm still a noob know how to flash move some things but when it comes to this I'm kind of lost
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
+1 to this, i'm trying to figuring out how to install it on emmc, in the post you get the idea of what you need to do but not how to do it, i mean what commands run,etc to install it. Say i want to test CM9 and want cyanoboot installed internally.
Could someone that has succesfully installed it internally (emmc) post proper instructions for this. TIA.
~ Veronica
lavero.burgos said:
+1 to this, i'm trying to figuring out how to install it on emmc, in the post you get the idea of what you need to do but not how to do it, i mean what commands run,etc to install it. Say i want to test CM9 and want cyanoboot installed internally.
Could someone that has succesfully installed it internally (emmc) post proper instructions for this. TIA.
~ Veronica
Click to expand...
Click to collapse
This may not be the exact answer you're looking for, but if you want to try it, just flash the newest CM9 (alpha 0.03) as it will install Cyanoboot to eMMC as well. I believe it's all contained in the CM9 boot.img.
There is no padding if you use flashing_boot.img on sdcard.
For emmc/internal, you need to pad flashing_boot_emmc.img to 512KB.
You have to pad flashing_boot_emmc.img correctly or else it can't find boot.img/recovery.img so you end in a bootloop.
dd if=/dev/zero of=flashing_boot_emmc.img bs=1 seek=524287 count=1
flashing_boot_emmc.img is then filled with zeros so the file size is 512KB. You then need to append boot.img or recovery.img to it.
cat flashing_boot_emmc.img boot.img > new_boot.img
Your new_boot.img can now be flash.
I haven't use cyanoboot, but bauwks 2ndboot method is the same except you need to pad it to 256KB.
You can gain cyanoboot by flashing my mmcblk0p2 i uploaded here, if you like
http://forum.xda-developers.com/showthread.php?t=1616951&page=2
I was recently given a nook tablet. It is running version 1.4.3. The only root methods I have been able to find all involve using the NT16or8gbV4_7 image and I can not find a working link to the file. Is there another way to internally root and install a recovery so that I can flash roms?
Am preparing a boot2recovery from sdcard for helping new nook tablet users install roms.
Unzip and copy everything included in this zip package to the root of a fat32 sdcard and tell me if you can boot into cwm.
http://d-h.st/ZRC
Btw this is development section and your problem belongs to q&a
demetris_I said:
Am preparing a boot2recovery from sdcard for helping new nook tablet users install roms.
Unzip and copy everything included in this zip package to the root of a fat32 sdcard and tell me if you can boot into cwm.
http://d-h.st/ZRC
Btw this is development section and your problem belongs to q&a
Click to expand...
Click to collapse
Sorry, should have put it in Q&A. Thanks for the response. If I unzip the files and copy them to my sdcard the nook still boots normally. They look like the files that are on my sdcard if I used windiskimager to write a bootable sdcard. Wouldn't I have to write stuff to the card and not just copy them over?
You must prepare the sd card for Nook compatibility booting
i bet you didn't.
If i remember well is 1st partition/70mb/fat32/named boot/and must be active.
Search around for answers or be patience until i find some time to prepare a new quide.
demetris_I said:
You must prepare the sd card for Nook compatibility booting
i bet you didn't.
If i remember well is 1st partition/70mb/fat32/named boot/and must be active.
Search around for answers or be patience until i find some time to prepare a new quide.
Click to expand...
Click to collapse
Yeah I had started to do that from one of the guides but had since re-formatted the card. Anyway I set it up as such and copied the files over. It's booting to Cyanoboot but I'm seeing "bboti: bad boot image magic (in memory)" and "Hold n for menu". Holding n does nothing.
Go into the stickies section there is a full guide with links to the files.
Sent from my LG-MS840 using xda app-developers app
Vyrus69 said:
Go into the stickies section there is a full guide with links to the files.
Sent from my LG-MS840 using xda app-developers app
Click to expand...
Click to collapse
There is only one guide in the stickies on this page and that involves using ADB and the link to the instructional video is dead. The other guides I've found required the file I mentioned above which all lead to dead links. I was hoping for a bootable SD card then installing a recovery internally to the nook so that I can flash roms directly from the recovery as I've done with many other Android devices.
I figured it out, can a mod please delete this thread? Thanks for the help guys.
Snakebear said:
I figured it out, can a mod please delete this thread? Thanks for the help guys.
Click to expand...
Click to collapse
Agreed. Somebody delete this, no offense Snakebear.
with the massive overhaul that is kitkat, google changed alot of files, and therefore a new way must be discovered to switch internal/external storages.
The editing vold.fstab option from 4.1-4.2 no longer works as vold.fstab was removed in 4.3, and the editing build.prop method for 4.3 no longer works.
Anyone know how to do it for 4.4?
thanks in advance
No Luck So Far
Been working for hours trying to figure this one out. Things to note is that now there are two mount points.
1) /mnt/media_rw/sdcard1 / sdcard0 (this has the actual /dev/block/vold/179:1 origin
2) /dev/fuse /storage/sdcard1 / sdcard 0
I've been unsuccessful trying any of the old build.prop tweaks. Hopefully someone smarter will come along and bang this one out.
Bump..... Stuck on 4.3 till a solution arises
Sent from my GT-I9100 using XDA Premium 4 mobile app
I've asked the compiler of the NeatKernel if he would fork it and swap out the sdcards in fstab.aries, but have yet to receive a reply....
Perhaps if you two went and posted the same, it might motivate him to do so.
Me too
alkspo said:
Bump..... Stuck on 4.3 till a solution arises
Sent from my GT-I9100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You got Company!
vivin007 said:
You got Company!
Click to expand...
Click to collapse
Same here! I upgraded to 4.4 and then realised that the build.prop 's changes made in 4.3 doesn't work for 4.4. Downgrading to 4.3 till there is a solution.
Still no "real" solution. but pretty convenient for me.
@fusionjack integrated swap option in the rom i was using which is slimsaber, so now i have swap
unfortunately, its only for this rom unless other rom makers incorporate it as well
alkspo said:
Still no "real" solution. but pretty convenient for me.
@fusionjack integrated swap option in the rom i was using which is slimsaber, so now i have swap
unfortunately, its only for this rom unless other rom makers incorporate it as well
Click to expand...
Click to collapse
Good news, so it's not impossible, it's just about time to see the swap method for 4.4 floating around.
I found an application that allows you to move the data from games to external sdcard, but you have to run the game through the application to play it though. Its called gl to sd, your phone must be rooted though.
Sent from my GT-I9100 using xda app-developers app
anatoliy0813 said:
I found an application that allows you to move the data from games to external sdcard, but you have to run the game through the application to play it though. Its called gl to sd, your phone must be rooted though.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yeah I know it, but DirectoryBind is better m8. Once it moves and link the data to external you can forget about it.
I've been trying to swap the storage on my note 2 on 4.3 can abtobetell me how to do this tried so many methods and nothing works. I would really appreciate some help guys. Thanks in advance
bigevil124 said:
I've been trying to swap the storage on my note 2 on 4.3 can abtobetell me how to do this tried so many methods and nothing works. I would really appreciate some help guys. Thanks in advance
Click to expand...
Click to collapse
Try file, called "fstab.sun6i" in / folder. I keep trying, but all the changes, I made was unstable...If I'll make some progress I'll write it down
Hi im not sure if this helps but someone released a script for cm11 to swap sdcards. Worked fine on resurection for me all I tested.the thread is somewhere in galaxy2 forum I posted to his thread so one of my last replys. I will find the link and edit
http://forum.xda-developers.com/showthread.php?t=2595756
Sent from my GT-I9100 using XDA Premium HD app
swap internal sd to external
Hello
did anyone come up to a solution for this or have any info about it?
i want to swap mine too and nothing seems to work on Kitkat
thank you
rictec said:
Hello
did anyone come up to a solution for this or have any info about it?
i want to swap mine too and nothing seems to work on Kitkat
thank you
Click to expand...
Click to collapse
Hi
on kitkat, you should unpack your boot.img file, update the fstab.* files inside, repack it, and flash it.
The way the img file is built depends on your device manufacturer. I did it successfully on my mtk tablet with the tools I found in this forum.
I am pretty sure that unpack/pack tools exist for samsung as well (for example: http://forum.xda-developers.com/galaxy-s3/help/how-to-unpack-split-samsung-boot-img-t1810907 )
Good luck in your search.
tried that but it failed
seb_131 said:
Hi
on kitkat, you should unpack your boot.img file, update the fstab.* files inside, repack it, and flash it.
The way the img file is built depends on your device manufacturer. I did it successfully on my mtk tablet with the tools I found in this forum.
I am pretty sure that unpack/pack tools exist for samsung as well (for example: http://forum.xda-developers.com/galaxy-s3/help/how-to-unpack-split-samsung-boot-img-t1810907 )
Good luck in your search.
Click to expand...
Click to collapse
thank you for you reply i already try that had some trouble to flash back the boot and when i manage to do it fstab got ignored
i m currently doing that with a boot script but have to run it every time the table reboots
its not a samsung is a storex A31 based device
rictec said:
thank you for you reply i already try that had some trouble to flash back the boot and when i manage to do it fstab got ignored
i m currently doing that with a boot script but have to run it every time the table reboots
its not a samsung is a storex A31 based device
Click to expand...
Click to collapse
You have to look for the dev kit dedicated to your processor. Have a look there : http://www.slatedroid.com/topic/73913-onda-kitchen-a31-a31s/
I have a mtk based device. I found the tools in this forum. I edited the 3 fstab.* files I found, and then all worked fine.
thank you
seb_131 said:
Hi
on kitkat, you should unpack your boot.img file, update the fstab.* files inside, repack it, and flash it.
The way the img file is built depends on your device manufacturer. I did it successfully on my mtk tablet with the tools I found in this forum.
I am pretty sure that unpack/pack tools exist for samsung as well (for example: http://forum.xda-developers.com/galaxy-s3/help/how-to-unpack-split-samsung-boot-img-t1810907 )
Good luck in your search.
Click to expand...
Click to collapse
seb_131 said:
You have to look for the dev kit dedicated to your processor. Have a look there : http://www.slatedroid.com/topic/73913-onda-kitchen-a31-a31s/
I have a mtk based device. I found the tools in this forum. I edited the 3 fstab.* files I found, and then all worked fine.
Click to expand...
Click to collapse
i have those thank you did not wanted to do a entire img just to change some files on boot but it looks like i have to maybe i do some more twicks and be great
Foldermount maybe a good solution
alkspo said:
with the massive overhaul that is kitkat, google changed alot of files, and therefore a new way must be discovered to switch internal/external storages.
The editing vold.fstab option from 4.1-4.2 no longer works as vold.fstab was removed in 4.3, and the editing build.prop method for 4.3 no longer works.
Anyone know how to do it for 4.4?
thanks in advance
Click to expand...
Click to collapse
Before 4.4 I could do it by "Android Internal to External sdcard" app, but this app couldn't do the trick on 4.4 KitKat OS, so "Foldermount" could be a good solution for you. All this app does is make a image of your apps (that you want to) to sdcard. The real files are located in external sdcard and only the clone file ( of max few KB) will residue at internal sdcard. If you are a gamer, this will help you until the real solution arrives.
Good Luck.
There is real solution! Or at least it works for me.
biopsin said:
Since Android 4.2 and the intro of multiusers there is a problem with bind folders across sdcards, making any attempt on mount bind folders as root would result in visible to root only.
Solution is to fool Android with temporary hijack debuggerd to create the mount binds for us. Thanks Chainfire for this workaround!
* Download both files and rename without .txt
* edit debuggerd.mnt to suit your needs (using any other dir then /emulated/legacy/ will result in read only if browsing folders from sdcard0)
* move debuggerd.mnt to /system/bin
* move mount.sh to any place with execute permissions
* execute mount.sh with any preferred method.
cheers!
Click to expand...
Click to collapse
Quoted from http://forum.xda-developers.com/showthread.php?t=2718760.
Thank You biopsin! Thank You Chainfire!
I'm including my files, but 'mount.sh' was not really changed in practical sense.
In case of 'debugger.mnt' it all depends on Your device. You need to check which block for You is internal and which external storage. Just 'mount' command should help.
You can also use it to mount only one folder - like 'obb', which will let You keep applications data on external card.
Just use "mount -o bind /storage/sdcard1/Android /obb /storage/sdcard0/Android/obb" command in debuggerd.mnt file.
You can also have different 'debuggerd.mnt' files (of course called somehow different - like 'debuggerd02.mnt') and different 'mount.sh' files which will let You mount different things whenever You like.
Enjoy!
-----
And for easier usage You can try $cripter - https://play.google.com/store/apps/details?id=sites.mjwhitta.scripter&hl=en .
It's the best I found.
This guide is show you how to install second OS in SDCard, so you can have two complete separate OS (each have their own /system, /data and /cache), this will be useful if you want to try out a new ROM or a new version, like CM or latest Stock build etc. I have pre-build 2 ROMs in this guide. and list the instructions of how to do it in post #2.
The whole method is just an implementation of @SHM (Modding.MyMind) guide that inside the post here, so all the credit goes to him:
http://forum.xda-developers.com/showpost.php?p=62460895&postcount=325
Highlight of the steps:
1. Partition a SDCard (32GB or bigger) to have 3 ext4 partitions after regular FAT32 partition
2. Flash two customized flashable zip in twrp so that:
boot image flashed to /dev/block/mmcblk0p18 (regular boot partition)
system image flashed to /dev/block/mmcblk1p2 (sdcard)
The boot image contains the fstab file, it has been updated to use partitions on sdcard as the /system, /data and /cache for the 2nd OS.
And of course, the flashable zip has updater script changed so that, it will flash they system image to correct partition on SDCard.
Note / Limitation:
1) After boot to 2nd OS on the SDCard, theoretically, while you are in Android OS, everything should work. The speed/performance may differ depends on the SDCard read/write speed.
2) TWRP, except flash the zip to install the customized system image to SDCard, all other function will not work for the 2nd OS, The backup/restore function is still working on the primary OS /system, /data etc.
3) Boot partition (/dev/block/mmcblk0p18), this partition will decide which OS it will boot, and the boot image should corresponded to your OS system partition. So if you flashed above boot image for 2nd OS, it will find /system on SDCard and boot it. And if you flashed (or restore) your primary OS boot image, then it will boot to your primary OS /system.
Things you need before you start:
1. MT2L03 with Lollipop installed, TWRP installed, and have a backup of your primary OS (at least /system, and /boot partitions)
2. An empty SDCard that is 32GB or bigger, strongly recommend class 10 or faster. (16GB will work, then you don't have much external space left)
Steps to install 2nd OS to sdcard:
(Note, I will call the empty SDCard as sdcard#2, and your current sdcard in the phone as sdcard#1.)
1. Make a backup of your current OS using twrp, include at least /system and /boot, to your sdcard#1.
2. Install the PartitionWizard (files location below) on windows, and put the empty SDCard#2 to computer sdcard reader.
3. Launch Partition Wizard, and carefully re-partition your SDCard#2 to following:
(pls refer to xda wiki about the usage: http://forum.xda-developers.com/wiki/SD_card_partitioning )
1st Partition: FAT32 primary size: (Total size minus 15000MB), for example, for 64GB(60000MB) card, choose 45000MB
2nd: ext4 primary size: 1800MB (/system for 2nd OS)
3rd: ext4 primary size: 12500MB (/data for 2nd OS)
4rd: ext4 primary size: rest space, should be great than 200MB (/cache for 2nd OS)
Since partition 2/3/4 total size is 14320MB, thus the 1st partition size is (Total size minus 15000MB)
4. Apply the change, this will take some time (like 20 to 30min).
5. Once sdcard#2 is re-partitioned and formatted, unplug and re-plug sdcard#2 to windows again. Right click the sdcard drive letter, and click "Open" to open the FAT32 partition. ( I found double click the drive letter will give error if the FAT32 is bigger than 32GB, but right click and open works)
Copy two flashable zip (file location below) to the sdcard#2.
6. Reject the sdcard#2, and remove it from windows machine.
7. In Mate2 phone, go to settings, storage, and un-mount your current SDCard#1, after it is unmounted, take out the sdcard#1 and put it to a save place. Do not mess the two sdcards!!
8. Put in the sdcard#2 to the phone, and reboot to TWRP.
9. Install the two zip you download in step 5 from sdcard#2. Reboot.
How to go back to your primary OS:
a. Put in sdcard#1 to the phone, boot into TWRP, restore your /boot partition from the backup you took in above step 1. then reboot.
How to switch to the 2nd OS on the sdcard again:
a. Put in sdcard#2 to the phone, boot into TWRP, flash the "MT2L03_xxx_BootOnly.zip" you downloaded in step 5.
Files to download:
PartitionWizard in above step 2:
http://tinyurl.com/q62m68x
location: under Lollipop/SD_Partition_Tools
FileName: pwfree91.exe
This tools is mentioned in XDA wiki: http://forum.xda-developers.com/wiki/SD_card_partitioning
You can use any tool you know to do the re-partition, above tools is what I used and it works.
Customized flashable in zip in above step 5:
http://tinyurl.com/q62m68x
location: under Lollipop/OS_on_SDCards
FileName:
If you want install B309 as 2nd OS, please download "MT2L03_B309_DBoot_BootOnly.zip" and "MT2L03_B309_DBoot_SystemWithRoot.zip"
If you want install CM12 as 2nd OS, please download "MT2L03_CM12_0820_DBoot_BootOnly.zip" and "MT2L03_CM12_0820_DBoot_SystemWithRoot.zip". (Please note the GApp is already included in the zip)
Attached two screenshot of the partition tool, one for 32GB, one for 64GB. Please note though the pic showing in GB, but when config the size, please use MB to make sure the partition size is accurate and big enough.
//reserved
I am not sure how many people is interested in dual boot, so for now, I have pre-built B309 and CM12 only.
In order to build a customize ROM for installing in SDCard, as detailed in SHM original post, two steps are required:
1) For Mate2, after split the original boot image, and unpack the ramdisk, only need following cmd to update the fstab:
cd ramdisk
sed -i 's/platform\/msm_sdcc.1\/by-name\/system/mmcblk1p2/g' fstab.qcom
sed -i 's/platform\/msm_sdcc.1\/by-name\/userdata/mmcblk1p3/g' fstab.qcom
sed -i 's/platform\/msm_sdcc.1\/by-name\/cache/mmcblk1p4/g' fstab.qcom
Then repack it back to boot2.img. Please note the un/repack boot image tool need support DTB section.
2) Then in the updater script of /META-INF/com/google/android/updater-script, install system.img to /dev/block/mmcblk1p2, and still install the new boot2.img to /dev/block/mmcblk0p18.
@SHM, Unfortunately, many tools mentioned in original post, the Aparted tool, and the android binary mkbootimg etc all have problem running under Lollipop, so for now, I am doing all the ROM modification under linux.
Lol. You just had to do it. Lol awesome work. And you picked up on that fast. Thanks Xordos.
Our divices supposedly only support up to a 64 gb SD card. I wonder if since we would partition the SD if it would accept a 128GB card and see it as two x 64GB's
MikeyLee said:
Our divices supposedly only support up to a 64 gb SD card. I wonder if since we would partition the SD if it would accept a 128GB card and see it as two x 64GB's
Click to expand...
Click to collapse
I think if huawei mention 64gb probably because they didn't have 128gb to test when they release the phone. 128gb has nothing special compare with 64gb card. But I could be wrong since I don't have 128gb.
For general use, no need to partition 128gb card unless you want to do something like this thread.
@xordos, no worries. Many things were broken because of Lollipop using a new linker file that checks if the binary is PIE or not. If it is not PIE or if it's not Statically compiled then it won't work on Lollipop. The linker file can be modified though to ignore this check and thus allow them to work regardless. This too could also resolve some issues with other apps not wanting to work on Lollipop . Modifying the linker file is relatively simple but this is off topic so I shall end it here.
Great work. Knew you would be able to get it done. Cheers!
Sent from my C525c using Tapatalk
SHM said:
@xordos, no worries. Many things were broken because of Lollipop using a new linker file that checks if the binary is PIE or not. If it is not PIE or if it's not Statically compiled then it won't work on Lollipop. The linker file can be modified though to ignore this check and thus allow them to work regardless. This too could also resolve some issues with other apps not wanting to work on Lollipop . Modifying the linker file is relatively simple but this is off topic so I shall end it here.
Great work. Knew you would be able to get it done. Cheers!
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
yup, exactly PIE problem.
So this is pretty cool that no need to worry about /data mixed up by different rom. but open the back cover is a little bit pain and my main sdcard is almost full so I am thinking to use otg cable. So i am wondering if we have grub-like boot image to have boot menu, or, the root is not ramdisk, but a file system, so we can modify the fstab after mount it. I know, maybe I ask too much, android is not design like linux.
xordos said:
yup, exactly PIE problem.
So this is pretty cool that no need to worry about /data mixed up by different rom. but open the back cover is a little bit pain and my main sdcard is almost full so I am thinking to use otg cable. So i am wondering if we have grub-like boot image to have boot menu, or, the root is not ramdisk, but a file system, so we can modify the fstab after mount it. I know, maybe I ask too much, android is not design like linux.
Click to expand...
Click to collapse
Yea, it's pretty nice. You can even modify the TWRP recovery for use with making backups and restoring to each Rom specific to their partition. Look at TWRP Unified and check out it's script inside the ramdisk. Modify the script to check some stuff and tell it which fstab to use . This way when you jump back and forth between roms just by the boot.img you flash TWRP will automatically recognize the change upon it booting up and target the partitions properly when you make a backup/restore. Put some thought into all of this and I am sure you could take this thread a bit further.
There are projects out there that are designed for multibooting on android devices but you would need to port one of them.
Sent from my C525c using Tapatalk
Just an update that the AParted app works for Lollipop now. Tested it out on my external sd tonight by resizing my fat partition without losing any of my contents and adding additional partitions with multiple filesystem's such as f2fs and ext4. Quick and effective .
Sent from my Ascend Mate 2 using Tapatalk
I have a HUGE GIFT that I am about to share for all you mate2 fans out there. Dual Booting just got taken to another level. Think of it as Multi Booting . Here are two screenshots to share as teasers. I have it working for our device and its a beast!
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
I have a HUGE GIFT that I am about to share for all you mate2 fans out there. Dual Booting just got taken to another level. Think of it as Multi Booting . Here are two screenshots to share as teasers. I have it working for our device and its a beast!
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Can't waiting.
MT2-User said:
Can't waiting.
Click to expand...
Click to collapse
More teasers. These pics show that its possible to install roms without the need for TWRP. Will be sharing this very soon. I'm running CM, PAC, and Carbon right now.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
More teasers. These pics show that its possible to install roms without the need for TWRP. Will be sharing this very soon. I'm running CM, PAC, and Carbon right now.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
You run all three (or four including stock one)?
MT2-User said:
You run all three (or four including stock one)?
Click to expand...
Click to collapse
Yes. I can install the roms using either the system, data, and/or cache partition however I don't recommend cache because it's size is way too small for our device. Can even choose to install them on your external sd. I can install and run as many roms as I like as long as I have space for the new ROM. The app even makes it possible to install new builds to the proper ROM without touching your primary ROM or any other ROM other than what its told to target. More info will be shared when I open a thread on it. In short, you just download the ROM, then patch the ROM.zip using the app. You then flash that patched zip which in turns will modify the boot.img to give it dualboot support. You can patch zips for SuperSU, gapps and so forth so you may install them to a specific ROM. Its legit bro.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
Yes. I can install the roms using either the system, data, and/or cache partition however I don't recommend cache because it's size is way too small for our device. Can even choose to install them on your external sd. I can install and run as many roms as I like as long as I have space for the new ROM. The app even makes it possible to install new builds to the proper ROM without touching your primary ROM or any other ROM other than what its told to target. More info will be shared when I open a thread on it. In short, you just download the ROM, then patch the ROM.zip using the app. You then flash that patched zip which in turns will modify the boot.img to give it dualboot support. You can patch zips for SuperSU, gapps and so forth so you may install them to a specific ROM. Its legit bro.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Could they or some of them share Data?
MT2-User said:
Could they or some of them share Data?
Click to expand...
Click to collapse
Not at the moment. You would have to reinstall your user apps again. You can backup your apps on your primary rom using something like Titanium backup and then restore them on the other ROM.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
Not at the moment. You would have to reinstall your user apps again. You can backup your apps on your primary rom using something like Titanium backup and then restore them on the other ROM.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
oh ic
MT2-User said:
oh ic
Click to expand...
Click to collapse
The app implements this feature but I'm working it out if that makes you feel better lol.
Sent from my Ascend Mate 2 using Tapatalk
Damn nice work SHM.. Congrats. And thanks!
Moody66 said:
Damn nice work SHM.. Congrats. And thanks!
Click to expand...
Click to collapse
I have it working %100 now. Its 3:35 am where I am at so time for bed. Sharing apps works as well between roms.
Sent from my Ascend Mate 2 using Tapatalk