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.
Hi I'm a new member,
I rooted my fascinate easily enough. Then searching and learning about ROMs and Kernels I decided to do use ODIN CWM Recovery to 'backup' or whatever most forums tell you to before installing a new ROM. Point is my phone is stuck in manual boot mode and I cannot undo it.
I have tried multiple times using ODIN plus the four stock files
Stock-i500-VZW-Kernel.tar.md5
Stock-i500-VZW-pit.pit
Stock-i500-VZW-Recovery.tar.md5
Stock-i500-VZW-System.tar.md5
(I always would try to implement them in order pit/system, pit/kernel, pit/recovery)
Unfortunately after the first one (pit/system) ODIN says the process fails, I go ahead with the other two and they both amount to nothing happening. My phone does not reset or do anything for this matter and I am forced to shut down ODIN and unplug my phone (upon which it dies with no battery).
Then I put back in the battery and Im back to before in manual boot mode with
Reboot system Now
Apply sdcard:update.zip
wipe data/factory rset
wipe cache partition
Btw wiped data and wiped cache and it didn't help me =(.
Please someone help me, I really don't want this new phone to be dead... Thanks in advance
Oh and when I press "apply sdcard:update.zip" I receive
E:Can't mount \dev\block\vold\179:9
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
I really don't care at all about keeping the phone rooted or not or whatever. I just want to be able to make calls again!
So it looks like you're stuck in blue recovery ... sounds like something that Odining a stock package should fix.
Here is a nice thread for getting back to stock (it's a sticky in the general section). The packages include system, recovery, kernel, and radio in a single file (I've actually never odin'd four separate files to get back to stock, or even ever flashed a system-only file), though no pit file.
So open up odin with your phone in download mode (with the battery out, otherwise there's a small chance of odin stalling at the end), and use:
- either the DI01 all-in-one, EB01 all-in-one, or this DL09 package in PDA
- the pit file in PIT (the link says DI01/EB01 but it also works with DL09)
- check "re-partition" if it isn't already checked
- run odin and hopefully in five minutes your phone will work again If for some reason it doesn't, that thread has instructions for using heimdall, although I've never had to resort to it.
So try this and see if it works! (For which package to use, I'd suggest trying DL09 first (since you'll need it to get to the official froyo build) and DI01 if that fails. If you're wondering whether DL09+pit actually works, I've used it to get out of a "stuck in blue recovery after odining stuff" situation myself so yes, it works.)
Thank you for the response! It's encouraging to hear any support and I think yours is promising.
So unfortunately I tried D101 and no go. Turns out this was before I realized this was for 2.1 and I'd prefer 2.2 for the upgrades. Although would you suggest 2.1 for the purpose of rooting/ROMing/Kerneling in the future? I ask because I'm slowly gaining confidence that after fixing this I might be willing to try this again...
Odin (1.7 -> I decided at your poster friend's advice to upgrade from 1.3) worked well said 'pass' and everything. Unfortunately when booting my phone it went straight to the boot screen as always.
Meanwhile I'm downloading the EB01 and your suggested DL09 to test those two.
Hopefully one of those will work but if not, I guess I'll try that heimdall technique the poster suggested in the other forum. Hopefully not tho b/c it looks a bit more complicated.
I'll let ya know if one of these others works.
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
mattjac1 said:
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
Click to expand...
Click to collapse
Definately stay away from rom manager cwm if you have the voodoo lagfix enabled, but since all the new fascinate roms are edify scripted, flashing through cwm in rom manager would be ok.
Sent from my Froyo'd Evil Fascinate full of PB&J
Ok...I'm at a point where I had no other choice but to get another replacement. I looked just about everywhere my patience would take me, and decided to give up. I hope someone could/would have a solution for me or others like me.
I had EH03 deoxed rom and decided I wanted ICS build5. So I installed CM7, I whiped cache, DLVK, and system data. Then flashed ICSb5 and GAPPS, Rebooted and stuck on ICS splash screen.
At this point USB ports wouldn't recognize fascinate. Downloaded all Fascinate drivers from Samsung, drivers for Nexus S, ADB, Android SK. You name it I got it. Nothing worked for USB detection. I even followed YT videos on turning Vista/PC off and unplug. Nothing.
After messing with data cords,(numerous ones,trying another PC), PC ports, I happened to pull plug and battery out of Fascinate at the same time, not sure what version of CWM, it was blue, came on. Luckily I had two Nandroid backups on SD.
I flashed Nandroid back to CM7 successfully. Rebooted fine and hooked to USB but still not recognized. At this point I was able to get into recovery using ROM. So, I did something stupid...lol...I tried to flash earliest Nandroid which was performed when on EH03 deoxed. Once I did this, I wiped all needed data and rebooted. Now Fascinate shows Samsung logo. It doesnt reboot, just that the logo stays until I pull battery. Now if I have battery in wth phone off and plug in, the charging battery comes on but doesn't show battery level. Doesn't go away till I pull battery.
The funny thing is that I can get into Download mode but USB is still unrecognized/malfunction on PC/Vista. I only wish that I was able to link phone and PC just to use Odin with PIT file and stock EDO5 or EH03.
Any advice?
dssheeley1 said:
Ok...I'm at a point where I had no other choice but to get another replacement. I looked just about everywhere my patience would take me, and decided to give up. I hope someone could/would have a solution for me or others like me.
I had EH03 deoxed rom and decided I wanted ICS build5. So I installed CM7, I whiped cache, DLVK, and system data. Then flashed ICSb5 and GAPPS, Rebooted and stuck on ICS splash screen.
At this point USB ports wouldn't recognize fascinate. Downloaded all Fascinate drivers from Samsung, drivers for Nexus S, ADB, Android SK. You name it I got it. Nothing worked for USB detection. I even followed YT videos on turning Vista/PC off and unplug. Nothing.
After messing with data cords,(numerous ones,trying another PC), PC ports, I happened to pull plug and battery out of Fascinate at the same time, not sure what version of CWM, it was blue, came on. Luckily I had two Nandroid backups on SD.
I flashed Nandroid back to CM7 successfully. Rebooted fine and hooked to USB but still not recognized. At this point I was able to get into recovery using ROM. So, I did something stupid...lol...I tried to flash earliest Nandroid which was performed when on EH03 deoxed. Once I did this, I wiped all needed data and rebooted. Now Fascinate shows Samsung logo. It doesnt reboot, just that the logo stays until I pull battery. Now if I have battery in wth phone off and plug in, the charging battery comes on but doesn't show battery level. Doesn't go away till I pull battery.
The funny thing is that I can get into Download mode but USB is still unrecognized/malfunction on PC/Vista. I only wish that I was able to link phone and PC just to use Odin with PIT file and stock EDO5 or EH03.
Any advice?
Click to expand...
Click to collapse
In the op of ics and also droidstyles guide you have to flash build 1 before you can flash build 5
Sent from my SCH-I500 using XDA App
I've never flashed version 1 before flashing.build 5. In fact I've had the least amount of problems going back to stock (ED05) then flashing ICS.
I bootlooped when i went from stock EH03 to Build 5 so i did 3 first then 5.
But this doesn't help our poster here.
OP:
you get into DL mode but odin wont see your phone?
What i suggest is to try: Move the usb cable to a different port. see if your pc can see it then. Second thing try a totally different computer. Chances are your PC is trying to use borked up drivers.
Once you get odin going flash a stock image [i recommend eh03] then cwm then build 3 and now the new build 6. good luck!
if you need any links or a more detailed guide I STRONGLY suggest Droidstyles guild, it is by far the best and most up to date for the fassy!
OhioYJ said:
I've never flashed version 1 before flashing.build 5. In fact I've had the least amount of problems going back to stock (ED05) then flashing ICS.
Click to expand...
Click to collapse
Consider yourself lucky....going from stock to build 6 causes me problems and many others. Going from stock, to build 1, then build 6 works flawless.
MOD please close thread due to lapsed timeline and no longer support of this model.Ty
Sent from my SGH-i717/GT-N7005 w/phMOD_beta2
dssheeley1 said:
MOD please close thread due to lapsed timeline and no longer support of this model.Ty
Sent from my SGH-i717/GT-N7005 w/phMOD_beta2
Click to expand...
Click to collapse
You realised you just bring a a old thread back yourself and no longer support of this model wtf you realise people.still use this phone everyday Right?
Sent from my SCH-I500 using Tapatalk 2
Last night I went to reboot into recovery and my phone now sits at the Galaxy S2 splash screen and won't boot up. Tried plugging it in powered off and it won't even go into charging mode. The battery picture just comes up and the little spinning wheel keeps going.
So Ive been trying for the last hour to reflash the phone back to stock using both Entropys return to stock guide as well as the 'How to return your phone to the store' guide too and no luck.
Heimdall of course as always just flat out doesn't work so I hooked it up to my laptop and ran Odin. Odin connects to the phone fine and the box turns yellow, but the minute I hit start, it just gives me this:
<ID:0/008> SetupConnection..
<ID:0/008>
<OSM> All threads completed. (succeed 0 / failed 1)
I even tried the one click ICS leak from Rootzwiki and the same thing.
I can get the phone into Download mode no problem but man I cannot get it to flash ANY of these rome!!
Any advice or should I just take it to an ATT store on the way home from work??
I got it around the second week of February so hopefully worst case scenario I can still exchange it..
Im at my wits end here, can't do anything with it!!
I had same problem with my sprint Gs2, I took it into the store they told me since I rooted they couldnt help me. But the guy said go into download mode and root it again, it will remove anything and everything off it. Idk if that's what you want though. It got my phone back up and running
Sent from my SPH-D710 using xda premium
Ahh forgot to add I can't get into Recovery anymore.
No clue what happened. I can get it into Download mode but not Recovery.
If I could've gotten into Recovery I could've just flashed my Nandroid last night and fixed it hehe..
ODIN requires Download mode, not recovery mode. If your phone can indeed go into download mode as you claimed, you should be able to flash any ODIN flashable ROMs.
Try flashing just a kernel with recovery
Sent from my GT-I9100 using Tapatalk 2 Beta-2
You didn't say what you were running before the problem occured. Or if you did anything just before. Need more information to be able to troubleshoot the problem.
You might try flashing Entropy's DD kernel only with odin. He has at least one tar in his DD thread OP.
It may be that one of the components, such as param.lfs is screwed, but it would be better to have more information first before just randomly trying to flash things.
You can find most everything you might need in the Download Repository.
creepyncrawly said:
You didn't say what you were running before the problem occured. Or if you did anything just before. Need more information to be able to troubleshoot the problem.
You might try flashing Entropy's DD kernel only with odin. He has at least one tar in his DD thread OP.
It may be that one of the components, such as param.lfs is screwed, but it would be better to have more information first before just randomly trying to flash things.
You can find most everything you might need in the Download Repository.
Click to expand...
Click to collapse
Yeah sorry about the lack of info hehe! I made the thread about 20 minutes before I had to go to work and spent the hour before that trying to fix it hehe.
Anyways, I WAS running the ATT ICS leak that Task and Fenny packaged up with CWM. I WAS going to get everything backed up and attempt to move over to CM9 when it went to crap.
So far what Ive attempted to flash with Odin was the following with no luck:
Entropys 'Return to Stock' PDA.tar (the UCKH7_stock_odin with root)
ATTGalaxyS2Unroot_SGH-i777.tar
The leaked ATT Odin one click flasher from Rootzwiki (same results as using regular Odin with any of the above)
I did in fact also download the I777UCKH7-CL503881-Parts-NoBL.7z from creepys 'How to prepare your phone for return to the store' thread BUT..
The instructions tell you to unpack the 7z and then run the one click .exe inside but there is no .exe in the archive. Just the modem.bin, cache.img, image, factoryfs.img, and hidden.img. This would've been fine to try but of course Heimdall is every Mac OS users enemy and anytime I try to use the front end I get a 'missing firmware.xml' error and running it via command line just never connects to the phone.
Since Entropys return to stock package only has the factoryfs.img and zimage, sounds like I need to find a complete tar file that has all the other parts that creepy's has in it..
Last thing I did before going to work was updating the USB drivers on my Win 7 laptop to see if that would help, but since I can only use my laptop via Remote Desktop Connection from my Mac (display is dead) I had to do a Windows Update so I could get the laptop to restart (which I don't think you can do through RDC unless I missed it), and I had to run to work before it finished..
And I was STILL 10 minutes late hahaha!
So the laptop JUST got rebooted now that Im home, Im going to go see if theres also a newer version of Odin, and Im gonna go dig through the Download Repository and also check that Samsung Firmwares site to see if I can find myself a complete tar ball of the stock 2.3.4 firmware..
Ive got Saturday off finally so if I can't get it flashed and fixed by then I think Im going to bite the bullet and just take it to an ATT store and see if they'll swap it. Hopefully theres no 30 day policy, because Im pretty sure my Blackberry crapped out on me about 2 months in and they had no problem sending me another in the mail.. I REALLY wish I had my MyBackup done on my external SD card and not the internal one.. Gotta put another 40 hours into grinding in all my Zenonias to get back to where I was hehe..
Slavestate said:
Yeah sorry about the lack of info hehe! I made the thread about 20 minutes before I had to go to work and spent the hour before that trying to fix it hehe.
Anyways, I WAS running the ATT ICS leak that Task and Fenny packaged up with CWM. I WAS going to get everything backed up and attempt to move over to CM9 when it went to crap.
So far what Ive attempted to flash with Odin was the following with no luck:
Entropys 'Return to Stock' PDA.tar (the UCKH7_stock_odin with root)
ATTGalaxyS2Unroot_SGH-i777.tar
The leaked ATT Odin one click flasher from Rootzwiki (same results as using regular Odin with any of the above)
I did in fact also download the I777UCKH7-CL503881-Parts-NoBL.7z from creepys 'How to prepare your phone for return to the store' thread BUT..
The instructions tell you to unpack the 7z and then run the one click .exe inside but there is no .exe in the archive. Just the modem.bin, cache.img, image, factoryfs.img, and hidden.img. This would've been fine to try but of course Heimdall is every Mac OS users enemy and anytime I try to use the front end I get a 'missing firmware.xml' error and running it via command line just never connects to the phone.
Since Entropys return to stock package only has the factoryfs.img and zimage, sounds like I need to find a complete tar file that has all the other parts that creepy's has in it..
Last thing I did before going to work was updating the USB drivers on my Win 7 laptop to see if that would help, but since I can only use my laptop via Remote Desktop Connection from my Mac (display is dead) I had to do a Windows Update so I could get the laptop to restart (which I don't think you can do through RDC unless I missed it), and I had to run to work before it finished..
And I was STILL 10 minutes late hahaha!
So the laptop JUST got rebooted now that Im home, Im going to go see if theres also a newer version of Odin, and Im gonna go dig through the Download Repository and also check that Samsung Firmwares site to see if I can find myself a complete tar ball of the stock 2.3.4 firmware..
Ive got Saturday off finally so if I can't get it flashed and fixed by then I think Im going to bite the bullet and just take it to an ATT store and see if they'll swap it. Hopefully theres no 30 day policy, because Im pretty sure my Blackberry crapped out on me about 2 months in and they had no problem sending me another in the mail.. I REALLY wish I had my MyBackup done on my external SD card and not the internal one.. Gotta put another 40 hours into grinding in all my Zenonias to get back to where I was hehe..
Click to expand...
Click to collapse
Add me on gtalk and we can see what we can do [email protected]
At this point I don't know if anything will help heh.
All it will do is either sit on the GS2 boot screen, or it will go into Download mode.
Download mode though, no luck so far. Odin just won't flash it for some reason. It sees it, the COM port box lights up yellow, but the minute you hit Start, it just goes right to that error message I posted above. After this, I have to close both Odin and disconnect the phone and reboot it into Download mode.
I went through the Download Repo. Tried I777UCKH7-CL503881-Full.7z, and even the param.ifs by itself but everything just gives the same result. I didn't try Entropys DD though since I was running the stock ICS and didn't want to really mess anything up. Only thing I can think of left to try is flashing Task/Fennys CWM modded stock ICS kernel but after all this I doubt its going to work. I tried the stock rooted GB kernel earlier and it didn't bother flashing either.
Am I maybe connecting it wrong? I have the battery pulled and am going into Download mode by holding the vol buttons and connecting the usb cable to the laptop. I don't want to kill the battery power I have left as it won't charge now either. Basically I just fire up Odin, connect the phone and put it in Download mode, select my tar file and put it in the PDA slot, hit Start and go.. Should I be doing anything differently??
Whenever I've had a problem with Odin like that, it has always been that some partition got flashed wrong/partially/corrupted, and the only fix was to reflash the damaged partition. As long as Odin is seeing the phone, then it must be either a software/firmware problem or a hardware problem. I'm still thinking it is firmware, but it seems to be outside my experience.
I havn't been playing with ICS yet, but I have noticed that there have been a number of reports similar to yours, where people have flashed some flavor of ICS. This supports the idea that it is firmware. I have always understood that if the problem is firmware, and if the phone can boot into download mode, it can be recovered.
Yeah Im wondering if I should try flashing the PIT file I have for the phone, but I don't know crap about partitioning these things and didn't want to really mess it up.
Guess at this point its worth a shot. I was about to go sit and chat with the warranty folks at ATT (mines a refurb so Ive only got til the end of the month before warranty s up). Maybe Ill try the pit file and let Odin repartition the thing. I can't flash a firmware back onto it anyways.
EDIT: Holy crap progress.. I flashed the stock secondary boot loader with Odin (in the Bootloader slot) and that actually flashed. Now I just reconnected it and decided to try the ATT ICS leak one click from Rootzwiki and it appears my phone is now flashing!!!!! As long as my crap is still on the internal usb storage today is gonna be a good day hehe! Yep all is well so far! Phone just rebooted and its now at the ICS setup screen! WOOHOO!!! Crisis averted!! Thanks guys for the comments and help! Creepy thank you for reminding me we have that repository!!
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737