Related
I've saved a couple i9000 Odin flashed Fascinates with this method so it should work.
First, grab my DI01 All in One. You need an all inclusive package.
http://adrynalyne.us/files/kernels/DI01package3.tar.md5
You will need odin3 v 1.30. Google for it.
You also need Heimdall.
Heimdall – Glass Echidna There is a readme in the windows version zip if you get stuck. Drivers must be installed for it as well.
You also need a copy of the samsung galaxy s usb drivers, because Heimdall will remove them when you use it.
[Drivers] MS Windows x86 and x64 USB Drivers for Samsung Galaxy S - xda-developers
You will also need a PIT file from me:
http://dl.dropbox.com/u/2056318/atlas_v2.2.pit
Steps:
1. Install Heimdall and drivers.
2. Put phone in download mode and plug it in to usb cable.
3. Unzip the Odin file. 7zip can do this, but will give an EOF error. Ignore the error.
4. Choose each section in Heimdall and add the appropriate file, including PIT. Check repartition. Primary boot loader is boot.bin and secondary boot loader is sbl.bin.
5. Start. Boot once, check for problems. If problems persist, continue.
6. Reinstall Samsung USB drivers for Odin. This may require a PC reboot.
7. Put phone back in download Mode and start Odin, making sure its detected.
8. Load the entire Odin package, not extracted into the pda section of Odin. Include the PIT file. CHECK repartition.
9. Run the process.
If all goes well, you should be back to stock, crappy Eclair 2.1 without force close errors.
On a whim last night I flashed cm7 from kaoscinate. It wasnt what I wanted (nothing worked except calls data and sms), so I tried to go nack to sc 2.4. And of course I was bricked. But I just odined the eb01 radio and voila, I was ok.
Not sure if that helps.
Sent from my SCH-I500 using XDA App
i went to cm7 from sc 2.4 aswell, and to get back to sc 2.4 i just flashed cwmfroyo edition through cwm, rebooted the recovery then wiped data, re-installed sc 2.4 and bam! i was back.
upsidedownaaron said:
On a whim last night I flashed cm7 from kaoscinate. It wasnt what I wanted (nothing worked except calls data and sms), so I tried to go nack to sc 2.4. And of course I was bricked. But I just odined the eb01 radio and voila, I was ok.
Not sure if that helps.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I wouldn't say you were bricked. Bricked means the phone no longer functions period, no matter what you do to it. But I'm glad this helped you. I'll probably use the DL09 All in One and then flash SuperClean back over that.
When you flash an All In One, you are taking your kernel and your radio (modem) back to that version as well. When you want to go back to Froyo or whatever, make sure you flash the radio along with whatever else your flashing.
Boot looped. Wouldn't get past Samsung logo. Not an uncommon problem for me. I have become very comfortable with Odin.
Sent from my SCH-I500 using XDA App
upsidedownaaron said:
I have become very comfortable with Odin.
Click to expand...
Click to collapse
haha yeah. It's saved me but a couple times mostly anytime voodoo is involved. Tried restoring a nandroid backup of EB01 after flashing CM7 and got force closes from hell. Odin'd back using the EB01 unbloated/deodexed.tar and everything booted fine. Tried to restore the nandroid and couldn't do anything because of the force closes. Think I have corrupt data somewhere though. I also made a backup of the apps and data in MyBackupPro and ended up in the same force close situation upon reboot after restoring all. Selectively restoring a couple apps worked fine. Oh well.
Basically, I can't sustain a data connection for longer than about a minute before my fascinate disconnects. It takes about a minute to reconnect, then it disconnects again. Over and over and over. It never affects phone calls because it's not losing signal, it's just dropping the data connection.
I've been poking around my phone a bit, and in the past week, but I can't pinpoint what I did that made this start happening. I was hoping this thread would save me, but it didn't. I went back to DI01 using heimdall, booted up, still had the same problem. Reflashed with Odin, same thing. Went back to SCv2.4 with EB01 modem, same thing.
I ask this in this thread because I'm wondering what part of the phone remains untouched even with the full DI01 flash? Like some kind of low-level device mode that I triggered?
If there is nothing then it must be hardware related, and I will get a replacement.
@gizmo, maybe its time to start all over again with adryn's full di01 odin restore. i have had to do that twice now. and it has saved my butt.
i have become pretty familiar now with rebuilding my entire phone. it only takes about an hour now to go from a rom i like, to soft bricking it and then back to the rom i liked before i soft bricked with another alpha i just couldn't seem to wait to try.
Why does the movinand.bin fail when using Odin?
upsidedownaaron said:
@gizmo, maybe its time to start all over again with adryn's full di01 odin restore. i have had to do that twice now. and it has saved my butt.
i have become pretty familiar now with rebuilding my entire phone. it only takes about an hour now to go from a rom i like, to soft bricking it and then back to the rom i liked before i soft bricked with another alpha i just couldn't seem to wait to try.
Click to expand...
Click to collapse
Sounds pretty familiar . I always have to be breaking my stuff to be happy.
I've done the full heimdall DI01, followed by full Odin, to no avail. I think I messed up something with the service programming on the phone, but reactivating it doesn't help. None of the factory reset options I've tried have cleared the activation settings back to stock. Anyone know how to accomplish this?
I suppose I should move to my own thread now.
For the past 6 hours i've been trying to load a custom flash on the vibrant, i tried simple honey and vibrace and always have same problem. The installation seems to go fine but after reboot I cannot get passed the lock screen as i get spammed with errors that need forced closing, the thing is i can see things working good in the back ground, from what i read online about the errors, it has something to do with fonts and templates.
I need help as im going crazy, this is stressful . Btw I flash through the recovery method and i downgrade to 2.1 every time i try to do it over. If needed ill redo another one just to take pics of the error messages. Thanks
edit:
heres a screen
Uploaded with ImageShack.us
reboot into recovery and wipe data/fact reset
wipe cache
i have tried that and nothing happens, still get the errors at the lock screen, can't drag the puzzle piece or the screen to unlock because of constant force close pop ups
factory reset go into Mounts and format system, then reflash the rom over itself, most of those roms require you be on a Gingerbread OS prior to installation.
Ok, thank you i got it to finally work with your help, was about to start pulling my hair out.
i had the same issues..
my remedy
Odin to stock JFD...
flash GB boot loaders
Flash SH via Odin
wait 15 mins
Flash SH 5.0 and you should be good to go...
In short, I have a US Galaxy 4.0 Player, and have been enjoying it immensely, I've messed around with a few roms and kernels, and thought I'd try out the newest version of Han's Ethereal rom, version 2.1, with the TerraSilent 1.3.5 kernel. I heard it would take a long time to boot the first time, between 10 and 15 minutes, and that it would appear like it's bootlooping when it actually is not. Unfortunately, it ha been doing this for close to an hour now, making me think there actually is a problem. Has anyone ever experienced this huge amount of boot up time before?
(Also, I changed the filesystem to EXT4, as per Han's instructions, but I heard going back into CWM under the TerraSilent 1.3.5 messes with that, would it have anything to do with it?)
The filesystem mix up could definitely be the issue. You're best just flashing and booting. If possible, just stick to RFS. I think EXT4 just makes things too messy.
Your not alone on this one. I didn't change the file system, installed the same rom w/ the same kernel, and it's still looping
Nnn Noob said:
Your not alone on this one. I didn't change the file system, installed the same rom w/ the same kernel, and it's still looping
Click to expand...
Click to collapse
I have put a new version (2.2) that should fix the bootlooping issues (or at least help them). How many apps to each of you have? Sometimes you have to pull the battery to get it to finish booting up properly. The EXT4 filesystem should have nothing to do with it bootlooping on the bootlogo, if that was an issue, it should be looping on the bootloader (the splash screen you see before it starts booting).
Interesting, because once I went back to stock with the RFS filesystem and reflashed the same rom, it went just fine, booted in just over a minute. When I was trying to boot before, I had perhaps a couple dozen apps, so I thought that was unlikely to be the cause. But yeah, did the whole deal with the battery pull/reboot a couple times and still no luck. But once I went back to stock before I flashed it was no problem. I'm going to be flashing 2.2 soon, when I didn't mess with the filesystem, if everything goes smoothly, then I think that might be our culprit.
silentdoh said:
Interesting, because once I went back to stock with the RFS filesystem and reflashed the same rom, it went just fine, booted in just over a minute. When I was trying to boot before, I had perhaps a couple dozen apps, so I thought that was unlikely to be the cause. But yeah, did the whole deal with the battery pull/reboot a couple times and still no luck. But once I went back to stock before I flashed it was no problem. I'm going to be flashing 2.2 soon, when I didn't mess with the filesystem, if everything goes smoothly, then I think that might be our culprit.
Click to expand...
Click to collapse
I have found out that if you wipe cache/dalvik, sometimes it will get stuck in a bootloop. If you head into recovery after that happens, and wipe cache/dalvik from there (again if need be), then hit fix permissions (might be necessary), it should boot just fine. I would also hold off until 1.3, as I am releasing it today, and it is finally stable.
Am I bootlooping?
hanthesolo said:
I have found out that if you wipe cache/dalvik, sometimes it will get stuck in a bootloop. If you head into recovery after that happens, and wipe cache/dalvik from there (again if need be), then hit fix permissions (might be necessary), it should boot just fine. I would also hold off until 1.3, as I am releasing it today, and it is finally stable.
Click to expand...
Click to collapse
I downloaded the latest (v2.4) Ethereal ROM and flashed it, and I think I may have gotten myself into a boot loop. Either that or I'm just impatient.
I'm currently running Klin's Klassic R5, rooted. Never messed with the file system.
Here's what I did:
1) Reboot to Recovery. Wipe cache and Dalvik.
2) Reboot to Download, flash the tar file with Odin. (Did not check PIT). All threads completed.
3) Device rebooted, I get Samsung logo (with Steve's Kernel icon at the bottom), then it displays "ANDROID" and the screen sleeps, and occasionally comes back on for a few seconds. This continues for close to an hour.
4) I found this thread. Pulled battery, wiped cache and Dalvik again, fixed permissions, rebooted.
5) Same results as #3.
I did make a nandroid backup before starting this. Should I restore it and re-flash?
Thanks,
Scott
Fixed?
thirdeye73 said:
I downloaded the latest (v2.4) Ethereal ROM and flashed it, and I think I may have gotten myself into a boot loop. Either that or I'm just impatient.
I'm currently running Klin's Klassic R5, rooted. Never messed with the file system.
Here's what I did:
1) Reboot to Recovery. Wipe cache and Dalvik.
2) Reboot to Download, flash the tar file with Odin. (Did not check PIT). All threads completed.
3) Device rebooted, I get Samsung logo (with Steve's Kernel icon at the bottom), then it displays "ANDROID" and the screen sleeps, and occasionally comes back on for a few seconds. This continues for close to an hour.
4) I found this thread. Pulled battery, wiped cache and Dalvik again, fixed permissions, rebooted.
5) Same results as #3.
I did make a nandroid backup before starting this. Should I restore it and re-flash?
Thanks,
Scott
Click to expand...
Click to collapse
I am back up and running. Flashed TerraSilent kernel and got my device back up. I tried restoring from my nandroid backup and that made my bootloop worse--left me in a samsung logo bootloop. I'd love to know why the nandroid restore didn't work, if anyone has any ideas what I might've done wrong.
Tried flashing Ethereal again, no problems this time. Only weird thing is Holo Launcher kept force closing, had to uninstall it.
Hi Guys,
I think the internal memory of my wifes phone is dead. Her phone all of the sudden turned off, then it was stuck in a bootloop. I tried to play back a nandroid backup but I always got an error message that the data partition was not being wiped... I used Odin then to flash back to stock and do a repartitioning of the phone. Odin works fine, then the phone reboots trying to apply the new rom, but it stops, telling me that the data partition again could not be formatted.
Is the nand-flash broken or is there a way to make it work? I can only use the download mode now, or use the regular 2e recovery... any tips are highly appreciated.
With the influx if new inexperienced vibe users I must ask, does your device have a stock front facing camera?
Paranoid, sitting in a deep sweat...
Lol,
no it does not, it is really the Vibrant T959 not the V not anything else. I am used to flash custom roms. It happened before, even playing Nandroid backups back, most of the time I had to do it twice, since data partition could not be mounted... 2nd try always worked and that was only for this specific phone. I simply guess the flash memory is corrupt...
We've seen some of this.. what rom was she on that fc'd and what rewrite odin files are you flashing? Are you familiar with the encryption Bug?
She was using the Passion Rom, v13.1 with Touchkernel 8.2 and the data.fix.
The phone had this problem like 3 times already. It simply shuts down, when you turn it back on, bootloop. Only thing that helped was playing a nandroid backup back. When doing this, nandroid already had problems mounting the data partition, so I had to flash it twice to go through.
This time, the 3rd time, the phone told me about a failed data encryption... this time, no nandroid backup is working, due to failing data partition.
When I Odin back to Elcair, I use the PIT file that comes with the AIO Toolbox and the Elcair Rom for Odin. I set the phone into download mode, Odin gets a connection to my phone. Then i select the PIT and PDA files, enable re-partition,autoreboot and F.reset time. I flash, everything works fine, Odin is done, the phone reboots, but then I get the red error message telling me that formatting the data partition did not work.
I did read about that ICS bug and about the workaround, but this kinda only works if you still have a working phone? Or did I get something wrong?
Yep. Sounds like EU bug. You'll find lots of info on that and things to try to get around it.
I'd go to Google and type in: XDA Samsung Vibrant encryption Unsuccessful and see what it brings up.
Happy trails and good luck!
Not sure if it is EU, sounds similar. Hers the work around guide
http://forum.xda-developers.com/showthread.php?p=24418319
Paranoid, sitting in a deep sweat...
I've been using CM13 on my phone for a long while, but it was heavily bugged (my camera kept crashing, I've kept losing cell reception, couldn't receive calls etc), so I finally decided to try another ROM. I've heard good things about ResurrectionRemix ROMs, so I've decided to give it a try. I did factory reset and wiped cache (using CWM 6. something) and flashed RR 7.1 along with the appropriate gapps and rebooted the phone. It's worth noting that I've put the ROM and Gapps zip files on USB stick and connected it to the phone via micro USB cable. It all went smoothly, and the phone booted right up. However, once I got into the startup setting and choosing the language suddenly it just rebooted all on its own. Same thing happened 2 more times, and I got stuck in a bootloop after that.
So I figured I should flash another ROM, and I wanted to give RR 6.0 a try. I've downloaded it and saved it to my USB stick, however, when I tried to flash any zip files from my stick, it just kept randomly unmounting, disrupting the process, giving me "USBdisc0 idle-unmounted" message. Since I don't have an SD card, only thing I could do was push files to my phone, and I've managed to do so via Quick ADB Pusher. This time, flashing went without a hitch, however, I've tried cleaning my phone completely (formatting all the data and system files), and I think I messed it up a bit when I did that, since I didn't flash SuperSU along with ROP and gapps. Again, I got stuck in a bootloop without any signs of the ROM working.
So I decided to flash CM13 again. At least I was sure it was working on my phone, and I figured it was better to have a crappy phone than no phone at all. So I pushed the CM13 file onto the phone and flashed it, but still got stuck in bootloop. I finally remembered about SuperSU and tried to flash it too, but now my phone kept restarting in the middle of the flashing process. I've tried doing the factory reset and cache wipe, but I can't flash any files now without it restarting only few seconds into the process.
I have no idea what's going on, but seems that my phone is doing worse and worse as time moves on. At least I can still boot into recovery and download mode, so (hopefully) something can still be done. As it's probably painfully obvious, I'm not too knowledgeable about this stuff, I'm just following instructions people smarter than me put out, but seems I've messed it up good this time. Am I beyond help?
Try to download newest firmware from sanmobile.com and flash it with odin. Then root it make backup flash recovery and flash rom that you choose with recovery. There are lots of tutorials here on xda and on youtube. Just remember that flashing stock firmware with odin will delete all of your data so try to back them up somehow (i think that if you boot phone in recovery (twrp) the pc will see it like a pendrive)
Sirius8 said:
...
As it's probably painfully obvious, I'm not too knowledgeable about this stuff, I'm just following instructions people smarter than me put out, but seems I've messed it up good this time. Am I beyond help?
Click to expand...
Click to collapse
TBH you made the mistake many beginners make... Going ahead too fast with insufficient knowledge. But never too late to learn that lesson
Since you are getting more and more confused and your phone seems acting strange I recommend starting from scratch an be analytic about it. This will take just a few minutes more but you can be sure where a problem comes from.
First of all: Take 30 minutes to get acquainted with the basics and read through the first thread in my signature (just do it...)
If you can still get in download mode, get your latest stock rom e.g. from sammobile.com and flash it via ODIN. Run stock for a few minutes to see if everything works correctly (test camera, outgoing/incoming calls, mobile data, wifi, gps etc.). If something does not work STOP HERE and report back.
If all is fine go back to ODIN and install latest TWRP (cwm is seriously outdated, can cause lots of errors). Then boot into TWRP and flash whatever custom rom you like. If you install e.g. LOS 14.1 or RR 7.1.1 make sure you install gapps direcly after you flash the rom (do not reboot in between).
Any questions pop up: Shoot. I'm happy to help.
---------- Post added at 04:49 PM ---------- Previous post was at 04:42 PM ----------
McXred said:
Try to download newest firmware from sanmobile.com and flash it with odin. Then root it make backup flash recovery and flash rom that you choose with recovery. There are lots of tutorials here on xda and on youtube. Just remember that flashing stock firmware with odin will delete all of your data so try to back them up somehow (i think that if you boot phone in recovery (twrp) the pc will see it like a pendrive)
Click to expand...
Click to collapse
Since he already wiped system and data there is no point in a backup of those partitions. Only thing worth saving would be the efs partition.
And you don't need to root stock rom to go further...
If you are unrooted you have to REMOVE the "auto-reboot" checkmark in odin options and then - after the flash of twrp - reboot to recovery (TWRP) manually via holding Power+Home+VolUp for a few seconds.
If you do not uncheck that "auto-reboot" box, an thus allow the unrooted system (stock samsung system) to boot, it will overwrite the new twrp recovery you flashed 2 seconds before...
This is the point where I believe many confusion comes from. If you root first, any recovery you flash will not be overwritten. That is - I think - why many tutorials/tips say you must root stock first before installing a custom rom, which is simply not true.
But you are right that it would help to flash TWRP fist as outlined above, boot into it and make a backup to a microSD card... but of the efs partition (!) as the very first step. Then keep that backup safe and go from there with stock rom, testing for any problems.
So to reiterate the steps I would go:
1) Flash TWRP via odin and boot directly into it
2) Backup efs partition to a microSD card
3) Flash stock rom via ODIN and test
4) Go from there / report baback
Thank you so much for the replies guys, I'm glad there's still hope for my trusty SIII.
Are there any alternatives for sammobile.com though, since it requires premium account for the firmware I need. I've found another mirror on the site mrcrab.net/stockrom/2444.html (mirror 1 leads to sammobile.com, while mirror 2 leads directly to rapidgator), but can I trust it not to mess my phone up further?
Try updato.com for the firmware.
Hawaiihemd said:
If you can still get in download mode, get your latest stock rom e.g. from sammobile.com and flash it via ODIN. Run stock for a few minutes to see if everything works correctly (test camera, outgoing/incoming calls, mobile data, wifi, gps etc.). If something does not work STOP HERE and report back.
Click to expand...
Click to collapse
I've manage to flash stock ROM via Odin, however, as soon as the phone booted up it gave me the "low battery" message, even though I think there was plenty of battery left. But I figured the flashing process must have drained it. As I've tried to tap the OK button, the screen just froze and remained frozen for over 5 minutes. I took battery out and reinserted it, since nothing else worked, and got stuck in bootloop again, just as before flashing stock firmware.
Sirius8 said:
I've manage to flash stock ROM via Odin, however, as soon as the phone booted up it gave me the "low battery" message, even though I think there was plenty of battery left. But I figured the flashing process must have drained it. As I've tried to tap the OK button, the screen just froze and remained frozen for over 5 minutes. I took battery out and reinserted it, since nothing else worked, and got stuck in bootloop again, just as before flashing stock firmware.
Click to expand...
Click to collapse
Try to charge phone without turning it on, when it says its fully charged try to flash it again.
McXred said:
Try to charge phone without turning it on, when it says its fully charged try to flash it again.
Click to expand...
Click to collapse
Good idea. I would also keep it on the charger while booting.
This could be a symptom of a defective battery. So these steps might help.
Looks like you were right guys. I've recharged the battery and tried to flash the stock firmware again, but for some odd reason (it seems like I can't do the same thing twice with this phone ) Odin was giving me grief and couldn't establish proper connection with my phone, even though it recognized it at the beginning of the process. I've tried changing cables and ports, but with no avail.
After I gave that up, I tried booting the phone up anyway, but keeping it plugged in the charger this time. It booted right up, but I expected it to crash and reboot at any moment. So I sped up through the settings a and login processes, but it still worked like a charm. I've checked the camera and everything worked perfectly. So I kept it on charger for a couple of hours, to check if I would have any random crashes, but nothing happened. After I was sure it was stable, I unplugged the charger, and within the second I did that the phone crashed and got stuck in the bootloop again.
I've plugged the charger back in and it booted up just fine. The battery level was 89%, and I left it on charger the whole night (12+ hours). It had 90% when I woke up, it's back at 89% right now.
So, everything points to a faulty battery, but it seems strange to me this happened just as I was flashing another ROM, even though I never had any problems with it before. And even though it wouldn't let me boot, I could use recovery and download mode for as long as I liked, and once I did boot with the charger plugged in, the battery wasn't drained but it was around 90%.
Hawaiihemd said:
TBH you made the mistake many beginners make... Going ahead too fast with insufficient knowledge. But never too late to learn that lesson
Since you are getting more and more confused and your phone seems acting strange I recommend starting from scratch an be analytic about it. This will take just a few minutes more but you can be sure where a problem comes from.
First of all: Take 30 minutes to get acquainted with the basics and read through the first thread in my signature (just do it...)
If you can still get in download mode, get your latest stock rom e.g. from sammobile.com and flash it via ODIN. Run stock for a few minutes to see if everything works correctly (test camera, outgoing/incoming calls, mobile data, wifi, gps etc.). If something does not work STOP HERE and report back.
If all is fine go back to ODIN and install latest TWRP (cwm is seriously outdated, can cause lots of errors). Then boot into TWRP and flash whatever custom rom you like. If you install e.g. LOS 14.1 or RR 7.1.1 make sure you install gapps direcly after you flash the rom (do not reboot in between).
Any questions pop up: Shoot. I'm happy to help.
---------- Post added at 04:49 PM ---------- Previous post was at 04:42 PM ----------
Since he already wiped system and data there is no point in a backup of those partitions. Only thing worth saving would be the efs partition.
And you don't need to root stock rom to go further...
If you are unrooted you have to REMOVE the "auto-reboot" checkmark in odin options and then - after the flash of twrp - reboot to recovery (TWRP) manually via holding Power+Home+VolUp for a few seconds.
If you do not uncheck that "auto-reboot" box, an thus allow the unrooted system (stock samsung system) to boot, it will overwrite the new twrp recovery you flashed 2 seconds before...
This is the point where I believe many confusion comes from. If you root first, any recovery you flash will not be overwritten. That is - I think - why many tutorials/tips say you must root stock first before installing a custom rom, which is simply not true.
But you are right that it would help to flash TWRP fist as outlined above, boot into it and make a backup to a microSD card... but of the efs partition (!) as the very first step. Then keep that backup safe and go from there with stock rom, testing for any problems.
So to reiterate the steps I would go:
1) Flash TWRP via odin and boot directly into it
2) Backup efs partition to a microSD card
3) Flash stock rom via ODIN and test
4) Go from there / report baback
Click to expand...
Click to collapse
Still on charger, still 90 percent.