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.
Related
So this morning I was checking out the new choices in my Froyo leak - rooted Captivate, I clicked on every one of them to see what it is and then I clicked on one that said something like user accounts, well ever since then my phone has been a black screen only displaying the top clock and a no signal bar. What should I do next? Unfortunately Im stuck at work with no programs. So Im wondering what would you do, which Odin should I use? Ill be checkin in cause at least I can do this and plan fixing my phone for later
Im guessing you tried pulling the battery?
Sent from my SAMSUNG-SGH-I897 using XDA App
sure did tried the reboot screen.
and the other thing, now the phone wont go into sleep mode so my battery is slowly dying too
try to boot into recovery and clear out the cache...
I did that too and it clears and then i reboot then it goes right back to black screen
The same thing happened to me, but I wasn't digging around in the settings. Like previously mentioned, I booted into recovery, and cleared cache/factory wipe, and it booted back fresh. Luckily, I had a Titanium Backup from a few hours before it happened, so I didn't really lose anything.
I had something like this too. Can you get into Download mode and use Odin to return to stock rom? It took me several tries before Odin worked.
Well I still haven't heard anyone who has completely bricked there samsung captivate yet so I think you'll be alright. Just to be the 1 click Odin when you get home.
I'm pretty new myself at this But I think the only way were really screwed Is if we kill the bootloader.
Sent from my SAMSUNG-SGH-I897 using XDA App
i will try when i get home, im stuck at work unfortunately, at least i know im not the only one, i was also fooling with settings
thank you
Theres been a few people that have fully bricked their captivates... Including me.
If you got your captivate within the last couple weeks be careful using odin with a froyo kernel. Check the Q&A thread for a post titled "phone-pc something" (Using my phone otherwise I'd provide a link)
loserskater said:
Theres been a few people that have fully bricked their captivates... Including me.
If you got your captivate within the last couple weeks be careful using odin with a froyo kernel. Check the Q&A thread for a post titled "phone-pc something" (Using my phone otherwise I'd provide a link)
Click to expand...
Click to collapse
Well that sucks.
Sent from my SAMSUNG-SGH-I897 using XDA App
theMaginator said:
Well I still haven't heard anyone who has completely bricked there samsung captivate yet so I think you'll be alright. Just to be the 1 click Odin when you get home.
I'm pretty new myself at this But I think the only way were really screwed Is if we kill the bootloader.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I had one. OTA update. And I wasn't the only one. I couldn't even get into download mode.
yeah, bricked here too trying to go to Froyo. Sent to Samsung, they fixed it.
theMaginator said:
Well I still haven't heard anyone who has completely bricked there samsung captivate yet so I think you'll be alright. Just to be the 1 click Odin when you get home.
I'm pretty new myself at this But I think the only way were really screwed Is if we kill the bootloader.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
lol its happened to many people, myself included.
Hi, I've had the glorious captivate for a few weeks now and I constantly read this forum. I am now ready to flash my phone and while I am not really afraid to do it, since I used to flash my Nokia 5800 every week, I wonder what is it during the process of flashing and loading a new rom that can cause the phone to get bricked? Are some parts riskier than others? Is there some common mistake or error or something people usually forget that kills it?
I'd appreciate some answers, since I love my phone and would hate to brick it.
Thank you very much! XDA rules!
Sent from my SAMSUNG-SGH-I897 using XDA App
rufex2001 said:
Hi, I've had the glorious captivate for a few weeks now and I constantly read this forum. I am now ready to flash my phone and while I am not really afraid to do it, since I used to flash my Nokia 5800 every week, I wonder what is it during the process of flashing and loading a new rom that can cause the phone to get bricked? Are some parts riskier than others? Is there some common mistake or error or something people usually forget that kills it?
I'd appreciate some answers, since I love my phone and would hate to brick it.
Thank you very much! XDA rules!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
If you test the phone to make sure it can accept the button combinations to go into download mode (almost all do, except for a batch of faulty ones), there is almost nothing you can do that will truly "brick" the phone. A bad or interrupted flash will result in a boot loop, which you can recover from by forcing download mode, and using Odin to reflash back to stock.
Flashing the first and second bootloaders would be the most dangerous, which is why the Odin one-click flasher is so bad. Also, the USB connection is a prime source of failure which is another reason to avoid Odin. So, if you have working button combos you are pretty unlikely to brick the phone as long as you avoid unnecessarily using any version of Odin.
Note: DesignGears includes sbl.bin (the second bootloader) in his ROMs, but since you aren't flashing it via USB it's relatively safe and it does have the side-effect of fixing you button combos if they aren't working. On the other hand, if you aren't using the one-click then you probably already have a good sbl.bin and so it's not needed.
Basically what causes a brick in any electronic equipment is from an interruption/error in any boot critical files. The item does not have the proper/complete instruction to turn on. You could say it is like starting a car being told to first put the key in
Sent from my SAMSUNG-SGH-I897 using XDA App
If you can use the 3 button combos to get into download or recovery mode, you are good to go. The only danger would be a bad Odin flash, but even so you'll have a chance to recover it by making a cheap USB jig (3 100k Ohm resistors into pins 3 and 4, I think, of the usb port) or buying one. This will boot the phone straight into Download mode.
When using Odin, there is only one stage where you can brick your phone for good, during the bootloader copy process, which probably takes less than a second.
Thanks for the replies! I just tried it and I got the 3 button into download mode combo, so that's great! Now, what other options do I have for flashing besides Odin? Apparently Odin is not the safest, huh? And is there a way to make the bootloader writing stage less risky?
Also, my Captivate is a 1007 build. Is that a good thing or a bad thing?
Thanks, again!
Sent from my Samsung Captivate using the XDA App
rufex2001 said:
Thanks for the replies! I just tried it and I got the 3 button into download mode combo, so that's great! Now, what other options do I have for flashing besides Odin? Apparently Odin is not the safest, huh? And is there a way to make the bootloader writing stage less risky?
Also, my Captivate is a 1007 build. Is that a good thing or a bad thing?
Thanks, again!
Sent from my Samsung Captivate using the XDA App
Click to expand...
Click to collapse
My Cappy is a 1007 build, too. I've soft bricked my phone more times than I can count, but Odin hasn't had anything to do with it. It can do it, though.
At one time in my life I flashed a new ROM every day, and I used Odin every time before I flashed.
On a side note, back when I flashed my first ROM, I pulled the battery during the first boot, dropped it, and then flashed another ROM without using Odin, and it never bricked it, so that should give you a good idea of how hard it is to brick these phones. Lol
Stupidity.
Sent from my Captivate.
opcow said:
Flashing the first and second bootloaders would be the most dangerous, which is why the Odin one-click flasher is so bad. Also, the USB connection is a prime source of failure which is another reason to avoid Odin. So, if you have working button combos you are pretty unlikely to brick the phone as long as you avoid unnecessarily using any version of Odin.
Note: DesignGears includes sbl.bin (the second bootloader) in his ROMs, but since you aren't flashing it via USB it's relatively safe and it does have the side-effect of fixing you button combos if they aren't working. On the other hand, if you aren't using the one-click then you probably already have a good sbl.bin and so it's not needed.
Click to expand...
Click to collapse
I didn't realize Odin one click was so bad. I have been using Odin3 one click routinely now for a couple weeks as I flash back and forth trying out all these great ROMs to see what I like and so far (knock on wood I guess?) I haven't had any problems at all.
So, now that I have used Odin one click many times over, does my Cappy now have a bad sbl.bin?
No odin really is not that bad just don't unplug it while it is running. You would not want to unplug your computer when flashing a new bios
Sent from my SAMSUNG-SGH-I897 using XDA App
Right, so if not Odin, what can I use for flashing? Can I do it all with the sdk using adb?
Also, I've been going through the guides and other stickies and apparently Odin is necessary only to flash back to stock. For rooting and installing new roms only the update.zip file and clockwork recovery are necessary. Could you do the same procedure to flash back to stock?
Sorry for any dumb or repeated question I may be asking.
Sent from my SAMSUNG-SGH-I897 using XDA App
Pierce533 said:
I didn't realize Odin one click was so bad. I have been using Odin3 one click routinely now for a couple weeks as I flash back and forth trying out all these great ROMs to see what I like and so far (knock on wood I guess?) I haven't had any problems at all.
So, now that I have used Odin one click many times over, does my Cappy now have a bad sbl.bin?
Click to expand...
Click to collapse
Odin isn't bad so much as an unnecessary risk. There are a lot of potential causes of failure: user error, accidents, flakey USB ports or software from other vendors that interferes with your drivers. The there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build. I can safely odin flash all day if I need to, but there's just no reason to. And if you look around these forums you will see a lot of people crying after an odin mishap.
rufex2001 said:
Right, so if not Odin, what can I use for flashing? Can I do it all with the sdk using adb?
Also, I've been going through the guides and other stickies and apparently Odin is necessary only to flash back to stock. For rooting and installing new roms only the update.zip file and clockwork recovery are necessary. Could you do the same procedure to flash back to stock?
Click to expand...
Click to collapse
I keep a CWM update.zip on my sdcard for reinstalling CWM and I flash my ROMs with CWM. I also keep a couple of spare know good ROM zips on the sdcard to go back to in case something goes wrong with a new install.
opcow said:
Odin isn't bad so much as an unnecessary risk. There are a lot of potential causes of failure: user error, accidents, flakey USB ports or software from other vendors that interferes with your drivers. The there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build. I can safely odin flash all day if I need to, but there's just no reason to. And if you look around these forums you will see a lot of people crying after an odin mishap.
Click to expand...
Click to collapse
Thanks for the info. Is there a stock I897UCJF6 ROM that can be flashed with CWM? I haven't been able to find one and if there is one I would like to have one around to use. Thanks for taking the time to answer my questions.
opcow said:
I keep a CWM update.zip on my sdcard for reinstalling CWM and I flash my ROMs with CWM. I also keep a couple of spare know good ROM zips on the sdcard to go back to in case something goes wrong with a new install.
Click to expand...
Click to collapse
That is exactly the sort of thing I had in mind! So I guess I could keep a CWM update.zip and a stock rom update.zip and some custom roms and just do everything directly from the phone and without Odin, right? Or am I missing something?
Sent from my SAMSUNG-SGH-I897 using XDA App
Guns don't kill people
opcow said:
Odin isn't bad so much as an unnecessary risk. Then there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build.
Click to expand...
Click to collapse
Yep. I have build 1008 that has always had the 3-button combo and lost it after using ODIN 1-click (I restored the combo with a later flash).
I believe opcow and others when they say that flashing back to stock is unnecessary. I just don't understand why the authors of some of these ROMs leave this as part of their installation guide.
Sent using XDA App
Pay close attention to the options in recovery when you are using a custom rom. It's part of the custom kernal, and of used properly can help you avoid odin. I avoid it because I have a mac and odin won't run on anything but windows. Custom recovery will allow you to format every part of the OS but the sbl.bin. Also in some custom recoveries there is an option to mount usb. This will allow you to format the internal sd then copy a new rom.zip and flash if you really want a clean flash. If your doing this make sure you are able to mount your sd before you format anything. Avoid stock 2.2 kernals because they have 3e recovery. There are ways around that but they have to be in play before you end up in a bootloop.
3e recovery + bootloop= odin recovery "only option".
Make sure lag fix for rom kernal A understands lag fix for rom kernal B. Also usually only a concern for stock 2.2 kernal. Other than that really hard to brick this phone.
Sent from my SAMSUNG-SGH-I897 using XDA App
As long as you keep a CWM update.zip and a ROM on your internel sdcard at all times, I see no reason why you would ever have to use odin 1-click.
I get bootloops all the time, just pull the battery and then use vol up + vol down + pow to enter recovery to flash the ROM back. Make sure it's a wipe ROM.
If it's not a soft-brick, then you will need odin.
ryude said:
As long as you keep a CWM update.zip and a ROM on your internel sdcard at all times, I see no reason why you would ever have to use odin 1-click.
I get bootloops all the time, just pull the battery and then use vol up + vol down + pow to enter recovery to flash the ROM back. Make sure it's a wipe ROM.
If it's not a soft-brick, then you will need odin.
Click to expand...
Click to collapse
Could you please explain what a wipe ROM is? Thanks
ok i see since it has been so long since all the rogers development started people dont really remember about all the rainbow problems and how they were fixed and how the fix needs source code.
we now have bootloaders available in leaks from samsung. they are needed with the stock kernels that come in the leaks to avoid rainbow garbage. i am providing the bootloaders to be flashed in heimdall without having to flash a whole rom.
i would like to make this explicitly clear that if this bricks your phone i am not to blame. there is a significant risk when flashing bootloaders! though the infuse seems to have safety measures i strongly recommend only flashing once. and if your phone becomes a brick you will need to solder things to the phone to fix it via j-tag or adam outlers unbrickable mod. be cautious! dont flash boot.bin without sbl.bin, dont flash sbl.bin without boot.bin, dont mix up the partitions, and if the phone bricks i dont want to know about it unless you want to pay me to fix it!
heimdall package
http://www.multiupload.com/GXUTF4QCJX
odin package (untested)
http://www.multiupload.com.... REMOVED May be failing to flash. very dangerous situation...
bootloaders for heimdall to be added through the "flash" tab (unzip first! ibl/pbl-boot.bin, sbl-sbl.bin)
http://www.multiupload.com/NAIA23JZL1
good luck!
Thanks for posting this. Hopefully it will help out with leak questions that tend to get asked over and over again.
Sent from my SAMSUNG-SGH-I997
Yeah. Thanks for posting, Dani.
do you know if there its any difference in bootloaders amongst different gingerbread leaks?
I have been running the first leaked gingerbread's bootloaders since Prezkit gave them to us and have had zero issues. I think it was kk1? I've been taking an "if it ain't broke" stance. its going good!
MattSoRaven said:
Yeah. Thanks for posting, Dani.
do you know if there its any difference in bootloaders amongst different gingerbread leaks?
I have been running the first leaked gingerbread's bootloaders since Prezkit gave them to us and have had zero issues. I think it was kk1? I've been taking an "if it ain't broke" stance. its going good!
Click to expand...
Click to collapse
there is difs. but I couldn't tell you what. I saw posts by Linux bozo who did binary diferencials but I don't see any difference.
I know the bootloaders have a counter for customer kernels. if you flash the parameters.ifs from the ultimate unbrick it resets it. I also know they changed the galaxy s 2 bootloaders so it was harder to reset the counter so don't expect to be able to reset it when the official update comes along. I also have been using the "if it ain't broke " theory and honestly don't remember which I am using. the packages here are uckk3. if people can test if the counter can still be reset by flashing param.ifs let me know. ill post older bootloaders if it can't otherwise I can't think of any reason to pick one over another.
If i am flashing the bootloaders via odin does the .tar file go in the pda slot. thank you for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
bigbadwolf311 said:
If i am flashing the bootloaders via odin does the .tar file go in the pda slot. thank you for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
yes. that's how I would do it. the PDA slot seems to be automatic as far as partition sorting. the phone slot is for modems but if a modem is included in a package for the PDA slot it flashes just fine. the bootloaders are in the PDA packages normally so that's how I would do it.
please report results because I don't run windows and did not test that package.
I will report back once i get around to flashing the bootloaders. Thanks again for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Dani897 said:
there is difs. but I couldn't tell you what. I saw posts by Linux bozo who did binary diferencials but I don't see any difference.
I know the bootloaders have a counter for customer kernels. if you flash the parameters.ifs from the ultimate unbrick it resets it. I also know they changed the galaxy s 2 bootloaders so it was harder to reset the counter so don't expect to be able to reset it when the official update comes along. I also have been using the "if it ain't broke " theory and honestly don't remember which I am using. the packages here are uckk3. if people can test if the counter can still be reset by flashing param.ifs let me know. ill post older bootloaders if it can't otherwise I can't think of any reason to pick one over another.
Click to expand...
Click to collapse
I've been using the UCKJ2 bootloaders since they came out with no issues.
Entropy512 said:
I've been using the UCKJ2 bootloaders since they came out with no issues.
Click to expand...
Click to collapse
Same here.
Sent from my SAMSUNG-SGH-I997 using xda premium
bigbadwolf311 said:
I will report back once i get around to flashing the bootloaders. Thanks again for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Wonder if u can give me directions for the odin method. Should i put it in download mode like im flashing back to stock? Can i Flash this over a custom rom?
schmidtty661 said:
Wonder if u can give me directions for the odin method. Should i put it in download mode like im flashing back to stock? Can i Flash this over a custom rom?
Click to expand...
Click to collapse
don't select repartition, no need for a pit, the rom shouldn't matter, the file should go in the PDA slot. remember I haven't tested it in Odin. I don't run windows and have little interest in using Odin for anything. phone needs to be in download mode just like flahong a rom. it should only take a second or two to flash. good luck
Cool i should be able to figure this out. Thanks for the quick response.
It didn't work. I had auto restart, f.reset and the PDA slot checked after i opened the file in the PDA slot and after clicking start it just sat at setup for 45 min until i gave up and flashed back to stock. I had to pull the cord while in download mode and the screen turned black with green dots so i had to flash blindly. I tried it twice and the same thing. Has anyone else tried this?
schmidtty661 said:
It didn't work. I had auto restart, f.reset and the PDA slot checked after i opened the file in the PDA slot and after clicking start it just sat at setup for 45 min until i gave up and flashed back to stock. I had to pull the cord while in download mode and the screen turned black with green dots so i had to flash blindly. I tried it twice and the same thing. Has anyone else tried this?
Click to expand...
Click to collapse
I have a bunch of downloads but nobody reported anything at all till now.
ill pull the Odin version for now. try it in heimdall. its not any harder to use.
Can you post an odin package.
I had an Odin package. I got a few downloads, didn't get any people thanking for it, didn't get any positive feedback that it worked and had one user report problems, see the last couple posts. I pulled the file for lack of evidence that it worked. I don't run windows and prefer heimdall so I haven't tested it in Odin. sorry but I suggest you either flash an entire rom leak then flash a non secure kernel through Odin ( any custom kernel should do also flashing back to stock should also do just fine) and then flash a rom or learn heimdall which works on windows as well as Mac and Linux. I would have done a oneclick package but it still requires the installation of the heimdall back end and I figured it was really no harder to just use the heimdall package system.
any chance of relink thats not at multiupload?
edit: disregard, found a workaround. might be useful in future tho.
First of all I apologize if this has been brought up before in other posts. I am in a mixture of frustration and panic right now because I tried upgrading to ICS on my Rogers SGS2 LTE, and it failed.
Using Kies, I followed the prompts, and for whatever reason it didn't finish. Now when I boot up the phone, it keeps telling me to use the recovery mode option in Kies. However, if I do try to use recovery mode, it always times out and tells me I may need to contact a Samsung service center. The computer has no problem communicating with the phone, AFAIK.
Basically, I'm here to ask what options I have. Currently, i'm trying to do this: http://forum.xda-developers.com/showthread.php?t=1342348 , but because the stock TAR is taking a long time to download, I'm asking if I have any other options. I would like to keep the data on my phone, but if I have to wipe it to return it to normal I'm willing to do that.
Please help.
Reboot and try again
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Are you rooted? Are you running the stock recovery that came on the phone? If your rooted and have apps that are froze or your running a modded recovery like cwm you must flash back to stock or kies will not ever work
Sent from my SAMSUNG-SGH-I727 using xda premium
I've tried rebooting the computer I was using, and I've also tried another computer with no luck. I got the latest Kies on the other computer, connected the phone with no problem, and tried recovery mode on THAT 2nd computer, but it didn't work because it didn't recognize my recovery code that the first computer gave me.
garydv2002 said:
Are you rooted? Are you running the stock recovery that came on the phone? If your rooted and have apps that are froze or your running a modded recovery like cwm you must flash back to stock or kies will not ever work
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I *think* I was rooted. I remember doing something a long time ago involving odin. I never installed Cyanogenmod or any other 3rd party roms.
I had Superuser under my apps, if that helps.
I wish I could reply sooner but this board is making me wait 5 mins between posts. Sorry. It's like I'm in the emergency room with a gunshot wound and I'm waiting for the doctor to finish his smoke break, then his coffee break, then washroom break, jesus
by CWM, I think you're asking about Clockwordmod? If so, yes, I had that on my phone. Does this mean I can't use the steps in this thread: http://forum.xda-developers.com/showthread.php?t=1342348 to fix my phone now? Or can I still proceed.
If you have superuser then most likely you are rooted and since you have clockworkmod especially then kies is not gonna update your phone. Your on Rodgers so you need to find the stock firmware and flash it. I'm on att or I could link you to one that would work. I got my stock firmware from Samsung website. Try going to sammobile and see if you can find the stock firmware for your phone. I'm sure since its Samsung they should have Rodgers firmware to. Download the stock firmware and flash it in Odin onto to your phone and then kies should work. If you can't find the stock firmware at sammobile then look for the stock firmware here on xda I'm sure someone on Rodgers has it....
Edit. The link up there to Odin back to stock should work. Just download the file and follow the steps in order and don't leave one out. There are no shortcuts when it comes to flashing a phone or it could be rendered useless for anything more than a paperweight. Konane is real good and would not lead anyone wrong....
Sent from my SAMSUNG-SGH-I727 using xda premium
Just flashed it via Kies, had to use ODIN by flashing stock, Odin wouldn't work till I rebooted my computer, then once Kies updated, I had had a error ( com.Android.phone stopped) but I cleared data and cache in 3e, then everything worked.
Sent from my SGH-I727R using xda premium
I just wanted to post a follow-up. I followed the steps from this thread: http://forum.xda-developers.com/showthread.php?t=1342348 and it fixed me phone. Best of all, I didn't lose anything.
I would still like to get ICS on my phone. I noticed on Sammobile's site that there is a firmware for 4.04 that was released recently. Would I somehow be able to use that, combined with Odin, to get ICS on my phone? In other words, follow all the steps in the aforementioned thread, except, use this newer firmware file? Sorry I realize this may sound like a dumb noob question, but I want to make sure I do things right.
Thanks for all the help btw.
bobbastard said:
I just wanted to post a follow-up. I followed the steps from this thread: http://forum.xda-developers.com/showthread.php?t=1342348 and it fixed me phone. Best of all, I didn't lose anything.
I would still like to get ICS on my phone. I noticed on Sammobile's site that there is a firmware for 4.04 that was released recently. Would I somehow be able to use that, combined with Odin, to get ICS on my phone? In other words, follow all the steps in the aforementioned thread, except, use this newer firmware file? Sorry I realize this may sound like a dumb noob question, but I want to make sure I do things right.
Thanks for all the help btw.
Click to expand...
Click to collapse
If you're back to stock and on Rogers, you should be able to update using Kies.
The thing is, when Odin fixed my phone, it didn't remove Superuser, so doesn't that mean my phone isn't stock anymore? I was expecting Odin to basically reset my phone back to factory settings, but it seems to have just reverted it back to before I tried updating to ICS with kies.
bobbastard said:
The thing is, when Odin fixed my phone, it didn't remove Superuser, so doesn't that mean my phone isn't stock anymore? I was expecting Odin to basically reset my phone back to factory settings, but it seems to have just reverted it back to before I tried updating to ICS with kies.
Click to expand...
Click to collapse
If you go into 3e or cwm if you still have it, you should be able to clear cache and data, so after that Kies should recognize it and start the download
Sent from my SGH-I727R using xda premium
denenatse said:
If you go into 3e or cwm if you still have it, you should be able to clear cache and data, so after that Kies should recognize it and start the download
Sent from my SGH-I727R using xda premium
Click to expand...
Click to collapse
I haven't used the stock 3e that much always just flash cwm but I would suggest that you do a factory data reset to from the recovery if 3e gives that option I've never used it so I'm not sure. But if you are still on cwm recovery kies will not ever update your phone until you put everything back stock. You must have just flashed the kernel only. Flashing just the kernel does not wipe anything you need to flash the stock firmware from sammobile in Odin and that will do a full wipe and restore everything to stock
Sent from my SAMSUNG-SGH-I727 using xda premium
Sorry but what is 3e? The only place i see cwm mentioned is under the rom manager app, but when i launch it rom manager says i don't have a rooted device and super user can't be found. Weird thing is i see super user as an app on my phone.
bobbastard said:
Sorry but what is 3e? The only place i see cwm mentioned is under the rom manager app, but when i launch it rom manager says i don't have a rooted device and super user can't be found. Weird thing is i see super user as an app on my phone.
Click to expand...
Click to collapse
Turn the phone off. Hold both volume up and volume down and hold the power button do not release the volume buttons yet. Pressing all 3 buttons when you first see the screen come on mine shows an att logo then release the power button only. The phone will then boot into either 3e stock recovery or cwm recovery
Sent from my SAMSUNG-SGH-I727 using xda premium
OK, I did what you said, and I see 3e and the option to wipe data/factory reset. So you're recommending I do this BEFORE i try to use Odin and the latest firmware for Sammobile?
Just out of curiosity, if I didn't do a reset before flashing using Odin, what would happen?
bobbastard said:
OK, I did what you said, and I see 3e and the option to wipe data/factory reset. So you're recommending I do this BEFORE i try to use Odin and the latest firmware for Sammobile?
Just out of curiosity, if I didn't do a reset before flashing using Odin, what would happen?
Click to expand...
Click to collapse
Yes. And if you don't it might not wipe everything. I suggest you do it before you flash it and again after...
Sent from my SAMSUNG-SGH-I727 using xda premium
read this to return to stock http://forum.xda-developers.com/showthread.php?t=1652398
this post is just a copy paste from another post i wrote to a n00b
read, read more, read the stickies, i read alot b4 i even attempted to flash, at least a few hundred posts and using the search button.
all problems and solutions have been posted, as u r a n00b all u have todo is invest time into reading alot of posts, because of ur post we all know u havent even bothered to read the stickies, espicially read the one w/n00b's in the title, thats y they r there. .
once u know what ur r doing and r stumped at a certain problem, believe me we can tell by how u post a question, post in the q&a forum
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!