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
Hey guys I need some help! So I have an AT&T Samsung Galaxy Note II and I am currently on Cyanogen mod (Version: 10.2-20131214-Snapshot-InstallerWPPQ50St0lteatt). I got cyanogen mod by using their simple installer that used to be on the play store. I want to switch to Omnirom but I need step by step instructions to do this. I have CWM. BTW I don't even know if my phone is rooted since I used that simple Cyanogen mod installer. Please Help! Thanks!
Root doesn't matter at this point.
Short version: You can download the t0lte (t0lteatt is deprecated) OmniROM installer (and gapps, assuming you want them) to your phone's SD card, reboot to recovery and install both zip files, clear user data and reboot. First reboot will be a bit longer than usual. But I recommend you stick to the longer version below.
Long version:
Backup your apps using Titanium Backup.
Download OmniROM, gapps and SuperSU to your phone's (internal or external) SD card.
Download TWRP (Teamwin Recovery Project, a touchscreen interface recovery) zip file installer to your SD card. This will allow you to update OmniROM through their OpenDelta system, the ROM is able to automatically download small incremental update files for the latest nightly build, notify you that there's an update and install it in one click. (Put your gapps zip in the /sdcard/OpenDelta/FlashAfterUpdate folder. Mine also has the sensors fix, Xposed framework toggle and one or two other little mods.)
Reboot to CWM recovery.
Install the TWRP zip from SD card
From CWM's advanced menu, reboot recovery. (Or reboot to CM, and recovery again.)
From TWRP, make a full backup.
Once that's done and you're back to the main menu, click "Install" and select the OmniROM zip.
Add the gapps zip
Add the SuperSU zip
Slide to install
Clear user data
Reboot
Proceed with activation, restore your apps and their data.
Enjoy!
Good luck,
Darkshado
Darkshado said:
Root doesn't matter at this point.
Short version: You can download the t0lte (t0lteatt is deprecated) OmniROM installer (and gapps, assuming you want them) to your phone's SD card, reboot to recovery and install both zip files, clear user data and reboot. First reboot will be a bit longer than usual. But I recommend you stick to the longer version below.
Long version:
Backup your apps using Titanium Backup.
Download OmniROM, gapps and SuperSU to your phone's (internal or external) SD card.
Download TWRP (Teamwin Recovery Project, a touchscreen interface recovery) zip file installer to your SD card. This will allow you to update OmniROM through their OpenDelta system, the ROM is able to automatically download small incremental update files for the latest nightly build, notify you that there's an update and install it in one click. (Put your gapps zip in the /sdcard/OpenDelta/FlashAfterUpdate folder. Mine also has the sensors fix, Xposed framework toggle and one or two other little mods.)
Reboot to CWM recovery.
Install the TWRP zip from SD card
From CWM's advanced menu, reboot recovery. (Or reboot to CM, and recovery again.)
From TWRP, make a full backup.
Once that's done and you're back to the main menu, click "Install" and select the OmniROM zip.
Add the gapps zip
Add the SuperSU zip
Slide to install
Clear user data
Reboot
Proceed with activation, restore your apps and their data.
Enjoy!
Good luck,
Darkshado
Click to expand...
Click to collapse
Thanks 4 the help hit thanks
Video?
Thank you so much for the help! I really do appreciate it! Is there any video you could link that gives these instructions but in a video maybe? Just so I don't get confused in the middle of the process. Thanks for the help!
Darkshado said:
Root doesn't matter at this point.
Short version: You can download the t0lte (t0lteatt is deprecated) OmniROM installer (and gapps, assuming you want them) to your phone's SD card, reboot to recovery and install both zip files, clear user data and reboot. First reboot will be a bit longer than usual. But I recommend you stick to the longer version below.
Long version:
Backup your apps using Titanium Backup.
Download OmniROM, gapps and SuperSU to your phone's (internal or external) SD card.
Download TWRP (Teamwin Recovery Project, a touchscreen interface recovery) zip file installer to your SD card. This will allow you to update OmniROM through their OpenDelta system, the ROM is able to automatically download small incremental update files for the latest nightly build, notify you that there's an update and install it in one click. (Put your gapps zip in the /sdcard/OpenDelta/FlashAfterUpdate folder. Mine also has the sensors fix, Xposed framework toggle and one or two other little mods.)
Reboot to CWM recovery.
Install the TWRP zip from SD card
From CWM's advanced menu, reboot recovery. (Or reboot to CM, and recovery again.)
From TWRP, make a full backup.
Once that's done and you're back to the main menu, click "Install" and select the OmniROM zip.
Add the gapps zip
Add the SuperSU zip
Slide to install
Clear user data
Reboot
Proceed with activation, restore your apps and their data.
Enjoy!
Good luck,
Darkshado
Click to expand...
Click to collapse
DISCONTINUED
Sorry .. due to limited time I have stopped this ROM.
Pls find the last downloads here ..
https://androidfilehost.com/?w=files&flid=289294
Thanks for understanding ..
Resurrection Remix for manta ..
RR-P-v7.0.0-20190208-manta-Unofficial.zip
Known issues:
- HWC (hardware composer) is partly broken (icons are not shown correctly and black home screen)
- NavBar is not visible - same hwc issues like above !
- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.
- NFC has been taken out - still not working.
- Camera is not working .. same problem like on Nougat. (broken HAL1 camera and unsupported HAL2 camera)
- If you set pin, pattern or password to unlock the device pls be patient - if you press "confirm" the system is freezing for a few minutes - just wait.
RR-O-v6.2.1-20181209-manta-Unofficial.zip
Known issues:
- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.
- NFC has been taken out - still not working.
- Camera is not working .. same problem like on Nougat. (broken HAL1 camera and unsupported HAL2 camera)
- If you set pin, pattern or password to unlock the device pls be patient - if you press "confirm" the system is freezing for a few minutes - just wait.
System and Cache repartitioning / Opengapps: Error 70
The current system partition is (getting) full !
You need to do repartition your system and cache partitions .. either via TWRP package or manually via shell.
It's an one time task.
But the filesystem of the system.img inside the ROM will keep always the same size .. approx. 800mb.
The filesystem does not know the "real" size of the actual partition.
In general .. If you install an image into a partition the filesystem will have the size of the image (in our case 800mb).
The free space we got thru repartitioning needs to be allocated again.
For this reason we need to enlarge/resize the filesystem after each ROM update and/or clean install.
Only the filesystem .. the partition itself will stay untouched.
The automatic enlarge/resize of the filesystem is part of the ROM installer.
For manual repartitioning have a look here:
https://forum.xda-developers.com/showpost.php?p=77759823&postcount=953
https://forum.xda-developers.com/showpost.php?p=77762148&postcount=954
For automatic repartitioning have a look here:
https://forum.xda-developers.com/showpost.php?p=77764246&postcount=957
https://forum.xda-developers.com/showpost.php?p=77770425&postcount=960
@ipdev - Thanks for your TWRP flashable repartitioning package !
Installation:
1. Boot into TWRP
2. Wipe system, cache, dalvik and data. (Not required if you upgrade from previous build)
3. Install RR-O-v6.x.x-yyyymmdd-manta-Unofficial.zip
4. install Opengapps or other Gapps package
5. install Magisk.zip
6. Reboot into system ..
- Please install Magisk.zip (17.x) yourself.
- If you had gapps installed before you don't need to install gapps again - the installer will take care.
- If you face any strange issues, pls do a factory reset via TWRP first.
SOURCES:
If you want to build your own ROM ..
https://github.com/followmsi/manifests/tree/manta-rros-lineage-16.0
https://github.com/followmsi/manifests/tree/manta-rros-lineage-15.1
Download:
https://androidfilehost.com/?w=files&flid=289294
https://drive.google.com/open?id=0By6p5AdQfavBNHkxVWhNOW5CdVk
Enjoy Resurrection Remix on your Nexus 10 ..
Finally it's own thread ..
August 2018
RR-O-v6.1.0-20180814-manta-Unofficial.zip
Changes:
- Google August 2018 Security updates
- Adjust DRM blobs
- ro.opa.eligible_device=true -> Google Assistant
- Latest LineageOS and RR changes
Enjoy
Awesome mate. You never think for abandon the old device. Thanks for your patience and dedication to the device.
Here one thing I want to know, is it first needed the lineage-xx.x-yyyyyyyy-UNOFFICIAL-manta.zip to flash on the device what you have mentioned on your first post then the RR-O-v6.1.0-20180814-manta-Unofficial.zip on the second post.??
Again appreciate your hard work Thanks so much.
Triggered from RN5pro
amitroutray said:
Awesome mate. You never think for abandon the old device. Thanks for your patience and dedication to the device.
Here one thing I want to know, is it first needed the lineage-xx.x-yyyyyyyy-UNOFFICIAL-manta.zip to flash on the device what you have mentioned on your first post then the RR-O-v6.1.0-20180814-manta-Unofficial.zip on the second post.??
Again appreciate your hard work Thanks so much.
Triggered from RN5pro
Click to expand...
Click to collapse
No .. RR is it's own ROM .. Even it's based on Lineage you don't need to install it first.
Just corrected the typo ..
3. Install RR-O-v6.x.x-yyyymmdd-manta-Unofficial.zip
Cheers
followmsi, great work, thanks.
FYI I think this latest build might be a little bigger than previous builds? I used your pico w/ the 6mb buffer, and it was still giving me the not enough space error. I tried it with latest open gapps and changing buffer to 2mb, with the same result. So I deleted some system apps like Easter egg, calculator, camera, etc., and then the pico gapps installed. Then I reinstalled the ROM to get those apps back, realizing that the ROM keeps existing gapps (thanks for mentioning it). Seems to have worked.
Giving it a test run over the next couple days. I used f2fs for data and cache, btw. Thanks again.
Edit: I got the google play services error and reinstalled like this: wipe system, install ROM, delete camera and onetimeinstall and calculator (IIRC), install latest pico open gapps w/ 6mb mod. Took a few flashes and reboots for magisk to install. Everything seems to be working now, at least everything that is supposed to work for oreo on N10. Seems pretty smooth.
Wow this is great, can I dirty flash this over the recnt nougat build? RR-N-v5.8.5-20180413-manta-Unofficial.zip
yeoldeusrename said:
followmsi, great work, thanks.
FYI I think this latest build might be a little bigger than previous builds? I used your pico w/ the 6mb buffer, and it was still giving me the not enough space error. I tried it with latest open gapps and changing buffer to 2mb, with the same result. So I deleted some system apps like Easter egg, calculator, camera, etc., and then the pico gapps installed. Then I reinstalled the ROM to get those apps back, realizing that the ROM keeps existing gapps (thanks for mentioning it). Seems to have worked.
Giving it a test run over the next couple days. I used f2fs for data and cache, btw. Thanks again.
Edit: I got the google play services error and reinstalled like this: wipe system, install ROM, delete camera and onetimeinstall and calculator (IIRC), install latest pico open gapps w/ 6mb mod. Took a few flashes and reboots for magisk to install. Everything seems to be working now, at least everything that is supposed to work for oreo on N10. Seems pretty smooth.
Click to expand...
Click to collapse
Yes .. it's actually 2 things .. gapps pico packages has been grown ... From ~105mb (may) to ~125mb (today)
As well RR made some additional changes (not part of lineage code) to optimize the compression of aapt. (.apk sizes)
I have taken out the changes now.
For next release camera will be taken out from build.
You may take gapps config file using "smallbuffer" parameter to use 2mb right away.
Or change buffer inside installer to another value.
Similar problems will happen for los-15.1 if the pico gapps size is still growing.
someguyatx said:
Wow this is great, can I dirty flash this over the recnt nougat build? RR-N-v5.8.5-20180413-manta-Unofficial.zip
Click to expand...
Click to collapse
Yes, still take backup before.
Wipe system and install ROM and pico gapps and maybe magisk.
Wipe cache and davlik and reboot into system.
Good luck !
@followmsi I am getting Error: 7 while flashing the ROM.
Triggered from RN5pro
followmsi said:
Yes, still take backup before.
Wipe system and install ROM and pico gapps and maybe magisk.
Wipe cache and davlik and reboot into system.
Good luck !
Click to expand...
Click to collapse
Thanks I will give it a try tonight. Nothing important enough to backup this is just my entertainment tablet.
amitroutray said:
@followmsi I am getting Error: 7 while flashing the ROM.
Triggered from RN5pro
Click to expand...
Click to collapse
Wipe system before rom install and get started again.. use older gapps because of space situation on system partition.
followmsi said:
Wipe system before rom install and get started again.. use older gapps because of space situation on system partition.
Click to expand...
Click to collapse
I always do a clean flash. Wiped System, Data, Delvik Cache & Cache. Downloaded the Gapps mentioned on the OP.
Triggered from my Nexus 10
amitroutray said:
I always do a clean flash. Wiped System, Data, Delvik Cache & Cache. Downloaded the Gapps mentioned on the OP.
Triggered from my Nexus 10
Click to expand...
Click to collapse
For now .. after ROM Installation and before gapps installation do mount /system in twrp - but untick read-only.
Go to system/app (priv-app) and remove the camera2 apk.
Unmount system and install mentioned gapps pico.
It's a space problem !
Will check if I can reduce system space usage a bit more ..as well reducing buffer for gapps down to 2MB.
Cheers
followmsi said:
Wipe system before rom install and get started again.. use older gapps because of space situation on system partition.
Click to expand...
Click to collapse
This process worked except I had to do this to get gapps to work
“For now .. after ROM Installation and before gapps installation do mount /system in twrp - but untick read-only.
Go to system/app (priv-app) and remove the camera2 apk.
Unmount system and install mentioned gapps pico.”
One more question do I need to install that audiojack kernel or is already in the rom?
someguyatx said:
This process worked except I had to do this to get gapps to work
“For now .. after ROM Installation and before gapps installation do mount /system in twrp - but untick read-only.
Go to system/app (priv-app) and remove the camera2 apk.
Unmount system and install mentioned gapps pico.”
One more question do I need to install that audiojack kernel or is already in the rom?
Click to expand...
Click to collapse
Audio jack kernel is part of this ROM ..
Depending on the gapps package size you may have to delete camera2.apk - to increase free space for gapps installation.
September 2018
RR-O-v6.2.0-20180909-manta-Unofficial.zip
Changes:
- Google Security updates -> September 2018
- moved shim libs to vendor
- Latest LineageOS and RR changes (update to version 6.2.0)
Enjoy
Hi !
I flashed the September version with a clean flash (full wipe). I tried to flash both "manta_open_gapps-arm-8.1-pico-20180702-UNOFFICIAL.zip" and "open_gapps-arm-8.1-pico-20180902-UNOFFICIAL.zip" from your GDrive, but after a (sucessful) flash in TWRP 3.2.0, the First time Pixel setup has Google Play services crashing in loops in anytime.
This prevents me from going further into using Gapps.
I also tried removing stuff from priv-apk in system, but I couldn't find the camera apk. I got rid of EasterEgg, but that didn't cut through.
Any help for troubleshooting ?
Don Moahskarton said:
Hi !
I flashed the September version with a clean flash (full wipe). I tried to flash both "manta_open_gapps-arm-8.1-pico-20180702-UNOFFICIAL.zip" and "open_gapps-arm-8.1-pico-20180902-UNOFFICIAL.zip" from your GDrive, but after a (sucessful) flash in TWRP 3.2.0, the First time Pixel setup has Google Play services crashing in loops in anytime.
This prevents me from going further into using Gapps.
I also tried removing stuff from priv-apk in system, but I couldn't find the camera apk. I got rid of EasterEgg, but that didn't cut through.
Any help for troubleshooting ?
Click to expand...
Click to collapse
- install latest TWRP (3.2.3)
- Wipe systen first.
- Install current ROM
- Install just one Gapps package (manta_open_gapps-arm-8.1-pico-20180702-UNOFFICIAL.zip - buffer has been reduced to fit into manta system partition)
- Wipe cache / dalvik
- Reboot system
If SetupWizard is crashing we will need logs for further troubleshooting.
Somehow it immediately worked by following closely your instructions. I must have done something wrong before then.
Thanks a lot still, and very kudos for this ROM : )
root access
Fyi it did not like addonsu 15.1 for what ever reason, it was flashed via TWRP and turned on in dev mode but never gave access .. However Magisk flashed fine from TWRP and gave root access so no problem. had to have my Adaway from XDA.