Develop Bugs

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

READ ALL OF THE OP BEFORE POSTING QUESTIONS​
The Intro;
As we now have NAND booting for the HD2, its time we also had a way to flash ROMs from the SD aswell so here we have ClockworkMod Recovery compiled for the HD2. It is fully working except ROM Manager is not supported.
Recovery can now boot from NAND instead of the old SD Card boot method, to flash the rom, download the recovery with the partition layout you require, then flash as you would a standard NAND rom using DAF and MAGLDR USB Flasher. then select AD Recovery to load into recovery.
Click to expand...
Click to collapse
MAGLDR v1.13 IS REQUIRED, OLDER VERSIONS ARE NOT SUPPORTED, DOWNLOAD v1.13 HERE​
Click to expand...
Click to collapse
Kind note to Devs;
Please stop posting modified flash.cfg files for use with CWM
CWM is designed to make it easier to flash roms without needing a windows PC, if you post a different flash.cfg in each rom thread then it defeats this purpose as a pc will be required for flashing each layout.
Stick to using the default partition layouts or use USB flasher
Click to expand...
Click to collapse
WARNING MESSAGES:
GOING FROM A DAF FLASHED ROM TO A RECOVERY FLASHED ROM WILL WIPE ALL DATA
IF YOU FLASH ANOTHER ROM USING DAF, RECOVERY WILL NO LONGER WORK CORRECTLY, YOU WILL NEED TO REFLASH RECOVERY
Click to expand...
Click to collapse
Features;
-Flash ROMs in update.zip format
-Backup and restore ROMs using Nandroid
-Flash ROMs from the SD card without use of a PC
-Easilly Wipe all Data/Cache
-Repartition SD card for use with Apps2SD
-Full Root ADB access
-Fix app permissions
Click to expand...
Click to collapse
How to use;
For MAGLDR NAND Boot;
1. Download recovery with partition size for the type of rom you plan on using, see guide below if unsure.
2. Extract downloaded file and load magldr into USB Flasher mode.
3. Run DAF.exe and follow instructions
4. After completed and phone reboots, hold power key and select AD Recovery from list
5. Recovery will now load
Click to expand...
Click to collapse
For old style SD Boot;
1. download one of the partition files for SD Boot, if you don't know which one you need, use the 250M one or check with rom developer.
2. Extract downloaded zip to a folder of your choice
3. Copy contents of copy_to_sd_root (initrd.gz and zImage) to the root of your sd card
4. boot into magldr and select USB Flasher option while phone is connected to PC
5. Run DAF.exe included in the zip and follow onscreen instructions.
6. After complete, again boot into magldr and select "Boot AD SD" option
7. ClockworkMod recovery should load, you can flash a rom from here.
Click to expand...
Click to collapse
Video Tutorials;
How To Install Clockwork Mod Recovery On The HD2 (Courtesy of GFurr)
How to Install NAND Android on HTC HD2 with ClockworkMod Recovery? (Courtesy of jayceooi)​
Click to expand...
Click to collapse
Downloads;
Latest;
-Download v1.3 150MB-
-Download v1.3 250MB-
-Download v1.3 400MB-
Old Versions;
-v1.2- DOWNLOAD
-v1.1- DOWNLOAD
-v1.0- DOWNLOAD - MegaUpload Mirror
Old Partition Layouts for SD Boot;
-150MB System-
-250MB System-
-400MB System-​
Click to expand...
Click to collapse
Changelog;
v1.3;
-Supports AD Recovery in MAGLDR
-MAGLDR v1.13 REQUIRED Download HERE
-400MB Partition layout now works with 512MB LEO for roms with Data2SD
v1.2;
-Fixed SD-EXT Backup/Restore/Wipe
v1.1;
-Updated ClockworkMod to 3.0.0.5, now based on Gingerbread Source
v1.0;
- Initial Release
Click to expand...
Click to collapse
Q&A;
Q. Ive flashed v1.3 but cant access recovery anymore.
A. Make sure you are using MAGLDR 1.13 and are selecting "AD Recovery" instead of "Boot AD SD"
Q. Ive downloaded v1.3 but there is no copy_to_sd folder
A. Recovery no longer requires any files on the SD card, just flash it like a standard nand rom and select "AD Recovery in magldr menu
Q. Can I change the partition sizes used for CWM
A. You can by editing the flash.cfg but this is not recommended, CWM is designed to make it easier for switching roms, by flashing a custom partition size you may stop other roms working and require reflashing a new partition size when you want to change roms.
Q. I dont know which partition size to download
A. Depending on what type of roms you plan on using, you should choose the partition size based on the following.
150MB Partition - For bare roms including CyanogenMod, AOSP, and MiUI
250MB Partition - For Standard sense roms including Desire and EVo based ROMs, can also be used for some squashed HD builds
400MB Partition - For Larger roms including unsquashed Desire HD and Z roms, ROMs REQUIRE data2sd for EU HD2 with 512MB NAND
Click to expand...
Click to collapse
*I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE BY USING THIS RECOVERY IMAGE*
​
Click to expand...
Click to collapse
Notes for devs;
Please add tags to the title of your threads stating if they are to be flashed with recovery or DAF, [ZIP] for recovery update.zip and [USB] if its installed over usb using daf.
The cache partition is only 10MB so that recovery can still use it, to get cache to work in android, make a directory in data called cachemnt and on boot symlink /cache to /data/cachemnt, this does not apply when using 150M partition size
Click to expand...
Click to collapse
Credits go to;
-Cotulla + DFT for the great work for Android on NAND
-CyanogenMod team for work on recovery
-Anyone else who has made the HD2 a great device
Click to expand...
Click to collapse

