Related
OK. On my last phone I immediately started playing with ROMs and lost my 3 button recovery as well as the ability to get and use OTA updates.
While I'd like to play with the ROMS and such, I'd like the ability to restore it to where it is today. 100% stock ATT.
Is there some way to make an image or something of my exact phone that I can use with odin or something later to get it back EXACTLY like it is today?
Sent from my SAMSUNG-SGH-I897 using XDA App
check out the forum sections. They have great video tutorials on how to rom. There is also a prog called odin3 which puts your phone back to stock.
Sent from my SAMSUNG-SGH-I897 using XDA App
Actually Odin does not return to your stock. That's why many Captivates lost 3button recovery when they used Odin and phones recovered with Odin will no longer do OTA updates.
I would like to avoid those pit falls before changing ROMs.
Sent from my SAMSUNG-SGH-I897 using XDA App
Msube answering my own question. Will clockwork recovery do the same as Odin, except get me back to where i am now?
Since I'll need to root/unroot, will my phone ba any different after the unroot than before the root?
Sent from my SAMSUNG-SGH-I897 using XDA App
cdwhit said:
OK. On my last phone I immediately started playing with ROMs and lost my 3 button recovery as well as the ability to get and use OTA updates.
While I'd like to play with the ROMS and such, I'd like the ability to restore it to where it is today. 100% stock ATT.
Is there some way to make an image or something of my exact phone that I can use with odin or something later to get it back EXACTLY like it is today?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Like a snapshot. I agree, would be nice
From my understanding odin will get you back completely to stock if you are trying to send the phone to at&t for repairs. I believe it is/made from leaks from at&t
Sent from my SGH-I897 using XDA App
crystalhand said:
From my understanding odin will get you back completely to stock if you are trying to send the phone to at&t for repairs. I believe it is/made from leaks from at&t
Click to expand...
Click to collapse
Nope. If it flashed completely to stock there would not have been all the phones that lost 3 button recovery after using it (apparently because it changed the sbl.bin file which is apparently NOT the same on all captivates). You also would be able to get OTA updates after using Odin, which once again, my phone and most others won't.
I suspect that there are minor differences between the software in various run of phones as new chips and programs were tried to correct issues. Odin is based on the software from ONE of these variations (maybe not even a Captivate). Odin will get you phone where you can use it and close enough to stock get it past the exchange flunkies, BUT IT IS NOT THE SAME AS WHEN YOU BOUGHT YOUR PHONE. At least not in all cases.
Sent from my SAMSUNG-SGH-I897 using XDA App
So, is there some way to get it back to the default, out of the box, AT&T ROM?
I don't know. That's what my original question was. I had a phone dtraight out of the box. For that matter, even now I only have rooted so I could do a clockwock back up. I was looking for a way to make an exact copy of my phone thst I could put back on latr. If anyone knows how, apparently they don't want to share.
trekie86 said:
So, is there some way to get it back to the default, out of the box, AT&T ROM?
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
I'm also interested in this.
If you have root and a copy of busybox installed could you just. "dd if /dev/pathtocopy of /dev/pathtowrite" to create a drive image?
Can it be that straight forward?
cdwhit said:
Nope. If it flashed completely to stock there would not have been all the phones that lost 3 button recovery after using it (apparently because it changed the sbl.bin file which is apparently NOT the same on all captivates). You also would be able to get OTA updates after using Odin, which once again, my phone and most others won't.
I suspect that there are minor differences between the software in various run of phones as new chips and programs were tried to correct issues. Odin is based on the software from ONE of these variations (maybe not even a Captivate). Odin will get you phone where you can use it and close enough to stock get it past the exchange flunkies, BUT IT IS NOT THE SAME AS WHEN YOU BOUGHT YOUR PHONE. At least not in all cases.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Interesting. So ODIN is "like" stock. Kinda scary to know you can never go back!
sircaper said:
Interesting. So ODIN is "like" stock. Kinda scary to know you can never go back!
Click to expand...
Click to collapse
Sort of odin is exasperating existing problems. The loss of the 3 button recovery is an issue with some builds. My build is among those but I have had no problems. As for the loss of kies support I imagine it is somehow related to the loss of 3 button recovery because I have been able to update after flashing to odin
Sent from my SAMSUNG-SGH-I897 using XDA App
If you lost 3 button recovery you most likely flashed JF6 firmware. You have two options, flash JF6 with 3 button fix or flash a newer at&t firmware such as jh7. I'm Canadian so I don't know if it will work 100% but in my limited experience it will at least fix the 3 button combo not working. If I flash JF6 on my i896 I loose my 3 button recovery too unless I use one with a fix included. Also kies tells me there is an update available when I have JF6 installed with the 3 button fix. Search xda for the image or I can post link later.
Edit: The one click made by Disigngears doesn't work for me, I use the 512.pit file and JF6 with three button combo image file that you can get for odin3.
Sent from my phone using the XDA app.
Some people got 3 button back with the jh7 update. Some (myself included) didn't. Also Kies is not the same as OTA. You should be able to get updates without plugging your phone into the computer.
BUT, I was using that as an example. I would like to be able to return to what I am TODAY. I don't know what other changes are being made by Odin that may bite me later.
Vaanhoot said:
If you lost 3 button recovery you most likely flashed JF6 firmware. You have two options, flash JF6 with 3 button fix or flash a newer at&t firmware such as jh7. I'm Canadian so I don't know if it will work 100% but in my limited experience it will at least fix the 3 button combo not working. If I flash JF6 on my i896 I loose my 3 button recovery too unless I use one with a fix included. Also kies tells me there is an update available when I have JF6 installed with the 3 button fix. Search xda for the image or I can post link later.
Edit: The one click made by Disigngears doesn't work for me, I use the 512.pit file and JF6 with three button combo image file that you can get for odin3.
Sent from my phone using the XDA app.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
Well, corruption of IMEI was a problem with Odin too, but it's easy to restore if you are trying to unlock your phone. I guess you could do a nandroid back up and a rom manager backup and try using them together to restore to exactly what you have now. So far I haven't had any problems with flashing with Odin on a 1010 build, but OTA updates have been unusable, but they just bricked phones anyway. There is also a kies update available too. If you wanna be a test subject, try buying Root Explorer (well worth it) and copy all the files in the root of your system partition into a folder on an external sd card or something.
Hey everyone! I've been reading these forums for the past two days, which have been awesome, except that I still can't get past this roadblock to root though -- namely, the problem in the tile: Odin v1.85 keeps on crashing when I hit "start" to install CWM. I hoping that someone can help!
My successes:
I've installed 4.0.3 and 4.0.4 using the one-click files without any problem.
I haven't had any problems with Odin recognizing my phone (i727).
My attempts:
Odin 1.85 crashes upon hitting start (CWM.tar is in the PDA slot, only auto-reboot selected).
I've also tried Odin 1.83
Switched USB cables
Switched USB ports
Tried two laptops, one computer
Re-downloaded the files several times
Is there anything I'm missing?
My current guess is a problem with the OS. All of the computers are running the Chinese version of Windows (have both XP and 7). I plan to find/install an English version today if the problem isn't resolved, but I'm hoping that there's another factor that I overlooked.
Thanks a bunch!
-D
You try running it as admin??
Sent from my SAMSUNG-SGH-I727 using xda premium
I just tried admin again in case I didn't. Odin still crashed
Going to try an English OS later
DFruit said:
Hey everyone! I've been reading these forums for the past two days, which have been awesome, except that I still can't get past this roadblock to root though -- namely, the problem in the tile: Odin v1.85 keeps on crashing when I hit "start" to install CWM. I hoping that someone can help!
My successes:
I've installed 4.0.3 and 4.0.4 using the one-click files without any problem.
I haven't had any problems with Odin recognizing my phone (i727).
My attempts:
Odin 1.85 crashes upon hitting start (CWM.tar is in the PDA slot, only auto-reboot selected).
I've also tried Odin 1.83
Switched USB cables
Switched USB ports
Tried two laptops, one computer
Re-downloaded the files several times
Is there anything I'm missing?
My current guess is a problem with the OS. All of the computers are running the Chinese version of Windows (have both XP and 7). I plan to find/install an English version today if the problem isn't resolved, but I'm hoping that there's another factor that I overlooked.
Thanks a bunch!
-D
Click to expand...
Click to collapse
what file r u trying to odin, never seen a "cwm.tar", i think ur trying to flash a bogus tar
read this on how to flash cwm http://forum.xda-developers.com/showthread.php?t=1566613
read this for further troubleshooting http://forum.xda-developers.com/showthread.php?t=1652398
vincom said:
what file r u trying to odin, never seen a "cwm.tar", i think ur trying to flash a bogus tar
read this on how to flash cwm http://forum.xda-developers.com/showthread.php?t=1566613
read this for further troubleshooting http://forum.xda-developers.com/showthread.php?t=1652398
Click to expand...
Click to collapse
My apologies. I am using the SkyrocketCWMrecovery.tar file. I couldn't remember the full name earlier, so I just made one up.
I try the .tar you linked me. Hopefully that's the problem thanks!
Thanks!
Thank you very much, good sir!
The CWM touch .tar file worked. I'm not sure how I didn't see it earlier. I remember the [howto] I found here used the other .tar -- I guess it was outdated? I should've looked into the .tar earlier. Thanks again so much! Lots of wasted time spent on this.
I have now entered rootworld for the first time. w00t!
Hey well, to start things off I was trying to unlock my T-Mobile SGS4G to work with AT&T but it turns out it needs to be rooted first. I have rooted before and this is the first time I have ran into a problem.
What I did first:
I used Heimdall in an attempt to flash CWM Recovery so I can gain root access. For some reason the zImage was bad (?) and my phone could only get to the T-Mobile logo and then freeze.
Recovery and Download DID work
What I did second:
I used odin3 to flash back a stock T-Mobile rom in hope to fix things... and it did everything succesfully but now it's stuck in a real boot loop.
Can't get into Recovery, nor Download. It's really depressing to keep seeing that battery show over and over again.
Any ideas on how to get my computer to detect my phone again?
Thanks.
Edit:
I did every button combination + usb plug combination known to man. I uninstalled and installed the files again.
Did my phone brick because I ticked the partition tab on odin?
PLEASE help.
Our phone IS NOT the Vibrant. Hopefully someone can help you, but... I don't know. If you flashed OUR stock rom, with bootloaders... you're screwed. But, the fact you have images on your screen, should give you some hope.
Yea, I saw that, but the title says he has a vibrant. I don't know....
Head to the vibrant forum there are some un-brick tools over there...you need to get it in download mode use odin to flash stock froyo vibrant rom.. Should get it back up and running
Sent from my SGH-T959V using xda premium
Kingarabian said:
T-Mobile SGS4G
Click to expand...
Click to collapse
Just to verify, pull out your battery and check if you have the SGH-T959V
One of the "download jigs" may help once you are certain which phone you have and what firmware and ROM you need to flash. You can make your own with a resistor and a microUSB plug, I bought one for $8.00, delivered, (I now see they have them on Amazon for $4, Super Saver eligible) and others have had good luck with even cheaper ones on eBay.
Also: http://forum.xda-developers.com/showthread.php?p=9403915
Jigs are cheap and unless you got the right resistor lying around buy a ready made one. Also if the phone shows up in odin you can download something whatever picture shows up on the screen. Raver has a thread about using heimdall to fix the boot files but its about six months old. Worked for me once. It might even be indexed in the bible under development.
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