Related
So it seems like the first time stuck so it restarted, now it's stuck at partition. I selected the PIT and the PDA stock file, but it's just sitting there ... I'm on the phone + PC logo.
Am I totally screwed? What to do?
What pit did you select?
gtg465x said:
What pit did you select?
Click to expand...
Click to collapse
The one from the xda thread additional infuse files
bella92108 said:
The one from the xda thread additional infuse files
Click to expand...
Click to collapse
Not seeing that thread. Please provide a link.
i think he means from lost1
@op i think the 512pit from the sgsphones will work
gtg465x said:
Not seeing that thread. Please provide a link.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1084837
in OP additional files
It gets stuck at "Setup Connection.."
im gonna go out on a limb here and say use h8rifts stock rom with the 512pit found in the i9000 and captivate sections. h8's rom is missing the param.ifs though, not sure if you will need that.
Dani897 said:
im gonna go out on a limb here and say use h8rifts stock rom with the 512pit found in the i9000 and captivate sections. h8's rom is missing the param.ifs though, not sure if you will need that.
Click to expand...
Click to collapse
So I've been able to use the 512 pit and get it to get back to the "Downloading... Do not turn off Target". ... but then when I go back in and try to flash the stock Rooted ROM I get the "Initialization..." then it just stops there... ideas?
not sure. let it sit for a while. h8rift or somebody said it took his like 20 minutes(if i remember right) which seems weird. also you should be logged in windows as admin and the usb plugged into a port that connects to the mother board not a expansion card or hub.
honestly though i have only used heimdall on the infuse. and never repartitioned because heimdall requires bootloaders for repartition. im not sure i trust lost1's bootloaders and if there is an issue with them there are no others to use.
it might be a driver issue. maybe samsung needs some updated drivers for the infuse.
also are you sure you have your .net framework up to date on windows? i cant think of everything odin depends on but i think having .netframework4 helps with some things on the phone, cant remember ifodin depends on it though
Dani897 said:
not sure. let it sit for a while. h8rift or somebody said it took his like 20 minutes(if i remember right) which seems weird. also you should be logged in windows as admin and the usb plugged into a port that connects to the mother board not a expansion card or hub.
honestly though i have only used heimdall on the infuse. and never repartitioned because heimdall requires bootloaders for repartition. im not sure i trust lost1's bootloaders and if there is an issue with them there are no others to use.
it might be a driver issue. maybe samsung needs some updated drivers for the infuse.
also are you sure you have your .net framework up to date on windows? i cant think of everything odin depends on but i think having .netframework4 helps with some things on the phone, cant remember ifodin depends on it though
Click to expand...
Click to collapse
So I've been able to get it to say FACTORYFS now. I decided to just try the NON-rooted stock file to see if maybe it'll work. Right now it says Firmware update Start.... and there's a tiny green line flashing, but it's just been sitting there for 5 mins alrady.... just let it sit?
bella92108 said:
So I've been able to get it to say FACTORYFS now. I decided to just try the NON-rooted stock file to see if maybe it'll work. Right now it says Firmware update Start.... and there's a tiny green line flashing, but it's just been sitting there for 5 mins alrady.... just let it sit?
Click to expand...
Click to collapse
cant hurt to leave it there a little longer. the captivate never took that long but we also had a true factory flash oneclick odin that they use to reset refurbished phones. no such luck on the infuse unless someone wants to see if designgears has some sort of connection at samsung who can get it like he somehow was able to get it for the captivate. the significance of odin oneclick is that is has all the files. param.ifs, boot.bin, sbl.bin, and all the first boot scripts. our stock roms have come from rom dumps. the captivate stock roms came from samsung.
i would leave it for a good 20 minutes. then try something else. you may need to try files from lost1's stock rom you can use 7zip to manipulate the .tar files and magic ISO to manipulate the .rfs files within the .tar files, but atleast one ofthe files from lost1 doesnt work. if i had 2 infuses id experiment with you to be able to post what works and what doesnt. with only one phone im hesitant to try anything that is not tested
Dani897 said:
cant hurt to leave it there a little longer. the captivate never took that long but we also had a true factory flash oneclick odin that they use to reset refurbished phones. no such luck on the infuse unless someone wants to see if designgears has some sort of connection at samsung who can get it like he somehow was able to get it for the captivate. the significance of odin oneclick is that is has all the files. param.ifs, boot.bin, sbl.bin, and all the first boot scripts. our stock roms have come from rom dumps. the captivate stock roms came from samsung.
i would leave it for a good 20 minutes. then try something else. you may need to try files from lost1's stock rom you can use 7zip to manipulate the .tar files and magic ISO to manipulate the .rfs files within the .tar files, but atleast one ofthe files from lost1 doesnt work. if i had 2 infuses id experiment with you to be able to post what works and what doesnt. with only one phone im hesitant to try anything that is not tested
Click to expand...
Click to collapse
I'm using H8rift's restore... and both of the two (rooted and non) have the same issue for me.
It just sits... I've used the rooted and non-rooted.... ugh.
It goes to firmware update start then has a little greenness in the progress bar on the computer, and a little blueness in the progress bar on the phone, but I let it sit for 30 minutes and it never progresses any further, so there's something going on.
I've tried other usb ports, updated drivers, every method of compatibility and admin mode, even reinstalled windows basic version, haha.... ugh, this is hopeless.
I think it's time to chalk this up to a very very expensive lesson learned and go out and buy a replacement... not happy about that :-(
bella92108 said:
I'm using H8rift's restore... and both of the two (rooted and non) have the same issue for me.
It just sits... I've used the rooted and non-rooted.... ugh.
It goes to firmware update start then has a little greenness in the progress bar on the computer, and a little blueness in the progress bar on the phone, but I let it sit for 30 minutes and it never progresses any further, so there's something going on.
I've tried other usb ports, updated drivers, every method of compatibility and admin mode, even reinstalled windows basic version, haha.... ugh, this is hopeless.
I think it's time to chalk this up to a very very expensive lesson learned and go out and buy a replacement... not happy about that :-(
Click to expand...
Click to collapse
Why did you use a .pit? Did I not state in the OP of the Odin thread not to use one? take out the .pit, uncheck re-partition and flash the package as it was originally attended. you will NEVER need to re-partition your phone until we actually start CHANGING your partitions sizes (i.e. CM7, MIUI, possibly Samsung's gingerbread, etc.)
h8rift said:
Why did you use a .pit? Did I not state in the OP of the Odin thread not to use one? take out the .pit, uncheck re-partition and flash the package as it was originally attended. you will NEVER need to re-partition your phone until we actually start CHANGING your partitions sizes (i.e. CM7, MIUI, possibly Samsung's gingerbread, etc.)
Click to expand...
Click to collapse
He doesn't follow directions well.This much we know. He royally screwed up flashing my ROM as well and then proceeded to blame his problems on my ROM being crappy.
gtg465x said:
He doesn't follow directions well.This much we know. He royally screwed up flashing my ROM as well and then proceeded to blame his problems on my ROM being crappy.
Click to expand...
Click to collapse
Sorry to hear that.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
I am putting up another Odin package right now for him to try if h8rift's doesn't get him going since he tried to repartition.
gtg465x said:
I am putting up another Odin package right now for him to try if h8rift's doesn't get him going since he tried to repartition.
Click to expand...
Click to collapse
...... She ...
Sent from my SAMSUNG-SGH-I997 using XDA App
Gtg the man
hoofadoo said:
...... She ...
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
see how nice he was to help you! ive listened to these guys from day one never one problem and if there is they help you untill its fixed. they were once like us too bu now deserve respect in the developing\helping noob world lol
Poor bella, she seems to be having a tough time lately...
Sent from my Samsung Infuse 4G
I figured I'd post this since there seems to be a bunch of people STILL having problems getting to EP1Q Gingerbread and Gummy.
I made a post about this in another thread but it seems not enough people have seen it.
Below you will find the steps and links to get you to EP1Q from absolutely any ROM or Kernel or Voodoo or Non-voodoo, Gingerbread or Froyo.
--------------------------------------------------------------------------------------------------------------
1. Turn off phone, remove battery, open Odin, plug in phone via USB and put in download mode. Put battery BACK in.
2. Check Re-Partition, UN-check Auto Reboot and F. Reset Time.
3. Load the PIT file below. Also load the ED1 file below in PDA.
4. Hit Start
5. Wait til it is fully finished. When it is done, unplug the phone and remove the battery.
6. Put battery back in and start up the phone. It may or may not boot into Recovery.
7. If it boots into recovery then hit Reboot. It should now boot into ED1.
8. First exit out of Odin and re-open it. Then Repeat STEP 1.
9. Load EP1Q into PDA in Odin. Hit Start.
10. Be patient and wait, when it is finished doing everything, you may or may not see red error lines, don't worry. Go to the next step.
11. Repeat Step 1 and load "New_CWM_Recovery.tar" into the PDA slot. Hit Start. It should reboot itself into Recovery, hit reboot.
12. It should now load into EP1Q.
You may stop here if you don't want Gummy.
--------------------------------------------------------------------------------------------------------------
13. Repeat Step 1.
14. Load Gummy EP1Q into the PDA slot in Odin. Hit Start.
15. It should reboot into Recovery when finished, hit Reboot.
16. You are now on a fully fresh copy of Gummy EP1Q!
--------------------------------------------------------------------------------------------------------------
Links:
ED1 - http://www.multiupload.com/LNTF3IKJ21
PIT - http://www.mediafire.com/?kk62yxpp8b8x918
CWM - http://www.multiupload.com/D7ELKNADJD
EP1Q - http://www.multiupload.com/0EKVFHOFJ9 - REAL WORKING FAST DOWNLOAD LINK, uploaded by myself.
Gummy - http://bit.ly/n0G8J9
Links are from imnuts, Kejar31, and P3Droid. They have done all of the dev work, this is just a How-To created by me.
Thank Jeebus. The noobs just say the same thing over and over.
Sent from my Droid Charge running GummyFroyo 1.9.1
kvswim said:
Thank Jeebus. The noobs just say the same thing over and over.
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
You're welcome. Let me know if you need any more help.
Why ED1or ED2 though, I keep seeing people say to use that instead of EE4... Anyways I've gone back and forth from EE4 to EP1H and EP1Q then back about a dozen times (to test, load different roms, or try and duplicate problems to troubleshoot) in the last few days without a single problem so I don't know what people are doing wrong. I'll always help when I can though
Nice write-up too btw
blazing through on my VZ Droid Charge 4G
Syn Ack said:
You're welcome. Let me know if you need any more help.
Click to expand...
Click to collapse
1) have you had any luck with EP1Q Special from TBH? 2) Do you notice any connectivity issues with 4G on EP1Q stock?
anoninja118 said:
Why ED1or ED2 though, I keep seeing people say to use that instead of EE4... Anyways I've gone back and forth from EE4 to EP1H and EP1Q then back about a dozen times (to test, load different roms, or try and duplicate problems to troubleshoot) in the last few days without a single problem so I don't know what people are doing wrong. I'll always help when I can though
Nice write-up too btw
blazing through on my VZ Droid Charge 4G
Click to expand...
Click to collapse
It just seems that the ED1 All in One file seems to be a 100% surefire way to get to EP1Q from anywhere. I came from a Voodoo Froyo and used this exact method to get to EP1Q Gummy. It seems that most people that are having problems are the ones with Voodoo Froyo.
j0kerm4n said:
1) have you had any luck with EP1Q Special from TBH? 2) Do you notice any connectivity issues with 4G on EP1Q stock?
Click to expand...
Click to collapse
Personally I haven't tried anything with the EP1Q special. All I know is flashing EP1Q Gummy over stock EP1Q is amazing. Stock EP1Q is pretty buggy compared to Gummy. Connectivity is better for 4G on EP1Q. Wifi is very good too.
j0kerm4n said:
1) have you had any luck with EP1Q Special from TBH? 2) Do you notice any connectivity issues with 4G on EP1Q stock?
Click to expand...
Click to collapse
the signal is greatly improved in terms of radio connectivity... 4G/3G/1X hand-off is pretty much non existent for me, I get 4G in 4G areas and 3G/1X in spotty areas. Not so much of that constant switching just when its sitting on my desk
blazing through on my VZ Droid Charge 4G
Syn Ack said:
It just seems that the ED1 All in One file seems to be a 100% surefire way to get to EP1Q from anywhere. I came from a Voodoo Froyo and used this exact method to get to EP1Q Gummy. It seems that most people that are having problems are the ones with Voodoo Froyo.
Click to expand...
Click to collapse
Alot of people are forgetting to deactivate voodoo lag and reverting back to rfs.... This is causing boot loops.
Sent from my SCH-I510 using XDA Premium App
danalo1979 said:
Alot of people are forgetting to deactivate voodoo lag and reverting back to rfs.... This is causing boot loops.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Yeah exactly. This completely fixes everything.
danalo1979 said:
Alot of people are forgetting to deactivate voodoo lag and reverting back to rfs.... This is causing boot loops.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
When flashing in Odin, if a file is included to perform a data wipe, you don't need to deactivate voodoo as it will auto-format the partitions correctly.
imnuts said:
When flashing in Odin, if a file is included to perform a data wipe, you don't need to deactivate voodoo as it will auto-format the partitions correctly.
Click to expand...
Click to collapse
Which is extremely helpful in situations like these
Otherwise it can cause a nightmare to casual flashers.
Anyone else having trouble with the stock EP1Q Odin file? I downloaded it from three separate links on the main download page, and when I start Odin every time I get this result:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CI510_VZW_EP1Q_ALL_ONE-LTE-CP_REV3_user_CL397514.tar.md5 is invalid.
<OSM> End...
Click to expand...
Click to collapse
I followed the instructions step-by-step up to this point, and the Odin of stock ED1 worked fine.
Thoughts?
tsgeek said:
Anyone else having trouble with the stock EP1Q Odin file? I downloaded it from three separate links on the main download page, and when I start Odin every time I get this result:
I followed the instructions step-by-step up to this point, and the Odin of stock ED1 worked fine.
Thoughts?
Click to expand...
Click to collapse
I went to p3's mydroidworld post and downloaded it from the second link. Did this yesterday midday and it had no problems with md5 hash, Although it bootlooped for me so I just odin'd gummy 1.9RC1 and all was well.
Sent from my Droid Charge running GummyCharged 1.9RC1
GoBlue13 said:
I went to p3's mydroidworld post and downloaded it from the second link. Did this yesterday midday and it had no problems with md5 hash, Although it bootlooped for me so I just odin'd gummy 1.9RC1 and all was well.
Click to expand...
Click to collapse
I'll try that one. Of course it was the one I skipped when choosing them randomly
Of course it was. I hate when that happens. Good luck!
Sent from my Droid Charge running GummyCharged 1.9RC1
OK, I did end up going to P3Droid's post on Droid World here to get the EP1Q stock download. I chose the Mirror 1 Download from there. Using that file with Odin did work. I got sent into a boot loop, but really didn't care because I was going to Odin GummyCharged EP1Q anyway. From that point, I picked up from Step 12 in this thread's OP.
Worked just fine. I'm now the happy owner of a GummyCharged EP1Q Charge,
I flashed ED1 with the pit, rebooted, and flashed driectly to gummy GBE from there. Worked fine without flashing the EP1Q leak first.
tsgeek said:
I'll try that one. Of course it was the one I skipped when choosing them randomly
Click to expand...
Click to collapse
I went over there. They talked about removing the .md5 extension and the file working. I did that and it appears to be working.
Removing the md5 extension is not a smart idea, even if it worked for you. That's an easy way to brick your phone. The md5 hash is how you know everything is there. If you odin a corrupt md5 file, it will just fail. If you odin a corrupt tar file, more than likely you're bricked.
I searched thoroughly before making this post, but I am a noob at this so I may have missed something relevant. Please don't get mad at me if I did!
Basically: I attempted to flash a custom ROM, intending to use clockwork mod. However, when I got to the step after rooting where you reboot the phone and put it into recovery mode to get into clockwork, I realized that no combination of button presses was working. Yes I know I was a fool not to check first to make sure I could get into recovery mode, but I didn't know and I'm new at this.
It was soft-bricked (stuck at samsung screen), so I got a jig and using that I can now get into download mode ONLY. I have scoured the internet and tried using KIES and Odin to get it working (I don't care if it's with a custom ROM, stock firmware, whatever, I just want a functional phone at this point), but I'm having no luck getting any of the numerous tutorials I've tried to work.
Before it became soft bricked it was running froyo (I believe 2.2, but I'm not positive).
Can someone please walk me through whatever the easiest way is to get functioning firmware of any type onto my phone, or direct me to a tutorial that will help me?
I appreciate any help, VERY MUCH. Thank you in advance.
EDIT: Also, the most recent tutorial I tried was this one: http://forum.xda-developers.com/showthread.php?t=853950
But when I run Odin I get this:
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Are you saying odin is not working for you?
Sent from my SGH-T959V using xda premium
Yes, Odin is not working for me. It recognizes my phone, but I can't get it to do anything. I'm not sure if I'm loading the correct firmware or making some other mistake, but thus far I feel like I am following the tutorials I've tried to the letter with no luck.
You do know that the thread above is NOT for this phone?
Sent from my SGH-T959V using xda premium
Okay, just to be clear you are attempting to load Galaxy S 4g software onto a Galaxy S 4g, correct?
I noticed that latest tutorial you posted was for the i9k which is nowhere near the same and in fact result in such errors if software from the i9k were to be loaded onto our phone.
http://forum.xda-developers.com/showthread.php?p=16762954
Everything you need, to get a gb ROM is right there
Sent from my SGH-T959V using xda premium
Yes, I am trying to load galaxy s 4g software onto a galaxy s 4g. Thank you. I'm sorry I'm retarded. I'm not really clear on the difference between different types of galaxy S. Thank for the link, I will try that and report back!
paxthomas said:
Yes, I am trying to load galaxy s 4g software onto a galaxy s 4g. Thank you. I'm sorry I'm retarded. I'm not really clear on the difference between different types of galaxy S. Thank for the link, I will try that and report back!
Click to expand...
Click to collapse
Sorry if we came off offending there man, we just wanted to make sure. Good luck and let us know if it works out
Sent from my SGH-T959V using XDA App
Use this... It's fool proof http://forum.xda-developers.com/showthread.php?t=1333423
paxthomas said:
I searched thoroughly before making this post, but I am a noob at this so I may have missed something relevant. Please don't get mad at me if I did!
Basically: I attempted to flash a custom ROM, intending to use clockwork mod. However, when I got to the step after rooting where you reboot the phone and put it into recovery mode to get into clockwork, I realized that no combination of button presses was working. Yes I know I was a fool not to check first to make sure I could get into recovery mode, but I didn't know and I'm new at this.
It was soft-bricked (stuck at samsung screen), so I got a jig and using that I can now get into download mode ONLY. I have scoured the internet and tried using KIES and Odin to get it working (I don't care if it's with a custom ROM, stock firmware, whatever, I just want a functional phone at this point), but I'm having no luck getting any of the numerous tutorials I've tried to work.
Before it became soft bricked it was running froyo (I believe 2.2, but I'm not positive).
Can someone please walk me through whatever the easiest way is to get functioning firmware of any type onto my phone, or direct me to a tutorial that will help me?
I appreciate any help, VERY MUCH. Thank you in advance.
EDIT: Also, the most recent tutorial I tried was this one: http://forum.xda-developers.com/showthread.php?t=853950
But when I run Odin I get this:
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try re-installing the drivers, this has happened to me b4 and that worked
AdamOutler said:
Use this... It's fool proof http://forum.xda-developers.com/showthread.php?t=1333423
Click to expand...
Click to collapse
If you want kj6 stock (latest stock), then run the same one click with kj6 from kies http://forum.xda-developers.com/showthread.php?t=1358498
The first click of "flash" writes just the rom, click "flash" after going back into download mode again to get bootloaders.
Then odin kj1 kernel with the odin link from http://forum.xda-developers.com/showthread.php?t=1194032
I'm planning on making an alternative one-click with the kj1 lagfix+cwm kernel with kj6 stock rom soon. So you have one-click to an install with cwm.
EDIT:If you have a problem getting into Download mode, you might want to shop around for a usb jig for the sgs4g. If that doesn't help they also provide unbricking service.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
you can do it.. just keep trying to put ur phone into download mode it happen to me... just keep trying and try different ways of doing it. after awhile i should work.. then odin with kd1 and start back from square one.. i been there if anything pm me.
tehgyb said:
Sorry if we came off offending there man, we just wanted to make sure. Good luck and let us know if it works out
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
It's cool; I really appreciate you guys helping me out! I'm trying what you suggested now!
AdamOutler said:
Use this... It's fool proof http://forum.xda-developers.com/showthread.php?t=1333423
Click to expand...
Click to collapse
So I just used it and it started going but then said "local and device PIT files don't match" and ended the session. Does that mean that my phone is not a Galaxy S 4G after all? If it's not, how can I tell which type of Galaxy S it is?
paxthomas said:
So I just used it and it started going but then said "local and device PIT files don't match" and ended the session. Does that mean that my phone is not a Galaxy S 4G after all? If it's not, how can I tell which type of Galaxy S it is?
Click to expand...
Click to collapse
Take the battery out. What is the model number?
Sent from my SGH-T959V using XDA App
It's an SPH-D700
EDIT: I think it's actually a Galaxy Epic. I'm sorry to have put you all through the trouble helping me when I didn't even have the right phone. I'm just so frustrated and I've never been good at this kind of thing. Ugh.
paxthomas said:
It's an SPH-D700
Click to expand...
Click to collapse
Wrong phone, man.
You have a Samsung Epic 4G.
Here: http://forum.xda-developers.com/showthread.php?t=1052813
Well thanks for all of your help anyway. It's awesome that you guys just come here and help people for free. Maybe one of these days I will have the time to read up on this stuff and not be such an idiot.
paxthomas said:
Well thanks for all of your help anyway. It's awesome that you guys just come here and help people for free. Maybe one of these days I will have the time to read up on this stuff and not be such an idiot.
Click to expand...
Click to collapse
You're not an idiot man, we've all been there, let us know how your phone restore goes, and don't be afraid to flash a custom ROM! You'll be amazed as to just how much better they run. c:
Just what everyone wants.... another thread about a bricked phone.
I have no idea what happened to my phone.... I have been running Valhalla Final for a week now with no issues to speak of and lost all my ringer tones after a failed attempt to put sound on a boot-loader using Absolute System. I rebooted into recovery and tried to restore my nandroid which failed when it said unable to unmount system. when I rebooted it had fc in android.core multiple times so I rebooted again and after it loaded had no control. did a battery pull and then would not go past the power up screen. downloaded heimdall one click file T959V-UVKJ6-One-Click.jar and put it into download mode. flashed and it went fine until factoryfs failed. now still in download but img is pic of phone to computer. last 2 attempt was
SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar and it failed first at loading the modem and then at loading recovery.
I am lost. seems like everything I try makes it little worse. Have not tried ODIN yet.
Is there any hope or am I out a phone?
Give Odin a try. Last time I used Odin it froze so I pulled the plug, and when I put my phone back in download it showed that same screen, yet Odin still went through.
So no, that screen doesn't mean you're out a phone.
Sent from my SGH-T959V using xda premium
95Z28 said:
Give Odin a try. Last time I used Odin it froze so I pulled the plug, and when I put my phone back in download it showed that same screen, yet Odin still went through.
So no, that screen doesn't mean you're out a phone.
Click to expand...
Click to collapse
I was hoping to hear that... what odin file do you suggest... A lot of the links are now dead.
ShadyAce80 said:
I was hoping to hear that... what odin file do you suggest... A lot of the links are now dead.
Click to expand...
Click to collapse
Grab chadster's KG4 here. I believe it has ODIN 1.85 included in the file. Don't mess with any of the check boxes in ODIN; let ODIN decide what to check.
After that, you should be able to get back to KJ6 via a one-click.
Shady grab Ravers stock GB and honks GB odin kernel. Flash Ravers, If you can, then honks. That will give you stock plus cwm. You know where to go from there. Funny thing is just yesterday FB had a post about leaving BOOTLOADERS alone w/o unbrickable mod. Good luck.
Downloading now from sendspace.com
I'm hoping this works...
hechoen said:
Funny thing is just yesterday FB had a post about leaving BOOTLOADERS alone w/o unbrickable mod. Good luck.
Click to expand...
Click to collapse
LOL yeah I read that AFTER the fact... I have been messing with the animations for a few days with out issue... it was only after I trying sound for a day or two that I crashed.
Live and Learn
ShadyAce80 said:
Downloading now from sendspace.com
I'm hoping this works...
Click to expand...
Click to collapse
wait no dude i downloaded that one from sendspace does the download stop and download stop download etc... for you? it did for me i think the files corrupt thomas.raines gave me a newer download link that one from sendpsace is like 197mb the one thomas gives me is 300mb and he said dont flash pit file (he did not include ) because is risky try this one first!!! i tried the sendspace one and it stop at setup connection...
http://dl.dropbox.com/u/54863010/T959VUVKG4.zip
shady
Are you going with the chadsters leak or ravers stock?
I don't know why you guys keep recommending old (leaked) ROMs to debrick with.
@Shady if you see anything posted by myself, dsexton, bhundven or raverx3x you can bet that we've tested it extensively and that it'll work on your phone.
On that note I recommend you read the whole page here:
http://forum.xda-developers.com/showthread.php?t=1358498
Download from the SMS KJ6 (beta2d) Kernel Stock Rom with Bootloaders link. This will get you a one click flash solution that you can go back to when you have problems. This, unlike the KG4 file others have been recommending, is the latest version of gingerbread (KJ6 is 2.3.6) and you'll have a custom kernel + root to boot so you can get flashing other gingerbread ROMs. I hope you don't have trouble flashing, and if you do, read the OP to what I linked you to. All the instructions are there.
I know this file has been failing for you but you can try restarting your computer and flashing it from safe mode. When your computer is booting up, keep pressing F8 until you get a menu. Pick "Safe mode with networking" from the menu using your arrow keys and press enter.
sorry too many tabs open
FBis251 said:
I don't know why you guys keep recommending old (leaked) ROMs to debrick with.
Click to expand...
Click to collapse
Only because he was failing with one-clicks and wanted to use ODIN. That one (KG4) has always worked for me, so I was basing it off of experience. Never claimed it was optimal
I know this file has been failing for you but you can try restarting your computer and flashing it from safe mode. When your computer is booting up, keep pressing F8 until you get a menu. Pick "Safe mode with networking" from the menu using your arrow keys and press enter.
Click to expand...
Click to collapse
Never thought about trying it from safe mode. Nice idea.
FBis251 said:
I don't know why you guys keep recommending old (leaked) ROMs to debrick with.
Click to expand...
Click to collapse
That's what I'm saying. I don't use heimdell(because my computer hates it for some reason). So ravers stock GB and honks kernel to get cwm works well to set me back up.
ShadyAce80 said:
glad you posted this. download just completed. i haven't done anything with this file yet... will follow your link.
Click to expand...
Click to collapse
oh after they say to flash the bhuvden kernel well that is what they told me to get rid of gremlines or something, then flash the custom rom, youll have cwm and such, tell me how it goes .
To all of you thank you very much for your help... I think I have my phone back.... Our fembot Linda is doing her thing right now...
@FB I tried one click method in safe-mode and it was unable to find the drivers even after reinstalling a few times.. restarted in normal mode and gave it one more shot and I now have my phone back.
Thanks again for all the help.
hechoen said:
That's what I'm saying. I don't use heimdell(because my computer hates it for some reason). So ravers stock GB and honks kernel to get cwm works well to set me back up.
Click to expand...
Click to collapse
I totally forgot he made a stock ODIN. My bad!
I really need to rewrite the starter pack to have heimdall one click instructions. Nobody ever got around to making it.
I've only given the guide a cursory look at times, but I'd be willing to draft something for the guide if thst helps keep you focused on developing.
Sent from my SGH-T959V using xda premium
stephen_w said:
I've only given the guide a cursory look at times, but I'd be willing to draft something for the guide if thst helps keep you focused on developing.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
A video would be perfect. Been busy with school since I just started and now I got a gig making a website so I'm also working on that.
FBis251 said:
A video would be perfect. Been busy with school since I just started and now I got a gig making a website so I'm also working on that.
Click to expand...
Click to collapse
I've never done the video thing. Guess I can research it and give it a go.
Hi all, yesterday I woke up to a world of pain.
I checked my phone to see a bunch of things had FC'd over the night. This had never happened before as I've been running this rom since sean released it and haven't had any issues since. I began to wonder if the ROM I was using had some kind of expiration date. Throughout the day, I tried multiple times to flash different roms, recoveries, even ODIN'd every rom tar I could find, only to face the same result over and over and over- my Skyrocket would boot back up to SKYICS 4.2E-17(ULCE2) and after a few minutes, start FC'ing everything. I made recovery tars and kernel tars and tried them too. Odin would flash, seem like everything was peachy, reboot and... back to my former rom, like nothing happened.
I realized later on in the day that this has to be an issue of not being able to write properly to any partition. I was stuck with CWM 5.8.1.3 (even though I'd try to upgrade that with no avail, even wrote through adb shell dd to of=/dev/block/mmcblk0p22 which made no difference).
Now I know to search before posting, and searching I have been for a file similar to the I9100's recovery image with the CODE, MODEM, CSC and .PIT in a bunch of tars and the closest method I could find was here [GUIDE] Fix an unflashable or soft bricked GSII (I9100G/M/P/T VERSION INCLUDED!).
I think I'm screwed. I've tried everything I can think of. The NAND just will not go RW. Is there any way to breathe new life into my Skyrocket, or is it doomed to repeat July 3rd over and over, Ground Hog day style?
mightyoj said:
Hi all, yesterday I woke up to a world of pain.
I checked my phone to see a bunch of things had FC'd over the night. This had never happened before as I've been running this rom since sean released it and haven't had any issues since. I began to wonder if the ROM I was using had some kind of expiration date. Throughout the day, I tried multiple times to flash different roms, recoveries, even ODIN'd every rom tar I could find, only to face the same result over and over and over- my Skyrocket would boot back up to SKYICS 4.2E-17(ULCE2) and after a few minutes, start FC'ing everything. I made recovery tars and kernel tars and tried them too. Odin would flash, seem like everything was peachy, reboot and... back to my former rom, like nothing happened.
I realized later on in the day that this has to be an issue of not being able to write properly to any partition. I was stuck with CWM 5.8.1.3 (even though I'd try to upgrade that with no avail, even wrote through adb shell dd to of=/dev/block/mmcblk0p22 which made no difference).
Now I know to search before posting, and searching I have been for a file similar to the I9100's recovery image with the CODE, MODEM, CSC and .PIT in a bunch of tars and the closest method I could find was here [GUIDE] Fix an unflashable or soft bricked GSII (I9100G/M/P/T VERSION INCLUDED!).
I think I'm screwed. I've tried everything I can think of. The NAND just will not go RW. Is there any way to breathe new life into my Skyrocket, or is it doomed to repeat July 3rd over and over, Ground Hog day style?
Click to expand...
Click to collapse
thats a new for the sr, dont think ive read any1 w/that prob so search might not help here for this forum, did odin(1.85) says it completed w/o any errors, did u do a full wipe b4 flashing a new rom. did u try going back to stock using sammobile, read this b4 u flash back to stock http://forum.xda-developers.com/showthread.php?t=1652398.
u can also try to reformat both sdcards, back them up 1st, do a full wipe(im not sure if u tried that) and try again, u can try the hercules forum(t989) its our sister phone, or else a hardware problem
vincom said:
thats a new for the sr, dont think ive read any1 w/that prob so search might not help here for this forum, did odin(1.85) says it completed w/o any errors, did u do a full wipe b4 flashing a new rom. did u try going back to stock using sammobile, read this b4 u flash back to stock http://forum.xda-developers.com/showthread.php?t=1652398.
u can also try to reformat both sdcards, back them up 1st, do a full wipe(im not sure if u tried that) and try again, or else a hardware problem
Click to expand...
Click to collapse
Thanks vincom, i've tried full wipe, mounted under pc and format the internal, did the darkside super wipe. reboot and back to skyics, internal SD stuffed with my data, which i wiped.
I've also tried the sammobile I727UCKJ2_I727ATTKJ2_ATT tar with odin 1.85 and 1.87 and had a successful flash, yet reboot and back to skyics. here is the message log below:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_SGH-I727user_CL626051_REV02.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> amss.bin
<ID:0/004> cache.img.ext4
<ID:0/004> mdm.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
..., yet reboot and back to skyics. My guess is that this is hardware related to the nand flash itself, i remember reading that these things only have so many rw cycles until they are toast. whats odd about that is that this is my work phone, only had it since Feb 20, 2012, and I haven't flashed a lot of roms on this, i think sky ics was my 4th one (however the updates were constant ~everyday updates up until v17). I've only odin'd this thing a total of 4 times since i've had it, and only with either the official stock or ics leaks.
lastly, have i posted this in the correct area? I know its a SR question but since this is the first case of nand rw corruption in an SR, should i ask a mod to move it to general android QA?
mightyoj said:
Thanks vincom, i've tried full wipe, mounted under pc and format the internal, did the darkside super wipe. reboot and back to skyics, internal SD stuffed with my data, which i wiped.
I've also tried the sammobile I727UCKJ2_I727ATTKJ2_ATT tar with odin 1.85 and 1.87 and had a successful flash, yet reboot and back to skyics...., yet reboot and back to skyics. My guess is that this is hardware related to the nand flash itself, i remember reading that these things only have so many rw cycles until they are toast. whats odd about that is that this is my work phone, only had it since Feb 20, 2012, and I haven't flashed a lot of roms on this, i think sky ics was my 4th one (however the updates were constant ~everyday updates up until v17). I've only odin'd this thing a total of 4 times since i've had it, and only with either the official stock or ics leaks.
lastly, have i posted this in the correct area? I know its a SR question but since this is the first case of nand rw corruption in an SR, should i ask a mod to move it to general android QA?
Click to expand...
Click to collapse
leave it in the [email protected] section, dev's are always flashing stuff and none of them have had this issue, if they did they would of posted it.
odin is the thing thats wierd, if it encounters a prob it would shoot out an error, did odin reboot ur phone or did u manually have to do it.
does battery have full charge, do a battery pull for a few minutes, maybe even for an hour(no cable plugged in) b4 u use odin, use another usb port in the back, use another computer.
the other method is to use adb, which i dont use so cant help u there.
vincom said:
leave it in the [email protected] section, dev's are always flashing stuff and none of them have had this issue, if they did they would of posted it.
odin is the thing thats wierd, if it encounters a prob it would shoot out an error, did odin reboot ur phone or did u manually have to do it.
does battery have full charge, do a battery pull for a few minutes, maybe even for an hour(no cable plugged in) b4 u use odin, use another usb port in the back, use another computer.
the other method is to use adb, which i dont use so cant help u there.
Click to expand...
Click to collapse
odin initiates the restart, i can uncheck that box and tell it not to but i dont think it will achieve anything. maybe i can flash multipe times without a restart and it may change? i think thats the definition of insanity but at this point its worth a shot.
full charge with the device, used my work mac pro, my macbook pro, a shuttle pc i have at home, multiple usb ports, different cables, etc. I know these can cause issues but i'm familiar enough with the process that i've knocked out as many variables as i can.
i've used adb push to send the boot/recovery/rom image to the phone's sdcard and external_sd, tried using flash_image under su shell in adb but got a -1 result unsuccessfully (this i'm not familiar with as i couldn't find any documentation on flash_image)
what is constant about this problem that maybe anyone else reading this can elaborate on is that whatever you do to the boot/recovery/rom partitions, it stays UNTIL rebooted. at reboot, all changes are wiped, nothing sticks (unless written to external_sd)
mightyoj said:
odin initiates the restart, i can uncheck that box and tell it not to but i dont think it will achieve anything. maybe i can flash multipe times without a restart and it may change? i think thats the definition of insanity but at this point its worth a shot.
full charge with the device, used my work mac pro, my macbook pro, a shuttle pc i have at home, multiple usb ports, different cables, etc. I know these can cause issues but i'm familiar enough with the process that i've knocked out as many variables as i can.
i've used adb push to send the boot/recovery/rom image to the phone's sdcard and external_sd, tried using flash_image under su shell in adb but got a -1 result unsuccessfully (this i'm not familiar with as i couldn't find any documentation on flash_image)
what is constant about this problem that maybe anyone else reading this can elaborate on is that whatever you do to the boot/recovery/rom partitions, it stays UNTIL rebooted. at reboot, all changes are wiped, nothing sticks (unless written to external_sd)
Click to expand...
Click to collapse
i asked about the reboot to make sure odin was properly sending out the command to reboot, it did, but u might have an idea is to flash stock a few times b4 odin can initiate a reboot to make sure it "sticks", just never seen odin do a successful flash of stock firmware only to reboot back to a custom rom. try searching that problem in xda
edit: u cant even hardbrick your phone to get warranty repair as they would c ur custom rom, lol
I've seen this one other time. It happened to a t989. As far as i know he never got it to work again. It's in the t989 section. He may have updated his situation, i haven't checked in a while.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
just a thought did u try the kies method of flashing stock
start kies w/o plugging ur phone to usb, manually enter s/n and model all in caps under tools/initilzation, then follow onscreen instructions
---------- Post added at 02:03 PM ---------- Previous post was at 01:36 PM ----------
can u try to flash a diff recovery to c if odin flashed it, this one has a tar file u can use in odin
regular cwm touch http://forum.xda-developers.com/showthread.php?t=1566613 if u r already on this one flash sk8erwitskils cwm http://forum.xda-developers.com/showthread.php?t=1472954&highlight=sk8erwitskils and then use odin to flash back the cwm tar
vincom said:
just a thought did u try the kies method of flashing stock
start kies w/o plugging ur phone to usb, manually enter s/n and model all in caps under tools/initilzation, then follow onscreen instructions
---------- Post added at 02:03 PM ---------- Previous post was at 01:36 PM ----------
can u try to flash a diff recovery to c if odin flashed it, this one has a tar file u can use in odin
regular cwm touch http://forum.xda-developers.com/showthread.php?t=1566613 if u r already on this one flash sk8erwitskils cwm http://forum.xda-developers.com/showthread.php?t=1472954&highlight=sk8erwitskils and then use odin to flash back the cwm tar
Click to expand...
Click to collapse
I haven't tried kies on PC yet, the OSX version is missing that part, it will be my next step. I can't get either of those recoveries to stick with odin but the 5.8.1.3 touch cwm is what i've got. I'm currently trying to flash either the stock recovery or the 5.5.0.4 through adb push and dd but it also won't stick.
I'm starting to think i'm going to have to sodder a new nand flash chip on the pcb.... does anyone know if the partition structure is different from a t989 (doner device)?
xcrazydx said:
I've seen this one other time. It happened to a t989. As far as i know he never got it to work again. It's in the t989 section. He may have updated his situation, i haven't checked in a while.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I just found his last post, Corrupt sd card (internal memory) and the one before that, Broken phone.
Dang, looks like i'm not alone in this sinking boat.
mightyoj said:
I haven't tried kies on PC yet, the OSX version is missing that part, it will be my next step. I can't get either of those recoveries to stick with odin but the 5.8.1.3 touch cwm is what i've got. I'm currently trying to flash either the stock recovery or the 5.5.0.4 through adb push and dd but it also won't stick.
I'm starting to think i'm going to have to sodder a new nand flash chip on the pcb.... does anyone know if the partition structure is different from a t989 (doner device)?
Click to expand...
Click to collapse
if u can solder that, thats cool, my hats off to u
did u ever try keeping the phone dead(no battery) for a lenghty period, then using a pc, not mac to odin
try the kies method if u can, im on rogers and the kies method wont work for us, i would try to hardbrick it if u can(maybe solder some contact point) to get a replacement if all else fails
this is still the wierdest prob ive seen
vincom said:
if u can solder that, thats cool, my hats off to u
did u ever try keeping the phone dead(no battery) for a lenghty period, then using a pc, not mac to odin
try the kies method if u can, im on rogers and the kies method wont work for us, i would try to hardbrick it if u can(maybe solder some contact point) to get a replacement if all else fails
this is still the wierdest prob ive seen
Click to expand...
Click to collapse
I odin only on PC, i didn't know that was even an option on mac. I'll try to kill off the battery and try that method, its worth a shot. Currently I am downloading a stock heimdall to see if anything can be done with that.
I don't want to solder unless I have to, that would without a doubt ruin whatever chances of warranty I have and I don't want to send it in for warranty with the data on the device- as this is a work device. I have some confidential data in corp email that I cannot risk worrying about. Even shorting the flash for data destruction would kill my chances of warranty as i'd have to cause the damage myself and I couldn't send it in knowing i did that. what a catch-22 situation i've found myself in.
I'm about to try the Kies method on PC right now. What mode does the phone need to be in to do the Kies emergency recovery? I don't have the stock recovery and cannot put that on the device. My only options right now are download mode and within SkyICS
once u enter the info into kies, its tells u what to do, but i suspect it tells u to put it into dl mode and it flashes the firmware once it downloads it for ur specific phone
if ur on att, i heard they just do a str8 exchange if they can see that it wont boot
as for ur private info cant u transfer it in a pc and then delete off ur phone, or a system restore from within phone
vincom said:
once u enter the info into kies, its tells u what to do, but i suspect it tells u to put it into dl mode and it flashes the firmware once it downloads it for ur specific phone
if ur on att, i heard they just do a str8 exchange if they can see that it wont boot
as for ur private info cant u transfer it in a pc and then delete off ur phone, or a system restore from within phone
Click to expand...
Click to collapse
If i could delete it off my phone, i'd be so happy, i wouldn't still be trying to fix this right now. Even after formatting the sdcard partition on the phone through a pc, at next restart, its all back.
I just went through the Kies emergency recovery and same result, after the restart- back to SkyICS.
Heres an update for anyone experiencing this issue and finds this thread:
I gave up. The issue (to me) is akin to a USB flash drive becoming corrupt, as they similarly have limited block erase cycles.
I called AT&T and put in for a warranty exchange. They never asked if it was rooted, the closest they got was "Does it have any third party apps?" to which I answered, "heck yes." I told him truthfully about the baseband version as well as running Android 4.0.4. He said he could offer me free expedited shipping. Winning.
If something ever surfaces from my rooted Skyrocket running a custom rom, I plan to direct them at 15 USC § 2304 - FEDERAL MINIMUM STANDARDS FOR WARRANTIES under Title 15 › Chapter 50 › § 2304 Part C (which I learned about from XDA TV today) and refuse charges.
I will update this post accordingly as well.
It wasnt related to this was it:
http://forum.xda-developers.com/showthread.php?t=1386234
i agree that it seems a r/w issue, just cant understand not getting errors from odin, odin is usually picky when it cant complete an operation and displays it, and the flashing u have done is not even comparable to what the devs do, so i think u just got a lemon.
u got 137 views and no devs chimed in, dont think they ever seen this b4, i know u already waiting for a replacement but maybe u can pm sean from the dev section to c if he has any ideas, or maybe another dev from there
what reason did u give for a replacement
edit: did u try having repartition checked in odin, ive read that it is supposed to hardbrick the phone
vincom said:
i agree that it seems a r/w issue, just cant understand not getting errors from odin, odin is usually picky when it cant complete an operation and displays it, and the flashing u have done is not even comparable to what the devs do, so i think u just got a lemon.
u got 137 views and no devs chimed in, dont think they ever seen this b4, i know u already waiting for a replacement but maybe u can pm sean from the dev section to c if he has any ideas, or maybe another dev from there
what reason did u give for a replacement
edit: did u try having repartition checked in odin, ive read that it is supposed to hardbrick the phone
Click to expand...
Click to collapse
With a working phone, checking repartition will brick it and it won't reboot. But the guy with the t989 could flash anything or check anything he wanted in Odin and it would run through fine but it wouldn't change anything. It would boot back to exactly the same thing he was running before. I couldn't figure it out, it wouldn't write to the partition but i don't know why.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
With a working phone, checking repartition will brick it and it won't reboot. But the guy with the t989 could flash anything or check anything he wanted in Odin and it would run through fine but it wouldn't change anything. It would boot back to exactly the same thing he was running before. I couldn't figure it out, it wouldn't write to the partition but i don't know why.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
i know it will brick it, hes returning a phone w/a custom rom on it so if he bricks it they might not c what hes has done to it, and wont c his private emails, unless they revive it
vincom said:
i know it will brick it, hes returning a phone w/a custom rom on it so if he bricks it they might not c what hes has done to it, and wont c his private emails, unless they revive it
Click to expand...
Click to collapse
Yeah, i was just thinking he would have the same result as the other guy. Meaning it won't work, but its worth a try..
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2