Hi!
I cant find my Stock ROM.(S5570B).
If i will install other ROM stock,will it brick?
**S5570B,but not my, cause i cant find it(S5570BJJKQ5)
Have you searched for it at androidangel or samfirmware?
Installing another stock rom, as long as it matches pda, phone, csc or just an upgrade e.g. 2.2 to 2.3, should not brick it. Now, flashing CWM from Rom Manager reportedly bricks it. So you should be real careful about it and follow guides already posted.
galaxymny said:
Have you searched for it at androidangel or samfirmware?
Installing another stock rom, as long as it matches pda, phone, csc or just an upgrade e.g. 2.2 to 2.3, should not brick it. Now, flashing CWM from Rom Manager reportedly bricks it. So you should be real careful about it and follow guides already posted.
Click to expand...
Click to collapse
if i will install an update to 2.3.6
I will not brick?
Last time i used ROM manger,I have bricked my phone....
Do the update through Kies and rest assured you will not brick it. I updated 2.2 to 2.3 through Kies for a friend's Mini and it was a successful update. It's the safest option you can try.
galaxymny said:
Do the update through Kies and rest assured you will not brick it. I updated 2.2 to 2.3 through Kies for a friend's Mini and it was a successful update. It's the safest option you can try.
Click to expand...
Click to collapse
I hate KIES.
He wont recognize my phone...
I Want to update using this:
http://forum.xda-developers.com/showthread.php?t=1255305
Is it safe?
Oh yes, ODIN is perfectly safe as long as you stick to instructions. I used ODIN yesterday just to flash tj_style CWM to my Mini and it was problem-free. Of course, I speak about my experience so just don't put the blame on me if the case something cropped up for whatever reason. But, yes ODIN is a safe bet.
Related
Ok so i would like to update my galaxy to 2.3 gingerbread official using keis.
I live in Australia and based on what i have read the update should be out on my model of galaxy. When i plug my phone into keis it is saying i have the latest firmware. I have done some reading up on this and if i am correct some of the hacks and things i have done to my phone could cause it not to be able to update and i would like to know if this is true and how i can fix this.
Things i have done:
- I am currently running 2.2 froyo
- I have voodoo lagfix and soundfix installed.
- I used sgs tools from market to use the optus apps which came with my phone that where unusable since i was with virgin.
- I applied a 3 button fix i found as well so i could update voodoo easier. But in the end i just used Odin.
One thing i read was that i have to restore the system apps to update it. which i have done with all accept one but the .apk backup for it is not working so i cannot. Will i have to use Odin and revert back to the original firmware and start again? Or is there something i can do from here?
Short answer- You can't.
Gingerbread isn't out officially anywhere at present (there was a brief period where it was out on Kies for Scandinavia- hence all the semi-official "leaked" roms).
On past performance we're likely to be waiting a fair while here in Oz- once Official GB Roms come out from Samsung you then have to wait for all the local carriers to add their garbage to it (and - according to them- "test" it) before it gets released on kies. I'd bite the bullet and just grab a nice rom from here.
Remember if you do decide to wait for the official update, you will have to downgrade to stock for kies to recognise your right to an upgrade.
+ 120 to that NO upgrade to 2.3.3 YET .
All upgrades are unofficial .When Kies has your upgrade it upgrades
Then before update undo lagfix .
Or to be really safe reinstall your original saved rom the one you saved before you started messing with the phone .
jje
I think using odin to flash a stock rom back before updating by kies would be safe way
myfifth said:
I think using odin to flash a stock rom back before updating by kies would be safe way
Click to expand...
Click to collapse
Depends Kies does not recognize stock rom as product code etc dont match = no update through Kies . Stock is not network supplied firmware as original .
jje
JJEgan said:
Or to be really safe reinstall your original saved rom the one you saved before you started messing with the phone .
jje
Click to expand...
Click to collapse
Lets just say I'm a total wanker and I didn't save my original rom. Am i stuck using custom roms from now?
Zeruf said:
Lets just say I'm a total wanker and I didn't save my original rom. Am i stuck using custom roms from now?
Click to expand...
Click to collapse
pretty much, unless some one has official firmware
I just got my phone back from repairs and I would like to create an odin rom out of it. Is it possible?
As of now, there is no way of backing up firmware entirely. However, there are firmwares out for every region and virtually all regions have received a 2.2 or 2.2.1 upgrade which can be applied through Kies or Odin.
Click to expand...
Click to collapse
you can root and make a nandroid backup and apply that in case you need to send back.
but the best option is just flashing stock FW from samfirmware.com in ODIN
Flashing stock firmware from samfirmware actually bricked my phone completely
Just now ? or before you sent it off for repairs ?
you probably didnt flash the rom properly, that what caused the brick, there are many variations of a bricked phone, yours could of been fixable.
anyway, the 2 options in my above post are the only options (i think) i did a search but found no answers other than them 2
You can make an Odin flashable rom Darkky has a guide here http://forum.xda-developers.com/showthread.php?t=960946
I got it to work, the guide doesn't always make it clear whether commands should be on the the phone or computer though.
DrFredPhD said:
You can make an Odin flashable rom Darkky has a guide here http://forum.xda-developers.com/showthread.php?t=960946
I got it to work, the guide doesn't always make it clear whether commands should be on the the phone or computer though.
Click to expand...
Click to collapse
Hmmm never seen that before, thats interesting. i think this would be a great way for the OP to backup the rom doesnt sound too tricky - the codes seem a little confusing but you can copy and paste
Its whats missing in Kies full backup of phone and firmware .
jje
I was just wondering I just recently bricked my last Captivate luckily At&t replaced it for free but im not sure how many more times thats going to work. My idea was that the brick occured from a suspicious looking 2.3 odin file but im not sure if that bricked it. Should I try flashing with the same computer but with a diferent 2.3 odin? I got a new one heres the link.
http://forum.xda-developers.com/showthread.php?t=1129821
Edit: forgot original package that bricked my phone.
http://forum.xda-developers.com/showthread.php?t=1232703
voldomart13 said:
I was just wondering I just recently bricked my last Captivate luckily At&t replaced it for free but im not sure how many more times thats going to work. My idea was that the brick occured from a suspicious looking 2.3 odin file but im not sure if that bricked it. Should I try flashing with the same computer but with a diferent 2.3 odin? I got a new one heres the link.
http://forum.xda-developers.com/showthread.php?t=1129821
Edit: forgot original package that bricked my phone.
http://forum.xda-developers.com/showthread.php?t=1232703
Click to expand...
Click to collapse
A hard brick occurs when you flash incompatible bootloaders. Make sure you flash the gingerbread bootloaders first (either the i9000 bootloaders or 2.3 captivate bootloaders) with odin then flash your gingerbread rom. There are odin packages that include just the bootloaders. Hope that helps.
Sent from my SGH-I897 using xda premium
Yeah it kinda helps im gonna wait though and buy a usb jig just so im ready if anything does manage to go wrong. Thanks though i didnt know that.
See with the package i used that bricked my phone it got stuck in a certain stage and wouldnt go anywhere so i tryed unpluging it and try to go back to 2.1 but after that attempted 2.3 flash it wouldnt accept any odins.
A hard brick not only happens with incompatible bootloaders, but with an incomplete bootloader flash, which is what happened, you say it stopped at a certain point, that is more than likely where it bricked. That package isn't "suspicious", if it were there would be a lot of reports about it.
The first link you posted is bootloaders only. It will not flash 2.3 firmware at all. Just the boots.
To make sure odin doesn't stall out, use a port on the back of the pc, right click odin and run as admin.
What studacris said. Keep in mind there is always a small risk on flashing that Odin fails. So once you flash Gingerbread bootloaders just don't flash any bootloaders again unless you really need to. OR Look in to the Unbrickable mod if you want that.
Just askin how long would ikt take to flash just the gb bootloaders?
Less than a second. Its a very small risk to begging with BUT a risk none the less.
ANother question is there any danger in downgrading bootloaders?
Same as upgrading. No reason to Downgrade except maybe AOSP specific kernels or warranty.
I had to right now because of a bootloop and a failed custom rom install and none of my backups worked and i couldnt install anything else. It said on clockworkmod that it couldnt read my cache folders. Did i have to go back to 2.1? Because thats what i did. Also thank you guys for answering my questions the captivate is so much more complex that the droid when it comes to custom roms and stuff like that.
voldomart13 said:
I had to right now because of a bootloop and a failed custom rom install and none of my backups worked and i couldnt install anything else. It said on clockworkmod that it couldnt read my cache folders. Did i have to go back to 2.1? Because thats what i did. Also thank you guys for answering my questions the captivate is so much more complex that the droid when it comes to custom roms and stuff like that.
Click to expand...
Click to collapse
No there are Odin packages that Do not include bootloaders, just saying. Same as there is GB packages without bootloaders as well (this goes for KF1 and KH3 to my knowledge). Once you flash GB bootloaders there is no reason to reflash bootloaders except for AOSP specific kernels and Warranty.
Hi, i'm new to all of this flashing stuff. I'm running CM7 on my captivate and i was just wondering if GB for it came out for it, would i have to flash back to stock before i can update or can i just update out of CM7? While i was trying to flash this CM7 i had problems and had to keep on flashing back to the stock rom(2.1) and when i ever i tried to do a upgrade on kies the phone wouldn't sync because it would just keep crashing.
CM7 is GB. The only ROM you could flash would be MIUI without going back to stock.
Sent from my SAMSUNG-SGH-I897 using XDA App
Like said you can only flash MIUI. Everything else needs to flash back to a stock because you need to repartition your phone. Gingerbread has not been released officially for I897 but it has for I896. Though none official there are a ton of Gingerbread leaks on the dev section.
prbassplayer said:
Like said you can only flash MIUI. Everything else needs to flash back to a stock because you need to repartition your phone. Gingerbread has not been released officially for I897 but it has for I896. Though none official there are a ton of Gingerbread leaks on the dev section.
Click to expand...
Click to collapse
But when i flash back to stock(2.1) it won't let me sync with samsung kies. on the phone it just keeps opening and closing USB MTP or something
Why do you want to sync on 2.1? If you are going to flash a GB rom.
prbassplayer said:
Why do you want to sync on 2.1? If you are going to flash a GB rom.
Click to expand...
Click to collapse
I'm already flashed on CM7. But I'm just wondering when the official At&t GB update comes out for the Captivate, i wanna know how i would update to it. Wanna just try it out. And whenever i did the one click restore and go back to 2.1 it would never let me sync with kies.
RLeWorm said:
I'm already flashed on CM7. But I'm just wondering when the official At&t GB update comes out for the Captivate, i wanna know how i would update to it. Wanna just try it out. And whenever i did the one click restore and go back to 2.1 it would never let me sync with kies.
Click to expand...
Click to collapse
You might be able to update straight from CM7 and do just fine. However, I would advise and I think others would too, to flash back to stock using odin one click. Have all of your stuff backed up externally, run a master clear, and then attempt the update. This is a surefire way to have nothing go wrong as you are coming from factory software.
Reboot your PC and try Kies again. And I think its Kies Mini that does the update not the full Kies program. But its not a special process. They walk you through it and if you can flash a custom rom you will have no problem with the kies mini process.
att gingerbread isnt officially out and YEAH right they would ever give a date....
also dont use keis for anything keis sucks!. use xda site. read xda site. read new user guide (below). read STICKES (explained in guide).
flash back to 2.1 ( or any stock with .pit file or "one-click odin" stock flash)
odin flash (NOT one click) gingerbread bootloaders (find in dev section of captivate)
odin flash (NOT one click) a kernel with cwm built in
cwm flash ANY captivate rom from dev section
---------- Post added at 08:39 PM ---------- Previous post was at 08:39 PM ----------
capocaccia said:
You might be able to update straight from CM7 and do just fine. However, I would advise and I think others would too, to flash back to stock using odin one click. Have all of your stuff backed up externally, run a master clear, and then attempt the update. This is a surefire way to have nothing go wrong as you are coming from factory software.
Reboot your PC and try Kies again. And I think its Kies Mini that does the update not the full Kies program. But its not a special process. They walk you through it and if you can flash a custom rom you will have no problem with the kies mini process.
Click to expand...
Click to collapse
cm7 uses a different partitioning table. STOCK IS A MUST to go backagain KIES IS ****
there are odin one- clicks for 2.1 2.2 and kf1 2.3.3 leak
DONT USE KEIS NO REASON TO IT SUCKS BALLS
This guy seems a little new to the scene so I wasnt going to throw him into the Odin stuff just yet. Its good to know about and while kies isnt the best it is the factory software and is easy for new people to use.
Doesn't matter if he is new. He decided to use CM7 and/or MIUI you NEED to repartition your phone. Kies is just a different UI ODIN with alot of extra checks that are useless. If he wants to move back to I897 roms or to I9000 ports he has no choice on the matter. But like everything else always a good idea t have a Jig just in case and try to use packages that DO NOT include bootloaders when ever possible (not sure if you need to flash bootloaders if you partition)
TRusselo said:
att gingerbread isnt officially out and YEAH right they would ever give a date....
also dont use keis for anything keis sucks!. use xda site. read xda site. read new user guide (below). read STICKES (explained in guide).
flash back to 2.1 ( or any stock with .pit file or "one-click odin" stock flash)
odin flash (NOT one click) gingerbread bootloaders (find in dev section of captivate)
odin flash (NOT one click) a kernel with cwm built in
cwm flash ANY captivate rom from dev section
---------- Post added at 08:39 PM ---------- Previous post was at 08:39 PM ----------
cm7 uses a different partitioning table. STOCK IS A MUST to go backagain KIES IS ****
there are odin one- clicks for 2.1 2.2 and kf1 2.3.3 leak
DONT USE KEIS NO REASON TO IT SUCKS BALLS
Click to expand...
Click to collapse
+1 Kies is beyond **** !!
I can imagine how many people get stuck with that complete "no use" piece of sftware. It is so useless, it just unnecessarily occupies internet space !!!!!!!!!!!!!!!
prbassplayer said:
Doesn't matter if he is new. He decided to use CM7 and/or MIUI you NEED to repartition your phone. Kies is just a different UI ODIN with alot of extra checks that are useless. If he wants to move back to I897 roms or to I9000 ports he has no choice on the matter. But like everything else always a good idea t have a Jig just in case and try to use packages that DO NOT include bootloaders when ever possible (not sure if you need to flash bootloaders if you partition)
Click to expand...
Click to collapse
You should not need to flash bootloaders if the only thing you are doing is going from CM7 to stock based GB ROM. And I believe GB bootloaders are backwards compatible to 2.2.
OP, since you are on CM7, you WILL need to flash back to stock in order to get back to Samsung ROMs, as the phone must be repartitioned.
astroZ0MB1E said:
You should not need to flash bootloaders if the only thing you are doing is going from CM7 to stock based GB ROM. And I believe GB bootloaders are backwards compatible to 2.2.
Click to expand...
Click to collapse
OP didn't indicate whether he has installed i9k GB at any point; to be 100% correct:
If OP flashed CM7 straight from Eclair/Froyo, he will need to flash GB bootloaders for a Galaxy S device.
IF OP has previously flashed i9k or i897 leaked GB, then he does not need to flash new bootloaders ever again.
Dear folks
When Samsung released their ICS update I was so exited but it wouldn't update mine since mine has csc lux so I had to wait till they released it for my country.
So the German version came online and I used PC Odin to get my phone to ICS with the German release. (So I flashed it? New to this)
Now I'm assuming that ICS is out for my country OTA or with Kies. So I want to use one of both to upgrade my phone so I have the stock and don't risk anything.
So you've probably seen the question coming, how do I get back to stock GB so I can update it afterwards with Kies or OTA.
Please take note that I'm a complete newb in this.
Thanks in advance!
You will have to use PC Odin to go back to stock Gingerbread.
Go here to find your stock rom for your country and download it:
http://forum.xda-developers.com/showthread.php?t=1424997
You probably had to Odin to the ICS version you are on now, so if you remember how you did that, it's the same thing in Odin.
After you have that stock Gingerbread you should be able to check for updates and get your official OTA or Kies ICS.
andreww88 said:
You will have to use PC Odin to go back to stock Gingerbread.
Go here to find your stock rom for your country and download it:
http://forum.xda-developers.com/showthread.php?t=1424997
You probably had to Odin to the ICS version you are on now, so if you remember how you did that, it's the same thing in Odin.
After you have that stock Gingerbread you should be able to check for updates and get your official OTA or Kies ICS.
Click to expand...
Click to collapse
i'm tired of waiting and with the new asian builds i just wanna update but coming from ios (just had my note for 2 weeks) i don't wanna mess up.so just download stock india rom for example use pc odin to flash and follow dr ketan tutorial to root?how about the modem (baseband), kernel and my unlock?do i have to worry about losing the unlock?thanks
So country is what my csc says right? Cause I bought it in Belgium (where I live) but my csc says lux
You *must* flash a safe kernel first, reboot the phone again into download mode then you can flash your old GB ROM.
If you don't do that, you can trigger the emmc bug in your current ICS kernel and fry the internal memory, unless you're using a CM9-based kernel then you're safe.
life.eq.null said:
You *must* flash a safe kernel first, reboot the phone again into download mode then you can flash your old GB ROM.
If you don't do that, you can trigger the emmc bug in your current ICS kernel and fry the internal memory, unless you're using a CM9-based kernel then you're safe.
Click to expand...
Click to collapse
Could you translate to noob friendly language? With a safe kernel you mean a safe rom or? I googled DL mode so got this and the last part to but the other piece of text is unclear
Can i Just flash s stock GB?
Sent from my GT-N7000 using XDA