dualboot guide for Z00L - Zenfone 2 Laser Android Development

UPDATE #NEW METHOD COMING
AND USING THAT U DONT HAVE TO MAKE ANY CHANGE IN ROM ZIP FILE EVERY TIME
AND A VIDEO ALSO I AM WORKING TO MAKE THE PROCESS MORE easily UNDERSTANDABLE
Pre requisite
1. unlocked bootloader
2. Root
3. Twrp installed
4. Pc
5. Or usb otg
My guide assumes
Primary rom - stock zenui rom or can be any rom u r using
Secondary rom - aoscp extended latest build
Dualboot means- installing roms on yoyr device without wiping your current rom, so rom called secondary rom can be installed on internal storage itself, or sdcard, usb
In this guide i have used sdcard for installing secondary rom
Steps
First we have to partition our sdcard so backup everything to pc as sdcard will be erased
.Install Aparted from playstore or download from attachment
.Open the app A parted. Grant root
.Goto tools tab select partition 1 it should be ur sdcard
Select delete from below and click apply
. now goto create and click add use this as fat32 size as u wish
. again click add now this will be ur system partition so use this as ext4 size min. 3000mb
. again click add ext4 for data partition and size should be something around 5000mb min. Max depends on ur sdcard space
. add cache partition ext4 size min. 100mb
.now apply the changes.
Now u have prepare ur rom zip file .
First unzip the rom
Just replace the attached boot.img with boot.img in ur rom zip file and same do with updater script
Location of updater script is metainf/com/google/android
And then repack the rom file into zip
Now flash the attached twrp recovery
Boot into new twrp goto wipe
Change file system
Select system, format as ext4
Go back select data and format as ext4
And do same with cache
Now what
Just copy ur new rom zip file onto sdacrd after formatting and flash it
Gapps simply flash
For switching roms
Just install flashify from playstore and flash the boot.img of the rom u want to use
I know above guide is not full fledged but if u get stuck anywhere just comment i am here to help
But if u are a developer u may have know the proces by ur own
Sorry for my bad english
Press thanks if i helped you. :good::laugh:
Thanks to rom developers coz without them there was no need of dualboot
And if u want to use another rom as dualboot just telegram me its boot.img and updater script
I will provide u the modified one
Id. ady692
https://drive.google.com/file/d/0B8O22xDxCq2FWm5KNThNaWtiOHc/view?usp=drivesdk

addy692 said:
Pre requisite
1. unlocked bootloader
2. Root
3. Twrp installed
4. Pc
5. Or usb otg
My guide assumes
Primary rom - stock zenui rom or can be any rom u r using
Secondary rom - aoscp extended latest build
Dualboot means- installing roms on yoyr device without wiping your current rom, so rom called secondary rom can be installed on internal storage itself, or sdcard, usb
In this guide i have used sdcard for installing secondary rom
Steps
First we have to partition our sdcard so backup everything to pc as sdcard will be erased
.Install Aparted from playstore or download from attachment
.Open the app A parted. Grant root
.Goto tools tab select partition 1 it should be ur sdcard
Select delete from below and click apply
. now goto create and click add use this as fat32 size as u wish
. again click add now this will be ur system partition so use this as ext4 size min. 3000mb
. again click add ext4 for data partition and size should be something around 5000mb min. Max depends on ur sdcard space
. add cache partition ext4 size min. 100mb
.now apply the changes.
Now u have prepare ur rom zip file .
First unzip the rom
Just replace the attached boot.img with boot.img in ur rom zip file and same do with updater script
Location of updater script is metainf/com/google/android
And then repack the rom file into zip
Now flash the attached twrp recovery
Boot into new twrp goto wipe
Change file system
Select system, format as ext4
Go back select data and format as ext4
And do same with cache
Now what
Just copy ur new rom zip file onto sdacrd after formatting and flash it
Gapps simply flash
For switching roms
Just install flashify from playstore and flash the boot.img of the rom u want to use
I know above guide is not full fledged but if u get stuck anywhere just comment i am here to help
But if u are a developer u may have know the proces by ur own
Sorry for my bad english
Press thanks if i helped you. :good::laugh:
Thanks to rom developers coz without them there was no need of dualboot
And if u want to use another rom as dualboot just telegram me its boot.img and updater script
I will provide u the modified one
Id. ady692
https://drive.google.com/file/d/0B8O22xDxCq2FWm5KNThNaWtiOHc/view?usp=drivesdk
Click to expand...
Click to collapse
Please comment below
How this guide can be improved
Upcoming support.
#dualboot patcher support

Wanna work together so that we make it comparatable with twrp...and users can use it directly

govind1233 said:
Wanna work together so that we make it comparatable with twrp...and users can use it directly
Click to expand...
Click to collapse
Yeah anytime
U can contact me on telegram @ady692

addy692 said:
Please comment below
How this guide can be improved
Upcoming support.
#dualboot patcher support
Click to expand...
Click to collapse
Awesome :good: Nice work buddy

prakharluv said:
Awesome :good: Nice work buddy
Click to expand...
Click to collapse
thanks @prakharluv

Related

[01 FEB][RECOVERY] ClockworkMod Recovery for HD2 - v1.3