i think i just wet myself....thanks so much

RaiderX303 said:
As we now have NAND booting for the HD2, its time we also had a way to flash ROMs from the SD aswell so here we have ClockworkMod Recovery compiled for the HD2. It is fully working except ROM Manager support still has some issues. See below for features and how to use.
Because ROMs are not flashed using DAF, a set partition layout is required before flashing any ROMs using recovery, included in the download is DAF which is configured to create the required partitioning, just run as you normally would to flash a NAND ROM and you are set to flash a new ROM through recovery
WARNING: GOING FROM A DAF FLASHED ROM TO A RECOVERY FLASHED ROM WILL WIPE ALL DATA
WARNING: IF YOU FLASH ANOTHER ROM USING DAF, RECOVERY WILL NO LONGER WORK CORRECTLY, YOU WILL NEED TO REFLASH THE PARTITIONING TO USE RECOVERY AGAIN
Features;
-Flash ROMs in update.zip format
-Backup and restore ROMs using Nandroid
-Flash ROMs from the SD card without use of a PC
-Easilly Wipe all Data/Cache
-Repartition SD card for use with Apps2SD
-Full Root ADB access
-Fix app permissions
How to use;
1. Copy content of copy_to_sd_root folder to the root of your SD card
2. Power on phone holding power button to access magldr menu
3. Select "USB Flasher" option
4. Run DAF.exe and go through installer to set required partition layout
5. After reboot repeat step 2 to access menu again
6. Select "Boot AD SD" and recovery will load
Download;
-v1.0-DOWNLOAD
Changelog;
v1.0
- Initial Release
*I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE BY USING THIS RECOVERY IMAGE*
Request for devs;
Please add tags to the title of your threads stating if they are to be flashed with recovery or DAF, [ZIP] for recovery update.zip and [USB] if its installed over usb using daf.
Credits go to;
-Cotulla + DFT for the great work for Android on NAND
-CyanogenMod team for work on recovery
-Anyone else who has made the HD2 a great device
Click to expand...
Click to collapse
You have to be ****ting me!!! Great work!!! Soon... Nandroid Got Your Back. LOL.
---
Sent from my HD2 DROID.

Great.
Sent from my HTC HD2

@Raiderx
Is the rom manager support you are talking about the ability to flash different themes and stuff of that nature in recover mode? Also can we expect it in the future?

This is now officially an android phone. Finally get to back up Roms awesome!!!!

Rom manager support is an app that allows you to control the recovery from within Android and then reboot to recovery to run the commands
Sent from my Desire HD using XDA App

Hell Yes
How will I install roms and where will I get them I am confused!

mattfmartin said:
@Raiderx
Is the rom manager support you are talking about the ability to flash different themes and stuff of that nature in recover mode? Also can we expect it in the future?
Click to expand...
Click to collapse
Rom manager is just the app that that you get from the market to flash without booting to recovery we could wait on that.

what the doctor
this is progress and what ive been looking to add

Just to clarify the instructions... Do we extract the Downloaded zip to the Root of the Sd Card then flash What ROM we will be using? Words in bold are my keys...
Thanks
EDIT: Scratch that.. I guess I should have opened the Zip first.
This is Bad Ass!!

Wow! My dreams have come true
Thanks!

