I'm trying to go back to 2.2 from cm7 and I'm having some issues with odin. First off, I can't get gapps to install. I've tried all of the following:
gapps_update-2.3.5-gb-20110725-signed
gapps-gb-20110613-signed(1)
Also, wi-fi is not working with cm7.
Now for the odin issues...
I have tried flashing DL09, EB01, ED01 and ED05 with odin versions 1.3, 1.7, and 1.83. None have worked. I'm getting an error message when I connect with the USB. Is it possible that the cord is bad? Could it be that simple?
I'm completely frustrated here. I have no market, gmail, or anything else, and can't revert to an earlier build. I'm hoping someone here has the experience and/or know how to help me out.
uofatree said:
I'm trying to go back to 2.2 from cm7 and I'm having some issues with odin. First off, I can't get gapps to install. I've tried all of the following:
gapps_update-2.3.5-gb-20110725-signed
gapps-gb-20110613-signed(1)
Also, wi-fi is not working with cm7.
Now for the odin issues...
I have tried flashing DL09, EB01, ED01 and ED05 with odin versions 1.3, 1.7, and 1.83. None have worked. I'm getting an error message when I connect with the USB. Is it possible that the cord is bad? Could it be that simple?
I'm completely frustrated here. I have no market, gmail, or anything else, and can't revert to an earlier build. I'm hoping someone here has the experience and/or know how to help me out.
Click to expand...
Click to collapse
Instructions are under stickies in the development section for proper Odin from cm7or miui
There have been reports that only stock cords work for connection to PCs in some cases. Try the instruction under stickies before you give up on your cord.
Sent from my SCH-I500 using XDA Premium App
I did follow those instructions. The problem is that odin isn't flashing properly...thanks tho
Have you tried to reinstall the drivers directly from the Samsung website and use the stock MD5 for Verizon?
Related
I've saved a couple i9000 Odin flashed Fascinates with this method so it should work.
First, grab my DI01 All in One. You need an all inclusive package.
http://adrynalyne.us/files/kernels/DI01package3.tar.md5
You will need odin3 v 1.30. Google for it.
You also need Heimdall.
Heimdall – Glass Echidna There is a readme in the windows version zip if you get stuck. Drivers must be installed for it as well.
You also need a copy of the samsung galaxy s usb drivers, because Heimdall will remove them when you use it.
[Drivers] MS Windows x86 and x64 USB Drivers for Samsung Galaxy S - xda-developers
You will also need a PIT file from me:
http://dl.dropbox.com/u/2056318/atlas_v2.2.pit
Steps:
1. Install Heimdall and drivers.
2. Put phone in download mode and plug it in to usb cable.
3. Unzip the Odin file. 7zip can do this, but will give an EOF error. Ignore the error.
4. Choose each section in Heimdall and add the appropriate file, including PIT. Check repartition. Primary boot loader is boot.bin and secondary boot loader is sbl.bin.
5. Start. Boot once, check for problems. If problems persist, continue.
6. Reinstall Samsung USB drivers for Odin. This may require a PC reboot.
7. Put phone back in download Mode and start Odin, making sure its detected.
8. Load the entire Odin package, not extracted into the pda section of Odin. Include the PIT file. CHECK repartition.
9. Run the process.
If all goes well, you should be back to stock, crappy Eclair 2.1 without force close errors.
On a whim last night I flashed cm7 from kaoscinate. It wasnt what I wanted (nothing worked except calls data and sms), so I tried to go nack to sc 2.4. And of course I was bricked. But I just odined the eb01 radio and voila, I was ok.
Not sure if that helps.
Sent from my SCH-I500 using XDA App
i went to cm7 from sc 2.4 aswell, and to get back to sc 2.4 i just flashed cwmfroyo edition through cwm, rebooted the recovery then wiped data, re-installed sc 2.4 and bam! i was back.
upsidedownaaron said:
On a whim last night I flashed cm7 from kaoscinate. It wasnt what I wanted (nothing worked except calls data and sms), so I tried to go nack to sc 2.4. And of course I was bricked. But I just odined the eb01 radio and voila, I was ok.
Not sure if that helps.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I wouldn't say you were bricked. Bricked means the phone no longer functions period, no matter what you do to it. But I'm glad this helped you. I'll probably use the DL09 All in One and then flash SuperClean back over that.
When you flash an All In One, you are taking your kernel and your radio (modem) back to that version as well. When you want to go back to Froyo or whatever, make sure you flash the radio along with whatever else your flashing.
Boot looped. Wouldn't get past Samsung logo. Not an uncommon problem for me. I have become very comfortable with Odin.
Sent from my SCH-I500 using XDA App
upsidedownaaron said:
I have become very comfortable with Odin.
Click to expand...
Click to collapse
haha yeah. It's saved me but a couple times mostly anytime voodoo is involved. Tried restoring a nandroid backup of EB01 after flashing CM7 and got force closes from hell. Odin'd back using the EB01 unbloated/deodexed.tar and everything booted fine. Tried to restore the nandroid and couldn't do anything because of the force closes. Think I have corrupt data somewhere though. I also made a backup of the apps and data in MyBackupPro and ended up in the same force close situation upon reboot after restoring all. Selectively restoring a couple apps worked fine. Oh well.
Basically, I can't sustain a data connection for longer than about a minute before my fascinate disconnects. It takes about a minute to reconnect, then it disconnects again. Over and over and over. It never affects phone calls because it's not losing signal, it's just dropping the data connection.
I've been poking around my phone a bit, and in the past week, but I can't pinpoint what I did that made this start happening. I was hoping this thread would save me, but it didn't. I went back to DI01 using heimdall, booted up, still had the same problem. Reflashed with Odin, same thing. Went back to SCv2.4 with EB01 modem, same thing.
I ask this in this thread because I'm wondering what part of the phone remains untouched even with the full DI01 flash? Like some kind of low-level device mode that I triggered?
If there is nothing then it must be hardware related, and I will get a replacement.
@gizmo, maybe its time to start all over again with adryn's full di01 odin restore. i have had to do that twice now. and it has saved my butt.
i have become pretty familiar now with rebuilding my entire phone. it only takes about an hour now to go from a rom i like, to soft bricking it and then back to the rom i liked before i soft bricked with another alpha i just couldn't seem to wait to try.
Why does the movinand.bin fail when using Odin?
upsidedownaaron said:
@gizmo, maybe its time to start all over again with adryn's full di01 odin restore. i have had to do that twice now. and it has saved my butt.
i have become pretty familiar now with rebuilding my entire phone. it only takes about an hour now to go from a rom i like, to soft bricking it and then back to the rom i liked before i soft bricked with another alpha i just couldn't seem to wait to try.
Click to expand...
Click to collapse
Sounds pretty familiar . I always have to be breaking my stuff to be happy.
I've done the full heimdall DI01, followed by full Odin, to no avail. I think I messed up something with the service programming on the phone, but reactivating it doesn't help. None of the factory reset options I've tried have cleared the activation settings back to stock. Anyone know how to accomplish this?
I suppose I should move to my own thread now.
Tried to flash a custom ROM for the 15th time or so, with the same result. E: Can't Symlink /system/bin/su
Failure at line 16
Have researched this error, thought I had it figured out. Obviously not. Feel like an idiot. I never had any problems loading custom ROM's on 2.1.
BTW, I am rooted thru S1Click, have backed up thru nandroid and Titanium, have installed 3e custom recovery, everything I have read I could be doing wrong I have changed. I have tried different makers- Bionix, Axura, Eugene, all with hte same errors, so I know it's not just the ROM file.
What am I doing wrong here?
I don't know.. but let's save everyone the trouble of answering this and let you odin back to stock.
It might be something you flashed etc..
tried that too. tried loading these ROM's right after rooting and adding ROM manager. It's just weird that know one can answer a specific problem like "failure at line 16". Surprised there isn't an answer to look up based on the Line 16 error.
I'm not pointing any fingers, because I don't know the answer either. Just know that if you you give me one of the basic replies, like try ODIN to stock, I've probably tried it.
What are you odining to? I've always had success going to back to jfd. Doesn't seem to be any issues with rooting or rom manager.
Trigger + Overstock = Awesomeness
yep. Odining to jfd.
One thing is that I always install 2.2 via mini-kies before attempting to install custom ROM. Reason being that for whatever reason, the super one click just does not want to install on 2.1. Could that be part of the problem?
Here's what I do and it works every time for me.
1. Odin to jfd
2. Root then install rom manager
3. Flash clockwork recovery
4. Download rom of choice to internal sd
5. Flash rom thru clockwork
6. Enjoy
That has never failed me.
Trigger + Overstock = Awesomeness
Check This Out....Tell me If It Helped You
http://forum.xda-developers.com/showthread.php?t=848737
I did it. FINALLY.
Loaded Simply Honey 2.5, and this thing is FAST and awesome. Such a cool ROM. I was so pumped when it actually worked. Thanks for all the help, guys. And all the great developers that put in hte time and work to make our phones what they should be. Good job, guys.
Glad you got it working. The first flash is pretty awesome.
Trigger + Overstock = Awesomeness
I had this happening yesterday, find and Odin Eugene's froyo that doesn't brick, followed by a stock Odin flash with checking repartition the second time to fully clear the problem, or it will happen again probably the next time you go to flash a rom.
Sent from my Loki powered Vibrant via the XDA App
Br1cK'd said:
I had this happening yesterday, find and Odin Eugene's froyo that doesn't brick, followed by a stock Odin flash with checking repartition the second time to fully clear the problem, or it will happen again probably the next time you go to flash a rom.
Sent from my Loki powered Vibrant via the XDA App
Click to expand...
Click to collapse
This is the safest way and the best way.
I'm a longtime reader, don't post too much.
I'm in desperate need of help. If you're just going to flame me, please save that for a little bit so I don't have to sift through it to find some help.
I have the ROM addiction--I've flashed just about everything available for the Fascinate. I am a novice at best (i've fumbled my way through ADB before), but have never had any serious issues. Tried to flash EB01 modem through Odin (was at DI01 still somehow), and Odin froze. After 20 minutes I closed and disconnected my phone. It wouldn't boot after that. I was running the EC10 Rom and kernel (v2, before it became nameless). And I accidentally flashed the 3.0 clockwork, so I couldn't do anything through recovery.
I was trying Odin 1.3 from a Vista machine (not mine, I run Ubuntu) to begin with. Finally got my hands on a Windows 7 machine and Odin worked great. Restored to DI01, then flashed Superclean 2.9.2, and had the correct Clockwork. Less than a day later, Zeam (which I had as my default launcher) started force closing. Somehow Clockwork reverted back to 3.0, so all i could do was try fix permissions. Tried to odin restore again, and odin froze again, from the Windows 7 machine this time.
I've tried different USB cables and ports on three different computers (Windows 7 and two XP's. I can't get heimdall to recognize it in Ubuntu (might not have the drivers loaded properly there). Odin at least recognized the phone earlier, and it would start to flash. After 4 or 5 minutes the screen on my phone would go black and the flash would just freeze. Restarted the computer, reinstalled the drivers. Kept trying to flash. Then the screen started to change colors when it froze--always a solid color, but changed with different flash attempts. White once, pink once, and i think blue once.
I've been on IRC and received some tips, but it's hard to get sustained attention there. Especially since i'm a n00b. I've read every post I can find.
I NEED my phone. My girlfriend is out of the country right now, and that's how we communicate. Skype, chat, etc. It's killing me not to have my phone right now.
Can someone please help me out? And if you must flame me, how about wait until my phone is working please
Thanks in advance
Well i'm a noob too but... I have read you should use oem cables. I guess people have issues with non-oem ones. I don't know why odin shouldn't run though. Just try flashing the right cwm. You can either try odin or just flash it in cwm itself.
I was hacing the same problem with odin 1.3, i have been using odin 1.7 for months with no problems. Here is a link for the one i use, hope it helps. http://www.mediafire.com/?t093btu771q0bgi
Sent from my SCH-I500 using XDA Premium App
thanks Dale, i'll try that now.
Exzackly--i was able to flash the correct CWM at one point but couldn't install a ROM through it. and now I can't connect to Odin at all.
thatoneguy1983 said:
thanks Dale, i'll try that now.
Exzackly--i was able to flash the correct CWM at one point but couldn't install a ROM through it. and now I can't connect to Odin at all.
Click to expand...
Click to collapse
Because this kind of question has been popping up all over the place, i put together a post with instructions, and links for everything you will need just to help everyone out. hope it helps you. http://forum.xda-developers.com/showthread.php?t=1026746
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
I originally set out to upgrade to the latest CM7 build, but got an error about proper load EDITstatus 7) and it would not upgrade. So I decided to just put the official 2.3 on my Vibrant, however now it seems I have a different bootloader, the I9000 bootloader.
Ultimately I would like to get back to full stock, including bootloader so I can start fresh and hopefully get CM7 installed or at least the official 2.3 installed. I currently have stock JFD installed (using Odin).
If there is a way with my current install (i9000 bootloader and JFD) to get CM7 nightly I would love to know how to do that. I have tried the wiki instructions, but I am not able to get Heimdall Suite to work (I have Lion installed on my Mac, and it just does not want to find the phone no matter what on my pc). I have Rom Manager Premium but I do not see CyanogenMod listed under downloadable roms.
I have a ton of bookmarked pages of how to install CM7, but I think my problem is the bootloader as I can not seem to get CM7 to install from recovery. Perhaps there is a way to put CM7 on my T959 using Odin?
I have also found one download with a boot.bin and sbl.bin inside a .rar, but since there were not decent instructions for how to load these using Odin (if that is even how you do it), I didnt want to attempt bricking my phone.
I would say im a pretty advanced user, I have in the past installed with out any problem many different roms (Bionix, Miui). Any advice is welcome. Please help me get back to my precious CM7
When trying to install the CM7 kernel from recovery i get the following error:
assert failed: getprop("ro.product.device") =="galaxys2" || getprop("ro.build.product") == "galaxys2" .... Status 7
Click to expand...
Click to collapse
and so on.
I got my kernel from here and have tried kernels from the CM7 wiki, as well as roms from there as well. I know it normally means it is a miss match between the phone and software (status 7), but I have a T959, and I have tried from the official vibrant wiki at CM7.
AK
austindkelly said:
I originally set out to upgrade to the latest CM7 build, but got an error about proper load and it would not upgrade. So I decided to just put the official 2.3 on my Vibrant, however now it seems I have a different bootloader, the I9000 bootloader.
Ultimately I would like to get back to full stock, including bootloader so I can start fresh and hopefully get CM7 installed or at least the official 2.3 installed. I currently have stock JFD installed (using Odin).
If there is a way with my current install (i9000 bootloader and JFD) to get CM7 nightly I would love to know how to do that. I have tried the wiki instructions, but I am not able to get Heimdall Suite to work (I have Lion installed on my Mac, and it just does not want to find the phone no matter what on my pc). I have Rom Manager Premium but I do not see CyanogenMod listed under downloadable roms.
I have a ton of bookmarked pages of how to install CM7, but I think my problem is the bootloader as I can not seem to get CM7 to install from recovery. Perhaps there is a way to put CM7 on my T959 using Odin?
I have also found one download with a boot.bin and sbl.bin inside a .rar, but since there were not decent instructions for how to load these using Odin (if that is even how you do it), I didnt want to attempt bricking my phone.
I would say im a pretty advanced user, I have in the past installed with out any problem many different roms (Bionix, Miui). Any advice is welcome. Please help me get back to my precious CM7
AK
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1117990
Thanks for the thread. This seems to have a the original bootloaders, and a lot of other nice bootloaders for gingerbread. I will test it out tonight and let you know if this worked for me.
If you happen to have a link for installing CM7 with Odin please let me know.
austindkelly said:
Thanks for the thread. This seems to have a the original bootloaders, and a lot of other nice bootloaders for gingerbread. I will test it out tonight and let you know if this worked for me.
If you happen to have a link for installing CM7 with Odin please let me know.
Click to expand...
Click to collapse
glad its what you wanted, i was in abit of a rush and just read the thread name so posted that
I have been trying some stuff, the official bootloader from there didnt pass MD5 check in odin. please read my update/edit if you can help.
I, too, have been messing around with the Vibrant way too many times and it has bricked on me at least 6 times already because (stupid me) I went from ROM to ROM without Odin-ing back to stock.
Pertaining to your matters, Im not sure exactly where you're stuck right now. If you're stuck ODIN-ing, check to see if you have the right PIT file. If anything, redownload the stock JFD and stock PIT file and re-do it again. I've read somewhere, you really cant "brick" an android unless its hardware related or you throw your phone out the window.
If you're stuck trying to get CM7 on your vibrant then... wait, why are you trying to get Nightlies on your vibrant? I say you're better of flashing CM7 Trigger Redux (which is what I'm using now). I've heard its much better with more features (working GPS and more) than Nightlies. In case you wanted to check it out, heres the link:
http://forum.xda-developers.com/showthread.php?t=1156123
But anyhow, you're decision. From past experiences, after I ODIN back to stock, I rooted the stock and downloaded ROM Manager and then flashed the ROM that I wanted like Trigger Redux or Bionix. This pretty much worked for me. Hope this helps.