Database Users

constant reboots

Hello, I have had my evo for about a month and over the last week or two my phone constantly reboots and crashes. It sometimes gets stuck in boot loops and i haveto yank the battery. it seems to happen most frequently during the browser or market apps. I cannot figure why it is doing this!!!!
my phone is rooted and this has been happening on multiple ROMS including CM6, AVA froyo, baked snack, and fresh EVO.
I have wiped:
cashe
DATA
full factory reset
Dalvik Cache
battery stats adn rotate settings
I have triedmultiple batteries and SDcardsi have tried an 8GB and 16GB and reformatted both
any other ideas?

Which ROM and kernel are you using? Your description sounds like an overclock or under voltage issue. Do you get the same behaviour with the stock ROM & kernel?

Right now I am Ava froyo v7 I have used cyanogenmod Ava froyo v6 as well as baked snack 1.5-7 and fresh 3.0.1 and 3.2 same with all
I have use the stock kernel and still get rebooting with stock speeds and 400mhz

I had VERY similar problems to you (rooted, no matter what ROM I would use (even rooted stock) I would get reboots). Usually after yanking the battery I'd get a good 2 or 3 minutes, and then, particularly when using the browser, I would get a reboot. Then reboots would repeat in perpetuity. I even tried unrooting and going back to complete stock, no luck.
Note there is a thread about a code to fix some problems with GPS -- this didn't fix my problem, but it might fix yours.
So just today I took my Evo back to a Sprint store, convinced them it was a problem, they tried doing the complete RUU flash, and the reboots happened again (yay!)...and they gave me a "new refurb".
So I'm currently rooting the new refurb.
- Eckless

Could it possibly be that I am not reapplying the stock kernel before flashing a new rom how log did it take you to get a new phone?

First of all what root method did you use and did you root 2.2 or root 2.1 then upgrade to a prerooted 2.2 rom.
And if you are not following the rom install instructions to a T and are wondering why you are getting reboots then frankly wtf do you expect.
I said that because you said you were not flashing the stock **** before flashing the rom.
Typically this is not needed unless the rom creator SPECIFICALLY states it is needed.
First of all you are using some very nonstandard Rom's. Start by completely wiping and removing any custom sdcard formatting and reformat your sdcard on your pc.
It has been said and proven many times that a bad sdard can screw with your phone and make some crazy **** happen.
Then go back to the STOCK 2.2 ODEXED, not deodex, the point is to get as close to retail as possible without losing root.
Then see what happens.
Sent from my PC36100 using XDA App

Started with 2.1 1.47 OTA update and Jane followed all instructions to the dot and I have re reformated my sdcard several times with windows for both the 8 gb and the 16 gb which both work great on my droid ( which I did reformat between moving them to a new phone) I also tried using no sdcard and no difference ill try going back to stock rom but I have always been using ava froyo and baked snack but now I'm getting problems with any romI use

I am using swype so sorry for any wrong words. Any way I was also using clockwork recovery for a while and it was apparently not wiping dalvik etc. Correctly so I thought that was why it was crashing so I switched to amon Ra recovery and its still crashing so could it have caused permanent damage that can't be fixed by just wiping everything with amon Ra

Clockwork didn't cause damage...flash stock 2.2...flash stock kernel...do a factory reset...and report back...

[ROM] Bonsai User Discussion

This post is only for discussing all issues regarding the use of the Bonsai roms. We can talk here about any version from 1.0.0 to x.x.x
Due to some political issues please do not post any links to the Bonsai website! This thread is just for us users and don't expect the developers of Bonsai to ever visit here.
One last thing >
nor

Yes this try to keep this thread open.
Sent From My Evo Killer!

So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Sent from my SPH-D700 using XDA App

I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force

forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Were you using CWM 3.0.0.6 or 3.0.0.5 ?
Sent from my SPH-D700 using Tapatalk

Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?

abrcrmdl23 said:
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Click to expand...
Click to collapse
I can't remember what stepping is on the kernel as we have been beta testing 4.0.1 and have been mainly dealing with a new setCPU governor called interactive. Were also still working on the other governor called smartass as well. I think that the stepping goes directly from 400 to 800, but we are always looking to go faster and with better battery life. I'll bug Randy and Mammon about it.
The sound will be Voodoo version 7, but I don't think the Voodoo color fix is going to make it into 4.0.1. Sorry, but we can't do everything...at least not all at the same time.

forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Did I see a similar post on the Bonsai website earlier today? I just want to verify that you were using CWM 3.0.0.6 as anything else will cause problems like that. Also when you get to these kinds of problems you should attempt a second flash of Bonsai before going to the trouble of a ODIN job. A second flash seems to fix a whole variety of odd kind of problems.
As you can imagine with all the beta testing I do I'm always finding ways to corrupt my phone. Some days I have managed to bork it 3-5 times.
I decided to test out today a 4.0.1 install directly from DI18 > CWM 3.0.0.6 > Bonsai 4.0.1 full rom. It went great with no problems at all and running just fine, so far

I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0

bluetooth
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?

forcelite said:
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
Click to expand...
Click to collapse
Do not use Rom Manager to be installing the beta CWM files. The correct way is with one of the 1 step CWM tools in the development forum. 3.0.2.4 is half-finished and is very difficult even to navigate through the various menu's. I know this because I tried out that CWM version for some grins one day. It will majorly screw your Epic if your not extremely careful. When DI18 was prevalent Rom Manager worked great to root your phone. When we started the move into the Froyo roms Rom Manager quit working and that is why the 1 click then became more prevalent.
Just follow the directions posted all over the place and Bonsai will install just fine and you will be a happy camper.

I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Thx All,
Force

forcelite said:
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
Click to expand...
Click to collapse
The linked one is the correct one for Bonsai version 4.x.x.

olddocwhite said:
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
Click to expand...
Click to collapse
Some people do and some don't I do know that Randy has instituted quite a few bluetooth linux upgrades into 4.0.1 rom. Some people are able to clear the data, but the problem usually reappears. Mattalica76 has the link to a more permanent fix to this problem, give him a PM.

Duplicate... Sorry

forcelite said:
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Click to expand...
Click to collapse
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.

Actually it didnt boot this time either, it installed the firs ttime fine, then kept booting after samsung in a loop,
So I went into CW3 and tried to flash bonsai 4.0.01 again and it gave me this error. It is long, however I shortened it, I have the whole error photo copied)
Finding package
Opening package
Install update
Assert failed getprop (“ro.product.device)”)
Sph-700
E:error in /SDcard/bonsai……….
(status 7)
Installation aborted

Top Nurse said:
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Click to expand...
Click to collapse
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.

forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
CWM3 will convert your filesystem to ext4 the first time you boot into it. It won't touch the sdcard so that won't be converted. After CWM is finished with the conversion, do not reboot the phone, you will then flash Bonsai.

forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
After flashing the boot script of cwm 3.0.0.6 you then have to power off. Then hold down the camera button, vol down, and power keys at the same time and the EXT4 script will automatically start to format your system. Please keep in mind that it is not formatting the SD card, but only the read only memory of the phone.
After you finished a few beers it will be done and will drop you back to cwm. Do not reboot, but flash bonsai. After bonsai is finished then reboot.
Sent from Bonsai 7.0.3

Random reboots/shutdowns with Aura and Atrix?