READ ALL OF THE OP BEFORE POSTING QUESTIONS​
The Intro;
As we now have NAND booting for the HD2, its time we also had a way to flash ROMs from the SD aswell so here we have ClockworkMod Recovery compiled for the HD2. It is fully working except ROM Manager is not supported.
Recovery can now boot from NAND instead of the old SD Card boot method, to flash the rom, download the recovery with the partition layout you require, then flash as you would a standard NAND rom using DAF and MAGLDR USB Flasher. then select AD Recovery to load into recovery.
Click to expand...
Click to collapse
MAGLDR v1.13 IS REQUIRED, OLDER VERSIONS ARE NOT SUPPORTED, DOWNLOAD v1.13 HERE​
Click to expand...
Click to collapse
Kind note to Devs;
Please stop posting modified flash.cfg files for use with CWM
CWM is designed to make it easier to flash roms without needing a windows PC, if you post a different flash.cfg in each rom thread then it defeats this purpose as a pc will be required for flashing each layout.
Stick to using the default partition layouts or use USB flasher
Click to expand...
Click to collapse
WARNING MESSAGES:
GOING FROM A DAF FLASHED ROM TO A RECOVERY FLASHED ROM WILL WIPE ALL DATA
IF YOU FLASH ANOTHER ROM USING DAF, RECOVERY WILL NO LONGER WORK CORRECTLY, YOU WILL NEED TO REFLASH RECOVERY
Click to expand...
Click to collapse
Features;
-Flash ROMs in update.zip format
-Backup and restore ROMs using Nandroid
-Flash ROMs from the SD card without use of a PC
-Easilly Wipe all Data/Cache
-Repartition SD card for use with Apps2SD
-Full Root ADB access
-Fix app permissions
Click to expand...
Click to collapse
How to use;
For MAGLDR NAND Boot;
1. Download recovery with partition size for the type of rom you plan on using, see guide below if unsure.
2. Extract downloaded file and load magldr into USB Flasher mode.
3. Run DAF.exe and follow instructions
4. After completed and phone reboots, hold power key and select AD Recovery from list
5. Recovery will now load
Click to expand...
Click to collapse
For old style SD Boot;
1. download one of the partition files for SD Boot, if you don't know which one you need, use the 250M one or check with rom developer.
2. Extract downloaded zip to a folder of your choice
3. Copy contents of copy_to_sd_root (initrd.gz and zImage) to the root of your sd card
4. boot into magldr and select USB Flasher option while phone is connected to PC
5. Run DAF.exe included in the zip and follow onscreen instructions.
6. After complete, again boot into magldr and select "Boot AD SD" option
7. ClockworkMod recovery should load, you can flash a rom from here.
Click to expand...
Click to collapse
Video Tutorials;
How To Install Clockwork Mod Recovery On The HD2 (Courtesy of GFurr)
How to Install NAND Android on HTC HD2 with ClockworkMod Recovery? (Courtesy of jayceooi)​
Click to expand...
Click to collapse
Downloads;
Latest;
-Download v1.3 150MB-
-Download v1.3 250MB-
-Download v1.3 400MB-
Old Versions;
-v1.2- DOWNLOAD
-v1.1- DOWNLOAD
-v1.0- DOWNLOAD - MegaUpload Mirror
Old Partition Layouts for SD Boot;
-150MB System-
-250MB System-
-400MB System-​
Click to expand...
Click to collapse
Changelog;
v1.3;
-Supports AD Recovery in MAGLDR
-MAGLDR v1.13 REQUIRED Download HERE
-400MB Partition layout now works with 512MB LEO for roms with Data2SD
v1.2;
-Fixed SD-EXT Backup/Restore/Wipe
v1.1;
-Updated ClockworkMod to 3.0.0.5, now based on Gingerbread Source
v1.0;
- Initial Release
Click to expand...
Click to collapse
Q&A;
Q. Ive flashed v1.3 but cant access recovery anymore.
A. Make sure you are using MAGLDR 1.13 and are selecting "AD Recovery" instead of "Boot AD SD"
Q. Ive downloaded v1.3 but there is no copy_to_sd folder
A. Recovery no longer requires any files on the SD card, just flash it like a standard nand rom and select "AD Recovery in magldr menu
Q. Can I change the partition sizes used for CWM
A. You can by editing the flash.cfg but this is not recommended, CWM is designed to make it easier for switching roms, by flashing a custom partition size you may stop other roms working and require reflashing a new partition size when you want to change roms.
Q. I dont know which partition size to download
A. Depending on what type of roms you plan on using, you should choose the partition size based on the following.
150MB Partition - For bare roms including CyanogenMod, AOSP, and MiUI
250MB Partition - For Standard sense roms including Desire and EVo based ROMs, can also be used for some squashed HD builds
400MB Partition - For Larger roms including unsquashed Desire HD and Z roms, ROMs REQUIRE data2sd for EU HD2 with 512MB NAND
Click to expand...
Click to collapse
*I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE BY USING THIS RECOVERY IMAGE*
​
Click to expand...
Click to collapse
Notes for devs;
Please add tags to the title of your threads stating if they are to be flashed with recovery or DAF, [ZIP] for recovery update.zip and [USB] if its installed over usb using daf.
The cache partition is only 10MB so that recovery can still use it, to get cache to work in android, make a directory in data called cachemnt and on boot symlink /cache to /data/cachemnt, this does not apply when using 150M partition size
Click to expand...
Click to collapse
Credits go to;
-Cotulla + DFT for the great work for Android on NAND
-CyanogenMod team for work on recovery
-Anyone else who has made the HD2 a great device
Click to expand...
Click to collapse
i think i just wet myself....thanks so much
RaiderX303 said:
As we now have NAND booting for the HD2, its time we also had a way to flash ROMs from the SD aswell so here we have ClockworkMod Recovery compiled for the HD2. It is fully working except ROM Manager support still has some issues. See below for features and how to use.
Because ROMs are not flashed using DAF, a set partition layout is required before flashing any ROMs using recovery, included in the download is DAF which is configured to create the required partitioning, just run as you normally would to flash a NAND ROM and you are set to flash a new ROM through recovery
WARNING: GOING FROM A DAF FLASHED ROM TO A RECOVERY FLASHED ROM WILL WIPE ALL DATA
WARNING: IF YOU FLASH ANOTHER ROM USING DAF, RECOVERY WILL NO LONGER WORK CORRECTLY, YOU WILL NEED TO REFLASH THE PARTITIONING TO USE RECOVERY AGAIN
Features;
-Flash ROMs in update.zip format
-Backup and restore ROMs using Nandroid
-Flash ROMs from the SD card without use of a PC
-Easilly Wipe all Data/Cache
-Repartition SD card for use with Apps2SD
-Full Root ADB access
-Fix app permissions
How to use;
1. Copy content of copy_to_sd_root folder to the root of your SD card
2. Power on phone holding power button to access magldr menu
3. Select "USB Flasher" option
4. Run DAF.exe and go through installer to set required partition layout
5. After reboot repeat step 2 to access menu again
6. Select "Boot AD SD" and recovery will load
Download;
-v1.0-DOWNLOAD
Changelog;
v1.0
- Initial Release
*I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE BY USING THIS RECOVERY IMAGE*
Request for devs;
Please add tags to the title of your threads stating if they are to be flashed with recovery or DAF, [ZIP] for recovery update.zip and [USB] if its installed over usb using daf.
Credits go to;
-Cotulla + DFT for the great work for Android on NAND
-CyanogenMod team for work on recovery
-Anyone else who has made the HD2 a great device
Click to expand...
Click to collapse
You have to be ****ting me!!! Great work!!! Soon... Nandroid Got Your Back. LOL.
---
Sent from my HD2 DROID.
Great.
Sent from my HTC HD2
@Raiderx
Is the rom manager support you are talking about the ability to flash different themes and stuff of that nature in recover mode? Also can we expect it in the future?
This is now officially an android phone. Finally get to back up Roms awesome!!!!
Rom manager support is an app that allows you to control the recovery from within Android and then reboot to recovery to run the commands
Sent from my Desire HD using XDA App
Hell Yes
How will I install roms and where will I get them I am confused!
mattfmartin said:
@Raiderx
Is the rom manager support you are talking about the ability to flash different themes and stuff of that nature in recover mode? Also can we expect it in the future?
Click to expand...
Click to collapse
Rom manager is just the app that that you get from the market to flash without booting to recovery we could wait on that.
what the doctor
this is progress and what ive been looking to add
Just to clarify the instructions... Do we extract the Downloaded zip to the Root of the Sd Card then flash What ROM we will be using? Words in bold are my keys...
Thanks
EDIT: Scratch that.. I guess I should have opened the Zip first.
This is Bad Ass!!
Wow! My dreams have come true
Thanks!
Oh man, this is amazing! Any chance of Amon Ra at some point?
to cool
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!
@Raider x
What I was getting at, I always see native android threads talking about flashing themes through recovery. Well we be able to do that with this?
jhr5474 said:
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!
Click to expand...
Click to collapse
Devs will need to release ROMs in update.zip format, there are none currently released although i am in the process of uploading one, you then copy the zip the dev provides to the root of the SD, and flash like you did on the G1
mattfmartin said:
@Raider x
What I was getting at, I always see native android threads talking about flashing themes through recovery. Well we be able to do that with this?
Click to expand...
Click to collapse
you will be able to flash themes using recovery once theme devs create them
SWEET!!!!!!!!!!!!
jhr5474 said:
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!
Click to expand...
Click to collapse
+1 good question, are we clear to load nand roms already or do the devs have to modify what they have? I think I will wait until more clarification.
Edit: thanks for the clarification
APJG said:
Oh man, this is amazing! Any chance of Amon Ra at some point?
Click to expand...
Click to collapse
What do u want from me? LOL As a matter of fact if i read this correctly this is almost what i need, a way to flash android ROMs without the usage of a pc (USB port). Can anyone tell me if it is correct
jhr5474 said:
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!
Click to expand...
Click to collapse
Yeah, We need some ROMS converted to flashable.zip's... I'm goning to load up CW now just so I can see it. LOL