Oh man, this is amazing! Any chance of Amon Ra at some point?

to cool
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!

@Raider x
What I was getting at, I always see native android threads talking about flashing themes through recovery. Well we be able to do that with this?

jhr5474 said:
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!
Click to expand...
Click to collapse
Devs will need to release ROMs in update.zip format, there are none currently released although i am in the process of uploading one, you then copy the zip the dev provides to the root of the SD, and flash like you did on the G1
mattfmartin said:
@Raider x
What I was getting at, I always see native android threads talking about flashing themes through recovery. Well we be able to do that with this?
Click to expand...
Click to collapse
you will be able to flash themes using recovery once theme devs create them

SWEET!!!!!!!!!!!!

jhr5474 said:
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!
Click to expand...
Click to collapse
+1 good question, are we clear to load nand roms already or do the devs have to modify what they have? I think I will wait until more clarification.
Edit: thanks for the clarification

APJG said:
Oh man, this is amazing! Any chance of Amon Ra at some point?
Click to expand...
Click to collapse
What do u want from me? LOL As a matter of fact if i read this correctly this is almost what i need, a way to flash android ROMs without the usage of a pc (USB port). Can anyone tell me if it is correct

jhr5474 said:
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!
Click to expand...
Click to collapse
Yeah, We need some ROMS converted to flashable.zip's... I'm goning to load up CW now just so I can see it. LOL

How to Flash/Use Multirom(Noob friendly)

Okay these are the steps I took and put as simple as possible.Some steps may be skipped depending on if you have done them or not.These are written based off my setup and what i did.
Disclaimer:Me nor Tassadar or bigsupersquid are responsible for any damage done to your phone so use at your own risk.
Multirom Install:
1.Format through cwm your sd card to have an ext(Recommended 512 mb)
2.Download the two zips from bigsupersquid posted here:http://forum.xda-developers.com/showthread.php?p=20626123#post20626123
3.Place them both onto your sd card.
4.Boot into cwm and flash the cwm zip you downloaded from squid's thread.
5.Now reboot your phone and then boot again into cwm(It should have blue text if it flashed correctly and the multirom option)
6.Now I highly recommend you make a backup of your current rom just in case anything goes wrong.(I made a copy of it onto my pc as well.)
7.Now flash the other zip titled "Multirom..." and wait for it to install.Now reboot to see if it boots.If boots then everything has been done correctly.
Rom on SD Card setup/install:
For this I have install on phone the latest build of cm for oV and will be using the same rom to setup on sd card just for test.
1.Now here Make another backup of your current rom through recovery(Will be used trust me)
2.Now flash the rom you want to use on sd card.(If using a 2.3 rom then the sd card crom msu also be 2.3 and vice versa for 2.2 roms).Reboot phone(a must so dalvik is created correctly).(Make sure to do the appropriate steps fro flash rom like wiping etc.)
3.Reboot back into recovery.Go to multirom and select "Create from current rom". (flash the multirom zip again if it says folder not found)(ROM on the sdcard is placed in /sd-ext/multirom/rom/).
4.After it finished you can go ahead and restore the backup you made in step 1. and the reboot after finished and wait until boot manager shows up.
5.Select boot from sd card and it should boot into the rom you chose to install to sd.(If it doesn't then you did one of the steps wrong).
6.That's it you now have multirom booting enjoy it !
MultiROM recovery menu description:
Active/deactive state is for recovery only, you can boot ROMs from backup in boot manager - that means its N-times boot rather than dual-boot.
When not active(boot from internal memory):
Activate (move from backup) - when you already have backup, this will move it to active folder (fast).
Activate (copy from backup) - same as above, but it copies it instead of moving
Create from current ROM - pretty self-explanatory
When active(boot from sdcard):
Deactivate (move to backup) - Moves current ROM to backup folder, so next boot will be from internal memory
Backup - Creates backup of current ROM
Erase current ROM - Deletes current rom, next boot will be from internal memory
Copy modules from int mem - Copies modules from ROM in internal memory to SDcard. Try this if WiFi does not work in SDcard ROM.
Thanks to Tassadar,bigsupersquid,everyone behind cm7 for optimus v and anyone else that contributed to this

Sounds awsome, gotta try the noob friendly lol....dont have patience for the more detailed one ;P
Sent from my LG-VM670 running ICS2.3.7 oc 806~825

any way to get link2sd to work with this. sdext doesn't appear to handle both multirom and link

what are the pro's n cons of this? someone please explain this to me b4 i attempt this. thanks.

Ventrue05 said:
what are the pro's n cons of this? someone please explain this to me b4 i attempt this. thanks.
Click to expand...
Click to collapse
Well pros would be you can dual boot between roms.Cons would be not many different roms since most are based off cm7 lol

why would i want to switch on the go from roms? im not being a **** or anything just wondering why someone would want to do that.

Ventrue05 said:
why would i want to switch on the go from roms? im not being a **** or anything just wondering why someone would want to do that.
Click to expand...
Click to collapse
Some just like the choice of having two different roms customized differently with different apps and such.

DarkLG said:
Well pros would be you can dual boot between roms.Cons would be not many different roms since most are based off cm7 lol
Click to expand...
Click to collapse
Plus you can partition a bigger space on your SD card giving you more room for apps

What is the likeliness this recovery will prevent you from flashing a different recovery.
There are a couple people trying to flash the rzrecovery and getting failed attempts.

eollie said:
What is the likeliness this recovery will prevent you from flashing a different recovery.
There are a couple people trying to flash the rzrecovery and getting failed attempts.
Click to expand...
Click to collapse
Hmm guess nobody has a answer to this...

eollie said:
What is the likeliness this recovery will prevent you from flashing a different recovery.
There are a couple people trying to flash the rzrecovery and getting failed attempts.
Click to expand...
Click to collapse
If you flash the recovery image using flash_image while booted into android, I think it's safe to say just about zero.

tdmcode said:
If you flash the recovery image using flash_image while booted into android, I think it's safe to say just about zero.
Click to expand...
Click to collapse
Something was not working right because a couple people using the multi recovery couldnt get rzrecovery to install. Not sure if they got IHO installed or not. I have a feeling something is not allowing flash_image to work properly with that recovery.
I just wanted to see what the devs of this recovery thought.

Tetris from recovery is worth it by itself! havn't installed a second rom yet but this is cool anyways

Did I brick my SGS3 ? ^_^

All right, first thing first. Thanks to everybody for this amazing forum and all support.
Well. Here's my story:
1) Planned on installing CM10 nightly
2) Went to recovery (TWRP v2.2.0) and by mistake wiped everything :/ (Cache, Dalvik Cache, Factory Reset, System Internal Storage)
3) In effect i wiped everything including system.
4) Still have access to TWRP and download mode.
Does anybody have a clue how to fix that and install CM10 again?
PS.
1) internal storage does not mount under system (WIN7)
2) TWRP does not recognize microSDXC (32gbz) formated to either exFat or NTFS. (Tried 4 (four) of them)
Should i buy another micro sd like 2gb, format it to Fat32 and drop CM.zip there ? Or need i do something else?
Very respectfully.

