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.
Related
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?
WHAT'S ALL THIS, THEN?
The fact that accessing the modem on this device has proven to be such a trainwreck has been the cause of much pretended weeping and gnashing of teeth amongst those of us who pretend to care about such things. Indeed, countless man-hours have been squandered by the larger community fiddling about with Odins and OTAs so as to obtain the ED01 or ED03 modems, for which there are, as yet, no Odinable versions generally available. For you, the sophisticated and discriminating SCH-I500VZW owner, there is a faster yet similar alternative - for what we were really after all along was the modem_delta.bin files ensconced within up to 100MB of Binged, unrooted, Verizon-approved OTA.
DISCLAIMER
These directions work for me. I would not have posted them if I had not been reasonably confident they will work for you. But I am tired of handholding. Computers (e.g. your phone - a computer that happens to make phone calls on the side) suck and break for no reason sometimes, but most problems are user error and failure to follow directions. I have added a section of general troubleshooting steps that will help you help yourself. If they don't work, the magic smoke is leaking from your phone, and the Wizards' Guild hates you for some reason. You knew the risks, so you will take responsibility.
You have been warned. Heretofore, if anything breaks, it is your fault.
DIRECTIONS
0. MAKE A NANDROID BACKUP and all manner of other backups - but then, you already knew that. You also knew how to use these backups. Right? Good. (Will probably only help in worst-case scenarios, which is a great reason to make one)
USE ODIN to flash the DL09 radio, which is the womb from whence all subsequent radios will emerge. The radio is included in the full DL09 Odin tar packages that are floating around, but it can also be flashed by itself. I have included a link to an Odin file that will flash only the radio below for your convenience.
USE CWM to flash the appropriate zip (BTW, they use Edify scripting) to copy the desired modem delta file (patch) to your phone. Make sure the zip's filename indicates that it is a match for your currently installed modem!
DO A FULL REBOOT immediately afterwards to have the phone patch the radio. Repeat steps 2 and 3 as necessary until you have your desired radio version.
NOTES & WARNINGS
WHEN USING ODIN, ALWAYS USE PDA PDA PDA ONLY USE PDA PDA PDA FOR THE LOVE OF GOD IGNORE PHONE AND CSC OR YOU WILL BE SORRY
It doesn't seem to matter whether you are using a Voodoo or stock kernel for the phone to patch the modem, but it won't actually do it until you reboot.
In an effort to foolproof the process I recommended flashing modems one patch at a time. Apparently more than one patch can be applied at a time so I have now added two new CWM packages that will get you from DL09 to ED01/ED03 in one step. The other zips remain for maximum flexibility. Enjoy y'all, but remember, if you choose to run a mismatched modem + ROM combo, you're on your own!
I don't know about CM6/CM7, but it looks like the newer ones that access the flash via mtd instead of BML are incompatible with these zips as of now. I'll see what I can do, but don't cross your fingers.
KEEP TRACK OF WHAT VERSION YOUR MODEM IS AFTER COMPLETING EACH STEP. FLASH THE RIGHT ZIP(s). FLASH EACH ZIP ONLY ONCE. There is no build.prop version string checking going on here.
DO A FULL REBOOT AFTER FLASHING A CWM ZIP. Using the advanced menu to reboot from recovery back into recovery or into download mode is NOT a full reboot.
The TW Froyo ROMs seem to be OK with booting when an Eclair modem is present. I haven't tested Eclair ROMs with Froyo modems. There may be problems with SMS/MMS or FC loops at the homescreen or God knows what else with mismatched modem + ROMs but the baseband should still have been updated.
GENERAL TROUBLESHOOTING
Check the MD5sums of the files you downloaded, and again with the files you put on the sdcard. If they don't match, redownload and retransfer until they do.
Verify that the baseband version changes to the version you expect after each flash.
Since only the modem is being modified, as long as you did not do something dumb like checking the wrong Odin checkboxes you can always Odin the DL09 modem and start over from the top.
If your CWM recovery is too old and does not support Edify scripting, get a newer one that does.
In extreme cases, Odin to the full stock DL09 ROM (this is where that nandroid comes in handy) before proceeding to steps 2 and 3, or...
Give up, use Odin to flash one of the still-fairly-topical EB01 or EC01 radios or whatever, and forget about it. There is no consensus as to whether the ED series radios are better (better for some and worse for others).
Think about what you're doing, and you will surely maximize your chances of cellular satisfaction!
FILES
Updated 6/9 with DL09 to ED04 and ED01 to ED04 packages. Thanks squash for grabbing it from the OTA before me
Updated 6/6 with one-step DL09 to ED01 and DL09 to ED03 packages.
Also updated 6/2 with new files that clean up the scripts a little. If you already have the old files, don't bother redownloading, you aren't missing anything important.
Odin-flashable DL09 modem: http://www.multiupload.com/6F3CF62RO7 (15.51 MB md5 f3682f58dfafc2d4d3ff74e2e2b3291a)
DL09 to EA28 CWM modem delta: http://www.multiupload.com/7JIP8HKASZ (159.45 KB md5 d2811be8f686ae5fe727eea66e8b3162)
DL09 to ED01 CWM modem delta: http://www.multiupload.com/WCVDI0GT1O (206.55 KB md5 3e99b93e998b3955b66d52ca2d5e99b5)
DL09 to ED03 CWM modem delta: http://www.multiupload.com/J7CRZWW7CM (206.55 KB md5 47786ff537b398e1a04652a0a91e5528)
DL09 to ED04 CWM modem delta: http://www.multiupload.com/P2X16H7XYV (211.52 KB md5 45b0fff31bd01c4681e8b269a0321b65)
EA28 to ED01 CWM modem delta: http://www.multiupload.com/CEB9DBV1PW (248.16 KB md5 a30fd9819640995e2dc664d4d0693ac7)
EA28 to ED03 CWM modem delta: http://www.multiupload.com/RY4ZS51RR5 (248.09 KB md5 02e89d60c130713c26948586dcc179ad)
ED01 to ED04 CWM modem delta: http://www.multiupload.com/FMS5Z3I8ZL (166.49 KB md5 a7ac9745b2adb09a271265d23107bc8f)
This came 24 hrs to late for me, but is awesome! Good job!
So if I'm on ComRom 1.3 with EC01 I can just go back to DL09 and work my way up to ED03 (Modem only) without having to completely go back to stock and rebuild everything else? If so....I love you.
spinnum said:
So if I'm on ComRom 1.3 with EC01 I can just go back to DL09 and work my way up to ED03 (Modem only) without having to completely go back to stock and rebuild everything else? If so....I love you.
Click to expand...
Click to collapse
Wondering the same thing. I have the EB01 stock touchwiz debloated and EC01 modem. Would like to go to ED03 without loosing my setup. Please advise. And I would love you too if it works, of course only as a friend...
jv
I'm doing that same thing right now. Looks like a winner.
With a running Comrom 1.3 setup, Odining just the DL09 radio and doing the steps to ED01 worked OK. Then I Odined back to DL09 and went to ED03, so at least for me, Comrom 1.3 worked with all 4 radios.
To be safe, I would recommend a nandroid of your current setup and be prepared to reinstall from scratch, but I didn't have to flash the full DL09 Odin and I don't expect that you guys will have to either. It's your risk, of course.
comradesven said:
With a running Comrom 1.3 setup, Odining just the DL09 radio and doing the steps to ED01 worked OK. Then I Odined back to DL09 and went to ED03, so at least for me, Comrom 1.3 worked with all 4 radios.
To be safe, I would recommend a nandroid of your current setup and be prepared to reinstall from scratch, but I didn't have to flash the full DL09 Odin and I don't expect that you guys will have to either. It's your risk, of course.
Click to expand...
Click to collapse
Successfully did the same while running CM 6.2. Thanks for this.
Thank you very much for this. This should be stickied or at a minimum added to the roms / kernels / modems sticky. Very helpful!
I just went to ED01 using your steps for now and I am seeing a huge improvement in D/L speed and time without signal. I may try ED03 but for now, ED01 seems just fine.
Using Evil Fascination v3.5.1 ROM
Edit:
I have noticed that after every reboot, my Time Without Signal would be at least 50% after either 5 minutes or 30 minutes after reboot. After toggling Airplane mode, this Time Without Signal would settle back down to the teens or better like it should be.
I have re-done the process putting my phone's modem at ED03. I will continue to test to see if toggling airplane mode after a reboot is still required to get the proper TWS.
I Odin'd to DL09 without a problem but when i try to flash to EA28 in CW (3.0.2.8xOTBv2) it gets stuck at "Copying files". Any ideas? Thanks!
topdogg_1 said:
I Odin'd to DL09 without a problem but when i try to flash to EA28 in CW (3.0.2.8xOTBv2) it gets stuck at "Copying files". Any ideas? Thanks!
Click to expand...
Click to collapse
I've think these are meant to be flashed in Odin, not cwm
Edit: Apparently, I'm wrong.
Sent from my SCH-I500 using XDA App
Wow this is helpful, i was about to go back
to stock to get the OTA.
renf said:
I've think these are meant to be flashed in Odin, not cwm
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Step 2 in the directions says to flash using CWM, no?
renf said:
I've think these are meant to be flashed in Odin, not cwm
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Incorrect. Only the initial revert to DL09 is via ODIN. From the OP:
2. Flash a zip using CWM to copy the appropriate modem delta file. (Uses Edify scripting)
If you're having trouble flashing the zips, corrupt download could always be a problem. I would try redownloading the zip and flashing again.
Yeah, confirmed working for me too. Went from DL09 to ED03 without any problems on CommRom 1.3.
iceman1183 said:
Incorrect. Only the initial revert to DL09 is via ODIN. From the OP:
2. Flash a zip using CWM to copy the appropriate modem delta file. (Uses Edify scripting)
If you're having trouble flashing the zips, corrupt download could always be a problem. I would try redownloading the zip and flashing again.
Click to expand...
Click to collapse
I re-downloaded and verified the MD5 check-sum and still hangs at "Copying files".
topdogg_1 said:
I re-downloaded and verified the MD5 check-sum and still hangs at "Copying files".
Click to expand...
Click to collapse
What CWM version are you using?
topdogg_1 said:
I Odin'd to DL09 without a problem but when i try to flash to EA28 in CW (3.0.2.8xOTBv2) it gets stuck at "Copying files". Any ideas? Thanks!
Click to expand...
Click to collapse
I have tested it with that version of CWM and it should work, although it did hang for a bit sometimes before it finally succeeded. I have no idea about exactly why it isn't working.
In order from small to big, things to try include verifying that the zips aren't corrupted, doing a full reboot and double-checking your baseband version before trying to continue, starting over by Odining the DL09 modem and going through the instructions again, flashing another CWM recovery, and doing a full format and reinstall.
Or you could just flash one of the more recent modems for which there exists a standalone Odin tar and forget about all this. Any concrete performance benefits to ED01 or ED03 vs. EC01 or whatever are still questionable at this point.
comradesven said:
I have tested it with that version of CWM and it should work, although it did hang for a bit sometimes before it finally succeeded. I have no idea about exactly why it isn't working.
In order from small to big, things to try include verifying that the zips aren't corrupted, doing a full reboot and double-checking your baseband version before trying to continue, starting over by Odining the DL09 modem and going through the instructions again, flashing another CWM recovery, and doing a full format and reinstall.
Or you could just flash one of the more recent modems for which there exists a standalone Odin tar and forget about all this. Any concrete performance benefits to ED01 or ED03 vs. EC01 or whatever are still questionable at this point.
Click to expand...
Click to collapse
Thanks for the help! I might try a full wipe, flash recovery and give it a go. If still doesn't work i'll just Odin back to EC01.
Well, everything worked great until I got to
the last ED03 update:script aborted error /sdc(status7) aborted...
..I followed the instructions and all.
Well....I think I might have done something really stupid. It should be obvious at the moment that I didn't understand completely what I was doing.
I just picked up my SGSII today from AT&T. In reading around I had hopes of a new ROM as I was very happy with CM on my captivate....unfortunately while in the process I followed instructions from an (obviously) european version of the phone and installed the KG6 modem....now I have no data connection.
I'm feeling really foolish...is there any way that I can get the stock modem for the AT&T U.S. Galaxy S2? Any help would be greatly appreciated.
Anybody? My phone is completely non-functional at the moment.
I've learned my lesson; I'll leave the modding to the more adept, I just need to get my phone back.
Try the stock plus root rom for odin/heimdall and that should over write the modem you flashed
Sent from my SAMSUNG-SGH-I777 using xda premium
FYI, you shouldn't expect rapid replies on a Monday morning.
The modem is currently missing from my "unbrick" packages, but this is an omission. I'll dump modem.bin tonight and post it up in my unbrick thread.
insaneturbo13 is not correct - as I said, my stock unbrick package is currently missing the modem.bin file. I will correct this tonight.
Entropy512 said:
FYI, you shouldn't expect rapid replies on a Monday morning.
The modem is currently missing from my "unbrick" packages, but this is an omission. I'll dump modem.bin tonight and post it up in my unbrick thread.
insaneturbo13 is not correct - as I said, my stock unbrick package is currently missing the modem.bin file. I will correct this tonight.
Click to expand...
Click to collapse
What would be the easiest way, If possible, to install european ROMS on the ATT version? Maybe, install the ROM without their kernel and modem and replace them AT&T's ?
Entropy512 said:
FYI, you shouldn't expect rapid replies on a Monday morning.
The modem is currently missing from my "unbrick" packages, but this is an omission. I'll dump modem.bin tonight and post it up in my unbrick thread.
insaneturbo13 is not correct - as I said, my stock unbrick package is currently missing the modem.bin file. I will correct this tonight.
Click to expand...
Click to collapse
Thank you! Thank you! Thank you!
Donation coming your way.
Thank you!
daraj said:
What would be the easiest way, If possible, to install european ROMS on the ATT version? Maybe, install the ROM without their kernel and modem and replace them AT&T's ?
Click to expand...
Click to collapse
I believe that alone should work - I haven't had time to test yet.
cgrums said:
Well....I think I might have done something really stupid. It should be obvious at the moment that I didn't understand completely what I was doing.
I just picked up my SGSII today from AT&T. In reading around I had hopes of a new ROM as I was very happy with CM on my captivate....unfortunately while in the process I followed instructions from an (obviously) european version of the phone and installed the KG6 modem....now I have no data connection.
I'm feeling really foolish...is there any way that I can get the stock modem for the AT&T U.S. Galaxy S2? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Feeling kinda foolish... I did the same thing yesterday AFTER I flashed the wrong kernel. (european kernel without proper button support) then everything went to hell, now I am back to the proper kernel, and the deoxed att firmware from the guide here on the forum... i just need the modem up and running with the right firmware and Ill have a working phone again
jdip1978 said:
Feeling kinda foolish... I did the same thing yesterday AFTER I flashed the wrong kernel. (european kernel without proper button support) then everything went to hell, now I am back to the proper kernel, and the deoxed att firmware from the guide here on the forum... i just need the modem up and running with the right firmware and Ill have a working phone again
Click to expand...
Click to collapse
I got all excited when my brother got his gs2 and I flashed a euro rom before I realized what I had done. I used entropy's stock package to get him fixed. Then he calls me from home and starts *****ing about how he can't use data unless he's on wireless. I put 2+2 together.
I am, like the others here, super eager to get that modem file when you post it. It would be a huge help. If it's not too much work on your part entropy, could you post a cwm version of the modem as well? I'd rather not have to flash him back to stock again just to fix the modem.
He's an iphone expat so I'm trying to make his android life smooth as possible.
I'm going to get home around 6 PM Eastern.
Initially I'm going to post up a Heimdall (and hopefully also Odin) flashable image of just the modem binary for those in a hurry, then I'll work on a CWM zip (need to find a reference one to pick apart in case it's different from the Infuse), then I'll upload a new more complete "unbrick".
Thanks for the donation cgrums.
OK, here's an emergency flash package for modem recovery - http://www.multiupload.com/JTFK1K1FOA
It's just a little too large to be an XDA attachment, sorry if multiupload is a problem for you.
It contains both a raw modem.bin, and a .tar file containing modem.bin (yes, redundant!)
It is NOT a CWM-flashable ZIP. Repeat, do NOT try to flash this ZIP in CWM. Seriously, it won't work!
The following method for flashing the modem IS tested:
Unzip the attached package
Use Heimdall to flash from the command line
Code:
heimdall flash --modem modem.bin
The following method for flashing the modem should work but is NOT tested:
Use Odin to flash the contained .tar file, using the Phone slot for the .tar
Man, before I even leave work! Awesome! Thanks again!
I made an error above - I believe in Odin, modem has to be in the Phone slot not PDA.
As I said in the post above - Heimdall is tested, Odin is not.
As to CWM - the maintainer of the I9100 modem collection frowns upon CWM for modem flashing - http://forum.xda-developers.com/showthread.php?t=1131950&page=2 . It sounds like CWM-flashing of modems might have issues on our device, I haven't had time to investigate but right now I'm going to trust pulser_g2's judgement for until I have more time to figure out GS2-isms of modem flashing. I've got a ton of stuff to do and I'm going to drop CWM-flashing of modems in priority for now since it should rarely be needed.
Entropy512 said:
I made an error above - I believe in Odin, modem has to be in the Phone slot not PDA.
As I said in the post above - Heimdall is tested, Odin is not.
As to CWM - the maintainer of the I9100 modem collection frowns upon CWM for modem flashing - http://forum.xda-developers.com/showthread.php?t=1131950&page=2 . It sounds like CWM-flashing of modems might have issues on our device, I haven't had time to investigate but right now I'm going to trust pulser_g2's judgement for until I have more time to figure out GS2-isms of modem flashing. I've got a ton of stuff to do and I'm going to drop CWM-flashing of modems in priority for now since it should rarely be needed.
Click to expand...
Click to collapse
I flashed the tar in odin using phone, the phone rebooted, but it will only make calls. The phone cannot use the internet when the wifi is off. Do you have any suggestions? I am going to try flashing your entire recovery image when you update it tonight.
What does your baseband version say now? If it flashed properly it should say UCKH7.
If it doesn't, it didn't flash for some reason. I know it flashes properly with heimdall, odin is kind of untested.
Entropy512 said:
What does your baseband version say now? If it flashed properly it should say UCKH7.
If it doesn't, it didn't flash for some reason. I know it flashes properly with heimdall, odin is kind of untested.
Click to expand...
Click to collapse
I had my brother do the factory reset, wiping the user data. That seemed to fix it (although we did flash your modem prior). Thanks so much!
I am happy to report that I am on my way back to functionality!
I've noticed a difference in connectivity though. At times, typically out-of-doors, I get decent signal strength and HSPA+ connection. Call service is a bit spottier than I remember it before the hijinks.
Inisde buildings is a completely different story...I can't seem to maintain a data connection of any type.
My baseband shows I777UCKH7 so I believe the flash went well. I'm planning to flash back to stock to get a good starting point going forward.
Anybody else experiencing similar issues? Thoughts?
This community is awesome!
I think someone did indicate that things were funky until they wiped - not sure though.
One click + CWM ICScrewed = in call audio problem
Hi I used your on click root kernel and then used CWM to flash the ICScrewed ROM .zip file.
Now I am having a problem where when I make or receive a call there is no audio. I still have data and wifi connectivity though it seems.
Could it be a problem with my modem? If so how do I flash another and where can I find the appropriate one?
Thanks, and sorry I cannot post on the ICScrewed page as I do not have permission to post in development yet.
jgordo32 said:
Hi I used your on click root kernel and then used CWM to flash the ICScrewed ROM .zip file.
Now I am having a problem where when I make or receive a call there is no audio. I still have data and wifi connectivity though it seems.
Could it be a problem with my modem? If so how do I flash another and where can I find the appropriate one?
Thanks, and sorry I cannot post on the ICScrewed page as I do not have permission to post in development yet.
Click to expand...
Click to collapse
I have no "one click" kernel. Any "one clicks" are repackaged by someone else and I have no idea what they contain in many cases.
i wanted to ask if i extract a rom can i use it threw odin to flash a rom
or does anyone have a list of odin flashable roms send it to me please
It would not be easy for someone who doesnt really know what they are doing to convert a flashable .zip into a pit/tar...
Well which type of rom are you looking for specifically? And why flashable through Odin?
Sent from my SGH-T959 (Samsung Vibrant)
Simply stock jvt 2.3.5 can you do it?
Sent from my GT-I9000 using XDA App
Sorry, but I wouldn't know how to go by doing it either. However, you may be able to get the developer to do it... Still I must ask, why through Odin?
Sent from my SGH-T959 (Samsung Vibrant)
Cus my phones dumb it always bootloops everytime I try to flash I do everything they say
Sent from my GT-I9000 using XDA App
whitehawx has a 2.2 odin flashable deodexed kb5 rom I use it as a stepping stone, not sure what your looking for, check dev. sec it wont loop, hawk writes good script
Why not?
I actually came to the Q&A section with a question along these same lines...is there a reason, other than developer preference, for NOT creating more ODIN flashable ROMs? I don't screw up flashing through recovery like the OP but I can say that I have never had to deal with one-off bugs, leftovers from previous ROMs that didn't get wiped (I'm lately a subscriber to the 'wipe three times' even after the paper is clean method), or ROM "settling," etc. I have a little more confidence in the process, I'm seldom so in need of a ROM flash that I am not near a computer...anyway, enough about me.
I am willing, if any developers want to take the time to teach me what is required to accomplish it, to start a project to convert as many of the flashable .zip ROMs as possible into tar files that can be flashed via ODIN.
There. Volunteered meself.
bord1er said:
i wanted to ask if i extract a rom can i use it threw odin to flash a rom
or does anyone have a list of odin flashable roms send it to me please
Click to expand...
Click to collapse
Good luck my friend tried doing this once and ended up bricking his device.
I warned him that it was for experienced people but he didn't listen to me haha
probably the definition of a newb
It's atually pretty easy to do if someone wants to take the time.
Here's the way to do it.
http://forum.xda-developers.com/showthread.php?t=960946&highlight=create+Odin+tar
Once I have my phone configured the way I like it I usually make one as a backup.
edit: the listed partition are for Samsung based roms not CM7or Miui.
heysoos said:
I actually came to the Q&A section with a question along these same lines...is there a reason, other than developer preference, for NOT creating more ODIN flashable ROMs? I don't screw up flashing through recovery like the OP but I can say that I have never had to deal with one-off bugs, leftovers from previous ROMs that didn't get wiped (I'm lately a subscriber to the 'wipe three times' even after the paper is clean method), or ROM "settling," etc. I have a little more confidence in the process, I'm seldom so in need of a ROM flash that I am not near a computer...anyway, enough about me.
I am willing, if any developers want to take the time to teach me what is required to accomplish it, to start a project to convert as many of the flashable .zip ROMs as possible into tar files that can be flashed via ODIN.
There. Volunteered meself.
Click to expand...
Click to collapse
I usually wipe 2 or 3 times as well.. just because I do it at work. I'm an electronics tech, and anytime we clear flash chips we do it 3 times to make sure the old stuff is gone. Stuff does stay in there!! Not sure if it applies to the chips in our devices, but it doesn't hurt to make sure you are clean.. that way you know you won't get skidmarks.
I also wish there were more odin roms.. I guess it is just too much extra trouble when these roms get updated so often.
Hi am obviously new to these forums but not new to Android/Samsung development so I had custom roms installed on my I777 so I needed to revert back to stock in which I flashed a leak which apparently changed the pit so I was able to download all the stock files for Odin3 for my device in the Download Repository. My question is there any reason why my device just doesn't act as accurately as I though I remembered it being when it was stock. Is there any ultimately right process for flashing because most instructions including my own are all different, some say wipe cache and data first and battery pull then download mode Creepys says its not neccessary until after the flash as does ZedoMax. I've followed all of them and haven't understood why there is no ultimately right process if there is one at all using odin3 and one-click. And if this is the case what could possibly be going on with the force closes and hangups I'm getting? If someone is willing to take the time to help me with all these questions I'd greatly appreciate it.
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
clay101eve said:
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
Click to expand...
Click to collapse
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
GalaxyHackster85 said:
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
Click to expand...
Click to collapse
I don't remember for sure, but I don't think fix permissions in available in stock 3e recovery. It should be available in just about any custom recovery.
GalaxyS2Root, and it's owner who goes by the screen name zedomax, is a strictly commercial endeavour, designed to make money but not necessarily designed to help people. I think zedomax is a developer, but I'm not sure how good he is. Many of the offerings on that web site, and presumably on his dozens of other web sites for other phones, cause problems for folks, bricking phones, and other things. Further, he takes the work of developers here and posts their work on his sites without giving any attribution or remuneration. He's spread way too thin keeping up with all his various sites, and/or he just doesn't seem to care if his offerings cause problems. We've had so many people come to this forum with various problems due to GalaxyS2Root that when the name is mentioned, everyone is on it right away.
I would only use the pit to repartition on the I777 when everything else fails. It can be a help, but you should be sure that you are going to have a successful flash before you use it, since it repartitions the memory space of the phone.
Most firmware for the I777 has everything in one .tar file, which you put into the PDA slot. If you are flashing just a param.lfs or just a sbl.bin, then that goes into the PDA slot. You can also flash a modem at the same time as the rest of the firmware, using the Modem slot, but most firmware packages have the modem in them too.
So essentially the oneclicks are absolutely the only thing I need in order to ensure a 100% successful restocking? And if so am I always suppose to factory wipe/cache then battery pull (3e recovery doesn't have a power off option)? The reason why I ask so many questions is A. A lot of peoples data isn't accurate as you've stated and its better for me to have as much data as possible when potentially getting into these things. And B. I've been flashing my S2 like a madman with OCD because as soon as I'd get a force close or any sort of hiccup happened I assumed it was because I flashed it wrong when in fact I was just following some of the directions that I've aqquired from here or GS2Root and so far everything has flashed with the same results but as its been forever since my phone was purchased so I can recall if these are just the normal hiccups that come with the inconsistancy of android. So to me I'm just trying to.make sure that I'm doing things absolutely correct.
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
creepyncrawly said:
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
Click to expand...
Click to collapse
And you are absolutely correct and I have your guide bookmarked but with so many people having different takes on how to return to stock can you point me in a direction that's the completely right way of flashing your pit and attempt software. Or is your guide with one click the most surefire way to do it? Like I said before I'm a bit OCD when it comes to my phone so whenever I get a little hiccup I can't tell if those are just normal for I777 software or is it something I've done wrong which I probably haven't but it still worries me.
If you havn't done something absolutely ignorant, i.e. flash firmware for a different phone, then you should just use my guide with the linked one-click downloader. That package does not contain bootloaders or param.lfs. Those (the bootloaders and param) will always be good, and not needing replaced, if you only flash firmware from these forums and never flash leaked firmware (which usually contains bootloaders.) There should never, ever be a reason to use a pit file. As I said before, the phone has to be pretty seriously screwed before you need to repartition, and then it should be the absolutely last thing you try.
And inform yourself before you do any actual flashing. You should know exactly what you are doing to your phone, and also know what the remedy is before you do it. That way, you can avoid doing something stupid. If you really want to learn about your phone, read at least a little bit from the forums here every day for a few months, get involved in the discussions, and before you know it, you'll be one of the helpers.
Thank you so much for all of your prompt replies, I have been using the data from this site for quite some years now but never ran into any issues which required me to create an account (although I have wanted to), but for s**ts and giggles let me just say that due to the few hiccups I encountered and not knowing what would have caused them I have already flashed the pit and repartitioned as well as flashed the oneclick w/ bootloaders and param. Now asside from the few force closes that I ran into and the one time I bricked it and brought it back to fully functional is there any harm to the flashing of those tools that I've already done so far. Is there any negative side effects of what I've done that I may not be seeing or is it a case of well "there in the repository so theyre safe as long as I've flashed them correctly". And if so are these few force closes just everyday hiccups that every version of Android experiences and that I'm just overthinking it and it's just been a case of my ocd kicking me in the ass?
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
colorsharpkid said:
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Honestly, I have no idea what you just said, or what you're asking.
qwertyaas said:
Honestly, I have no idea what you just said, or what you're asking.
Click to expand...
Click to collapse
Me either, sometimes punctuation goes a long way
Sent from team Pirate! Using Tapatalk 2
colorsharpkid said:
i flashed zedo then used s2 unlock. then i flashed aokp and siyah kernel. I forgot to do triangle away (because I used zedo) and then tried an ota update. This messed up my rom because I couldn't access cwm. then i flashed zedo again to get cwm back. After that i flashed aokp again and ran triangle away.
I then did a return to stock backup after root and an odin flash for stock non root. While on stock i did an ota update to 2.3.6. (some nonsense about 2.3.7 and Google wallet)
.....on reboot it hangs so i did 3e recovery wipe and wiped cache. Reboot has been good since. My batt has been outragously long on uckk7!! But, after an ota update it shows as uckk6 i used a non rooted file, maybe I should have used a rooted return to stock file?
Anyway, the file i used was I777UCKH7-CL503881-No-BL as stated and i just used pda slot .....idk, after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and flash custom ROMs all over again. i honestly just miss the torch feature and the easy brightness slider on the pulldown.
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone. im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Fixed... I think. And "zedo" refers to the sh;t zedomax has on gs2root.
Clay
Team Pirate
Sent from my Buttery Pink SGH-i777
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Sorry for double post but I wanted to make sure my questions are targeting creepy seeing as this thread is getting a bit off topic.
GalaxyHackster85 said:
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again.
Click to expand...
Click to collapse
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I also had on flash that was the 2.3.5 leak but flashed over that and it was fine.
Click to expand...
Click to collapse
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Click to expand...
Click to collapse
I don't know how to look behind the scenes... but I would think your phone is fine.
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
OK great info and definitely a relief but just out.of curiousity what are the repercussions of a bad bootloader flash or an improper pit flash? And how would we know that whatever pit or bootloaders flashed weren't for our phone or are corrupted data?
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
And trust me I absolutely appreciate all the responses the answer to my last question is all I needed to know to truly understand how the i777 works and functions and I commend you for that. I felt that trying to find all these answers would have been trying to find a needle in a haystack.
Also regarding the repartioning I just wanted to make sure that everything is correct in terms of space. My device is showing only 1.89gb of "Device Memory" at the bout of the "Storage" screen is this normal I though it was higher before but I cant quite remember.