[Q] CW 7.1 /MIUI gapps dont work. - Fascinate Q&A, Help & Troubleshooting

So I've done the whole go back to stock reflash cwm etc. bla bla. Are there thoes of you who are running CM 7.1 and or MIUI with glitch running stably? When in both instanced i could not get Gapps to install. I was also getting force closes on rom manager and G voice. I've gone all the way back to stock with the atlas pit file etc. twice and every time i get no gapps and force closes. Am I doing something wrong or missing something?? Ive followed all instructions to the letter, why does this keep happening?

what stock package are you using when odining back to stock? Fwiw Im running cm7.1 w/ glitch v13 rc and everything works great. I have only had one data drop and toggling airplane fixed. Also once in awhile my dock icons disapear, but for the most part everything has been good enough to call it a daily rom.

I believe it was ED05 stock. Then achieved root using the adb push method. Is there a different rom that I should be using when flashing to cm7/miui based roms. Also odin'd the recovery that was supposed to be compatible with cm7 ect.

propylene22 said:
I believe it was ED05 stock. Then achieved root using the adb push method. Is there a different rom that I should be using when flashing to cm7/miui based roms.
Click to expand...
Click to collapse
try dl09 eclair and follow the steps in section 3 of my guide. No need to root first!
http://forum.xda-developers.com/showthread.php?t=1238070

I had this problem as well. The trick is to boot into clockworkmod through CM7 and NOT by the traditional hold both volume buttons along with the power button. So to do it correctly, put gapps on your scard, in CM7, press the power button like you are going to boot off but instead select Reboot. Now select recovery. This is some special CM CWM and now install zip and choose gapps. All will be well.

Related

[Q] froyo

I am coming from one of team whiskeys 2.1 roms and I havent looked much into other roms since then about 2 months ago or so. I want to try going Froyo with Nero 3. I have Odin downloaded and kind of get how to use it and stuff. But when going from eclair to froyo everybody says to odin to stock.. Well which rom is the stock one and is it stock 2.1 I am supposed to odin back to or is it the 2.2 stock? and Is there any other steps I should follow after odin-ing back to "stock" I have downloaded much of what I needed and have been searching for a while And i remember seeing a post a long while ago on the steps i should follow but my search skills aren't the greatest. Thanks in advance for any help!
dev_man77 said:
I am coming from one of team whiskeys 2.1 roms and I havent looked much into other roms since then about 2 months ago or so. I want to try going Froyo with Nero 3. I have Odin downloaded and kind of get how to use it and stuff. But when going from eclair to froyo everybody says to odin to stock.. Well which rom is the stock one and is it stock 2.1 I am supposed to odin back to or is it the 2.2 stock? and Is there any other steps I should follow after odin-ing back to "stock" I have downloaded much of what I needed and have been searching for a while And i remember seeing a post a long while ago on the steps i should follow but my search skills aren't the greatest. Thanks in advance for any help!
Click to expand...
Click to collapse
If you are on Fusion 2.1, just use rom manager and install this using install from SD card option. You should be OK. If that does not help try ODIN.
Incase you are stuck and need to revert back to stock or want to take the long route just incase then use this file
Stock Rom
PIT File for ODIN
Thanks. I just tried it and everything seemed to have flashed over okay. I just didnt know if it was required to odin to stock first or not. Everything is working pretty good so far. gonna mess around with a few new kernels now.
Cant seem to get clockwork mod recovery to work
Any suggestions on how to get back into the clockwork mod recovery so i can install from zips again?
dev_man77 said:
Any suggestions on how to get back into the clockwork mod recovery so i can install from zips again?
Click to expand...
Click to collapse
Install Rom Manager from Market, Make sure you have Busy Box & Super user app. Launch rom Manager, Select Clockwork Recovery, Select your device from pop up window. Select Reboot to Clockwork Recovery menu. Phone will restart, select reinstall packages it will restart again and take you into Clockwork menu.
Tried this twice and it keeps taking me back to the stock recovery mode... Dont know why.
*edit*
Had to reinstall packages twice and it finally worked. Everything is gravy. Gonna see if the SuperIO kernel is better than the stock+Voodoo5...

