OK i have to say i m not a noob anymore. And i m pretty confident.
Having said I am coming from Vegan 5.1 and tried many times to download the new Vegan Ginger. But each time I got stuck at the "birds" screen.
And yea I do all the same steps for when i was ROMing to Vegan 5.1
So my questions are: why isn't it working this time?
Do i have to be on Stock Rom for it to work?
Any suggestion?
Thank you
Its always a good idea to start from stock and then going to custom rom. I suggest you use nvFlash to go back to stock, then flash cwm .8 and then try to follow your steps to install it.
enjoy
Best way to flash a new rom is to fully wipe data cache dalvik ect ect do that in cwm then install zip from disk. Works every time and usely it take like ten minites to fully install. If you need help just look around or ask.
Good luck
Awessssoooommmee
You guys are awesome
I just Nvflash and Install the ginger edition easily
Thank youuuuu
I'm having the exact same problem. Even fully wipe data, cache and davik does not help.
I noticed that, when ClockworkMod Recovery showed that it was installing update, the progress bar stayed grey, not changing or moving at all.
Guess I'll have to try nvflash.
Yeah do that
ww9rivers said:
I'm having the exact same problem. Even fully wipe data, cache and davik does not help.
I noticed that, when ClockworkMod Recovery showed that it was installing update, the progress bar stayed grey, not changing or moving at all.
Guess I'll have to try nvflash.
Click to expand...
Click to collapse
Yea do that, cause it looks like this ONLY works on stock rom. And after that just do your usual process, and you should be good.
Everything went so well that my first boot took less than a minute
Hi All, first time poster, long time lurker.
I previously had CM7 installed on my fascinate and that was the first time I ever rooted so it was a tad buggy and there were two CWM recoveries (JT’s red 2.5 & CWM 4.X fixed for CM7) installed. To get to JT’s I did the three finger salute, and to get to 4.X, I used long held the power button in CM7 and rebooted into recovery. Anyways I decided to right my wrongs and flash CM7 from scratch. I followed these instructions to the letter (started with Post #2 then moved onto post #1) ([http :// w w w .fascinateforums. c o m/forum/fascinate-rs-guides/2961-how-upgrade-cyanogenmod7.html[/url]) [sorry could not post links... please edit spaces for it to work], multiple times, and could not get it to work. If anyone could shed some advice, it would be greatly appreciated.
A brief overview of what I did.
1. Phone had CM7 Installed, w/ CWM4.0.1.0 and JT’s Red CWM 2.5… decided to reflash from the very beginning.
2. Downloaded DL09 & Atlas v2.2 PIT as defined in Post #2 in the instructions provided in the previous link.
3. Used odined, put DL09 in PDA, Atlasa v2.2 in PIT, checked off re-partition, and Started Odin. Success.
4. Did not turn on the phone, instead connected into Odin immediately after and flashed CWM4 that was fixed for CM7. Success
5. Used three finger method and got into blue CWM4.0.1.0
6. Wiped data three times… wiped cache three times… wiped Dalvik three times.
a.Note: While wiping data, it did not allow me to wipe “datadata” and skipped that part
b.Note: While wiping Dalvik, it said that it had wiped dalvik but the line to it mentioned a path not being found..?
7. Flashed the 7/17 build. Now the trouble begins…
a.Recovery says “Checking status of bml/mtd” then “installation complete.” Phone reboots into the SAMSUNG splash screen then to the SAMSUNG & CM7 splash screen. It never makes it to the skateborder screen and is just stuck on the SAMSUNG & CM7 screen.
b. How long am I supposed to wait here? I waited 10 minutes and it was still stuck… so I just battery pulled. Phone is restored to stock now (using steps 1-2).
I tried this method at least 3-4 times and it always gets stuck on the Samsung & CM7 Splash Screen and just stays there… I am probably doing something wrong but can’t catch it.
I also another method. In step 5, I also went to mount/storage in recovery and wiped /system in addition to wiping data/cache/dalvik. Afterwards I flash the 7/17 build and instead of it being stuck in Samsung & CM7 splash screen it was stuck in an infinite bootloop from SAMSUNG -> SAMSUNG & CM7 -> Recovery (for a quick second) and back to SAMSUNG. When it loops back to recovery it quickly says “Can’t mount” then “installation aborted” and then continues the infinite loop to Samsung => Samung/CM7, etc…
Currently i followed steps 1-2 above and got the phone back to stock and have been using it ever since like that. I miss CM7...
Any help would be greatly appreciated. This forum has provided a plethora of wealth, and I would love to contribute back one day.
Many thanks,
Pat
This may be placebo more than anything, but when I was having problems, I went back to the EB01 stock with atlas as opposed to DL09 and then rooted manually to rooted stock using super one click before flashing the fixed CWM. Things worked great after that.
Also, if all else fails, flash CM7 7/4 and then upgrade from there... even though 7/17 should be fine, 7/4 was considered the jumping off point for a while.
pmanliu said:
Hi All, first time poster, long time lurker.
I previously had CM7 installed on my fascinate and that was the first time I ever rooted so it was a tad buggy and there were two CWM recoveries (JT’s red 2.5 & CWM 4.X fixed for CM7) installed. To get to JT’s I did the three finger salute, and to get to 4.X, I used long held the power button in CM7 and rebooted into recovery. Anyways I decided to right my wrongs and flash CM7 from scratch. I followed these instructions to the letter (started with Post #2 then moved onto post #1) ([http :// w w w .fascinateforums. c o m/forum/fascinate-rs-guides/2961-how-upgrade-cyanogenmod7.html[/url]) [sorry could not post links... please edit spaces for it to work], multiple times, and could not get it to work. If anyone could shed some advice, it would be greatly appreciated.
A brief overview of what I did.
1. Phone had CM7 Installed, w/ CWM4.0.1.0 and JT’s Red CWM 2.5… decided to reflash from the very beginning.
2. Downloaded DL09 & Atlas v2.2 PIT as defined in Post #2 in the instructions provided in the previous link.
3. Used odined, put DL09 in PDA, Atlasa v2.2 in PIT, checked off re-partition, and Started Odin. Success.
4. Did not turn on the phone, instead connected into Odin immediately after and flashed CWM4 that was fixed for CM7. Success
5. Used three finger method and got into blue CWM4.0.1.0
6. Wiped data three times… wiped cache three times… wiped Dalvik three times.
a.Note: While wiping data, it did not allow me to wipe “datadata” and skipped that part
b.Note: While wiping Dalvik, it said that it had wiped dalvik but the line to it mentioned a path not being found..?
7. Flashed the 7/17 build. Now the trouble begins…
a.Recovery says “Checking status of bml/mtd” then “installation complete.” Phone reboots into the SAMSUNG splash screen then to the SAMSUNG & CM7 splash screen. It never makes it to the skateborder screen and is just stuck on the SAMSUNG & CM7 screen.
b. How long am I supposed to wait here? I waited 10 minutes and it was still stuck… so I just battery pulled. Phone is restored to stock now (using steps 1-2).
I tried this method at least 3-4 times and it always gets stuck on the Samsung & CM7 Splash Screen and just stays there… I am probably doing something wrong but can’t catch it.
I also another method. In step 5, I also went to mount/storage in recovery and wiped /system in addition to wiping data/cache/dalvik. Afterwards I flash the 7/17 build and instead of it being stuck in Samsung & CM7 splash screen it was stuck in an infinite bootloop from SAMSUNG -> SAMSUNG & CM7 -> Recovery (for a quick second) and back to SAMSUNG. When it loops back to recovery it quickly says “Can’t mount” then “installation aborted” and then continues the infinite loop to Samsung => Samung/CM7, etc…
Currently i followed steps 1-2 above and got the phone back to stock and have been using it ever since like that. I miss CM7...
Any help would be greatly appreciated. This forum has provided a plethora of wealth, and I would love to contribute back one day.
Many thanks,
Pat
Click to expand...
Click to collapse
In step three of your post you have to fully reboot after flashing dl09 with the atlas pit file to convert all your files back to rfs before trying to install cm7...by pushing the dl09 w/atlas pit and not rebooting youre not fully completing the dl09 install so pretty much you just needed to reboot fully after flashing dl09 thats all.
If your sitting on a running dl09 now, then just do everything you did before minus the atlas pit and dl09...basically flash recovery...boot immediately into cwr and flash the same build using your same method...you probably won't have the data/data wiping problem anymore either!
Edit..you can also try the previous posters instructions as they have worked for me as well in fact every time I have to go back the eb01 file is what I use but most have no trouble with dl09
Sent from my SCH-I500 using XDA App
OMG im having the exact problem and for me that eb01 install did no difference i was also Stuck on SAMSUNG & Cm7 and by the way there is no 7/04 build because JT updated his site and there is none left
izzjkjoe said:
OMG im having the exact problem and for me that eb01 install did no difference i was also Stuck on SAMSUNG & Cm7 and by the way there is no 7/04 build because JT updated his site and there is none left
Click to expand...
Click to collapse
Have you tried booting up the phone after the initial first two steps (PDA +atlas 2.2 Pit)?
I'm at work and have not been able to try anything yet... will do when i get home in a hour
I have tried full reboot after flashing DL09 and it still doesnt work... gets me into a boot loop again. It did fix the wiping datadata issue but no luck with CM7...
I also tried EB01 without any luck.
Additionally i tried JT's 2.5 CWM (Red) and also a newer CWM 3.x...
none of these work. This is day 3 of my rooting problems... thanks for the replies, any more advice would be greatly appreciated...
Try it again and record your steps exactly and post them and I'll try and see what went wrong...it could just be a corrupt download of one of your files or just a simple missed step. What build are you on and what rom are you trying to go to?
Edit: this is what I have done multiple time without a hitch
regardless of what build and rom your on..
-pull your battery
-odin official vzw EB01 (pda button only..just a reminder) and the atlas
2.2 pit file and check the repartition box (I use odin v.1.7, but it shouldn't matter) and let odin do it's thing
-install battery and fully boot and let it sit for a minute our two after it loads
-pull battery
-odin recovery jt's 3-30 fix all... (found in nitsuj's sticky in the development section under recoveries)
-insert battery
immediately three finger boot into recovery and wipe everything
-flash newest cm7 build..I can't remember the date (I used the 7/4 build to get on to cm7 but it has been removed but the latest on will work)
-reboot fully
-use power button menu and select reboot..recovery to get to new blue recovery
-Flash newest cm7 build (if applicable), gapps and or mtd kernel if desired without wiping
-reboot, and enjoy cm7
Sent from my SCH-I500 using XDA App
Just saw your post. Will give it a try now.
When i'm in a bootloop and it hits the recovery part of the loop, i was able to get the error message (via using a camcorder lol)
-- Installing
Finding update package
E: unknown value for path []
E: Can't mount
Installation aborted
hope this helps,
many thanks
patrick
-----
edit:
tried your method to the dot. I get stuck on trying to flash CM7. Now instead of boot looping it just says
E: Error in /sdcard/cm7new/update-cm-7.1.0-fascinate-kang-0717-signed.zip
(status 7)
installation aborted.
i'm redownloading the update and will see if replacing it on the sd card will work. Otherwise...
-----
redownloaded & replaced the cm7 zip file on SD card. No success.
No luck w/ your method posted either...
Oi...
this is upsetting
Download the recovery in the cm7 thread and repeat the same steps but use the recovery from the cm7 thread instead of 3-30 fix all and that should work
Sent from my SCH-I500 using XDA App
efan450 said:
Download the recovery in the cm7 thread and repeat the same steps but use the recovery from the cm7 thread instead of 3-30 fix all and that should work
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Did that... just goes back into the bootloop from recovery => SAMSUNG => SAMSUNG/CM7 (not the skateborder screen) and gives me this errorr:
-- Installing
Finding update package
E: unknown value for path []
E: Can't mount
Installation aborted
------
edit:
okay i decided to flash MIUI fascinate 1.7.15 instead of CM7 and see if that works.
Well MIUI is running, but the weird thing is i still get SAMSUNG/CM7 boot screen before the MIUI boot screen comes up...
i am so confused!
I went through that same nightmare trying to install MIUI. CM7 or MIUI would give me status 7, and sometimes CM7 would go through, but just bootloop like you mentioned.
I tried about everything, and the only thing that worked for me was to first flash the 7/4 CM7 release for CWM 4.x, then flash MIUI over that. With any luck, the same will work for you for newer CM7 releases.
Unfortunately, like someone mentioned, the file was removed for some reason or another. I've still got it, so I reuploaded it for you, but jt, if there was some particular reason it was removed, say the word and I'll delete this copy. Otherwise, it's probably best to keep it up for people with this issue.
So basically, wipe data/cache/etc., flash the 7/4 CM7 release. Get that running, then reboot into recovery from CM7. Don't use the three-button method. Then wipe again, and flash the zip for whatever release you want.
mediafire.com/?u1n0wcqbwpuvts2
Download that file and flash that...it's how I got in to cm7 for the first time from eb01...if you are still on miui you can flash this with the blue recovery, wipe all and install
Sent from my SCH-I500 using XDA App
Many thanks to both your help! It has been of great assistance.
I downloaded the CM7 file posted, and will flash tomorrow. MIUI is running on it's first shot, and i'm entranced by it (for the time being).
However i am liking CM7 better, although both have many similarities
pmanliu said:
Many thanks to both your help! It has been of great assistance.
I downloaded the CM7 file posted, and will flash tomorrow. MIUI is running on it's first shot, and i'm entranced by it (for the time being).
However i am liking CM7 better, although both have many similarities
Click to expand...
Click to collapse
No problem, glad to help. If you end up flashing it, give us an update. Hopefully it'll work that way.
I used Cyanogenmod for a while back when I was more into stock ROMs. On different devices, though. It wasn't bad. But I flashed MIUI a few days ago and haven't looked back since. It's a great ROM. MIUI or CM7 is your choice, and I haven't used CM7 enough to say much about it, but MIUI has my full support. I never thought I'd switch from UKB so easily.
efan450 said:
Try it again and record your steps exactly and post them and I'll try and see what went wrong...it could just be a corrupt download of one of your files or just a simple missed step. What build are you on and what rom are you trying to go to?
Edit: this is what I have done multiple time without a hitch
regardless of what build and rom your on..
-pull your battery
-odin official vzw EB01 (pda button only..just a reminder) and the atlas
2.2 pit file and check the repartition box (I use odin v.1.7, but it shouldn't matter) and let odin do it's thing
-install battery and fully boot and let it sit for a minute our two after it loads
-pull battery
-odin recovery jt's 3-30 fix all... (found in nitsuj's sticky in the development section under recoveries)
-insert battery
immediately three finger boot into recovery and wipe everything
-flash newest cm7 build..I can't remember the date (I used the 7/4 build to get on to cm7 but it has been removed but the latest on will work)
-reboot fully
-use power button menu and select reboot..recovery to get to new blue recovery
-Flash newest cm7 build (if applicable), gapps and or mtd kernel if desired without wiping
-reboot, and enjoy cm7
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
So you never used jt's cm7 fix odin package?
Nope..I was able to go to cm7 with cwm3-30 fix all with no problem and I was able to go to it from otb's 3.x.x.x recovery...either way I've been back and fourth a few times but never had to use the 4.x.x.x. fixed recovery...maybe I'm just lucky but I know a few others have had success with those recoveries as well...you just flash it like normal...wipe everything and install the 7/17 build...reboot...and just make sure if you want to flash gapps or the glitch kernel you use the power button menu to reboot recovery...no three finger booting anymore.
Sent from my SCH-I500 using XDA App
Solution
pmanliu said:
Did that... just goes back into the bootloop from recovery => SAMSUNG => SAMSUNG/CM7 (not the skateborder screen) and gives me this errorr:
-- Installing
Finding update package
E: unknown value for path []
E: Can't mount
Installation aborted
Click to expand...
Click to collapse
I was getting the exact same thing.
Started after I flashed the glitch v12 kernel on top of nightly #29. No problems.
Then I used ROM Manager to download nightly #35
Rebooted into CWM 4.0.1.5 orange via power button
Navigated to CWM folder to find nightly #35 to install from zip
Selected to install, checked for BML/MTD, said complete, auto rebooted
Boot loop with the above quoted errors, never gets to skateboard logo
Tried adb solutions, not enough time to issue adb commands before reboot
three fingered into cwm4 dark blue, got the usual expected E: can't find errors
tried restoring nandroid backup, auto reboots, no change, same errors as in quote
three fingered into cwm4 dark blue, tried flashing nightly #35 from RM download, no change
3fgered back into cwm4 dblue, flashed nightly #29 from SD that I had previously direct downloaded from cm7 nightly website, phone checked bml/mtd status, auto-rebooted, completed install.
Phone booted up normal with cm7 kernel, nightly #29, Data had been wiped
Used power button to reboot into recovery 4.0.1.5 orange
restored nandroid backup, rebooted
all is good! bazinga.
What I've learned from this is that using ROM Manager to download nightlies is risky. It may work fine if you use ROM Manager to download, wipe, and install, but if it fails during any of those (which it seems to do frequently) you could be out of luck with a headache. Best practice seems to be to download nightly directly from the cm7 website or copy it from your computer to the SD card and reboot via the power button into recovery and install that known good copy you downloaded via the cm7 website in the browser or transfered from your computer to the SD card. ROM Manager does something weird. This has occurred to me 3 separate times with ROM manager and with different nightlies. Also, it is worth noting that jt does not support the Glitch kernel for use with CM7 nightlies and a lot of issues seem to stem from using it. It is amazing when it works, but seems to add a lot of risk. YMMV
Let me know if this has helped or if anyone has any questions. Sorry for it being long, just trying to be thorough as there was no info out there to help me when this happened so I hope I can be of help to someone else.
Just got my gtab for $270 as a toy and have been reading all the material I could find about flashing a new ROM waiting for it to arrive.
Of course, I got ahead of myself and may have screwed up right out of the box.
I forgot to see which boot loader I have (like I said...I was excited).
I downloaded CWM...installed it per the 'dummies' web page...all good.
Downloaded BL1.2 CM7.0.3 and transferred it per the dummies page...and hit install from zip file. It then dumped back to CWM where I installed GAPPS while still in CWM.
Then hit system reboot, and it got to the CM7 android screen with the looping arrow in a circle. Problem seems to be that it's been sitting on that screen with a looping arrow for about 20 minutes now. I read that it takes a while for the first boot to load everything, but am pretty sure 20 minutes is more than generous?!
Is there a way to see what BL I've got from CWM having already wiped out the method to find out (going into setting in android OS) by virtue of starting the CM7 ROM load?
Should I give up on this install of CM7, turn off the gtab, go back into CWM and try the install again AND reboot before installing GAPPS?
Having forgotten to look at the BL version, does it makes sense that I would have likely got BL1.2 being that this gtab is brand brand new?
Any help would be appreciated.
Thanks,
Joe
San Antonio TX
joseph.fox said:
Just got my gtab for $270 as a toy and have been reading all the material I could find about flashing a new ROM waiting for it to arrive.
Of course, I got ahead of myself and may have screwed up right out of the box.
I forgot to see which boot loader I have (like I said...I was excited).
I downloaded CWM...installed it per the 'dummies' web page...all good.
Downloaded BL1.2 CM7.0.3 and transferred it per the dummies page...and hit install from zip file. It then dumped back to CWM where I installed GAPPS while still in CWM.
Then hit system reboot, and it got to the CM7 android screen with the looping arrow in a circle. Problem seems to be that it's been sitting on that screen with a looping arrow for about 20 minutes now. I read that it takes a while for the first boot to load everything, but am pretty sure 20 minutes is more than generous?!
Is there a way to see what BL I've got from CWM having already wiped out the method to find out (going into setting in android OS) by virtue of starting the CM7 ROM load?
Should I give up on this install of CM7, turn off the gtab, go back into CWM and try the install again AND reboot before installing GAPPS?
Having forgotten to look at the BL version, does it makes sense that I would have likely got BL1.2 being that this gtab is brand brand new?
Any help would be appreciated.
Thanks,
Joe
San Antonio TX
Click to expand...
Click to collapse
Yes, you can temrinate your install if it hasn't finishws. Congrats on your first brick. Sometimes it just happens even when you use the correct files.
If it's a new tab you most likely you were on 1.2. If you boot back to CWM (PWR & Vol+) it will give you the CWM version. If you loaded the 1.2 CWM version it will say V3.0.2.8. In CWM try a wipe data/factory reset, wipe cache, wipe dalvik cache & fix permissions and then reflash the rom & gapps. If it loops again, go to dummies and run code red (use the version of nvflash with cwm). Follow the instructions step by step & download everything via his links since his instruction are written with them in mind. If you have problems just post back.
Al
Thanks for the advice! I did load CWM-BL1.2, and I guess by virtue of the fact that CWM-1.2 didn't crash my system, that I had BL1.2 on the gtab.
Went back and tried to load CM7 7.0.3 again, but no luck; then revisited the catch-all GB ROM thread and downloaded CM7 7.1RC, and it loaded.....so I'm up and running!
Now just got to learn more about the market....numerous favorite programs don't show up in the market.
Thanks again!
So, I SBF'd 2.3.4, rooted, and flashed Eclipse 1.2rc3. Ran great. Today, I accidentally hit recovery in Eclipse Parts without installing it first. Now it loops at the Eclipse boot animation. First try: factory reset and wipes, flashed Eclipse again- same problem. Second try: factory reset, SBF'd again, root, wipe, flashed Eclipse- same problem. I don't know what it could be. Suggestions? Any help is greatly appreciated.
Very strange.
Did you try a fresh download of the rc3 zip? Maybe bad download? Rare but I hear it happens.
how long was it at bootanimation? Mine played the eclipse bootanimation for almost ten minutes when I first flashed it.
ashclepdia said:
Very strange.
Did you try a fresh download of the rc3 zip? Maybe bad download? Rare but I hear it happens.
how long was it at bootanimation? Mine played the eclipse bootanimation for almost ten minutes when I first flashed it.
Click to expand...
Click to collapse
Yes, I got new downloads of the SBF and Eclipse. I should clarify: from reflashing and doing a new SBF, I'm able to access the phone once. After doing a single reboot, the phone then bootloops and I'm forced to do a factory reset/start the process all over because it will sit at the boot animation for forever. Previously, I had no problems. Ran 2.3.3 with the latest Eclipse and did all necessary steps in transitioning to 2.3.4. I have no idea what to do.
[edit]
The issue may have been resolved. I did another factory reset and have been able to reboot a few times without a bootloop, so far.
Thread closed @ OP request.
I have my phone rooted and BSR/busybox/superuser installed. How do I flash it and actually put the rom on the phone?
(P.S. Its eclipse 2.1)
Well you have a lot of reading to do but let me give you a few important tips:
1) Before doing anything else make sure to go into your BSR and make a nano back up of your stock system. If you do not know how to do nano back ups then read up on that. You will be doing that for different roms. http://forum.xda-developers.com/showthread.php?t=1318083
2) Make sureyour kernal matches the version of the rom. For example you want to flash eclipse 2.0+ this is made for 2.3.5 update. If you are stock you are probably 2.3.4 Some have flashed eclipse 2.0+ and had no issues but it is not recommended.http://forum.xda-developers.com/showthread.php?t=1313103
this thread should help you out a lot also.
3) Once you get your stock Rom backed download the rom of your choice onto your sd card. Go back into BSR and first wipe data factory reset, wipe partion cache, go into advance and wipe Dalvik cache. Once you wiped the big 3 go to install from sd. Locate the rom using your volume buttons and power button to select. Sit back and let the rom run. Once it is done you can reboot now or flash one more safety step. It is the rerecovery zip. This actually allows you to restore your phone easy in the case of something bad happens. If you boot loop or something goes wrong then you just pull your battery and give it about 30 seconds. Put the battery back in and leave the phone off and just plug it into the wall charger. This will bring you straight to BSR. Here is that link http://forum.xda-developers.com/showthread.php?t=1426062
Also remember as long as you can get into BSR you can restore your nano backup of choice. Good luck and have fun. If you run into trouble we can help you out. The phone is pretty easy to fix.
I have made my recovery but was told it is ok to install Eclipse 2.1 on 2.3.4. I have the file downloaded but am I going to have to reprogram my phone for service?
If I'm not mistaken, flashing eclipse 2.1 on Android 2.3.4 can cause some Wi-Fi and data problems, so I highly recommend sbf-ing android 2.3.5 before flashing eclipse. Ill link a comprehensive sbf guide at the end of this post. To answer your question, though, you shouldn't have to activate your phone again if you havent sbf-ed or updated android. If you do decide to use 2.3.5, you will have to activate your phone again, though it only takes about 30 seconds in my area (could take more or less time depending on your signal strength).
http://forum.xda-developers.com/showthread.php?t=1317707
Hope I could be of assistance. If you need help, feel free to ask. I have no life so ill be here all day.
theredvendetta said:
If I'm not mistaken, flashing eclipse 2.1 on Android 2.3.4 can cause some Wi-Fi and data problems, so I highly recommend sbf-ing android 2.3.5 before flashing eclipse. Ill link a comprehensive sbf guide at the end of this post. To answer your question, though, you shouldn't have to activate your phone again if you havent sbf-ed or updated android. If you do decide to use 2.3.5, you will have to activate your phone again, though it only takes about 30 seconds in my area (could take more or less time depending on your signal strength).
http://forum.xda-developers.com/showthread.php?t=1317707
Hope I could be of assistance. If you need help, feel free to ask. I have no life so ill be here all day.
Click to expand...
Click to collapse
I have managed to softbrick my phone. No it is stuck on the "dual core technology" screen and I can't do anything
Spanks906 said:
I have managed to softbrick my phone. No it is stuck on the "dual core technology" screen and I can't do anything
Click to expand...
Click to collapse
Have you pulled you battery and tried it again? If you have I'd sbf back to 2.3.4 and then update to 2.3.5 then root it, and then install BSR and go into recovery and like said above, wipe the "big 3," install the ROM and then reboot and see if that helps.
Spanks906 said:
I have managed to softbrick my phone. No it is stuck on the "dual core technology" screen and I can't do anything
Click to expand...
Click to collapse
I tried installing it just now... It gets past the dual core but sticks on the ECLIPSE loading screen... wtf? any idea how to load the original os?
GaryMcDroid said:
I tried installing it just now... It gets past the dual core but sticks on the ECLIPSE loading screen... wtf? any idea how to load the original os?
Click to expand...
Click to collapse
Sbf back to 2.3.4....its not too hard. Search for it.
Sent from my MB870 using xda premium