Related
Hello here is a detailed description of what I did to get my phone in this state of possible brick. Sorry if this does not belong in Q&A.
-I was on GummyCharged 1.8
-I followed the guide on How to get on GummyCharged GBE 1.9RC2.3 with lagfix/EXT4. I did all the steps but in the end, ext4 was not displayed in any of the partitions. I could not enable it through Recovery (even when I pressed "enable lagfix," it still said voodoo was disabled on next boot) and through Voodoo (it did not show status of anything including rfs or ext4).
-So I redid all the steps starting from step 1. This time, everything actually worked on the first boot.
-I rebooted my phone once and the mobile data could not connect.
-I rebooted again and it still couldn't connected. I connected to wifi to see if that was a problem but there was none.
-I thought it could've been a problem with the EP1Q modem so I went to download mode and tried to Odin the EP1Q modem.
-Odin said it failed and now my phone wouldn't boot. I got this image when I tried to boot it with my battery inserted and everything (image attached)
-Now I can't get into download mode. Odin can't detect my phone unless the battery is inserted. And even if the battery is inserted, my phone displays the battery being charged and not the download mode and triangle. (image attached)
- I tried using the guide [HOW-TO]Fix your phone and used GummyCharged 1.8 and GummyCharged FE 1.9.1 full Odin in replace of ED2. Odin can detect it when I'm not in downloading mode and I get the battery charging image (image attached). I tried flashing it but it stays stuck at SetupConnection for more than 10 minutes and stays stuck at the battery image.
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GummyCharged_GBE_1.8_Full_Odin.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
I'm not sure what other way I can fix this. I was wondering if I did something wrong when I flashed the EP1Q modem. Any help is appreciated thanks!
l0lz0rss said:
Hello here is a detailed description of what I did to get my phone in this state of possible brick. Sorry if this does not belong in Q&A.
-I was on GummyCharged 1.8
-I followed the guide on How to get on GummyCharged GBE 1.9RC2.3 with lagfix/EXT4. I did all the steps but in the end, ext4 was not displayed in any of the partitions. I could not enable it through Recovery (even when I pressed "enable lagfix," it still said voodoo was disabled on next boot) and through Voodoo (it did not show status of anything including rfs or ext4).
-So I redid all the steps starting from step 1. This time, everything actually worked on the first boot.
-I rebooted my phone once and the mobile data could not connect.
-I rebooted again and it still couldn't connected. I connected to wifi to see if that was a problem but there was none.
-I thought it could've been a problem with the EP1Q modem so I went to download mode and tried to Odin the EP1Q modem.
-Odin said it failed and now my phone wouldn't boot. I got this image when I tried to boot it with my battery inserted and everything (image attached)
-Now I can't get into download mode. Odin can't detect my phone unless the battery is inserted. And even if the battery is inserted, my phone displays the battery being charged and not the download mode and triangle. (image attached)
- I tried using the guide [HOW-TO]Fix your phone and used GummyCharged 1.8 and GummyCharged FE 1.9.1 full Odin in replace of ED2. Odin can detect it when I'm not in downloading mode and I get the battery charging image (image attached). I tried flashing it but it stays stuck at SetupConnection for more than 10 minutes and stays stuck at the battery image.
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GummyCharged_GBE_1.8_Full_Odin.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
I'm not sure what other way I can fix this. I was wondering if I did something wrong when I flashed the EP1Q modem. Any help is appreciated thanks!
Click to expand...
Click to collapse
Well first of all don't use CWM to enable/disable voodoo or to check as it doesn't work/report it correctly.. Second of all I wouldn't try and flash something on to the phone if its not in download mode, that sounds like your problem right there when it comes to stalling at 'SetupConnection'. As for the failed modem flash its not a huge deal I don't think (something the phone can recover from) and I would reinstall the phone drivers, try and get into download mode and odin the EE4 stock rom package with the PIT file to completely start over
edit: oh yeah that first image is a classic soft-brick, you need to try and odin back to absolute stock and start over
Oh I did not know that meant a soft brick. I'm reinstalling the drivers right now. I'll let you know if anything happens.
edit: still not working
l0lz0rss said:
Oh I did not know that meant a soft brick. I'm reinstalling the drivers right now. I'll let you know if anything happens.
edit: still not working
Click to expand...
Click to collapse
ok maybe try a different usb port on your pc, also disable any antivirus software temporarily cuz its known to interfere with odin/phone connections... power the phone completely off, take battery out, open odin, connect phone to pc, and see if it recognizes it then put battery back in the phone and uncheck 'auto reboot' option then flash like normal
edit: also there is currently a temporary VZ network outage for all data (4G, 3G, 1x) so that may have been your problem in the first place so you didn't need to odin the modems and get these problems
I'll do some more trials and pray I get into download mode. I did not know that the network was down. It went down right when I finished flashing. That's why I thought I did something wrong.
Omg i kept powering it on and off and it finally got into download mode. I freaking love you
l0lz0rss said:
Omg i kept powering it on and off and it finally got into download mode. I freaking love you
Click to expand...
Click to collapse
nice, must've got the right combo or something lol.. its very hard to actually permabrick these phones, you just gotta keep trying
hope it gets up and running
blazing through on my 4G Droid Charge
Hi guys. I really need your help on this. I have a samsung galaxy S from T-mobile. I tried to add the arabic mode to make it read Arabic the correct format. This involved replacing the framework.jar file.
I have done that and I rebooted the phone to apply changes. Now the phone is stuck on the 1st boot window where it says "Galaxy S 4g Exclusively from T-mobile."
It keeps showing this window only. I have tried the hard reset method with the volume button but that did not work
Can you guys assist me what to do.
Sorry for opening this here since I already opened one before but dont know how to delete it there
ok guys I was able to go to samsung recovery Utils that has 4 options.
1- reboot system
2- reinstall package
3- delete all user data
4- delete cache data
I chose reinstall package and got the following message
install from SDcard...
Finding update packages...
opening update package...
verifying update package...
E:failed to open /mnt/internel_sd/update.zip (no such file or directory)
E: signature verification failed installation aborted
What should I do now
Thanks
Sure fire thing would be to get into download mode and Odin another rom.
Sent from my SGH-T959V using xda premium
Odin RaverX3X's KC1 ROM. http://forum.xda-developers.com/showthread.php?t=1129933
Put in the .pit file into PIT. REV00 into PDA. Phone into PHONE. CSC into CSC.
LEAVE ALL SETTINGS UNTOUCHED. Whatever the settings are when you put in the files are correct!
You can refer the bible and probably ODIN a recent version of Gingerbreak..
http://forum.xda-developers.com/showthread.php?t=1117554
Exodian said:
Sure fire thing would be to get into download mode and Odin another rom.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
how to get into download mode please
bkoon1218 said:
Odin RaverX3X's KC1 ROM. http://forum.xda-developers.com/showthread.php?t=1129933
Put in the .pit file into PIT. REV00 into PDA. Phone into PHONE. CSC into CSC.
LEAVE ALL SETTINGS UNTOUCHED. Whatever the settings are when you put in the files are correct!
Click to expand...
Click to collapse
Thank you for the reply. I think I got the hang of it but I got this message and it was stuck
<ID:0/022> Added!!
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> Enter CS for MD5..
<ID:0/022> Check MD5.. Do not unplug the cable..
<ID:0/022> Please wait..
<ID:0/022> Checking MD5 finished Sucessfully..
<ID:0/022> Leave CS..
<ID:0/022> Enter CS for MD5..
<ID:0/022> Check MD5.. Do not unplug the cable..
<ID:0/022> Please wait..
<ID:0/022> Checking MD5 finished Sucessfully..
<ID:0/022> Leave CS..
<ID:0/022> Enter CS for MD5..
<ID:0/022> Check MD5.. Do not unplug the cable..
<ID:0/022> Please wait..
<ID:0/022> Checking MD5 finished Sucessfully..
<ID:0/022> Leave CS..
<ID:0/022> SetupConnection..
In download mode?
Pull battery, plug in USB/power cable, while holding both volume up & down buttons, insert battery (or a form of this procedure) and up should pop the black and yellow screen that everyone loves.
Sent from my SGH-T959V using XDA App
champ1919 said:
In download mode?
Pull battery, plug in USB/power cable, while holding both volume up & down buttons, insert battery (or a form of this procedure) and up should pop the black and yellow screen that everyone loves.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
I did this and used odin but was stuck as you can see from my last post
any suggestions
A few things to try
This is likely a driver issue.
Reboot your computer then try to ODIN again. The reboot could "reset" the driver and possibly purge whatever programs may be trying to use the phone.
Are you certain you have the proper drivers installed? If you need them, check the SGS4G Bible (http://forum.xda-developers.com/showthread.php?t=1117554) and scroll down to "{USEFUL FILES}" for drivers.
Make sure other apps that may be monitoring/using that connection (like Samsung KIES). You may need to force close KIES in Task Manager.
That isn't a complete list, but a good place to start at least. After doing those things, please remove your battery, unplug your USB and go back in to download mode per champ1919's instructions above and attempt to ODIN again.
tinkererx said:
This is likely a driver issue.
Reboot your computer then try to ODIN again. The reboot could "reset" the driver and possibly purge whatever programs may be trying to use the phone.
Are you certain you have the proper drivers installed? If you need them, check the SGS4G Bible (http://forum.xda-developers.com/showthread.php?t=1117554) and scroll down to "{USEFUL FILES}" for drivers.
Make sure other apps that may be monitoring/using that connection (like Samsung KIES). You may need to force close KIES in Task Manager.
That isn't a complete list, but a good place to start at least. After doing those things, please remove your battery, unplug your USB and go back in to download mode per champ1919's instructions above and attempt to ODIN again.
Click to expand...
Click to collapse
Thank you very much for the reply. I have followed your instructions and got the drivers although I had them and I installed them. I uninstalled kies but still the same thing
an update. I have tried 2 other PCs one with win 7 32Bit, and XP 32 bit and still the same stuck on setup connection
Hmm...then I'm stumped. Perhaps more enlightened forum members can help.
Doesn't sound much like a driver issue any more, but have you tried installing PDANet on your computer? I think it uses slightly different drivers. I had tried several before one if them finally worked for me.
Update:
ok I managed to make it go to download mode but now near the end of the recovery using odin it gives me failed
It starts the download on the phone but then it reaches the end of the download and on odin shows modem and then says failed. Can anyone help
Have you tried to download the ROM again in case the download was corrupt? Also check to make sure you are putting the files in the right spot in ODIN.
In another thread, someone said that ODIN 1.85 worked more reliably than 1.7. Are you using the newer version?
Make sure you have latest Samsung drivers installed on your computer so that your computer recognizes your phone so that Odin can recognize your phone upon connection. Then try placing your USB cable into a different port also use as suggested Odin 1.85 it is a very reliable version of Odin.
Sent from my SGH-T959V using xda premium
Phone (Droid Charge) is completely unresponsive after I tried flashing to the factory ROM using Odin per this link: [ODIN][ROM][EP4D][FACTORY] Full factory restore 2.3.6 with radio - unrooted 12/7/11. (Two attempts to flash to this ROM aborted in CWM.)
When I used Odin, I got only <OSM> messages in the message box, ending with this one:
<OSM> All threads completed. (succeed 0 / failed 0)
The green status bar never appeared, and the "Start" button reactivated. I did this twice with repeatable results - nothing flashed. I then made the (apparently) huge mistake of removing the USB cable from the phone. It is now a paperweight. No response to power button, no response to plugging phone into wall outlet for charging (battery symbol doesn't appear).
Any ideas, or am I totally screwed?
My guess is that Odin never picked up your phone when you attempted to flash. Have you tried to re-enter download mode to flash again? Make sure Odin detects your device, otherwise, nothing will happen.
My experience is nothing compared to others but I had a situation similar but for some reason I ended up using the Samsung Flash program instead of Odin and after hours of screwing around it worked.
imnuts said:
My guess is that Odin never picked up your phone when you attempted to flash. Have you tried to re-enter download mode to flash again? Make sure Odin detects your device, otherwise, nothing will happen.
Click to expand...
Click to collapse
I have tried to do this. Nothing appears on the screen when I connect the phone with the volume-down button depressed.
By the way, before I flashed the ROM (or tried to) I first did the PIT thing per the following thread: [HOW-TO]Fix your phone
Additional info: here is the log of ODIN messages.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI510_VZW_EP4_ALL_ONE-LTE-CP_REV03_user_CL706183_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI510_VZW_EP4_ALL_ONE-LTE-CP_REV03_user_CL706183_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Removed!!
Did you check "re-partition" in Odin before you flash?
If your phone doesn't display logo "Samsung" then your bootloader is shot. The phone is brick for good. Only by miracle it may come back to life. Just let it rest for a day then retry....it's in coma...sorry.
buhohitr said:
Did you check "re-partition" in Odin before you flash?
Click to expand...
Click to collapse
I did that before I did the "PIT" thing. Then when flashing the ROM, I unchecked the Re-Partition box and then checked the Auto Reboot and F.Reset Time boxes as directed here. Checked only the PDA box and downloaded the ROM file to actually flash.
Look, guys, I think it's clear that I'm hosed. But don't hesitate to ask for more details so that fixes can be developed to help prevent the next guy from suffering the same fate. Rooting has been an expensive, time-wasting exercise for me, and I'd rather it not be for anyone else, if possible.
based on what you described and the logs(you did everything right), you may have communication(driver) issue between your pc and your phone which cause corruption during flashing. This is the only reason I can come up with. I did pit file and factory stock 6 or 7 times already and no issue.
buhohitr said:
based on what you described and the logs(you did everything right), you may have communication(driver) issue between your pc and your phone which cause corruption during flashing. This is the only reason I can come up with. I did pit file and factory stock 6 or 7 times already and no issue.
Click to expand...
Click to collapse
Your explanation sounds reasonable. And it sounds like the kind of unpredictable problem that could cause bricking for other people who go this route. In other words, not only does your phone need to be handled right, but things related to your main PC setup can also cause the process to go awry.
My goal here is to communicate to people that rooting is by no means "safe" or easy. Got no problem with those who wish to root, but doing so for trivial reasons like "I hate seeing all the bloatware" or "I don't like the way my screen looks" is pretty stupid IMO. In my own case, all the problems that I hoped rooting might solve (battery life; problematic Bluetooth; file backup) were not really solved by rooting - indeed, things got worse. And now I have a $700 paperweight.
The only time removing the USB cable during a flash can result in a brick is while it is flashing sbl.bin AFAIK because that is what contains the "download mode". You can usually recover it without too much trouble otherwise. I don't think that was the root cause.
Sent from my SCH-I510 using Tapatalk
MaxBuck said:
Your explanation sounds reasonable. And it sounds like the kind of unpredictable problem that could cause bricking for other people who go this route. In other words, not only does your phone need to be handled right, but things related to your main PC setup can also cause the process to go awry.
My goal here is to communicate to people that rooting is by no means "safe" or easy. Got no problem with those who wish to root, but doing so for trivial reasons like "I hate seeing all the bloatware" or "I don't like the way my screen looks" is pretty stupid IMO. In my own case, all the problems that I hoped rooting might solve (battery life; problematic Bluetooth; file backup) were not really solved by rooting - indeed, things got worse. And now I have a $700 paperweight.
Click to expand...
Click to collapse
humor me while I go through this.... First things first.. You can't get into download mode? (Using a usb port on back of pc preferable) you opened odin, took battery out f phone, held volume button and than plugged usb end into phone right?
there are a few bad pit files out there. Flashed pit file with the original froyo rom? You flashed pit file and stock froyo rom at the same time with repartition selected right?
If I read it right you flashed just the rom with repartition selected one of those times?
Sent from my SCH-I510 using xda premium
Hindle1225 said:
humor me while I go through this.... First things first.. You can't get into download mode? (Using a usb port on back of pc preferable)
Click to expand...
Click to collapse
That is correct - I can get no response whatever from my phone whether I attempt any of the following:
- going into download mode with battery removed OR installed, using the USB port directly on my computer.
- turning on the phone normally
- turning on the phone with the home button depressed
Hindle1225 said:
you opened odin, took battery out f phone, held volume button and than plugged usb end into phone right?
Click to expand...
Click to collapse
Correct.
Hindle1225 said:
there are a few bad pit files out there. Flashed pit file with the original froyo rom? You flashed pit file and stock froyo rom at the same time with repartition selected right?
Click to expand...
Click to collapse
PIT file came from here: [HOW-TO]Fix your phone
ROM installed at the outset of this process came from here: [12-14-11][ROM][EP4D] InfinityROM
ROM I was trying to flash to came from here: [ODIN][ROM][EP4D][FACTORY] Full factory restore 2.3.6 with radio - unrooted 12/7/11
Hindle1225 said:
If I read it right you flashed just the rom with repartition selected one of those times?
Click to expand...
Click to collapse
Not sure what you're asking here.
Again my knowledge is very limited but all of what you described I went through and eventually recovered. I pulled the cable out while installing. It didnt see it in Odin. Says it installed but didnt. And Im sure several other things. In my mind this thing is really hard to totally brick. I reinstalled all samsung drivers, downloaded the files again but used the Samsung Flash program to get back up.I tried different ports, cables etc.I went through the stuff you are for almost 8 hours lol before I finally got it running but it did. Cant hurt to try everything one more time. If you feel it is a paper weight then and have no recourse such as warranty sell it.Crap I might buy it cheap to waste a couple of hours(lol) just to see what I could do.
MaxBuck said:
I did that before I did the "PIT" thing. Then when flashing the ROM, I unchecked the Re-Partition box and then checked the Auto Reboot and F.Reset Time boxes as directed here. Checked only the PDA box and downloaded the ROM file to actually flash.
Click to expand...
Click to collapse
I have no idea what you're talking about with PIT thing. There is a PIT, you flash it with a ROM at the same time. You can't flash just the PIT to the phone. You have to flash a ROM at the same time. You also shouldn't need to use a PIT file when flashing 99% of the time with the Charge. As for what you can do, you can try a download mode jig, but you may want to figure out your communication issue on your computer before you try anymore flashing, and also read more and learn what you're doing before you ruin another phone.
MaxBuck said:
Not sure what you're asking here.
Click to expand...
Click to collapse
I was making sure I knew the steps you went through. If you really can't get into download mode, thats bad news.
imnuts said:
There is a PIT, you flash it with a ROM at the same time. You can't flash just the PIT to the phone. You have to flash a ROM at the same time.
Click to expand...
Click to collapse
This is what I was getting at.
Sent from my SCH-I510 using xda premium
imnuts said:
I have no idea what you're talking about with PIT thing. There is a PIT, you flash it with a ROM at the same time. You can't flash just the PIT to the phone. You have to flash a ROM at the same time. You also shouldn't need to use a PIT file when flashing 99% of the time with the Charge. As for what you can do, you can try a download mode jig, but you may want to figure out your communication issue on your computer before you try anymore flashing, and also read more and learn what you're doing before you ruin another phone.
Click to expand...
Click to collapse
Look at the steps as I outlined them above. The "How to fix your phone" thread says that once you connect to the phone via Odin, you first check ONLY the "Re-Partition" box and press the PIT button in Odin -- that's what I did, and Odin indicated successful flashing of the charge.pit file.
Then, without disconnecting the phone or doing anything else, I unchecked the Re-Partition box, and checked the Auto Reboot and F.Reset Time boxes, checked the box next to the PDA button, and then pressed the PDA button. I was using the "stock" ROM identified above. The process stalled at the message, "<ID:0/03> Completed..", with no green progress bar at the top.
I think you and buhohitr are correct in that there is a communication issue associated with the USB connection between my computer and phone. That could happen to other people also (I have no other issues when using my computer USB ports) without advance warning. Hence my caution that rooting can be dangerous, even if you follow instructions here to the letter, as I believe I did.
Oh, and don't worry -- I won't be rooting any more phones. This whole experience has been a nightmare. Your comment that I should "learn what I'm doing first" is a nice cheap shot; I read all the threads here on rooting thoroughly before I started anything with the phone, and the initial rooting and flashing went flawlessly, which suggests I read the instructions pretty carefully. BTW, I have BS and MS engineering degrees and substantial computer experience (though no Linux experience whatever, which may in part be my problem).
imnuts said:
...
2. Open up Odin, click PDA, and select the package you downloaded
3. Click on PIT and select the PIT file that you downloaded.
4. Get your phone into Download mode.
...
7. Press "Start" and flash the package.
Click to expand...
Click to collapse
It seems that step 2 is what you were confused on - while I can't speak to how others interpret this my interpretation is that there is something in both PDA and PIT before pressing start. I seem to remember something about folks that "unbricked" phones for something like $40 - mobiltech video or unbrickable mod are terms that come to mind. In the same How-To thread the above instructions are quoted from are folks mentioning such things at least.
Just get your phone unbricked for 40 bucks. then I would either get a new comp to flash with or borrow a friends comp. I suggest using spc latency checker on your comp to see if you have latency issues. Also, try a new cable. I have found that many cables don't work well.
Sent from my SCH-I510 using XDA App
MaxBuck said:
Look at the steps as I outlined them above. The "How to fix your phone" thread says that once you connect to the phone via Odin, you first check ONLY the "Re-Partition" box and press the PIT button in Odin -- that's what I did, and Odin indicated successful flashing of the charge.pit file.
Then, without disconnecting the phone or doing anything else, I unchecked the Re-Partition box, and checked the Auto Reboot and F.Reset Time boxes, checked the box next to the PDA button, and then pressed the PDA button. I was using the "stock" ROM identified above. The process stalled at the message, "<ID:0/03> Completed..", with no green progress bar at the top.
I think you and buhohitr are correct in that there is a communication issue associated with the USB connection between my computer and phone. That could happen to other people also (I have no other issues when using my computer USB ports) without advance warning. Hence my caution that rooting can be dangerous, even if you follow instructions here to the letter, as I believe I did.
Oh, and don't worry -- I won't be rooting any more phones. This whole experience has been a nightmare. Your comment that I should "learn what I'm doing first" is a nice cheap shot; I read all the threads here on rooting thoroughly before I started anything with the phone, and the initial rooting and flashing went flawlessly, which suggests I read the instructions pretty carefully. BTW, I have BS and MS engineering degrees and substantial computer experience (though no Linux experience whatever, which may in part be my problem).
Click to expand...
Click to collapse
I'm pretty sure you did it wrongly.
Like others comment, you only need press START button once, AFTER you select PIT file and ROM file (in PDA section), tick the Re-partition (and leave the other unchanged). No need to press START button twice (it seems you press it twice? based on your explanation) ...
If you still able to enter DOWNLOADING MODE, maybe better if you try to reinstall your samsung driver and maybe change the usb port used to flash, or if needed restart your computer ... and after it is detected by ODIN, do it again in the correct way ...
Hope you can unbrick your phone ...
For what it's worth, I've flashed the PIT file by itself in Odin with no problem. Completely acceptable but like was mentioned, you shouldn't really need it in most cases, even situations like this. But I wonder if somehow Odin attempted to flash sbl.bin and failed. That has the potential to hard brick the phone for sure since that file contains download mode. Does anyone know of another way to push the bootloader files to the phone?
Sent from my SCH-I510 using Tapatalk
Did you ever get this phone recovered and/or try one of those $40 programs someone mentioned? I am in the same boat it seems. =(
Hello,
I have been using this site for days now and accomplished everything I have needed to so far.
I rooted and flashed about 6 roms and found the Aeon v1.4 to be the best for me regarding my infuse 4g.
I tried to install the " Unofficial CM9 rom" for the ics look and it turned my phone into a paperweight.
Symptoms:
-Phone will not go into recovery
-will not turn on
-when attempting to turn it on, i get a barely noticable millisecond flash and then nothing.
The phone, however, will go into download mode.
I tried odin and did the repartition, pit, etc..
I tried heimdal (however its spelled) and it wont recognize drivers. (i installed drivers and they worked for odin)
I basically just want to put Aeon back on my phone and actually use my phone.. nothing else. I would appreciate any insight into the matter.
Thank you very much.
Chris.
I recently had the same problem when I tried to downgrade back to GB. I used Odin to reflash my phone using this.....http://forum.xda-developers.com/showthread.php?t=1613523.....
Thanks
omansteveo said:
I recently had the same problem when I tried to downgrade back to GB. I used Odin to reflash my phone using this.....http://forum.xda-developers.com/showthread.php?t=1613523.....
Click to expand...
Click to collapse
Thanks, ill definitely give it a whirl.. I have tried many different versions of Odin and different PIT, PDA files. Most of the time it just says:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> NewStock.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> factoryfs.rfs
and sits there... stuck for like 20 min+ (currently)... no progress bar or anything. Currently, this one is PDA .tar only. No pit or anything else with only auto-reboot and f. reset time checked.
I'll definately let you know how it worked out though, thank you!
Try other usb ports & another usb cable if possible.
Sent from my SGH-I997 using xda app-developers app
use gtg ultimate unbrick
Azrael-09 said:
Thanks, ill definitely give it a whirl.. I have tried many different versions of Odin and different PIT, PDA files. Most of the time it just says:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> NewStock.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> factoryfs.rfs
and sits there... stuck for like 20 min+ (currently)... no progress bar or anything. Currently, this one is PDA .tar only. No pit or anything else with only auto-reboot and f. reset time checked.
I'll definately let you know how it worked out though, thank you!
Click to expand...
Click to collapse
You need to go back to stock. Look for it in the software part. It is the ultimate gtg unbrick. It works flawless.
OP no need to double Post Threads of the same issue, your Thread in the General Section is no longer, utilize this thread for your issues. Thank You.
Is there an average time for Odin to pass?
andros11 said:
Try other usb ports & another usb cable if possible.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I've been trying all 3 ports and decided to just stick to the on directly connected to the motherboard. Also have been using "USB Deview" to remove usb connections in order for phone to recognize the infuse drivers i unzipped and put on the desktop. Ill try another cord as well, thank you.
kenetix said:
You need to go back to stock. Look for it in the software part. It is the ultimate gtg unbrick. It works flawless.
Click to expand...
Click to collapse
I have tried that one i beleive, but my phone was originally Froyo and "GTG's ultimate unbrick" is for Gingerbread.. (GB PIT file) (it said my phone couldnt upgrade to GB when i was unrooted). I'll Try again though, couldnt hurt. Thanks.
You should go back to stock rom via Odin
When in doubt go stock
Sent from my GT-S5360 using xda app-developers app
Azrael-09 said:
I have tried that one i beleive, but my phone was originally Froyo and "GTG's ultimate unbrick" is for Gingerbread.. (GB PIT file) (it said my phone couldnt upgrade to GB when i was unrooted). I'll Try again though, couldnt hurt. Thanks.
Click to expand...
Click to collapse
Really no way to go back to Froyo. You have to now assume GB is the beginning...
Sent from my SGH-I997 using xda premium
Going stock
An1mus said:
You should go back to stock rom via Odin
When in doubt go stock
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
I would absolutely love to flash it back stock, problem is I can find good files to drop me back to stock.. or maybe its the phone, idk. I even tried files used from the dump of someones stock phone to recreate a "stock" version. Next step is trying Gtg's Ultimate unbrick again.
I'll keep you guys updated, thanks for all your help.
I dont have enough posts to be able to put in outside links but if someone needs the GTG's_Ultimate_Unbrick.zip link, i found it. )Most of the links are broken and its a pain to find) Just PM me.
Odin update
20 min into it.
Odin shows this:
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCKD5.tar.md5 is valid.
<OSM> PHONE_UCKD5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> factoryfs.rfs
And phone is in DL mode with the blue progress bar showing about 1% since the beginning and hasnt moved. Odin isnt saying that its not responding or anything... any ideas?
If you want stock Froyo: http://forum.xda-developers.com/showthread.php?t=1629079
If you want stock GB : http://forum.xda-developers.com/showthread.php?t=1524081
Many thanks to qkster for this.
5 days and counting.. =(
Pony Express said:
If you want stock Froyo: http://forum.xda-developers.com/showthread.php?t=1629079
If you want stock GB : http://forum.xda-developers.com/showthread.php?t=1524081
Many thanks to qkster for this.
Click to expand...
Click to collapse
Thank you very much, I have tried those. This is my fifth day doing this and i cant seem to get Heimdall to work. I tried doing as much research as possible before posting a problem.
For Heimdall even though when it asks for drivers I can click on "Samsung usb composite device" and reflash but it just says "installing drivers" and loops over again.
For Odin its just not continuing to increase the progress bar or add anything new to the log screen.. Pretty confused at this point.
My phone is bricked from flashing the wrong rom. I dont mind which OS i go to because im going to end up flashing Aeon v1.4 again anyways since it looked and worked great.
Thanks for the links!
Update
[Well, i still cant get odin to get past the factoryfs.rfs ...
Phone is still only showing an 1/8 inch progress bar..
I keep trying Heimdall but no luck... i do not have file upload options in Heimdall though... is that normal?
If anyone has any other ideas, please share..
Here is a post I did for someone else, I hope it will be helpful to you.
http://forum.xda-developers.com/showpost.php?p=33215877&postcount=15
(The link I mention in post 13 is qkster's Heimdall link)
I'll get right on it. Thank you.
I think im missing some tar files... only thing in the video i can think of is that he mentions having odins tar files for some reason while using heimdall on-click.. I do have some files on my desktop > pit, phone and pda files but no other ones..
Also in the video it mentions the binary at the top of your screen in download mode. Mine says: Custom binary download: NO
Current binary: Samsung official
That normal for someone who flashed 6 roms?
On top of it all dev-host isnt downloading anything for me... click and click and nothing.
I think i just need some expert phone help, lol...
I just put mine in download and binary also says 'no'. I have lost count as to the number of roms I have flashed.
I think you are close but from my end I can't tell what is missing. I have used odin with no problem and yet my preference is Heimdall.
Maybe take some time and go through some of qkster's threads, including the link to his Heimdall tutorial. Some have found that they did not have the latest version of Java while others did not know that you have to use the same port you were using each time you use Heimdall. Others did not know that Heimdall has it's own drivers or that they should uninstall kies first.
Qkster may drop by this thread and if he has suggestions he will post. He has forgotten more about the Infuse than I know.
I installed then uninstalled Kies
I do have the latest version of Java.
I downloaded a binary version of Heimdall for the Zadig driver file so that i can manually put in the samsung driver before opening the one click Heimdall
I have followed tutorials to the letter so much that when i watched the video it seemed like I was knowledgeably far beyond the video's tutorial.
Im am however, unsure what you mean by using the same port (please keep in mind that im on the computer trying to fix my phone about 45 min out of every hour for about 8 hours a day for the past 5 days)... I actually had to erase all the zip files and tar files and such just to re-grasp where i was at because my desktop was overloaded...
Oh and i read a thread about bricking your phone (good read) and i think i screwed it up somewhere in the bootloaders... its not enough to hard brick it since i can still go into DL mode but something is definately wrong.
I do appreciate your advice and concern. Thank you again.
Hopefully we can come to a conclusion soon and i can pass on my knowledge...
Pony Express said:
Qkster may drop by this thread and if he has suggestions he will post. He has forgotten more about the Infuse than I know.
Click to expand...
Click to collapse
Thanks for the vote of confidence, Pony. I'm not very good at getting the drivers installed.
What you noted is all that I can recommend.
Update java. Install Samsung USB device. Install Zadig from Heimdall. Sometimes it take a reboot or two with the PC. Other times, it takes a different PC altogether. It may also work by moving the USB cord to a different usb port.
It has been almost a year since I tried Odin. No help there.
I can tell you that after you get the heimdall to work, save that cord and that usb port only for heimdall and don't install Odin over it.
With all the heimdall-1-click packages available, there are many options to restore from soft brick or return to stock.
jscott30 made a bunch of Odin packages as well if Heimdall is not working for that person.
Perseverance is the key. We have all been there. I can tell you that the more mistakes you make, the more you will learn.
Hello,
I came here to look for help. I have a Verizon Samsung Galaxy s3. I rooted my phone and had CM10.2 on my phone.
I used casual to root phone/unlock boot loader and everything.
I decided I wanted to put CM11 on my phone. I downloaded everything from CM site for my phone. I made sure it was for my phone. I have TWRP recovery on the phone. put on debugging and everything.
I went into TWRP and started the process of putting CM11 on the phone. I made a nandroid back up in TWRP. I did a wipe data/factory reset.Once did all this, I went into install and installed zip file from my external sd-card. I believe it said failed, but i don't remember the exact thing that happened or the message I got. I know that doesn't help, but I am going to try and type everything I have done. Once that happened, I think i stupidly went to reboot and it said about super user rights needing to be fixed. I think i pushed fix. I know i probably did a big mistake there. The phone started to reboot.
When the phone is rebooting what happened was it would got to samsung galaxy logo and then CM logo. It would then immediately reboot. It just kept going through this cycle. So i tried to boot into recovery. It starts to attempt to boot in recovery. TWRP logo starts popping up. Boom it reboots again. So i can't get into recovery mode.
So i started to read around about my problem. I found articles saying about using odin to correct this boot loop (soft brick i think from what I read). I started to follow this article: http://forum.xda-developers.com/showthread.php?t=1840030
When I followed that article I got steps one through six done with odin saying pass. I start to do step 7. I actually tried to do step 7 twice. I got fails both times. I don't have the results form the first time. I downloaded the root66 tar file from somewhere else. I don't remember. When I got the failure, I pulled the root66 tar file i found here: http://forum.xda-developers.com/showthread.php?t=1984436 I used the main on on there. I go through and it fails: Here is the log from it.
<ID:0/005> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> root66_VZW_I535VRBMB1.tar.md5 is valid. <OSM> Checking MD5 finished Sucessfully.. <OSM> Leave CS.. <ID:0/005> Odin v.3 engine (ID:5).. <ID:0/005> File analysis.. <ID:0/005> SetupConnection.. <ID:0/005> Initialzation.. <ID:0/005> Erase... <ID:0/005> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1)
I am completely stuck on what to do at this point. I am growing tired of trying stuff and I am completely stuck. I have tried to look around, but no luck.
Have you tried Odin flashing the VRBMF1 4.1.2 stock image? You would need to root and unlock your bootloader afterwards. This file formats /sdcard as well.
I'm downloading the image right now. I will try and use it and see what happens. I'll get back to you as soon as it downloads and I run odin again.
thunderisraw said:
I'm downloading the image right now. I will try and use it and see what happens. I'll get back to you as soon as it downloads and I run odin again.
Click to expand...
Click to collapse
Cool, just do not accept the 4.3 OTA if this flashes fine and boots up for you
SlimSnoopOS said:
Cool, just do not accept the 4.3 OTA if this flashes fine and boots up for you
Click to expand...
Click to collapse
Okay i got odin to work. I got it flashed on there. thank you so much! Now i just got to unlock the bootloader again. Which I'll do real fast with casual. Thank you again for being so fast to respond!
thunderisraw said:
Okay i got odin to work. I got it flashed on there. thank you so much! Now i just got to unlock the bootloader again. Which I'll do real fast with casual. Thank you again for being so fast to respond!
Click to expand...
Click to collapse
Great! You'll have CM11 installed in no time :thumbup:
Sent from my SCH-I535 using Tapatalk 4