Anyone care to help out a n00biE?

So, Where do I begin? I, like everyone else was upset about not getting ota 2.2 for the fascinate. So i decided to go through the whole rooting thing and used odin to get a sc 2.2 rom, But it wasn't running so smoothly, so I tried to put a new rom on using rom manager...Now heres the problem, I did something wrong in recovery manager and now I can boot the phone up, into my 2.2 rom still, but I cant do anything because it repeatedly comes up with the messages that you get when a program crashes(Force close button)
So basically I need a way to get back to any working ROM (stock is fine too), which doesn't need access to the phone os. I can provide any other details necessary to fix he problem.
Please help me..
I will donate to whoever can get me working again!
http://forum.androidcentral.com/ver...tom-roms-w-root-clockwork-updated-3-25-a.html
Follow that link and do some reading there. Basically, it takes you through the process of using a program called Odin to completely flash a new, working ROM. It also has the most recent release of the SuperClean ROM which can also be found in the Fascinate Development section here.
dnnkbk said:
So, Where do I begin? I, like everyone else was upset about not getting ota 2.2 for the fascinate. So i decided to go through the whole rooting thing and used odin to get a sc 2.2 rom, But it wasn't running so smoothly, so I tried to put a new rom on using rom manager...Now heres the problem, I did something wrong in recovery manager and now I can boot the phone up, into my 2.2 rom still, but I cant do anything because it repeatedly comes up with the messages that you get when a program crashes(Force close button)
So basically I need a way to get back to any working ROM (stock is fine too), which doesn't need access to the phone os. I can provide any other details necessary to fix he problem.
Please help me..
I will donate to whoever can get me working again!
Click to expand...
Click to collapse
s13_slider said:
http://forum.androidcentral.com/ver...tom-roms-w-root-clockwork-updated-3-25-a.html
Follow that link and do some reading there. Basically, it takes you through the process of using a program called Odin to completely flash a new, working ROM. It also has the most recent release of the SuperClean ROM which can also be found in the Fascinate Development section here.
Click to expand...
Click to collapse
Well, it seems that you know how to use Odin (download mode, use the PDA button), what you probably didn't know was NOT to use ROM manager. It only works with the newest CWM, which does not work on our phones. And that doesn't matter b/c all of the roms for our phones are made to work with CWM Red (2.x, not 3.x).
So after you flash the new ROM (and the new modem) using ODIN, you can then select different kernels that you may want to use with that rom.
I've been using ROM manager pretty successfully. I just simply haven't upgraded CWM to 3.x
dnnkbk said:
So, Where do I begin? I, like everyone else was upset about not getting ota 2.2 for the fascinate. So i decided to go through the whole rooting thing and used odin to get a sc 2.2 rom, But it wasn't running so smoothly, so I tried to put a new rom on using rom manager...Now heres the problem, I did something wrong in recovery manager and now I can boot the phone up, into my 2.2 rom still, but I cant do anything because it repeatedly comes up with the messages that you get when a program crashes(Force close button)
So basically I need a way to get back to any working ROM (stock is fine too), which doesn't need access to the phone os. I can provide any other details necessary to fix he problem.
Please help me..
I will donate to whoever can get me working again!
Click to expand...
Click to collapse
Personally ide stay away from rom manager. ive heard nothing but bad things.. but to fix your mess ull need to odin like stated above.. but u dont have to flash the whole rom on odin.. just find a whole rom/radio/kernal package, use odin to flash clockwork 2.5 and you should b able to book into clockwork at that point and just flast the rom following the directions in the noob post under the dev section.. good luck
Thanks for the help guys! I originally got into this mess by trying to flash to JT1134's AOSP, uhmm here
http://forum.xda-developers.com/showthread.php?t=919864
and i read on that post (I think) that you cant use odin for that. Which makes sense as it isnt the same ".tar.md5" that my 2.2 sc rom was...How would I go about doing this, without rom manager?
Easiest way I can think of would be to use Odin for one of the SuperClean ROM's just to get your phone working as easy as possible.
Then, once it's functioning again, download the ROM and kernel zips(if you haven't already) and copy the zip file for the AOSP ROM you want along with the kernel. You can copy them to the root of the sdcard so they would be easiest to find in the coming steps. Also, remember the names so you can find them later.
Then pull up the shut down menu on the phone(by holding the power button) and choose the recovery option.
You should be in Clockword Mod Recovery at this point. You'll want to clear out the SuperClean ROM, so run through both the "wipe data" and "wipe cache" options in the menu. Run through those twice just for good measure.
Now scroll down and select install zip from sd card.
Next, select choose zip to install.
Find the zip file for the ROM, and select it. Then select the only Yes option on the list.
Repeat the last step for the kernel's zip file.
Press menu to get back to the main menu, and select reboot system now.
Wait out the reboot(it may take SEVERAL minutes this first time).
Enjoy AOSP!
s13_slider said:
Easiest way I can think of would be to use Odin for one of the SuperClean ROM's just to get your phone working as easy as possible.
Then, once it's functioning again, download the ROM and kernel zips(if you haven't already) and copy the zip file for the AOSP ROM you want along with the kernel. You can copy them to the root of the sdcard so they would be easiest to find in the coming steps. Also, remember the names so you can find them later.
Then pull up the shut down menu on the phone(by holding the power button) and choose the recovery option.
You should be in Clockword Mod Recovery at this point. You'll want to clear out the SuperClean ROM, so run through both the "wipe data" and "wipe cache" options in the menu. Run through those twice just for good measure.
Now scroll down and select install zip from sd card.
Next, select choose zip to install.
Find the zip file for the ROM, and select it. Then select the only Yes option on the list.
Repeat the last step for the kernel's zip file.
Press menu to get back to the main menu, and select reboot system now.
Wait out the reboot(it may take SEVERAL minutes this first time).
Enjoy AOSP!
Click to expand...
Click to collapse
I dont have that option when i hold the power button, i usually get into recovery through rom manager...This shouldn't make a difference right?
I have tried that when i do it, it starts to run the code and Aborts. The rull message is
"Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery. Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation aborted"
This probably spells out exactly what my problem is.....but i dont understand it...lol
I think I see the issue. Do you have CWM 3.x on your phone? I don't believe that works with the Fascinate. Head to this link:
http://forum.xda-developers.com/showthread.php?t=942021
And download the .tar file in the first post and use Odin to flash the correct recovery. Then, after that, hold the power button and both volume buttons(up and down) which will force you into the new recovery mode, which should be red. From there, you should be able to go forward with the flashing of your AOSP ROM and kernel.
Worked perfectly!!! This rom is Stellar!
Fantastic! I'm so glad you're back up and running!
Sent from my SCH-I500 using Tapatalk

