Related
I'm pleased to present my repack of the stock ROM for the HTC Desire HD! READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know.
Remember that if you use this ROM, you do so entirely at your own risk!!
About MoDaCo stock ROM repacks
Unlike a MCR (MoDaCo Custom ROM) release, a stock ROM repack is as close to the stock ROM as possible. Only root / Superuser and an insecure boot image are added. The benefits of the repack are providing a rollback option in update zip format as well as providing an online kitchen to remove parts that are not required.
A MCR release of this version will follow soon!
Requirements
In order to use this ROM on your device, you must have a custom recovery image installed (Clockwork Mod).
Features
Repack of the 1.32.405.6 ROM
Pre-rooted with su and Superuser Permissions by ChainsDD
Insecure boot image (ro.secure=0)
Changelog
Please see the post below this one for the changes in each release.
Installation
To install this ROM:
Download the zip file of your choice from the links below (or the online kitchen) and copy to your SD card
Restart your device in recovery mode
PERFORM A NANDROID BACKUP FROM THE MENU
Select the option to apply an update zip, and select the zip file you copied to your memory card
Upgrading
No wipe is explicitly required in order to use this ROM (unless you are coming from a 'Sense' ROM), however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Downloads
This ROM is now available in the online kitchen! In addition to the kitchen, a prebaked download is available.
DOWNLOAD
Thanks
It's impossible to mention everyone who contributes to the Android community by name, but to everyone out there who does great work and shares it with us all - you have my gratitude and respect.
And finally...
Details on how to donate should you wish to do so are in download topic at MoDaCo.
Enjoy!
P
Changelog
17/Nov r1
Initial Release
This is the STOCK ROM kitchen, the MCR kitchen will be online tomorrow!
P
YESYESYESYES
Can't wait for the MCR kitchen to be online!
sorry for noob question but this is my first experience with android...how can i make a nandroid backup...or if there is a guide can someone give me a link??
thanks
vitodecataldo said:
sorry for noob question but this is my first experience with android...how can i make a nandroid backup...or if there is a guide can someone give me a link??
thanks
Click to expand...
Click to collapse
You can perform a nandroid backup inside the clockwork mod.
1. Boot into Recovery (power off, hold volume down button and power on, then select recovery.
2. inside clockwork go to option 'backup and restore'
3. hit backup
4. wait a bit
5. your done
ther amybe a quicker/easier way to do this but this is how i did it.
I did not get this, I want the stock ROM. And the lastest one, I have not found a stable costum rom for my usage yet. I have looked at htc.com but I were not able to find anything to download. How can I get the lastest ROM from HTC? I'm going to change the kernel, but that's it. I want a stock ROM:
OK guys, you have NO idea what it has taken to get to this point...
Welcome to the first officially supported ClockworkMod for the Epic 4G since cwm 2.5.1.0, I think it's been over a year now...
Changes since 3.1.0.1:
* Backups are tar files by default, with the filesystem type noted in the filename. Backups automatically reformat to the backup filesystem before restore. This will work to restore rfs and ext4 setups. So, for example, if you're currently on rfs, but your backup was done while on the ext4 filesystem, the restore will reformat back to ext4 before restoring. Older backups done by cwm 3.x and ACS Recovery can be restored by this ClockworkMod version, and will not reformat before restoring older backups.
* This cwm is not meant for mtd partition layout / yaffs2 filesystem, that is another matter entirely, and mtd will require it's own cwm build and kernel, that will most likely be in the official CM repo when it's done.
* One "No" in confirmations, for all but factory wipe: Make a blank file called .one_confirm (that is a period in the beginning of the name), and place it in /sdcard/clockworkmod directory. This works right now with 3 finger boot from power off, but will be added to the next Clockwork Recovery update in ROM Manager. When that happens, then it will also work from the option Reboot into Recovery, when called from ROM Manager. This is now official, so that in the future, anyone with ClockworkMod 5.0.27+ will be able to benefit from this. Thanks to chris41g for this edit and push to the official source.
* Keycodes were fixed to work with the gingerbread kernel... and menu was fixed up a bit.
up = vol up, keypad up, keypad left
down = vol down, keypad down, keypad right
back = back cap key, power button, keypad backspace key
select = home cap key, keypad enter key, camera button
toggle display = keypad d key
reboot = power button 5 times, no matter where you are in the cwm menu
NOTE ON KEYS:
If your current kernel is a froyo kernel, then the cap keys will be reversed... We will have some growing pains, until everyone is on board with gingerbread, and the kernel devs start implementing the kernel mod described below, to change the mode of reboot recovery to go to bml8 recovery partition. If you are running gingerbread, then you can flash this prerelease:
Clean_Kernel-2011-11-20-15.51.32.zip
md5:389f5b1745352326c9357c1252cd37b9
This isn't exactly finished yet, but it's stable, and has voodoo sound, root, busybox, etc.
* DO NOT REPARTITION YOUR SDCARD WITH CLOCKWORKMOD. There are problems associated with this that I will detail later.
* I highly recommend flashing both the new recovery kernel and the ROM Manager update... pretty soon, ROM Manager will be able to flash our favorite ROMs, by downloading and flashing from ROM Manager.
* FOR USERS OF ACS RECOVERY:
At this time, I recommend flashing the new cwm over ACS Recovery. Testing has shown that backups done when the ROM Manager fakeflash is called through ACS Recovery, is that the backups won't be in the proper format... they will probably work, but not in the way the CWM 5 intends it too, with fs saved tar backups.
I know that some of you are avid fans of ACS Recovery, and I have nothing against that. In fact, it should be pretty easy for chris41g to make a new version if he so desires... and, he did contribute to the official source, which is something I truly appreciate In fact, I have been working with koush, to get some other of the most requested features, into the official cwm sources, so they can benefit everyone in android. One of the first new features to be put into the next cwm update in ROM Manager, is the ability to have only one "No" in the confirmations, if the file /sdcard/clockworkmod/.one_confirm is present. chris41g authored this for the cwm sources. Also, we have been given the go ahead to implement the inclusion of reboot into download mode from the main cwm menu in the official sources as well
WHAT TO DO IN ROM MANAGER:
Firstly, flash the new recovery with odin/clockworkmod.
Also, I'd recommend a known working kernel for the new recovery:
Clean_Kernel-2011-11-20-15.51.32.zip
md5: 389f5b1745352326c9357c1252cd37b9
This isn't exactly finished yet, but it's stable, and has voodoo sound, root, busybox, etc.
Nubernel by nubecoder for gingerbread
other kernel devs feel free to link me to your posts!
Get ROM Manager from the market, and choose Flash ClockworkMod Recovery.
Choose the Samsung Epic4G.
It should then download, and you should see ClockworkMod version: 5.0.2.7
Now, whenever you use ROM Manager for anything, it will automatically load the latest supported ClockworkMod for the Epic.
DEVELOPERS: Please visit this forum thread, and learn all you need to know about getting your zips listed in ROM Manager, and the features available for you to use.
KERNEL DEVELOPERS: It is highly recommended at this time to use this commit, to change boot mode for reboot recovery to boot from bml8 recovery partition:
https://github.com/EpicCM/android_k...mmit/ea1dbf2c9be977aeb6f78d871e0b05d989bfad59
OK, here are the links:
cwm-5.0.2.7-epic4g.tar tar flash for odin
cwm-5.0.2.7-epic4g.tar mirror
md5: edd321a3aa2ba4c73f1d3612e9b19c05
cwm-5.0.2.7-epic4g.zip zip flash for cwm
md5: 869baf2d6a52b5604764f70556c9482e
TUTORIAL VIDEOS COURTESY OF QBKING77:
Flashing ClockworkMod Recovery Kernel:
http://www.youtube.com/watch?v=xuLWzeJ1lT4
Setting up ROM Manager for the Epic 4G:
http://www.youtube.com/watch?v=6KTZj3LOsxc
Thanks goes to:
koush - Creator of ClockworkMod, and very good guy for his patience and willingness to listen to the needs of the Epic community, and the android community at large.
mkasick - help with C code to support rfs formatting in the official cwm sources.
chris41g - inclusion of code in official sources to permit one "no" in confirmations, if file /sdcard/clockworkmod/.one_confirm is present
DEVELOPER NOTES:
Yes, this time there are developer notes! I will be adding more over the next couple of days.
SOURCES
ClockworkMod Binary:
https://github.com/CyanogenMod/android_bootable_recovery/tree/gingerbread
Epic4G device file sources:
https://github.com/koush/android_device_samsung_epic4g/tree/master
ClockworkMod Recovery kernel sources:
https://github.com/EpicCM/android_kernel_epic4g_gb_official/tree/cwm_5.0.2.7-rfs-ext4
I have put the branch trees in the URLs, since the masters could be subject to change in the future.
WHY CWM 5 WAS A CHALLENGE
ClockworkMod version 5 now stores the backup filesystem in the name of the tar backup files. When I first submitted my device files to koush for ROM Manager support, it became clear that now ClockworkMod would have to support the formatting of rfs volumes for the restores to work properly. This took me a while, but thankfully with the generous advice of mkasick, I wrote the function and pushed to the official source:
https://github.com/CyanogenMod/android_bootable_recovery/commit/a8f265dd6f764188d07ea2637d5638b8c64e4a6b
To experienced C programmers, this is easy stuff, but hey, admittedly, I'm a very new to C programming, and I wanted to learn... and I wanted to get it as correct as possible the first time... so this took me a while
RECOVERY KERNEL DETAILS
The important thing with a recovery kernel, is that it only needs to do one thing:
Load ClockworkMod, and anything ClockworkMod might need.
For this reason, there are minimal kernel modifications for the ClockworkMod Kernel. The following details, however, are worthy of note:
* This kernel supports kexec, as in the future, dual boot may become the norm.
* The boot mode for reboot recovery has been modified to reboot the bml8 recovery kernel, and not the boot kernel recovery.
* I left in the keypad timer patch by mkasick, since it really makes a difference in scrolling through the menus in ClockworkMod.
* The initramfs /sbin was modified to only have files needed for ClockworkMod, along with the following scripts and binaries that I often find useful:
bmlwrite - binary to flash kernels
bmlflash - script to flash boot or recovery kernels easily
bclean - script to clean all busybox files from /system
rclean - script to clean all busybox and root related files in /system
FOR BOOT KERNEL DEVELOPERS
It is highly recommended at this time to use this commit, to change boot mode for reboot recovery to boot from bml8 recovery partition:
https://github.com/EpicCM/android_ke...0b05d989bfad59
LESSONS FROM HAVING WORKED ON CLOCKWORKMOD RECOVERY
When I did ClockworkMod 3.1.0.1, I created a custom recovery, with some requested features. However, with time, it became apparent that having an official recovery with ROM Manager support was ultimately more favorable than having a custom one. Furthermore, with just a little effort and cooperation, the official source can be appended to include the most requested features. We're not the only ones asking for those features. I now believe that contributing to the official source benefits the entire community in the end, and not just one or two devices.
Along with my rfs formatting commit, I invited chris41g to contribute as well, and hence his following commit was also accepted, which allows only one "No" to appear in confirmations, when the blank file /sdcard/clockworkmod/.oneconfirm is detected:
https://github.com/CyanogenMod/andr...mmit/a8f265dd6f764188d07ea2637d5638b8c64e4a6b
Again, very simple here, but solves the most requested modification to ClockworkMod probably ever, and now, anyone with ClockworkMod 5.0.2.7+ can enjoy it too!
I really want to thank chris41g for taking the time to contribute. I respect and appreciate his work on the ACS Recovery, and I feel that his work will make even more of a difference in the end- to a lot more people than just the Epic 4G community.
I truly hope that my example can be an inspiration to others, to cooperate with other developers for the benefit of all. This may appear idealistic, but I believe the Epic 4G community has matured and has already started reaping the benefits of this cooperation. I also believe that in learning from others, you are also given the obligation to help others, who will, in turn, help others, and so on. I should hope that the benefits to all are obvious. And with that, I'll stop "preaching"... hehe.
Rockstar! Thanks are in order!
Sent from my SPH-D700 using Tapatalk
Great news!
Sent from my SPH-D700 using XDA Premium App
First page reserve. This recovery is great.
Sharing via any means i can. Gonna get Kevin to do something with our roms now
Great job! Thank you for all the hard work that you put into this!
Sent from my SPH-D700 using Tapatalk
All i can say is wow. Thanks.
Sent from my Legandary Epic or my Galaxy Tab rooted (feels naked without a ROM)
Sweeeeeet!!! Thanks Drockstar! And devs!
Could we get md5's
Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
hear the md5 from the cwm flash 869BAF2D6A52B5604764F70556C9482E
Thanks Drockstar!! Been testing it out and it works awesome!
Sent from my SPH-D700 using Tapatalk
Thanks!!! This rocks.
Sent from my SPH-D700 using XDA App
i know this is dumb but i gotta ask what color is it ?
Thank you for this. Since its official and no longer a port does this mean no more having to wipe 3x?
Sent from my SPH-D700 using Tapatalk
Digglez said:
i know this is dumb but i gotta ask what color is it ?
Click to expand...
Click to collapse
Basically Cyan/Ics blue
Sent from my Samsung Legendary 4G, a Universe UTES phone, running "two.three.five"
Digglez said:
i know this is dumb but i gotta ask what color is it ?
Click to expand...
Click to collapse
It is a cyan looking color...real easy to see/read. Me lovez it!
Sent from my SPH-D700 using xda premium
Digglez said:
i know this is dumb but i gotta ask what color is it ?
Click to expand...
Click to collapse
These are the official colors for cwm 5, pics are here:
http://forum.xda-developers.com/showthread.php?t=1354095
Eins7ein said:
Thank you for this. Since its official and no longer a port does this mean no more having to wipe 3x?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Well, honestly, wipe 3x hasn't been an issue for a while now... if you need to wipe, just do factory wipe from the main menu only once.
The version that flashes from ROM manager has one minor issue - the capacitive back button acts as a select button, but the menu key works as a back button... That's all I've noticed so far, other than the three finger salute going into my previously installed CWM 3.1...
Sent from my SPH-D700 using XDA App
styles420 said:
The version that flashes from ROM manager has one minor issue - the capacitive back button acts as a select button, but the menu key works as a back button... That's all I've noticed so far, other than the three finger salute going into my previously installed CWM 3.1...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Well the the finger boot to cwm 3 is sure as hell not right...
sent from my always aosp epic
Got plenty of "no" choices again before getting to a "yes"...that's annoying. Otherwise, pretty cool.
DRockstar said:
Reserved for developer notes
Click to expand...
Click to collapse
DRockstar ... got a question ... R U gonna make us a GB version of CleanKernel that will work with this new CWM ?
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.2.3:
-Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
-Fixed a bug with deleting a backup with a space in the name
-Added highlights on keyboard key presses
-TF101: Ignore blkid when mounting /data
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
NOTE: If you're coming from another build of TWRP, you may need to go into settings and tap reset defaults to reset the storage paths so that you can see your zip files.
BUGS:
If you have found a bug, please acquire a recovery.log - you can do this in two ways - the fastest is "adb pull /tmp/recovery.log" right after you have the issue. Alternatively in the advanced menu there's an option to copy the log to the sdcard. Also consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
We also now back up and restore boot! Yay!
Want to compile yourself?
I'm using this config: https://github.com/ViViDboarder/android_device_asus_tf101
And this kernel: https://github.com/ViViDboarder/android_kernel_TF101
And compiling against CM9 source tree
Further device specific announcements will go here
A few thanks for this specific build:
Roach2010 for helping be me test and find the mystery kernel
RaymanFX for finding a config that worked. Still not sure where he found it yet exactly
And... Dees_Troy and eyeballer for their relentless nagging
first ...
well second lol
So, third ......thanks guys, that's awesome !
thanks, been waiting for this.
great work, i've been waiting forever and finally have this on all my devices and those that I support.
I've been using the other one RaymanFX had built and both are awesome. Only 1 change other than the known issues, would be remove the "Bootloader" button under restart. But just my opinion. Thanks Again.
gdeeble said:
I've been using the other one RaymanFX had built and both are awesome. Only 1 change other than the known issues, would be remove the "Bootloader" button under restart. But just my opinion. Thanks Again.
Click to expand...
Click to collapse
Good note. That's a theme issue then. I can build a new theme zip or something later. Working on releasing the much delayed Nexus One build.
EDIT: I've been informed by Dees_Troy that we have build flags to do just this. So I'm adding them to my configs so the next build should have them removified.
It's worth pointing out that this build of TWRP has a recompiled kernel with boot and recovery exposed. You can finally back up boot and restore it.
GooManager keeps hanging at Looking for recoveries after trying to install OpenRecoveryScript. Unable to retrieve files...
Finally recovery on a touch screen device the way it should be! Thanks guys!
Sent from my SGH-I747 using Tapatalk 2
I thought I would give this a try and went to the TWRP page link as instructed. Followed the instructions to download the open recovery through goo manager, which it did and it rebooted my tablet and all looked good. I then tried to reboot to recovery from Team EOS3 Power menu. The usual TWRP blue curtain was there and when it raised, I saw the text at the bottom that my /data partition was being formatted without formatting /data/media and the tablet rebooted, without ever getting to the TWRP recovery menu and I'm now back at the initial Google setup screen. Guess I should have made a fresh Titanium backup first. A warning would have been nice, or is this a bug?
Strange. But I copped the blob from twrp site as "not recommended" suposedly. Ran the command in terminal cuz I don't Fux with goo manager... Everything worked fine. No issues
~Poisoned Viper4g LTEvOne by TeamVenom, Lionheart Cranked to 1.72Jigawats Deadline: Ca1ned.
MassStash said:
Strange. But I copped the blob from twrp site as "not recommended" suposedly. Ran the command in terminal cuz I don't Fux with goo manager... Everything worked fine. No issues
~Poisoned Viper4g LTEvOne by TeamVenom, Lionheart Cranked to 1.72Jigawats Deadline: Ca1ned.
Click to expand...
Click to collapse
Since it's installed now and it wiped my data without asking, I'm going to clear things out and reflash everything. I will test if it tries to wipe my data again after I reinstall a few apps.
sidneyk said:
Since it's installed now and it wiped my data without asking, I'm going to clear things out and reflash everything. I will test if it tries to wipe my data again after I reinstall a few apps.
Click to expand...
Click to collapse
Weird. It didn't wipe my data. Just installed nicely as per instructions.
running great with no issues I used goo manager app but i flashed it through the flash roms selection on the main menu not the 3-dot menu install open recovery script selection.
sidneyk said:
I thought I would give this a try and went to the TWRP page link as instructed. Followed the instructions to download the open recovery through goo manager, which it did and it rebooted my tablet and all looked good. I then tried to reboot to recovery from Team EOS3 Power menu. The usual TWRP blue curtain was there and when it raised, I saw the text at the bottom that my /data partition was being formatted without formatting /data/media and the tablet rebooted, without ever getting to the TWRP recovery menu and I'm now back at the initial Google setup screen. Guess I should have made a fresh Titanium backup first. A warning would have been nice, or is this a bug?
Click to expand...
Click to collapse
Did you ever try to use goo manager with the old unofficial version?
Sent from my HTC One S using xda premium
ViViDboarder said:
Did you ever try to use goo manager with the old unofficial version?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
No, I was using RaymanFX's TWRP build prior to this and before that Team Rogue Touch and before that Roach's CWM build, all flashed from within recovery. I only did the GooManager thing because that was the recommended method. Subsequent boots to recovery did not reproduce the data wipe and after reflashing my ROM and restoring my apps, I went into recovery without a hitch. It was only after installing this one through GooManager per the instructions. It downloaded, rebooted and flashed and rebooted back to Android (Team EOS3 JB #57). After a few minutes I rebooted to recovery from the Power menu in EOS3 and as soon as the blue curtain raised it was wiping my data partition - /data/media. Of course, I didn't expect that and didn't get any chance to stop it. I know I read somewhere before that open recovery wasn't working on the TF101, but since this was new and it was recommended to use open recovery, I just assumed that meant it was now working. Oh well, all is well now.
never mind i figured it out, open recovery only works with internal for now.(it may be because TWRP-2.2.1.4 is mounting the micro SD as /sdc instead of /storage/sdcard0) I moved the goomanager folder to /data/media updated the download folder location in the goomanager app settings to /data/media/goomanager re-ran flash roms from the goomanager apps made my selections and order to flash and selected wipe Cache and Dalvik and it ran just fine, it rebooted to recovery, flashed all the zips(including my mods) in the proper order and booted back up with no issues.
Running EOS3-N58 at this time.
Dam sweet once i figured it out!
Great job!
Thanks
cbrox said:
never mind i figured it out, open recovery only works with internal for now.(it may be because TWRP-2.2.1.4 is mounting the micro SD as /sdc instead of /storage/sdcard0) I moved the goomanager folder to /data/media updated the download folder location in the goomanager app settings to /data/media/goomanager re-ran flash roms from the goomanager apps made my selections and order to flash and selected wipe Cache and Dalvik and it ran just fine, it rebooted to recovery, flashed all the zips(including my mods) in the proper order and booted back up with no issues.
Running EOS3-N58 at this time.
Dam sweet once i figured it out!
Great job!
Thanks
Click to expand...
Click to collapse
I had already flashed EOS3-N58, but had changed some files experimenting with getting Polaris Office to work and gave up. So, I followed your suggestion and moved a few other files that I normally flash along with the ROM and it worked like a charm. Pretty nifty. I setup the order to flash for EOS3-N58, gapps, Guevor kernel, nVidia codecs, iobusy, and DSP Manager along with the preliminary cache and Dalvik cache wipes and it just worked like you say. Thanks. I hadn't tried that feature yet, mostly because until now I thought it might break something since I had read that open scripting wasn't working yet for TF101 somewhere. I can say now, with this recovery and your change to the download folder, that it is working and working well. You just have to have whatever files you want to flash in that folder (or maybe just somewhere in /data/media) and you're good to go.
Hi, if you are looking here, chances are you know what HypnoToad is - a modded KitKat CM for the Relay 4G:
http://forum.xda-developers.com/showthread.php?t=2528752
I am compiling here some of the questions I kept asking the devs and whose answers are scattered in the above (long) thread.
1-You WILL need the latest CWM. Since the download is in img format, you probably need to use a PC to install it. I found that the easiest was to use the free CWM app from the play store and update from CM.
2-HypnoToad is dirty-flashable over cm10.2.x stable. If you have it running, just reboot to your updated CWM (see above) and flash the latest zip ON TOP of your CM install, no need to wipe the phone (that is probably better, but if you want to keep your setup you can dirty flash).
3-You DO need to flash the new gapps for KitKat too
Please feel free to correct me, add new FAQs, etc.
AND THANKS TO THE DEVS!
Guiyoforward said:
Hi, if you are looking here, chances are you know what HypnoToad is - a modded KitKat CM for the Relay 4G:
http://forum.xda-developers.com/showthread.php?t=2528752
I am compiling here some of the questions I kept asking the devs and whose answers are scattered in the above (long) thread.
1-You WILL need the latest CWM. Since the download is in img format, you probably need to use a PC to install it. I found that the easiest was to use the free CWM app from the play store and update from CM.
2-HypnoToad is dirty-flashable over cm10.2.x stable. If you have it running, just reboot to your updated CWM (see above) and flash the latest zip ON TOP of your CM install, no need to wipe the phone (that is probably better, but if you want to keep your setup you can dirty flash).
3-You DO need to flash the new gapps for KitKat too
Please feel free to correct me, add new FAQs, etc.
AND THANKS TO THE DEVS!
Click to expand...
Click to collapse
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexq_recovery-10.2-347.zip
Is also a fully supported (by TeamApexQ) version of CWM for the relay, in an update.zip form.
This recovery is better (cmw based) and more up to date (also zip):
http://forum.xda-developers.com/showthread.php?t=2588646
[Guide] Multi Boot Note 3 (Updated 24/07/2015)
*** Hi Guys i no longer have a note 3 so i cant do any testing but our team member is here to give support for you all and even im here to give support except testing. please contact @[email protected] and @djnim for support.***
I am using this on SM-N9005 Snapdragon Variant of the Note 3; I believe this will work with other Note 3 Variants as well. Few of them are already tested and you can find them below. Others who have different variants which are not tested can try this and update us, and we will be here to help you out if you are ready to try this out.
@chenxiaolong is the one who made this happen to our beloved Note 3
Main advantage of this is you can try any new rom with out loosing or having any kind of trouble with your existing rom. This mod will not change anything in your primary rom, so any time you can go back to your normal state.
Disclaimer
1.I am not responsible for bricked devices, dead SD cards,etc.
2.Before going further! YOU are choosing to make these modifications.
supported Devices: ( Tested and confirmed working)
SM-N9005 (International Qualcomm): hlte (Tested by me )
SM-N900T (T-Mobile US): hltetmo (Tested by @MistaEast ) confirmation post
SM-N900R4 (US Cellular): hlteusc (Tested by @harshal10398 ) confirmation post
SM-N900 (International Exynos): ha3g (Tested by @mohnishkat ) confirmation post
SM-N900P (Sprint): hltespr (Tested by @lord dredd ) confirmation post
SM-N900K(Korean): (Tested by @Premananda_laishram) confirmation post
Requirements
* Read the full guide before Starting.
* Backup your phone if you are doing this first time. (Full Nandroid backup recommended for the new comers and it’s also recommended to others who don’t know what they are doing exactly even if they have multi booted several times)
* Rooted Note 3 with custom recovery (preferred TWRP or philz).
* free space in your internal SD (for example a Cm based roms take up to 2.5GB to 3.5GB and a TW roms take up to 5GB or more.)
* If you face any trouble please read the FAQ before doing something or asking for help. And if you want help please provide as much as details(device, roms, etc.) you can.
*
Instruction:
1.Download your desired Rom which you want to use for multi booting and the mods, addons, gapps, Kernel etc for the same. Keep the files in your internal memory.
2. Download the most recent snapshot release of Dual Boot Patcher and install it on your Note 3.
3. Open Dual Boot Patcher and grant SU permission. Then go to ROMS and you will see your Primary rom, press the 3dotmenu key and click "set kernel". If it fail to set kernal please read the FAQ.
4. Then In Dual Boot Patcher go to Patch Zip File and Choose hlte for snapdragon variant and ha3g for Exynos veriant (Samsung Galaxy Note 3) from the drop down menu.
5. In the second drop down menu select "Data Slot".
6. Below that you have to enter the ID of the secondary rom.(Example 1, 2, 3, etc. - it will take it as /data/multiboot/data-slot-1)
7.Now tap on the below button to choose the ROM's, Gapps, Kernel and mods to patch them and make them perfect for Multi booting.
8. Always remember to keep same slot ID for the Gapps, kernels and mods same as the rom. (Example: if you want to flash the gapps/kernel to the data-slot-1 rom then you have to select the same ID that’s 1 or if you want to flash the gapps/kernel to the data-slot-2 rom then you have to select the same ID that’s 2.)
9. When selecting the files except cm rom zip there will be a “preset” drop down menu, from that you have to select according to the file you are going to patch. (Examp: for roms, kernels, mods, addons – custom; for gapps – Google_Apps; for Su zip – other/SuperSu; For xposed-Other/Xposed)
10. Now press the tap to begin patching button to patch the file. And you will get a new patched zip file in the same location.
11. Now Boot into custom recovery and flash the new patched file and reboot.
12. And your device will boot into New Rom.
13.Install the Dual Boot Patcher app and set the kernel for your second ROM as well.
14. To switch between roms
•Open Dual Boot Patcher app/roms and click on primary or secondary rom as you like and reboot.
•Or Use Swap Roms to switch between Roms.
* Important things to keep in mind: while installing a rom or mod with Aroma installer don't reboot directly from the aroma.
You have to always uncheck the last option to reboot in aroma and click finish. So it can finish the final steps for multi booting.
And if you miss that it will only reboot to recovery. To boot back you have to flash your primary rom kernel or re-flash the patched rom.
Never update a secondary rom through OTA Update.
*. For other devices:
1. You have to download and install X-plore File Manager (which I am using) from play store.
2. Open X-plore File Manager from app drawer and navigate to the patched zip file and open it.
3. Now you will see a folder named multiboot inside that you will find info.prop, now open info.prop with the text editor which comes with the x-plore file manager.
• And then find and change mbtool.installer.ignore-codename=false to mbtool.installer.ignore-codename=true
Revert
To revert back or if you face any problem just flash my Multi Boot cleaner.zip which will wipe all the installation files from \system and restore the primary rom kernel.
As a backup keep a copy of your kernel flashable zip file.
FAQ
1. I can't set the primary rom kernel in xyz rom. And I can’t switch to other rom in primary rom.
Ans. Just download the set kernel fix as per your model and flash it in the recovery.
The above fix only work for primary rom. If you have trouble with any other roms just add ro.patcher.device=hlte(for other models add your model instead of hlte) to the bottom of build.prop of that rom and you are good to go.
If you don’t know how to do that just pm me and I will make a flash able zip to add it to your secondary rom.
if the above didnt work Read this post please
2. App sharing?
Ans. Until now no luck. (Still under testing)
3. This rom can’t be patched.
Ans. some roms are not supported its known, if the Dev have time may be he will consider including them.
Also read this
Credits/ Thanks:
@chenxiaolong
Original Thread: http://forum.xda-developers.com/showpost.php?p=45659284
Don't forget to thank him and if you can please consider a small donation for him because he really deserve it.
@aukhan & Team Emotroid
His Thread (Where I got the idea and help to make this guide): http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
@rlorange for the help and support.
His thread for Dual boot backup and restore app. http://forum.xda-developers.com/showthread.php?t=2491299, http://forum.xda-developers.com/not...-4-15-multi-boot-backup-restore-v1-0-t3087187
@AholicCert for helping me with some scripts
@ other XDAmembers
Video Guide
https://www.youtube.com/watch?v=upeSC65t5XQ
Going to try it mate tnx
a_prabhu7 said:
Going to try it mate tnx
Click to expand...
Click to collapse
Welcome try it and let us know.
Sent from my SM-N9005 using XDA Free mobile app
Has anyone tried this out on N900????
thetitanium said:
Has anyone tried this out on N900????
Click to expand...
Click to collapse
Try it your self and let us know. i will promise you that it will not touch your primary rom. Any time you can go back to normal.
54NJ41 said:
Try it your self and let us know. i will promise you that it will not touch your primary rom. Any time you can go back to normal.
Click to expand...
Click to collapse
tried on my 4.4.4 vn rom-set kernel-failed to set kernel..
vagenrider said:
tried on my 4.4.4 vn rom-set kernel-failed to set kernel..
Click to expand...
Click to collapse
1. First of all have you grant super user permission for Dual Boot Patcher. If not just reboot and try again.
2. Do you have enough space in your sdcard (internal) for the backup of the kernel.
3. Just check if there is sdcard/multiboot/primary/boot.img is their.
4. Try the 8.0.0.r1119.g9c51715 version of dual boot patcher if the above didn’t help.
54NJ41 said:
1. First of all have you grant super user permission for Dual Boot Patcher. If not just reboot and try again.
2. Do you have enough space in your sdcard (internal) for the backup of the kernel.
3. Just check if there is sdcard/multiboot/primary/boot.img is their.
4. Try the 8.0.0.r1119.g9c51715 version of dual boot patcher if the above didn’t help.
Click to expand...
Click to collapse
tried all mate but nothing..
vagenrider said:
tried all mate but nothing..
Click to expand...
Click to collapse
Hi bro can you please send me the link to the rom which you are using. I will try and let you know.
54NJ41 said:
Hi bro can you please send me the link to the rom which you are using. I will try and let you know.
Click to expand...
Click to collapse
here you go http://samsungviet.vn/threads/note-3-snapdragon-vn-team-vn-rom-v7-0-online.1034/
apreciate very much your time-effort etc thank you
vagenrider said:
here you go http://samsungviet.vn/threads/note-3-snapdragon-vn-team-vn-rom-v7-0-online.1034/
apreciate very much your time-effort etc thank you
Click to expand...
Click to collapse
Which version 7.2 or other
54NJ41 said:
Which version 7.2 or other
Click to expand...
Click to collapse
7.2
Here we go! I have complete dual Boot on my Note 3! It's awesome! My first Rom is Aryamod 5.3 and my Second Rom is temasek unoffical cm rom! Thanks to the Developers for your great Roms! And now Thanks to you 54NJ41! Your tutorial is great! I wait over 1 year for dual Boot on my Note 3 and now I have it!
does anyone knows how i could get more system partition space?
I tried to use titanium backup to move some apps but it says my system is 2.38gb full
Rogers Note 3
Anyone can tell me if I can install it for the Canadian Rogers Galaxy Note 3 ?
Thank you
you said:
Download and keep your desired (Secondary Rom) CM or AOSP rom + Gapps zip files
the second must be CM or AOSP?
what about if i want to use Arya and Omega roms for example?
vagenrider said:
7.2
Click to expand...
Click to collapse
I have tried the rom but same result as yours. But don’t worry I have an alternative way to set the kernel for your primary rom.
First make folders in your SDCard, “MultiBoot” in it “Primary” it should be like: Sdcard/MultiBoot/Primary
Then extract the boot.img from your rom zip and copy it to Sdcard/MultiBoot/Primary
So the result will be Sdcard/MultiBoot/Primary/boot.img
It’s done.
NightForce said:
Here we go! I have complete dual Boot on my Note 3! It's awesome! My first Rom is Aryamod 5.3 and my Second Rom is temasek unoffical cm rom! Thanks to the Developers for your great Roms! And now Thanks to you 54NJ41! Your tutorial is great! I wait over 1 year for dual Boot on my Note 3 and now I have it!
Click to expand...
Click to collapse
Welcome bro
dream_catcher79 said:
does anyone knows how i could get more system partition space?
I tried to use titanium backup to move some apps but it says my system is 2.38gb full
Click to expand...
Click to collapse
To make space in your system partition.
1. Delete what ever apps you are not using from system/app and syatem/priv-app (Don’t delete if you don’t know what it is or what your are doing.)
Example: shealth, etc.
2. Move some google apps from /system/app to /data/app to make them user app using root explorer.
Example: maps, gmail, chrome, etc.
thermax04 said:
you said:
Download and keep your desired (Secondary Rom) CM or AOSP rom + Gapps zip files
the second must be CM or AOSP?
what about if i want to use Arya and Omega roms for example?
Click to expand...
Click to collapse
To dual boot two TW roms is very hard. Because there is not enough space to fit both system file in your system partition. Other wise you have to deboalt the primary rom and you have to deboalt secondary rom zip before flashing. And by doing so you will lose most of the features of your TW roms.
And if you want to use CM as primary and TW rom as secondary its possible but not recommended. Because you will have trouble with flashing mods etc for your TW rom.
The better option at the moment is to keep the TW rom as Primary and others a secondary.