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
Related
So I was messing with that CWM "FIX" and I was able to get back to stock using Odin and the T959VKB5-Custom file.
After messing with doing the supposed fix I decided to try to use the PIT file that troby1986 reposted what krylon360 posted on the Vibrant forum. The PIT file was named "Hawk_Sidekick_VibrantPlus_831.pit"
After running Odin with both files and Odin saying it was successful, the phone rebooted and then the Galaxy S 4G bootup screen came up but then went straight back to system recovery. I tried several times trying to use Odin with and without the PIT file and keeping the TAR/PDA file the same. I would always get the same result. It would reboot and show the Galaxy S 4G screen then straight to system recovery.
Did anyone else get into this loop and was able to recover? Also my external SD card was wiped out. If I can't get this fixed I'll try to go into a tmobile store and try to get it replaced.
Also can someone load up a zip file of what's in the SD card stock minus the movie?
yes i did the samething and got exactly what u have now hope we get some help with this
Beefvvl said:
So I was messing with that CWM "FIX" and I was able to get back to stock using Odin and the T959VKB5-Custom file.
After messing with doing the supposed fix I decided to try to use the PIT file that troby1986 reposted what krylon360 posted on the Vibrant forum. The PIT file was named "Hawk_Sidekick_VibrantPlus_831.pit"
After running Odin with both files and Odin saying it was successful, the phone rebooted and then the Galaxy S 4G bootup screen came up but then went straight back to system recovery. I tried several times trying to use Odin with and without the PIT file and keeping the TAR/PDA file the same. I would always get the same result. It would reboot and show the Galaxy S 4G screen then straight to system recovery.
Did anyone else get into this loop and was able to recover? Also my external SD card was wiped out. If I can't get this fixed I'll try to go into a tmobile store and try to get it replaced.
Also can someone load up a zip file of what's in the SD card stock minus the movie?
Click to expand...
Click to collapse
From what I've read, that pit file is not for the SGS 4G its for the 3G. They have different Partition structors. The only thing you change in oden is putting the Tar file in PDA and press start after your phone is in download mode. And sorry, I can't tell you the solution.
nwpro3 said:
From what I've read, that pit file is not for the SGS 4G its for the 3G. They have different Partition structors. The only thing you change in oden is putting the Tar file in PDA and press start after your phone is in download mode. And sorry, I can't tell you the solution.
Click to expand...
Click to collapse
I dunno. Accord to him it is the correct one but he say maybe it was corrupt download that he loaded or it may be a wrong partition. I know for the regular vibrant it's 512. Maybe 803 also. We won't find out till we get the real one. But I'm not going to try and experiment on a pit till someone else does and verify's it...lol. I ended up exchanging mine at the store since it hasn't been 30 days yet. Anyone having issues and it hasn't been 30 days should be able to exchange their phone for a new one at the Tmobile stores.
I did the same thing. Is anyone working on putting together a PIT for this phone that works? I'd be happy to get my donation on if someone were able to help me get unbricked.
Initially, this post was meant to fix people's phones after a bad restore from CWM, but now I'm changing it to be more general and pretty much be a guide for how to fix your phone from nearly any problem. The original reason for this post is this error:
Code:
-- bootmode=7 from cmdline...
-- Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
--Movi_check already executed!!...
--movi_checking done!...
# MANUAL MODE #
It was caused by a problem with /data and this guide helped fix that. Now that several other things have come along (leaks, voodoo, etc.) people are having a host of random errors show up with their phones. This guide will hopefully get you back to a working phone regardless of what is wrong with it. Take note though, that following this guide will delete all data not on the sdcard. So, with that being said, here is how you can fix your phone.
1. Download one of the packages below as well as the PIT file.
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.
4a. Pull out the battery, hold down on Vol Down, and plug in the USB Cable while still holding the button.
4b. After you are in Download Mode, put the battery back into your phone. This increases the reliability of flashing with Odin
5. Make sure your phone is recognized in Odin
6. Check the box for Re-partition (Odin will fail if you check this and don't use the PIT file) and un-check the boxes for Auto-Reset and F. Reset Time.
7. Press "Start" and flash the package.
8. After it is finished flashing, take the battery out, unplug the USB cable, put the battery back in, and start up what should now be a working phone.
Download descriptions. There are 3 files linked to below. The first is the PIT file, and required for this. The PIT file is the partition information table. It tells your phone where different packages go on the phone, as well as how big partitions are on the phone. Without this information, Odin cannot properly re-partition your device. The next two files are more or less the same and you will only need one of the two, not both (unless you want them just for fun). There is ED1, which is what the phone initially shipped with, and ED2, the update that was released just after the phone was. The ED1 package may be a little bit smaller for those that are concerned about download size as it is compressed. However, you will need 7-zip or similar to extract it after downloading. Also note that this cannot be done with Heimdall as Heimdall does not have the ability to re-partition your phone, thus, you need a Windows computer to be able to follow this procedure.
All packages are available here.
Sweet, as always thanks for the work/effort on this stuff. At least now we don't have to be AS concerned atm if a restore was done in CWR and someone hoses there device.
this work for anyone?
Updated this with what I believe to be the proper steps. I was in and out at work while papi was fixing his phone, and lost track of the exact files used, but some combination of the above Odin packages and the PIT should get you back to a working phone if you are having a problem.
Good sh|t man ... phone was bound to have growing pains.
papi92 said:
this work for anyone?
Click to expand...
Click to collapse
Unfortunately, I am trying to fix this very problem right now.
I was able to get rid of the error message with your method and I can now get into CWM again.. which is progress. I used the smaller file as it looks like the bigger one was corrupt for me (may just have been a bad dl on my end). I'm re downloading the full file now.
Anyway, I used odin. Selected the charge.pit and repartitioned. I allowed that to finish. I then restarted and flashed the smaller .md5 file. I then was able to reboot into CWM.. which is where I am now as the system just boot loops on the Samsung logo ATM.
Any words of wisdom to get me out of the boot loop would be great.. I'll check back later - hopefully with news that I fixed my phone.
trebores1 said:
Unfortunately, I am trying to fix this very problem right now.
I was able to get rid of the error message with your method and I can now get into CWM again.. which is progress. I used the smaller file as it looks like the bigger one was corrupt for me (may just have been a bad dl on my end). I'm re downloading the full file now.
Anyway, I used odin. Selected the charge.pit and repartitioned. I allowed that to finish. I then restarted and flashed the smaller .md5 file. I then was able to reboot into CWM.. which is where I am now as the system just boot loops on the Samsung logo ATM.
Any words of wisdom to get me out of the boot loop would be great.. I'll check back later - hopefully with news that I fixed my phone.
Click to expand...
Click to collapse
Can you flash anything in CWM? Or how about odin the Ed1 rooted package.?
hoppermi said:
Can you flash anything in CWM? Or how about odin the Ed1 rooted package.?
Click to expand...
Click to collapse
I'm going to try that next.. it's downloading now (slowly). It may just be me, but I can't get the full ED1_CWM_Fix.tar.md5 to flash at all. I have now downloaded it from multishare direct and rapidshare and both fail the same way (Write operation failed).
hoppermi said:
Can you flash anything in CWM? Or how about odin the Ed1 rooted package.?
Click to expand...
Click to collapse
And, yes - I was able to previously flash the ed2-debloat rom from CWM, but it wouldn't boot up... I may try that again while I'm waiting for the stock-ED1 root to finish downloading.
trebores1 said:
I'm going to try that next.. it's downloading now (slowly). It may just be me, but I can't get the full ED1_CWM_Fix.tar.md5 to flash at all. I have now downloaded it from multishare direct and rapidshare and both fail the same way (Write operation failed).
Click to expand...
Click to collapse
Pretty sure that papi flashed this http://forum.xda-developers.com/showthread.php?t=1085190 one the error message was gone, and he was good to go.
Hey after you flash the smaller package given by imnuts07 I flashed stock ed1 rooted thru odin and it worked.
Sent from my SCH-I510 using XDA Premium App
papi92 said:
Hey after you flash the smaller package given by imnuts07 I flashed stock ed1 rooted thru odin and it worked.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Yeah, that worked. It got rid of the error and I can now boot into stock recovery.. but I'm stuck in a droid eyeball bootloop now. Not sure what else to do. I factory reset everything. I think it's time to just return to the VZW store.
Don't return it. You got that far it can be restored. Try flashing altered beast thru odin o
Sent from my SCH-I510 using XDA Premium App
Also start up took about 10 minutes for me and make sure your phone still isn't on ext 4.
Sent from my SCH-I510 using XDA Premium App
Same here. Flashing altered beast fixed the problem and let me cwm flash debloatedv4. (4.1 seems really buggy)
Sent from my SCH-I510 using Tapatalk
papi92 said:
Also start up took about 10 minutes for me and make sure your phone still isn't on ext 4.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
I think I turned off ext4. In cwm I disabled the voodoo lagfix and the voice said that it was disabled. How else would I tell if it's off?
I tried your other suggestions too. Flashed altered beast, ed1 rooted, no luck getting past the bootup loop.
When you restored via Odin using the almost-everything.tar.md5, were you able to reboot and use your phone? I can't get that far. If I reboot it just hangs on the samsung logo. After that, I can flash altered beast or ed1-rooted and I get to the droid bootloop.
Trust me, I don't want to return it.. I'm sure there's a fix here somewhere.
You need to wipe data. You have too. And yes I got stuck at Samsung logo after. I had to flash stock ed1 rooted then wipe data
Sent from my SCH-I510 using XDA Premium App
trebores1 said:
I think I turned off ext4. In cwm I disabled the voodoo lagfix and the voice said that it was disabled. How else would I tell if it's off?
I tried your other suggestions too. Flashed altered beast, ed1 rooted, no luck getting past the bootup loop.
When you restored via Odin using the almost-everything.tar.md5, were you able to reboot and use your phone? I can't get that far. If I reboot it just hangs on the samsung logo. After that, I can flash altered beast or ed1-rooted and I get to the droid bootloop.
Trust me, I don't want to return it.. I'm sure there's a fix here somewhere.
Click to expand...
Click to collapse
To find out if lagfix is disabled run mount from a root terminal app, or adb shell mount if you're hooked up to your computer. If anything shows up as ext4, lagfix is still enabled. If it is all rfs/vfat/not ext4 then you're ok.
Progress has been made! I followed steps 1-8 on imnuts guide. On step 8, nothing happens(as it should). Rebooted into download mode, flashed almost-everything, rebooted, system hangs on samsung logo. Rebooted into download mode, flashed ed1-rooted. Rebooted, system boots into phone!
Now I get an error that my sim card is not supported or readable.. but at least I got back into the phone..
trebores1 said:
Progress has been made! I followed steps 1-8 on imnuts guide. On step 8, nothing happens(as it should). Rebooted into download mode, flashed almost-everything, rebooted, system hangs on samsung logo. Rebooted into download mode, flashed ed1-rooted. Rebooted, system boots into phone!
Now I get an error that my sim card is not supported or readable.. but at least I got back into the phone..
Click to expand...
Click to collapse
Did you activate another phone? I know someone w/ a TB who reactivated his Fascinate then wanted to switch back and his sim wouldn't work. Had to get a new one.
Sent from my SCH-I510 using Tapatalk
Hi guys!
I'm a semi noob when it comes to all this, BUT I did thoroughly look over the forums for almost 8 hours now trying to figure all this out on my own, but now I think I may have taken a turn for the worse.
First of all I have a Samsung Galaxy S Vibrant 4g. I first rooted my phone successfully using the SuperOneClick, no problem. Then I wanted to use team whiskey's Bionix Frost rom (http://forum.xda-developers.com/showthread.php?t=1119986) which I LOVED on my other vibrant galaxy s (not 4g).
I then went to this thread to get CWM (http://forum.xda-developers.com/showthread.php?t=1099374) which was placed in all the right folders I believe, BUT here was when the problems started....
I did not run the update.zip file twice... I went in CWM mod (by pressing the volume buttons and power button) and then reinstalled packages and then selected the update.zip....THEN I thought I could go ahead and install the Bionix rom by selecting that zip file..
It unloaded and then went to reboot...but the screen never passed the GALAXY S 4g logo....
so back to the forums I went. I really couldn't find anything that would help except load the old firmware with odin, so I went to http://www.akaskriller.com/free/vibrantflashing1.php and followed his steps..but I think that was a bad move because these files aren't particularly for my 4g
so when I went to flash the original stock (which was 2.1) I think I really screwed it up because it said FAIL when I tried to run it through odin..
now here's the big probem:
I can't get into download mode any longer (by pressing JUST the volume buttons and then usb and then battery). I took the picture and attached it, so now what can I do?
the picture is a cellular mobile phone connected to a yellow triangle with an exclamation point connected by dots to a computer.
please please please help if you can and leave step by step instructions if possible. I would greatly appreciate it, and I know it's stressful reading these things, but I honestly have tried for 8 hours now trying to figure this out on my own, and now I'm asking the community. Thanks!
You can still Odin from there. That is basically another download screen. I got it once after an Odin fail. Ran Odin again and was fine. Start Odin up and plug in your phone to see if it recognizes it. If it does then Odin a rom mentioned for the sgs4g only.
Sent from my SGH-T959V using xda premium
You are in download mode. Also, the stock rom isn't 2.1, it is 2.2.1 this isn't a vibrant.
airfluip1 said:
You are in download mode. Also, the stock rom isn't 2.1, it is 2.2.1 this isn't a vibrant.
Click to expand...
Click to collapse
I can't seem to find a stock rom to use through odin (a .tar file right?)
tortabeech said:
I can't seem to find a stock rom to use through odin (a .tar file right?)
Click to expand...
Click to collapse
Use this,it will work , it has root too http://forum.xda-developers.com/showthread.php?t=1063696
tortabeech said:
I can't seem to find a stock rom to use through odin (a .tar file right?)
Click to expand...
Click to collapse
Sent from my SGH-T959V using xda premium
Ok so I've been rooted and unlocked for a while now, but stayed with the stock rom as when I tried out Synergy Nightlies it gave me some errors. So I went to try out CleanRom 2.1, people liked it and I didn't notice any flashing errors. So I flashed it through CWM 6.0.1 and it gave me the yellow exclamation mark saying I had unauthorized data on my phone. So I followed the sticky on how to unbrick my phone using the 2 boot loaders and the root66 stock image. My issue is that when running the root66 stock image through Odin it fails at _XmitData_Read, which seems to be somewhere in system.img.ext4. I've tried rebooting the computer, the phone, Odin, it just doesn't work. So when I reboot my phone after the failure I get Odin auto loading saying:
Odin Mode
Product Name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
Then an image of a phone, 2 dots, a yellow exclamation, 2 dots and a computer are shown with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Anyone able to help me?
can you still get to odin mode? also if you have kies installed on the computer erase it.
kidhudi said:
can you still get to odin mode? also if you have kies installed on the computer erase it.
Click to expand...
Click to collapse
Kies isn't installed on the computer and yes I am still able to get into Odin Mode.
I'm under the impression that "unauthorized software" message comes from the locked bootloader (if I'm wrong about that someone plese correct me.)
Sounds like you're functional enough to be able to Odin back to stock and go from there - that's what I'd try. See the stickied thread in the Q&A forum.
I would run the FULL VRALF stock image through ODIN to return to stock. That is always the safest way out of a sticky situation.
Thanks guys, according to another post the version of EZ-Unlock I used most likely gave a false report and never actually unlocked my phone. The problem with going back to stock, which if what I'm trying to do, is that it fails.
Could be an USB issue - an intermittent connection would be most likely to cause problems while sending the system partition since that's the biggest. I've had problems using adb from time to time if I plug into one of the front-panel ports on my PC but no trouble with one on the back.
Maybe try switching ports or try a different cable ...
Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app
Strange.... i was able to flash syergy on thefirst try. Never used odin during the whole process....
If youre rooted you need to make sure you have a custom recovery in place like cwm or twrp. Make sure you make a nand-backup.
I used casual to flash unsecure bootloader, with that and recovery in place you should be able to flash roms without any hitches....
I could never find a comprehensive guide on using odin so i never got around to testing it
kintwofan said:
Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So far I've tried 3 different USB cables and both a desktop, both front and back ports and a laptop, each one fails on the write of XmitData under system.img.ext4
I had a custom recovery installed and Odin is only being used to get me back to a stock rom, otherwise I did all my flashing under CWM 6.0.1 or twrp. I think the whole fake unlocked bootloader just hard bricked the software.
EDIT: Come to think of it I remember waking up to my phone in download mode. I think Verizon tried to install the update to my phone while I was sleeping. Granted it failed at the end, but I'm wondering if that did something to brick me now.
If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yea, I'm currently downloading at the speed of slug the newest update from the forums, will probably just redownload at home, since it's going to take over an hour >.<
EDIT:
Does anyone have a link for an older EZ-Unlocker, that is known to work, so that I don't get this problem yet again.
FIXED!
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.
LlirasChosen said:
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.
Click to expand...
Click to collapse
I personally suggest not using the app if you already had trouble. Just root your phone using the Debug Root method in Development, download the aboot.img from Adam Outlers thread HERE to your phone, and run the commands at the very bottom in Terminal Emulater app (from the market).
That way you know for sure your bootloader is unlocked. This is what I have done and never had an issue.
Edit: Glad you got your issue resolved!
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