[TUT]Custom mtd partitions

After tons of googling ive finally been able to customize the size of my data partition.
Im sharing it with you all...
Install Instuctions
It really is quite simple
1.download FR-recovery-v1.5.6-CustomMTD_S.zip and FR-boot-v1.5.6-CustomMTD_S.zip
2.create mtdpartmap.txt and put on /sdcard/ see configuration *
3.reboot to recovery
4.nandbackup
5.wipe cache + data
6.flash FR-recovery-v1.5.7-CustomMTD_S.zip(follow onscreen instructions)
7.reboot to recovery
8.Either : -
Nandrestore
or
Flash ROM + extras
9.flash FR-boot-v1.5.7-CustomMTD_S.zip
10.reboot
*For cyanogenmod- write "mtd 135 15"
this will give ur system 135mb, cache 15 mb and rest for data!!!!(u can change the values but be sure u give enough to system otherwise ull face problems while flashing)
NOTE-each time u flash a rom u MUST flash FR-boot-v1.5.7-CustomMTD_S.zip.
NOTE-if u reduce cache size by a large amount, market and other apps depending on cache will fc.
credits-Firerat for the files and instructions at http://forum.xda-developers.com/showthread.php?t=717874
as sense roms are heavy...this wouldnt be of much help.
PS-as always im not responsible if u brick ur device.
PRESS THANKS IF IT HELPED!
Can someone test this please? To OP: does it work?
Want to do it, but don't want a bricked phone.
I just need a 100 mb more for data, so i dont need the build in "move to sd" option from android.
Henry_1 said:
Can someone test this please? To OP: does it work?
Want to do it, but don't want a bricked phone.
I just need a 100 mb more for data, so i dont need the build in "move to sd" option from android.
Click to expand...
Click to collapse
Chicken. As I wrote in the other thread....it works.
Be careful not to undersize your Cache partition though or Market and other apps that rely on it for temp storage will force close.
The guy that said he uses a 10 MB cache partition is on better drugs than I can afford...
dude,
i followed all the mentioned steps by letter but unfortunately i still have the stock part intact
1-copied the files to Sd
2-creating the text file mtd 150 25
3-flashed the recovery attached
4-flashed the rom (caynogenmod 7)
5- flashed the boot file
still have the original partitions :S i am missing smthing ?
wildfire S , **UNLOCKED**
draconian said:
dude,
i followed all the mentioned steps by letter but unfortunately i still have the stock part intact
1-copied the files to Sd
2-creating the text file mtd 150 25
3-flashed the recovery attached
4-flashed the rom (caynogenmod 7)
5- flashed the boot file
still have the original partitions :S i am missing smthing ?
wildfire S , **UNLOCKED**
Click to expand...
Click to collapse
Yes.
First this is a confusing and partially explained tutorial...No offense. Here it is for CM7.x with updated script files and an mtdpartmap.txt for CM7.x
1/ Create the txt file and do not hit enter. Make sure there is no carriage return taking you to a second line.
2/Now save it as "mtdpartmap.txt" (For CM7x you can use 145 20 with no worries).
3/ Copy the recovery file, the boot file and the mtdpartmap.txt files to the root of your SD card
4/Copy Alquez's latest nightyly CM7 zip to the root of your SD card along with the latest gapps zip
5/Reboot to recovery
6/ Erase user data
7/ Under Mounts, format system
8/ Install zip from SD card and run the Recovery zip
9/ Go back to mounts and format data, cache and system partitions
10/ Go to advanced menu and reboot to recovery
11/ If you are restoring a NANDROID backup do so now using backup/restore
12/ If you are installing CM7.x Install zip from SD and flash the CM7 zip and the gapps zip
13/ Install zip from SD card and now flash the boot zip.
14/ Return to recovery main menu and reboot device
15/ Enjoy your roomy CM7.x install!
Don't listen to 135 for CM7! It's not close to enough.
Will it work with Wildfire S with unlocked bootloader (via HTC webpage)? Or is it only for S-OFF phones?
I have the bootloader unlocked and it seems that it does not work :-( Maybe I am doing something wrong?
Y not 250 20?
HTC WILDFIRE S
Cm7
@ d33spx the tutorial is perfect and complete.the steps u posted are unnecessary.
@everyone with s on but bl unlocked: it won't work.
@everyone with soff and cyanogen mod: 135 15 is more than enough...
For sense roms which are debloated 250 20 is good...
135 means I'll have Oly 135 MB internal?
HTC WILDFIRE S
ROM:CM7
1 GB INTERNAL MEMORY
806MHZ OVERCLOCKED
ELECTRIC CYAN THEME
szpaq69 said:
will it work with wildfire s with unlocked bootloader (via htc webpage)? Or is it only for s-off phones?
I have the bootloader unlocked and it seems that it does not work :-( maybe i am doing something wrong?
Click to expand...
Click to collapse
only on s-off phones !!
If i do a nandroid backup and after partition if i do a nandroid restore will the partition go??
kp.nikhil said:
If i do a nandroid backup and after partition if i do a nandroid restore will the partition go??
Click to expand...
Click to collapse
Follow the OP... Simple as that.
kp.nikhil said:
If i do a nandroid backup and after partition if i do a nandroid restore will the partition go??
Click to expand...
Click to collapse
You need to flash flash "FR-boot-v1.5.7-CustomMTD_S.zip" immediately after flashing a new ROM or Restoring any nandroid backup before restarting your device. This will keep your partitions.
Cheers!!
What mtdpartmap would you recommend for modpunks CM9?

[Q] Many questions (CWM, ROMs)

Hi,
I'm new here and I'd like to install a new ROM on my Gio but I want to make sure I know what I'm doing before trying something and bricking my phone. :angel:
ClockWorkMod
I installed CWM v5.2.0.6 (followed the instructions here). Is this ok, or do I need to install v5.0.2.7? And if I do need a newer version, is there a way to get an update or do I have to follow the same steps as before?
1.Download the CWM 5.0 v2 and copy to the Root (not in any folder) of your SD card
2. Put your phone in recovery Mode(press: Home button + Power button toghether)
3. In recovery mode, select the downloaded file from SD-card(Use Volume keys to navigate and home button for enter).
4. Search for the root gb updated.zip file on your SD-card
5. Run the update
6. Reboot
Click to expand...
Click to collapse
I tried creating a backup with the CWM version I have, but I get this error: "Can't mount /system".
CWM does create a folder in sdcard/ clockworkmod/ backup/ date, but it only contains the following files:
recovery.img and boot.img.
However, this post says I should actually have more files in the backup folder:
.android_secure.vfat.tar ,boot.img , cache.ext4.tar , data.ext4.tar , nandroid.md5 , recovery.img, system.ext4.tar.
Is this because of my CWM version? Or maybe because I still have the operating system that came with my device (+updates)?
What I really want to know is: can I rely on this backup, will it work?
ROMs
I want to install CM10.1.5 from here, but I have many questions and I don't really know where to look for answers. (Sorry, I really am a complete noob.)
What's the difference between androidarmv6 jenkins build and mardon build? And what's the difference between the 3 versions? Can I just install the Version with CM-Superuser and not worry about it?
Should the updates be installed via CWM - apply update from SDcard? What about the additions - CWM --> install zip from SDcard?
How can I install extras if they are "not CWM flashable"?
What happens to my apps when I install a new ROM? Do I have to install them all again? Is all data lost? Or will they all be restored from my google account and the SD card or something like that?
Finally, how can I use the ext2 partition in my SDcard to install apps? Is this function included in the ROM? Or do I need to install something else? a2sd darktremor? If yes, how (I find the instructions here confusing and overwhelming, and the post is old, so probably outdated)? Or should I use the "Link2SD" addition to the ROM?
I'm sorry for asking so much, but I'm feeling kind of lost.
Thanks in advance.
Anyone?
I've continued trying to figure things out when I have time. I'll post what I find in this thread, in case someone else comes here looking for answers to similar doubts/problems.
In trying to understand what's going on with ClockWorkMod Recovery, I found this very useful link:
wwwDOTtechbiiDOTcom / cwm-recovery-cant-mount-system-error-solution-how-to/
(sorry for the DOTs and spaces, can't post outside links yet)
CWM Recovery – Can’t Mount System Error Solution [How To]
(...)
The error is an expected one and happens generally when you are trying to backup a stock ROM using the clock work mod recovery. Please, note that you can’t do a completed nandroid backup of a stock firmwares. So, just install any custom ROM and then you can backup and restore anytime.
Click to expand...
Click to collapse
If I understood correctly, the best (only?) way to return to stock ROM is to install Odin or similar firmware flashing tool and to get the stock firmware from sites like sammobile.com and sampro.pl. However, it also says that not all firmwares might be available and I haven't looked more into it all of this yet.
Did you root your phone yet?
That should solve the problem from the can't mount system, data, etc
If you need more information, then look at this post http://forum.xda-developers.com/showthread.php?t=1397120
HerroYou said:
Did you root your phone yet?
That should solve the problem from the can't mount system, data, etc
If you need more information, then look at this post http://forum.xda-developers.com/showthread.php?t=1397120
Click to expand...
Click to collapse
Yes, I used the instructions there to root my phone and install CWM (v5.0.2.6), but that thread is 2 years old, so I'm afraid it won't be up to date in relation to certain things. For example, I did create an ext2 partition on my SD card using those instructions, but I found an easier way to move apps from my phone to the SDcard (using the link2SD app, available on Google Play). The information about ROMs is also not up to date.
If you want to install a custom rom just
-wipe data factory reset
-wipe cache partition
-advance>wipe dalvik cache
-install zip from sdcard
-reboot
NOTE: the zip is the rom
HerroYou said:
If you want to install a custom rom just
-wipe data factory reset
-wipe cache partition
-advance>wipe dalvik cache
-install zip from sdcard
-reboot
NOTE: the zip is the rom
Click to expand...
Click to collapse
Thank you.
My main concern at the moment is how to restore my original ROM if something should go wrong, though. I've found some interesting information in this thread but I've been busy this week and I'll need to go back and read it all with more attention before I try something.
Download ODIN 4.42 and GIO ops and a sotckrom MD5 file then put it into the odin and put your phone into recovery mdoe and plug it into your computer. Then click start
you have to put your phone in downloadmode to flash with odin as far as i know,but i have an other question;
can you use heimdall with the samsung galaxy gio
I am trying to flash a new recovery on my samsung galaxy gio with ODIN after it is bricked flashing tass- 6.0.4.5.zip(this cwm seems for the mini!!!) is this possible and if so,which one can?and how to do that...
thanks in advance
Yes it is possible and you need ODIN 4.42, GiPS and a Stock Rom extracted out of the zip.
Here is a video to help you because I am too lazy to explain
http://www.youtube.com/watch?v=euZqtaAMe5c

[FLASHABLE_SCRIPT][UPDATED_ERRORS FIXED] Increase system space to 1.2/2GB [15/7/2017]

-By following this you can can increase /system space from default 800MB to 1.2GB/2GB
-You can flash gapps on CM ROMs without insufficient space issue.
-You can flash regular MIUI ROMs too,without any issue.
Statutory warning
*Repartition can kill your phone forever if anything goes wrong,so proceed with caution (and make sure you have at least 30% battery)
*This process would format your internal sdcard,backup its contents
*I'm not responsible If your phone dies during this procedure under any circumstances beyond control
Prerequisites:
1)Redmi 1s partition script_system space 1.2GB.zip/2GB.zip
2)Parted
3)Twrp v3.0.2-1.zip
4)Download and copy all these files to external sdcard
Procedure:
1)Flash Twrp recovery(incase if aren't already using it).
2)Boot in to Twrp--->Advanced--->File manager--->Browse to the location of file "parted"--->Select "parted"--->Copy File--->/sbin.
3)Now using Twrp File manager browse /sbin--->parted--->select parted--->chmod 755.
4)You can also use "aroma file manager" instead of Twrp file manager for copying "parted" to "/sbin" and changing it's permissions to 755.
5)In Twrp flash "Redmi 1s partition script_system space 1.2GB.zip/2GB.zip" and wait for the script to finish execution(recovery will reboot automatically once this process finishes).
6)In Twrp--->Wipe--->Advanced wipe--->Mark in "Dalvik/ART Cache"__"Cache"__"System"__"Data"__"Internal Storage"--->Swipe to wipe.
7)Reboot recovery.
8)Install your ROM(don't flash gapps now).
9)Back again to Twrp start screen select "Wipe"-->Advanced wipe-->select/mark "System"-->press "Repair or change file system(notice that size hasn't increased to 1.2GB/2GB)-->Resize file system.
10)Back(though size of partition appears unchanged, its actually increased to 1.2GB)-->Back>select/mark"System"-->Repair or change file system-->Notice size of partition increased.
10)Back to Twrp start screen and flash gapps,that's it.
Reset to default partition:
1)I am also giving link for flashabe script file "Reset to default partition.zip" for restoring default partition sizes.
2)Boot in to Twrp--->Advanced--->File manager--->Browse to the location of file "parted"--->Select "parted"--->Copy File--->/sbin.
3)Now using Twrp File manager browse /sbin--->parted--->select parted--->chmod 755.
4)You can also use "aroma file manager" instead of Twrp file manage for copying "parted" to "/sbin" and changing it's permissions to 755.
5)In Twrp flash "Reset to default partition.zip" and wait for the script to finish execution(recovery will reboot automatically once this process finishes).
6)In Twrp--->Wipe--->Advanced wipe--->Mark in "Dalvik/ART Cache"__"Cache"__"System"__"Data"__"Internal Storage"--->Swipe to wipe.
7)Reboot recovery.
8)that's it you are back to default partition.
PS:
1.Need for "Resizing System partition"(step 9) comes only with CM14.1(haven't tried other CM versions or other custom roms) no need to do that if you are flasing MIUI ROMs(i,e you can skip step 9 if you are flashing MIUI ROMs)
2.If you still need more System space or want to further modify partition table(only if you know what you are doing),you can edit "update-binary" file inside the zip as per your needs.
Credits:
1)forumber2_ Samsung Galaxy S III.
2)slst_for his valuable input.
3)owaisnaim & fefifofum Twrp for redmi 1s.
Downloads:
1)parted:https://drive.google.com/folderview?id=0B6_hhjS3nx4IU05yLVc2Mk9uOEk
2)Repartition script Redmi 1s_1.2GB system space:https://drive.google.com/folderview?id=0B6_hhjS3nx4IRkJFZzAtMjZEa2s
3)Repartition script Redmi 1s_2GB system space:https://drive.google.com/folderview?id=0B6_hhjS3nx4IRXlDZUU1cEJ3Smc
4)Reset to default partition:https://drive.google.com/folderview?id=0B6_hhjS3nx4IeGtXb0liazdLWVk
5)TWRP 3.0.2-1.zip:https://drive.google.com/folderview?id=0B6_hhjS3nx4IdzFHXzdfNXVCYm8
good work mate
Great tutorial! Have a some questions:
1. After successfully doing this, If I decided to full clean wipe system, data, cache, dalvik cache, internal storage, and format data, the size will be reset? Do I need to do all the steps again?
2. If I decided to go back in default partition size I just flash that to reset all the steps? Or there will be a steps to reset all I've done?
Thank you.
Sent from my HM 1SW using Tapatalk
vhick said:
Great tutorial! Have a some questions:
1. After successfully doing this, If I decided to full clean wipe system, data, cache, dalvik cache, internal storage, and format data, the size will be reset? Do I need to do all the steps again?
2. If I decided to go back in default partition size I just flash that to reset all the steps? Or there will be a steps to reset all I've done?
Thank you.
Sent from my HM 1SW using Tapatalk
Click to expand...
Click to collapse
no you just have to go to
wipe >mark on system>click repartition
go back you can see system size 1.2gb
after doing this can i flash latest twrp ?
vhick said:
Great tutorial! Have a some questions:
1. After successfully doing this, If I decided to full clean wipe system, data, cache, dalvik cache, internal storage, and format data, the size will be reset? Do I need to do all the steps again?
2. If I decided to go back in default partition size I just flash that to reset all the steps? Or there will be a steps to reset all I've done?
Thank you.
Sent from my HM 1SW using Tapatalk
Click to expand...
Click to collapse
1.You can do all the wiping as usual, size of partition wil stay as it is and won't get reset,but if you're flashing current version of cm14.1 again you need to resize "System" partition before flashing gapps.
2.You additionally need to change "System" partition too to F2FS and than to EXT4(like you do with "Data" partition),in case you're going back to default partition.
I forgot to mention point 2 in OP,I will now add this there
vinayak.ghimire said:
after doing this can i flash latest twrp ?
Click to expand...
Click to collapse
Ya you can.
and whats the size of userdata and cache partition ?
vinayak.ghimire said:
and whats the size of userdata and cache partition ?
Click to expand...
Click to collapse
Based upon the scenario, the only concern is the system partition coz newer or update partition is too large. Cache partition is ok because it only use as a temp file partition. The userdata partition is large as internal storage because it shared as the same partition. That is the good thing at xiaomi phones, data partition is large as long as you have space in internal storage.
Sent from my HM 1SW using Tapatalk
vinayak.ghimire said:
and whats the size of userdata and cache partition ?
Click to expand...
Click to collapse
Install diskinfo app and check
Thanks for the script. It will help us a lot in now and in future also.
I know, i am asking too much. I bet we all are from developers but I will be very glad if you can provide me link of flashable file of TWRP and philz recovery 6.55.
Thanks Loads.
Anyone have checked this tutorial working ??
I checked this tutorial working fine. Thanks for this awesome tip. Here the flash able zip of twrp
Here is screenshot
apoorvpandey41 said:
I checked this tutorial working fine. Thanks for this awesome tip. Here the flash able zip of twrp
Click to expand...
Click to collapse
Thanks mate appreciated.
Thanks man works perfectly fine. Awesome tutorial.
Guys please help me:
Today morning I reparationed my Redmi 1s as the Op said. it went successful. after using for 5hours I've found an update from CM. So I updated using CM UPDATER APP. after reboot I've lost my Google play store and Google app (after updating to todays CM update using CM UPDATER APP). When I went to see the system partition size, it's size went back to the default 782mb (around 782mb, I don't remember exact size).
I checked whether it is disabled or what in apps. But I can't find there also. I tried Show system apps and reset app preferences, but nothing showed them.
I tried to get them back (play store and Google app) by resizing the partition to 1.2 gb (wipe>advanced wipe> Mark system>change or resize partition>back> checked system partition size whether 1.2gb or not>wipe cache and dalvik cache> reboot to system). But nothing worked.
So please help me in getting them back. Please exclude solution such as factory reset or flash gaggs again.
Is anybody else also facing the same issue or it's just me?:crying::crying::crying:
freeshared said:
1.You can do all the wiping as usual, size of partition wil stay as it is and won't get reset,but if you're flashing current version of cm14.1 again you need to resize "System" partition before flashing gapps.
2.You additionally need to change "System" partition too to F2FS and than to EXT4(like you do with "Data" partition),in case you're going back to default partition.
I forgot to mention point 2 in OP,I will now add this there
Click to expand...
Click to collapse
please give detailed instructions to get back to default partition as i am not anymore able to flash any rom on my device. Sometimes it strucks at patching system image unconditionally and sometimes shows error 7 in twrp. And not even being able flash using adb sideload. Please give detailed instructions to revert back to default partition
sharathe100111 said:
please give detailed instructions to get back to default partition as i am not anymore able to flash any rom on my device. Sometimes it strucks at patching system image unconditionally and sometimes shows error 7 in twrp. And not even being able flash using adb sideload. Please give detailed instructions to revert back to default partition
Click to expand...
Click to collapse
1)Detailed instructions for returning back to default partitions are given in op under the sub header "PPS", nothing more to add to it,just follow as it is.
2)I myself havent faced any issues till now iam currently on cm14.1 6-12-2016 version
3)Saw your posts on cm41.1 thread too,so you're on latest twrp
but still facing error 7,If possible post a screenshot of error 7(coz it never happed for me)
4)coming to the issue at hand,could you able to mount cache,system and data partitions.In twrp go to wipe>>advanced wipe>>select "cache">>Repair/change filesystem and see if everything(regarding partition size)is ok there.
Then do same for system and data too and check how are those partitions,if possible post screenshots.
Post your relpy as soon as possible.
freeshared said:
1)Detailed instructions for returning back to default partitions are given in op under the sub header "PPS", nothing more to add to it,just follow as it is.
2)I myself havent faced any issues till now iam currently on cm14.1 6-12-2016 version
3)Saw your posts on cm41.1 thread too,so you're on latest twrp
but still facing error 7,If possible post a screenshot of error 7(coz it never happed for me)
4)coming to the issue at hand,could you able to mount cache,system and data partitions.In twrp go to wipe>>advanced wipe>>select "cache">>Repair/change filesystem and see if everything(regarding partition size)is ok there.
Then do same for system and data too and check how are those partitions,if possible post screenshots.
Post your relpy as soon as possible.
Click to expand...
Click to collapse
Thank you brother for your reply. Now i am on miui as i am not being able to go to CM14 anymore. But i can flash CM11. (it seems i can use only kitkat).
Here are the screenshots: for MOUNT, ADVANCED WIPE, CACHE, SYSTEM, DATA. And problem struck on patching system image unconditionally