How to Install AOSP ROMS?

I have tried for the past 4 hours to install the AOSP MIUI ROM. I have tried a newer recovery, a mtd kernel. No luck. I install the rom in CWM 2.5, but it boot loops at that point and states that the sd card can not be mounted. It then counts down to 20 and resets over and over. Can anyone shed light and provide steps?
Well the first thing I would do for yourself is to Odin back to stock using the 2.2 pit file as well as odining the stock 2.2 ROM. Make sure you repartition as well so that everything is formatted!!! This will solve SO many issues and give prospective forum members a place to start with your problems you are having.
2.2 Pit file - http://download180.mediafire.com/09z...atlas_v2.2.pit
2.2 stock froyo - http://www1279.megaupload.com/files/...EL.tar.md5.tar
I am going to assume you have odin and not link a download simply for the fact that if you have read ANYTHING pertaining to CM7 or MIUI in our forums you should be well aware of how to use it.
After wiping you will need to flash the modem you want via odin. They are located in the sticky in the dev thread.
After this you will need to flash the CWM that is located in the CM7 or MIUI threads themselves.
here is a link : cwm3_fixed_for_cm7-ODIN.tar
Use odin to flash it, then simply flash the AOSP package of your choice from the their respective threads here in the forums.
TedLWJR said:
I have tried for the past 4 hours to install the AOSP MIUI ROM. I have tried a newer recovery, a mtd kernel. No luck. I install the rom in CWM 2.5, but it boot loops at that point and states that the sd card can not be mounted. It then counts down to 20 and resets over and over. Can anyone shed light and provide steps?
Click to expand...
Click to collapse
Also worth noting that I missed in the first post. You mentioned CWM 2.5....sadly this will not work nor will it work with any other CWM floating around. The ONLY way currently to flash it is with the CWM I linked above. These are from JT and fixed to work with the AOSP ROMs.
from JT himself
*** The recoveries attached below are ONLY to be flashed on a BML ROM, ie: touchwiz based ROM or earlier, non-MTD CMx ROM. DO NOT FLASH THEM IF YOU ARE CURRENTLY ON CM7 OR MIUI MTD ROMS! ***
Click to expand...
Click to collapse
Thank you, I tried to use the new recovery provided by JT, alas it did not work for MIUI, I will try again tomorrow when spirits are higher, I usually start from DL09 and OTA my way back to ED04, Do i have to stay on EB01 or can i use ED04, and yes i am familiar with odin. Thanks again my friend.
TedLWJR said:
Thank you, I tried to use the new recovery provided by JT, alas it did not work for MIUI, I will try again tomorrow when spirits are higher, I usually start from DL09 and OTA my way back to ED04, Do i have to stay on EB01 or can i use ED04, and yes i am familiar with odin. Thanks again my friend.
Click to expand...
Click to collapse
Don't quote me.... It shouldn't matter (EB01, ED01, ED04...etc) All that is needed is the updated recovery to run the package install. The package will format your filesystem so your version should not matter. If you are referring to the modem... its your preference. I am on EC01 but last time I was on like ED04 or something...
Might also try flashing CM7 first, booting in, then flashing MIUI since they use the same BML format.
Still no dice, I'm sick of trying this, I have Odined back to 2.2 around 10 times already. A good write-up is definitely necessary.
What kernal are you loading with ED04, etc.. before trying CM7?
Stock as i think i read that the rom includes a kernel, should i try a MTD kernel and then flash CM7/MIUI?
No, I was just making sure you weren't loading any voodoo kernals.
When I had issues loading MIUI, I went all the way back to the DI01 all in one rom (odin) then DL09, then CWM Fix all (3.x), then MIUI. Load the rom before you load the MIUI cwr.
I'm having major problems too. I've tried about every method to get onto CM7, but I either end up with boot loops or get stuck on the GalaxyS/CM7 boot screen for a long time (over 30 minutes).
I've started from almost every platform (stock back to DI01, comrom, evil, ....)
Used JT's cwm and still no go. I've rebuild my partitions in both odin and heimdall, I don't know what else to try myself.
I've gotten to the same place with the Galaxy S and Cyanogen screen, help is appreciated.
Sent from my SCH-I500 using XDA Premium App
im in teh same situation. ive tried doing everything i can find and i NEED miui on my phone.
haha seriously any additional help would be appreciated