That happened to me I just downloaded the rom to a sd card from my old phone put it in my s3 and installed it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Hey thank you for quick answer. Do you know if there is any limitation for TWRP? It does not read my 32gb MicroSDXC.

Go into download mode and re flash then stock rooted rom.
Then install your twrp and try cm again.
Sent from my SGH-I747M using xda app-developers app

Personally, I would (try to?) use adb with the phone booted into TWRP to transfer the ROM you want to flash over to the phone's internal storage, and go from there.
If that's not a possibility for whatever reason, you'd be best off starting by reflashing a stock rooted image with Odin and going from there.

Well. First of all thank you all for all your help in support. Got it back to stock with root (Odin flash). However there is another small problem that i can't figure out. TWRP itself seem not to have access to anything. I mean it sees all / but after openning /sdcard or anything else all it sees is empty folders. It doesn't have an access to external sd either (when you check log it sees that it couldn't mount ext sd correctly [even if after boot to stock system it recognizes it witout any issues).
Any idea how to solve this problem? What has been tried:
1) Reflash recovery (TWRP 2.2 using ODIN)
2) moving all files to /
3) RootExplorer see files (cm.zip) after reboot TWRP doesn't
4) Installing GooManager (it crashes after granting supersu permissions)
Very Respectfully.

With all those problems, flash to stock rooted and start over. You will be better off in the long run. You may want to also format your external sd.
Don't flash twrp with Odin.
Rooted stock
Dl and use goo manager to get twrp

What about a stock kernel? Just my chime in
Sent from my SAMSUNG-SGH-I317 using xda premium

