Ok, a couple of people have varients of this, but most of them are pretty similar. This is my method which is based on the post by SINN which I and many others have used to get their's working. I will try to consolidate the know methods that people have used to the top post. Okay, Let's go do this...
My Method
Method 1 (Do First):
1) Start from a DI18 ROM/Modem with WORKING GPS
2) ODIN in DK28 Modem - I (and others) have had better success with version 1.3 and 1.61. GIYF them.
3) Restart and verify GPS lock in DI18 ROM + DK28 Modem - It could take a minute or two
3a) If this step fails go to method 2
4) Flash a DK28 ROM, verify GPS lock
Method 2 (Long Way Home):
1) Start with stock DI18 + working GPS
2) ODIN in modem
3) Restart and verify GPS functionality with DI18 ROM + DK28 GPS
2) ODIN in DK28 full
3) Restart and reverify gps lock
3a) If this step fails, take a nap, and return to step 1)
4) Reroot and flash in new DK28 based ROM
5) Reverify GPS lock
Originally Posted by styles420
Instead of writing method 2, you could have just said (in method 1)
3a) If this fails, repeat steps 1 - 3, then pretend step 3 did not fail and continue as normal (If it fails again, you are sleep deprived)
It is exactly the same as the method SINN posted, with added (and ridiculous) redundancy (take a nap? really?)
And I'd still like to know how doing anything at all before an Odin flash will make a difference... Anyone?
Click to expand...
Click to collapse
[Regarding the comment on the description] I could have, but you can start with method 2 by itself. It just takes longer. IMO trying method 1 first is worth it if it works. The sleeping comment was and is a joke, sometimes people use them in conversations or in prose to keep things light.
Regarding ODIN flashing, it doesn't just magically wipe your phone. The primary bootloader on your phone calls a secondary bootloader (usually loaded and run out of RAM in my experience (I make flash bootloaders BTW.)) The sbl.bin (secondary bootloader) file for DK28 is different than the DI18 one already on your phone. Also, the PIT file contains partitioning information and is only used when flashing the modem. Potentially (however unlikely since some people can use method 1) this could be causing an issue for some since I don't know what *.pit file they are using. Also, since this bootloader is working on a filesystem and partitioned flash arrays, this really complicates things if say partitions are changing sizes, moving, etc. So to answer your question the method's are different and not redundant.
SINNN's Method
Whats funny is dk17 with its modem worked flawless for me. Then odin dk28 and all over broken gps. Out the box Sprint Epic has Zero problems.And comfirmed by almost all tech sites.The rest of the galaxy s lineups have serious connecting problems. So if you have a Epic and were never ever were able to get 1 single lock with stock, u have a bad gps chip. Now for everyone who flashed the leaked betas and lost gps sattelite locks, there is a fix and it sticks compared to the early dk05 leak.
In a nut shell, after odin broke my gps with dk28, I did these exact steps. They are rather simpler and almost guaranteed to work.
1: Flash Stock.zip with CWM.
2: Boot up.
3: Swipe down top task clock bar thingy.
4: Touch GPS (turns green)
5: Open google maps. Hit My Location button on top left. Wait a few seconds and it WILL lock.
6: Odin DK28. Done. Gps works.
In a even more smaller nutshell for more advanced users.
1: Flash Stock.zip thru CWM.
2: Boot and gps lock thru google maps.
3: Odin DK28. Gps works again.
Click to expand...
Click to collapse
Omair2005's Method
omair2005 said:
maxhax200..try this method.
This method worked for me and it seems to be the easiest..
1) Download DI18 and DK28 for here: http://forum.xda-developers.com/showthread.php?t=794138
2) Once Downloaded, remove .md5 extention (if you have it, I used a download manager and it was there). So now you only have .tar for both files.
3) Put your phone in Download mode (hold 1 on keyboard and press power) ODIN to DI18. Uncheck everything but autoreboot. Place the .tar file in the PDA.
4) Boot up, get a gps lock. Best way is to google navigate to somewhere and leave it in the background.
5) Once you get a gps lock, power off and put back in download mode.
6) ODIN to DK28. Boot up and you should get a GPS lock.
7) Root using the new method found here: http://forum.xda-developers.com/showthread.php?t=770388
8) Flash custom rom!
**Remember you must run ODIN first on the computer then plug phone in USB while in download mode.**
ODIN link: http://www.sdx-downloads.com/devs/noobnl/Odin3+v1.61andepic.pit.zip
Click to expand...
Click to collapse
plapczyn said:
I really highly doubt that Samsung/Sprint would release an update that breaks GPS entirely on so many devices. If we can get some other devs to verify, I think we can close this issue out for good.
Click to expand...
Click to collapse
Sprint hasn't released this update, in fact they specifically say not to use it:
http://community.sprint.com/baw/thread/52685
(of course, I still installed it and I'm happy to say I have no GPS issues).
Plus, Samsung has been working on GPS fixes for the Galaxy S phones for a while, they have even released supposed fixes for some, just not the Epic.
I flashed only the modem for both dk17 and dk28 when it was available and have had zero GPS issues since dk17. I've never flashed a full tar on the my current Epic. GPS has been absolutely perfect.
mattallica76 said:
I flashed only the modem for both dk17 and dk28 when it was available and have had zero GPS issues since dk17. I've never flashed a full tar on the my current Epic. GPS has been absolutely perfect.
Click to expand...
Click to collapse
I was running Epic experience rom (DI18) and GPS worked fine.
I ODIN'ed the full Pre Rooted TAR.. GPS did not work
I went back to DI18 and GPS worked.
I used the Update.zip from google servers to update.. GPS broke
I went back to DI18- GPS worked
While running 2.1 I flashed the modem only DK28 and got a GPS lock
Then I used the upgrade.zip to 2.2 thru normal recovery-- GPS worked
Then I re rooted.
Thats the only way I got my GPS to work.
Install fresh 2.1 thru ODIN--- Get a GPS lock
Install modem only DK28-- Boot and Get a GPS lock
Install Froyo via update.zip ---GPS still locks
I've tried everything described all over this forum, but to no avail. I rarely ever use GPS, but it would be nice to actually have it working in case I need it lol. In my completely non-professional opinion, I think it either has to do with the DK28 modem itself or with the method we are using to flash it. Hopefully someone over in South Korea is looking into this, because it seems like half of the users on this site have problems with the Epic's GPS.
Sent from my Xtremely Syndicated and Emotionless Epic 4G
thomasskull666 said:
I've tried everything described all over this forum, but to no avail. I rarely ever use GPS, but it would be nice to actually have it working in case I need it lol. In my completely non-professional opinion, I think it either has to do with the DK28 modem itself or with the method we are using to flash it. Hopefully someone over in South Korea is looking into this, because it seems like half of the users on this site have problems with the Epic's GPS.
Sent from my Xtremely Syndicated and Emotionless Epic 4G
Click to expand...
Click to collapse
It's possible your issue could be hardware. I know my first Moment came out of the box with a bad GPS chip. Wouldn't get any GPS signal at all. I took it back and swapped it out for another one that never had any GPS issues.
edonnelly said:
Sprint hasn't released this update, in fact they specifically say not to use it:
http://community.sprint.com/baw/thread/52685
(of course, I still installed it and I'm happy to say I have no GPS issues).
Plus, Samsung has been working on GPS fixes for the Galaxy S phones for a while, they have even released supposed fixes for some, just not the Epic.
Click to expand...
Click to collapse
Below is a statement from the Epic Product Manager regarding the leaked release (DK28):
Sprint is working on a software package for the Samsung Epic4G that will upgrade it to the Froyo version of Android. Over the weekend, some users were able to access and download a test build (DK28) for the Samsung Epic from some 3rd party developer sites. Unfortunately, this is not approved software for Sprint production devices and we strongly recommend that users refrain from loading it.
Click to expand...
Click to collapse
...standard PR stuff. Hey we aren't responsible for breaking your phone with this. Do you think they would be like...hey we are slowly rolling out the release, if you are in a hurry go dl it from xda. lmao.
Secondly, I wouldn't believe everything you read on forums. The GPS issues before had to do with bad cache information, not simply not working at all. The point of the post is to try to come to a consensus about how to fix the issue of no GPS after reflashing so that the solution isn't buried in all of the different ROM threads.
mattallica76 said:
It's possible your issue could be hardware. I know my first Moment came out of the box with a bad GPS chip. Wouldn't get any GPS signal at all. I took it back and swapped it out for another one that never had any GPS issues.
Click to expand...
Click to collapse
The fact that it works for DI18 but not on DK28 is unlikely hardware my friend. If it never worked, that is an entirely different issue.
mattallica76 said:
It's possible your issue could be hardware. I know my first Moment came out of the box with a bad GPS chip. Wouldn't get any GPS signal at all. I took it back and swapped it out for another one that never had any GPS issues.
Click to expand...
Click to collapse
That is very well possible, and most likely the root of my issue. My GPS has never worked properly, even on stock DG27 and DI07. A friend of mine also has a Moment, and had the exact same problem and got his replaced as well. I love my Epic though, I mean this specific phone because my cpu plays well with overclocking Oh well just gonna have to tough it out, and keep using my TomTom lol.
Sent from my Xtremely Syndicated and Emotionless Epic 4G
plapczyn said:
The fact that it works for DI18 but not on DK28 is unlikely hardware my friend. If it never worked, that is an entirely different issue.
Click to expand...
Click to collapse
I was talking about thomasskulls problem. His never worked on any build.
I had issues with the GPS cache getting gunked up every other day when I was running di18, but as I stated earlier, GPS has been flawless with dk17 and dk28 modems.
I'll post the steps I took that broke my gps if it helps anyone.
I flashed back to di18 stock from acs syndicate/phoenix kernel zip through clockwork.
Flashed dk28 modem using the clockwork flashable zip
Flashed nebula rom with clockwork.
= broken gps
To fix I followed sinns steps:
Back to di18 stock and modem
Flashed dk28 modem
Booted into stock 2.1 and gps locked in google maps
Flashed nebula
=working gps
imdjenk said:
I'll post the steps I took that broke my gps if it helps anyone.
I flashed back to di18 stock from acs syndicate/phoenix kernel zip through clockwork.
Flashed dk28 modem using the clockwork flashable zip
Flashed nebula rom with clockwork.
= broken gps
To fix I followed sinns steps:
Back to di18 stock and modem
Flashed dk28 modem
Booted into stock 2.1 and gps locked in google maps
Flashed nebula
=working gps
Click to expand...
Click to collapse
LOL I thought I was replying to a different thread. Either that or thread title was changed.
Whats funny is dk17 with its modem worked flawless for me. Then odin dk28 and all over broken gps. Out the box Sprint Epic has Zero problems.And comfirmed by almost all tech sites.The rest of the galaxy s lineups have serious connecting problems. So if you have a Epic and were never ever were able to get 1 single lock with stock, u have a bad gps chip. Now for everyone who flashed the leaked betas and lost gps sattelite locks, there is a fix and it sticks compared to the early dk05 leak.
In a nut shell, after odin broke my gps with dk28, I did these exact steps. They are rather simpler and almost guaranteed to work.
1: Flash Stock.zip with CWM.
2: Boot up.
3: Swipe down top task clock bar thingy.
4: Touch GPS (turns green)
5: Open google maps. Hit My Location button on top left. Wait a few seconds and it WILL lock.
6: Odin DK28. Done. Gps works.
In a even more smaller nutshell for more advanced users.
1: Flash Stock.zip thru CWM.
2: Boot and gps lock thru google maps.
3: Odin DK28. Gps works again.
Hope it helps.
Sent from my SPH-D700 using Tapatalk
SINNN said:
Whats funny is dk17 with its modem worked flawless for me. Then odin dk28 and all over broken gps. Out the box Sprint Epic has Zero problems.And comfirmed by almost all tech sites.The rest of the galaxy s lineups have serious connecting problems. So if you have a Epic and were never ever were able to get 1 single lock with stock, u have a bad gps chip. Now for everyone who flashed the leaked betas and lost gps sattelite locks, there is a fix and it sticks compared to the early dk05 leak.
In a nut shell, after odin broke my gps with dk28, I did these exact steps. They are rather simpler and almost guaranteed to work.
1: Flash Stock.zip with CWM.
2: Boot up.
3: Swipe down top task clock bar thingy.
4: Touch GPS (turns green)
5: Open google maps. Hit My Location button on top left. Wait a few seconds and it WILL lock.
6: Odin DK28. Done. Gps works.
In a even more smaller nutshell for more advanced users.
1: Flash Stock.zip thru CWM.
2: Boot and gps lock thru google maps.
3: Odin DK28. Gps works again.
Hope it helps.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Odin flashing overwrites everything in the phone except the sd card... how would anything you flash before the Odin flash be able to have any effect on anything after the Odin? Is it possible you mixed those up? (Odin to stock, update.zip to DK28)
Followed to the letter, but GPS still doesn't lock on after 24-48 hours. Only way to make it latch onto the satellites is by powering off and r&r the battery. Using GPS Tracker so I know exactly what is going on with the GPS. This IMHO is being caused by the GPS cache problem.
plapczyn said:
This is based on the post by SINN, as well as the method I, and many others have used to get mine working. Okay, Let's go do this...
Method 1 (Do First):
1) Start from a DI18 ROM/Modem with WORKING GPS
2) ODIN in DK28 Modem
3) Restart and verify GPS lock in DI18 ROM + DK28 Modem - It could take a minute or two
3a) If this step fails go to method 2
4) Flash a DK28 ROM, verify GPS lock
Method 2 (Long Way Home):
1) Start with stock DI18 + working GPS
2) ODIN in modem
3) Restart and verify GPS functionality with DI18 ROM + DK28 GPS
2) ODIN in DK28 full
3) Restart and reverify gps lock
3a) If this step fails, take a nap, and return to step 1)
4) Reroot and flash in new DK28 based ROM
5) Reverify GPS lock
Click to expand...
Click to collapse
Instead of writing method 2, you could have just said (in method 1)
3a) If this fails, repeat steps 1 - 3, then pretend step 3 did not fail and continue as normal (If it fails again, you are sleep deprived)
It is exactly the same as the method SINN posted, with added (and ridiculous) redundancy (take a nap? really?)
And I'd still like to know how doing anything at all before an Odin flash will make a difference... Anyone?
There are several methods to restoring the gps...i did so without odin.
But regardless of what method you use, clear your cache and data.
I was literally logging in to write this up. The same steps, while annoying, worked great for me last night. I could not get a fix yesterday, last night after all this I was getting quick and accurate fixes.
Sent from my SPH-D700 using XDA App
I'd suggest getting "GPS Status" from the marketplace. Once you install that, hit menu, then tools, then "Manage A-GPS State". I'm betting you can fix it without a reload. Worked on mine!
sleebus.jones said:
I'd suggest getting "GPS Status" from the marketplace. Once you install that, hit menu, then tools, then "Manage A-GPS State". I'm betting you can fix it without a reload. Worked on mine!
Click to expand...
Click to collapse
Worked for me too.
Related
Background. Was using 2.2 for the longest time, loved Firefly. Went ahead and bit the bullet and decided to go to 2.3 and use Gingerbread. Solid week of great success. However I started notcing my antenna saying no signal. Several Reboots and still nothing worked. Decided I would One-Click Back to 2.1 and start fresh. Well I never had issues with Odin 1 Click before, but now I get in a boot loop (ATT SPlash Screen) I have noticed when its unloading the package after , the last thing i see is CSC and that it boots into the loop. Would love to get my phone back to stock so i can see if its a hardware or software issue with my antenna. I have looked at this link, http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 but was afraid I possibly might still have GB bootloaders on my phone. I would think not if Odin finished, but I just want to double check with the community so I dont brick.
Thanks guys.
Can you get into DL mode? IF so, i would try and Odin again. ALthough I looked at the link in your OP, unless your heart is set on 2.1JH7, i would use the Odin3 one click downloader. That will restore your phone to 2.1JF6 as well as flash the correct bootloaders. I have gone back and forth from continuum to cm7 a few times now using that method.
Thanks for the quick reply. however this is the 3rd time trying Odin-1 Click tonight and I still end up in a boot loop. I have redownloaded the file just to make sure I didnt have a corrupt one. I just want a stock system and see if the constant antenna issues continue. (Trust me Ive tried different modems and all those possibilities.) Is it safe with that link? I noticed when i do Odin they flash a sbin and bootloader. I am assuming that puts it back on 2.1
which Odin are you using? Are you using the one click program that gives you stock firmware... JF6 firmware?
It is here:
http://www.megaupload.com/?d=SBSMALFJ
Yup thats what I have. It looks like it doesn't load the android system. Soon as it says installing Multi-CSC its done and rebooting. It would seem like its not unpacking the files. I have no status bar at the bottom. I have no idea why its doing this. Here is the crazy part. If i go back to the ginberbread stock, its not a problem to get to boot.
while I'm no expert.. seems like a bootloader thing. Try downloading it again from the link i put up and see if it was maybe a corrupted download.
The bootloaders are the first thing flashed in odin. It stopped after that then you have stock bootloaders. Also if all you see is the white AT&T screen and then it reboots, that indicates stock bootloaders as well. The gb bootloaders have a black galaxy s I9000 screen as the param.lfs image.
I would bet money you have stock bootloaders, use that link you posted that work be perfect. If you go back to gingerbread and want to return to stock bootloaders you'll have to use one click again even though you got a problem from it this time, if you get the same problem you know this worked to fix it.
And lastly usually problems with cell signal are modem related ... Which one were you using, did you even try another one? That would've been my first move instead of going all the way back to stock.
Hey studacris,
I have been using Mosaic (Love the work you guys do over there). I did try and use the other method to get back to Stock Last night and it did the same thing. Just a bootloop. If its plugged into the USB cable it goes directly to the Battery Symbol, if its not the Att 3G bars loop. I can flash to Gingerbread stock and then apply Other Roms. I tried GR-2 and Mosaic again, but still nothing with the signals. I just dont like the fact I cant get back to Stock with those 2 different methods. What I think is odd is when I load Gingerbread, it seems like items are being unpacked and loaded. When i try to go to Stock, everything happens super quick, making me believe nothing ever gets installed on the Internal Card during the unpacking sequence. I am no pro, but thats just something i noticed. Here was my original post on the Mosaic board. http://forum.xda-developers.com/showthread.php?p=14043766&highlight=Rizz67#post14043766
UPDATE: This ROM is now outdated. Please use Dfgas's newer MIUI port, located here:
http://forum.xda-developers.com/showthread.php?t=1152518
Original Post:
You've watched. You've waited. You've sat impatiently looking for an update. I know I have. The wait is over.
Gingerbread AOSP MIUI 1.6.24 MTD Port
Ported to: Mesmerize (still having issues with Showcase port)
Please note: The 1.6.24 links currently posted are not my work! I just couldn't correct the eri.xml in framework-res.apk to remove "Verizon Wireless" from the top bar (cosmetic I know, but it bugged me--I'm picky like that), and... BDE sorta had his port done several hours before mine anyway. I can't take any credit whatsoever for these links, this is all his porting work.
WARNING: READ BEFORE FLASHING!!
This ROM was designed using the newer (for us) yaffs2/ext4 filesystem. Excepting CM7MTD, no other ROM uses this filesystem. As a result, this ROM uses CWM 4, and once you flash, you CANNOT flash any other ROM from Recovery. Should you have issues with the flash, or want to return to a different non-MTD ROM, you will need to Odin all the way back to stock. See post #2 for instructions.
SHOWCASE USERS: This is especially critical for Showcase users, as Cell South has prevented Odin flashing packages for the Showcase. IF YOU USE A CELLSOUTH SHOWCASE AND WANT TO FLASH BACK TO A DIFFERENT ROM, FIND A WORKING ODIN PACKAGE FIRST.
As always, the standard warning applies: I am not responsible for what may happen to your phone as a result of flashing this ROM, properly or improperly. No warranty whatsoever. You have been warned.
Credits
The biggest thanks go out to jt1134. NONE of this (including CM7MTD) would be possible if it weren't for the work he's done for the Fascinate, Mesmerize, and Showcase.
Andmer has also been critical to making this happen. He was the one to take JT's work, use his AOSP source, and build a working MIUI port for the Fascinate. Both he and JT continue to modify the ROMs and Kernels for MTD that we enjoy to work towards getting that hardware working.
Without these guys, there would be no port for us.
I'd like to thank lmartin92 for his tremendous help and knowledge. He worked tirelessly with me to get this working. Similarly, bdemartino has been a huge help in all around, as well specifically making sure we could get the "fascinatemtd" SMS padding code implemented into CM7MTD, and therefore MIUI MTD. Lastly, I'd like to thank Akellar for getting some Framework-res cosmetic edits working when I could not.
1.6.24 Note: Again, these are actually BDE's ports, not mine, I can't take any credit.
ROM Details
Update Schedule: MIUI receives weekly official updates, and Andmer has said he intends to port them to the Fascinate on that same schedule. I intend to port from his work on that same schedule, and once my overlay is fully worked out, it should take me only as long as it takes to apply it and upload. This thread will be updated every time a new ROM is released. I'll try to keep one or two previous week's ROM links just in case.
Radio: This ROM does not flash a radio, so it should use whatever radio you had before you flashed. This ROM is built for a Mesmerize/Showcase radio (making it an actual Mesmerize port), so if you're using the Fascinate EC01 radio, you'll want to either flash the EC10 or EE19 radios (typically by flashing the stock versions of those ROMs). Don't worry if you flash those ROMs; everything else (except the radio) will get overwritten.
Recovery: In order to support the yaffs2/ext4 filesystem, this ROM uses CWM 4. As a result, the normal "three finger Recovery" method does not work. Similarly, although the ROM includes a "Reboot into Recovery" menu option after holding power, that does not boot into recovery. The only method of getting into recovery at this point is to either use ADB or a Terminal Emulator app.
Within Terminal Emulator, type the bolded, underlined text:
su (enter; this grants SuperUser rights to Terminal Emulator)
reboot recovery (enter)
This should properly reboot the phone into Recovery mode.
Working:
Calls
Bluetooth!!
3G / Data
WiFi
SMS
Camera/Camcorder!!
USB mass storage / sdcard
GPS
ALL Sensors!!
Not Working/Known Issues:
MMS
Calls/SMS during deep sleep mode are not waking up the device to ring.
This app will prevent your device from deep sleep which is of course a battery drain, but you will receive calls. Whether its worth it or not is up to you.
https://market.android.com/details?id=otis8.softlocker
How to Flash
Copy the ROM to your SDcard.
Reboot phone into recovery, flash ROM as normal.
Make sure to wipe data, cache, and dalvik cache if you are coming from a non-MTD ROM, and possibly even CM7MTD.
Flash MIUI ROM from SD card.
The "MIUI" branded flash script will appear, and quickly disappear. THIS IS NORMAL. This verifies if CWM 4 is installed (on the first time through it will not be), and if not, installs it. The phone should reboot once again into recovery, but it will be standard CWM 4 Orange recovery.
Flash the ROM from your SD card once more. Note that the softkeys have changed; use the Search key as "Enter". The flash should proceed as normal.
1.6.24.1: Flash the 1.6.24.1 patch to correct all sensors.
Reboot phone when complete.
When your phone reboots, you should see the normal Samsung logo, and then a Galaxy S/CyanogenMod 7 logo. This will be followed by the MIUI.us boot screen, which is a moving starfield with a spinning globe.
Welcome to GB MIUI!
Mesmerize Download
http://olvisfoundation.com/xdadump/bdemartino/ROMS/MIUI/MIUI.us_mesmerize_1.6.24.1_Eng_Deo_ZipA_Signed_0627.zip
Showcase Download
((Still broken))
1.6.24.1 Patch Download - Fixes ALL sensors! (for both Mesmerize and Showcase, once later is released)
http://olvisfoundation.com/xdadump/bdemartino/ROMS/MIUI/MIUI.us_patch.zip
HOW TO GO BACK TO NON-MTD ROMS
Kanged from the Fascinate forums with immense thanks to kidserious, and referencing the "Files to get your Mesmerize back to stock 2.1 and 2.2.1" guide from Phidelt82
Things you'll need:
Odin
Working Odin package for your phone model
If you don't already have these, here are some links (sorry, Mesmerize stock ROM only):
Odin: http://download1422.mediafire.com/ii578172dylg/429fcpdtpckkcea/Odin3+v1.83.exe
EC10 Odin Package: http://www.megaupload.com/?d=N6JNT1ZE
Whatever Odin package you use must have a full bootloader included in the flash. EC10 should work, EE19 may not. I'm unable to advise which Showcase Odin package would work, I'm not familiar enough and they're not generally available.
STEP-BY-STEP
I'm writing these for the Odin newbie in mind. Experts, as long as you check "Repartition", you know the drill.
Open Odin. This does not need to be installed, simply run.
Pull off the back from your phone, remove the battery.
Connect the USB cable (best with the Samsung one that came with your phone), and hold Volume Down until you see the phone say "Download Mode". A little box should turn Yellow in Odin, signifying it detects the phone and is ready to flash it.
Click the PIT button. Locate the path to the PIT file extracted from the ZIP you downloaded above (or previously) to populate that field.
Click on the PDA button. Locate the path to the TAR.MD5 file extracted from the ZIP you downloaded above (of previously) to populate that field. Do NOT click on PHONE, Phone should be empty.
Make sure Re-Partition is checked. We want to overwrite the previous MIUI flash, and Re-Partition is what lets us do that fully.
Click the Start button. Let it proceed through the whole flashing process, which is approximately 10 minutes. You'll see "Complete!" in Odin and your phone's screen will go blank once it's finished.
For thoroughness' sake, I'm including the below steps. Again, experts could potentially circumvent, but below is the failsafe way.
Re-insert battery, boot phone. Allow it to boot into Blue (stock) recovery. it's okay if it says it can't mount "HIDDENSDCARD"; it's done the rest of the setup it needs to. If you're just staying with the stock ROM and recovery, you're done.
If you want a custom recovery:
Follow steps 1-7 above, skipping over step 4 (no PIT file needed), and flash your recovery of choice. You should now be able to flash whichever custom ROM you were on before, or restore from a Nandroid backup.
It is absolutely mandatory that you follow these steps exactly to properly get off of GB MIUI MTD (or CM7MTD for that matter) so that you can flash another ROM. Attempting another method or not following these steps implicitly will result in a bricked phone and you will have to follow this guide to fix it.
#3 reserved for me also.
Good for you man. Way to go!!!!!!
Tap-a-Talked from my Mesmerize
is there anyway u could port the cm7 releases to id really love to be running cm7 instead of having to flash fascinate radios and all tht crap..
Outstanding.
I'd love to test on my showcase. I have everything I need to go back via odin, and this is the rom I've been waiting for.
Congrats man, I know how much time/effort you put into this!
Sent from my SCH-I500 using XDA App
O and thx my pants are wet now good rom
Sent from my SCH-I500 using XDA App
hold of on tht keeps boot looping on the miui bootupscreen any thoughts?
I got the same thing, but I think it's because I forgot to wipe data/cache/whatever... So I'm trying again.
Edit:
Yeah, it's just looping the spash.
Im also getting boot loop. Im on the ee19 radio, should i do the 10 and retry it?
i tryed both and it bootlooped
godofwar762 said:
i tryed both and it bootlooped
Click to expand...
Click to collapse
That makes me very worried about flashing this.. I was just going to do it.
I wonder if flashing to the cm7 then trying to flash this would work better. Using the cm7 you can use rom manager to install the miui, so im gonna try that.
Edit: Unfortunately same thing that route also. Boot loop
That's what I came from, then the second time I went from the latest offical froyo.
seishuku said:
That's what I came from, then the second time I went from the latest offical froyo.
Click to expand...
Click to collapse
With no issues?
It did the same thing.
Well imma go try it ill report back when I'm done.
Are you guys flashing the Rom twice like the op says to?
Sent from my SCH-I500 using XDA App
The other day I updated my phone to 2.3.4 using odin. after that I had a horrible wifi signal and i kept losing my data connection all together. So I flashed back to Froyo 2.2.1. I am so confused because my phone kept force closing, I did a factory reset and it stopped but it says my kernal version is 2.6.32.9...is that normal? Also how do I go about flashing a good rom to my phone? The way it is now it is soooo slow which is why i updated to the 2.3.4...any information would be helpful as I am ready to throw my phone out the window.
pammiecaykz said:
The other day I updated my phone to 2.3.4 using odin. after that I had a horrible wifi signal and i kept losing my data connection all together. So I flashed back to Froyo 2.2.1. I am so confused because my phone kept force closing, I did a factory reset and it stopped but it says my kernal version is 2.6.32.9...is that normal? Also how do I go about flashing a good rom to my phone? The way it is now it is soooo slow which is why i updated to the 2.3.4...any information would be helpful as I am ready to throw my phone out the window.
Click to expand...
Click to collapse
Which 2.3.4 ROM did you flash via ODIN? KG4/KG6 both show less wifi signal but I actually haven't seen a difference in speed. I'm on this one right now:
[ROM] Stock Deodexed T959VUVKG4 with Root [Gingerbread 2.3.4][7.26.2011]--Whitehawkx
http://forum.xda-developers.com/showthread.php?t=1187293
The way to properly get to that is by doing the following:
1. ODIN
[ROM-Leak][ODIN] Gingerbread 2.3.4 T959VUVKG4
http://forum.xda-developers.com/showthread.php?t=1183413
2. Then boot up like normal and wait for it to load up into the system.
3. Turn off your phone again (shutdown) and put it back into download mode.
4. ODIN this to get CWM+Root http://forum.xda-developers.com/showthread.php?t=1194032 (use the ODIN version)
5. Keep lagfix disabled via the voodoo menu in recovery after you flash the CWM+root+Voodoo EXT4 package in the link in step 4.
6. Boot into the system. It's up to you, I flashed this
[ROM] Stock Deodexed T959VUVKG4 with Root [Gingerbread 2.3.4][7.26.2011]--Whitehawkx
http://forum.xda-developers.com/showthread.php?t=1187293
Which is a deodexed build which allows you to theme etc.
Some people have had issues getting onto EXT4 partitions while on a gingerbread ROM. I had a few issues myself. Needless to say there are several places to read about how to get EXT4 working on all partitions if you want to.
Best of luck, hope this helps.
Well to be completely honest, I don't know anything about partitions. All I know is that I updated my phone and then all of a sudden I had a horrible wifi connection and my data connection would just drop out all together and say "searching". I would have to reboot my phone 2 or 3 times to get it working again. What is a good rom to update to? Is have the kernal build that I do going to be an issue?
pammiecaykz said:
Well to be completely honest, I don't know anything about partitions. All I know is that I updated my phone and then all of a sudden I had a horrible wifi connection and my data connection would just drop out all together and say "searching". I would have to reboot my phone 2 or 3 times to get it working again. What is a good rom to update to? Is have the kernal build that I do going to be an issue?
Click to expand...
Click to collapse
Please read the post above and follow the steps and links and you will be fine
I have a Samsung Rugby Smart ( AT&T ).
I used the last two files on this page:
http://forum.xda-developers.com/showpost.php?p=30347369&postcount=5
Stock recovery and system: odin_gingerbread.ucla4_recovery_stock_system_stock _no_root.tar.md5
ClockworkRecovery 6.0.1.1 and No-Bloatware and Root: odin_gingerbread.ucla4_recovery_cwr_6011_system_no _bloat.tar.md5.gz
and my WiFi is not working. When I go to Wireless and Networks - Wi Fi Settings -
Says: Error next to the check mark to turn wifi on or off. :crying:
Everything else seems to work including sound.
Baseband: I847UCLH4
Gingerbread 2.3.6
Build Number: GINGERBREAD.UCLH4
Kernel version: 2.6.35.7
WiFi MAC address: Unavailable
Bluetooth address: works!!
Does anyone have any idea what could be the problem?
thanks you
Is this issue solved?
Is this issue solved?
VoiceArtistUSA said:
I have a Samsung Rugby Smart ( AT&T ).
I used the last two files on this page:
http://forum.xda-developers.com/showpost.php?p=30347369&postcount=5
Stock recovery and system: odin_gingerbread.ucla4_recovery_stock_system_stock _no_root.tar.md5
ClockworkRecovery 6.0.1.1 and No-Bloatware and Root: odin_gingerbread.ucla4_recovery_cwr_6011_system_no _bloat.tar.md5.gz
and my WiFi is not working. When I go to Wireless and Networks - Wi Fi Settings -
Says: Error next to the check mark to turn wifi on or off. :crying:
Everything else seems to work including sound.
Baseband: I847UCLH4
Gingerbread 2.3.6
Build Number: GINGERBREAD.UCLH4
Kernel version: 2.6.35.7
WiFi MAC address: Unavailable
Bluetooth address: works!!
Does anyone have any idea what could be the problem?
thanks you
Click to expand...
Click to collapse
You could flash back to stock firmware and try again. If the error persists then the files are probably not right for your phone.
broadways said:
You could flash back to stock firmware and try again. If the error persists then the files are probably not right for your phone.
Click to expand...
Click to collapse
The files the OP pulled are for his phone based on the baseband shown. It looks like it may be related to the OTA update that came through recently.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
---------- Post added at 08:40 AM ---------- Previous post was at 08:37 AM ----------
VoiceArtistUSA said:
I have a Samsung Rugby Smart ( AT&T ).
I used the last two files [edit] [and] my WiFi is not working
Baseband: I847UCLH4
Does anyone have any idea what could be the problem?
Click to expand...
Click to collapse
Did you install the OTA update that AT&T pushed recently before flashing the ODIN images?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
kemonine96 said:
Did you successfully apply the ota update that came through for the rugby?
Click to expand...
Click to collapse
VoiceArtistUSA said:
Yes, before any root or flash of course.
Click to expand...
Click to collapse
That explains it, the OTA update includes a slightly changed kernel (based on what I saw in the diffs) that is likely causing your WiFi issue. Can you try applying motorhead's kernel from here and see if WiFi starts working? I know it is not a full fix, but it should get your wifi back to working while motorhead and I coordinate on getting a stock kernel that can be flashed from CWR put together.
YEEEEE HAAAAWWWWW
I got some WIFI !!!!
Camera, BT and sound, seems like everything works.
Can't imagine why not a "Full fix".
Thank You !!!!
Says there is an OTA update, after it downloads, I get tossed into CWM bootloader 6.1.1 and the update doesn't get applied.
All I do is choose 'reboot system'.
Also I'm getting ...
"[ AT&T Address Book] Checking Subscriber Information"
when I touch contacts.
I am not an AT&T customer, I use STLK the BYOP program.
We really need a custom ROM for this great device, no bloat, no AT&T updates, no AT&T bloatwares, No CIQ, No City ID.
I would be HAPPY to PAY for a custom ROM and have it delivered two weeks from last Thursday. Jellybean?
Someone like me who chooses a rugged phone may not be into all the bells and whistles, so a basic stripped down
ROM would be great.
and yes, I am getting lag coming out of deep sleep. may have to hit power button twice to unlock.
Can't wait to try Motorheads soon to be released power kernel...
kemonine96 said:
That explains it, the OTA update includes a slightly changed kernel (based on what I saw in the diffs) that is likely causing your WiFi issue. Can you try applying motorhead's kernel from here and see if WiFi starts working? I know it is not a full fix, but it should get your wifi back to working while motorhead and I coordinate on getting a stock kernel that can be flashed from CWR put together.
Click to expand...
Click to collapse
VoiceArtistUSA said:
I got some WIFI !!!!
Camera, BT and sound, seems like everything works.
Click to expand...
Click to collapse
I'm glad to hear it's working again for you.
VoiceArtistUSA said:
Can't imagine why not a "Full fix".
Click to expand...
Click to collapse
Because I assumed you wanted to roll back all the way to stock . If I knew you were good with non-stock kernel I'd have said full fix .
VoiceArtistUSA said:
Says there is an OTA update, after it downloads, I get tossed into CWM bootloader 6.1.1 and the update doesn't get applied.
All I do is choose 'reboot system'.
Click to expand...
Click to collapse
There is an updater app you can freeze to prevent this from running. Nicedream06 and motorhead1991 have it disabled w/o ill effects.
VoiceArtistUSA said:
"[ AT&T Address Book] Checking Subscriber Information"
when I touch contacts.
I am not an AT&T customer, I use STLK the BYOP program.
Click to expand...
Click to collapse
No ideas on this one. I'm an ATT subscriber and I don't remember that firing off, but I bought the phone the month it was released...
VoiceArtistUSA said:
We really need a custom ROM for this great device, no bloat, no AT&T updates, no AT&T bloatwares, No CIQ, No City ID.
I would be HAPPY to PAY for a custom ROM and have it delivered two weeks from last Thursday. Jellybean?
Click to expand...
Click to collapse
Working on it with a few others "right now". We have stable boot in ICS (CM9 and AOSP builds) but the modem is dead. No cell service at all. There are other problems but we are focused on getting the antenna up and going.
VoiceArtistUSA said:
Someone like me who chooses a rugged phone may not be into all the bells and whistles, so a basic stripped down
ROM would be great.
Click to expand...
Click to collapse
Check the super thread. I have an ODIN image that is pretty stripped down and it includes the 6.x version of CWR. I left a few things in "just in case" but they can easily be stripped out using any of the various root tools for removing system apps.
VoiceArtistUSA said:
and yes, I am getting lag coming out of deep sleep. may have to hit power button twice to unlock.
Can't wait to try Motorheads soon to be released power kernel...
Click to expand...
Click to collapse
If you can post over in motorhead's thread that you are experiencing the problem it will help out to know that it is common. He mentioned he was looking into it. I'm sure something will be ready soonish.
kemonine96 said:
I'm glad to hear it's working again for you.
Because I assumed you wanted to roll back all the way to stock . If I knew you were good with non-stock kernel I'd have said full fix .
There is an updater app you can freeze to prevent this from running. Nicedream06 and motorhead1991 have it disabled w/o ill effects.
No ideas on this one. I'm an ATT subscriber and I don't remember that firing off, but I bought the phone the month it was released...
Working on it with a few others "right now". We have stable boot in ICS (CM9 and AOSP builds) but the modem is dead. No cell service at all. There are other problems but we are focused on getting the antenna up and going.
Check the super thread. I have an ODIN image that is pretty stripped down and it includes the 6.x version of CWR. I left a few things in "just in case" but they can easily be stripped out using any of the various root tools for removing system apps.
If you can post over in motorhead's thread that you are experiencing the problem it will help out to know that it is common. He mentioned he was looking into it. I'm sure something will be ready soonish.
Click to expand...
Click to collapse
The lag is a noted issue, along with the WiFi shutting off randomly and intermittently. I'm researching these issues as much as I can to find a fix, but I can only do so much so fast .
I was going to start a new thread but then I found this. I too had the issue with I the wifi turning off and the screen lag. After reflashing the no bloat Odin image and the 1.1 kernel my wifi turns on, but does not find any networks. It just searches then shuts off? Any ideas? I wonder if the stock kernel being worked on would fix this or if there is something else wrong. Any help would be greatly appreciated.
Sent from my SAMSUNG-SGH-I847 using xda premium
I sent the rugby smart to SAM to have it completely reloaded. when it comes back, i will try to make a back up much like i make an image of a hard drive...if that's possible.
For my PC, I have an image of this existing hard drive. If i pull it out and put in a BLANK hard drive, I can write the image to the new disk with all my apps installed...I use that feature often with my pc's and others...for mine, I frequently make a new updated image and delete the oldest one.
Once I change the bootloader, is it possible to get it back if I backed up with with Kies?
You guys are in luck. Kernel1.2 should be out shortly with the lag and wifi fixed . I'm waiting to hear back from another tester, but so far ut's proven stable. I've only had one error pop up, and that was after running pretty hard.
Motorhead1991, Is this for the Samsung Rugby Smart?
How much of, if any, overclocking??
Can you also tweak a non-overclocked version without "City ID" app, "Carrier IQ" app and possibly no AT&T bloatware??
You rock for everything thus far
No overclocking just yet, but I'm giving it hell. On the bright side, Kemonine and myself are currently treading in uncharted territory for this device (see if anyone gets my reference)
And to answer your question, yes it'll be for the Rugby.
iam not sure
thats a good question
Motorhead1991 said:
And to answer your question, yes it'll be for
the Rugby.
Click to expand...
Click to collapse
After a day of use, it seems very stable and even more efficient.
That is great news! Can't wait to test
Sent from my SAMSUNG-SGH-I847 using xda premium
alan2424m said:
thats a good question
Click to expand...
Click to collapse
Yeah, it actually did hurt to ask that one.
So after flashing the following new odin images
•Stock boot / kernel:
•Stock Boot + Stock Recovery + Stock System:
•Stock Boot + CWR 6.0.1.2 + No Bloat System:
My WiFi still turns on, searches for a while, finds nothing and turns back off! I have no idea what to do next. Any ideas?
ESPFreak said:
So after flashing the following new odin images
•Stock boot / kernel:
•Stock Boot + Stock Recovery + Stock System:
•Stock Boot + CWR 6.0.1.2 + No Bloat System:
My WiFi still turns on, searches for a while, finds nothing and turns back off! I have no idea what to do next. Any ideas?
Click to expand...
Click to collapse
When you flashed via ODIN did it show it was flashing the boot area? In the status window it should tell you which images are being flashed to the device. Can you re-try the stock boot/kernel ODIN image and confirm it did flash the boot image?
That is the only thing that booted. As soon as I selected the image I got a "MD5 checksum failed" prompt. The "start" button changed to the same message but it let me click it and it loads the boot.img. Does that help at all?
Sent from my SAMSUNG-SGH-I847 using xda premium
Not getting a cell phone signal at all on my Captivate. very rarely I get it and it stays on until I reboot for some reason, or sometimes goes off on its own. No problem with wi-fi or anything else.
Have had Gingerbread 2.3.5 - KK4 (official) for a long time, and did not have this problem. Here is what I did:
Installed Cyanogenmod 9.0 (ICS 4.0.4) on my Captivate that had the stock Gingerbread KK4. Also installed the gapps-ics package from 29 April 2012
I did this after rooting, and installing clockworkmod.
Even updated it to Cyanogenmod 9.1, but have the same issues.
More detail on it:
- The cellular radio shows no signal, but Wifi is on fine.
- When I press the power button, I see the power off and reboot options, including one that says "Airplane Mode is ON", although it clearly isn't since Wifi is working
- A couple of times, I rebooted into recovery, and did a "repair permissions" and rebooted, and it got a signal, but does not happen always
- Once the signal is on, it stays on for the whole day, but goes off again after a reboot
- Turning Airplane mode on and off does not help
Is this a modem issue, that seems to be a popular problem. It's almost as if there is a software bug that fools the phone into switching off wireless radio
Please help me fix it, or share successful fixes
I had same problem when I went to helly bean then back to remics-jb I flashed back to stock then back up to what I wanted it fixed the problem so I think its the modem.
Sent from my SGH-I897 using xda app-developers app
You need to flash to stock and back.
Sent from my SGH-I777 using xda premium
How do you flash your rom?
Im a little bit afraid to bricked again my cappy.
Sent from my SAMSUNG-SGH-I897 using xda premium
KOROCK is right
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?
up_on1 said:
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?
Click to expand...
Click to collapse
Not fixed yet. Wheredo I get the stock rom.?
rdugar said:
Not fixed yet. Wheredo I get the stock rom.?
Click to expand...
Click to collapse
A little search/reading goes a long way.. http://forum.xda-developers.com/showthread.php?t=1300843
KK4 is what you'll want to go back to stock but I highly suggest you read this before you do anything http://forum.xda-developers.com/showthread.php?t=1350266
Also, before returning to stock, you could try flashing a different modem.
Check to see if your baseband is still there. If it said "Unknown", you need to restore it. CM9 is supposed to have the modem.bin file included though. Check to see if the /radio folder have modem.bin in it, if it does, and the baseband still say Uknown, then manually delete the modem.bin, do a wipe and reflash a CM rom that have modem.bin included.
If Baseband is still there and still no signal, then check to see if IMEI is corrupted or lost (if its null or doesn't match the back of the phone). You can either copy over the efs backup folder if you have one and "fix permission" in CWM. If not, then you need to ODIN the phone to stock to fix it.