Related
When I bought my used Nook Color, I used the 8 re-boot method to flash back to 1.0.0 ... de-registered... registered... updated to 1.1.0 ... then used Auto-Nooter 3.0 to get my perfect device.... Everything has worked great until the BN 1.2 update totally ruined by device!! I have tried booting off the uSD card for AutoNooter3.0 but doesn't work... I tried using 8 re-boots to get back to 1.0 (to start over)... doesn't work... i get the Android screen and it stays stuck on that screen no matter what I do!!! Please somebody help me!! I want to go back to stock 1.0 ... then 1.1 then Auto-Nooter 3.0... restore my Titanium... and turn off Auto-Updates (which I've just found instructions for.)
Thanks,
Kevin
Do you want to stay on eclair? I would highly recommend using one of the modified stock froyo (modified 1.2 update) roms from this site and flash it per site instructions. Then you could manual nooter it. Then due to cuurent limits on the root of 1.2, I would go to the dual boot thead and set up dual boot with froyo (1.2) on the second boot and cm7 on the first. Nothing beats cm7, especially if you add dalgrin's overclock to the works. If you end up not liking the setup, it's very easy to recover to stock.
No, I really just want to get back to my 1.1.0 ... with Auto-Nooter 3.0... restore my apps... and then turn off Auto Updates.
Actually, my problem right now is that I cannot seem to flash back to stock at all!!
You could try this if you have not already.
http://forum.xda-developers.com/showthread.php?t=945838
If you already tried to install a stock rom over the mess that B & N made, all you may need to do is a wipe data/factory reset from ClockworkMod Recovery. That might clear up some boot issues for you.
dapazz238 said:
.... and turn off Auto-Updates (which I've just found instructions for.)
Click to expand...
Click to collapse
Is there a confirmed method to prevent auto updating? <Link please?>
Look for the Pre-rooted 1.1 upgrade and flash that. I am not sure if it blocks automatic update.
This worked!!!
bonez318ti said:
Is there a confirmed method to prevent auto updating? <Link please?>
Click to expand...
Click to collapse
This is what I've used:
http://forum.xda-developers.com/showthread.php?t=946969
So far so good. No OTA and I've been on autonootered 1.1.0 since before the 1.2 update, and WiFi always on for the past couple of weeks.
I was running on a rooted 3.1 with tiamat 1.7 overclock
What I did was:
tried to follow [UPDATE][US WIFI ONLY]Android 3.2 on Xoom WiFi, Root, via ClockworkMod Recovery
then I did this: Note also if you are coming over from a custom ROM, wipe your cache partition (under main menu) and dalvik cache (under Advanced) in ClockworkMod Recovery prior to performing the following steps.
next I applied the 3.2 update
Now Im stuck in the boot animation.
From what I understand Im getting this because I was not on the stock kernel, can anybody help me fix this and get me to 3.2
Thank you
download the stock images here http://forum.xda-developers.com/showthread.php?t=1080963
and flash via fastboot, this will get you out of the boot loop, i had the same issue
should I try and flash the 3.2 or the 3.1 given my current situation?
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
jase33 said:
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
Click to expand...
Click to collapse
You probably should wipe user data in recovery along with the caches. That's what got me out of the bootloop and into the updated stock 3.2.
i flashed the stock images from the first link provided via fastboot and it worked perfect, the thread said you can flash from whatever to whatever by using those images so i flashed 3.2 and it fixed everything. Took about 5 minutes to do, I wonder if this way will give me problems when I try to root (pretty sure I lost root) but everything now seems to work fine
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Tomate2K8 said:
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Click to expand...
Click to collapse
Yep, that's the easiest solution, but whatever works!
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
phekno said:
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
Click to expand...
Click to collapse
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
zbee said:
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
Click to expand...
Click to collapse
Yeah, they really are almost bullet-proof. Good thing too, seeing all the abuse they have to take.
: )
okantomi said:
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
Click to expand...
Click to collapse
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
phekno said:
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
Click to expand...
Click to collapse
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I updated in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
okantomi said:
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I update in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
Click to expand...
Click to collapse
Yeah, I was rooted before all of this. I had done a full wipe in CWM and then did the boot/kernel and now I'm here. I think I should have just done the Tiamat Xoom Rom 2.0 in stead. Can I just flash the 2.0 ROM over what's on there now?
Edit: Now, I can't seem to get in to CWM. I'm not really sure how to other than using adb reboot recovery, but windows isn't picking up the device now.
Edit #2: I got back in to CWM. I'm running CWM 3.0.2.5, FYI.
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
phekno said:
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
Click to expand...
Click to collapse
Great! Have fun with it. I think you'll love it.
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
blee00 said:
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
Click to expand...
Click to collapse
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if debugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
okantomi said:
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if degugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
Click to expand...
Click to collapse
Thanks for your reply! =)
I have done the "Wipe user data/factory reset" in CWM, If I do that I usually can boot Honeycomb, but I rarely get past the setup wizard (although sometimes I do), but then after a few minutes it freezes again.
Also, I can access my Xoom through ADB.
hi guys,
i want to root and flash custom rom on my acer iconia with 3.2 OTA.
Correct me if i'm wrong...
i understand that i have to:
1. revert to 3.0.1 via http://forum.xda-developers.com/showthread.php?t=1276227
2. root my iconia via http://forum.xda-developers.com/showthread.php?t=1055354
then i don't know whats next? can i already install custom rom after root?
or do i need to install some kind of recovery to flash this custom roms..
Please help.. thanks!
exactly my friend revert first then root, then download acer recovery app install recovery start flashin
jhannbernas said:
hi guys,
i want to root and flash custom rom on my acer iconia with 3.2 OTA.
Correct me if i'm wrong...
i understand that i have to:
1. revert to 3.0.1 via http://forum.xda-developers.com/showthread.php?t=1276227
2. root my iconia via http://forum.xda-developers.com/showthread.php?t=1055354
then i don't know whats next? can i already install custom rom after root?
or do i need to install some kind of recovery to flash this custom roms..
Please help.. thanks!
Click to expand...
Click to collapse
Once you root install this:
Acer Recovery Installer
That will install CWM (recovery).
thanks for you both. i will try all of this on weekend.
but before doing this.. how can i backup my current rom? it is possible? thanks
You should install the Acer recovery installer first, then boot into CWM. When you are in there you will have the option to perform a full backup. This backup function will become your best friend.
thanks.. can't wait for the weekend to do this.
lastly, can anyone give me suggestion on what rom should i try in our opinion? thanks
jhannbernas said:
thanks.. can't wait for the weekend to do this.
lastly, can anyone give me suggestion on what rom should i try in our opinion? thanks
Click to expand...
Click to collapse
IMHO the stock based ROMs are the most stable, and trouble free. Head over to the DEV section and pick one out
There are plenty of ROMS to choose from. Some are better than others, and some work better for others. Taboonay seems to be the most popular. I liked Lightspeed because it basically removed EVERYTHING that I didn't need. Citvao seems to be gaining momentium. There is also another guy by the name of THOR who created a custom ROM that incorporates some files from the transformer stock ROM that is pretty good too.
I'd try them all and see what one you like best
Steps to using CWM?
If there's a thread to using CWM please direct me to it.
I have taken a short cut in using it by watching a YouTube video for installing a custom ROM and not learned all the in's and out's of using CWM.
I had installed the OTA HC 3.2 over a rooted 3.1 and lost my rooting as I expected. I decided I wanted to have root capabilites but with HC 3.2, so I found the (Oct 5 )version here and started over again.
I started with the Method 2 approach to install HC 3.2 update (that was already rooted here on this web site) to get to HC 3.0.1. However, initially when I got to installing the HC 3.2 zip it just booted afterwards and then went to a blank screen. So I tried it again only not doing all the clearing of user data, caches, etc., that was mentioned in the YouTube Video for installing a custom ROM. That worked. I now have a Acer Iconia 16 GB A500 rooted with HC 3.2 on it which what I wanted.
I would like to try some other ROMs and still go back if I could but I'm not sure about what exactly has to be cleared every time you load a new ROM. I don't want to have it hang again to a blank screen and maybe screw it up so I can't fix it.
Any directions?
Oh, BTW, when I installed the HC 3.0.1 from Method 2, it was so unstable that I couldn't make a WIFI connection. I had to go right to 3.1 to be able to use WIFI and get Acer Recovery Installer and continue on to installing HC 3.2 rooted.
Thanks
Redevil06 said:
If there's a thread to using CWM please direct me to it.
I have taken a short cut in using it by watching a YouTube video for installing a custom ROM and not learned all the in's and out's of using CWM.
I had installed the OTA HC 3.2 over a rooted 3.1 and lost my rooting as I expected. I decided I wanted to have root capabilites but with HC 3.2, so I found the (Oct 5 )version here and started over again.
I started with the Method 2 approach to install HC 3.2 update (that was already rooted here on this web site) to get to HC 3.0.1. However, initially when I got to installing the HC 3.2 zip it just booted afterwards and then went to a blank screen. So I tried it again only not doing all the clearing of user data, caches, etc., that was mentioned in the YouTube Video for installing a custom ROM. That worked. I now have a Acer Iconia 16 GB A500 rooted with HC 3.2 on it which what I wanted.
I would like to try some other ROMs and still go back if I could but I'm not sure about what exactly has to be cleared every time you load a new ROM. I don't want to have it hang again to a blank screen and maybe screw it up so I can't fix it.
Any directions?
Oh, BTW, when I installed the HC 3.0.1 from Method 2, it was so unstable that I couldn't make a WIFI connection. I had to go right to 3.1 to be able to use WIFI and get Acer Recovery Installer and continue on to installing HC 3.2 rooted.
Thanks
Click to expand...
Click to collapse
This has been posted in another thread by another member, and I saved it. I just can't remember who posted it again.
It's how I do EVERY flash and NEVER have problems.
"Before installing:
Boot into CWM
1/wipe cache
2/wipe data/factory reset
Advanced Menu:
3/wipe dalvik
4/wipe battery stat
Mount and Storage Menu
5/format (system, data, cache )... leave SD card alone.
install the zip ( new rom ) file !
Once done installing... repeat steps #1 - #4 only ( this is to assured that you are cleaned 110% in regard to the NEW rom that you have just installed )
DO NOT DO THE STEP #5 AFTER THE INSTALLATION !
Reboot system into initial Android greeting screen."
Some would say it's a bit on the "overkill" side, but better safe than sorry.
Thanks for the quick reply.
I think I also found where some of the information I wanted was in:
http://forum.xda-developers.com/showthread.php?t=1205204
I should have done more searching.
Thanks again
Oh, BTW, I have read your other posts on this site and like what you have to say. Also, the last step you have, Step 5, isn't in the YouTube video. Maybe that's where I fouled up and somehow recovered by doing again without some of the clearing. I think I just lucked out and got it working. Initially, without WIFI, I was stuck on how can you install Acer Recovery Installer without going to the "Market"? I had to go to 3.1 to get WIFI and then install it from the Market. I searched the internet with a computer for it, but couldn't find the apk to download so I could move it to a SD card and the Acer. Anyway it's working now and looking forward to more new ROMs and maybe Ice Cream if that's going to be the way to go in the future.
hardslog said:
You should install the Acer recovery installer first, then boot into CWM. When you are in there you will have the option to perform a full backup. This backup function will become your best friend.
Click to expand...
Click to collapse
Unfortunately he cannot use Acer Recovery Installer as long as he does not have root and that is why he cannot backup his current configuration i.e. OTA 3.2. Taking the risk of reverting is in first place if he insists on using a custom ROM.
Right on!
drkalo said:
Unfortunately he cannot use Acer Recovery Installer as long as he does not have root and that is why he cannot backup his current configuration i.e. OTA 3.2. Taking the risk of reverting is in first place if he insists on using a custom ROM.
Click to expand...
Click to collapse
+1
Some people don't read before posting
kjy2010 said:
+1
Some people don't read before posting
Click to expand...
Click to collapse
MY BAD!
I thought I read that he rooted it already and wanted to make a backup of that......
drkalo said:
Unfortunately he cannot use Acer Recovery Installer as long as he does not have root and that is why he cannot backup his current configuration i.e. OTA 3.2. Taking the risk of reverting is in first place if he insists on using a custom ROM.
Click to expand...
Click to collapse
got it. thanks!
folks, my a500 is overheating .. is getting too hot near the Dock Connector ...
is without overclocking, began in the ROM v10 ... already installed a four roms and the error still continues,
currently with honeyvillian, I leave with the original stock which is 3.0.1
I try the same way as was done to use mod 3.2, and does not work
... only shows the current version
well ..
current version: 1.0.1 Honey Villian ...
New Verson: N / A
I want to install the original version to send assistance to repair the high temperature
Verdeee said:
folks, my a500 is overheating .. is getting too hot near the Dock Connector ...
is without overclocking, began in the ROM v10 ... already installed a four roms and the error still continues,
currently with honeyvillian, I leave with the original stock which is 3.0.1
I try the same way as was done to use mod 3.2, and does not work
... only shows the current version
well ..
current version: 1.0.1 Honey Villian ...
New Verson: N / A
I want to install the original version to send assistance to repair the high temperature
Click to expand...
Click to collapse
You're not flashing your Rom correctly. I told you this in Thor's forum (at least the exact post was there also, so I suspect it's you, if it's not you, then accept my apologies ).
The reason it keeps telling you that a certain Rom/kernel is installed, is because it seems like you're just flashing one over the top of another without cleaning anything out. This is why your cpu overheats. You've got a corrupted OS.
Also, a Kernel image is not a Rom. And there are 2 types of kernels. 1 for a stock rom, and 1 for a cooked rom. You shouldn't mix the 2 or you may get problems depending on the rom. Another reason why your cpu overheats.
Do this. Put your SD in your PC's card reader, and format it to Fat32. Reason, is that I have absolutely no idea what you have on your sd. Update.zips, Kernels, Roms, etc.
Copy your VillainRom or Revolver Rom or Taboonay Rom (or whatever rom you want to use) to your SD, then put it back in your 500.
When you flash a new rom, you boot to CWM.
Wipe User Data
Wipe Cache Partition
Goto Advanced and Wipe Delvik
I like to do each a couple of times, just to be sure.
Then go back to the previous menu, and select "Install zip from sd"
Choose your rom and install it.
All three of the above roms come with a cooked kernel so you shouldn't have to mess with kernels.
Also, if you wish to install a different cooked kernel, you only need to wipe Delvik before installing.
Also, Install the rom first and let it run for awhile before installing a kernel. Never do both at the same time.
And the final rule, if you used a backup program like Titanium Backup or any of the others, Never Ever backup and restore system files to a different rom.
But, if you want to put it back to stock, the I suppose you can use the acer recovery tool to flash a stock acer rom and flash the stock recovery image. For more info, see this thread;
http://forum.xda-developers.com/showthread.php?t=1155664
Can someone please explain to me how to go from Bionix 1.3.1 to ICS? I have read a lot (perhaps too much) about GB bootloaders, etc. but am not sure what is required.
Do I need to have a GB ROM installed before going to ICS?
I have also seen guides for going from 2.1 to ICS, but that is not my situation.
I guess my main area of ignorance is that I have never flashed any bootloader of any kind.
If I go to ICS and want to restore my Froyo backup do I need to flash a bootloader before I do that?
Obviously I'm confused about the whole process.
Thanks for any clarification you can give me.
See my guide to go from 2.1 to ICS and one if the top lines tells you how to go from Froyo to ICS.
GB bootloaders are no longer needed but suggested. Probably the only scary part of the whole process, but it is actually the easiest.
CM7 needed before ICS or not?
From a post in the same thread as your guide:
"
If you want a stable 2.2 try Toxic8 (I run this with Gingerbread theme as my "home" ROM when I am not testing), Deranged9, Bionix (no longer supported) and Bionix Fishman's version (this is supported), Bi-winning. All you have to do to flash these is follow the instructions above and when it comes time to flashCM7, skip it and flash the ROM of your choice."
Does this mean that if I have Bionix already that I don't need to go to CM7 before ICS?
There are a couple of ICS Roms where you can come from froyo. You have to probably flash it twice to get into the specific cwm.
To get back to you bionix, you have to use Odin to get back to stock.
rblancrt said:
From a post in the same thread as your guide:
"
If you want a stable 2.2 try Toxic8 (I run this with Gingerbread theme as my "home" ROM when I am not testing), Deranged9, Bionix (no longer supported) and Bionix Fishman's version (this is supported), Bi-winning. All you have to do to flash these is follow the instructions above and when it comes time to flashCM7, skip it and flash the ROM of your choice."
Does this mean that if I have Bionix already that I don't need to go to CM7 before ICS?
Click to expand...
Click to collapse
This is from a different thread in a different context. Someone was asking how to flash a custom ROM, IIRC.
If you want ICS, you have to flash CM7 first, let it bootloop, pull the battery, reflash and then once it settles, flash ICS.
Also, don't apologize for being detailed or thinking that you are reading into too much, Wished more were like this.
From the Guide
This is for a clean install. You can also install straight from Froyo. Just start at the CM7 part below and skip the Odin portion.
Click to expand...
Click to collapse
so any luck with getting to ICS from bionix 1.3.1...cause im still in the same spot...and im very wary as to what to do as well...so if any luck...please let me what you did...
I just did it
If you follow the instructions in the Passion ICS thread it's pretty straightforward. I had never used Odin before even though I had flashed Bionix almost a year ago. I'm not a phone guru, just somebody who likes to mess with these custom ROMs.
These steps are high level, you can find specific links in numerous places.
Here's what I did:
- Download Odin
- Download the required files to flash the phone back to stock 2.1 (.pit file and .tar file)
- Backup apps with Titanium (don't bother backing up the system it's different in newer versions anyway and all you'll have is trouble if you try to restore system settings)
- Backup anything else you feel is important on your internal and external SD cards
- Use Odin to flash the phone back to stock
- Root the phone (using the update.zip technique)
- Install clockwork recovery (I found an update.zip for this too)
- Flash the Cyanogenmod version of ICS (no longer under development but you need it for the boot loaders). You will likely encounter a boot loop in this process. Don't panic, just pull the battery once it loops a few times. Boot back into recovery and flash again.
- From this point you can now flash ICS using clockwork, following this you can restore your apps with Titanium if desired
ICS totally rocks by the way. I've been using Passion v13 RC1 for a week now. Tried the newest one Euphoria but it didn't work out for me.
I have to admit that I never tried ICS. I have been using an ICS theme for a long time so my phone looks like it has ICS on it. I was also leary of the mute/unmute problem I had read about and wasn't sure about how well good GPS was.
I've been testing out the ICS that is to become CM9 with the latest build being 16 found at http://forum.xda-developers.com/showthread.php?t=1503038
It's really stable... granted not everything is implemented such as a number of the settings screens. But I was on CM7 when I installed it so I was able to just flash it direct.
atatistcheff said:
If you follow the instructions in the Passion ICS thread it's pretty straightforward. I had never used Odin before even though I had flashed Bionix almost a year ago. I'm not a phone guru, just somebody who likes to mess with these custom ROMs.
These steps are high level, you can find specific links in numerous places.
Here's what I did:
- Download Odin
- Download the required files to flash the phone back to stock 2.1 (.pit file and .tar file)
- Backup apps with Titanium (don't bother backing up the system it's different in newer versions anyway and all you'll have is trouble if you try to restore system settings)
- Backup anything else you feel is important on your internal and external SD cards
- Use Odin to flash the phone back to stock
- Root the phone (using the update.zip technique)
- Install clockwork recovery (I found an update.zip for this too)
- Flash the Cyanogenmod version of ICS (no longer under development but you need it for the boot loaders). You will likely encounter a boot loop in this process. Don't panic, just pull the battery once it loops a few times. Boot back into recovery and flash again.
- From this point you can now flash ICS using clockwork, following this you can restore your apps with Titanium if desired
ICS totally rocks by the way. I've been using Passion v13 RC1 for a week now. Tried the newest one Euphoria but it didn't work out for me.
Click to expand...
Click to collapse
This method works great! I used this last week and had some trouble with boot loops. But nothing that can't be fix with removing the battery. I suggest finding the youtube video that is on the ICS Passion thread. The person does it on real time, so you can follow along as you do it.
I love ICS passion. It is as smooth or even smoother than Bionix.
mikesdot said:
so any luck with getting to ICS from bionix 1.3.1...cause im still in the same spot...and im very wary as to what to do as well...so if any luck...please let me what you did...
Click to expand...
Click to collapse
Just follow instructions in OP of attached link and your good.
-Download ICZen and place it on your internal sd
-Reboot to Clockwork Recovery
-Perform a wipedata/factory reset
-Go to mounts and storage and format the system partition
-Flash your downloaded ICZ rom file
-From the main menu of recovery, perform a wipedata/factory reset again
-Reboot
-On bootup, give it a few minutes to settle in, reboot and use as normal.
-Enjoy your ICZen!
http://forum.xda-developers.com/showthread.php?t=1499455
No need to have GB boots and if you want to go back,odin to stock to reflash Bionix and then your nandroid.
This is a great ICS rom and I'm a huge Bionix fan,with a 1.3.1 and 1.3.1 Fishman final nandroid backup.
I flashed Passion ICS rc13 on 2 Vibrants, one from Bionix 1.3.1 and another from trigger 2.2 and skipped some steps (like GB bootloader) and they are working just fine.
My steps:
1. Wipe data/factory reset
2. Flash CM GB.
3. Wipe data/factory reset
4. Flash Neobuddy ICS
5. Flash kernel.
6. Let the phone boot, sign up and do its setup.
All in all, took maybe 30 minutes first phone and 20 min second phone once I got more comfortable.
bionix 1.31 striaight to CM7 then on to ICS?
Do you have to go back to stock? Why couldn't you just flash to CM7 then go on to ICS? I am on Bionix 1.31 and this process just seems easier.
rblancrt said:
I have to admit that I never tried ICS. I have been using an ICS theme for a long time so my phone looks like it has ICS on it. I was also leary of the mute/unmute problem I had read about and wasn't sure about how well good GPS was.
Click to expand...
Click to collapse
I think mute/unmute is hit or miss. But if you are worried about or need GPS, dont flash an ICS rom.
Also, when upgrading fro 2.2 -> 4.0, take out your external sd card prior to that! It might cause a bootloop when flashing the initial CM7 rom. I happened to me and also other people on youtube (where I found out, was the source of the problem)
---------- Post added at 03:27 PM ---------- Previous post was at 03:27 PM ----------
licktheback said:
Do you have to go back to stock? Why couldn't you just flash to CM7 then go on to ICS? I am on Bionix 1.31 and this process just seems easier.
Click to expand...
Click to collapse
Yep you can, just make sure you make a back up and clear all data
licktheback said:
Do you have to go back to stock? Why couldn't you just flash to CM7 then go on to ICS? I am on Bionix 1.31 and this process just seems easier.
Click to expand...
Click to collapse
It's mainly to get rid of any ghosts left from other roms to avoid any bugs not caused from the rom you install and avoid giving a rom a bad review without giving it a clean canvas to start with.
powered by ICS Euphoria