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
Related
I'm trying to flash my friend's Galaxy s 4g, but I'm having an issue with Odin failing to flash.
I originally used Vibrant 3g .pit and .tar files, not knowing it wouldn't work on the 4g model. Anyway, that semi bricked it, while still allowing it to get to the download mode.
So I figured I needed the "custom" .tar file to flash the 4g model. I booted up Odin and opened just the .tar that's in the noob guide. This time all I got from Odin is a red panel saying FAIL! It happened during the cache.rfs process. And now I get a new download mode screen. Before it used to be the android digging, now it's just an image of a phone and a computer with an exclamation mark in between the two.
When I get FAIL! on Odin, the progress bar on the phone freezes about 75% of the way.
So what am I doing wrong? Do I need a .pit file? Is it my computer? Should I try another computer? help me out please
I'm not sure about that second message you got, but did you make sure to open ODIN before flashing?
And do you also have the correct USB Drivers downloaded for your computer?
bustanut said:
I'm not sure about that second message you got, but did you make sure to open ODIN before flashing?
And do you also have the correct USB Drivers downloaded for your computer?
Click to expand...
Click to collapse
Yea, i had ODIN open before I connected the phone. And I made sure to install the correct drivers for it (It said "drivers installed successfully)
Another thing, is when I was trying to flash it thinking the regular vibrant 3g method would work, I had "Re-Partition" checked. Could that be part of the problem?
You're not supposed to have Re-Partition checked.
Refer to this guide to make sure you're doing everything right in the flashing process : http://forum.xda-developers.com/showthread.php?t=1001759
Well, I have been following that guide. Step by step.
But that was after I semibricked it.
Before, I thought using the method for rooting a vibrant 3g would work for the 4g model. I guess the "Re-partition" box was checked (before I started following that "Noobs guide") and that's why I'm having problems now.
The symbol you are now seeing on your phone means you have a currupt firmware. It was most likely caused by using the vibrants pit file. If you try everything else and it still doesn't work. You may have to wait until we either have a working pit. But follow the directions on the Odin flashing instruction and keep trying.
Good luck
Sent from my GT-I9000 using XDA Premium App
So, there's nothing I can do now besides keep trying? It's not my phone though... my friend was expecting it back today.
Is there a way I can get to the recovery menu and download somebody's nandroid backup to restore mine?
bryanoid said:
So, there's nothing I can do now besides keep trying? It's not my phone though... my friend was expecting it back today.
Is there a way I can get to the recovery menu and download somebody's nandroid backup to restore mine?
Click to expand...
Click to collapse
Sorry bud. Cwm doesn't work that way yet. And even so, I don't think you can even get into recovery mode with your problem. When you used the vibrant pit file you formatted the phone to be like the vibrant which its not. Its very similar, but different enough to cause issues.
Sent from my GT-I9000 using XDA Premium App
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 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:
THIS IS A SUCCESS STORY SO IF YOU STUMBLED HERE READ IT OVER...WORKED FOR ME ON MY MAC!!!
OK, I've been reading threads all afternoon/evening and can't find anything that solves my situation.
I'm stuck booting into CWM no matter what I do at this point.
How I got here:
Started unadulterated stock ROM.
Ran AdamOutler's Heimdall One-Click Defuse 1.5 kernel to get root/CWM (Mac user).
Installed Superuser, Tibu, etc...
Flashed Zues 5.1 and Aries.
Enjoyed devine bliss for a few days until enticed by Zues 5.2
Ran AdamOutler's Heimdall back to stock.
Wouldn't boot so flashed again with boot loaders (per instructions).
Flash failed, couldn't get anywhere but download.
Flashed Defused 1.5 kernel again an got CWM back.
Went in circles for a while.
Present situation:
Can only boot to download and CWM.
Can't restore from CWM (did back up previous to problems but won't work).
Flash from CWM seems to work until reboot, then I'm just back in CWM.
Heimdall flashes appear to work until reboot (pretty much like CWM depending on what I flash).
Heimdall flashes with bootloaders just continue to fail part way through.
Is there anyone that can help me out of this?
Again...I have a Mac and no PC.
I would truly appreciate any help anyone can offer.
Perhaps somebody here knows something about Heimdall flashing fine the first time but failing to flash with bootloaders?
Anybody ever experience this on a Mac or a PC?
i would use gtgs to get back to stock ..
http://forum.xda-developers.com/showthread.php?t=1116251
i was there too!! good luck!!
where are you getting stuck when you try adams?
remember to try a different usb cable even if you think you cable is problem free..also try different usb port, i do not have a mac but i dont see why mac users would be excluded from these issues..
did you try to redownload the uckj4 package ? is there space on the hard drive?
try to install the heimdall frontend and extract the unbrick .tar.md5 file and load the files into the heimdall flash tab...
add bootloaders from my bootloaders thread. that is if the links still work... and if it all fails try a new cable and then try with repartition selected.
mejori said:
i would use gtgs to get back to stock ..
http://forum.xda-developers.com/showthread.php?t=1116251
i was there too!! good luck!!
where are you getting stuck when you try adams?
remember to try a different usb cable even if you think you cable is problem free..also try different usb port, i do not have a mac but i dont see why mac users would be excluded from these issues..
Click to expand...
Click to collapse
Thanks for the reply. First flash (without BLs) seems to go fine but can't boot (sort of). Second flash (with BLs) won't even finish. The error has something to do with the PIT. More details if you like later (at work now). I have sucessfully flash with this port and cable but I guess I'll give it a go switching them up.
DozenMadder said:
Thanks for the reply. First flash (without BLs) seems to go fine but can't boot (sort of). Second flash (with BLs) won't even finish. The error has something to do with the PIT. More details if you like later (at work now). I have sucessfully flash with this port and cable but I guess I'll give it a go switching them up.
Click to expand...
Click to collapse
are you using gtgs infuse.pit?
Dani897 said:
did you try to redownload the uckj4 package ? is there space on the hard drive?
try to install the heimdall frontend and extract the unbrick .tar.md5 file and load the files into the heimdall flash tab...
add bootloaders from my bootloaders thread. that is if the links still work... and if it all fails try a new cable and then try with repartition selected.
Click to expand...
Click to collapse
I did try redownloading exact same symptoms.
I've have the front end installed. I'll search for the uckj4 package when I get home. Thanks a lot for the instructions (I'm pretty new at all this).
DozenMadder said:
Thanks for the reply. First flash (without BLs) seems to go fine but can't boot (sort of). Second flash (with BLs) won't even finish. The error has something to do with the PIT. More details if you like later (at work now). I have sucessfully flash with this port and cable but I guess I'll give it a go switching them up.
Click to expand...
Click to collapse
yea same thing happened with me..i switched cables and port ...worked like a champ!!!
remember to take your time.. i freak out every time i brick my phone and then go back and see that i rused and missed some dumb **** ...lol
Dani897 said:
are you using gtgs infuse.pit?
Click to expand...
Click to collapse
I have tried that one and AdamOutlers one that you can get to from the Super Thread also. Both fail on the bootloaders.
edit-
The gtgs I tried was in a package so I didn't really try it on its own.
AdamOutler's One-Click is obviouslly part of a complete package as well.
Gtgs fail at PIT (I think) but anyway failed overall for sure.
mejori said:
yea same thing happened with me..i switched cables and port ...worked like a champ!!!
Click to expand...
Click to collapse
Very encouraging. Thank you!
DozenMadder said:
I did try redownloading exact same symptoms.
I've have the front end installed. I'll search for the uckj4 package when I get home. Thanks a lot for the instructions (I'm pretty new at all this).
Click to expand...
Click to collapse
If you need a PIT file for heimdall frontend, you can pull it from the uckj4 package
I really appreciate the help ya'll are offering up.
Can't stay at work all day, though, so I'm hittin' the road.
Maybe catch back up with ya'll in an hour or so.
When I get this fixed I'm gonna put my phone away for an entire day and just drink beer, play guitar, and make my kids psyched that I'm their dad! Probably not in that order though
Dani897 said:
did you try to redownload the uckj4 package ? is there space on the hard drive?
try to install the heimdall frontend and extract the unbrick .tar.md5 file and load the files into the heimdall flash tab...
add bootloaders from my bootloaders thread. that is if the links still work... and if it all fails try a new cable and then try with repartition selected.
Click to expand...
Click to collapse
Alright here I go!
Heimdall Frontend is open.
gtgbacktostockheimdall is extracted.
gtgbacktostockheimdall/infuse.pit is in the PIT box.
Repartition is not checked for this try.
I have bootloaders from dani's thread: boot.bin and Sbl.bin
Got those entered.
I'm in the process of matching up all the files and browsing to them.
When I'm done I'm going to pull the trigger on this.
Sound right? Any objections? Sure feel nervous...
If anyone's reading this and thinks something doesn't sound right, please let me know.
Anyone think it all sounds good, feel free to cheer me on...
I'm supposed to have that PIT file in there, right?
DozenMadder said:
Alright here I go!
Heimdall Frontend is open.
gtgbacktostockheimdall is extracted.
gtgbacktostockheimdall/infuse.pit is in the PIT box.
Repartition is not checked for this try.
I have bootloaders from dani's thread: boot.bin and Sbl.bin
Got those entered.
I'm in the process of matching up all the files and browsing to them.
When I'm done I'm going to pull the trigger on this.
Sound right? Any objections? Sure feel nervous...
If anyone's reading this and thinks something doesn't sound right, please let me know.
Anyone think it all sounds good, feel free to cheer me on...
I'm supposed to have that PIT file in there, right?
Click to expand...
Click to collapse
Yeah that all sounds right. Yes, I think it's PIT that reformats all of your partitions.. not positive though.
PS.. next time.. buy a PC.
Holding off for the moment.
I have a few left over pieces that don't seem to match up quite right.
In the extracted heimdall package I have zlmage and zlmage-1
In the Heimdall Flash tab I have Kernel, Recovery, EFS, and SBL2
My searching suggests that zlmage goes with Kernel.
My intuition tels me that zlmage-1 must be Recovery.
Think I'll just set those up that way.
That leaves EFS and SBL2...
Is it OK to leave those blank?
I've double checked all the other pairings.
Feel like a kid jumping off the cliff into the lake for the first time.
Please, some one who knows what they're doing...push me.
(Or just say, "All sounds good to me, DO IT MAN!!!)
(Or scream, "STOP!!! You don't have the SBL2?!! Are you nuts? Go and find it.)
Erik_T said:
Yeah that all sounds right. Yes, I think it's PIT that reformats all of your partitions.. not positive though.
PS.. next time.. buy a PC.
Click to expand...
Click to collapse
Right on about the PC.
I had no working computer until I inherited this one from my step mom.
DozenMadder said:
Holding off for the moment.
I have a few left over pieces that don't seem to match up quite right.
In the extracted heimdall package I have zlmage and zlmage-1
In the Heimdall Flash tab I have Kernel, Recovery, EFS, and SBL2
My searching suggests that zlmage goes with Kernel.
My intuition tels me that zlmage-1 must be Recovery.
Think I'll just set those up that way.
That leaves EFS and SBL2...
Is it OK to leave those blank?
I've double checked all the other pairings.
Feel like a kid jumping off the cliff into the lake for the first time.
Please, some one who knows what they're doing...push me.
(Or just say, "All sounds good to me, DO IT MAN!!!)
(Or scream, "STOP!!! You don't have the SBL2?!! Are you nuts? Go and find it.)
Click to expand...
Click to collapse
(Or say, dude, you really need to find that EFS file and get it in there).
Searching turns up no results for zlmage-1
Don't want to proceed until I know for sure that I've got this stuff right.
Perhaps I shouldn't be flashing the recovery partition.
Then again, I seem to remember that CWM kept telling me that recovery couln't be mounted. Probably I do need to flash something over it.
But I've heard all about the dangers of flashing the wrong thing to the wrong place.
Dude just do it. Yes i am meaning to yell at you. Seriously... It's sooooooooooo damn hard to brick this thing! It has the unbrickable mod...
Edit: Boo.. I typed that all in caps.
OMG all that agonizing before I clicked start.
All it did was immediately say "flash completed sucessfully!"
But it didn't do a damn thing!!!
I got heimdall to work before.
Guess I try closing it and setting things back up again.
Looks like I've soft-bricked my S3 and cannot get it back working at all.
When you power it on, it shows the yellow triangle and "Firmware Upgrade encountered an issue. Please use software repair assistant and try again."
I can get into download mode but nothing flashes through. I've tried ML1, MF1, the VRALEC bootchain method, including the PIT file, everything. Odin just won't complete any of the flashes. On some it hangs on Initializing (and I've tried all USB ports, different cables, and two laptops), on others it hangs on nand write partition. I even tried the trick where I add the PIT file but unselect Re-Partition. Nada. Oh, and I tried the actual verizon repair assistand and at 83% it says "phone was disconnected, please reconnect and try again."
Here's what the download mode screen looks like if that helps anyone http://i.imgur.com/zpNGAy4.jpg
Help please? I would really appreciate it.
What did you exactly do that brought you to this state?
thebballkid said:
Looks like I've soft-bricked my S3 and cannot get it back working at all.
When you power it on, it shows the yellow triangle and "Firmware Upgrade encountered an issue. Please use software repair assistant and try again."
I can get into download mode but nothing flashes through. I've tried ML1, MF1, the VRALEC bootchain method, including the PIT file, everything. Odin just won't complete any of the flashes. On some it hangs on Initializing (and I've tried all USB ports, different cables, and two laptops), on others it hangs on nand write partition. I even tried the trick where I add the PIT file but unselect Re-Partition. Nada. Oh, and I tried the actual verizon repair assistand and at 83% it says "phone was disconnected, please reconnect and try again."
Here's what the download mode screen looks like if that helps anyone http://i.imgur.com/zpNGAy4.jpg
Help please? I would really appreciate it.
Click to expand...
Click to collapse
Are you brick with 4.3?
I'm having the same problem (stock rooted 4.3). I flashed clockworkmod via ROM manager and when I went to boot into recovery... yellow triangle of death. I too have tried Odin back to stock, but everything fails. Trying Odin from the triangle screen right now. Seems to be hanging on "SetupConnection".
Update: Failed.
jpmi23 said:
I'm having the same problem (stock rooted 4.3). I flashed clockworkmod via ROM manager and when I went to boot into recovery... yellow triangle of death. I too have tried Odin back to stock, but everything fails. Trying Odin from the triangle screen right now. Seems to be hanging on "SetupConnection".
Update: Failed.
Click to expand...
Click to collapse
If you took the 4.3 OTA you will be unable to flash a custom recovery. This very helpful thread created by @BadUsername will get you back up and running:
http://forum.xda-developers.com/showthread.php?t=2639337
Looks like that's working! Thanks man!
buhohitr said:
Are you brick with 4.3?
Click to expand...
Click to collapse
I think so? I tried going back to stock from being rooted and on CM and I'm actually not positive if I'm on 4.3 now or not since the flash never succeeded. I may have had the wrong bootloader when trying to flash 4.3.
Any ideas?
BattsNotIncld said:
What did you exactly do that brought you to this state?
Click to expand...
Click to collapse
Great question. I was rooted and on CM 10.2 when the phone started shutting down randomly. Reinstalled everything CM-related and it was still happening. I then used TriangleAway to reset root counter which worked flawlessly. Tried putting on a stock rom (the latest off of sammobile I believe 4.3), when the flash failed and then I got where I am now. Maybe I had the wrong bootloader for 4.3? Throughout my research I kept leaning towards this being the case similar to many that flashed OTA 4.3 and got a brick, but all the solutions for that haven't worked for me
thebballkid said:
Great question. I was rooted and on CM 10.2 when the phone started shutting down randomly. Reinstalled everything CM-related and it was still happening. I then used TriangleAway to reset root counter which worked flawlessly. Tried putting on a stock rom (the latest off of sammobile I believe 4.3), when the flash failed and then I got where I am now. Maybe I had the wrong bootloader for 4.3? Throughout my research I kept leaning towards this being the case similar to many that flashed OTA 4.3 and got a brick, but all the solutions for that haven't worked for me
Click to expand...
Click to collapse
You can tell which bootloader you are on from download mode. Use this thread it has all the info you need including how to fix it:
http://forum.xda-developers.com/showthread.php?t=2639337
Unless you've tried all those methods already? I think specifically this is the method you should try:
http://forum.xda-developers.com/showthread.php?t=2586319
BattsNotIncld said:
You can tell which bootloader you are on from download mode. Use this thread it has all the info you need including how to fix it:
http://forum.xda-developers.com/showthread.php?t=2639337
Unless you've tried all those methods already? I think specifically this is the method you should try:
http://forum.xda-developers.com/showthread.php?t=2586319
Click to expand...
Click to collapse
Thanks, at least I've confirmed I'm on the 4.3 baseband. However, I tried the guide on there and the guide you provided and am still unable to get past the "Initialzation" step in Odin. Any ideas?
thebballkid said:
Thanks, at least I've confirmed I'm on the 4.3 baseband. However, I tried the guide on there and the guide you provided and am still unable to get past the "Initialzation" step in Odin. Any ideas?
Click to expand...
Click to collapse
You're using Odin right?
Try to flash it with the pit file. If that doesn't work then try to use the Verizon utility. That thread should work if you follow those directions perfectly, at least I haven't heard of it not working yet.
Sent from my SCH-I535 using Tapatalk 2
thebballkid said:
Thanks, at least I've confirmed I'm on the 4.3 baseband. However, I tried the guide on there and the guide you provided and am still unable to get past the "Initialzation" step in Odin. Any ideas?
Click to expand...
Click to collapse
Hmm. Well at this point I would suggest you make sure you're using a quality USB cable and make sure you use the USB port right on the motherboard. But it looks like you already tried all that. What version of ODIN are you using?
Sent from my SCH-I535 using Tapatalk
BadUsername said:
You're using Odin right?
Try to flash it with the pit file. If that doesn't work then try to use the Verizon utility. That thread should work if you follow those directions perfectly, at least I haven't heard of it not working yet.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Hey thanks for chiming in, really appreciated your guide. I followed everything to the T and had no luck. Tried both Odin 3.07 (PDA) and 3.09 (AP) and your method kept getting stuck at Initialzation in Odin. I tried the PIT file on both too, same thing. Tried the Verizon Utility and at 83% it says "phone is disconnected, lease reconnect and try again."
I will say this: when it gets stuck on Initialzation and I unplug the phone, Odin says "PIT file not found." Not sure if that means anything since the phone is unplugged but only other info I can think to share.
Got any other ideas? Would hate to be the first one that couldn't be helped by your directions. Thanks anyways!
BattsNotIncld said:
Hmm. Well at this point I would suggest you make sure you're using a quality USB cable and make sure you use the USB port right on the motherboard. But it looks like you already tried all that. What version of ODIN are you using?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I have tried, been using two official Samsung USB cables that came with the phone and my Nexus 10. I'm working on two laptops and tried all of the different ports getting the same result, Odin hangs on Initialzation.
I tried using both Odin 3.07 (PDA) and 3.09 (AP).
Any other ideas? Thanks!
thebballkid said:
Hey thanks for chiming in, really appreciated your guide. I followed everything to the T and had no luck. Tried both Odin 3.07 (PDA) and 3.09 (AP) and your method kept getting stuck at Initialzation in Odin. I tried the PIT file on both too, same thing. Tried the Verizon Utility and at 83% it says "phone is disconnected, lease reconnect and try again."
I will say this: when it gets stuck on Initialzation and I unplug the phone, Odin says "PIT file not found." Not sure if that means anything since the phone is unplugged but only other info I can think to share.
Got any other ideas? Would hate to be the first one that couldn't be helped by your directions. Thanks anyways!
Click to expand...
Click to collapse
I didn't write the softbrick guide, @ThePagel deserves that credit. I just made a sticky thread to have everything in one place.
I think you followed everything perfectly and did all that you could, you've read around a lot and tried everything you found. My guess is somehow your system partition is in a read only state and simply isn't letting anything write to it. That would explain what is happening.
What I would do is treat this as a hard brick. I would do one of 3 things:
1) try to hardbrick the phone yourself, maybe run the old version of casual and flash the insecure aboot file to unlock the phone, this obviously will corrupt the 4.3 bootloader and hardbrick the phone. Then you could use the hardbrick restore guide to fix it that way.
2) or you could send it in "as is" for jtag that will write the bootchain for you and most likely fix the problem.
3) try to use the methods in this thread but use all the 4.3 files. If you could somehow get this to work you should write a guide for it and I'll post it in the sticky. I think you have enough know how to attempt it.
http://forum.xda-developers.com/showthread.php?t=1840030
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I didn't write the softbrick guide, @ThePagel deserves that credit. I just made a sticky thread to have everything in one place.
I think you followed everything perfectly and did all that you could, you've read around a lot and tried everything you found. My guess is somehow your system partition is in a read only state and simply isn't letting anything write to it. That would explain what is happening.
What I would do is treat this as a hard brick. I would do one of 3 things:
1) try to hardbrick the phone yourself, maybe run the old version of casual and flash the insecure aboot file to unlock the phone, this obviously will corrupt the 4.3 bootloader and hardbrick the phone. Then you could use the hardbrick restore guide to fix it that way.
2) or you could send it in "as is" for jtag that will write the bootchain for you and most likely fix the problem.
3) try to use the methods in this thread but use all the 4.3 files. If you could somehow get this to work you should write a guide for it and I'll post it in the sticky. I think you have enough know how to attempt it.
http://forum.xda-developers.com/showthread.php?t=1840030
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I tried the method you posted under 3) and Odin is still stuck on Initialzation
As for hard bricking it myself, it does look like that's my only choice now since booting into download mode does nothing for me since I can't flash anything. When you talk about the insecure aboot file from casual, can you please be more specific? I looked at the casual thread (http://forum.xda-developers.com/showthread.php?t=2332825) and in the jar file I downloaded, there's a Scripts folder, under which there's a d2vzw toolkit zip file, in which there's a aboot.mbn file. Is this what you were referring to?
If I can avoid JTAG I would prefer that. Guess my next goal is to hard brick then try the write to SD Card and boot method.
thebballkid said:
I tried the method you posted under 3) and Odin is still stuck on Initialzation
As for hard bricking it myself, it does look like that's my only choice now since booting into download mode does nothing for me since I can't flash anything. When you talk about the insecure aboot file from casual, can you please be more specific? I looked at the casual thread (http://forum.xda-developers.com/showthread.php?t=2332825) and in the jar file I downloaded, there's a Scripts folder, under which there's a d2vzw toolkit zip file, in which there's a aboot.mbn file. Is this what you were referring to?
If I can avoid JTAG I would prefer that. Guess my next goal is to hard brick then try the write to SD Card and boot method.
Click to expand...
Click to collapse
Just make sure you have all the equipment for a hard brick restore first.
There's an old version of casual, not the most recent one, it's on the thread. It has an option to unlock the device. I'm not sure it will work in this circumstance, but if you can get it to recognize your phone you should be able to select that option only.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Just make sure you have all the equipment for a hard brick restore first.
There's an old version of casual, not the most recent one, it's on the thread. It has an option to unlock the device. I'm not sure it will work in this circumstance, but if you can get it to recognize your phone you should be able to select that option only.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Casual won't recognize the phone
I tried flashing a GSM radio and it hung on initialzation again. Am I somehow stuck between a soft and hard brick now?
thebballkid said:
Casual won't recognize the phone
I tried flashing a GSM radio and it hung on initialzation again. Am I somehow stuck between a soft and hard brick now?
Click to expand...
Click to collapse
Man you have a tough situation.
I'd just get it a jtag repair. It'll start you clean and you can start over. I can't think of anyway to force download mode to write something to your phone.
That other guide is your exact symptom, but we don't have a way to fix a read only state on a 4.3 system.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
thebballkid said:
Casual won't recognize the phone
I tried flashing a GSM radio and it hung on initialzation again. Am I somehow stuck between a soft and hard brick now?
Click to expand...
Click to collapse
Technically you're softbricked in a read only state.
Sent from my SCH-I535 using Tapatalk 2
NEED HELP
I have the same problem as the OP. Nothing will work. Any ideas? :/. I have tried absolutely everything