Hi,
I'm considering flashing CM7.. I've flashed plenty of ROMs but they've all been based on stock samsung ones. If I give CM7 a go are there any risks other than the usual ones (i.e bootloaders, odin fails)..?
Will I need new usb drivers? and can I easily revert back to a Samsung ROM?
Thanks
You'll need to get the Nexus S USB drivers. I did a Google search at the time, which bought up a thread on here with a direct link. Otherwise you can use the drivers bundled with the SDK. Either way, they aren't hard to find.
There aren't any major risks that I know of. I've been running it just fine for 3 weeks now.
That being said, I haven't attempted to flash back to another rom yet. I don't foresee any major issues, though. Just gotta make sure I wipe everything, repartition, and that should clear it all up.
msolus said:
Hi,
I'm considering flashing CM7.. I've flashed plenty of ROMs but they've all been based on stock samsung ones. If I give CM7 a go are there any risks other than the usual ones (i.e bootloaders, odin fails)..?
Will I need new usb drivers? and can I easily revert back to a Samsung ROM?
Thanks
Click to expand...
Click to collapse
There are no problems with CM7 other than the well documented ones, ie patchy camera, increased battery drain. If you have flashed JV1 or JVK you will need to flash a stock froyo with bootloaders first, if you are on stock froyo ROM just go ahead and flash it!
Reverting is straightforward. The risks are minimal, as long as you can get download mode with the 3 buttons you can always flash back to stock. Just follow the instructions on the CM7 thread in android development forum
Sent from my GT-I9000 using XDA App
I installed speedmod kernel and perception 10.4 together in CWM. And i tried to restart the phone but it won't start. Screen doesn' t even light up. What do i do now ??? I have no warranty either.
If there is nothing that could be done is there a place to sell it for some bucks ??
You have a bricked bootloader which can be fixed through JTAG restoration. If you are interested just PM me. Same goes for anybody else in this situation...
Yes please. Let me know. I am dying to turn this on again. Thanks.
i am just wondering what exactly you did. by 10.4 do you mean the 2.3.3 perception beta that came out on the 10th of april or some other 10.4 version. if it was the perception 2 beta thats a 2.3.3 (or 2.3.4 cant remember) whereas speedmod kernal is for the original bootloaders and 2.1 and 2.2 you cant mix and match like that. and before you go and buy a jig from the guy above realize that your original 3 button combos arent the same as the ones from g12. try holding volume down the home soft key and power or volume up and power. if clock work (up and power) works then reflash g12 if download workd (android and shovel) plug it into computor and flash to stock using oden. if NONE of these things work buy the jug or buy a 301ohm resistor and build it yourself theres lots of tutorials
Perception 10.4 is the most stable version of FroYo perception.
Installing that after running GB without reinstalling the 2.1/2.2 bootloaders will brick. But if you never installed GB, or installed the 2.1/2.2 bootloaders first then your problem is elsewhere.
What were you running before you installed perception + speedmod? I'm guessing GB ROM of some flavor. If not, then it shouldn't be a bootloader issue.
Sent from my Captivate running GR-12
quarlow said:
Perception 10.4 is the most stable version of FroYo perception.
Installing that after running GB without reinstalling the 2.1/2.2 bootloaders will brick. But if you never installed GB, or installed the 2.1/2.2 bootloaders first then your problem is elsewhere.
What were you running before you installed perception + speedmod? I'm guessing GB ROM of some flavor. If not, then it shouldn't be a bootloader issue.
Sent from my Captivate running GR-12
Click to expand...
Click to collapse
Does perception have a froyo sbl.bin? Otherwise just flashing a froyo rom will not result in a hard brick at all. Gingerbread bootloaders are backward compatible as long they both match ... So if perception doesn't have any bootloaders at all and not just the froyo secondary bootloader it should be fine to flash from gingerbread. As long as you flash it from cwm 2.5 because cwm3 doesn't seem to want overwrite the kernel, but that won't even cause a hard brick just a bootloop, so you could odin a kernel after that and be golden.
the only thing that will cause a hard brick is either a plane old bad write/disconnection while the bootloaders are flashing. Which means, are you ready for a jaw dropper? odin one click is just as dangerous as flashing gingerbread!!!
Or now that there are new bootloaders the mixing if primary of froyo and secondary of gingerbread.
studacris said:
Does perception have a froyo sbl.bin? Otherwise just flashing a froyo rom will not result in a hard brick at all. Gingerbread bootloaders are backward compatible as long they both match ... So if perception doesn't have any bootloaders at all and not just the froyo secondary bootloader it should be fine to flash from gingerbread. As long as you flash it from cwm 2.5 because cwm3 doesn't seem to want overwrite the kernel, but that won't even cause a hard brick just a bootloop, so you could odin a kernel after that and be golden.
the only thing that will cause a hard brick is either a plane old bad write/disconnection while the bootloaders are flashing. Which means, are you ready for a jaw dropper? odin one click is just as dangerous as flashing gingerbread!!!
Or now that there are new bootloaders the mixing if primary of froyo and secondary of gingerbread.
Click to expand...
Click to collapse
DG has been known in the past to package sbl.bin's in his ROM's. I'd suspect a 2.1/2.2 sbl.bin was flashed with the 2.3 boot.bin. That will equal brick every time.
connexion2005 said:
You have a bricked bootloader which can be fixed through JTAG restoration. If you are interested just PM me. Same goes for anybody else in this situation...
Click to expand...
Click to collapse
He is the man. He fixed it for me. Unbricked it. You can trust him..
I'm having a bit of trouble with Odin one-click. Last night I decided to upgrade from Perception 10.4 (Froyo based) to Perception 2b3 (Gingerbread based). I plugged it in, put it into download mode, and activated Odin. It ran just fine, but at the end, my phone rebooted into a boot loop. I ended up putting together a jig to get it back into download mode, and tried again. Same thing happened. I eventually ended up using a Froyo Odin to qwerty least get it working again. Does anyone have any ideas as to why Gingerbread Odin soft bricks my phone, and what I should do to fix it? Let me know if you need any more details. Thanks in advance.
I know this would do better in the odin thread, but I don't have enough posts to post there, mending the fact that I've been lurking around for close to a year
Guess I'll just keep posting here until a) someone responds or b) I have enough posts to ask in the proper thread
I'd ready like to be able to get my cappy running Gingerbread tonight. Anyone have any ideas?
What one click are you taking about? Is it this one?
http://forum.xda-developers.com/showthread.php?t=731989
If it is, this will take you to stock eclair. Not sure what ur talking about with one click froyo. There is a one click GB from Design Gears in the development section. It flashes the newest release of GB stock. If you can get into dl mode you can flash either of the one click odins, but read about both before you do. Bootloaders are involved, and if you don't know about them they can be trouble. Read in development section.
This is a link to one click for GB stock. CONTAINS BOOTLOADERS.
http://forum.xda-developers.com/showthread.php?t=1127249
Sent from my SAMSUNG-SGH-I897 using XDA App
Sorry, for some reason can't get that second link to work properly. Doing this from my phone. Just type in the url. If you decide to flash this GB oneclick, you'll be on the kf1 "official" release. Check dev section and you can flash beta cognition if you want. People are having great results with this rom, including myself. Good luck.
Sent from my SAMSUNG-SGH-I897 using XDA App
I recommend flashing the KF1 odin one-click. I just flashed that one, and it worked like a champ. Its in the Continuum v6 thread at http://forum.xda-developers.com/showthread.php?t=1136128. If you read the instructions it will work flawlessly. The only odin problems I've ran into have been user induced.
Okay, I'll try out that KF1. All I really need it for is to get the bootloaders so I can install other 2.3 roms. Will this work for that?
The Froyo Odin I was tackling about was just an older version, I think.
Edit: Why is it so much more difficult to go from 2.2 to 2.3 than it was going from 2.1 to 2.2? Upgrading to 2.2, I just had to use CWM to flash the new rom onto the phone.
Okay, I was trying to follow the instructions in the Continuum thread, and it looks like I am supposed to go back to Eclair before flashing Continuum. I was using this one-click Odin, and it was causing my phone to softbrick. No idea why. Will I be able to use that KF1 Odin to get to Gingerbread, then flash other GB based roms?
And by the trouble caused by bootloaders, you just mean how it will hardbrick if it loses connection in the middle of flashing, right? Or is there more. I've been switching out roms on phones for a while now, but it hasn't been this complex before...
If you mix bootloaders, you will hard brick ur phone. 2.1/2.2 roms have the same bootloaders. GB boots are different. That's why there is more involved to flash GB roms. Basically all the GB roms are I9000 based roms. The kf1 is an i897 based stock rom. If you flash kf1 stock rom, you will lose cwm. You can try cog beta 2 rom if you would like. After following steps to flash GB bootloaders with link mentioned above, check dev section. There are currently 2 kf1 custom roms. I use the cog beta 2, and it works great. people have mentioned that they have flashed i9000 roms over kf1, but I personally haven't, cuz so far cog beta is working great and the call quality is outstanding compared to any of the i9000 roms. Read read read read, before taking any steps. You don't want to ruin it phone! If you want to flash i9000 based GB, read this:
http://forum.xda-developers.com/showthread.php?t=1045734
Btw, what build is ur phone? (4 digit number under battery). Some builds, especially 1010 have trouble with oneclick.
Sent from my SAMSUNG-SGH-I897 using XDA App
So it sounds like what I need to do is use that KF1 Odin, then I can flash other roms over that? How can I tell which custom roms are KF1? Is Perception KF1 based? What would you recommend I read to make sure I'm doing it right? Are there specific threads that are especially helpful for this? Thanks for all of the help, I'd really like to learn how to do this.
It'll say in the title. Liked I said, currently there are only two kf1 based roms. Cog beta and another one that I can't remember the name of. If it says something in the title besides kf1/or i897, it's for i9000. Ex/ jvh, jvo, jvp are all i9000 based.
Sent from my SAMSUNG-SGH-I897 using XDA App
What do I need to do if I want to use a non-KF1 based GB rom? I've been very happy with Perception, and I'd like to keep using it.
If you want to flash GB stock that is based off of I9000 read and follow this, step by step:
http://forum.xda-developers.com/showthread.php?t=1045734
After you do this you can flash GB roms via cwm.
If you want to flash GB with kf1, you can, and people have been running I9000 based custom roms on the same bootloaders. JUST MAKE SURE YOU CHECK ANY ROM YOU'RE FLASHING TO SEE IF IT INCLUDES BOOTLOADERS. I personally haven't run any I9000 roms after flashing kf1, but I believe if you want to do this, (NOT POSITIVE ABOUT THIS, SO YOU MIGHT WANT TO RESEARCH THIS FIRST) you would have to flash an appropriate I9000 kernel using odin (not oneclick, but the full version). Put the kernel in the PDA slot, uncheck repartition, and auto reboot and flash. That way you will get cwm 2 or3 back which will enable you to flash the rom you want. (Remember, with stock KF1 you lose cwm). After kernel flashes, boot ONLY into recovery, and flash rom that you put on your SD card before doing any of this, and flash via cwm. AGAIN, NOT POSITIVE THIS IS WHAT YOU DO, SO RESEARCH.
That makes a lot more sense than the instructions I was trying to follow. I'll try that in a bit.
It worked! Thanks for all of your help
What did you end up doing? GB I9000 stock, or kf1 then flash I9000 custom rom over it?
Sent from my SAMSUNG-SGH-I897 using XDA App
I used the I9000 GB stock rom from that link you posted, then flashed a custom rom over it. I ended up using Perception 2 beta.
Glad it worked for you.
Sent from my SAMSUNG-SGH-I897 using XDA App
does this fix still exist? Every link I look on has a dead file link.
AIO toolbox has it. But I would recommend just flashingg I897 Gingerbread bootloaders.
I concur with prbassplayer. I know it's not the link you're asking about, but frankly, there have been a lot of hard bricks on here as a result of trying to use that 3-button fix. If you're planning on staying in the custom rom world, you'll probably be best off to just flash over to a set of Gingerbread bootloaders (depending on the rom you're going for), and not looking back, as the GB bootloaders will fix the 3-button issue as part of their installation.
my story is flash stock 2.1 rogers i896, then miui latest. Use to have the 3 button until I pooched the rom and had to reflash 2.1 and back to miui
I897 GB loaders work with MIUI. I am using them now. Also gives you the flexibility to flash the other GB roms later.
Hi Everyone,
I have a Rogers Captivate and coming from CM7, I would like to try MIUI. However, I feel like I should restore my phone back to stock before I do so. I've looked into doing it, came across this thread and I just want to double check on my thought process...
I am going to use ODIN3 one-click 2.3.3 (with bootloaders) to restore to Rogers 2.3.3 stock and then flash MIUI afterwards. Is this wrong? Do I need to worry about bootloaders since I have CM7?
Thanks in advance!
If you are on cm7 now, there's no need to go back to stock. Just back up your stuff, do a factory reset and flash MIUI. Bootloaders are not that important on MIUI, but I wouldn't recommend I9000 Bootloaders.
Oh OK, good to know. I'm assuming the only way to get I9000 Bootloaders is to flash a I9000 ROM? If that's the case, I think I'm OK. I think I will still go back to stock. I feel like I need a complete refresh of my phone (peace of mind, haha). Thanks for your help.