[Q] Flashing to bionix 1.3.1 from CM7 HELP - Vibrant Q&A, Help & Troubleshooting

I flashed my vibrant from bionix 1.3.1 with touchwiz to the CM7 just to see what was on CM7, the problem i'm running into now is that i'm trying to flash it back to bionix until CM7 becomes stable. It now states the following:
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.
As far as i know, i researched the problem and the problem i believe has to concern with the way CM7 and the recovery work with scripting.
I just want to know how to get back to bionix, i'm relatively new to this flashing and stuff so i would like a detailed description, even maybe a step by step answer but at this point any answer would work.
Additional Information:
I have a forward facing camera installed on my vibrant this is NOT the sgh-t959v, this is the sgh-t959 with a camera mod.

lfrenkel said:
I flashed my vibrant from bionix 1.3.1 with touchwiz to the CM7 just to see what was on CM7, the problem i'm running into now is that i'm trying to flash it back to bionix until CM7 becomes stable. It now states the following:
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.
As far as i know, i researched the problem and the problem i believe has to concern with the way CM7 and the recovery work with scripting.
I just want to know how to get back to bionix, i'm relatively new to this flashing and stuff so i would like a detailed description, even maybe a step by step answer but at this point any answer would work.
Additional Information:
I have a forward facing camera installed on my vibrant this is NOT the sgh-t959v, this is the sgh-t959 with a camera mod.
Click to expand...
Click to collapse
You MUST Odin back to stock JFD with repartition first, before going back to a Froyo ROM, including Bionix 1.3.1

Mr. Apocalypse said:
You MUST Odin back to stock JFD with repartition first, before going back to a Froyo ROM, including Bionix 1.3.1
Click to expand...
Click to collapse
How can I do that ??

Use the toolbox stickied in the Dev section. Has pit and tar files, drivers,...

He's right. You have to flash back to stock. You can try Heimdall One-Click, which will do all, he work for you.
Sent from my SGH-T959 using XDA App

odin back
I went through the same issues this past Friday. I had upgraded to ICS v13 and could not for the life of me get GPS to work.
I crashed my phone trying to load bionix v1.3.1 from cwm 5.x. had to Odin back and install cwm, and then update to bionix's rom.
Should be easy once you get all the files and get your drivers installed and your phone into download mode.

Related

Which recovery to use? 2.5.1x vs 3.x...

So I can't figure out which recovery is better, more useful. I was on 2.5.1.x forever because most scripting is still (if I remember correctly) Amend, whichever is the older one. But I know 3.x.whatever is the newest that we pretty recently got ported to the Fascinate, but it uses Edify and I keep hearing it isn't backwards compatible. I just switched from JT's last kernel to OTB 1.4 pulled from the Comm ROM, which forced me to 3.x.
Any ideas if I should flash back down to 2.5.1.x or just keep 3.x?
edit: *clarified scripting names
NoHolidaysForAHooker said:
So I can't figure out which recovery is better, more useful. I was on 2.5.1.x forever because most scripting is still (if I remember correctly) scriptify, whichever is the older one. But I know 3.0.whatever is the newest that we pretty recently got ported to the Fascinate, but it uses edify and I keep hearing it isn't backwards compatible. I just switched from JT's last kernel to OTB 1.4 pulled from the Comm ROM, which forced me to 3.0.
Any ideas if I should flash back down to 2.5.1.x or just keep 3.0?
Click to expand...
Click to collapse
If you are gonna stick w/ TW Rom, use Edify.
However, a lot of scriptings in AOSP/CM7 are Amend, so for time sake, use 2.5.1.x.
also as a stupid sidenote, i'm siked to finally have found someone else from hawaii.
another related question
in another related question, does edify/amend scripting apply to clockwork recovery, SU or busybox zip packages or is it just to how ROMs and themes are coded? just so in the future i don't mix it up, flash packages in the wrong recovery and mess with the phone

CM7 update looping

Hello,
I was trying to update my phone to CM7's Gingerbread nightlies. My history is Stock Eclair to Bionix froyo rom. I was trying to update directly from Bionix to update-cm-7-INITIAL-GalaxyS_B-signed.zip using CWM, but when the installation begins it keeps looping (switching on - Vibrant screen - CM7 screen - first 5-6 lines - swicthing off).
Maybe I should have updated from stock Froyo instead. But I can't find the stock PIT and TAR file to odin back. Googling for past 2 hours with no result (got Eclair files though).
Am I going the right way? Can someone direct me to the files I can use to odin back to froyo and update to CM7?
Thanks!
azoicwight said:
Hello,
I was trying to update my phone to CM7's Gingerbread nightlies. My history is Stock Eclair to Bionix froyo rom. I was trying to update directly from Bionix to update-cm-7-INITIAL-GalaxyS_B-signed.zip using CWM, but when the installation begins it keeps looping (switching on - Vibrant screen - CM7 screen - first 5-6 lines - swicthing off).
Maybe I should have updated from stock Froyo instead. But I can't find the stock PIT and TAR file to odin back. Googling for past 2 hours with no result (got Eclair files though).
Am I going the right way? Can someone direct me to the files I can use to odin back to froyo and update to CM7?
Thanks!
Click to expand...
Click to collapse
If you have Vibrant you choose a wrong CM7 ROM.
ODIN back to JFD, root, install CWR, and get the VIBRANT CM7 ROM http://mirror.teamdouche.net/?device=vibrantmtd
Thanks! That fixed it. The cyanogenmod post said it should be in stock 2.2. So every time I change a ROM I need to go back to JFD? Or is it only a precautionary option?
Once on CM7, no need to flash back--just update.

[Q] Help finding a ROM that works!!!!

Hey all. I am having trouble finding a Rom that will work on my Fascinate. I have ROM Manager and all the options I am getting from that are for builds that are different than mine. I tried several that were not labeled with a build and they all failed. I am using Clockwork Mod recovery. As it finishes the restart and begins applying the Rom it says that files failed to initialize. Operation aborted. Here are my phone details:
Firmware: 2.2.1 Froyo
Base band: S:i500.04 V.EC01
Kernel:2.6.32.9
Build:SCH-I500.ED03.
Any suggestions on a Rom and kernel (non-voodoo please) that will work with my phone? Am I doing something wrong? Do I need to flash via Odin to accomplish this? I would rather use Clockwork Mod if possible. Any help or suggestions will be greatly appreciated. Please excuse my ignorance as I am pretty new at this rooting stuff but learn a bit more everyday. Thanks again.
1. ROM manager is a big no-no for the fascinate.
2. You probably need to install a newer CWM via odin.
3. I am using ComRom2.1 w/ OTB 1/6 kernal (voodoo) but all you have to do is disable voodoo in the CWM settings.
4. Not sure why you don't want a voodoo kernal.
http://forum.xda-developers.com/showthread.php?t=1013312
Scroll though that thread. It has all the current roms and kernals and even CWM versions.

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] I am looking for the stock T959 (Vibrant) bootloader, and detailed instructions.

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.

Categories

Resources