[APP][UTILITY] Dual Boot Patcher

Dual Boot Patcher - Dual boot any ROMs on your Galaxy Grand Prime VE
Huge thanks to @chenxiaolong for his wonderful app, bringing a new life to our device
Now let's get started!
This app patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.​
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!​
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.​
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.​
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.​
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it ​
Downloads:
[LINK] Dual Boot Patcher
[LINK] DualBootUtilities.zip
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
XDA:DevDB Information
Dual Boot Patcher, Tool/Utility for the Samsung Galaxy Grand Prime
Contributors
doesntexits, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Testing
Created 2016-12-21
Last Updated 2016-12-21
Reserved
Reserved
Whats dual boot do?
Owen007 said:
Whats dual boot do?
Click to expand...
Click to collapse
That means you can install both rom and use it both. Its like when you install another OS on top of Windows
naimrlet said:
That means you can install both rom and use it both. Its like when you install another OS on top of Windows
Click to expand...
Click to collapse
Oh ok like in windows gr8 thing. Mean I can have two os.
Owen007 said:
Oh ok like in windows gr8 thing. Mean I can have two os.
Click to expand...
Click to collapse
Like cm13 and 14.1on the same phone or touchwiz and cm
Not Working
it's a great utility bt needs fix. I tried dual booting cm13 but image verification failed when flashing the patched image then i looked up updater-script and removed code block of SHA verification. pathced zip flashed successfully this tym bt still i m not able to boot cm13. dual boot patch app says cant switch the rom then i tred dual boot utilities frm recovery but it also dnt let to continue after the device information screen is shown
d1v1n3 said:
Not Working
it's a great utility bt needs fix. I tried dual booting cm13 but image verification failed when flashing the patched image then i looked up updater-script and removed code block of SHA verification. pathced zip flashed successfully this tym bt still i m not able to boot cm13. dual boot patch app says cant switch the rom then i tred dual boot utilities frm recovery but it also dnt let to continue after the device information screen is shown
Click to expand...
Click to collapse
First, to work with CM13, you have to edit updater-script of the patched ZIP a little bit
Find any lines with "/dev/block/bootdevice/by-name/XXXX", for example:
Code:
block_image_update("/dev/block/bootdevice/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
Change "bootdevice" to "platform/sdio_emmc", like this:
Code:
block_image_update("/dev/block/platform/sdio_emmc/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
The partitions path I used before for CM13 was for recovery usage only, and DBP seems couldn't find bootdevice path from /dev/block. Also, there's no need to remove system verification from updater-script
Cheers,
working perfectly
doesntexits said:
First, to work with CM13, you have to edit updater-script of the patched ZIP a little bit
Click to expand...
Click to collapse
Thank you so much. i am happy that u have fixed this in the new update of cm13 and yes it's working now. without updating the updater-script i've another question too. there is app sharing feature bt when i try to open that it says that mbltools not enabled and ramdisk needs update. it would be so nice if app sharing can be enabled. any solution for this?
waleeds1 said:
Like cm13 and 14.1on the same phone or touchwiz and cm
Click to expand...
Click to collapse
Any rom m8
naimrlet said:
Any rom m8
Click to expand...
Click to collapse
I know mate. I was giving an example
---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------
Btw will it heavily affect the space as 8gb rom is really less with arround 3 gb left for use apps and after another rom it will be even less
Thanks for this man !
Can this work on g530h xxu,?
naimrlet said:
Any rom m8
Click to expand...
Click to collapse
Is it safe to use this with the 8.0 ROM with Los 14.1 ?
waleeds1 said:
Is it safe to use this with the 8.0 ROM with Los 14.1 ?
Click to expand...
Click to collapse
Yes, of course. I use this app for the whole time to test new Oreo builds
remilia15 said:
Yes, of course. I use this app for the whole time to test new Oreo builds
Click to expand...
Click to collapse
Thanks gonna try both of em now, Oreo and this because I was reluctant to switch from your los 14.1 to Oreo untill stable build for Oreo would have been released but now I'll try it.
remilia15 said:
Yes, of course. I use this app for the whole time to test new Oreo builds
Click to expand...
Click to collapse
Can you tell me how much system space does the ROM needs as I am running out of system partition while flashing the ROM I have applied the screen shot of how much space I have, the system size is the free storage as I will be removing that ROM. You could look it in the patcher app
waleeds1 said:
Can you tell me how much system space does the ROM needs as I am running out of system partition while flashing the ROM I have applied the screen shot of how much space I have, the system size is the free storage as I will be removing that ROM. You could look it in the patcher app
Click to expand...
Click to collapse
For convenience, better keep system partition more than 700MB free space. IMO, most of our N ROMs are more than 600MB big
Or you can install the secondary ROM on SD card or the data partition instead. DBP has that option tho
remilia15 said:
For convenience, better keep system partition more than 700MB free space. IMO, most of our N ROMs are more than 600MB big
Or you can install the secondary ROM on SD card or the data partition instead. DBP has that option tho
Click to expand...
Click to collapse
Thanks for the reply, I know it has that option but but I want it to be in system partition so that it doesn't take up other space and also to maintain stability.

Categories

Resources