[Q] Initial Install CM7... stuck in either boot loop or splash screen... forever! D:

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.

Can't install any application on my Vibrant

Hello, at the start i wanted to install some new ICS rom for my Vibrant..i try to root it with one click and i couldn't do that coz i had froyo(2.2update)..so i read some forums and found solution in odin...i used that to turn back to stock eclair where i rooted the phone ...but the problem is that now i can't install any application on the device(i need ROM manager)..i get to android market and ,click on application but nothing is happening, no download at all...than i try to use android injection with apks that i found on the net , but nothing, i always get INSTALL_FAILED_OLDER_SDK...so now i am stuck i have: fimware version-2.1 update 1,baseband T959UVJFD, kernel 2.6.29 can you tall me should i do?? thx
Read the guide in my signature on how to install ICS ROMs. It has an update.zip that you can use for CWR.
ROM manager no longer supports 2.1 (Eclair), so that is why you can't see it in the market.
Download the clockwork mod recovery file (update.zip) and save it to the internal storage on the phone. Then reboot into recovery and install packages. Might have to do it twice. Then you'll be in CWM recovery. Install from from there.
Sent from my SGH-T959 using XDA
The AIO Vibrant toolbox might be something you need to look at. you can find it here http://forum.xda-developers.com/showthread.php?t=954509
guide
i followed your guide...flashed CM7, than i try to flash Euphoria RM2.1(ICS) and flashing is starting all ok , than after 30 secs i see message 'Random offset 0x302' and it's not going forward with flashing,i pulled out battery and try 2 more times,and there is always the same problem, i'm on CM7 now(and i don't have google play what should i do? can you recoommand me some good and stable gingerbread ROM for Vibrant(if i goona be unable to install ICS Rom) thx
Woodrube said:
Read the guide in my signature on how to install ICS ROMs. It has an update.zip that you can use for CWR.
ROM manager no longer supports 2.1 (Eclair), so that is why you can't see it in the market.
Click to expand...
Click to collapse
FWIW, and this is not a knock on Team Passion (they do excellent work but few updates), but Euphoria is somewhat outdated. There are plenty of ICS ROMs out there that are more up-to-date and when ICS went from 4.0.3 to 4.0.4 there were significant code changes that were done. I suggest ICZen, or Slim or CM9.
But if you want to stay on Euphoria (AOKP based), this is from my guide:
If you get the RANDOM OFFSET error.
Don't freak out. This is an ICS security feature (as posted in Passion's FAQ post). All you have to do is pull your battery and boot back into recovery and reflash ICS over itself (just like you did with the initial CM7 bootloop) and it should push through. You may need to do this multiple times. I have read of people having to do it up to 5x. YMMV though.
Click to expand...
Click to collapse
Edit:
***----> I am having all kinds of trouble with my browser today at work, so if I don't respond right quick, that is why. But I'll get back to you or some others out there can help.
stack
man, now i am completly stack, i try to flash slim ics, found the file for vibrant, but it culdn't flash , in the middle it just stoped..and phone is just rebooting it self when i enter cw mod i can't install any other ROM from internal sd, it says no files found ffs now i can't even use phone, i need help emergently
Woodrube said:
FWIW, and this is not a knock on Team Passion (they do excellent work but few updates), but Euphoria is somewhat outdated. There are plenty of ICS ROMs out there that are more up-to-date and when ICS went from 4.0.3 to 4.0.4 there were significant code changes that were done. I suggest ICZen, or Slim or CM9.
But if you want to stay on Euphoria (AOKP based), this is from my guide:
Edit:
***----> I am having all kinds of trouble with my browser today at work, so if I don't respond right quick, that is why. But I'll get back to you or some others out there can help.
Click to expand...
Click to collapse
I suggest you Odin immediately. I fear that the next screen you will see is the Encryption Unsuccessful screen. Make sure you hit repartition in Odin though since you reformatted your system from RFS/Ext4 to MTD when you went to CM7.
odin
ok i get into odin , marked repartiton but is sais fail ??? what should i do now?
Woodrube said:
I suggest you Odin immediately. I fear that the next screen you will see is the Encryption Unsuccessful screen. Make sure you hit repartition in Odin though since you reformatted your system from RFS/Ext4 to MTD when you went to CM7.
Click to expand...
Click to collapse
If you do get past all of these, but this is unlikely for a normal flash, get either Iczen or chimera.
Sent from my SGH-T959 using xda app-developers app

Categories

Resources