Allright small update.
1) ReFlashed to rooted stock (root66_ATT_I747UCDLK3.tar.md5)
2) Installed GooManager
3) Installed TWRP (using GooManager)
4) Downloaded lastest CM10 nightly (cm-10.1-20121218-NIGHTLY-d2att.zip) using GooManager
5) Flashed cm-10.1-20121218-NIGHTLY-d2att.zip from GooManager menu (FlashROM) - Wiped Dalvik & Cache
Now I'm stacked with CM boot splash for past 5 min hoping it just takes longer that it should.
Any ideas?
Very Respectfully.
EDIT:
Booting into recovery and performing factory reset fixes problem.
Thanks to everybody who helped.

widofmaker said:
Allright small update.
1) ReFlashed to rooted stock (root66_ATT_I747UCDLK3.tar.md5)
2) Installed GooManager
3) Installed TWRP (using GooManager)
4) Downloaded lastest CM10 nightly (cm-10.1-20121218-NIGHTLY-d2att.zip) using GooManager
5) Flashed cm-10.1-20121218-NIGHTLY-d2att.zip from GooManager menu (FlashROM) - Wiped Dalvik & Cache
Now I'm stacked with CM boot splash for past 5 min hoping it just takes longer that it should.
Any ideas?
Very Respectfully.
EDIT:
Booting into recovery and performing factory reset fixes problem.
Thanks to everybody who helped.
Click to expand...
Click to collapse
GJ take it sure and slow. Other than flashing stock/rooting form Odin I wouldn't flash anything form Odin. Once you have super user on your phone, leave Odin out and do everything from phone
That's the safest route and it gets easier from here. The countless hours you spent are much easier the more you do it. Shouldn't take more than 20 minute to backup and flash roms and new apps from now on

Oh boy.
Almost done. But here are another tiny problems that just bother me and but I think they're solvable.
1) GooglePlay suddenly gives "No Connection" error, even though every other app that requires connection (Messenger, Browser) work just fine.
Have to mention that it worked for a while, installed couple apps (drop some more to install in queue and when I woke up - FAIL!)
Things done:
-Forced to stop
-ClearedData & Cache
Is there any other solution to fix it rather than reflashing gapps ?
2) The ExternalSD is mounted under PC as Internal Storage and vice versa.
When you click "Samsung -GHS-I747) in my computer it shows both with proper sizes but once you click them it opens the other.
No clue how to solve that one.
Very respectfully.

widofmaker said:
Oh boy.
Almost done. But here are another tiny problems that just bother me and but I think they're solvable.
1) GooglePlay suddenly gives "No Connection" error, even though every other app that requires connection (Messenger, Browser) work just fine.
Have to mention that it worked for a while, installed couple apps (drop some more to install in queue and when I woke up - FAIL!)
Things done:
-Forced to stop
-ClearedData & Cache
Is there any other solution to fix it rather than reflashing gapps ?
2) The ExternalSD is mounted under PC as Internal Storage and vice versa.
When you click "Samsung -GHS-I747) in my computer it shows both with proper sizes but once you click them it opens the other.
No clue how to solve that one.
Very respectfully.
Click to expand...
Click to collapse
1. you are flashing a version of gapps that is out of touch with your rom or you did not flash it correctly/cleanly. I remember no matter how many times I flashed gapps I wouldn't get it to sync. Backed all user apps to Titanium backup. Did a clean install from scratch, and wallah it worked. Last sort.
Without doing that though there is usually one that is compatible that is listed on your rom page. Flash that one. For me that is 10/22 but I remember it giving that same error for a while so I ended up flashing the previously compatible version before that which was 7/26. Goo.im might help here, I haven't used it myself. Once you find a working gapps version etc. Store your 'safe' builds in one folder
2. Not sure what you mean. When you click your phone you should see internal and external storage on your phone. They are what they say they are. People tend to piss on not being able to find the right file size and folder attributes on this phones usb mount. It is a common problem. Probably one of the few problems on the phone. Annoying but manageable

zetsui said:
2. Not sure what you mean. When you click your phone you should see internal and external storage on your phone. They are what they say they are. People tend to piss on not being able to find the right file size and folder attributes on this phones usb mount. It is a common problem. Probably one of the few problems on the phone. Annoying but manageable
Click to expand...
Click to collapse
1) Ended up reflashing gapps with goomanger (script to TWRP)
2) What i mean is that under phone it recognizes them perfectly. Just when I connect phone through USB to PC, my PC tends to mix them up. Just shows ExSD as Internal and Internal as ExSD. No biggy, just tried to fix as many tiny issues as possible before I hit deployment.
Very respectfully.

That is a known, and stated, issue with cm 10.1

