Related
Hey guys I was was flashing up to VIPERS rom after I put the phone back to default and updated to 2.2. Well any way step by step I first did the ONE CLICK ROOT. Then I download the DK28.pit(put pit in the pit section) and I download the modem.bin (and put that in the phone section) and I forgot to uncheck re-partition. I then put the phone in download mode and it finished with no errors. Of course it bricked my phone and the only thing it would do was go into download mode!
I had never bricked my phone before and it was cause of rookie mistakes.. I was reading numerous threads about how to fix a bricked phone and it didn't seem to hard to fix. I downloaded the original firmware SPH-D700-DG27-8Gb-REL(in PDA section) and the pit file that came with it. I attempted to flash it with odin and it keep failing so I looked for a alternative route.
Finally I found a post http://forum.xda-developers.com/showthread.php?t=732199 and followed the guide to a T and everything finished up just fine.(I just figured it would work because it had all the files in ODIN) And I was positive that everything was going to work just fine! I was planing to just get it up and running and then get the phone back to its original firmware.. But now the phone will not even go into download mode..
P.S. I have tried pulling the sd card out and the battery, and while holding 1 and the power button while trying to put it in download mode(like i had to do previously) and there is no response. Any suggestions?
clem4221 said:
Hey guys I was was flashing up to VIPERS rom after I put the phone back to default and updated to 2.2. Well any way step by step I first did the ONE CLICK ROOT. Then I download the DK28.pit(put pit in the pit section) and I download the modem.bin (and put that in the phone section) and I forgot to uncheck re-partition. I then put the phone in download mode and it finished with no errors. Of course it bricked my phone and the only thing it would do was go into download mode!
I had never bricked my phone before and it was cause of rookie mistakes.. I was reading numerous threads about how to fix a bricked phone and it didn't seem to hard to fix. I downloaded the original firmware SPH-D700-DG27-8Gb-REL(in PDA section) and the pit file that came with it. I attempted to flash it with odin and it keep failing so I looked for a alternative route.
Finally I found a post http://forum.xda-developers.com/showthread.php?t=732199 and followed the guide to a T and everything finished up just fine.(I just figured it would work because it had all the files in ODIN) And I was positive that everything was going to work just fine! I was planing to just get it up and running and then get the phone back to its original firmware.. But now the phone will not even go into download mode..
P.S. I have tried pulling the sd card out and the battery, and while holding 1 and the power button while trying to put it in download mode(like i had to do previously) and there is no response. Any suggestions?
Click to expand...
Click to collapse
I hope you didnt flash JG5 to your epic. I believe this will cause a real hard brick.
If you flashed JG5, congratulations, you just killed your Epic.
Also, please read the stickies before you post. This is Android DEVELOPMENT. Questions are to be asked in General.
This is why you READ before you begin dealing with stuff like this.. The modem goes in the PDA section not phone; and if your phone can't boot; or go into download mode.. There is no hope.
Seems like you've truley bricked your phone my friend..
I did read it and it said that I needed to put the modem in the phone section. But good news is I have a new epic waiting at the repair center 4 me to pick up today.. I was practicing on the messed up one so I would do it on this one right.. I have rooted and flashed every phone I have ever had and never had a problem.. The original post I found for odin said to put the modem in the phone section..
It is pretty darn hard to brick these, even if you flash incorrectly. Try taking the battery out for 20 minutes and then putting it back in. Should get you to download mode.
I always put modem in phone, pit in pit, and the tar.md5 in pda. Always works.
Sent from my SPH-D700 using XDA App
If you're using the full .tar.md5, there's no need to place the modem.bin in the modem section; there's already a modem inside the .tar.md5.
I am pretty sure its done.. No biggie though I am going to get my new one today.. I am glad I work at SPRINT!!! It wasnt bricked until I did the JG5.. I was trying to figure out if it changed the buttons that put it in download mode but I couldn't find a combo.. oh first bricked phone in years of flashing cause I was trying to rush things
*removed 10chars
clem4221 said:
Well any way step by step I first did the ONE CLICK ROOT.
Click to expand...
Click to collapse
If you're using Odin to flash anything except a modem, it will completely wipe the phone (not the SD card, so don't worry about that) - which means performing the One Click Root before hand is unnecessary because it will be overwritten.
Also, in the future, don't start a new thread like this in the Development section - there is a Q&A thread in the Dev section that you could use, or you could post in the General section... I'm not trying to start a flame war (which seems to be what usually happens lately, lol), just trying to bring you up to speed on where to post - we have recently started a renewed effort to clean out the clutter and put an end to redundant posts, so that noobs and experienced users alike will be able to more quickly and easily find the information they need, making it easier to NOT brick your phone
Please post questions in General Section.
I think it would be nice if someone could post a screenshot guide for noobs to stop asking these questions (including me) and do the flashing back to di18 and coming back to dk28 easily. I m in the same boat.. havent flashed it yet..will be doing later today but i m **** scared that i might brick it.. no matter how many times i read and post questions.. I know it cud be difficult for pros to put together a guide but if someone can that would really cut down all the questions and numerous threads in this forum.. I can do that but once I get all the info .. and do my stuff properly only
In other news from 1993: Messageboard forums around the world introduce new feature that allows users the ability to search for already previously discussed topics.
Sent from my SPH-D700 using Tapatalk
styckx said:
In other news from 1993: Messageboard forums around the world introduce new feature that allows users the ability to search for already previously discussed topics.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
QFT
Traced with Ultra Keyboard from my *Epic*
So i was flashing the firmware to use the phone on the tab and while doing it the install failed. the tab cut off and will not come back on at all. no download mode nothing...anything can help. wont connect to odin either. any suggestions
Not come back on at all ?
Contact your service center then
Oh one thing...
When something like this happened, people call it "Bricked" not "Fu***d".
GOF007 said:
Not come back on at all ?
Contact your service center then
Oh one thing...
When something like this happened, people call it "Bricked" not "Fu***d".
Click to expand...
Click to collapse
lol i am fully aware of that just expressing how i feel about the brick and saying that it will not do anything..no download mode nothing.
thenewak said:
So i was flashing the firmware to use the phone on the tab and while doing it the install failed. the tab cut off and will not come back on at all. no download mode nothing...anything can help. wont connect to odin either. any suggestions
Click to expand...
Click to collapse
Do you get any lights whatsoever when it's plugged in?
Also, have you tried leaving it on charge for a while in the mains? Generally, when ODIN fails, the phone/tab allows you to get back into download mode, so this is new to me.
Was it flashing the radio (modem.bin) at the time, out of interest?
nprussell said:
Do you get any lights whatsoever when it's plugged in?
Also, have you tried leaving it on charge for a while in the mains? Generally, when ODIN fails, the phone/tab allows you to get back into download mode, so this is new to me.
Was it flashing the radio (modem.bin) at the time, out of interest?
Click to expand...
Click to collapse
No modem only the .tar and .pit files. i had flashed my galaxy s plenty of times with no problems. i left it charging tonight while im at work to see if that will do anything but i get no lights or anything. ive seen that some ppl get the pc to device screen but i dont get that either. but just wanted to try some things before shipping it to samsung only bc im in iraq and shipping takes forever.
Do U get anything when plugging the tab via USB to your computer ? And I do not mean Odin, I am just saying if the computer sees the USB connection.
Also, have you tried to press the POWER button and tap the screen at the same time ?
P_
pakalrtb said:
Do U get anything when plugging the tab via USB to your computer ? And I do not mean Odin, I am just saying if the computer sees the USB connection.
Also, have you tried to press the POWER button and tap the screen at the same time ?
P_
Click to expand...
Click to collapse
Nope the computer doesn't recognize it either. i get nothing at all..no i haven't tried that ...what exactly will that do?
If I bricked my Tab, I too would describe it as F***ED! But even with my moderate modding experience, Im not ready to do the phone mod. Just seems to me like too much risk.
Good luck with your Tab!
How is this a development issue? This isn't your personal support forum.
miketaylor00 said:
How is this a development issue? This isn't your personal support forum.
Click to expand...
Click to collapse
well i figured this would be an appropriate place to ask this type of ? as other ppl do. due to the fact that i was installing firmware from this section of the forums i figured i would ask the developers that read and write here.
anyways...i called samsung and told them idk why it wont cut on and they said to call it a power issue. so im going to send it to them to see if they can tell what i did..hopefully not. but we will see.
thenewak said:
well i figured this would be an appropriate place to ask this type of ? as other ppl do. due to the fact that i was installing firmware from this section of the forums i figured i would ask the developers that read and write here.
anyways...i called samsung and told them idk why it wont cut on and they said to call it a power issue. so im going to send it to them to see if they can tell what i did..hopefully not. but we will see.
Click to expand...
Click to collapse
Try leaving it connected to your computer for up to 1 hour with Odin loaded and ready on the screen.
Someone it will take time before it allow your PC to talk to it when it a messed up state due to a bad flash!
rmanaudio said:
Try leaving it connected to your computer for up to 1 hour with Odin loaded and ready on the screen.
Someone it will take time before it allow your PC to talk to it when it a messed up state due to a bad flash!
Click to expand...
Click to collapse
even if it will not power on at all?
thenewak said:
So i was flashing the firmware to use the phone on the tab and while doing it the install failed. the tab cut off and will not come back on at all. no download mode nothing...anything can help. wont connect to odin either. any suggestions
Click to expand...
Click to collapse
What were the names of the tar and pit files you flashed?
rotohammer said:
What were the names of the tar and pit files you flashed?
Click to expand...
Click to collapse
i dont see the thread on here but it was on here about a week ago. the first one that got you 3g + phone. Im not on my laptop bc im at work but do you know what im takling about.
Edit: i think it was the old JME and 512.pit...
OK just as an update and for anyone who had the same prob...as in tab will not do anything...i called samsung used the 1 yr warranty and told them it was a power issue...that i went to work it was on came home it was off and wouldnt power up so they replaced it with another one.
Okay,
There is a growing number of us XDA members on the Vibrant platform who have just bricked out phones. Save for other DEV tools, which I have not used, do not have access, and do not know how to use, for all intensive purposes, this phone is Br'iKTed ! ! !
Here are the series of events
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,
4. worked great for 2 days.
5. then on night 2, the phone was stuck on the DOW Green robot screen
6. could not get into Recovery mode (none of the recovery modes)
7. Phone would not boot
8. ODIN back to stock
9. After Vibrant screen, the phone turns off. No soft keys, Nada!
10. Flashed JI5, Ji6, Eugene's Non Bricking Froyo (ODIN Files)
11. Same result, Turned off after Vibrant
and
12. still cant' get into recovery
I am having problems with the phone starting up and loading what I flashed.
I flashed JI5 Ji6, and Eugene's non bricking Froyo Rom
These 3 are the only ones I was able to find that is ODIN flashable
Why you ask?
I cannot get into Recovery, but I can get into Download mode. I can't get into any recovery at all. NOTHING. This is why ODIN seems to be my only option.
But regardless of any ROM i flash, my phone shuts off right after the Vibrant screen. No splash screen, no loading, no booting. .Nothing. It just shuts off.
I can't charge it either.
i get a Charging bootloop. HOurglass - battery shows up for a bit, then restarts over and over.
So in other words. it's ****ed.
Hope that explains it sufficiently. if you have any more questions or suggestions, Im open man, Im open.
Help me
So I'm not sure how DEVs would like to proceed on this.
TW (I've always loved your roms. Been following you since the first BIONIX 1.8)
Morific (If it's the Kernel, i'd like to know about it)
Thanks for reading guys. I wanted to give everybody a heads up.
I don't know what the problem is, but I do know that the phone does not work.
I'd appreciate some suggestions or anything.
And to inform the community that this problem is out there. I hope there aren't any more bricked phones.
Cheers,
have you tried using odin with the repartition checked
Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks
a4 moda said:
Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks
Click to expand...
Click to collapse
have you tried to odin to ka6 or ka7? something with a bootloader
not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.
I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.
I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.
Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk
STiGLOGiC said:
not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.
Click to expand...
Click to collapse
Completely reasonable. This pertains to development because if there is an endemic problem with one of our ROMS or KERNELS (not pointing fingers, just pointing out the possibilities that I know of, there could be more), people in our community need to know. Hence, I titled it "PUBLIC SERVICE ANNOUNCEMENT"
Thanks. I hear you about Tmobile. I'd rather not have to dump my problem on Tmobile if I can fix it, because I flashed the rom. Despite the fact that Tmobile JFS leaves something to be desired, they did deliver me a working phone. So i'd like to exhaust all possibilities before calling it quits.
hackman17 said:
I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.
Click to expand...
Click to collapse
Exactly.
jaetm83 said:
I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.
Click to expand...
Click to collapse
Thanks for the heads up. I've gone through this myself many times. And i'm sure your post will help others out there. My problem (as well as many others on here with the same ROM and KERNEL I used) seems to be different and unique. Something that ODIN won't cure.
vibrant2010 said:
Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Yes, tried that too. Same result. Vibrant.. then shut off.
Thanks anyway.
I had actually just had Bionix-v 1.2.1 and the new DoW combo to try out Voodoo Sound. I really loved the sound quality, but battery drain was not adequate as being my daily driver, even though I set it to run at 1ghz and used a sleep profile. After just over 2 days of use, I backed out by ODIN'ing to JFD and I installed Bionix-v 1.2.1 again. Only thing I have noticed so far is GPS not initiating immediately after it's turned on. I would go into GPS Test app, and turn on GPS after the app is started, but I get no satellites for at least 1 min. I used to get a lock within seconds, not minutes. I will try ODIN again tomorrow and see if it fixes. I guess I was lucky enough not to get a bootloop again though.
But I can't see why you and I would have any issues after the Bionix+Dow combo. Wouldn't ODIN just clear everything up? I even repartitioned when flashing, so my guess is that my system, data, datadata, etc., are all reformatted completely? Am I missing something?
I had the same problem. I flashed DoW and then the next day my phone didn't want to turn on. I pulled the battery and restarted it. It didn't want to start up all the way. It got to the vibrant screen and shut off. luckily for me, my replacement phone that I ordered a week ago came in the same day. I sent off my old phone letting samsung/tmo take care of it.
This exact same thing happened to me.
I too had the phoen bricked after flashing the DOW after Bionix 1.2.1
I have been flashing since the G1. This is the first time I've ever bricked a phone.
Hoping to get it fixed this weekend
Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.
black spirit said:
Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.
Click to expand...
Click to collapse
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!
If you have not already done this, I recommend doing this: http://forum.xda-developers.com/showthread.php?t=954509
Bay Wolf made a nice software for the computer that pretty much shows you a step-by-step instruction on how to flash to stock, reroot, and flash the new ROM of your choice. This program will push you into download mode, clockwork recovery, etc. There is a video on that link that will also show you a step-by-step instruction. Try that out if you haven't, and let us know how it goes.
That program comes with a PIT and TAR file for you to use as well.
Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.
drewdude007 said:
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!
Click to expand...
Click to collapse
I thought the same when it happen to me.
Nothing would work, but went that approach and happy days.
s1_odin_20100512.pit
and
T959UVJFD.tar
are the only ones you need, and if your good with your flashing, just do a pit first, no pda.
And if your still getting to download mode, ect, and dont have the computer /!\ phone icon on the screen, sounds like a soft brick.
jellette said:
Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.
Click to expand...
Click to collapse
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?
SamVib said:
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?
Click to expand...
Click to collapse
Because he started off with his problem stated as:
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,
Your phone probably IS charging.
Your /efs nodes may be messed up. Do you have a backup of your /efs?
Try reading here: http://forum.xda-developers.com/showthread.php?t=859914
\\\\\\\\\\\\warning///////////
It seems that phones batch 1010 and newer dont like this method of going back to stock. If you're caught in a boot loop try flashing the official froyo for Captivate. One source can be found here
\\\\\\\\\\\\warning///////////
Disclaimer: Anything you do with the content found in this thread and the content that this thread links to, is your own choice and you are fully responsible for what happens to your phone.
This method is for ATT Captivate ONLY!
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
The purpose of this thread is to give flash addicts/custom ROMs users a more secure way to go back to stock - JF6 - without risking bricking their devices.
Do not use this if you want to send your phone back to ATT or Samsung for warranty!
Use this if you want to go back to stock before flashing a custom ROM.
Use this without worries if you changed your boot screen image or if you flashed the secondary boot loader which allows you to enter download/recovery with key combos.
This package contains NO BOOTLOADERS and NO PARAM.LFS!
Download the package from here
Download Samsung Kies and install it. It will install the latest Samsung drivers.
How to:
Remove sdcard and SIM card from the phone
Extract JF6_secure.zip somewhere.
Boot in Download Mode (see below)
Run Odin3 v1.3.exe
Click on the button PDA
Choose JF6_secure.tar.md5
Click start.
Wait and do not unplug cable until it is finished
How to boot in download mode:
There are 3 methods:
Method 1: (ADB) - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons
Plug in the USB cable and continue holding both Volume buttons
Method 3: (JIG)
Link
If moderators believe this does not belong in development, I have nothing against to moving it to General. However, I think the community would appreciate if it would remain here.
Works fine
I used this to flash the latest Continuum 3.5 and everything worked fine. Thanks!
you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered NO BOOTLOADERS! @@ YAY
Yep, updated, thanks!
Thanks for this and I appreciate all your work.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Success !!
Just used this to go back to stock prior to flashing another ROM. Worked with no problems and only took about 5 minutes. Will use this from now on to avoid the possible brick.
Again, really appreciate you providing this for us.
Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???
sircaper said:
Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???
Click to expand...
Click to collapse
Here you go again, is in the OP
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
Click to expand...
Click to collapse
on top of the read phail, i would add that you dont need to flash stock between roms, you only need to do it after a failed flash or a "no wipe" rom that depends on original files, **which they dont do anymore**. All the good full roms do a wipe before flashing. so there is no point going to stock! hope that clearifies!
icezar1 said:
Here you go again, is in the OP
Click to expand...
Click to collapse
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?
sircaper said:
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?
Click to expand...
Click to collapse
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?
icezar1 said:
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?
Click to expand...
Click to collapse
Makes sense. Is there ever an instance where those files need to be wiped, though?
sircaper said:
Makes sense. Is there ever an instance where those files need to be wiped, though?
Click to expand...
Click to collapse
Not really. Only if you flashed a boot loader from a different SGS model.
icezar1 said:
Not really. Only if you flashed a boot loader from a different SGS model.
Click to expand...
Click to collapse
Thanks. Appreciate you clearing things up for me.
Trusselo said:
you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered
Click to expand...
Click to collapse
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.
Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.
WickedNite said:
Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.
Click to expand...
Click to collapse
Yes, is OK
Has anyone flashed the three button fix? I really want to. just wanna verify its ok.
likiud said:
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.
Click to expand...
Click to collapse
take a look here
double RL said:
Has anyone flashed the three button fix? I really want to. just wanna verify its ok.
Click to expand...
Click to collapse
You dont have the 3 button fix?
EDIT: yes, is OK, I tested it. Make sure you run a md5 checksum after putting it on your sdcard
so i had a rooted s3 which is now my old phone and wanted to return it to stock for sale.
i start by unrooting the phone (now realise this should of been done last)
i then tried to flash the stock firmware on with odin however keep getting stuck at NAND write start (i have tried using different PIT files and kies is all closed down)
i can get to recovery and download mode but nothing else. cant install any roms from recovery.
is there a way i can root the phone again to get a rom on it? its not found by the pc when trying to use s3 toolkit or abd devices
Thanks
viper1402 said:
so i had a rooted s3 which is now my old phone and wanted to return it to stock for sale.
i start by unrooting the phone (now realise this should of been done last)
i then tried to flash the stock firmware on with odin however keep getting stuck at NAND write start (i have tried using different PIT files and kies is all closed down)
i can get to recovery and download mode but nothing else. cant install any roms from recovery.
is there a way i can root the phone again to get a rom on it? its not found by the pc when trying to use s3 toolkit or abd devices
Thanks
Click to expand...
Click to collapse
You are posting in the wrong forum see sticky top of the page .
Problem reads as you need a new motherboard or you can read multiple identical posts re NAND.
doesnt matter fixed it now anyway, just used the kies recovery
Thanks anyway
1 wrong section
2 u dont need root to install any roms.
3 He dont need new motherboard. Wth r u talking about?
Just use usb from backside of ur pc. NO from keyboard or hub, frontside. Just backside usb port and flash any rom u want.
maqikpl said:
1 wrong section
2 u dont need root to install any roms.
3 He dont need new motherboard. Wth r u talking about?
Just use usb from backside of ur pc. NO from keyboard or hub, frontside. Just backside usb port and flash any rom u want.
Click to expand...
Click to collapse
U nid root to flash roms
Sent from my GT-I9300.
Give a thank if i helped you
I had the same problem on trying to 100% clean my phone since its freeze on locking unlocking and I turn it on it reboots like 10 times and then I just bought an external card with a USB thing to put it inside and conect it to my PC which allowed me to get cmw/rom/ etc and re do it all again.
JJEgan said:
You are posting in the wrong forum see sticky top of the page .
Problem reads as you need a new motherboard or you can read multiple identical posts re NAND.
Click to expand...
Click to collapse
New motherboard? And you wonder why I dismissed advice from you calling you intolerant when you give wrong, lazy and bad advice like that.