Hi Everyone,
As the title states I'm looking for a .zip I can flash via Clockwork Recovery to get back to stock JFD baseband. I'm currently running Frankin Twiz 4 which is based off the JI6 build, but it would be nice to get back to JFD easily to flash other roms. I know I can use ODIN to get back to 100% stock but I have been trying to avoid ODIN like the plague. From an earlier post I read it seems it is possible to compile the JFD modem.bin into a flashable .zip file. The problem is I do not have any experience what so ever in compiling anything like this. I have scoured the forums looking for one and have been unable to turn up any results. Is there anyone who knows where I can find this or would be willing to compile JFD into a flashable .zip for Clockwork?
Thanks!
Second. This would be pretty nice to have.
So is there no one that can make this happen? I'm seeing in a lot of the new ROMS that are coming out where the devs are including the modem.bin install in their package, but this is only on the JI6 releases. A JFD modem.bin packaged into the stock rom would make going back to true stock SO easy. I think this would help a lot more ppl out than just myself... Again, I appreciate everything the community does to help! Sorry for asking for a little bit more...
think this is what you want
http://forum.xda-developers.com/showthread.php?t=740077
demo23019 said:
think this is what you want
http://forum.xda-developers.com/showthread.php?t=740077
Click to expand...
Click to collapse
Thank you, however after searching/reading through some of the posts JAC states that this does NOT flash the baseband but only the system partition. I am trying to find one that at the very least replaces the system partition and baseband, and even better the kernel too.
yea sorry, i remembered seeing before never really read threw
This would be nice, but I'm pretty sure nandroid can not restore the kernel. I remember once trying to flash a vibrant 9 JFD backup I had after installing the JI2 leak. The phone just got stuck at the vibrant screen. Had to odin back to stock JFD.
So I looked over this and it seems.. (I'm assuming) all you would need to do is make an update-script executing redbend_ua to flash to the appropriate partitions. Looking through the bionix update-script shows that at least for the latest version, it just does this.
copy_dir PACKAGE:kernel_modem_update TMP:/kernel_modem_update
set_perm 0 0 755 TMP:/kernel_modem_update/redbend_ua
run_program /tmp/kernel_modem_update/redbend_ua restore /tmp/kernel_modem_update/modem.bin /dev/block/bml12
run_program /tmp/kernel_modem_update/redbend_ua restore /tmp/kernel_modem_update/zImage /dev/block/bml7
kernel_modem_update is a directory in the root directory of the rom zip.
looking up redbend_ua lead me to z4ziggy[dot]wordpress[dot]com/2010/09/15/rom-flashing-using-redbend_ua/
you can probably grab the zimage and modem.bin from the true stock odin flashable rom and put a package together to see if this works.. if nobody wants to try it out I can mess with it when I get home see if it restores the modem.
I'm not familiar with the exact requirements to do this but I don't think I really have anything to worry about on my phone.
Sweet Success!
Well I decided to be brave and just give ODIN a shot. Worked like a charm. I'm rockin' the stock once again.
Related
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.
ive been doing some reading and have some questions
1. is clockwork mandatory? id prefer to flash via odin.
2. can you recommend a touchwiz rom thats cleaned and based on the new ed01 source?
Well, Clockwork isn't absolutely mandatory, but the vast majority of ROMS/Kernels/Themes/etc. come packaged in .zip files which are meant to be flashed via CWM.
Odin uses .tar/.md5 files and is usually relegated to a more disaster recovery tool, or flashing items like a new radio. You CAN use Odin to flash ROMS, but you options can me more limited.
Here's a list of the most popular ROMS/Kernels/etc for the Fascinate:
http://forum.xda-developers.com/showthread.php?t=1013312
For Odin flashable ROMS, there's a great post at androidcentral.com:
http://forum.androidcentral.com/ver...tom-roms-w-root-clockwork-updated-3-25-a.html
Hope this helps.
its the the red/green/orange cw that im not crazy over 9i may be reading something wrong
You definately want to use RED cwm for the fascinate. Orange does not play nice at all, since support for amend scripting was removed. (Almost all fascinate ROMS use this type for flashing) If you accidentally flashed Orange through ROM Manager, you can use this post to help you get back to red:
http://forum.xda-developers.com/showthread.php?t=942021
Use either Odin (.tar file) or CWM (.zip file) to flash and you'll be back to red after manually booting into clockwork.
CWM really is much easier to flash, if for no other reason than not having to pull the case and battery off
havent flashed yet, just rooted, but i figured if vzw is dropping 2.2, i might as well do a custom.
just gotta decide
as i said im thinking clean, nonvoodoo. but i dont see an ed01, just an ec01
Pretty sure everybody will tell you ed01 and ec01 are the same, but I'm just going by the the general post on the matter.
Sent from my SCH-I500 using XDA Premium App
hhhmm then i guess what im waiting for now are restore files for ec01/ed01
or would older ones be ok?
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
Yes, ED04. Verizon could decide to make, um, some other ROM official tomorrow, and then wouldn't all this look silly?lol~ it happened! nothing to see in my thread move along to this one And why hasn't anybody done this before?
SCHI500VZW_ED04_stock_systemandkernel.tar.md5 (319.5 MB) http://www.multiupload.com/WH7E09IIF8
Obviously, it isn't a full Odin file. It includes just the stock kernel (which will flash stock recovery if given the chance) and the stock system partition image, and you would brick your phone if you tried repartitioning in Odin with this. Maybe if, for whatever reason, you feel the imminent necessity of getting your phone to look like your mother's ED04, you might find this interesting. Particularly interesting in the context of things like this and this. Use your imagination. If you wanna get a party started, you're gonna have to BYOB.
I also found these other files on the ground, after nearly tripping over them, but I couldn't quite decide what to make of them. I think they might have something to do with OTA.
SCHI500VZW_DI01toEA28_official_OTA_update.zip (15.77 MB) http://www.multiupload.com/NOX4L5QA1T
SCHI500VZW_DL09toEA28_official_OTA_update.zip (203.22 KB) http://www.multiupload.com/8Q3J5NUUY5
SCHI500VZW_EA28toED04_official_OTA_update.zip (97.96 MB) http://www.multiupload.com/ND2E1OV6ZQ
Edit:
lane32x said:
So if someone wanted to make their phone completely stock, we would need to do something like this?
1) flash DL09 rom + modem
2) flash the VZW updates (in order) by placing each one, in sequence, on the SD
3) and that would flash Kernel, Rom, AND modem, right?
Click to expand...
Click to collapse
Alright, I'll explain myself. Yes, flashing a known good full DL09 odin with repartition is one way to get things started. And yes, these are the official and signed OTAs, so they do update everything and they do work with stock recovery if renamed as just update.zip. Just remember that if you checked the repartition box in Odin, you need to boot into stock immediately after that to format the new partitions and allow your phone to save data.
There are other ways to use these files. For example, from a custom TouchWiz rom with ED04 modem, you might flash the partial ED04 Odin, do a factory data reset, and be done with it. Or you might have to flash the DL09 modem on top of that and use the modem delta upgrade technique. Or you might only want to unroot yourself from a rooted ED04 and keep all your data. It depends on your situation and preference, which is why I said to use your imagination. I included some links to help people with their research into what they have to do and why to get where they want.
The whole point of all this, besides putting the files out there, was to make damn sure that people can get to ED04 without having to rely on Verizon. I know some people were trying to get back to stock and odining the full DI01 or DL09, only to find that they couldn't initiate the OTA. And I've helped at least one dude who was (long story short) overseas.
Enjoy.
comradesven said:
Yes, ED04. Verizon could decide to make, um, some other ROM official tomorrow, and then wouldn't all this look silly? And why hasn't anybody done this before?
SCHI500VZW_ED04_stock_systemandkernel.tar.md5 (319.5 MB) http://www.multiupload.com/WH7E09IIF8
Obviously, it isn't a full Odin file. It includes just the stock kernel (which will flash stock recovery if given the chance) and the stock system partition image, and you would brick your phone if you tried repartitioning in Odin with this. Maybe if, for whatever reason, you feel the imminent necessity of getting your phone to look like your mother's ED04, you might find this interesting. Particularly interesting in the context of things like this and this. Use your imagination. If you wanna get a party started, you're gonna have to BYOB.
I also found these other files on the ground, after nearly tripping over them, but I couldn't quite decide what to make of them. I think they might have something to do with OTA.
SCHI500VZW_DI01toEA28_official_OTA_update.zip (15.77 MB) http://www.multiupload.com/NOX4L5QA1T
SCHI500VZW_DL09toEA28_official_OTA_update.zip (203.22 KB) http://www.multiupload.com/8Q3J5NUUY5
SCHI500VZW_EA28toED04_official_OTA_update.zip (97.96 MB) http://www.multiupload.com/ND2E1OV6ZQ
Click to expand...
Click to collapse
Wonder if the update zip files will update modem as well.
Great find, since I am on ed04 and would like a way back to it after I flash a new rom.
Sent from my SCH-I500 using XDA App
Nice "find."
comradesven said:
I also found these other files on the ground, after nearly tripping over them, but I couldn't quite decide what to make of them. I think they might have something to do with OTA.
SCHI500VZW_DI01toEA28_official_OTA_update.zip (15.77 MB)
SCHI500VZW_DL09toEA28_official_OTA_update.zip (203.22 KB)
SCHI500VZW_EA28toED04_official_OTA_update.zip (97.96 MB)
So if someone wanted to make their phone completely stock, we would need to do something like this?
1) flash DL09 rom + modem
2) flash the VZW updates (in order) by placing each one, in sequence, on the SD
3) and that would flash Kernel, Rom, AND modem, right?
Click to expand...
Click to collapse
Edit: Actually, I'll put this reply in the OP.
Quicker way to get to ED04 modem from DL09
View attachment DL09toED04_modemdelta.zip
This is much quicker way to get to ED04 modem once you odin DL09 radio. This was formerly under the stickies http://forum.xda-developers.com/showthread.php?t=1013312 for radios under http://adbdev.com/danknub/ but the link is now dead, so I thought I would put it back up here. Just talking radios here. The ED04 Odin in the op will get your system and kernel to ED04 stock.
Odin for DL09 radio /modem is under development sticky by nitsuj by clicking the first link in this post.
I'm wondering how I can get CWM back on my stock gingerbread fascinate now... I used the speedmod kernel to root, which had CWM built in. Then I replace it with stock GB kernel.. which has 3e recovery.
When I run ROM manager now with gingerbread the fascinate don't come up in the list no more.. there are 2 i9000's, one of those is a MTD... and 2 others. 4 in total.
I have the update.zip file which I downloaded from Rom Manager when I was on Froyo. Will that work? I'm afraid to try.
I've also seen methods of ADB pushing the recovery.bin over the current 3e. I just really not to sure which is the best way to do it, and I've done so much reading now it's got me confused.
Thx
Maniac
MrManiacNF said:
I'm wondering how I can get CWM back on my stock gingerbread fascinate now... I used the speedmod kernel to root, which had CWM built in. Then I replace it with stock GB kernel.. which has 3e recovery.
When I run ROM manager now with gingerbread the fascinate don't come up in the list no more.. there are 2 i9000's, one of those is a MTD... and 2 others. 4 in total.
I have the update.zip file which I downloaded from Rom Manager when I was on Froyo. Will that work? I'm afraid to try.
I've also seen methods of ADB pushing the recovery.bin over the current 3e. I just really not to sure which is the best way to do it, and I've done so much reading now it's got me confused.
Thx
Maniac
Click to expand...
Click to collapse
Second that - in the same boat.
As I understand it, it's a bootloader issue to install CM7 on Gingerbread. Downgrade to 2.2 and flash away!
Rabid_Gypsy said:
As I understand it, it's a bootloader issue to install CM7 on Gingerbread. Downgrade to 2.2 and flash away!
Click to expand...
Click to collapse
I don't want CM, I want to get clockwork recovery on my stock gingerbread.
I'm also in the same Boat. It would be nice to get clockwork recovery installed.
I have successfully rooted Gingerbread, part of the process is to flash the the Speedmod kernel first. With the Speedmod kernel, it has clockwork on it which you can boot into but unfortunately your phone cannot normally boot with that kernel.
I'm loving Gingerbread right now, it is so much smoother then 2.2, there is no way I want to go back to 2.2.
iwebsource said:
I'm also in the same Boat. It would be nice to get clockwork recovery installed.
I have successfully rooted Gingerbread, part of the process is to flash the the Speedmod kernel first. With the Speedmod kernel, it has clockwork on it which you can boot into but unfortunately your phone cannot normally boot with that kernel.
I'm loving Gingerbread right now, it is so much smoother then 2.2, there is no way I want to go back to 2.2.
Click to expand...
Click to collapse
Right there with you - so much better than 2.2 EVEN with lagfix running - was very thankful for ROOT but would love CWM recovery back - very useful tool.
I don't know if it was this thread I made the post, but something I did mention that I did was...
When I used the speedmod kernel to root the phone, I made a nandroid backup. Then I flashed the stock kernel back. I'm assuming if I wanted to restore my phone with the backup I could just flash the speedmod kernel back, restore by backup, then flash the stock kernel back again.
I don't know if clockwork is programmed to backup certain partitions, or if its dynamic, but I'm tempted to try my restore, but at the same time I don't want to go through all the updating agan.
Another thing, I have the 3 ODIN CWM file, the purple, blue, and no color ones you find on here. If you extract those you get a recovery.bin file, and there is no zimage (kernel). If you take one of those clockworkmods with no kernel and overwrite the stock recovery.bin in the phone, shouldn't that work?
I'm still new to android, first time I laid hands on one was this june, I'm still new, but I'm a fast learner too, but I want to figure this one out.
-Maniac
MrManiacNF said:
I don't know if it was this thread I made the post, but something I did mention that I did was...
When I used the speedmod kernel to root the phone, I made a nandroid backup. Then I flashed the stock kernel back. I'm assuming if I wanted to restore my phone with the backup I could just flash the speedmod kernel back, restore by backup, then flash the stock kernel back again.
I don't know if clockwork is programmed to backup certain partitions, or if its dynamic, but I'm tempted to try my restore, but at the same time I don't want to go through all the updating agan.
Another thing, I have the 3 ODIN CWM file, the purple, blue, and no color ones you find on here. If you extract those you get a recovery.bin file, and there is no zimage (kernel). If you take one of those clockworkmods with no kernel and overwrite the stock recovery.bin in the phone, shouldn't that work?
I'm still new to android, first time I laid hands on one was this june, I'm still new, but I'm a fast learner too, but I want to figure this one out.
-Maniac
Click to expand...
Click to collapse
Hey MrManiacNF,
Thanks for the idea, I guess it is a work around for now until we are able to get CWM installed on Gingerbread.
I ended up flashing the speedmod kernal back on, booted into CWM and made a full nandroid backup. Reflashed the stock gingerbread kernal back and booted up as normal.
Yea I do the same thing, I mean you can't make a backup without a pc to flash with, but a backup is better then none.
No love from ROM Manager
Saw ROM Manager had a few updates, but still seeing the limited device selection when trying to create a custom recovery, and still fails with the unsigned zip.
Just wanted to post that if anyone was wondering if recent updates corrected anything, as they have not (at least for me).
I can also confirm, actually no new phones added to the list. I've also tried an app call Root Toolbox Pro. It has options to backup your recovery or flash another. I tried flashing the fascinate-3.0.0.8.zip that I had from Rom Manager from Froyo. No luck, just hung at boot. Had to re-flash stock kernel in odin to fix.