I've re-installed Atrix 4 times on my phone, each time doing a factory reset, clearing cache, and Dalvik cache. I've had random reboots/shutdowns on every install of Alien Build #4 and Aura 1.1.3.8. One running Atrix stock kernal, 2 using faux's kernal 0.1.6 (one non-oc, one oc), and one using faux's OC 0.1.7. Now I'm running Aura 1.1.3 Build #8 Deblurred. All with random reboots and shutdowns.
I've noticed I never get a random reboot while I'm charging, only while on battery. I've calibrated my battery several times so it's not lack of juice. Sometimes it just reboots, other times it shuts down and doesn't reboot so I have to turn on the phone, though most of the time the screen won't turn on and the phone won't shut off so I have to take out the battery to turn on the phone. I've tried uninstalling SetCPU, disabling profiles, and setting the max clock to 1000mhz. None of this helped.
On the last Alien install (now I'm running Aura) I was having even more problems but they only happened on that install:
1. I got an error when trying to boot in red: "Unrecoverable Bootloader error (0x00000004)" though I was able to turn the phone off and reboot normally.
2. I got an error about 5 times in a row while trying to boot, I forgot the exact text but something along the lines of "Unable to load radio module (0)". I had to take out the battery and try about 5 times till it would boot properly.
3. After this, I was unable to boot into Recovery through the volume buttons, I'd press down till I got the Android Recovery, then press up and it'd hang there. It works now for some reason.​
I installed Alien right when I got my phone so I'm unsure if random reboots happen stock. Also my phone gets really warm when I'm using it, I look in SetCPU and the CPU temp is anywhere from 42 to 57 C. Does anyone else's phone get this hot?
I would just take it back to Best Buy and get a new one cause I have a protection plan with them, but my phone is unlocked which voids the warranty.
Does anyone know what could be causing all of these issues and how to fix them?
Thanks for the help, XDA is great!

Im by no means a expert...but I'm currently running AURA 1.1.3#8 debloat and all is well on my phone....I would recommend performing a Ti backup on ur aps and doing a factory reset to see if the problem persists....if it does I would take it back...if not reinstall through CWM wiping devalk cache then a full data wipe then install AURA and reboot all in CWM ....btw I'm running Rom Racers CWM also. Hope you can get it figured out!

JRW 28 said:
Im by no means a expert...but I'm currently running AURA 1.1.3#8 debloat and all is well on my phone....I would recommend performing a Ti backup on ur aps and doing a factory reset to see if the problem persists....if it does I would take it back...if not reinstall through CWM wiping devalk cache then a full data wipe then install AURA and reboot all in CWM ....btw I'm running Rom Racers CWM also. Hope you can get it figured out!
Click to expand...
Click to collapse
I would have just taken it in but my phone is unlocked, rooted, and using Romracers CWM so I doubt Best But will accept it. I've tried all of this. I'm going to try CM7 Beta2, if the problem still persists I don't know what to do cause Best Buy won't accept it when they see the Unlocked at the top of the bootloader. It works fine when it's charging but so far no matter what I've tried I always got reboots. Does your phone get hot? Can you check what temps you get in SetCPU? Thanks for the suggestions btw.

My phone has never gotten over 33*....Try going back to stock gingerbread and see if the problems persist there and if not then u can proceed forward.....that way you can rule out if the problem is the phone or a certain build and a bug you have picked up

Sorry I meant 39* on phone temp

I went into my settings>widow and turned it off then rebooted, seemed to work, I also would get random reboots after a fresh install. Like at least 20x. But try that. Worked for me.
Sent from my MB860 using XDA App

JRW 28 said:
My phone has never gotten over 33*....Try going back to stock gingerbread and see if the problems persist there and if not then u can proceed forward.....that way you can rule out if the problem is the phone or a certain build and a bug you have picked up
Click to expand...
Click to collapse
33? Wow, my phone never goes below 42C, it's usually around 49-50C. How do you return to stock gingerbread like the phone came with? All I've found was flashing the SBF through RDA, is there any way to do it with CWM so it's safer? Sorry for the noobiness, I'm new to the Atrix, is there a way to completely restore the phone to stock (stock gingerbread, locked bootloader, no CWM)?
Edit: I just flashed CM7 pre-beta 2, going to see how this works, hopefully it fixes my problems.

performing a data wipe/factory reset in CWM should put you completely back to stock. It wont matter that you have a UL bootloader or rooted.

Ecstacy42 said:
I've re-installed Atrix 4 times on my phone, each time doing a factory reset, clearing cache, and Dalvik cache. I've had random reboots/shutdowns on every install of Alien Build #4 and Aura 1.1.3.8. One running Atrix stock kernal, 2 using faux's kernal 0.1.6 (one non-oc, one oc), and one using faux's OC 0.1.7. Now I'm running Aura 1.1.3 Build #8 Deblurred. All with random reboots and shutdowns.
I've noticed I never get a random reboot while I'm charging, only while on battery. I've calibrated my battery several times so it's not lack of juice. Sometimes it just reboots, other times it shuts down and doesn't reboot so I have to turn on the phone, though most of the time the screen won't turn on and the phone won't shut off so I have to take out the battery to turn on the phone. I've tried uninstalling SetCPU, disabling profiles, and setting the max clock to 1000mhz. None of this helped.
On the last Alien install (now I'm running Aura) I was having even more problems but they only happened on that install:
1. I got an error when trying to boot in red: "Unrecoverable Bootloader error (0x00000004)" though I was able to turn the phone off and reboot normally.
2. I got an error about 5 times in a row while trying to boot, I forgot the exact text but something along the lines of "Unable to load radio module (0)". I had to take out the battery and try about 5 times till it would boot properly.
3. After this, I was unable to boot into Recovery through the volume buttons, I'd press down till I got the Android Recovery, then press up and it'd hang there. It works now for some reason.​
I installed Alien right when I got my phone so I'm unsure if random reboots happen stock. Also my phone gets really warm when I'm using it, I look in SetCPU and the CPU temp is anywhere from 42 to 57 C. Does anyone else's phone get this hot?
I would just take it back to Best Buy and get a new one cause I have a protection plan with them, but my phone is unlocked which voids the warranty.
Does anyone know what could be causing all of these issues and how to fix them?
Thanks for the help, XDA is great!
Click to expand...
Click to collapse
Are you doing a factory data/reset wipe cache and wipe dalvik step after you install a new rom? Do the same wipe steps before and after rom flash. If you are doing this then it sounds like a hardware problem or your bl got thrashed unlocking it.
Sent from my MB860 using xda premium

Ecstacy42 said:
33? Wow, my phone never goes below 42C, it's usually around 49-50C. How do you return to stock gingerbread like the phone came with? All I've found was flashing the SBF through RDA, is there any way to do it with CWM so it's safer? Sorry for the noobiness, I'm new to the Atrix, is there a way to completely restore the phone to stock (stock gingerbread, locked bootloader, no CWM)?
Edit: I just flashed CM7 pre-beta 2, going to see how this works, hopefully it fixes my problems.
Click to expand...
Click to collapse
Go the fruitcakes thread in the developement section. Stock cwm flashable builds.
Sent from my MB860 using xda premium

JRW 28 said:
performing a data wipe/factory reset in CWM should put you completely back to stock. It wont matter that you have a UL bootloader or rooted.
Click to expand...
Click to collapse
It will only reset to the current rom defaults. If you have cm7 or alien flashed, It will revert back cm7 or alien. Doesn't effect root or bootloader. If the rom is pre rooted it stays rooted even after a full wipe.
Sent from my MB860 using xda premium

Dirtburgler said:
Are you doing a factory data/reset wipe cache and wipe dalvik step after you install a new rom? Do the same wipe steps before and after rom flash. If you are doing this then it sounds like a hardware problem or your bl got thrashed unlocking it.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
That sounds highly possible as it happens with each install and I am doing a factory reset, cache wipe, and dalvik cache wipe with each install. If ran the unlocking script again would it erase the bootloader and re-install it to fix that?
Edit: I just got another "Unrecoverable Bootloader error (0x00000004)" error, I'm going to re-run the script.

Ecstacy42 said:
That sounds highly possible as it happens with each install and I am doing a factory reset, cache wipe, and dalvik cache wipe with each install. If ran the unlocking script again would it erase the bootloader and re-install it to fix that?
Edit: I just got another "Unrecoverable Bootloader error (0x00000004)" error, I'm going to re-run the script.
Click to expand...
Click to collapse
No don't. The script doesn't update the boitloader I don't think. Did you use the ota to get gingerbread?
If the bl is fubared and your not on the legit ota you can rsd to 1.83 and start over. If you are on the ota update then all you can use is cwm(safely)
Sent from my MB860 using xda premium

when I was on Ninja SF I performed a factory reset and forgot to perform a backup and it took me back to completly stock gingerbread....sorry if I was misleading him

Dirtburgler said:
No don't. The script doesn't update the boitloader I don't think. Did you use the ota to get gingerbread?
If the bl is fubared and your not on the legit ota you can rsd to 1.83 and start over. If you are on the ota update then all you can use is cwm(safely)
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
My phone came shipped with 2.3.4 Gingerbread, I never used the OTA update. I re-ran the script and got another random reboot.
Edit: I'm flashing the official 2.3.4 SBF from here: http://forum.xda-developers.com/showthread.php?t=1125944
I'll let you all know how things went.

From what I understand ...once u are on 2.3.4 if u try to flashback to. 83 it will hard brick you...definitely flash back to stock gingerbread 2.3.4 and hopefully that will solve your problems ....good luck

I installed Aura 1.1.3 Debloat #7 two days ago and my phone rebooted by itself today. I had it in my pocket, then I took it out and it was loading. I thought I might have pushed something when moving, but maybe it is related to the rom.

Okay, I flashed 2.3.4 with pudding boot loader unlocked and Romracer CWM Recovery. I'm going to install Alien and faux's kernal, hope flashing 2.3.4 fixed this and it's not a hardware issue.

Did you experience any problems while you were on 2.3.4 or did you flash straight to alien afterwards ...hope you get your problems figured out! Make a backup of the 2.3.4 flash also so if you do experience any problems you can always flash back

JRW 28 said:
Did you experience any problems while you were on 2.3.4 or did you flash straight to alien afterwards ...hope you get your problems figured out! Make a backup of the 2.3.4 flash also so if you do experience any problems you can always flash back
Click to expand...
Click to collapse
I flashed straight to Alien when I got the phone so I'm not sure it stock Gingerbread had problems. I just flashed 2.3.4 with pudding unlocked bootloader, Romracer's CWM, and finished installing Atrix Build 4 and faux's kernal 0.1.7. I'm going to take the phone off the charger (I only get reboots and shutdowns while on battery), and start installing my apps, restoring contacts, messages, and see if I have any problems. I'm not going to install SetCPU and mess with profiles and undervolting till I know I'm good.
I'll report how it's going tomorrow morning (usually by that time I get at least 5 to 10 random reboots/shutdowns). If this doesn't fix it then I'm going to flash the stock 2.3.4 SBF so they don't know I messed around with the device and take it back to Best Buy to get a replacement.

Bionix 1.3.1 to ICS

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

Been awhile, quick question regarding ICS now

So I've been out of the loop for awhile... since I've been using TeamWhiskey's Bionix and loving it - keeping it simple.
Firmware - 2.2
Kernel 2.6.32.9
Build - Bionix 1.3.1
Now, if I want to install an ICS ROM, do I have to ODIN or something along those lines to factory?
I'm lost again with all the kernel talk along with firmware version, etc.
Essentially I'm considering ICS CyanogenMod 9.
Thanks.

If you're going from froyo to ics you don't need to Odin. You can just flash over it. But turn voodoo off!
If you decide to go back to froyo you do need to Odin.
Sent from my SGH-T959 using Tapatalk 2

You don't have to Odin back to stock, but it's highly recommended.
Most of the ROMs have instructions on what to do for installing them but whenever I decide to test out an ICS ROM I do the following (in addition to the usual nandroid, app, and data backups):
1) Disable Voodoo lagfix
2) Perform a wipedata/factory reset
3) Format the system partition
4) Flash the ROM
5) Perform a wipedata/factory reset again
6) Clean the cache and dalvik
7) Fix Permissions
8) Reboot
You should also consider loading up the Gingerbread bootloaders using Odin before flashing an ICS ROM as well.
I also usually format the internal SD from the current ROM I'm running (Settings->SD card and phone storage) after I complete all my backups. I like starting out with as clean a slate as possible, but doing that is not necessary.
I hope you've seen the threads about the encryption unsuccessful error that can happen with the ICS ROMs, but I'll remphasize that you need to backup all your important data that's on your internal SD before you try to flash. It's not that you can't get your phone back, but that internal SD will be useless if you're unlucky enough to get that message.
PS: Read up on ICZen if you're thinking about flashing ICS. It has very active support, and is specifically for the Vibrant.
http://rootzwiki.com/topic/21742-romimm76i-iczen-184-6-25-12-deficient-development/

http://forum.xda-developers.com/showthread.php?t=1464423
everything you need to know.

Its alot easier than the bad old days, prepare to have your mind officially blown, you'll never go back. Enjoy.

Thanks everyone, really appreciate the replies.
I'll take my time on this one, don't want to mess anything up.