Dual-Boot FAQ thread | devil2-kernel by DerTeufel1980 [Note 2]

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

[OFFICIAL] TWRP 3.7.0 | DRG/DRG_sprout support thread

Note - I am not responsible for bricked devices
About TeamWin Recovery Project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our Zulip channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
You can find the source code for TWRP at github.com/teamwin/android_bootable_recovery/
Installation procedure
1 . Download the latest TWRP img file from the downloads page
2. Boot to fastboot, and use a PC to boot into TWRP using the command: fastboot boot (TWRP filename).img
3. Head to TWRP's advanced section
4. Press "Flash Current TWRP"
Note: the installed TWRP will be lost if you flash another ROM or update your ROM, and the process has to be repeated then.
Find the Nokia 6.1 Plus (OPEN SOURCE!) Community here​
XDA DevDB Information
TWRP for the Nokia 6.1 Plus / X6
Device Tree
Version Information
Status: Stable
Current Stable Version: 3.6.0
Like my work? Consider donating!
https://ko-fi.com/Sid127
UPI users - [email protected]

Great job !

Official builds are now up for download, please refrain from downloading any version other than v3.6.0

Will it work for Android 12? Thanks for the good work...

goodlife1870 said:
Will it work for Android 12? Thanks for the good work...
Click to expand...
Click to collapse
yessir, you can flash any ROM that our device supports with this TWRP

Sid127 said:
yessir, you can flash any ROM that our device supports with this TWRP
Click to expand...
Click to collapse
Thanks so much Sir Sid127... I appreciate...

How awesome is that - thank you for your hard work, @Sid127.
TWRP's new Advanced -> "Flash Current TWRP" feature has the same effect as its predecessor "Install Recovery Ramdisk", with the advantage of not having to manually select the twrp.img file and then flash it - very convenient! So more appropriately it should be labeled "Flash (or Install) Current TWRP as Recovery Ramdisk". Both features enable booting into TWRP rather than the ROM's built-in recovery when choosing to boot into Recovery.
So here's my report:
(Almost) all ¹ is working mighty fine on my new Nokia 6.1 with the official LineageOS 18.1 (Android 11) ROM, except three things (+ one feature missing):
1) After (while booted into LOS) formatting my SD card as internal and having LOS move all data from phone internal to SD, making the SD card the only/ exclusive Internal, TWRP does't or can't access the SD card anymore.
As supposed, I have a PIN set in LOS. Once TWRP has booted, I enter the PIN as requested by TWRP, but after doing so, only see (as before with the SD as mobile storage) that DATA gets decrypted successfully, but no mention of or even an attempt to also decrypt the content of the SD card.
In TWRP storage picker, I do see my SD card with full size (appr. 128 GB), + Internal Storage (19 of the nominal 32GB). But regardless if I choose Internal Storage or MicroSD, TWRP does not see my previous backups (which are now on the encrypted "internal" SD).
Same in TWRP File Manager: the content of the SD formatted as and then dedicated as sole internal and thus encrypted by LOS does not show up anywhere (SDCARD/ SDCARD1/ Storage/ mnt etc.).
Still, after choosing "Internal Storage" as backup location, TWRP does backup. Afterwards I can choose that backup via "Restore", and also see it in File Manager in /sdcard/TWRP. But when I boot LOS, I do not see the new backup in /sdcard/TWRP, only the older ones. The new backup is nowhere to be found, not even via FX File Manger with root privs, querying the entire file System. Obviously TWRP created the backup into the phone's real internal, but LOS has blinded that out after migrating Internal -> SD, most likely by means of a virtual symlink internal /sdcard -> external /sdcard1, and TWRP does not honor that.
Therefore backup options right now are:
- backup to USB via OTG (only partially working, see 3) below)
- backup to internal phone storage, then (while still in TWRP) move (copy then delete) the backup via MTP from internal to a storage on one's computer
All that said, the following (non-exclusionary) questions arise:
1. Are you aware of that?
2. Can you or somebody else reproduce this?
3. Is this fixable somehow, either in TWRP or in LOS?
4. Is this a shortcoming of TWRP in general, failing to also decrypt an SD card if a) it's formatted as internal and b) serves as the phones *only* internal?
5. Or is that an issue that only arises with LOS (18.1) but not with other Android 11 ROMs?
I hope some insights on this issue can be shared and gathered, or even better a fix
2) fastboot reboot recovery doesn't work for me; instead my ROM boots.
Nokia connected to my Mac via USB cable and booted into bootloader. Active slot is the correct one with TWRP and my ROM (LineageOS 18.1, Android 11).
I can however boot TWRP just fine via key combo (Volume Up + Power), and also via Magisk in LineageOS, so it's installed correctly.
3) USB OTG is only working with limitations:
works if TWRP was flashed/ installed as per instructions above, then (with the device powered off and (via USB cable) either connected to your computer or plugged into your charger) boot TWRP via the Power/ Volume Up key combo. (This also works in native install - not recommended because then standard boot will boot into TWRP as default rather than into your ROM)
- NOT working if booted live!
on your connected USB drive, TWRP only sees the 1st partition with a compatible file system (FATxy, ExFAT, ExtFS) incl. the EFI partition! Therefore make sure a) your USB drive does not have an EFI partition as 1st partition; b) the partition you want to backup to is the 1st with one of the compatible file systems!
4) The "Fix Recovery Bootloop" feature option in the "Advanced" section is missing. I was experiencing a boot loop and had to live-boot another TWRP to execute that feaure, which did fix the issue as expected. @Sid127 it would be great if you could re-add that feature.
________________________________________
¹ run live via fastboot w/o flash, flash then boot, decrypt, backup, restore, USB OTG partially

