Related
Hey guys, I just wanted to share my experience so far. I can't post on the MIUI page because I don't have enough posts, so I'll share here for anyone interested.
For anyone wanting to try MIUI for the DX, here's my experience, some tips, and suggestions.
-Beware, installing or trying to install ANY ROM may brick your phone. although it's very rare and unlikely to be unable to find a solution to problems, it can and has happened. so take caution and read instructions and so-forth carefully.
Some history of my DX. I soft-bricked my phone back in the early months of the DX trying to deodex it to install themes. It was stuck on M logo for 2 days before i learned enough from scratch to find out what an SBF was, where to find it, and how to flash my phone back to stock. Ever since then these nice folk on XDA-developers forums and other droid forums have helped me successfully mod my phone many times, through Q&A, detailed instructions, and a little luck.
I've rooted my phone using the command method, Z4Root, and several other processes. Some were hard to figure out, some soft-bricked my phone, most were easy as pie. I'm on a Z4Root atm.
The first successful ROM I installed was GUMMY-JAR. I liked it, it was good to me. nothing like the comprehensive ROMs out now though.
Then I jumped to Liberty 1.5, Liberty x.x etc... Liberty was awesome, but was still basically Froyo with advanced options. I loved it.
Now, just today, I've installed MIUI. And let me tell you, its amazing!
For anyone running Froyo Liberty ROMs, I believe that you can install MIUI right over the top. I didn't think it was going to work, as I hadn't seen anyone mention if it did or not over the top of Liberty 1.5.
If you want to install MIUI, go here. http://forum.xda-developers.com/showthread.php?t=1181486
You MUST be rooted, and be running FROYO, NOT GB! You must also have the Droid X bootstrapper.
I won't give instructions, as I'm not qualified to do so. But I can tell you what I did from Liberty 1.5. MAKE SURE TO MAKE A BACKUP FIRST! 1) I downloaded the MIUI ROM from the above XDA post to my SD card on my phone. 2) I clicked 'bootstrap recovery' on the DX bootstrapper app, then 'reboot recovery.' My phone booted into clockwork recovery mode. 3) wiped data/factory reset. 4) cleared cache. 5) install from SD Card. 6) install MIUI.zip i downloaded from the link i posted above. let it run it's course. rebooted. DONE.
It's really that easy if you are running the DX stock Froyo kernal.
Keep in mind with MIUI, it does NOT auto-sync your Google account. you need to go into the options>>accounts/sync and add your Google account. You can then re-install apps from your backup or just re-download them. Make sure you've synced your contacts with your Google account so they will be there when you add your Google account.
Some thoughts on MIUI...
There is NO STOCK APP DRAWER. I recommend ADW launcher or Launcher PRO. The MIUI launcher inst bad, but it's like iOS in that there's no app drawer. It's just a bunch of screens with all your app icons like an iPhone.
You can download theme's and customize themes through settings>>personal>>theme manager. MIUI allows you to change fonts, boot animation, boot audio, lock-screen style, status bar, icons, launcher, wallpapers, text style, dialer style etc. There's tons of pre-made packages, but you can also change them all individually and create one you like best. You can do all of this directly from the settings menu including looking up new themes, downloading them, and applying them.
MIUI is running on 2.3.4 GB. So it wont say 2.2 anymore after you install. (I believe the kernal is still Froyo though? Please correct me if I am wrong)
I really hope this helps some of you newbies. I am thankful for all of you that have made posts like this that I have found useful in the past.
Note- some people are having issues installing MIUI. They are getting bootlooped on the M logo for some reason. I have no idea why this is, it worked perfectly for me first try. Just remember to follow the instructions on the ROM page, and that you are running the correct version of Android. You shouldn't get a boot-loop if you do so.
Hope this helps!
i have a question.... and this question is what will decide if i keep this or go back to liberty gingerbread....
how the hell do i flash anything.. i can't even install clockwork mod without getting bootloops.... and i'd love to flash certain apps onto this.... but if this can not be done i will have to go back.... the only thing going into recovery does is use the retarded original recovery... and that is a big deal.. if i ruin my phone on the go and need to pullup a backup i can not do this with this rom and i will end up phoneless until i can get to a computer to sbf
nosboost300 said:
i have a question.... and this question is what will decide if i keep this or go back to liberty gingerbread....
how the hell do i flash anything.. i can't even install clockwork mod without getting bootloops.... and i'd love to flash certain apps onto this.... but if this can not be done i will have to go back.... the only thing going into recovery does is use the retarded original recovery... and that is a big deal.. if i ruin my phone on the go and need to pullup a backup i can not do this with this rom and i will end up phoneless until i can get to a computer to sbf
Click to expand...
Click to collapse
What exactly are you asking? "Flashing" is the process of basically overwriting your current Android OS with an Android OS SBF. If you are trying to install MIUI, you cannot do it with Gingerbread installed on your phone. "You MUST be on CyanogenMod 7 or .340 Froyo to flash this rom!" (MIUI)
If you want to install MIUI, i think the best bet would be SBF flashing to stock DX 2.2 .340 FROYO, re-rooting, then using the DX boot-strapper to boot into recovery. Then installing the MIUI .zip from SDcard in the recovery menu. Everything should work fine after that. Rmember you CANNOT go into recovery using DX boot-strapper once this ROM is installed. you CAN go into recovery with this ROM using ROM-manager. This is what I have experienced so far, and what others have said also.
no.. i already have the rom installed... i just want to be able to go into recovery without needing to be booted up.
i'm trying to install some zips through clockwork such as the old blur camera and a few other things... i will install rom manager and see how it goes from there... i love the UI of this rom but as far as being comfortable and stable.. liberty gingerbread has my vote as of now
i've cleared my cache and data several times and i get force closes alot. and this is a clean install coming straight after an SBF.
with liberty gingerbread i had the ability to set it so every phone reboot, even if a battery pull, would boot directly into clockwork mod.. making it easy for me in case i installed a zip that would get me into bootloop
Hmm, sorry mate, I dunno what to tell ya. Try looking aroudn forums or startign a new thread. someone more knowledgable than you or me will help you out.
thanks for everything though!! this really is a beautiful rom and i'd love to stick with it... i'll bite the bullet for the meantime and post around to get some help... i'd love to post in the developer section but i don't have enough posts yet.. haha
nosboost300 said:
no.. i already have the rom installed... i just want to be able to go into recovery without needing to be booted up.
i'm trying to install some zips through clockwork such as the old blur camera and a few other things... i will install rom manager and see how it goes from there... i love the UI of this rom but as far as being comfortable and stable.. liberty gingerbread has my vote as of now
i've cleared my cache and data several times and i get force closes alot. and this is a clean install coming straight after an SBF.
with liberty gingerbread i had the ability to set it so every phone reboot, even if a battery pull, would boot directly into clockwork mod.. making it easy for me in case i installed a zip that would get me into bootloop
Click to expand...
Click to collapse
You need to install Rom Manager, and select flash Clockwork Recovery. Make sure you select Droid X (2nd Init). Then you can reboot into recovery with Rom Manager :-D
laxattack said:
You need to install Rom Manager, and select flash Clockwork Recovery. Make sure you select Droid X (2nd Init). Then you can reboot into recovery with Rom Manager :-D
Click to expand...
Click to collapse
but the problem is that i would like to be able to go into recovery without having to do it through an app... i'd like to make it so every reboot (including battery pull) makes it boot into recovery. thats how i had liberty gingerbread doing it... if not.. i can live with it.. i'll just be a little more careful on what i'm installing
Just wanted to chime in about MIUI rom, I just flashed it yesterday and am ABSOLUTELY loving it thus far. I had no trouble at all installing the rom what-so-ever. I used ROM Manager to do the whole thing: downloaded newest ver. of MIUI, backup current ROM, wipe data and dalvik. Let it run its course and it rebooted and was up and running in no time flat!
Good day all. I recently bought a Nook Color. I'm running CM7.0.2 along with gapps 20110613 from a 16gb SanDisk class 4 SD. When set up the apps (after enabling wifi) I got an error, due to the fact that my sucky router dropped the signal. As a result of this I was not able to download gmail, google maps, etc. My android market runs perfectly but I wanted to flash gapps so as to download gmail and the others. I went into ROM manager and updated to the latest CWM. However, no matter what I do I can't but into recovery. I tried n+power button, reboot into recovery from the power button menu, and from within ROM manager. All no go...it just booted into CM7, so I removed the SD card to boot into stock Nook 1.2 software. When I did this it brought me to the CWM recovery menu (SD card not in). Of course I could not select anything on the menu. Put back in the SD while still in the menu to try select an option but nothing. Shut it down by holding the power button and booted it back up and it went str8 into CM7. Shut down took out SD and it booted into stock Nook 1.2 software. What am I doing wrong guys? I'm trying to flash the overclock kernel and reflash gapps. THANKS
Could the reason gmail, youtube, googlemaps didn't install on setup be due to the fact that I'm not in the USA? If so I'd still like to know what the problem is so I can flash the overclock kernel.
No one has any idea? I know one option is to backup and redo everything, but I'd really like some troubleshooting ideas before.
Did you use the 1.3 image from verygreens thread? If so the old 7.0.* stables are not supported. You will need to back up and redo it either with the old image or a new CM7 version.
---
- Sent from my LG Optimus V using Tapatalk
Yea I used the 1.3 in the thread with 7.0.2. What version cm7 would I need to use with the 1.3? 7.0.3 or a nightly,? Where would I be able to find an older image to work with 7.0.2 and what version of the image should it be?
The 1.3 image won't work with any 7.0.* versions. You should upgrade to either a recent nightly or the 7.1.0 RC. You could find an older image somewhere but there isn't much of a point as you would have to redo it all anyway so why not upgrade? Plus your battery life will improve by a lot as 7.1 RC and the nightlys have deep sleep.
---
- Sent from my LG Optimus V using Tapatalk
As I said many times to newbie who runs CM7 off uSD that do not or should not mess up with ROM Manager. In fact, there are members also confirm that if booting off uSD, ROM Manager has no effect.
Based on what you, OP, described, you had flashed the CwM into the internal memory.
Keep your fingers crossed as I do hope you didn't screw up anything else.
Anyway, using verygreen's 1.3 image along with the latest nightly-built CM7 and the latest 06132001 gapps and boot it off uSD again. You should be fine.
Before that, fix your home wireless network first.
I decided to just go with 7.1RC1 since I wanted the better battery life. Is there a way to check about the CWM on the internal and how would I go about removing it if I did? I ask for warranty purposes ofcourse since I opted for the 2 year extended one. Also to flash upgrades and such, since you don't recomend using ROM manager then how should I go about doing it (i.e. overclocking kernel)?
dna59 said:
I decided to just go with 7.1RC1 since I wanted the better battery life. Is there a way to check about the CWM on the internal and how would I go about removing it if I did? I ask for warranty purposes ofcourse since I opted for the 2 year extended one. Also to flash upgrades and such, since you don't recomend using ROM manager then how should I go about doing it (i.e. overclocking kernel)?
Click to expand...
Click to collapse
1. I never have any issue related to battery with any nightly build that I've ever used. I am currently having the nb153 and it is fantastic.
2. Check CwM and how to remove off the internal memory? I don't know any quick way except restoring the original ROM.
Again, for warranty purposes, strongly suggest running off uSD
3. Updating by loading/copying/dragging the updated files onto the root folder (aka "boot" partition), then TRY loading into Recovery by:
a. combination of power/N buttons if you have skill or
b. let it boot normally into CM7, wait until completely loaded, then reboot and select "recovery" option. Keep yr fingers crossed. This is an easy method but if it doesn't work then option a is the only choice.
Sorry the battery issue was as compared to the current CM7 stable not the nightly. I got everything installed so far besides the overclock kernel. So I will try your recommendation for booting into recovery not using ROM manager.
You don't flash anything when running off an sd card you just boot into recovery and then reboot. Easiest way to get the overclock kernel would be to just upgrade to the latest nightly.
---
- Sent from my LG Optimus V using Tapatalk
Hi guys. I seem to have outdone myself and am now stuck with a phone that plain refuses to boot any more. Let me give you some history so you get the full story.
Not long after I got my U8800 (18 months ago, 'ish) I decided to change my ROM to MIUI because I wanted to get rid of Froyo and Huawei were being incredibly slow to update officially. I did this with minimal troubles and ran it for a long time, updating etc. as needed to be done. Then along came ICS ports and I admit it, I had to fiddle once more...
I downloaded Aurora and read up in here on how to get it on my phone. It seemed before I did anything I needed to set my phone back to the defaults I had and this involved installing Froyo then the latest stock ROM for the U8800. I did all this without hassle and then tried to get the ICS on.
I don't know if it was me, bad reading, something built into the new stock ROM or what, but I could not get the ICS ROM on my phone no matter what I tried. It seemed to have issues deciding if it was rooted or not, it said it was but then failed to work when I needed it to, plus CWM Recovery completely failed to work for me and I just kept getting the stock recovery when trying to boot into it. ROM Manager was also being a pain and kept insisting my phone was a U8160 when previously it had worked as a U8800 (I may have flashed to the U8160 and having thought this I assumed this was my mistake).
I tried various methods of getting to my cust_ folders and manually changing the recovery.img but everything I tried ran into the same "is it or isn't it rooted" problem.
At this point I gave up and stayed with the official stock ROM from Huawei for a bit.
Two days ago I decided I couldn't hack the defaults any more, my phone was slower and I missed the MIUI way of doing things. I decided to have another go!
Ok, we are up to date, thanks for reading so far if you have.
I decided to try getting to the recovery.img again by doing the pink screen and connecting to my PC, problem was when I did this nothing ever showed on my PC, so I looked for other methods.
I uninstalled ROM Manager, because it still insisted I had the wrong phone and found the app, Root Explorer, it worked! Wish I'd have found it weeks ago. I instantly had access to the folders I needed and could mount them etc to overwrite/backup my recovery.img and as I was a little worried about the rooting thing again, despite Root Explorer working I though what harm can it do to overwrite the boot.img too. I did both by copying the originals to my SD Card and pasting the new ones that I had previously placed on my SD Card through the USB connection. I used the files recommended here: http://android.modaco.com/topic/340...-and-then-some-for-the-huawei-u8800-ideos-x5/ and here: http://forum.xda-developers.com/showthread.php?p=14870348
I rebooted the phone and again failed to get into CWM Recovery, just the default Android one.
I then hunted down another recovery and found this: http://www.androidxpert.com/2011/08...k-work-mod-recovery-on-huawei-u8800-ideos-x5/
It worked! I could finally get into CWM Recovery and figured I was home free.
Not so
I then downloaded the same stockwell MIUI I had used previously as I knew that worked, his latest stable version, and dropped the zip on my SD Card. Went to install it and found that CWM Recovery refused to mount my SD Card (16 gig sandisc). Tried a couple more times because I had issues with this card before and then the card ended up corrupted or something because it just refused to work now on anything I had. This was fairly major because I had backed up to this SD Card and forgot to take the backup off and into my PC for safer storage... I know... I do have the back up of recovery and boot.img though on my PC.
It was at this point I noticed I had a boot loop but could still get into CWM Recovery.
Not panicking too much, I tried my old 4gig SD Card, it mounted! I copied the MIUI Rom across to this card, booted into recovery and selected it. It stated it was installing etc but seemed to go pretty quickly. It said it was done so I rebooted as is the norm. Boot Loop. Damnit! Tried this a couple more times, made sure I once again wiped cache, dalvik etc, all of the things it states to do on the ultimate guides etc. Nothing.
Again, still not panicking I thought, fine, I will go back to stock rom. Downloaded the correct one, dropped dload into root, booted using vol + and - and up comes the unpacking screen. Trouble is it refuses to unpack. I quickly look on the net and find that some say if you take the battery out and connect just using the USB it will install it that way, maybe it does for them but it doesn't for me, it just boot loops again.
I am now at my wits end.
I have the feeling its something to do with my changing of the boot.img and I have the original should it be that but I cannot access the insides of my phone through Windows to change anything, plus of course I can't boot the phone due to the loop to change it back using Root Explorer (otherwise it would work anyway).
Is there anything you guys can help me with?
I can install Linux if needed, I read that it lets you view the phones file system better compared to Windows and with my slight knowledge of Linux Id quite expect this but even so, I am not sure what to do.
Any advice/solutions are extremely welcome.
Sorry for the long post, figured I should give as much info as possible.
So what was the latest Huawei official firmware you had on your phone?
What version of CWM are you trying to use?
What version of the huawei official rom did you have on the phone when you tried to install aurora?
What was the last huawei stock rom you tried to install?
Try and get a 2.2 froyo stock rom and flash it using the vol+and- method. This should hopefully get your pink screen back and access to recovery and boot.img. You can then use any recovery earlier then 5.0.2.6 and install stockwells miui.
It sounds like you have a Gingerbread based official rom flashed which you would have needed to flash aurora and are dropping bits into it like boot.img, roms and recoveries which are for froyo.
If this is the case and you can still get into recovery, I would try flash another rom like sbasils miui or wipe everything and format /system and then flash aurora again.
Ok, not sure what changed but, I figured whilst I wait for a reply I may as well keep playing and try to fix it myself still. So I stick my battery back in, was out all night, plug it in the USB as I wasn't sure what juice it had left and turn it on with vol + and - down for that one last try at the default install.
It starts unpacking!
I have no idea what changed, I did nothing different bar having left the battery out all night. Can it have had something in the residual memory?
Anyway, short version. Installed the default froyo, updated to the beta gingerbread (stock and latest).
Back up everything to internal storage this time, just incase and went to superclick to see if I could root it again, it did so. Used Root Explorer to copy CWM Recovery.img over, backed up it all again using CWM to internal, rebooted, worked.
At this point I got silly again and having it all backed up a few ways now decided to try Aurora again, 2.4 this time. It works.
Again, no idea what changed but its going again and after an initial mess with the SC Card again, that works too now.
Sorry to have wasted any ones time with this, though I still really appreciate the reply even if it seems to have fixed itself.
I just wish I was sure what fixed it so It could help others who have the same issue, unfortunately I don't
great stuff, seems upgrades are just a bit hit and miss on this phone. glad it all worked out.
I joined the site about a year ago when I first got my TMobile G2 with the intent of modding it. Since I used it mainly for work, I decided to leave it alone and became a lurker since I didn't have much to offer (info wise). Recently I picked up a Nook Color, and after reading about several different mods, decided on Rack's Dual Boot.
Being a noob to Android Systems (but not to computers), I reread the directions a few times. When I got the gist of what to do, I ran through it with no issues. Turned out to be unbelievably easy. Many Thanks to Racks and everyone else that worked so hard to bring us this awesome information (as a side note F**K those douches that are selling cards on fleabay).
Now to the point; There are a couple of questions/issues I have that maybe someone can help with:
1. Occasionally, when I try and download apps from Play, I get an "error in processing purchase" message. When I power down, then boot back and flash the ICS gapps, everything is fine. I have tried clearing cache and data and get the same error message.
2. In CM7, the Nook Tweak App does absolute wonders for the volume of the crappy little speaker. Anything for ICS?
3. I have LG HBS700 Bluetooth Headphones. They work great in GB CM7, but nothing in ICS CM9.
4. Netflix works like a charm in GB CM7 but bogs and freezes in ICS CM9. Same for Youtube. I have downloaded Flash Player with same results.
5. Lastly, is there any way to get sound INTO the NC? That way I can use the Dolphin Voice Browser, Google Voice Search, etc.
Not big on flashing nightlies. Prefer to get system doing what I want and being stable, then sticking to it.
Many Thanks in advance - Mike
UPDATE:
#1 happened again, and reflashed GAPPS. Got the same error message again. Now, I can't download anything from Play Store in ICS CM9.
??????????????????????????????????????
Mike
gollumses said:
UPDATE:
#1 happened again, and reflashed GAPPS. Got the same error message again. Now, I can't download anything from Play Store in ICS CM9.
??????????????????????????????????????
Mike
Click to expand...
Click to collapse
Sorry to hear ur having issues. Only suggestion I would have is to backup whatever apps you have on CM9 with Titanium Backup or any other app that is capable of doing so. Then download a more recent update of a DualbootSD CM9 from the techerrata server. Copy the zip over to the /sdcard partition of the DualbootSD rom and boot into the CWM that is included with the DualbootSD. Then go to "mounts & storage" and choose to format /system & /data then flash the update you just downloaded. That should fix whatever issues you are having with market.
-Racks
gollumses said:
Now to the point; There are a couple of questions/issues I have that maybe someone can help with:
5. Lastly, is there any way to get sound INTO the NC? That way I can use the Dolphin Voice Browser, Google Voice Search, etc.
Click to expand...
Click to collapse
No. The nook has no microphone and bluetooth Mike inputs don't work either. Sorry.
Thanks Leapinlar.
I pretty much already knew the answer to 5, but asked just in case anyone had gotten something to work.
The rest aren't horrible problems. Thanks to the dual boot card, I just reboot into CM7 to watch Netflix. And by the way, the range with my BT Headset is in feet not inches. I was pretty impressed for having no antenna.
The recent Play thing is a pain though. I will walk through your recommendation and get back.
Thanks - Mike
Attached is what I get with Netflix via ICS
Sorry
Meant my last to say "Thanks Racks and Leapinlars"
Mike
racks11479 said:
Sorry to hear ur having issues. Only suggestion I would have is to backup whatever apps you have on CM9 with Titanium Backup or any other app that is capable of doing so. Then download a more recent update of a DualbootSD CM9 from the techerrata server. Copy the zip over to the /sdcard partition of the DualbootSD rom and boot into the CWM that is included with the DualbootSD. Then go to "mounts & storage" and choose to format /system & /data then flash the update you just downloaded. That should fix whatever issues you are having with market.
-Racks
Click to expand...
Click to collapse
Hey Racks,
Okay, I downloaded the MIUI Updates for the Dual Boot Card and put them on the SD Card. I then booted to recovery and open chose zips from SD Card. Installed both GB and ICS Updates. Rebooted into ICS, and everything looked fine. Tried booting into GB and got a nice MIUI.us Boot Screen, then splash screen looks nice, and as soon as I unlock the device I get: "The application launcher (process com.android.launcher) has stopped unexpectedly" and the same with "media" and "acore"
I tried reflashing the old GAPPS, and nothing. My only two options are "FORCE CLOSE" and "REPORT TO MIUI"
Any suggestions?
Thanks Again - Mike
Okay, now I reflashed CM7 MIUI and can't boot into GB. Stuck at MIUI Boot Screen.
On the good news side; I can now download files from Google Play in ICS. WOW! If it's not one, it's the other. HAHAHA
Issues get fixed, and it's still better than the stock Nook Color.
Can I go back to standard Mirage CM7 and keep MIUI CM9, or is it "all or nothing?"
Thanks Again - Mike
gollumses said:
UPDATE:
#1 happened again, and reflashed GAPPS. Got the same error message again. Now, I can't download anything from Play Store in ICS CM9.
??????????????????????????????????????
Mike
Click to expand...
Click to collapse
Try going into Settings, Applications, Manage Applications, All. Find the Google Playstore app. Clear cache. Playstore will then reload your apps when you start it next. If that doesn't work, clear cache and data. You'll have go through the registration process again, but it may work.
Thanks Shumash.
I finally got Google Play working after installing MIUI Update 03252012 (ICS). My big issue now is with CM7.
After doing the update, as soon as I do the unlock, I start getting error messages (see above). I can't get into anything. I can only reboot or turn off power.
I know I can go back to factory settings, reformat and setup the SD Card, and start all over with Mirage CM7 and CM9. Is there a shorter way? Ideally, I would like to revert MIUI CM7 back to the original Mirage, and leave it be (everything worked fine HAHAHA) until someone comes out with a stable HW accelerator, so I can have my Netflix and YouTube in ICS.
Thanks Again - Mike
Convert2Dualboot-SD Tool
Racks,
I've been using your triple-boot for a couple weeks (works great, by the way--thanks!), and I decided to try your Convert2Dualboot-SD Tool (mainly so that I could have ICS CM9 as my primary). Previously I've had Mirage CM7.2-RC1 from 3-23-2012 in primary and ICS CM9 non-OpenGL from 3-25-2012 in secondary. I downloaded everything, including your newest ICS CM9 non-OpenGL (the 5-1-2012 version), to the Nook, extracted, dropped the ICS CM9 zip into the rom-to-modify folder and the ICS gapps file into the gapps-to-modify folder, opened a terminal session and ran the Android script. Everything seems to have been created fine--the new files were in Primary-Mod. I then went into recovery, formatted system1 & data1, then flashed both the ICS CM9 zip and ICS gapps zip.
When I tried to boot into primary, nothing happened. I then booted into secondary and discovered that the secondary partition had been updated to the new ICS version (5-1-2012). It was flaky, so I went back into recovery and re-applied gapps (this time using the non-modified version). It seems to be working fine now, but is in the secondary partition. My primary is apparently currently empty because of the formatting.
So unless CM9 should never be placed in the primary partition, there seems to be a bug somewhere (at least in the Android version). I did see something in the script that appears to be a problem. Within the "ga" leg, it has this coding:
mv gapps_DualbootSD_alternate_${DATE}.zip ../Primary-Mod/gapps_DualbootSD_alternate_${DATE}.zip
I'm not a programmer, but having "Primary-Mod" intermixed with "alternate" would seem to be problematic. But since this is the "ga" leg, I don't know that this would have caused CM9 to be applied to the secondary partition instead of the primary, so there may be a problem somewhere else.
Do you know if anyone else has successfully applied your modded version of the CM9 rom to primary using the Android script? Or should the existing modded version only be placed in the secondary partition?
Thanks,
oldfolkie
oldfolkie said:
Racks,
I've been using your triple-boot for a couple weeks (works great, by the way--thanks!), and I decided to try your Convert2Dualboot-SD Tool (mainly so that I could have ICS CM9 as my primary). Previously I've had Mirage CM7.2-RC1 from 3-23-2012 in primary and ICS CM9 non-OpenGL from 3-25-2012 in secondary. I downloaded everything, including your newest ICS CM9 non-OpenGL (the 5-1-2012 version), to the Nook, extracted, dropped the ICS CM9 zip into the rom-to-modify folder and the ICS gapps file into the gapps-to-modify folder, opened a terminal session and ran the Android script. Everything seems to have been created fine--the new files were in Primary-Mod. I then went into recovery, formatted system1 & data1, then flashed both the ICS CM9 zip and ICS gapps zip.
When I tried to boot into primary, nothing happened. I then booted into secondary and discovered that the secondary partition had been updated to the new ICS version (5-1-2012). It was flaky, so I went back into recovery and re-applied gapps (this time using the non-modified version). It seems to be working fine now, but is in the secondary partition. My primary is apparently currently empty because of the formatting.
So unless CM9 should never be placed in the primary partition, there seems to be a bug somewhere (at least in the Android version). I did see something in the script that appears to be a problem. Within the "ga" leg, it has this coding:
mv gapps_DualbootSD_alternate_${DATE}.zip ../Primary-Mod/gapps_DualbootSD_alternate_${DATE}.zip
I'm not a programmer, but having "Primary-Mod" intermixed with "alternate" would seem to be problematic. But since this is the "ga" leg, I don't know that this would have caused CM9 to be applied to the secondary partition instead of the primary, so there may be a problem somewhere else.
Do you know if anyone else has successfully applied your modded version of the CM9 rom to primary using the Android script? Or should the existing modded version only be placed in the secondary partition?
Thanks,
oldfolkie
Click to expand...
Click to collapse
Goodness! Gotta check my script! But that should have been moved to Alternate-Mod. But as in the appended filename. It should flash to alternate boot. Will correct on next update.
Regarding ur issue, you shouldnt be using my modded zips for conversion as it is already prepped specifically for Primary or Alternate boot.
The script is for converting standard .zips. like a regular nightly. Also note if ur flashing a new rom over default setup. It is recommended to format /system1, /data1 for primary & /system2, /data2 for alternate.
Thanks again for pointing out that error!
Sent from my NookColor using Tapatalk
I figured the issue might be with using the modded zips, but I wasn't sure. Thanks!
Firstly I did a search and this is probably something I should have found, but I really couldn't see anything- so apologies in advance if this has been answered.
Anyway, so have nexus 4, running CM 10.2 and Franco Kernel (always up to date with both of them).
I had TWRP 2.5 on there for a while which is how I kept flashing updates, and then 2.6 came out. So first thing was I couldn't update it, using various methods (I tried to ADB in, I tried the standard Goo Manager thing, all sorts).
Thought that was odd, but also I couldn't change to CWM (using Rom Manager Pro) which was frustrating too. I re-locked and installed stock custom recovery using WugFresh's stuff, then went through it all again, put on TWRP 2.6 on it.
All was working fine. Out of interest I tried to transfer to CWM (latest) again using Rom Manager. All fine. But then I tried to go back again and it got 'stuck' again. Couldn't downgrade or change to any other custom recovery.
So, it looks like I can sort it using WugFresh's stuff, so not a huge detail, but it niggles me because I should be able to do it 'in phone' right? Shouldn't I technically be able to just hop back and forth if I wanted to for some reason? Any ideas what may have gone wrong?