▐▄▀▄▀▌ TUTORIAL CWM roms are the way to go right now!!!
THIS IS A TUTORIAL TO GET CWM ROMS UP AND RUNNING ON UR RHODIUM
SO i felt completely compelled to share my amazing experience and results with my CWM rom!!!!
i almost always try to keep the development process here away from other sites
if you want a REALLY GOOD WORKING version of android on your device without trying NAND ... follow my instructions...
first off i have a ATT Tilt 2 i have been using with this..
to find anything you need to know on android for our phones go HERE
(Neopeek site)
any size card should do for runing CWM builds,,, i however am runnig an 8gb class 4 sdhc and all is well
MY recommended partition sizes... (i set 300mb as all my EXT2 partitions just to make calculating it easier...)
(primary) FAT32 - storage for music videos pics etc... rest of space
(primary) EXT2 - 200-300mb (system) holds rom build... none are over 250mb
(primary) EXT2 - 200-300mb (data) data for android... i believe is the space for app install... so bigger is better..
(primary) EXT2 - 50-100mb (cache) like ram sorta...
with these sizes... worryin about the size of the rom will not matter ..
look on the site link i posted above on how to install and use CWM if you havent before... (dont worry newbs... its easier then everyone makes it seem...)
with CWM builds the standard Gapps are not included...
THIS SITE is the repository to go to... i am using "gapps-hdpi-20101114-signed.zip" but feel free to try others to see if they load...
this is the the most frustrating part of CWM, finding GAPPS that install...
u install them the same way you do a rom... by installing the zip from the sd card...
i do recommend installing gapps zip after you have already installed the rom and booted and restarted android a couple of times
otherwise i recommend THIS ROM as it is the one i use... i know it is only Froyo but it has a themed gingerbread taskbar with black pull down so it still looks nice!!!
lastly
((((technically test kernel.. so not recommended!!... but proven to fix screen not coming on problem...))))
for you crazy tester ppl waiting for the day you brick your phone(im totally kidding dont worry newbs) i use the WIS-Tilt2 kernel the newer test one to be specific...
GO HERE
With this kernel my device goes in to deep sleep with the GReen light and wakes up perfect every time!!!!!
the zip is just modules package and a zImage.. just have to replace and boot...
WARNING... when i updated with the working kernel it looked like it wasnt going to work.. didnt seem to be anywhere enough scrolling text and the boot animation barely played and then the screen went black... i played around with the buttons and found the device to be opperating with out the screen on i kept pressing buttons and the screen finally woke up!!!! be patient!!!! after that it worked perfectly everytime...
other tips... for people experiencing wifi unable to scan problem ..
use the Wifi-nvram.txt trick look it up in xda... once command is entered no need to reboot just turn on wifi and connect!!!
i hope that this has been helpful i couldnt find any where that had all the tips and tutorial in one place to get CWM up and running at least once... had to do it trial and error.. hope my hard work will help you newbs out!!! hahaha
---
Here is the CMW version of the normal FRX06 by arrrghhh. Credits to arrrghhh for the build and to preston74 for making it ready for CMW.
G-apps are already included in this build so you don't have to flash them separate.
http://www.multiupload.com/2VS5ZKUFBA
jellenl said:
Here is the CMW version of the normal FRX06 by arrrghhh. All credits goes to him, I only made it ready for clockwork mod. Gapps are already included so you don't have to flash them seperate with this build.
http://www.multiupload.com/TQSN4TG28U
Click to expand...
Click to collapse
thanks guy...
\
i want to make it as easy on peopl eto get a stable working version of android on their TP2's
Well, i used CWM with an 1GB SD and worked like a charm...
and first time i did it with a 2gb... i just said more cause there is more room for apps... lol
should prolly clarify that...
Trekfan422991 said:
thanks guy...
\
i want to make it as easy on peopl eto get a stable working version of android on their TP2's
Click to expand...
Click to collapse
Yes you are doing a good job
I first made a cmw version of frx06 without gapps, but argghhh told me it was ok if I include the gapps, so I did
You may also integrate my link in your first post, then I'll delete my post.
Forgive me here... I am new to the CWM builds. If I have a CWM build on an SD card, with the appropriate ex2 partitions and all, can I use CWM to put on a different build? That would be a whole lot easier than having to reformat and start over...
Well if you run in to any problems the support here is going to be limited.
On the other hand if you use XDAndroid the support here is maximal.
For testing and dev reasons, I will stay with my current build. I quite like my bluetooth.
For any beginners I would very much recommend that you use 'standard' (see intro to android sticky). Well, at least until you are confident you don't need to be hand-guided through this and know what to do if something goes wrong.
ppcfly said:
Forgive me here... I am new to the CWM builds. If I have a CWM build on an SD card, with the appropriate ex2 partitions and all, can I use CWM to put on a different build? That would be a whole lot easier than having to reformat and start over...
Click to expand...
Click to collapse
It actually is pretty easy - you can backup your current system & data partitions, and throw a new build on - if you don't like it, wipe and revert to the backup.
The only problem is if you have CWM installed, other 'normal' (looped mount) builds will not work - the rootfs will see the partitions and think you want to run from partitions - of course, this results in a failure to boot... I like having many builds on my card at one time so I can flip between them - this also makes testing a heckuva lot easier, so heads up folks!
Nice tutorial and thanks for putting my build in it,but you should put proper credits as Neopeek(and his team) made cwm and i made the build you linked(you can avoid doing this)
And it's gingerbread like themed and the theme name is minimal green..
You can avoid doing 300 mb system as almost all the builds are less than 100 mb,so doing it 150mb is good
CWM and loopmounted builds can co-exist.
arrrghhh said:
The only problem is if you have CWM installed, other 'normal' (looped mount) builds will not work - the rootfs will see the partitions and think you want to run from partitions
Click to expand...
Click to collapse
To avoid this you can just add the "no_partitions" (without the quotes) switch to your cmdline on your startup.txt of the loopmounted build and you should be good to go.
It may depend on your rootfs, but I'm using F22's rootfs and it works like a charm.
i'm trying cwm with frx6 and it keep saying fail rootfs., what am i doing wrong?
Do you followed the tutorial on how to set up your sd-card for cmw? I think you are using a wrong rootfs. As far as I know you need the rootsf from neopeek's cmw.
jellenl said:
Do you followed the tutorial on how to set up your sd-card for cmw? I think you are using a wrong rootfs. As far as I know you need the rootsf from neopeek's cmw.
Click to expand...
Click to collapse
i"ve gotten into CWM but now its telling cand find the zip find even after scroll down to the update. do need to just rename update_frx6 to just plain update. It say installation aborted. I'm using update-frx6
drynaps said:
To avoid this you can just add the "no_partitions" (without the quotes) switch to your cmdline on your startup.txt of the loopmounted build and you should be good to go.
It may depend on your rootfs, but I'm using F22's rootfs and it works like a charm.
Click to expand...
Click to collapse
Damnit, hyc even told me about this - and I forgot about it.
Thanks for mentioning it!
villa15 said:
i"ve gotten into CWM but now its telling cand find the zip find even after scroll down to the update. do need to just rename update_frx6 to just plain update. It say installation aborted. I'm using update-frx6
Click to expand...
Click to collapse
I think you are choosing the wrong item in cmw, you need to choose 'Install zip from sd-cart' and then 'choose zip from sdcard'. Don't choose 'apply sdcart/update.zip' or something like that.
And if that doesn't work, maybe try another build. There is a (really small, because I tested it myself) option that the frx06 cmw build doens't work well.
jellenl said:
I think you are choosing the wrong item in cmw, you need to choose 'Install zip from sd-cart' and then 'choose zip from sdcard'. Don't choose 'apply sdcart/update.zip' or something like that.
And if that doesn't work, maybe try another build. There is a (really small, because I tested it myself) option that the frx06 cmw build doens't work well.
Click to expand...
Click to collapse
No thats not it. i did just just what u are saying. I even tried the CherryPieV3 and it still installation aborted. I'm using CWM 1.8 could that be the problem
If you already have CWM files on your phone, then do not just install the CherryPieV3.zip file. You must extract the zip file which has another zip file inside that you should use to install in CWM.
bleuleon said:
If you already have CWM files on your phone, then do not just install the CherryPieV3.zip file. You must extract the zip file which has another zip file inside that you should use to install in CWM.
Click to expand...
Click to collapse
Yes, you´re right. But he said that he also tried frx06, and that doesn´t worked for him too, and with the frx06.zip bundle, you don´t need to extract it first (if i'm right ;p)
jellenl said:
Here is the CMW version of the normal FRX06 by arrrghhh. All credits goes to him, I only made it ready for clockwork mod. Gapps are already included so you don't have to flash them seperate with this build.
Click to expand...
Click to collapse
I tried to install your CMW version of he Arrghhh FRX06 build but it fails on installing.
I have followed all the steps closely but still can't get it installed.
In the CWM tool when I choose Install zip from SD card and then choosing the FRX06 update the install process starts and within a few seconds aborts.
This is what I see on my screen:
Installing: // sdcard/npkboot/update-frx06.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted
Using the FRX06 CWM build from this thread with the WIS-Tilt2 kernel.
Does anybody have a clue about why this is not working?
Related
hi guys,
i am a total noob to android and i just bought a vibrant(used)
it has the firmware version 2.1-update 1 .
i have rooted the phone and now have super user permission(downloaded update.zip and went to recovert mode).
and installed titanium backup then rom manager..
backed up too and flashed the clockworkmod recovery 2.5.1.2 .
then downloaded the custom rom "nero beta 3 with voodoo".
copied it to internal 16 gig storage then went to rom manager then "reboot into recovery"
everything was ok untill that point.
but in recovery,i always get blue screen with 4 options and no matter what i tried nothing happens..
please someone help me with this problem..
thanks
Ok, let me take a shot at it
go to your phone /sdcard/clockworkmod and copy recovery-update.zip into /sdcard as update.zip (you might have a file update.zip in there possibly to root your phone, you don't need it, just rename it and archive it for future use if you need to re-root your phone, etc.).
Now reboot into recovery, and select reinstall packages, it will read the cwr update.zip and will go to a similar screen with green text, from there you can select a zip to install, and flash away.
I would strongly suggest though you download a ROM that is not marked as beta - there are a few options available from different teams.
just hit reinstall packages a couple times
lqaddict said:
Ok, let me take a shot at it
go to your phone /sdcard/clockworkmod and copy recovery-update.zip into /sdcard as update.zip (you might have a file update.zip in there possibly to root your phone, you don't need it, just rename it and archive it for future use if you need to re-root your phone, etc.).
Now reboot into recovery, and select reinstall packages, it will read the cwr update.zip and will go to a similar screen with green text, from there you can select a zip to install, and flash away.
I would strongly suggest though you download a ROM that is not marked as beta - there are a few options available from different teams.
Click to expand...
Click to collapse
hi it worked !!
but new problem.. its in clockworkmod recovery and says
"installing: SDCARD:Nero_3TWE_voodoo.zip
Finding update package... "
its been sometime but nothins changes than that
royalkalana said:
hi it worked !!
but new problem.. its in clockworkmod recovery and says
"installing: SDCARD:Nero_3TWE_voodoo.zip
Finding update package... "
its been sometime but nothins changes than that
Click to expand...
Click to collapse
Wait for it to finish!!! It might take a little long.
P.S. You didn't happen to put your ROM zip file on your external card, did you?
lqaddict said:
Wait for it to finish!!! It might take a little long.
P.S. You didn't happen to put your ROM zip file on your external card, did you?
Click to expand...
Click to collapse
no no i read soo many threads so i know the process(theoretically lol )
i put the file to 16 gig internal.. and i got the green screen as u said then it found the rom too ..
i forced to power on and going to try again
please let me know what i should know
thanks
hi it worked it worked !!
thanks lqaddict and jmcghee1973 for ur help.specially lqaddict thanks alot for ur time mate
royalkalana said:
hi it worked it worked !!
thanks lqaddict and jmcghee1973 for ur help.specially lqaddict thanks alot for ur time mate
Click to expand...
Click to collapse
No problem I am glad to help. Enjoy your new Vibrant!
lqaddict said:
No problem I am glad to help. Enjoy your new Vibrant!
Click to expand...
Click to collapse
and can you recommend some stable and good custom roms for me please ?
royalkalana said:
and can you recommend some stable and good custom roms for me please ?
Click to expand...
Click to collapse
It's all user preference
All the current ROM's in the dev section can be considered at this point stable to a degree that the core functionality of the phone is working properly, there might be some quirks with advanced configurations.
Some of the established ROM's are Eugene's Ginger Clone, Team Whiskey Nero and Master's and his team Axura.
My own preference is TW NeroV3 running Supercurio's Voodoo on JL5 build.
Can't go wrong with the latest Voodoo based ROM's, they are smooth, fast and a pleasure to use.
And whoever says that once you flash a custom ROM you are in for a bag of tweaking for the rest of the phone's life I strongly disagree, I can easily see how I can stay with NeroV3 until a stable ROM based on the current iteration of Android OS - Gingerbread - appears here.
P.S. Just be careful when you flash from ROM to ROM, the current ROM's the incorporate Voodoo infused kernels do not require you to disable Voodoo before flashing a Voodoo based ROM, otherwise you must disable it before you flash another ROM. As a common practice, it is best to disable Voodoo before flashing another ROM anyway, and one of the preferred methods is to flash back to stock JFD via ODIN before you flash another ROM to hunt all the ghosts of the ROM past.
Read, read, read and read some more - the Bible in the dev section is a good place to start.
lqaddict said:
It's all user preference
All the current ROM's in the dev section can be considered at this point stable to a degree that the core functionality of the phone is working properly, there might be some quirks with advanced configurations.
Some of the established ROM's are Eugene's Ginger Clone, Team Whiskey Nero and Master's and his team Axura.
My own preference is TW NeroV3 running Supercurio's Voodoo on JL5 build.
Can't go wrong with the latest Voodoo based ROM's, they are smooth, fast and a pleasure to use.
And whoever says that once you flash a custom ROM you are in for a bag of tweaking for the rest of the phone's life I strongly disagree, I can easily see how I can stay with NeroV3 until a stable ROM based on the current iteration of Android OS - Gingerbread - appears here.
Click to expand...
Click to collapse
thanks alot mate..
i think you are saying about this rom
http://forum.xda-developers.com/showthread.php?t=883379
i installed the same
and it is soo cool..
but i dont know what is the difference between voodoo enable/disable.
and couldnt find that disable lag fix file
""" On your internal sdcard, you will find a voodoo folder containing a file called 'disable-lagfix'. This was pre-installed when you flashed. Find it.
Delete the 'disable-lagfix' file from the voodoo folder """
any idea about it ?
thanks again
royalkalana said:
thanks alot mate..
i think you are saying about this rom
http://forum.xda-developers.com/showthread.php?t=883379
i installed the same
and it is soo cool..
but i dont know what is the difference between voodoo enable/disable.
and couldnt find that disable lag fix file
""" On your internal sdcard, you will find a voodoo folder containing a file called 'disable-lagfix'. This was pre-installed when you flashed. Find it.
Delete the 'disable-lagfix' file from the voodoo folder """
any idea about it ?
thanks again
Click to expand...
Click to collapse
Voodoo converts your phone's filesystem to EXT4 (I am not gonna bore you with the technical details ), it is faster better filesystem than the one Samsung implemented. What it does, it virtually eliminates lag when you scroll/open apps, etc.
Now onto enabling/disabling Voodoo.
While your phone is up and running if you press and hold your power button for a few seconds a menu will appear, choose Recovery, and your phone should reboot into modified clockwork recovery, now all your green texts are now bloody red, navigate to Voodoo lagfix option (i think that what it is called, sorry cannot replicate it on my phone it is currently in use ) and you can enable/disable Voodoo from there.
Just let it do its thing, it will take a bit of time to convert the filesystems, do not touch your phone until the process is completed.
lqaddict said:
Voodoo converts your phone's filesystem to EXT4 (I am not gonna bore you with the technical details ), it is faster better filesystem than the one Samsung implemented. What it does, it virtually eliminates lag when you scroll/open apps, etc.
Now onto enabling/disabling Voodoo.
While your phone is up and running if you press and hold your power button for a few seconds a menu will appear, choose Recovery, and your phone should reboot into modified clockwork recovery, now all your green texts are now bloody red, navigate to Voodoo lagfix option (i think that what it is called, sorry cannot replicate it on my phone it is currently in use ) and you can enable/disable Voodoo from there.
Just let it do its thing, it will take a bit of time to convert the filesystems, do not touch your phone until the process is completed.
Click to expand...
Click to collapse
thanks mate.. you've been a big help for me..
btwn.. how could i know that its enable after i did that process ? is there a way for that ?
royalkalana said:
btwn.. how could i know that its enable after i did that process ? is there a way for that ?
Click to expand...
Click to collapse
The bulletproof way is to use a terminal emulator app or use adb to execute the follwing command
Code:
mount
If you see ext4 next to /data, /system, /cache and /dbdata in the output you are golden
thanks lqaddict
Alright! Here it is!
Want an EXT4 compatible bootable CWM SD card?
Done.
You'll need this for installing/maintaining a CM7 build on your NookColor.
All thanks to the excellent NookDevs team!
(you guys are excellent!)
Downloads:
All files, including ext4-compatible build environment, are located here:
http://legacyschool.us.to/nookdev/clockwork/0.1-ext4/
Mirror 1:
http://tsunade.net/nookdev/clockwork/0.1-ext4/ - Thanks tehsu!
Mirror 2:
http://www.r00tyou.com/android/nook/clockwork/0.1-ext4/ - Thanks Reneg4d3 !
Torrents are here:
http://tracker.cryptolect.com/IOM/ courtesy of Vid.
Click to expand...
Click to collapse
Usual instructions are the usuals...
Got an 8gb SD card? Get the 8gb_clockwork file (or smaller).
Got a 1gb SD card? Don't download anything bigger than the 1gb_clockwork file.
Coming soon!
ZIP files for installing/removing EXT4 clockwork to internal storage, and the CM7 O/C kernel installable zip.
Click to expand...
Click to collapse
WARNING:
This WILL NOT work on stock NookColor OS.
It is ONLY compatible with EXT4 partitioning of the internal storage.
If you use this to backup or install anything to your stock NookColor OS, I can't make any promises about what might happen...
Click to expand...
Click to collapse
By the way- my server's about to get hammered, so if anyone wants to post a mirror link (no rapidshare-like sites PLEASE!) I'd be very grateful.
Code:
f957165fd4dd85cdb99deec31f104de6 update-cm-7.0.0-RC1-encore-KANG-signed.zip
Code:
0afa3a3a189914f709dd5f18aadd43cb 128mb_clockwork-0.1-ext4.tar.gz
0aad5d16eb9a274f2a72b12f7be44c55 1gb_clockwork-0.1-ext4.tar.gz
598262de35053f2d34480175ac337d7c 2gb_clockwork-0.1-ext4.tar.gz
71ba12fc908c6bcc643aec6e9359b9f1 4gb_clockwork-0.1-ext4.tar.gz
41ac8d2b425f47db3f811676d35bd904 8gb_clockwork-0.1-ext4.tar.gz
4e9e91930f960d540509f10b0ecfb08b buildenv-0.1-ext4.tar.gz
Want something to test this bootable SD with?
http://legacyschool.us.to/nookdev/cyanogenmod/update-cm-7.0.0-RC1-encore-KANG-signed.zip
Instructions (and a few mirrors):
http://forum.xda-developers.com/showpost.php?p=11452450&postcount=22
Remember: this is NOT final. It may not even install. It may eat your device. IT the clown may come after you... I can't really do much about that...
Before anyone gets upset about a -KANG build released, it's okay, I have permission from the devs, since now all the source is publicly buildable.
If something bad happens, don't blame me, don't blame anyone. Not even your dog.
Be careful: to get back to anything relatively stock, you'd need to use my bootable SD (non EXT4) to apply uninstallclockwork.zip, then format /system, /data, and /cache from the non EXT4 card. Reboot and the device should bootloop 8 times before deciding it's useless and begins to restore the factory.zip.
That should leave you with a completely stock NookColor.
I think.
To install: boot from the ext4 cwm from this thread, format /data and /cache, then install this zip. Done.
DO NOT post here questions about this build. This thread is for the Clockwork card only...
http://tsunade.net/nookdev/clockwork/0.1-ext4/
Mirror'd
If you need anymore mirroring pm me.
Thank you!!
--edit-- what a loooong day. saw this @ 6am and had to go to work.
just getting to flash now. this sd can't format fast enough
tehsu said:
http://tsunade.net/nookdev/clockwork/0.1-ext4/
Mirror'd
If you need anymore mirroring pm me.
Click to expand...
Click to collapse
Thank you!
Hopefully someone wil mirror you CM7 rom. The download is super slow right now.
jkurl said:
Hopefully someone wil mirror you CM7 rom. The download is super slow right now.
Click to expand...
Click to collapse
check http://tsunade.net/nookdev/cyanogenmod/ in about an hour. he should have it mirrored by then.
I'm mirroring CM7
if someone puts up a torrent, i'll seed... im done in 20 min
Backwardsblade said:
if someone puts up a torrent, i'll seed... im done in 20 min
Click to expand...
Click to collapse
Torrent up at http://tracker.cryptolect.com/IOM/update-cm-7.0.0-RC1-encore-KANG-signed.zip.torrent
Thanks Vid!
ALSO!
Anyone caught using a download manager will be banned from my server. I'm sick of this. Splitting your download into 30 pieces and gaming my bandwidth limiting is just rude.
will start seeding in 10..
Can we have md5's for the files please
Backwardsblade said:
will start seeding in 10..
Can we have md5's for the files please
Click to expand...
Click to collapse
Code:
f957165fd4dd85cdb99deec31f104de6 update-cm-7.0.0-RC1-encore-KANG-signed.zip
Code:
0afa3a3a189914f709dd5f18aadd43cb 128mb_clockwork-0.1-ext4.tar.gz
0aad5d16eb9a274f2a72b12f7be44c55 1gb_clockwork-0.1-ext4.tar.gz
598262de35053f2d34480175ac337d7c 2gb_clockwork-0.1-ext4.tar.gz
71ba12fc908c6bcc643aec6e9359b9f1 4gb_clockwork-0.1-ext4.tar.gz
41ac8d2b425f47db3f811676d35bd904 8gb_clockwork-0.1-ext4.tar.gz
4e9e91930f960d540509f10b0ecfb08b buildenv-0.1-ext4.tar.gz
seeding torrent atm, md5 checks!
Thanks again!
http://mother-douchebag.com/update-cm-7.0.0-RC1-encore-KANG-signed.zip
mirrored
Usage notes after 20 minutes of use:
* Feels very snappy.
* Wifi, sound work.
* Switch to the Sliding Tab lockscreen style at Settings > CyanogenMod settings > Lockscreen > Style Options > Lockscreen style. Defaults to Revamped Rotary which doesn't scale right.
* Google apps work. Install from http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps (go to the bottom, CyanogenMod 7 part of the table). Market doesn't show anything under My Apps, but searching does find most of my purchased apps. Some apps don't show up (e.g. ADW Launcher Ex) - I am guessing this is because of the device signature.
* Menu, back buttons in the status bar work great so far.
* Too early to say much about battery other than it doesn't drain the way HCv4 did.
thecubed said:
Torrent up at http://tracker.cryptolect.com/IOM/update-cm-7.0.0-RC1-encore-KANG-signed.zip.torrent
Thanks Vid!
ALSO!
Anyone caught using a download manager will be banned from my server. I'm sick of this. Splitting your download into 30 pieces and gaming my bandwidth limiting is just rude.
Click to expand...
Click to collapse
Seeding now on a fast connection. Thanks for this!
Noob questioning
Sorry but you said "usual instructions are the usual"
So how would I go about making a bootable SD card for CM7?
and what's the buildenv file for?
no bootable sd for CM7, its an emmc rom only.
Nook Color CM7 install instructions
There are a couple of ways to install Cyanogen on your Nook Color. Either of these work fine. I use the ROM Manager approach so I that I don't have to slide out the microSD on every reboot.
Install the recovery using ROM Manager from the Market. You need to root using http://forum.xda-developers.com/showthread.php?t=1054027 first.
Create a bootable recovery SD, boot from it and install Cyanogen.
Step by step instructions for installing Cyanogen using ROM Manager. Up to date as of 2011-10-02:
Follow the instructions at http://forum.xda-developers.com/showthread.php?t=1054027 to root your Nook Color and install the Market.
Using the Market app install ROM Manager.
Launch ROM Manager, install the recovery.
Download the flashable CM7 zip of your choice. I recommend the CM7 nightly from: The CM7 nightly builds.
Download the google apps from one of the links at http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
Copy the cm7 zip, the uBoot .zip and the google apps zip to your SD card.
Use the reboot to recovery option in ROM Manager.
Flash from .zip the cm7 zip and the google apps zip.
Reboot.
Step by step instructions for creating a bootable recovery SD and using it to install CM7. Up to date as of 2011-10-02:
Download the 3.2.0.1 bootable SD recovery image from http://forum.xda-developers.com/showpost.php?p=14462733&postcount=120.
Extract the .img from the archive
Burn the recovery img to an SD card as explained at http://nookdevs.com/NookColor_Rooting#Steps
Download the flashable CM7 zip of your choice. I recommend the CM7 nightly from: The CM7 nightly builds.
Download the google apps from one of the links at http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
Copy the cm7 zip, the uBoot .zip and the google apps zip to your SD card you created.
Unmount the SD card from your PC, insert it into your nook color.
Reboot your Nook Color. It should boot into the SD card recovery. Should read version 3.2.0.1.
Under mounts Format /system, /data, cache. Do not format /boot.
Flash from .zip the cm7 zip and the google apps zip.
Remove the SD card.
Reboot your Nook Color.
Enjoy CM7.
I keep this microSD in my NookColor all the time. When I reboot I remove it just long enough for the uBoot screen to show (Read Forever or the Cyanogen Mod logo) and then put it back in.
Downloads sometimes get corrupted. Verify md5 checksums where possible. Redownload if you have a problem when md5 checksums are not provided.
To be able to use the Netflix app, modify your build.prop to make the device claim it's an HTC Vision.
just flashed this and so far so good. the lockscreen was a little wonky on reboot (it wasn't properly sized and it took a few tries to get the rotary unlock to work.) I might need to futz around with it though.
i was successfully able to boot into CWM, wifi works great, i'm about to flash gapps and play around a bit more.
what can i say: it's CM7! this just made my day and is about to make me late for a business meeting!
I got a nook tablet recently, i registerested it already which i understand you have to do... now i want to backup everything and run regular android as in not B&N version. Im not sure which way to go from here, i see there is an sd option and a regular option?
i was reading this
http://forum.xda-developers.com/showthread.php?t=1439630
as i was getting ready to do it, i started to double think if it was what i wanted.
i want to be able to run the latest android rom possible.
appreciate any help, thanks.
The process you are linking to is very simple and "safe". With the card you create you can startup CWM (ClockWorkMod - utility for flashing and backup and more) and not only root your device, but also make a backup, should you want to go back to where you were prior to flashing whwaever you decide to flash.
The rooting alone lets you install apps from other sources than BN. I think rooted stock tweaked a bit isn't too bad to run actually!
To try out other options completely risk free you can run CM10 (ICS) from an sd card. I do that while I wait for CM10 to be more stable/bug free. It runs incredibly well from sd, and I doubt performance will be greatly enhanced onec I install it internally (as I probably will do at som point.
To run from sd card you don't have to root the device unless you want to.
Great guides for making a sd-card are here and there. For example http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
The first thing I would suggest is to make a bootable recovery SD card using the process and files from here (use the MLO_u-boot_flashing-boot.rar and one of the packages with sdcard.zip suffix), and backup your current stock config and safely save/archive the backup folder -- you'll be glad you have it around one of these days. Make sure that you also keep a copy of whichever recovery program version you choose to use together with the backup folder, since different recovery programs and versions use different backup file archive formats.
If you want to root the NT I would recommend using the update.zip referenced in this post (by liquidzoo) which is more up-to-date than the rooting package you saw (I had used the latter version and had problem updating its Google Store app). Just put this zip package on the same recovery SD card and use the recovery program to install it.
Having tried out the rooted form of the NT for about a week I think it's just marginally better than a stock NT -- there are just so many common apps that are no longer available for the NT's Android version. You would be much better of investing time in going full-fledge CM10, either running off an SD or natively. If you choose to go native CM10 you can revert back to stock using the backup discussed above.
Can you please verify if I am doing the correct thing
@digimax,
I just got my Nook Tablet today, so just wanted to be very clear to make the backup of the current stock config. Here's what I propose to do. Please correct me if I am doing anything wrong.
1) As per you post, I downloaded 3 files
a) MLO_u-boot_flashing-boot.rar,
b) CM9-10_CWM_V6.0.1.2_8-16gb_tools_sdcard.zip,
c) CM9-10_TWRP_v2.2.2.0_8-16gb_tools_sdcard.zip
2) Unzip all the above 3 files
3) Rename the CWM file to recovery.img
4) Rename the TWRP file to altboot.img
5) Copy recovery.img and altboot.img and MLO, flashing_boot.img and u-boot.bin to the root of the SDCard.
6) Insert the SDCard into the Nook Tablet and boot the Nook into one of the recovery and make a backup.
Please let me know if this is the correct procedure.
Thanks!
It looks right, make sure that your boot partition is Primary FAT32 (type 0x0C) with LBA and Active flags set (you can check and set all this using a partition management tool such as MiniToolPartition).
Also, to boot into SD: just turn off the NT and insert a powered-USB cable, and the NT will boot up after a few seconds (assuming that the SD is bootable).
Once CyanoBoot comes up, hold the "N" button to get the boot menu from which you can select one of the two recovery programs.
a lot of this is going way over my head, i need to make sure i go slow and read carefully.
thanks for all the info.
Snjperman said:
a lot of this is going way over my head, i need to make sure i go slow and read carefully.
.
Click to expand...
Click to collapse
Remember that you can make CM10 run totally risk free from am SD-card. That way you can have a smooth running device to explore while you keep reading up on diffrent options. That's what I do! The Tablet doesn't even have to be rooted to do this (mine is though).
asawi said:
Remember that you can make CM10 run totally risk free from am SD-card. That way you can have a smooth running device to explore while you keep reading up on diffrent options. That's what I do! The Tablet doesn't even have to be rooted to do this (mine is though).
Click to expand...
Click to collapse
thats exactly what i want to do, can you link me to the tut you used?
thanks!
Snjperman said:
thats exactly what i want to do, can you link me to the tut you used?
thanks!
Click to expand...
Click to collapse
This is the website I used:
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Look through the comment sections for further clarity on the process.
If that is beyond you, then I suggest getting a pre-made image for the size of SDCard you have and burning your own image. Google AndroidforNook or N2A for the website links.
Snjperman said:
thats exactly what i want to do, can you link me to the tut you used?
thanks!
Click to expand...
Click to collapse
To install and run CM10 off SD card: http://forum.xda-developers.com/showpost.php?p=35245689&postcount=7
To install and run CM10 internally on NT: http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1
attiato year
thank you guys so much!
Hi people. I've been browsing a lot lately and Reading about roms, kernel, and other stuff related to customization of Android devices. I consider myself enough tech-savvy to understand technical things about hardware on this devices but when it comes to all the thing related to flashing roms and kernels and related things i have no clue of what you're talking about, lol.
However, I'm really interested on "installing" Cyanogenmod 10 on my Galaxy Player 4 just to see what happens and how flashing roms feels like, so i can try different roms later and enhance my device. But no matter how hard I try to find a tutorial about how to begin from total stock (as the device comes from the store) haven't been lucky finding one. As far as I know the first step is flashing a new kernet with CWM, so then i can flash the roms. But I'm stuck on Step One :s
So, if there's a link you can post here to help begin with this flashing trend it'd be great. Or if you can redact a "custom" tutorial for me, a total programming noob but interested as hell about modifying my GP4 that would be a thousand times better.
Also, feel free to recommend me kernels or roms or whatever you feel i could use
Thanks!!!
PD: not native english speaker
I just finished doing this exact thing myself, so its fresh in my mind First, BACK UP!! there are different methods with varying degrees of how much they back up, search the forum for them. Definitely backup the efs. Instructions are in the first post for the CM10 ROM. Then, I began by flashing a custom kernel using Odin. Instructions on how to do this can be found in the Tips and Tricks section of this post:
http://forum.xda-developers.com/showthread.php?p=27615927
Kernels can also be found in the appropriate section of that post. Make sure you get one for your device. All of them include CWM (ClockworkMod) which is what you need to easily flash a full ROM. The kernel won't actually effect your current operating system accept to maybe improve performance.
Next, download the ROM file(s) onto your device. ROMs are also in the above post. Again, make sure you get one for your device. Read the instructions in the ROM thread on how exactly to flash them, but the general procedure is to boot into CWM by holding some set of buttons during start up (probably power + volume up) and navigate the CWM menu to flash the ROM.
Sent from my YP-G1 using xda app-developers app
from stock
download odin: https://docs.google.com/file/d/0B2ZcXCdM0CVJS196MFRtaUhfSUk/edit?usp=sharing
boot into download mode
flash terra silent: http://forum.xda-developers.com/showthread.php?t=1643384
download rom and gapps: rom: http://forum.xda-developers.com/showthread.php?t=2233983 gapps: http://goo.im/gapps/gapps-jb-20121011-signed.zip
put on sdcard
BACKUP!!!
flash rom and gapps
reboot
thanks a lot for the help!
Now a question... When you tell me to make a backup, what exactly should I backup and with what program or app? Installed Titanium BAckup app and all i see is the option to backup individual apps. I expected to find something like "total backup of the device" or a similar thing that bacups the whole thing...
please tell me what to use and what to do
thanks a lot again
kennethac said:
thanks a lot for the help!
Now a question... When you tell me to make a backup, what exactly should I backup and with what program or app? Installed Titanium BAckup app and all i see is the option to backup individual apps. I expected to find something like "total backup of the device" or a similar thing that bacups the whole thing...
please tell me what to use and what to do
thanks a lot again
Click to expand...
Click to collapse
Create a backup in cwm
This is so if anything goes wrong, you can get back
Sent from my Kindle Fire running CM10.1/SGT7
Ok i downloaded both Odin and the Terra Silent kernel. Samsung kies is already installed so Odin is detecting my galaxy player.
But the terra silent kernel is a zip file, if i extract it the extracted file has no extension, only says zlimage and i have no idea what it is. Then, when I open Odin, there are the next options:
PIT
BOOTLOADER
PDA
PHONE
CSC
where should i upload the zlimage?
kennethac said:
Ok i downloaded both Odin and the Terra Silent kernel. Samsung kies is already installed so Odin is detecting my galaxy player.
But the terra silent kernel is a zip file, if i extract it the extracted file has no extension, only says zlimage and i have no idea what it is. Then, when I open Odin, there are the next options:
PIT
BOOTLOADER
PDA
PHONE
CSC
where should i upload the zlimage?
Click to expand...
Click to collapse
That's because you're suppose to flash it via CWM. If it's a tar file, you flash it via Odin. And you're not suppose to extract it, lol.
TheKryptonite said:
That's because you're suppose to flash it via CWM. If it's a tar file, you flash it via Odin. And you're not suppose to extract it, lol.
Click to expand...
Click to collapse
haha ok i'm not extracting it anymore. But from those options that shows Odin, where i have to upload the "TerraSilent_usa-1.3.5" file?
This is what i see...
PIT
BOOTLOADER
PDA
PHONE
CSC
that's where i need help for the moment
kennethac said:
haha ok i'm not extracting it anymore. But from those options that shows Odin, where i have to upload the "TerraSilent_usa-1.3.5" file?
This is what i see...
PIT
BOOTLOADER
PDA
PHONE
CSC
that's where i need help for the moment
Click to expand...
Click to collapse
PDA is the one, I believe.
Is Terra Silent compatible with CM10??? Reading the thread of Terra Silent a user made a comment on this asking the developer (i guess) to make Terra Silent compatible with CM10.... :s
ok now i have some problems...
got to flash the Terra Silent Kernel. After rebooting everything was ok. Installed Rom Manager in order to install CWM. Rom Manager installed CMW and then came back to main menu. There was an option for creating a copy of the stock rom, thought it wolud be a good idea to make a copy. When i did it, phone went black and then reboted. after rebooting came back to the lock screen but changed language (spanish -> english). Algo noticed there was missing the google search bar. When entered to the apps menu there were a lot of icons of the android robot with an SD card symbol over. When clicked them it says that the apps are not installed on the system.
installed rom manager again, and went to recovery boot. flashed both cm9 and cm 10 included in the cm 10 thread. Now my playr is stuck in the recovery screen...
what do i do?
kennethac said:
ok now i have some problems...
got to flash the Terra Silent Kernel. After rebooting everything was ok. Installed Rom Manager in order to install CWM. Rom Manager installed CMW and then came back to main menu. There was an option for creating a copy of the stock rom, thought it wolud be a good idea to make a copy. When i did it, phone went black and then reboted. after rebooting came back to the lock screen but changed language (spanish -> english). Algo noticed there was missing the google search bar. When entered to the apps menu there were a lot of icons of the android robot with an SD card symbol over. When clicked them it says that the apps are not installed on the system.
installed rom manager again, and went to recovery boot. flashed both cm9 and cm 10 included in the cm 10 thread. Now my playr is stuck in the recovery screen...
what do i do?
Click to expand...
Click to collapse
Did you wipe the data, cache, and Davik cache?
TheKryptonite said:
Did you wipe the data, cache, and Davik cache?
Click to expand...
Click to collapse
Sorry. False alarm, i finally found i was doing something wrong so corrected it and now i'm using Jelly Bean in my galaxy player. But now there's another problem: system won't read the external SD card.
How can i fix this?
kennethac said:
Sorry. False alarm, i finally found i was doing something wrong so corrected it and now i'm using Jelly Bean in my galaxy player. But now there's another problem: system won't read the external SD card.
How can i fix this?
Click to expand...
Click to collapse
You internal SD card is probably switched for the external.
Find "vold.fstab. (system/etc)" open it, and change "/mnt/sdcard/sdcard1" to "/mnt/sdcard/sdcard0."
TheKryptonite said:
You internal SD card is probably switched for the external.
Find "vold.fstab. (system/etc)" open it, and change "/mnt/sdcard/sdcard1" to "/mnt/sdcard/sdcard0."
Click to expand...
Click to collapse
This is what the file shows:
#internal sdcard
dev mount sdcard / storage /sdcard0 1 /
devices/platform/s3c-sdhci.0/mmc host/mmco
#external sdcard
dev mount emmc /storage/sdcard1 auto /
devices/platform/s3c-sdhci.2/mmc_host/mmc1
what's the part that i have to edit???
kennethac said:
This is what the file shows:
#internal sdcard
dev mount sdcard / storage /sdcard0 1 /
devices/platform/s3c-sdhci.0/mmc host/mmco
#external sdcard
dev mount emmc /storage/sdcard1 auto /
devices/platform/s3c-sdhci.2/mmc_host/mmc1
what's the part that i have to edit???
Click to expand...
Click to collapse
#internal sdcard
dev mount sdcard / storage /sdcard1
#external sdcard
dev mount emmc /storage/sdcard0
Wait, before doing any changes like this, have you tried on going mnt/emmc or storage/sdcard1? @TheKryptonite he have a 4.0 and the sdcard is working without changing the paths.
Envoyé depuis mon Nexus 7 avec Tapatalk
zaclimon said:
Wait, before doing any changes like this, have you tried on going mnt/emmc or storage/sdcard1? @TheKryptonite he have a 4.0 and the sdcard is working without changing the paths.
Envoyé depuis mon Nexus 7 avec Tapatalk
Click to expand...
Click to collapse
That is the same thing four me. I did not have to switch storages at all
Sent from my Kindle Fire running CM10.1/SGT7
TheKryptonite said:
#internal sdcard
dev mount sdcard / storage /sdcard1
#external sdcard
dev mount emmc /storage/sdcard0
Click to expand...
Click to collapse
I did this change, switched numbers and now i can see the files on the sd card. Only that before flashing CM 10 the access to the sd card was through a folder calles "externa sd", now the sd card files and folders are scattered on the home screen of any file explorer i acess the sd card with. It's not a big ideal but i dont like it.
When i edited the file you told me there was a 1 after where now says sdcard 1. Shoud that number be erased or better keep it?
kennethac said:
I did this change, switched numbers and now i can see the files on the sd card. Only that before flashing CM 10 the access to the sd card was through a folder calles "externa sd", now the sd card files and folders are scattered on the home screen of any file explorer i acess the sd card with. It's not a big ideal but i dont like it.
When i edited the file you told me there was a 1 after where now says sdcard 1. Shoud that number be erased or better keep it?
Click to expand...
Click to collapse
I'd keep it.
Haven't seen anyone else discussing this particular solution yet so figured I'd share that we can boot multiple roms using dual boot patcher by @chenxiaolong.
*The only things I'd recommend are the following:
*MAKING A BACKUP FIRST IN RECOVERY. Especially if you've never used the app, this helps in case you misunderstood something or didn't read enough or didn't think enough or the dog ate your homework.
*I recommend using TWRP version 3.0.3-0 which can be found here - https://dl.twrp.me/angler/
* I have not tried this with f2fs only ext4 so naturally I'd only recommend using ext4 partitioning on your device.
* If your device is encrypted in any way booting multiple roms will not work, which should be obvious but I'll state that anyways. Thanks @JKforUA for helping us figure this out.
*If you want to boot more than just two roms, that you use the data slot options for your roms which can be named anything you'd like and they will be stored on the phones internal storage.
* Make sure you're on the latest Radio and Bootloader for the nexus 6p, I flashed this and it works fine and is backwards compatible with Marshmallow roms.
Radio & Bootloader link -
https://forum.xda-developers.com/nexus-6p/general/nexus-6p-radio-bootloader-recovery-t3433637
* Use the patcher app to update the ramdisk and set your primary rom's kernel as Primary before patching or flashing anything.
*If you use the fingerprint scanner you'll have to delete the file /data/system/locksettings.db in each multi boot directory, this disables getting an incorrect pin error when switching roms.
*If using a marshmallow and nougat rom you'll need to flash the appropriate vendor image in recovery before boot.
*Vendor images should not be patched.
This process is fairly simple to me because I've been using it for years but if you have any questions feel free to ask in this thread and hit thanks if I helped ya.
* Before reporting errors I would suggest you try the following steps-
1. Make sure you're using this version of the patcher app because it is the one I have been using without issue -
Version 9.1.0r80-
https://dbp.noobdev.io/files/9.1.0....atcherAndroid-9.1.0.r80.gd5920b2-snapshot.apk
2. Make sure you have enough free space to have two of the zips you want to use because that is what you will have after you patch.
3. Make sure your path to the zip is correct when browsing for the zip, go through internal storage to the directory where the zip is.
4. If you get any error patching, uninstall the patcher app, re-download it, and reinstall it.
5. There is also a Windows version you can try if you prefer.
*If you are still having issues we can discuss it here, and if nobody can seem to come up with a fix in this thread then errors can further be reported by following instructions here - https://dbp.noobdev.io/downloads/
Credits - @chenxiaolong for the patcher app!
Links :
Dual boot patcher (All versions) - https://dbp.noobdev.io
Original forum - https://forum.xda-developers.com/showthread.php?t=2447534
* Screen shots of my current setup attached below for additional guidance if desired.
Status - sharing, using, in some cases testing, always learning (^_-)...
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Thanks for sharing. Used this on my further G4. Didn't know that our device is supported. So no need to wait until multirom is working on 7.1.1. Gonna play around now.
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
DaringDomino3s said:
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Click to expand...
Click to collapse
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
OmegaBlaze said:
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
Click to expand...
Click to collapse
Hmmm I found this
https://forum.xda-developers.com/showpost.php?p=64727670&postcount=8259
I would try re-downloading the app because I haven't had it crash in any roms I've used yet, I just grabbed the latest build, installed, opened, granted root when prompted, updated the ramdisk if needed which is indicated the app, rebooted when prompted, set kernel, and done.
If it's still crashing for you there's the usual force closing the app from your roms settings and clearing the apps cache and data but you probably already tried that?
t83wood said:
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
Click to expand...
Click to collapse
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
DaringDomino3s said:
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
Click to expand...
Click to collapse
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
t83wood said:
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
Click to expand...
Click to collapse
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
DaringDomino3s said:
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
Click to expand...
Click to collapse
Yep looks good!
t83wood said:
Yep looks good!
Click to expand...
Click to collapse
Awesome, thanks, I'll see what happens :good:
Edit: it worked! It's a little more involved than multirom, but it seems to be fine! Easier than I thought.
I've not yet switched between the two, but the app on the secondary (data slot) recognizes the primary
Wow great. Running great on data-slot. Even magisk is supported. Good to have a new playground. Happy to have the 128 GB variant. Gonna do some test with Viper.
How do I switch roms
All perfect. Viper running with magisk. Every rom i tried booting without any problem. So atm the perfect tool to test other rom!
---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------
DEVILOPS 007 said:
How do I switch roms
Click to expand...
Click to collapse
Install dualpatcher app and choose rom in 'ROMs'. Then reboot. Or run utulities in twrp (install).
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Donric13 said:
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Click to expand...
Click to collapse
Okay thanks Bro, I might try out lineage. Also open gaps failed for me bit do I need the rom first or do I need to use dynamic gaps? I appreciate the help!
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Donric13 said:
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Click to expand...
Click to collapse
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
DEVILOPS 007 said:
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
Click to expand...
Click to collapse
Did you flash in twrp (3.0.3.0)? I only use twrp to flash a new multiboot rom. Before flashing a new rom just make sure, you patch all necessary zip files (rom, gapps, etc.). Same name means u choose where (on angler i always choose Data slot - this is internal sd card). Then you give the name (no capital letters) and choose the directory to save the patched file. This you do with every zip file for the rom u gonna flash. The new zip file have the original name and the text "....._data-slot-namegiven.zip" (example for data-slot). The part "data-slot-namegiven" should appeir in every name of the patched zip file. I think with our device it's goot to use the data-slot if you have enough space on your internal sd-card. Using Multi Slot could lead to space problems on system partition of the device. Then just flash the patched files one after another in twrp. Don't forget to flash also patched supersu.zip oder magisk.zip to get root (if it's not in the rom included). You need to patch gapps and supersu or magisk for each slot separately. The name of the patched file just says the path for the multiboot rom. So twrp flashes the patched zip to the right place. Sorry if i wrote to much. Hope it's gonna give you some help. More information you find in the original thread of multiboot.