@BladeRunnerA2C @goodlife1870
has any of you inserted an SD card, and if so, have you formatted it as Internal in Android, and then confirmed when Android asked to move all data from Internal Storage to now "internal" SD, making the SD the only internal?
And if so, can TWRP see that?
For the context see my previous post. Trying to narrow things down.

Does fastboot reboot recovery work for anybody? Instead my ROM boots.
Nokia connected to my Mac via USB cable and booted into bootloader. Active slot is the correct one with TWRP and my ROM (LineageOS 18.1, Android 11).
I can however boot TWRP just fine via key combo (Volume Up + Power), and also via Magisk in LineageOS, so it's installed correctly.
When you share if it's working or also not working for you, please let us know your OS + version of fastboot.

twrp-3.6.1_9-0-DRG_sprout.img | ChangeLog

@RootedLee
1 and 3) If I'm not mistaken, SD card as internal is only supported by the ROM, and not by TWRP, and has been a limitation since Marshmallow days. As for USB OTG, most people don't use partitioned USB drives, and hence TWRP returns after finding the first compatible partition.
2) fastboot reboot recovery isn't a valid command on our device, sadly, since the recovery image is embedded in the boot image and not its own partition.
4) I sadly have no control over TWRP features, I can only work on device side things.

hey @Sid127 Friendly Neighborhood Cacodemon, good to hear from you
SD card as internal can't generally be accessed by TWRP if encrypted: OK, bummer - esp. in the light of that you say it's been requested/ suggested since "prehistoric" times. Needless to say it's feasible technically because TWRP can decrypt /Data. Oh well..
TWRP USB OTG:
a) only finding the first compatible partition: as long as only attaching a USB flash drive - OK. But when attaching an external hard disk whose 1st partition usually is the ESP when it's partitioned as GUID, that's inconvenient. At least a function to skip the ESP would make a lot of sense.
b) reliability: does it always work on your Nokia and in any scenario, regardless if you boot into TWRP via key combo after powering on, or from your running ROM?
2) fastboot reboot recovery & 4.) OK, gotcha
BTW did you do the current 3.6.1 port for this Nokia?

@Sid127 I have a (hopefully simple to implement) request: could you add the "Fix Recovery Bootloop" patch into the "Advanced" menu? Because for the Nokia 6.1 (2018) it's necessary.
Would be really awesome if that's not too much out of your way

RootedLee said:
hey @Sid127 Friendly Neighborhood Cacodemon, good to hear from you
SD card as internal can't generally be accessed by TWRP if encrypted: OK, bummer - esp. in the light of that you say it's been requested/ suggested since "prehistoric" times. Needless to say it's feasible technically because TWRP can decrypt /Data. Oh well..
TWRP USB OTG:
a) only finding the first compatible partition: as long as only attaching a USB flash drive - OK. But when attaching an external hard disk whose 1st partition usually is the ESP when it's partitioned as GUID, that's inconvenient. At least a function to skip the ESP would make a lot of sense.
b) reliability: does it always work on your Nokia and in any scenario, regardless if you boot into TWRP via key combo after powering on, or from your running ROM?
2) fastboot reboot recovery & 4.) OK, gotcha
BTW did you do the current 3.6.1 port for this Nokia?
Click to expand...
Click to collapse
yes indeed, 3.6.1 is also out, and it supposedly fixes adoptable storage, so maybe give that a whirl
RootedLee said:
@Sid127 I have a (hopefully simple to implement) request: could you add the "Fix Recovery Bootloop" patch into the "Advanced" menu? Because for the Nokia 6.1 (2018) it's necessary.
Would be really awesome if that's not too much out of your way
Click to expand...
Click to collapse
as much as I'd love to implement features, there's not much I can do on that front because it's again a source side thing and not a device side thing

