Related
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
You can find all the features and info here: http://goo.gl/B0qqW
===========Gingerbread GT-S5660M Stock Recovery===========
These are the things I changed:
Code:
default.prop (lifted security)
=======================
Changelog:
Code:
March.1.12 ~ Added Odin file
[B]===================[/B]
Feb.27.12 ~Major Update!
• Fixed All Recoveries's update-binary
• Added Phiexz and Maclaw Roms compatible Recoveries [B](Only Flash if you are flashing their ROMS)[/B]
• My Recoveries named: [B](My Roms)[/B] are only compatible with [B]My Roms![/B]
[B]===========================[/B]
Feb.26.12 ~[B]Added CWM 5.0.2.6[/B]
Feb.26.12 ~Corrected CWM 5.0.2.7's [B]updater-script[/B]
Feb.23.12 ~[B]More Stable![/B]
Feb.12.12 ~Initial Release[/FONT][/SIZE]
Thanks to Darkshado for always giving me tips!
Thanks to Phiexz's for his hard work! (CWM credit to him)
(Phiexz & Maclaw Roms) ClockWorkMod Recovery Modded GIO.RLE ONLY:
px-CWM-v2.zip
ClockWorkMod 5.0.2.7 ext+rfs (Phiexz)
ClockWorkMod 5.0.2.6 No EXT Support (MORE STABLE THAN 5.0.2.7) (Hyriand)
(My Roms) ClockWorkMod Recovery Modded GIO.RLE & Build.prop ONLY:
ClockWorkMod 5.0.2.7 ext+rfs (Phiexz)
[ODIN]ClockWorkMod 5.0.2.7 ext+rfs [ODIN] (Phiexz)
ClockWorkMod 5.0.2.6 No EXT Support (MORE STABLE THAN 5.0.2.7) (Hyriand)
Stock Recovery
GT-S5660MUGKG3 Stock Recovery (Samsung and I )
READ READ READ:
Not every Installable zip can handle mount system, data & cache.
so you should mount it manually before flash them. mount menu can found on: Mount & Storage Menu
EXT4 FORMATTER (S5660M Mod) (Phiexz)
Galaxy Gio ext4 converter (Darkshado)
*Tested and working on my own Canada phone!
*All zips are signed*
can you help me about building a cwm recovery for i569？
Sent from my GT-S5660
Well for sure you need Linux. You also need a lot of space on your Drive.
Is it for Stock or Custom Rom (Like CM7)
Try checking this out: Build a custom kernel and [HOWTO] Build custom kernel, libraries and applications on your own
Make sure you're using the right/recommended toolchain but if you pulled directly from the AOSP repo then i guess that's not your problem.
thank you for cwm recovery for 5660m but when I try to clear dalvik cache it reset back to home screen
Peteragent5 said:
Well for sure you need Linux. You also need a lot of space on your Drive.
Is it for Stock or Custom Rom (Like CM7)
Try checking this out: Build a custom kernel and [HOWTO] Build custom kernel, libraries and applications on your own
Make sure you're using the right/recommended toolchain but if you pulled directly from the AOSP repo then i guess that's not your problem.
Click to expand...
Click to collapse
thank you my friend,i will learn it later！
Sent from my GT-S5660
zman4753 said:
thank you for cwm recovery for 5660m but when I try to clear dalvik cache it reset back to home screen
Click to expand...
Click to collapse
That means the Dalvik Cache is cleared even though it doesn't show it
Trust me.
Peteragent5
This customization is much appreciated however I still have two bugs:
1- I can’t mount the sd-ext (I’m using ext2 partition for link2sd); everything else were mounted correctly (cache, system, data and SD )
2- In the last step of backup I had an error when trying to generate the md5 sum (error while generating md5 sum!)
Any thoughts?
Thanks
-----------------------
Darkshado’s great Rom Already installed (ArpegGioMod ROM v0.8) on S5660M
1- Weird.. Try checking the original post and ask for help there or search your problem there
2- Did you try backing up just once or multiple times? Try backing up more than once. I had same problem even without my mods. But i tried what I said above and it works. If it still doesn't work ask in the original thread also and/or search on google
Peteragent5 said:
1- Weird.. Try checking the original post and ask for help there or search your problem there
2- Did you try backing up just once or multiple times? Try backing up more than once. I had same problem even without my mods. But i tried what I said above and it works. If it still doesn't work ask in the original thread also and/or search on google
Click to expand...
Click to collapse
Thank you for the quick response:
1- It's what I did but don't get any response yet.
2- I tried backup for multiple times but bug in the same step md5
Thanks
All right it seems like there's some Bugs with this modded cwm. I'll try to find the problem and fix it Thanks for posting bug
EDIT~
It seems when I Backup on my own phone (without any fix yet), it seems to work!? Keep in mind I also have no SD EXT.
Updated to much stable Recovery
Peteragent5 said:
Updated to much stable Recovery
Click to expand...
Click to collapse
The file on mediafire has the same name... Is this the updated one? Thanks.
koodiifin said:
The file on mediafire has the same name... Is this the updated one? Thanks.
Click to expand...
Click to collapse
Yes it is. Too lazy to rename
Changed file name.
mobilis2009 said:
Peteragent5
This customization is much appreciated however I still have two bugs:
1- I can’t mount the sd-ext (I’m using ext2 partition for link2sd); everything else were mounted correctly (cache, system, data and SD )
2- In the last step of backup I had an error when trying to generate the md5 sum (error while generating md5 sum!)
Any thoughts?
Thanks
-----------------------
Darkshado’s great Rom Already installed (ArpegGioMod ROM v0.8) on S5660M
Click to expand...
Click to collapse
Peteragent5,
I just tested Nandroid backup with your CWM and ArpegGioMod 0.8 and I also get "error while generating md5 sum!". I tried it multiple times.
You mentioned that it works on your phone, but were you testing it with an EXT4 base system or RFS?
Nandroid backup with your CWM on a Ext4 system worked fine for me, but not RFS.
koodiifin said:
Peteragent5,
I just tested Nandroid backup with your CWM and ArpegGioMod 0.8 and I also get "error while generating md5 sum!". I tried it multiple times.
You mentioned that it works on your phone, but were you testing it with an EXT4 base system or RFS?
Nandroid backup with your CWM on a Ext4 system worked fine for me, but not RFS.
Click to expand...
Click to collapse
I actually was testing on RFS lol
My backups work fine?
S5660=S5660M ?
[Sent to the mobile device Gio]
[aOS 2.3.7/CM7.2-RC2-B4 patch1]
Update again! View change log!
Change Log & Original Post
m.ali.ozkaya said:
S5660=S5660M ?
[Sent to the mobile device Gio]
[aOS 2.3.7/CM7.2-RC2-B4 patch1]
Click to expand...
Click to collapse
S5660!=S5660M
Use the search function, it's well documented you oafish troll.
I have a problem, and I'm dealing with it since this saturday. I really need my phone this evening so I really want help. My phone has since saturday a bootloop with every rom. Today I found out that it could have something in common with a error in the recoveryscreen which says it can't mount /data. CWM and the stock recovery both have this problem. Can please anyone help me? I'm really confused, because I have tried everything.
//I've discovered that the problem is that the /data partition is crashed. Is is possible to recreate the internal partition table?
install a stock rom then re-install cwm 5.0.2.7
Msulviu said:
install a stock rom then re-install cwm 5.0.2.7
Click to expand...
Click to collapse
I have done that already a few times.
Try flashing an ext4 converter, or re dd'ing an empty RFS format partition into place.
Already done. When I try to use ext4formatter in CWM it doesn't give an error, but when I try to do the data reset I will get an error again because it can't mount (and unmount) /data.
//And how do you add a RFS partition on the phone? Or do you mean on the SD?
Factory reset?
Have you tried doing a factory reset with Kies?
be_born said:
Have you tried doing a factory reset with Kies?
Click to expand...
Click to collapse
Thank you for trying to help, but your answer is stupid. It's impossible to go to Kies without a (working) rom...
I think I just found something interesting to know. I tried again to install Cyanogenmod 7.2 (ported by Phiexz) and in the Aroma installer I looked at the System Info. Almost everything looks fine, but this is not good I think:
Data Size : -1MB
Free : -1MB
(/mnt/sdcard) : -1MB
Free : -1MB
Click to expand...
Click to collapse
Are those partitions crashed? And how do I resize or reformat them back?
Which ext4 converter did you use?
Phiexz's if I remember correctly, uses the formatting tools included in the recovery. Mine has its own, separate binaries.
To reflash an RFS partition into place, you could use the dd command (carefully). Here's an empty RFS formated /data partition.
Or reflash back to the stock recovery and use that to format the partitions back to RFS.
Extract to your SD card and use the following command:
dd if=/sdcard/data.rfs of=/dev/block/stl13 bs=4096
Good luck,
Darkshado
Darkshado said:
Which ext4 converter did you use?
Phiexz's if I remember correctly, uses the formatting tools included in the recovery. Mine has its own, separate binaries.
To reflash an RFS partition into place, you could use the dd command (carefully). Here's an empty RFS formated /data partition.
Extract to your SD card and use the following command:
dd if=/sdcard/data.rfs of=/dev/block/stl13 bs=4096
Good luck,
Darkshado
Click to expand...
Click to collapse
I did use Phiexz's first yes. But I can't install yours. And where do I have to use dd commands? :$
What do you mean by "can't install mine"? Is there an error message or you're not sure how to do it?
If so, just apply it from the SD card like any other update.
The dd command has to be input through ADB shell while in recovery. So get ADB working if you haven't already.
Darkshado said:
What do you mean by "can't install mine"? Is there an error message or you're not sure how to do it?
If so, just apply it from the SD card like any other update.
The dd command has to be input through ADB shell while in recovery. So get ADB working if you haven't already.
Click to expand...
Click to collapse
I did know how to install a zip, but I tried 2 times and I think both were a bad download. Now I'm installing your Ext4 Converter.
// YOUR EXT4 CONVERTER WORKED!!! After a week without a phone it finally worked! Thank you so much!
Glad to hear that!
I had a similar problem of being unable to mount /system after installing a CM9 beta (can't remember which) and ended up solving it like that.
Hey guys i have a question relating to this dscussion. I have my gio running CM9 and i recently used BML5 to find my phone's unlock code. I have a nandroid backup of Rooted stock ROM, and when i tried to flash back to it, it said "Could format dev/block/stl13". I have the CWM 5.0.2.7 with RFS and EXT4 support, so it should work. What is the problem?
That's the thing; the exact behavior of those RFS+ext4 CWM builds when changing from one type to the other hasn't been very well documented.
I'm not sure they can format back to RFS properly.
You could always try that empty RFS partition set and attempt a restore afterwards.
What can i do if dd says, that it can't open '/dev/block/stl13': Invalid argument? I placed the data.rfs to the root directory of sdcard. Am I doing something wrong?
Can't mount /data
Hello, I have a bricked phone, and no idea why, and so far I'm unable to fix it. I've been waiting for an RMA so I can send it back to GSM Nation to evaluate and hopefully fix. My problem started when Samsung support told me to do a factory reset of my Samsung Galaxy S3, and it rebooted, then said it could not find or mount /data or anything therein. I have Not, repeat NOT, rooted my phone, it had the stock Android 4.3 OS and updates from T-mobile. The tech at the Samsung Experience Shop in the Best Buy store could not reflash it, when Kies tries to talk to the phone in Side Load mode it freezes or something, nothing happens. I downloaded ODIN 3 on Dad's win XP laptop, and in ODIN download mode the computer sees it as a new device with no driver to make it talk to it, and the drivers I've downloaded simply will not install. The installers die as soon as they run having done nothing. I am using my Samsung Chromebook to write this and have no Linux machine to work with. I am at a loss. Can you help me? Maybe I could re-install android using a microSD card?
I have the solution for data partition crash or any other partition
please do it with your responsibility but your phone is alreay bricked so it doesn't matter
hi every one i 've been through this problem for a long time and just yesterday hamdo lilah i discovered the solution it is by repartitioning your partitions with a pit file . i tried this method with samsung galaxy fit and it works even the pit file is for samsung .all you have to do is open odin included in the package then select pit file included then click start and there you go 'even if it doesn't show PASS ' after that just flash a stock rom ' or maybe any rom ' and that's it you are ready to go . i uploded the package on gulfup cause i have no account in mediafire enjoy if you face any problem just contact me or add a replay
gulfup.com/?rP8hfs
This thread should clarify the methods you can use to enable dual-boot functionality along with common problems and solutions. Hopefully, the list of questions should help. The initial author of this important thread was RichMD. He has kindly asked me to maintain it further instead of him, as he is too busy for that in the moment. I have accepted it and I do it as of February, 2014. Although I'm an active user of dual boot since I own my N7100, I don't consider myself to be a guru for this and I will highly appreciate any cooperative posts and I will try to add the important information and frequently update this OP.
IMPORTANT: particulary new users, please read especially careful here and mind, as the features of Devil Dual Boot Recovery have been strongly changed between the updates! I have kept first two parts of this OP the way RichMD has written them. So all the information are regarding pre-F2FS recovery versions (until v6.0.4.4). My screenshots also show only UI of the 6.0.4.4 version. From part 3 onwards, th einformation are regarding entirely newer recovery and kernel versions with F2FS support.
LIST OF CONTENTS:
About Devil dual boot recovery
Part 1: FAQs: dual-boot general
Part 2: GUIDE: setup dual-boot
Part 3: FAQs: benefits of F2FS
Part 4: GUIDE: migrate from ext4 to F2FS
Part 5: bootloader info & download links
Click to expand...
Click to collapse
About Devil Dual Boot Recovery
A luxory version of CWM based recovery with touch UI
Each choice must be clicked twice by touch navigation (to avoid accidental touch)
Navigation can be done by swiping with finger up or down beyond the menu contents
The navigation bar on the bottom works identic like with PhilZ recovery
SCREENSHOTS: (v6.0.4.4, the last pre-F2FS version)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
1: FAQs / dual-boot general
Q.) Can I run all 4.3 and 4.4 AOSP and Touchwiz based ROMs with devil2 dual-boot kernel?
A.) All AOSP ROMs between 4.3 and 4.4.2 will work, but ATM only 4.3 TW based ROMs will boot, 4.4 isn't yet supported.
Q.) Why do I keep getting "Something went wrong..." when trying to install a ROM.
A.) Some people have had this problem when trying to install from the external SD card and the error does not happen after the zip is moved to the SD card. There are additional reasons for that error that I listed below.
Q.) I am having ... problem with the secondary ROM (Play Store FC, no SD card access, no MTP, it fails to install and affects the primary ROM, etc)
A.) 4.2 ROMs do not typically install properly to the secondary partition currently. Additionally, 4.1 roms have a problem with MTP frequently or AROMA roms will fail the ROM to secondary install-script-modification step . Instead, install your desired ROM to primary, boot with the kernel included in the ROM and ensure everything works including MTP. Then flash the dual-boot kernel. Then back it up and wipe the secondary partition. Then restore your backup to the secondary.
Note: DerTeufel has fixed the problem of internal SD card access for 4.2 ROMs for N-7105 (LTE) based phones but N-7100 phones still have the problem. It is being worked on.
Workaround if you can't access the phone via USB
You can load and use easy UMS one time. You will have access to the external SD. Simply reboot and then set the app back to the default MTP mode and both should be accessible. You don't need the app after that. - (https://play.google.com/store/apps/details?id=com.mohammadag.samsungusbmassstorageenabler) and you shouldn't need it anymore.
Q.) Can I revert back to a configuration without dual-boot and how do you do it?
A.) Yes. Use a file manager with root access on the primary ROM to delete the /data/media/.secondrom folder which contains the 1.5GB file and the data folder. Flash another recovery (CWM or TWRP) and flash as you normally would.
Q.) I can't seem to get my nandroid to restore to the secondary partition. What am I doing wrong?
A.) One possible problem is that the secondary /system partition is sized at 1.5GB (recent F2FS kernel version enlarged secondaryFS to 1.9GB). If your nandroid backup has over this amount in /system then it won't work. One possible solution is if you use Titanium Backup (or similar backup program) to do a full backup of apps AND system info. Although it is often written not to restore system info, it is OK if it to the same exact ROM and version. You could then factory reset to wipe it clean, do a nandroid backup and then restore that to secondary. Then install TB and restore selectively only the apps you want. I would probably suggest restoring "missing apps + all system data" but then deselect most of the apps that aren't really necessary. Once that is complete and the configuration is working, you could selectively restore other missing apps and data on a priority basis until you start running low on /system space. TB will show that at the bottom of the initial screen.
Q.) I tried a fresh install to the secondary partition and it completed successfully but now when I boot the primary ROM, I have what I meant to install to the secondary partition. What's wrong?
A.) This will happen if you choose "ZIP to secondary rather than ROM to secondary because of what I listed below in initial setup. Choosing ROM to secondary will cause the installation script to be modified to install to the secondary partition or it will error out with "Something went wrong". Zips installation scripts do not need to be modified because they will reference recovery.fstab which has been modified to support the secondary partition (when you select enable secondary FS.
Q.) Why doesn't vibration work after flashing this kernel?
A.) The default setting for vibration in the kernel is 2%. Use the DevilTools app referenced in DerTeufel's OP and change "Set Vibration Intensity" under the Tweak group.
Q.) Does exFat work?
A.) The kernel supports it but the recovery has not yet been modified to support it.
Click to expand...
Click to collapse
2: GUIDE / how to setup dual-boot
Initial Setup
1) Have you flashed the dual-boot (aka DB ) kernel yet? If yes, go to step 3
2) Flash the DB kernel: Go to the DB OP here and flash the version for your model type - http://forum.xda-developers.com/showpost.php?p=40410021&postcount=1 N7100 is for non-LTE models and t0lte is LTE enabled (AT&T, Verizon, etc). The zip will NOT list recovery in the name...
3) Have you flashed the DB recovery? If yes, go to step 5
4) Flash the DB Recovery: Navigate to DB OP listed above and flash the version for your model type (as in step 2 above)
5) Have you created the secondary system partition? If yes, go to step 7
6) Create the secondary partition image: Boot into the DB recovery and select Dual Boot Menu > enable mounting secondary and then select create secondary system image (also under Dual Boot Menu". This will take a couple of minutes. This only has to be done once.
7) Ready to flash primary or secondary ROMs: Note: It is probably a good idea to get in the habit of always selecting the FS (primary or secondary) that you want to affect just to ensure you don't wipe the wrong one, etc. Select Dual boot menu > enable mounting of (pri or sec.)... It stays selected until you boot into recovery and change it. You will see recovery flash (reload) with the appropriate FS selected. Obviously, don't select it again - logic loop...
8 ) You at least need to follow standard ROM installation instructions at this point such as wipe data, etc (as appropriate). Wipe Data/Factory Reset will leave the ROM (typical) and the 2nd option (wipe data-cache-system-preload) will wipe out the ROM completely so you can start "clean". Only the selected FS is modified so the other ROM is not affected. All apps and data are separate for each ROM. SD card storage is common so keep that in mind for an app that exists in both ROMs.
9) Installing to the primary partition does not need any special instructions. You should have already selected "enable primary". Select "Install zip" > Choose zip from sdcard or external > ROM to Primary FS. The difference between the "ROM" and "Zip" selections is that zips do not typically explicitly access the file systems - they use references in recovery.fstab which DerTeufel modified to point to the appropriate locations depending on your selection (primary or secondary). Yes, choosing install zip might work for installing a ROM to primary but NOT to secondary. Also, the intention is to avoid confusion.
10) Installing to the secondary partition MIGHT be more problematic since the zip has to be modified first to replace FS references with the secondary locations. When you select this option, it can take a couple of minutes since it is changing the references and then re-zipping to a modified file on the SD card. Note: The original will be gone (at least if it was originally on the SD rather than the external SD) so make a copy, etc before proceeding if you want it to be available for standard/primary flashing in the future. The modified file will always install to the secondary partition after being modified. Note: Complicated install scripts (such as AROMA) will likely fail. If you want an AROMA based installation then the safest way is to install it to the primary partition, ensure it is working, make a backup and then restore the backup to the secondary partition (using the DB recovery of course). Backup/restore will be detailed below.
11) Recovery does not automatically mount /system, and /data so ensure /cache and these are already mounted before running a zip that will need to modify them
12) Avoiding MTP issues: After flashing a ROM, recovery prompts you to install the DB kernel again. Otherwise, the kernel installed with your ROM will not be able to boot the secondary ROM. However, if you do flash the DB kernel right away (for now at least) you may have a problem with MTP (access from a PC over USB ). If you boot the new ROM (with the ROM's kernel which will work for PRIMARY) then MTP should be working. You can then flash the DB kernel after rebooting to recovery and MTP will still work (afaik). Similar to the AROMA note above, you might want to install a ROM to primary first even if you want it in the secondary partition. The install script will not need to be modified and a normal kernel will boot the ROM so MTP will work. Then you can flash the DB kernel, make a backup and restore to the secondary. Hopefully, this is only temporary but at least this workaround exists.
13) Ready to flash zips to primary or secondary ROMs Flashing gapps, etc. simply requires that the correct FS is enabled, /system and /data (as necessary) are mounted and select your target under "Install zip" > "Choose zip from..." > Zip to (primary or secondary).
Kashortiexda has created another installation process documented in post #13 > http://forum.xda-developers.com/showpost.php?p=41992232&postcount=13
Click to expand...
Click to collapse
3: FAQs about F2FS / benefits of F2FS and dual-boot in f2fs
Q.) What is F2FS?
A.) "The Flash Friendly File System" created by Kim Jaegeuk (Samsung) and released in February 2013. Read more about F2FS here
Q.) Recently, DerTeufel1980 has updated his devil2 dual-boot kernel and recovery and merged F2FS support. What is the benefit of F2FS?
A.) if the internal sdcard is formatted to F2FS, the system is supposed to be up to 2 times faster than on ext4 (default formatting).
Q.) After update to the newest Devil DB Recovery with F2FS support I had problems by installing ROM to the Secondary FS / my nandroid backup was restored with errors
A.) The newest recovery has enlarged Secondary FS image to 1.9GB (earlier was 1.5GB). This can be cause for many errors. So be sure to create a nandroid backup of your Secondary ROM before you erase /secondrom partition from data/media and to create it again with the new recovery. This is very important to do after the recovery update.
Q.) What should I do to be able to use the benefits of F2FS on my device?
A.) Five steps! First: flash new DB recovery & new DB kernel with F2FS support. Second: create nandroid backup(s) of your ROM(s). Third: move all your data from internal sdcard and save them elswhere, as the formatting to F2FS will erase your entire internal sdcard. Fourth: format in recovery mode all the (internal) sdcard partitions to F2FS one by one. Fifth: restore your ROM(s) and data.
Q.) Can I revert from F2FS back to ext4?
A.) Yes. You can use either of Devil DB Recovery versions to revert back to ext4 (in the new version you will can choose between F2FS or ext4) or you can simply flash any other recivery that doesn't support F2FS and format with it all the partitions. It will format all back to ext4 (you will have to repeat the procedure like described in the question right before).
Q.) After return to ext4 I couldn't format /cache back to ext4
A.) Formatting back to ext4 seems to not work reliably with the newest Devil Touch recovery for N7100. If it is only /cache, it doesn't matter as everything seems to work normally. You can use any other non-F2FS recovery (like TWRP 2.6.3.x or PhilZ touch 6.12.8 to format cache back to ext4)
Q.) Can I with F2FS update my ROM(s) normally with any nightly build?
A.) No, it is not recommended, as the nightlies will ATM reformat some of the partitions back to ext4. Well, yes, in fact you can update, but it is quite complicated way around, therefore, F2FS is more practical for those who want to stick longer time with their ROMs and use benefits of very fast performance of their device on F2FS.
Q.) I've got error message after migration to F2FS when I tried to restore my nandroid backup
A.) This happens occasionally mostly there is a "can't mount /data" error message. Don't worry about that, simply reboot recovery, format again all to F2FS and restore your nandroid backup then.
Q.) After migration to F2FS, I can't reach my Secondary FS partition under "dual boot menu", why?
A.) If the recovery displays "Only with Devil Kernel available" (altough it is flashed already), simply reboot into the Primary FS and reboot into the recovery right after that. Then you will be able to create again the Secondary FS partition and restore your nandroid backup.
It has been reported at least by one user that System, Data, EFS, & Storage had to be remounted manually every time for successful boot up by switching from Primary to Secondary FS and vice versa.
DerTeufel1980's features description just after updating kernel and recovery for t0lte to F2FS (N7100 update was released about one week later):
What's new:
kernel:
added new f2fs filesystem support (supposed to be up to 2 times faster than ext4)
introduce the BFQ-v6r2 I/O sched for 3.3
block, bfq: add Early Queue Merge (EQM) to BFQ-v6r2 for 3.3.0
enable CGROUP_BFQIO by default
backport SLUB from Linux 3.3 (thanks to faux123)
afsync: replace fput() with fput_light() accordingly
cfg80211: Fix memory leak
mm: implement WasActive page flag (for improving cleancache)
fix triangle away
usb: fix 'adb root'
recovery:
completed the rework of recovery ui (primary and secondary rom need to be selected once in dualboot menu) if you can't access dualboot menu, please boot primary or secondary rom with the new kernel once
resized secondary system image to 1.9 gb
possibility to flash roms to secondary without modifying the zip (you HAVE TO CHOOSE ROM). if this fails, select use workaround (this is the old method) next time
added support to format and mount f2fs formated partitions (/system, /data and /cache)
if you format data to f2fs (this gives the maximum performance, you have to select primary rom in dualboot menu, then the option will be in mounts and storage: format /data, /data/media and secondary (please backup before, this wipes your internal sdcard as well)
You only can format data to f2fs, when you select to manage primary Filesystem, because it formats the entire partition, including your internal sd card (which also includes your second rom partitions). Formatting data gives you a complete clean data partition, and you need to backup/restore data, and sdcard (if you backup the sdcard with custom nandroid to external sdcard, you can restore it afterwards, which also restores the secondary rom).
The kernel 2.4.5b for t0lte fixes boot on Omnirom, as well as fixes Selinux on Samsung rom. By default Selinux is set to "enforcing" now, for Samsung as well as for AOSP roms.
If one wants to completely disable selinux, you need to create the file: "/.secondrom/.selinux_disable" (if you are currently booted into secondrom, otherwirse the path would be "/data/.selinux_disable" (both is the same file, and creating it, disables selinux for both roms, once rebooted). selinux stays disabled until the file gets deleted again, and the device rebooted.
On some Sammy roms FC may occur with enforced selinux with the warning: "smartcard service has stopped". Except the fact that only few may know what this service does, usually nothing bad will happen (this message appears once once after boot up)
WARNING: After "fixing" booting on Omnirom, DerTeufel1980 has warned that f2fs only seems to be working properly on CM11 based roms. Samsung ROMs are at least working with selinux disabled, but Omni ROM breaks baseband if selinux disabled!!
Click to expand...
Click to collapse
4: GUIDE / ext4 to F2FS migration
New Devil Touch-DB-recovery v6.0.4.5 has some new features:
Instead of double amount of options (for primary FS or secondary FS, respectively) now there is "dual boot menu" where we can choos which FS to manage
Menu text of the secondary FS is displayed now in red color
The size of secondary FS partition is now 1.9GB so even big ROMs can be installed as secondary FS
SCREENSHOT: (new Devil Touch v6.0.4.5 with f2fs support)
As described above under F2FS FAQ, we will migrate to F2FS in five steps:
Step 1/5: flash Devil Touch v6.0.4.5 recovery & kernel with F2FS support for your device (check the download links on the bottom of this post)
flash Devil Recovery with F2FS support for your device (download links are on the bottom of this post)
reboot recovery (under "power options" on the bottom of the main menu)
for single-boot: flash Devil2-F2FS-kernel.zip to your ROM (2.4.5b for t0lte and Verizon / 2.4.6 for N7100)
for dual-boot: if you are already dual-boot user, now flash Devil2-F2FS-kernel.zip to both your ROMs: primary FS and secondary FS
Step 2/5: create now nandroid backup(s) of both your ROM(s):
under "Backup and Restore" choose "Custom Backup and Restore"
in this sub-menu, choose "Custom Backup to /sdcard1" or optionally: "Custom Backup Job"
check for backup only: /system and /data and then >>Start Custom Backup Job<<
as the final step choose "Backup to /storage/sdcard1" option (your external micro SD card)
repeat the same procedure for your second ROM
OPTIONALLY: under this step you can also create a full nandroid backups, but just make sure that you then after migration to F2FS restore only /system and /data in "Custom Restore Job"!
Step 3/5: move all your data from internal sdcard and save them elsewhere, as the formatting to F2FS will erase your entire internal SDcard!
use either external SD card, or your PC as storage, as the entire internal phone memory will be erased in the following step.
mind that this step can take some time, regarding size of the data that has to be copied (20-30 min)
Step 4/5: reboot into the recovery to fs=1 (primary) and format under "Mounts and Storage" following partitions to F2FS:
format /system
format /data, /sdcard and secondrom (this step will destroy the /.secondrom partition)
Step 5/5: restore your ROM(s) and data.
reboot recovery
restore your primary FS
flash Devil-DB kernel
reboot to system and back to recovery
create secondary FS partition
restore your nandroid backup to secondary FS (if you have used "Custom Backup Job")
flash Devil-DB kernel again
OPTIONALLY: if you have made full nandroid backups under step 2/5 now at this point don't miss that you should restore only /system and /data with "Custom Restore Job" option!
Finished! Enjoy F2FS
reverting from F2FS back to ext4
Repeat whole the procedure, just choose under formatting always "ext4" instead of "F2FS"
Click to expand...
Click to collapse
5: download links / troubleshooting
DOWNLOAD LINKS:
Latest versions of the kernel and recovery without F2FS support for Note 2:
Devil2 dual-boot kernel MAIN THREAD
Note 2 kernel and recoveries with F2FS support:
n7100 Devil2 kernel: download here
n7100 recovery: download here
t0lte Devil2 kernel: download here
t0lte recovery: download here (this one works also for Verizon)
The newest Devil3 hybrid kernel for N7100 and t0lte: download here
BOOTLOADER check
Regarding the fact that Devil2-recovery boots 4.3 and 4.4 ROMs, owners of the Note 2 should mind, that many recent custom ROMs are designed to work flawless only with the recent JB bootloaders. Custom ROMs don't update your bootloader, so your bootloader was flashed together with your latest stock ROM that you were using. While ICS bootloaders are nearly completely outdated, now also earliest JB bootloaders might cause problems and malfunctions. If so, some users will have to consider to update the bootloader.
Experienced users know: this is a damn risky task, as if Odin fails so that the old bootloader gets erased and new doesn't get properly flashed, only JTAG will be able to revive your device.
I have made a little guide and provided download link how to flash a knox-free 4.3 MJ5 bootloader for N7100: CLICK HERE
This 4.3 bootloader will boot any 4.3 or 4.4 OS, but it still has the charging issue (Sammy's fault) if the device is turned off. All the newer 4.4 bootloaders where the issue is solved are KNOX'ed, so bootloader downgrade won't be possible anymore if you use any of the later bootloader versions.
CAMERA APP TROUBLESHOOTING:
All who use AOSP custom ROMs (especially CM based ones) on their Note 2 devices might face the "ERROR: can't connect camera" issue. This problem is not devil2 kernel related. The Camera app is crashy on numerous devices. We can have our Camera working reliably, just mind that it is utterly important to keep the phone in clearly defined position when starting the camera (horizontal/vertical) and to be careful by each change of the axis rotation. Also don't view freshly shot photo in your camera app, but close the Camera and use Gallery for that.
Should you still face the nasty "can't connect..." error, instead of rebooting the OS use either of those apps, that can successfully restart the camera with one click (my N7100 needed to have both apps installed to make reset working, now either works fine):
Camera (CMFix) app from Play Store
Restart Camera.apk from HERE
Click to expand...
Click to collapse
Devil-DB-Recovery screenshots (v6.0.4.4):
Nice work m8!! Appreciate the time in you explaining the processes involved:thumbup:
Sent from my SGH-I317M using Tapatalk 2
Very detail write up Rich. Double:thumbup::thumbup:
Thanx
Sent from my SAMSUNG-SGH-I317 using Xparent SkyBlue Tapatalk 2
Thanks RichMD, appreciated "how-to" guide.
However a few remarks:
Similar to the AROMA note above, you might want to install a ROM to primary first even if you want it in the secondary partition. The install script will not need to be modified and a normal kernel will boot the ROM so MTP will work. Then you can flash the DB kernel, make a backup and restore to the secondary. Hopefully, this is only temporary but at least this workaround exists. Hopefully, this is only temporary but at least this workaround exists.
Click to expand...
Click to collapse
It means that in the future we won't need to backup then restore Roms which have to be installed with a Aroma Installer?
In your guide I suggest to add the following b4 Step 5:
Make a Nandroid backup to save our current configuration! If you don't manage to install DB or if we aren't convinced by DB benefitis we can come back to an "one ROM boot".
totelysw classical
Sounds good so far hope to be able to install to external sd storage instead of the internal
Sometimes this process will need extras. At least it did for me, and more than once. Most probably because recovery is trying to replace or prevent original kernel of the second rom to be installed and causing mishaps..
So my additions are:
After flashing second rom howsoever, reflash dualboot kernel.
Reboot rom if stuck get into recovery and wipe cache and dalvik.
I had the issue of cm roms to use partitions, i had to fix permissions (for sec fs) and also once i had to log into recovery, then advanced menu and select /data location..
Sent from my GT-N7100 using xda premium
Memphis_ said:
Thanks RichMD, appreciated "how-to" guide.
However a few remarks:
It means that in the future we won't need to backup then restore Roms which have to be installed with a Aroma Installer?
In your guide I suggest to add the following b4 Step 5:
Make a Nandroid backup to save our current configuration! If you don't manage to install DB or if we aren't convinced by DB benefitis we can come back to an "one ROM boot".
Click to expand...
Click to collapse
Thanks. I plan to add a "How do you completely remove dual-boot" even if you didn't make a nandroid first but I will add a comment similar to what you mentioned.
Awesome!
great work cheers!:fingers-crossed:
myaslioglu said:
Sometimes this process will need extras. At least it did for me, and more than once. Most probably because recovery is trying to replace or prevent original kernel of the second rom to be installed and causing mishaps..
So my additions are:
After flashing second rom howsoever, reflash dualboot kernel.
Reboot rom if stuck get into recovery and wipe cache and dalvik.
I had the issue of cm roms to use partitions, i had to fix permissions (for sec fs) and also once i had to log into recovery, then advanced menu and select /data location..
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Flashing the DB kernel again is required after flashing primary or secondary. My comments are simply that you may not want to do it immediately and let the (primary partition ROM only) boot initially with the ROM included kernel to ensure MTP works. You then need to flash the DB kernel after if you ever want to boot the secondary ROM. If you just finished flashing a ROM to secondary then I "believe" you would need to flash the DB kernel before you could ever boot that ROM. However, MTP (at this point) might not work. If it doesn't then the workaround I listed would help. Does that answer your question/comment?
I will add more to the post on fixing permissions, etc. I need a bit more detail on what your process for CM was. You installed CM to secondary and it wouldn't boot so you went into recovery and advanced > fixed permissions (secondary FS was already enabled)?. I'm not sure what your comment about /data means other than you went to mounts and storage and mounted /data. Is that what you meant?
RichMD said:
Flashing the DB kernel again is required after flashing primary or secondary. My comments are simply that you may not want to do it immediately and let the (primary partition ROM only) boot initially with the ROM included kernel to ensure MTP works. You then need to flash the DB kernel after if you ever want to boot the secondary ROM. If you just finished flashing a ROM to secondary then I "believe" you would need to flash the DB kernel before you could ever boot that ROM. However, MTP (at this point) might not work. If it doesn't then the workaround I listed would help. Does that answer your question/comment?
I will add more to the post on fixing permissions, etc. I need a bit more detail on what your process for CM was. You installed CM to secondary and it wouldn't boot so you went into recovery and advanced > fixed permissions (secondary FS was already enabled)?. I'm not sure what your comment about /data means other than you went to mounts and storage and mounted /data. Is that what you meant?
Click to expand...
Click to collapse
No it is the other way around. Everything worked fine, CM booted perfectly, settings were to be applied easily. Gapps flashed well and worked without glitch. However, file managers, play store or anything trying to access fs couldnt manage to do so.. I first changed my ROM tried old sentinel (4.5) then paranoidandroid and then new sentinel.. But same thing happened. Then I booted reflashed DB and fixed permissions. Rebooted CM, still no access. Afterwards, I rebooted into recovery re-fixed permissions but this time under the advanced menu (surely after activating second partition from dualboot menu) I set the storage to /data/media/0 .. rebooted 2nd rom. this time everthing worked fine.
Aforementioned are all for 2nd rom. 1st rom worked like a charm except for the MTP
I would love to see this on the tmobile s4
Sent from my SGH-M919 using xda premium
Strange behaviour on my N7100
After I flash the Devil dual-boot kernel (either the current - Devil-n7100-DUAL-0.21.3_20130529.zip or the previous version) this is happening to my device:
0. flashing is succesful and I reboot
1. the logo "Samsung Galaxy Note II N7100" stays on screen for approx. 4 or 5 minutes. Initially I believed it's completely frozen
2. the ROM specific logo (CyanogenMod or Samsung) appears on screen and ROM is loading shortly
3. everything works perfect, except touchscreen with fingers. Only S-Pen is working. I can check the kernel and it's the version I've flashed. Also when I press Home button 4 times, screen colors becomes negative, as it should.
4. if device enters in Sleep (screen off), the notifications are working (eg. new mail)
5. if phone gets an incoming call or if I wake the phone from sleep, the screen stays on for less than a second, then forcibly reboots
6. back to step 1.
Have anyone encountered this problem? This is happening with either Samsung stock 4.1.1 firmware rooted or with Cyanogenmod 10.1 nightly from last days.
I would love to have this kernel working...
RichMD
sorry to hijack your thread, delete if you need.. here's what works for me, several times ( I used your and Der Teufel guide as reference) just put it in a step by step guide
After a lot of reading and some tinkering, I've got PACMAN 4.2.2 PA /AOKP /CM10 1on ROM1 and 4.1.2 Mike1986 ARHD17 Sammy on ROM2.
Adb, MTP, Trickster works fine on both.
Working great. Even managed to get Simplistic Framework and Xposed working on rom 2 (Sammy)
simply
(a) first put the rom you want as PRIMARY on your ext sd card, either a flashable zip or a CWM nandroid backup (NOT TWRP).. you will need this later in step 32
1 on your existing rom and kernel combination , flash DT recovery,
2 reboot to recovery
3 go to dual boot options in recovery
4 create second partition
5 reboot to first rom
6 check MTP
7 reboot recovery
8 dual boot menu
9 enable mount primary ( second on list of 3 options )
10 go back, Mounts and storage
11 mount efs, system, data, ext sdcard
12 go Back, wipe data (2nd option for FULL wipe)
13 check mounts again and remount as above
14 flash the rom you want to be as SECOND rom
15 do all your fancy mods now (Xposed etc)
16 check mounts, remount if necessary
17 flash DT dual boot kernel with "flash kernel" option
18 reboot
19 check MTP
20 go to step 7 and repeat 7-11 inclusive
21 do a backup to ext sd
to move the rom to second rom position..
22 dual boot menu
23 enable mount secondary ( third/last on list of 3 options )
24 go back, Mounts and storage
25 mount efs, system, data, ext sdcard
26 go Back, wipe data (2nd option for FULL wipe)
27 go to Backup and Restore
28 restore the rom you made in step 21 from the ext sd
29 reboot to second rom (allow full boot)
30 check MTP, should work
31 do steps 7-13
32 flash, or restore the rom you placed on your ext sd card in the very beginning step (a) ie the one that you want to be as FIRST/PRIMARY rom
33 Reboot
Done
DO NOT FLASH ANY KERNEL AFTER STEP 33 ( the kernel will show in primary rom settings as unavailable but check with Trickster Mod or CPU spy, it will show you that it is DT dual boot kernel)
The above has worked for me several times now, and some steps are overkill..
The 0 folder from 4.2.2 is visible from the Sammy rom but the Sammy files are not visible from 4.2.2 that's why I recommend using the ext sd for the above procedures as a failsafe
Sent from my dual boot GT-N7100 using Tapatalk 2
kashortiexda said:
RichMD
sorry to hijack your thread, delete if you need.. here's what works for me, several times ( I used your and Der Teufel guide as reference) just put it in a step by step guide
After a lot of reading and some tinkering, I've got PACMAN 4.2.2 PA /AOKP /CM10 1on ROM1 and 4.1.2 Mike1986 ARHD17 Sammy on ROM2.
Adb, MTP, Trickster works fine on both.
Working great. Even managed to get Simplistic Framework and Xposed working on rom 2 (Sammy)
simply
(a) first put the rom you want as PRIMARY on your ext sd card, either a flashable zip or a CWM nandroid backup (NOT TWRP).. you will need this later in step 32
1 on your existing rom and kernel combination , flash DT recovery,
2 reboot to recovery
3 go to dual boot options in recovery
4 create second partition
5 reboot to first rom
6 check MTP
7 reboot recovery
8 dual boot menu
9 enable mount primary ( second on list of 3 options )
10 go back, Mounts and storage
11 mount efs, system, data, ext sdcard
12 go Back, wipe data (2nd option for FULL wipe)
13 check mounts again and remount as above
14 flash the rom you want to be as SECOND rom
15 do all your fancy mods now (Xposed etc)
16 check mounts, remount if necessary
17 flash DT dual boot kernel with "flash kernel" option
18 reboot
19 check MTP
20 go to step 7 and repeat 7-11 inclusive
21 do a backup to ext sd
to move the rom to second rom position..
22 dual boot menu
23 enable mount secondary ( third/last on list of 3 options )
24 go back, Mounts and storage
25 mount efs, system, data, ext sdcard
26 go Back, wipe data (2nd option for FULL wipe)
27 go to Backup and Restore
28 restore the rom you made in step 21 from the ext sd
29 reboot to second rom (allow full boot)
30 check MTP, should work
31 do steps 7-13
32 flash, or restore the rom you placed on your ext sd card in the very beginning step (a) ie the one that you want to be as FIRST/PRIMARY rom
33 Reboot
Done
DO NOT FLASH ANY KERNEL AFTER STEP 33 ( the kernel will show in primary rom settings as unavailable but check with Trickster Mod or CPU spy, it will show you that it is DT dual boot kernel)
The above has worked for me several times now, and some steps are overkill..
The 0 folder from 4.2.2 is visible from the Sammy rom but the Sammy files are not visible from 4.2.2 that's why I recommend using the ext sd for the above procedures as a failsafe
Sent from my dual boot GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I certainly don't see that as a "hijack". The intent of the thread is to help anyone that is having a problem with the installations. Having multiple methods to try just helps ensure success if they keep trying.
n4553 said:
After I flash the Devil dual-boot kernel (either the current - Devil-n7100-DUAL-0.21.3_20130529.zip or the previous version) this is happening to my device:
0. flashing is succesful and I reboot
1. the logo "Samsung Galaxy Note II N7100" stays on screen for approx. 4 or 5 minutes. Initially I believed it's completely frozen
2. the ROM specific logo (CyanogenMod or Samsung) appears on screen and ROM is loading shortly
3. everything works perfect, except touchscreen with fingers. Only S-Pen is working. I can check the kernel and it's the version I've flashed. Also when I press Home button 4 times, screen colors becomes negative, as it should.
4. if device enters in Sleep (screen off), the notifications are working (eg. new mail)
5. if phone gets an incoming call or if I wake the phone from sleep, the screen stays on for less than a second, then forcibly reboots
6. back to step 1.
Have anyone encountered this problem? This is happening with either Samsung stock 4.1.1 firmware rooted or with Cyanogenmod 10.1 nightly from last days.
I would love to have this kernel working...
Click to expand...
Click to collapse
Just to confirm, this looks like you aren't trying to do anything with dual-boot - just using his dual-boot kernel on a solitary ROM - correct? If you can flash other custom kernels successfully (perseus, sabre, soap, etc.) then I don't know what to tell you. What recovery are you using to flash it?
HI RichMD,
I am getting error at step 6.
it fails to mount Primary Files.
I tried following
Reloaded Recovery -in duel boot menu -enable mounting of Pri File.
thn i tried to create secondary System image. Still m getting same error.
am i missing something .
Also i noticed that i am not able to mount SDCARD in menu Maount and Storage
regards
JoyMoro
---------- Post added at 11:31 AM ---------- Previous post was at 10:50 AM ----------
JoyMoro said:
HI RichMD,
I am getting error at step 6.
it fails to mount Primary Files.
I tried following
Reloaded Recovery -in duel boot menu -enable mounting of Pri File.
thn i tried to create secondary System image. Still m getting same error.
am i missing something .
Also i noticed that i am not able to mount SDCARD in menu Maount and Storage
regards
JoyMoro
Click to expand...
Click to collapse
Pls ignore it,. I got it working.
regards
JoyMoro
RichMD said:
Just to confirm, this looks like you aren't trying to do anything with dual-boot - just using his dual-boot kernel on a solitary ROM - correct? If you can flash other custom kernels successfully (perseus, sabre, soap, etc.) then I don't know what to tell you. What recovery are you using to flash it?
Click to expand...
Click to collapse
Yes, for now I haven't installed the second rom, however this is what I want to achieve, dual-boot. But firstly I wanted to make sure the kernel is working. I am using Devil recovery, when I flash other things with it, there are no problems...
I am getting error at step 6.
it fails to mount Primary Files.
I tried following
Reloaded Recovery -in duel boot menu -enable mounting of Pri File.
thn i tried to create secondary System image. Still m getting same error.
am i missing something .
Also i noticed that i am not able to mount SDCARD in menu Maount and Storage
Pls ignore it,. I got it working.
How did u get it working since i got the same issue here?
Is it only me who cannot get play store to work on sec.rom or anyone else have the same issue
Sent from my GT-N7100 using xda premium
no prob
myaslioglu said:
Is it only me who cannot get play store to work on sec.rom or anyone else have the same issue
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Play store works fine for me on second rom
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