[Q] Installing CM for dummies - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi guy,
I'm a little bit upset. Since 2-3 month, my phone was a little slow and with a lot of bug. Before changing it and because I had the idea since a long time, I want to try to custom my phone with Cyanogen.
I looked a lot about mobile but i never put my hands in, so I'm not very familiar with all vocabs and different concept. So I tried to find a simple tutorial to do it.
This morning I decide to try to do it and I begin with the CM tutorial: Install_CM_for_galaxysmtd
As soon as I begun my phone doesn't have Download Mode (with Home, sound down and power button) and I am stuck... I begun looking for some solution to get download mode (I saw an other method with command line but I saw that we could brick the phone...)
And there I found a lot of different forum but nothing simple and complete (I don't understand how we could lose download mode or root from "flashing"...)
So if somebody could help me step by step to customize my phone, I will be really greatfull. I don't plan to understand everything but if I could it will be a bonus.
Thanks in advance
Guillaume

check ur fone first n make sure if ur got i9000 or 9000b or M110S or anything else

Related

bricked G1 - need some help.

i . ll just start from the beginning. i installed a jesus freke ROM on my G1, i dont remember what version. i think it was 1.41 or something like that. (RC29 or RC33, idr). i downloaded an app or maybe it was an app that came with the ROM that let me know of jesus freke's updates. i hadnt checked it awhile as the G1 is not my primary device. when i checked for it last week, it showed an update and i attempted to install it. i completely forgot the procedure for updating a new image and im prretty i bricked it because it wont go past the android screen, even after waiting about 10-15 minutes, it still wont go past it. so my question is, can somebody please help me unbrick my G1? im in no hurry as im not using it on a daily basis, but id like to get this resolved as soon as possible so i can sell my G1. anyways, id appreciate it if someone could help. if so, can you give some detailed instructions as im not TOO familiar with android. i know a little about it, but too much.
thanks guys,
josh.
if you can access recovery mode, just go and reinstall other rom, i recommend cyanogenmod - user friendly and it got a complete guide on there website to install.
youll have to expand on that a little more, like i said, im not that familiar with android.. i dont have an SD card in there, and i suppose that might pose a problem trying to flash another ROM to it.. can you give me some links and some specific directions when you have a chance..? i'd greatly appreciate it.
josh_prayyforplagues said:
i . ll just start from the beginning. i installed a jesus freke ROM on my G1, i dont remember what version. i think it was 1.41 or something like that. (RC29 or RC33, idr). i downloaded an app or maybe it was an app that came with the ROM that let me know of jesus freke's updates. i hadnt checked it awhile as the G1 is not my primary device. when i checked for it last week, it showed an update and i attempted to install it. i completely forgot the procedure for updating a new image and im prretty i bricked it because it wont go past the android screen, even after waiting about 10-15 minutes, it still wont go past it. so my question is, can somebody please help me unbrick my G1? im in no hurry as im not using it on a daily basis, but id like to get this resolved as soon as possible so i can sell my G1. anyways, id appreciate it if someone could help. if so, can you give some detailed instructions as im not TOO familiar with android. i know a little about it, but too much.
thanks guys,
josh.
Click to expand...
Click to collapse
This right here is why I say don't root if you don't know wtf you're doing. This always happens to people who should have just stayed away. Look:
Power phone completely off. Hold home key and power on. If you get to the recovery screen (the screen with a bunch of options, probably all written in green for you) then you're not bricked. All you need to do is put latest cyanogenmod on your sdcard, wipe your phone, and install it.

Trouble with Captivate.

So, recently i bought a samsung captivate, switched over from iphone and i am pretty familiar with jailbreaking iphones and able to do that. however when it comes to android phones and rooting im lost.
okay, the captivate i got from a dude off craigslist, and he said it was suped up and extra fast and rooted. i thought okay well that sounds like a great deal let me check it out. however, homie didnt tell me that he took off the original captivate software and now i have an at&t samsung captivate running on galaxy 19000 and not the original software. I am not able to find anywhere instructions on how to put the original software on the phone and get it back it the brand new factory default. I am not sure if i unroot it would that take the 19000 galaxy Os off and then the original would come back? or do i need to download the original? i cant even find that ive looked all over samsungs website.
Like i said i am pretty good with messing around with iphones and im sure if i just got a step by step instruction on how to fix my issue i could do it i just need some help from someone who knows how and where to find the tools i need to do it. I really appericiate any help you can offer. Thanks!
Phil
You can get back to stock, but the i9000 roms are much better then stock. It is likely if you like to play with your phone that you would end up flashing in no time.
What rom are you on
Settings, about phone, bottom
Find the galaxy s (not captivate drivers), then use odin 1 click downloader to revert to stock.
Step 1: install drivers
Step 2: got to download mode. Easiest way is to turn off phone, remove sim and battery, put battery back in, then hold vol up and down buttons while inserting usb. If you get a yellow android symbol that is shoveling, you're golden.
Step 3: use the odin 1 click to revert to stock. On the odin screen, you should see a com port light up and at the bottom "added". If your device is in downolad mode click start.
Step 4: set your phone down, don't touch anything, and watch the magic.
Step 5: (optional) donate to design gears, the person who will have really saved your butt.
u can try this single post if u wan to reflash to original rom..
it got everyting inside.
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Check out this thread. Also check let us know what rom you are on using the instructions some one posted above.
http://forum.xda-developers.com/showthread.php?t=887525
it's the best place to start. I wish i had started there.

[Q] 3 button download mode not working

hello
ive got a samsung galaxy s gt 19000
i want to be able to overclock my phone so i was pointed to this site.
after reading the sticky threads it says first thing first get the download mode working
ive tried loads of times and it will not work.
could someone help me out please.
need some noob guides please.
also if someone could help me clock my phone or point me in the right direction that would be great
thanks alot in advanced
also its a car phone warehouse phone
NEXT QUESTION INSTEAD OF OPENING ANOTHER THREAD
ok guys ive got my 3 button mode working fine.
what do i do next.
i want to be able to overclock my phone but when i find a thread about flashing it it says ive got to do this first so i click on that link then that says ive got to do this first etc etc
can someone point me in the right direction PLEASE!
after ive done what i need to do i will make a guide for noobs like me
Three Key Stickies .
http://forum.xda-developers.com/showthread.php?t=819551
http://forum.xda-developers.com/showthread.php?t=723596
http://forum.xda-developers.com/showthread.php?t=939752
If you want to overclock or mess with your phone and know nothing read nothing and learn nothing before you start be prepared to throw a dead phone in the bin .
So take your time and read up first .
jje
Hi, I have no 3BR either but I found an app that gives you the 3BR, it's called Quick Boot and is available in the market, hope that helps.
brian.
That app just goes to force shut down all the time
Jj i understand that you can brick your phone. Ive messed with a psp and that took days of reading. Just need to get this 3 button working and then go from there
http://forum.xda-developers.com/showthread.php?t=785201
I restored download mode on my phone using this guide, you need to read it very carefully though, as I bricked my phone on the first time trying (used odin v1 instead of 1.3), luckily if you do brick then you can use the download mode jig.
got it going ha ha now try to find out how to clock this baby
is anyone can help me with that would be great.
+1 to jjgane and DrFredPhD
http://forum.xda-developers.com/showthread.php?t=966646
just go there, you will find what you looking for
derrzredeem said:
http://forum.xda-developers.com/showthread.php?t=966646
just go there, you will find what you looking for
Click to expand...
Click to collapse
better get the reading glasses out. thanks for that
from what guides ive read through they all seem to be for people who know what there doing.
dont get me wrong i build my own computers (not exactly rocket science) and ive flished my gpu and ive flash WII's and psp's although i did have to do alot of reading on them there were many noob guides or at least semi noob guides
all seem to be going over my head a little
OP updated with another question. dont want to keep opening new threads. so if someone could help i would be grateful thank you
of reading on them there were many noob guides or at least semi noob guides
No all you can do is read whats posted first ..
Noob guides are of no use 99% of noobs dont read guides .
Overclocking most definitely advanced users .
User must be able to recover from bad flash and no how to flash via Odin via CPW update get into download mode and use a recovery jig .
The beginning posts.
http://forum.xda-developers.com/showthread.php?t=723596
http://forum.xda-developers.com/showthread.php?t=939752
jje

[Q] [SOLVED] Boot looped, Can't use Recovery mode..

Hi everyone.. after hours and hours of reading and studying on this website I really got myself into a mess and I just can't seem to climb out of it.. I desperately need some grade A help..
To be descriptive, I was trying to flash Serendipity 7, I was following the steps, used odin 3 1.7, I put all the files where they needed be, and followed it down to a tee, I pressed start, and then my phone goes into a boot loop... So I google around to look for solutions, and I thought I found one, well after I flash this "P-SBL.tar.md5" some tar file that is meant to fix the 3 button recovery mode issue. (Basically my cappy can't select anything in recovery mode due to it not having a "ok" button..) So I try it.. and not my recovery mode is littered with multi colored lines.. and I can't seem to get them to go away.
If anyone can help me I would forever be in your debt.. I would be happy just to go back to stock 2.2 if possible.. or perhaps advice on getting serendipity 7 to work.
I could make it happen if only I could get my recovery mode to work. D:
Please anyone help, I'm in dire need..
Thanks!
Search for "stock kb2 adam outler"
Then after you get back to stock, stay that way until you have done about 12 more hrs of research and reading. You were lucky that you didn't hard brick your phone, and you don't realize it. Don't just flash something because you"think"it will fix it. Know what you are flashing and what it will do to your phone. And you can call me an a#&h&$#if you want, but i believe most of the regular users here would agree me.
^
+ 100
Totally agree !!
suoh18, If....wow....whoa....dude don't be so trigger happy to flash. You were this " | " <---(that is a thin thin line by the way) to having a brick.
They need to get rid of that 3 button fix, its bricked more phones than I know, it should include both bootloaders and not just the one, I would contact Adam Outler like mrhaley said, to see if he can help, 3 button fix brick may require a jtag.
I know I was.. I was just reading what everyone was saying how easy it was.. it was my first flash and I guess it just back fired on me.. x_x
I really appreciate your help a ton, you have no clue how thankful I am.
I'm downloading what I need right now and I'm praying it works, thank you again so much.
^
Keep us posted on the end result.
I just used the program.. and it very well got my phone back on the right track. The boot looping stopped, it's back on the recovery mode that I can actually use, but after it loads it just goes to a black screen and keeps vibrating, I read that if it doesn't work the first time to check the flash bootloaders button. so I'm going to reboot one more time, then try that.
Thanks a ton guys, you really are great.
EDIT:
Which I think I need to do, because I still have a weird Galaxy S starting screen that appeared after I tried to flash serendipity.
EDIT 2:
Okay, After re-flashing the bootloaders it removed that screen that shouldn't have loaded, but I still get a black screen after the boot and nothing shows up..
I can enter and exit my recovery and download modes fine..
EDIT3:
Okay.. I went back into recovery mode and literally just wiped everything I could.. cache, user data, internal card, and after I rebooted again, viola it worked.
I'm so happy and I am seriously very appreciative. You guys are great and there has always been a reason why I respect this community so much.
Thanks again everyone that helped me, I don't know how much I can say it, but really, thank you so so so much, you are amazing.

[Q] Forgot USB-debugging downgrading

Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh
emsoh said:
Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh
Click to expand...
Click to collapse
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?
arneldna said:
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?
Click to expand...
Click to collapse
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:
emsoh said:
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:
Click to expand...
Click to collapse
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]
th3cr0w said:
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]
Click to expand...
Click to collapse
Ok, it makes me a bit more calm and Im starting to believe a bit, theres a way back for the phone to rise again. So you mean it might not be the failure of missed debugging, instead the critical main thing can be re-partiton?! It sounds very possible based on what you said.
The thing now is, ofcourse I would be satisfied if my first plan come true. But right now I really dont care what version it´ll be running, rooted or not. I only want it to act like a smartphone again n matter what´s installed. So I will go with your advise and test it one by one.
Thanx so far! To be continued..
SOLVED Forgot USB-debugging downgrading
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:
emsoh said:
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:
Click to expand...
Click to collapse
Glad to know you fixed it.. Appreciate your patience and efforts... :thumbup:
You don't care where I sent it from....!

Categories

Resources