You are right - 3.6.1 did fix adoptable storage, thanks for letting me know (that fact slipped my attention somehow).
"Fix Recovery Bootloop" patch: OK, gotcha. With 3.6.1 + the latest LOS boot/ recovery that error seems to be fixed anyway
Keep up your friendly neighborhood commitment !

Correction: support for adoptable storage ("AS") is not fully implemented into TWRP 3.6.1:
- in File Manager it's still only the internal storage which shows up
- in the 'Select Storage' dialogue only 'Internal' can be selected, which is still only the internal but not the merged internal/ SD AS
I simply hadn't migrated any data yet which is why all data still resides on internal.
I'm beyond sick & tried of this (not just in TWRP but all across Android) faultily implemented "AS BS" and will revert back to mobile storage for the SD card!

RootedLee said:
will try. Thanks for the links (I had already come across some of them during my research). Quick question in between (just have a minute right now): could it be of any help to edit the twrp.img and replace contained tar binary with the GNU one?
OT: this whole thread should be moved to the TWRP section where it belongs to in the first place because this is a TWRP not a Xiaomi Redmi Note 3 issue to begin with
Click to expand...
Click to collapse
actually (gnu) gtar is only used by my own linux scripts (to imitate twrp look-a-like backup) and schily (standard) star only used by android-backup-extractor. /sbin/tar -> toybox is a symlink, if you want to replace make sure to unlink /sbin/tar first. but it's not used by twrpTar anyway therefore pointless. your backup looks completely broken, try with another backup first. once you ruled out Error 255 you could try to repair backup

@aIecxs smart and circumspect of you to continue the issue (TWRP restore not producing a functional system from FBE (file-based encryption) Data backup after factory reset: either stuck before reaching login screen, or tar error 255 trying to restore Data) here
Now guess what: I'M BACK UP 'N RUNNING !!!! Even (almost) all apps appear to be working fine apart from a few apps which realize that security settings have changed but performed just fine again after restoring from their own built-in backups, see below ¹ (exceptions also see below ²)
Eventually (after all the steps I had already documented in the other thread), here's the only things I just did:
with LOS installed to slot B unencrypted (no PIN), booted into stock TWRP
because the last backup I made with TWRP from my working and encrypted (PIN > FBE) install was in slot A, changed slot to A
thought, what the heck - just try and see if restore of Data (which so far, if I booted into TWRP with an unecrypted Data present and TWRP not asking for the decrypt PW, had always failed with the notorious tar error 255) works, and indeed, it would suddenly run!!!
decided to at this point to only also restore Boot, but not (yet) System
BOOM - back to Homescreen WITHOUT having to enter any PW thus NOT encrypted - Yeeha !!
the Homescreen launcher (stock LOS Trebuchet) was behaving iffy > restart
launcher now working as supposed; everything else (apart from Signal), too, as it seems, incl. Wi-Fi and making calls.
I am not 100% sure but I think the main do-jobbie indeed was
Code:
./busybox gzip -cd data.ext4.win00# | ./tar --selinux --xattrs -P -vxp
run via adb shell, based on your script, along with the special SELinux tar + busybox (all info see here), + the unencrypted install (currently on the other slot), maybe changing the slot to the inactive one and restore form there - I am honestly not sure.
I am SOOO thrilled about your high-profile help (esp. looking at the numerous threads over at TWRP/Issues where people were not able to resolve this). Let me know if I can buy you a coffee or something.
-----------
¹ Apps also running again after restoring their built-in backups: Signal, Swift Backup, Banking4
² Country-specific apps of mine which required a reset by deleting their data: luca, SBB Mobile, Payback)
In general, since some apps rely on software keystore, it is worth making recurring backups of the data/misc/vold folder which is said to contain the keystore files.
-----------
PS: Once all apps are verified running, I'll apply multiple backup tools, not just TWRP..

donate to Sid127 don't thank me

agreed, friendly neighborhood Cacodemon @Sid127 deserves a donation - done !