WiFi Dead? Galaxy Tab GT-P1000 [SOLVED] - Galaxy Tab Q&A, Help & Troubleshooting

What's good, chaps? This problem is currently on Overcome 4.1.0--beautiful ROM.
So what had happened was......
My Tab's WiFi worked perfectly, until yesterday (from the time of this post). Before this problem occurred, I had tried to flash a file I though would be useful for the Tab. The file sent my Tab into bootloops, and I scolded myself for not having made a nandroid.
I decided it'd be a good chance to try another ROM.
I eventually lighted on MIUI v4. I liked it for 5 minutes, then wanted to go back to Gingerbread (Overcome). I read that the MIUI ROM was an MTD ROM; I have no idea what that is, heh.
The only way to return to Gingerbread was to use Odin, so I did that. I followed every instruction on flashing the Overcome ROM to the letter. The installation went smoothly....until I found out my WiFI is broken. In fact, the baseband comes up as unknown--that never happened before. The Tab was getting a cellular signal, but that was it. I tried to reinstall the modem using Odin--no good. I tried using the fix from the Overcome Thread--no good.
I don't know what's wrong or what to do next.
If anyone can help me shed some light on this, it'd be greatly appreciated!
Thanks in advance!

I don't know why most people will try to fix their broken tab using overcome rom, find it broken but didn't tell how it was when it was merely on SG-stock-safe-v5
remember, Gb-stock-safe-v5 is Gingerbread from Samsung, JQ1 rom, in fact.
If it is broken at that stage, it is an entire different story than if it broke under Overcome ROM.
So which one is it?

Sorry for my late reply!
I found out it was broken when I reflashed the Overcome ROM. I never tried WiFI when I flashed GB-Stock-Safe-v5, so I can't tell you anything from there.
Did I do the right thing in using Odin, when downgrading from ICS 4.0.4 to GB 2.3.6?

No idea. But re-do the GB-stock-safe-v5 again and see how it goes.
If all good, add overcome kernel, see again how it goes.
if all good, flash overcome rom, and then see again.
Be methodical when you want to find your root cause.

Alright, I'll give it a go. Thanks for your help!
For the record, does downgrading from flashing a ROM with a different partition set-up have to be done a certain way?

just need a rom that has pit file and you tick the repartition in Odin.
That should take care of the downgrading from MTD rom

Followed your instructions and everything is back to normal!
Thanks again!

priyana said:
just need a rom that has pit file and you tick the repartition in Odin.
That should take care of the downgrading from MTD rom
Click to expand...
Click to collapse
tried every thing. flash froyo, flashed ginger. flashed Overcome's. flashed other roms like Boca or Miui.
but nothing can bring back the wi-fi even tried overcome's wi-fi fix and wpa-supplicant with proper permissions bla bla bla...
the tab was working fine before and was on overcome's last rom. but suddenly if wi-fi switched on, tab started giving constant re-starts.
do you think it's a hardware issue now? i flashed 2.3.6 stock on which it doesn't give restarts but wi-fi keeps scanning and switching off by itself.
3G works fine no issues at all.
please someone tell me if there is any thing that i'm not trying.

Yours sounds like hardware issue.
Sent from my GT-N7100 using xda app-developers app

Related

How to revert to stock kernel

I have a Bell SGS, GT-I9000m. I'm considering installing hardcore kernel only, i.e. no custom ROM. If later I want to revert to the stock kernel, how would I do that?
Thanks for your help.
Sent from my GT-I9000M using XDA App
I'm not quite sure if it is possible with the stock-kernel but if you can make a full backup (like with CWM) you could restore it later. But why do you want to get back to stock-kernel?
If the backup-possibility does not work you have to find the stock-kernel for downloading and flash it via Odin or you have to flash the whole stock-ROM with Odin.
Thanks for your answer. I can't make a Nandroid backup while I'm on stock (because I can't install CWM recovery because I'm on 3e stock recovery, not 2e)
I'm not sure why I would want to go back to stock... Maybe something goes terribly wrong? I guess I just wanted to know if it was possible.
Last question: when you say I would have to find the stock kernel, is that just Google, or are there sites/repositories out there for this sort of thing?
Sent from my GT-I9000M using XDA App
I should add, the site/repo question is for kernels and stock ROMs...
Thanks.
Sent from my GT-I9000M using XDA App
site1ca said:
I'm not sure why I would want to go back to stock... Maybe something goes terribly wrong?
Click to expand...
Click to collapse
Well, then just flash the whole stock-ROM and flash it (look at samnfirmware.com for firmwares).
site1ca said:
Last question: when you say I would have to find the stock kernel, is that just Google, or are there sites/repositories out there for this sort of thing?
Click to expand...
Click to collapse
Don't know if you'll find it anywhere cause nobody needs it.
Possible scenario
Alright, thanks for your help. I guess the one scenario that is bothering me is as follows:
1) Bell - FINALLY - releases their official Gingerbread update.
2) I've installed Hardcore kernel, which according to - http://forum.xda-developers.com/showthread.php?t=822756 - "works on all 2.2 and 2.2.1 ROMs".
3) Would I be able to install the Bell Gingerbread update with Hardcore kernel?
This is why I keep asking how I would revert from Hardcore because I obviously don't want to lock myself out of Bell updates forever.
It doesn't matter which kernel you are using when you are flashing with Odin. And Bell releases the updates later than Samsung, so you'd have the advantage of getting updates earlier with a 'free' firmware.
One solution to flash back the stock kernel is to extract the zImage (the kernel) from the stock rom and flash that with Odin or Heimdall.
But as far as I know having a custom kernel would not cause problems with installing a stock upgrade.
Done
I've installed Hardcore's kernel. Everything seems to be working fine, phone started up and picked up service.
I booted into recovery, enabled lagfix, turned on all of the recommended tweaks and then ran the Quadrant Standard. Things seem a bit faster, so I guess it's all good.
Next step, Darky's 10.1.
Thanks for your help, everyone.
One more question:
I did a Nandroid backup of everything (so data, dbdata, cache AND system). The restore option says "Be careful!". What's up with that? I mean, what's the caveat?
Thanks.
I've already made some NANDROID-backups, but never seen 'Be careful!'.
If the backup was succesful I wouldn't care about that.
*sigh*, I hate to keep adding questions on to this thread, but I must.
After installing the hardcore kernel and enabling tweaks and lagfix, I'm running into exactly this problem: http://forum.xda-developers.com/showthread.php?t=851970
My phone was extremely hot for a while, then I got a warning indicating that my internal phone storage was running low, etc.
Eventually, I found this file (/data/local/tsprsp) to be the culprit. I deleted it and rebooted and now my phone is fine. However, vibration just doesn't work at all!
Any ideas? Has anyone else run into this problem?
I was told that if you do a 'full' backup, in some cases restoration will fail with some error. But it depends on the version of the ROM you are using.
That is the reason why it is recommended to backup only data and if you want to restore, then first reflash your rom, then restore the data.
Thanks, zsori. That explains the "Be careful!".
Sent from my GT-I9000M using XDA App
After trying MIUI, a stock ROM will never touch my SGS again.
meresis said:
After trying MIUI, a stock ROM will never touch my SGS again.
Click to expand...
Click to collapse
you will have to flash back a stock rom via odin if anything wrong happen during the flashing of custom roms, although chances are low if you follow the instructions carefully.
good luck and have fun flashing custom roms!
Which Gingerbread?
So I'm continuing my quest to learn more about all of this custom ROM flashing stuff. And I wanted to get gingerbread on my phone... So I figured I'd just get an image from samfirmware.com and flash it. But then, I went here (because I was also interested in Darky's 10.1 so I was reading their guide): http://www.darkyrom.com/community/i...-darkyrom-gingerbread-jvh-noob-friendly.3080/
It says that flashing "Ficeto_JVH_I9000_Odin" will get me a stock Gingerbread. My question: what's the difference between flashing an image from samfirmware.com or flashing "Ficeto_JVH_I9000_Odin"? How do I know which to pick?
In all my browsing/reading, I realize that there are 3 "separate" parts: kernel, modem and then the "ROM". Ideally, I want to keep my modem as is... What does that correspond to in Odin? I've tried to find what "PIT", "PDA", "PHONE" and "CSC" represent in Odin, but I'm not sure I got it right. PIT = Kernel? PHONE = modem?
And finally, how do I know if a particular kernel is compatible with a particular ROM?
Sorry, I know there are lots of questions there. But please help clearing up a n00b's confusion. Thanks.
site1ca said:
So I'm continuing my quest to learn more about all of this custom ROM flashing stuff. And I wanted to get gingerbread on my phone... So I figured I'd just get an image from samfirmware.com and flash it. But then, I went here (because I was also interested in Darky's 10.1 so I was reading their guide): http://www.darkyrom.com/community/i...-darkyrom-gingerbread-jvh-noob-friendly.3080/
It says that flashing "Ficeto_JVH_I9000_Odin" will get me a stock Gingerbread. My question: what's the difference between flashing an image from samfirmware.com or flashing "Ficeto_JVH_I9000_Odin"? How do I know which to pick?
In all my browsing/reading, I realize that there are 3 "separate" parts: kernel, modem and then the "ROM". Ideally, I want to keep my modem as is... What does that correspond to in Odin? I've tried to find what "PIT", "PDA", "PHONE" and "CSC" represent in Odin, but I'm not sure I got it right. PIT = Kernel? PHONE = modem?
And finally, how do I know if a particular kernel is compatible with a particular ROM?
Sorry, I know there are lots of questions there. But please help clearing up a n00b's confusion. Thanks.
Click to expand...
Click to collapse
you got it wrong.
PIT is for mapping the partitioning of the phone. In most cases you should only use 512 pit file. and only use it when you want to wipe the phone.
the three parts is "pda" (which is the rom), "phone" (which is the modem), and "csc" (which is the carrier customization and apns)
the kernel is in the part of pda (the rom)
check the thread in xda of the kernel to see if its a gingerbread kernel or froyo kernel.
hope this clear things up
Yes, that helps. That's really good to know. So now, in Darky's guide to flashing Flash Ficeto_JVH_Odin, I see that only PIT and PDA are specified. This is reassuring, knowing that the modem and carrier stuff isn't touched.
Many thanks.
There are firmwares with three parts (Phone, PDA, CSC, including bootloader) and with only one part (PDA, no bootloader(?)). The one-part-FW is just an 'update', the one with three parts an 'upgrade'.

[Q] After flashing back stock ROM, the phone keeps blinking on the boot screen (HELP)

I am in desperate need of help you guys! I screwed up so hard that I don't even know where to begin...
THE SITUATION:
-Right now when I go to turn on my phone, it will only stay on the current SAMSUNG GALAXY S I9000 screen (the very first screen when booting your phone) and it keeps flashing in and out.
Before trying to use Odin to put back the original Kernal on my phone, it was just stuck as the SAMSUNG GALAXY S I9000 screen, still wouldn't start. <I followed this website step by step>
http://www.samsunggalaxysforum.com/...-to-a-stock-rom-after-installing-darky's-rom/
BEFORE ALL OF THIS EVER HAPPENED:
I finally rooted my phone and manage to download Clockworkmod recovery on my phone and then used it to flash Darky's 10.2 custom ROM. Everything turned out great except at the beginning of the boot, the screen turned all rainbow coloured, completely distorted, and it continued to do that. I then tried to go back to Recovery mode to do the Voodoo lagfix but I couldn't even get into the recovery mode anymore, it either wouldn't let me, or it did but the screen didn't go to it properly (more likely the first one). I read somewhere that if you reflash your phone again, it should make all the tweeks go away. So I tried that from the Darky's tools menu and ever since then, I've been stuck with the Boot Screen this whole time...
I already bricked my phone once, and that was before the Flashing Boot Screen.
I really need help you guys, I would at least like to have my phone back to the original basis, at least! Your help would be greatly appreciated!
THANK YOU
P.S. (i'm not that great at all this phone tweeking, but I've succeeded in doing it up until yesterday)
Can you get into download mode (vol down+home+power while putting the battery in)?
If you can, just reflash a stock or custom rom in odin (like a darky odin rom) as guided by whatever rom you choose.
If you cannot get into download mode then we should know that too.
Edit: oh it looks like you could (and hopefully still can). Try a different rom or reflash. Sometime things do go wrong but as long as you can get to the download screen you should be fine in the end.
G
gfacer said:
Can you get into download mode (vol down+home+power while putting the battery in)?
If you can, just reflash a stock or custom rom in odin (like a darky odin rom) as guided by whatever rom you choose.
If you cannot get into download mode then we should know that too.
Edit: oh it looks like you could (and hopefully still can). Try a different rom or reflash. Sometime things do go wrong but as long as you can get to the download screen you should be fine in the end.
G
Click to expand...
Click to collapse
Yes, I can get into download mode! (thank you for reading my post).
If it's not too much to ask, could you maybe find the ROM that would be good for me to flash, considering my situation?
I want to be sure that it's what the top tech guys would recommend
A link would be appreciated
thank you again!
I'd start with a Darky rom - lots of users - active forum and odin editions for your situation. I have to go but you'll find the link on the first page of the development section.
G
gfacer said:
I'd start with a Darky rom - lots of users - active forum and odin editions for your situation. I have to go but you'll find the link on the first page of the development section.
G
Click to expand...
Click to collapse
So in essence all I have to do is flash the Darky ROM V10.2 with Odin using the Download mode on my phone and it should be okay?
Wait one caveat. Was it a gingerbread rom or froyo? Use a Darky rom of the same type...
Then yes it should be ok if you follow their guide. Cross fingers.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
Wait one caveat. Was it a gingerbread rom or froyo? Use a Darky rom of the same type...
Then yes it should be ok if you follow their guide. Cross fingers.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
well...I did everything you said. The ROM is on there alright, it flashed and everything (And I know this because now when the boot screen STILL FLASHES, the darkcore & darky's rom logo are on it too).
THIS TIME AROUND:
The stock recovery seems to work...
any ideas??
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Alright I'll try and reflash the same one using a different version of odin the. I'll let you know what happened
gfacer said:
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
tried ezodin, flashed it, and i still get the exact same thing I've exhausted every single possibility there is!!!
I really need help on this, my warranty is not gonna do anything because i have the phone rooted..
If you flash a stock rom with pit the root is gone. It won't boot but they can't prove it was you either and I don't think it was you.
But see my other post on your other thread for one last thought.
G
Sent from my GT-I9000M using XDA Premium App
gfacer said:
If you flash a stock rom with pit the root is gone. It won't boot but they can't prove it was you either and I don't think it was you.
But see my other post on your other thread for one last thought.
G
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
okay that could be useful data potentially (let's hope it won't have to be).
If you didn't see my reply from the other thread, here it is:
Once I rooted my phone, I automatically went from Stock Froyo to Darky's 10.2 extreme edition. It worked and everything except for that color disfiguration and the clockworkmod recovery not working.
It's weird because after I flashed my first darky's rom, i checked the phone and it said that the firmware version was 2.3.X (I believe X may have been 4). So from what you're saying, I don't exactly think it has anything to do with the fact that I went straight from froyo stock to GB darky ROM.
So are you saying that I should flash darky's 9.3 for Froyo and THEN flash the latest version?
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Ok, so just to be 100% on this
-I should flash Darky's 9.2 froyo onto my phone,
-then I should flash regular GB onto my phone (Not sure about the bootloader part though, if you could clarify that)(Also where would I get JUST a stock GB ROM?)
-then I can flash a custom GB ROM?
gfacer said:
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
well i can safely say that flashing the 9.2 froyo rom was a fail. It's still doing the same old routine.
I just know that this problem can be fixed somehow without sending it in to bell or samsung or something.
roma17 said:
well i can safely say that flashing the 9.2 froyo rom was a fail. It's still doing the same old routine.
I just know that this problem can be fixed somehow without sending it in to bell or samsung or something.
Click to expand...
Click to collapse
I think you are right but other than trying again and again, which I've done before -though now I know why I had too - I am out of suggestions. Good Luck and if I have a brainwave I'll let you know.
Sent from my GT-I9000M using XDA Premium App
OK a few last brainwaves:
1) Try a fully complete stock rom with cache.rfs, dbdata.rfs, factoryfs.rfs, modem.bin, param.lfs, zImage, and sbl.bin (this was from JL2 rom for Bell - not sure if they all have the sbl.bin) and pit.
The key is to make sure it is complete. Try downloading the same rom from 2 different sources just to be sure its not a corrupt download (going overboard I know).
2) Can you get into recovery? Try to format partitions (not system) under advanced features (I think - I only have 3e right now as I am trying to diagnose other issues).
3) If you have a froyo rom on at one point, try to put a steam recovery kernel on. Its not really being developed anymore but I think that if you put a CWM packaged rom on to the external SD you could flash from there or at least move it to the internal and then flash it. Worth a shot. Or you might be able to transfer one in regular CWM recovery - can't recall as I have not had to try for about 8 months.
4) If you really want to try something completely different, and I am not sure I've got the balls if it was me but if you can get a file to flash from CWM or steam that you can get on from the external SD, you might try CM7. It uses a completely different file system so you'd have to go back to froyo via odin only (as a samsung based rom will not play well when flashed on top of the cm7 file system).
And calling it a day at this one...
gfacer said:
OK a few last brainwaves:
1) Try a fully complete stock rom with cache.rfs, dbdata.rfs, factoryfs.rfs, modem.bin, param.lfs, zImage, and sbl.bin (this was from JL2 rom for Bell - not sure if they all have the sbl.bin) and pit.
The key is to make sure it is complete. Try downloading the same rom from 2 different sources just to be sure its not a corrupt download (going overboard I know).
2) Can you get into recovery? Try to format partitions (not system) under advanced features (I think - I only have 3e right now as I am trying to diagnose other issues).
3) If you have a froyo rom on at one point, try to put a steam recovery kernel on. Its not really being developed anymore but I think that if you put a CWM packaged rom on to the external SD you could flash from there or at least move it to the internal and then flash it. Worth a shot. Or you might be able to transfer one in regular CWM recovery - can't recall as I have not had to try for about 8 months.
4) If you really want to try something completely different, and I am not sure I've got the balls if it was me but if you can get a file to flash from CWM or steam that you can get on from the external SD, you might try CM7. It uses a completely different file system so you'd have to go back to froyo via odin only (as a samsung based rom will not play well when flashed on top of the cm7 file system).
And calling it a day at this one...
Click to expand...
Click to collapse
Okay, basically at this point, I just want my phone to work I've tried what you said. I remember that before rooting my phone initially I was running Froyo 2.2.1. So I found the ROM for that ( http://www.samfirmware.com/WEBPROTECT-i9000.htm ) Just like you said. I downloaded from the *Provider Samsung Galaxy S i9000 heading and picked the I9000BOJS5 ## from February 2011 because I think somewhere around there I updated my phone to Froyo. Flashed it, did everything, still no luck.
I've had a recent hunch though. When the bootscreen boots up, it keeps saying i9000 only, when before it used to say i9000M at least for a little bit (yes my phone is i9000m). Is there a stock froyo rom that's specifically designed to go with the i9000m model? Or are they just all the same?
Never give up
-Thank you so much

[Q] DarkyRom 10.2 RE Issues/Question

Hey Guys,
I have a couple of questions in regards to going back to stock from DarkyROM 10.2.
After using 10.2 for about a month now, I have noticed that while the rom is fast, There are quite alot of glitches in my day to day operations. My 3D HD games no longer work smoothly (as they did in 2.3.3 with CWM), the phone will randomly freeze up when using the browser/gallery/calender etc. After multiple re-flashes I am coming to the conclusion that to get back to my original performance I may need to flash a stock JVQ and then mayby just us CF ROOT or something of the like to get CWM access.
My question is, what preparations need to be done before preforming this flash. Also, can the stock files be flashed with ODIN? Also, if anyone has any input on why DARKYROM 10.2 seems to have these issues, please feel free to let me know. Any help will be greatly appreciated, thanks in advance!!
Phone Specs:
Samsung Galaxy Vibrant (i9000m)
DarkyRom 10.2 RE -w- KC1 Modem
Only Mod preformed after flashing RE was updating the SMS application to the SGS2 App to restore the chat bubble colors. The issues were present before this update. Did the update through DarkyRom Tool.
If you guys need any more information, just let me know..
Anyone??????
Alright, I'll take this one if no one else will. I too have the i9000m, and have learned all I can about keeping it alive and well. Going back to stock is easy. Go to general and look for the stock firmware thread. You will get instructions there on how to flash with odin. I've never used darky before but I did use CM7 and flashed back no problem. You could also look for Ramad's prerooted roms. I'm running one right now, UGKG3. Works great as I couldn't root it myself.
Sent from my GT-I9000M using XDA App
Getinaf said:
Alright, I'll take this one if no one else will. I too have the i9000m, and have learned all I can about keeping it alive and well. Going back to stock is easy. Go to general and look for the stock firmware thread. You will get instructions there on how to flash with odin. I've never used darky before but I did use CM7 and flashed back no problem. You could also look for Ramad's prerooted roms. I'm running one right now, UGKG3. Works great as I couldn't root it myself.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Hey Dude, Thanks alot for your response! One more question before making the switch....Should the voodoo lag fix that comes with Darky 10.2 be disabled before flashing with Odin back to stock?
If you want to go back to stock ROM. Before flashing disable the lagfix (for safe). You can download the firmware from www.samfirmware.com. and its an odin base installation.
Post your problem in www.darkyrom.com some expert will help you...
Hey guys.
I have flashed stock ROM (2.3.4) via Odin and worked absolutely fine. Didn't need to fiddle with the lagfix or anything. Simply popped phone into DOWNLOAD mode and flashed (with re-partition/wipe and backing up "stuff" beforehand).
The lagfix menu I think, is in the RECOVERY mode in the extended power options menu. I think thats the CWM with the DarkyROM maybe? Either way, you can enable/disable the lagfix in that menu.
Hope this helps!
Akhtar

[Q] Keep getting "Unregistered device" while updating to Gingerbread

Okay, so I did a factory reset, no custom roms, only had official Froyo and Speedmod kernel. I also unrooted. Why do I keep getting "Unregistered device" from Kies Mini? Maybe it's because my Baseband version on "About Phone" shows "I9000UGJK4"? Or is it maybe that their servers are being bombarded by Cappy users updating their phones? Any help is greatly appreciated.
If you have flashed a custom ROM before, it won't work. Just wait on a Odin/Heimdall one click!
Sent from my SGH-I897 using xda premium
aicirt17 said:
Okay, so I did a factory reset, no custom roms, only had official Froyo and Speedmod kernel. I also unrooted. Why do I keep getting "Unregistered device" from Kies Mini? Maybe it's because my Baseband version on "About Phone" shows "I9000UGJK4"? Or is it maybe that their servers are being bombarded by Cappy users updating their phones? Any help is greatly appreciated.
Click to expand...
Click to collapse
This worked for me, I tried this morning, I had the same issue while on CM9 ICS.
As mentioned flashing any rom your device's I'd might change. I've never had my imei change but read enough ppl to know it happens.
Sent from my SGH-I897 using Tapatalk
I don't know if this matters, but I've never installed a custom ROM, only a custom modem and kernel. Would that change the IMEI?
Have you messed with unlocking it?
Sent from my ICS powered i897
I'm pretty sure kies mini will detect kernel changes. I had stock froyo with a flashed kernel and it wouldn't let me update. I flashed everything back to stock, but was still rooted, and it still wouldn't let me update. I ended up doing a full flash back to stock kb2 and it finally let me upgrade.
I wonder if I flashed the stock kernel and unrooted if it would have worked. At the time I was too lazy to browse for everything and already had the heimdall package downloaded.
Sent from my SAMSUNG-SGH-I897 using XDA App
If your "About Phone" shows anything other than SGH_I897 kies mini will not recognize your device. I was running andromeda , wouldn't see it so I went back to stock, oneclicked jf6. After that kies immediatley recognized it. I probably didn't have to go back to jf6 but, I had nothing better to do for that next hour. If you do go back to jf6 you will have to kies mini twice to get GB, first time it will install froyo, when it's done close kies, unplug re-open kies, re-plug your phone kies will show update again, click and sit back and wait for it to finish. ...you now have GB.
Thank you all for your help. I finally got it. I ended up RE-flashing back to stock using this method: http://forum.xda-developers.com/showthread.php?t=1300843
Turns out that I did in fact have a custom modem and custom kernel, and when I flashed back to stock the first time (I used Clockwork Recovery), it didn't put back the original modem and kernel, thus making Kies Mini not recognizing my phone. So, after RE-flashing the ORIGINAL OFFICIAL Froy update using the above link, everything went smooth fronm there. Hope this helps somebody.

[Q] Downgrading Android Versions -- Verification

I have a SGS Captivate I have been using as a sports tracking device and as a music player for the past year. I now have a few questions before changing ROMs on it.
History >> Two years ago I soft bricked it while on CM9. Not being able to resurrect it at the time I purchased an SGS3 and set the Captivate aside for a while. I resurrected it using a KK4 Heimdall One-Click and immediately flashed it to CM10.1. Having been on CM10.1 for a number of months I upgraded the device to CM10.2. After doing so I noticed the bootloader was listed as unknown and the baseband was KG3. I have checked this in terminal emulator and using a "Samsung Info" app from the PlayStore. I've verified the KG3 modem is for the i9000. I checked in the updater-script of the CM10.2 I downloaded and installed and observed it being coded for captivate and for i897. So, I am not fearful that I downloaded the incorrect ROM.
I have known of the above discrepencies for months and have not been terribly concerned. I do not know if they could have something to do with the fact that I have not had a sim card in the phone since before I resurrected it. Even though I do not currently plan to use it as a phone I intend to have it in a condition to do so if needed. That, and I was interested in flashing a ROM I have seen recommended several times by @BWolf56, Gamerzrom Legend 4.0. The questions I have stem from the fact that I will be going from a ROM based on Android 4.3 to one based on 4.2.2.
To correct the bootloader and modem I intend to flash, again the KK4 stock ROM (Gingerbread). This will be with the Heimdall One-Click from the forums, Odin is not an option - I run Linux. Once installed I will verify bootloader and modem. Based on the Gamerzrom blog I will then install CM10.1 before installing their ROM. (This could be avoided if I were not going back to stock.) At each step I will wipe and format as indicated, I will probably wipe and format to excess.
[Q1] Is this the best approach to get to having the 4.2.2 based Gamerzrom installed from where I am?
[Q2] Should I not do this at all, the donwgrade, even to stock, could seriously damage my phone?
[Q1] Is there anyone who thinks I could safely shortcut the above by simply flashing the KK4 bootloader and modem?
(If I can still find a download on the forums.) This would eliminate going back to stock GB and then to CM10.1.
[Q2] Is there no reason to worry about the bootloader and modem? The discrepency is simply an artifact based on there being no sim card in the phone and I would be best off advancing directly to flashing Gamerzrom from CM10.2.1.
dawgdoc said:
I have a SGS Captivate I have been using as a sports tracking device and as a music player for the past year. I now have a few questions before changing ROMs on it.
History >> Two years ago I soft bricked it while on CM9. Not being able to resurrect it at the time I purchased an SGS3 and set the Captivate aside for a while. I resurrected it using a KK4 Heimdall One-Click and immediately flashed it to CM10.1. Having been on CM10.1 for a number of months I upgraded the device to CM10.2. After doing so I noticed the bootloader was listed as unknown and the baseband was KG3. I have checked this in terminal emulator and using a "Samsung Info" app from the PlayStore. I've verified the KG3 modem is for the i9000. I checked in the updater-script of the CM10.2 I downloaded and installed and observed it being coded for captivate and for i897. So, I am not fearful that I downloaded the incorrect ROM.
I have known of the above discrepencies for months and have not been terribly concerned. I do not know if they could have something to do with the fact that I have not had a sim card in the phone since before I resurrected it. Even though I do not currently plan to use it as a phone I intend to have it in a condition to do so if needed. That, and I was interested in flashing a ROM I have seen recommended several times by BWolf56, Gamerzrom Legend 4.0. The questions I have stem from the fact that I will be going from a ROM based on Android 4.3 to one based on 4.2.2.
To correct the bootloader and modem I intend to flash, again the KK4 stock ROM (Gingerbread). This will be with the Heimdall One-Click from the forums, Odin is not an option - I run Linux. Once installed I will verify bootloader and modem. Based on the Gamerzrom blog I will then install CM10.1 before installing their ROM. (This could be avoided if I were not going back to stock.) At each step I will wipe and format as indicated, I will probably wipe and format to excess.
[Q1] Is this the best approach to get to having the 4.2.2 based Gamerzrom installed from where I am?
[Q2] Should I not do this at all, the donwgrade, even to stock, could seriously damage my phone?
[Q1] Is there anyone who thinks I could safely shortcut the above by simply flashing the KK4 bootloader and modem?
(If I can still find a download on the forums.) This would eliminate going back to stock GB and then to CM10.1.
[Q2] Is there no reason to worry about the bootloader and modem? The discrepency is simply an artifact based on there being no sim card in the phone and I would be best off advancing directly to flashing Gamerzrom from CM10.2.1.
Click to expand...
Click to collapse
1: don't need to flash cm first but you do have to flash the ROM twice to repartition it then flash the gapps.
2: flashing stock should recover/fix your unknown bootloader issue but unless your imei is unknown, you shouldn't have any problem using as a phone if needed.
I do suggest flashing KK4 before going to GamerzROM to avoid any issues.
BWolf56 said:
1: don't need to flag cm first but you do have to flash the ROM twice to repartition it then flash the gapps.
2: flagging stock should recover/fix your unknown bootloader issue but unless your imei is unknown, you shouldn't have any problem using as a phone if needed.
I do suggest flashing KK4 before going to GamerzROM to avoid any issues.
Click to expand...
Click to collapse
The imei is still present at least according to "Samsung Info" and using getprop in terminal emulator.
Okay, flash stock KK4 rom, no need to flash CM10.1, but flash Gamerzrom 4.0 twice.
I was getting CM10.1 from Gamerzrom 3.0 installation instructions for those coming from GB. I was thinking going back to KK4 would reset the partition scheme to GB. I guess the double flash of GLE4.0 takes care of the repartitioning back to JB layout.
Thank you.
dawgdoc said:
The imei is still present at least according to "Samsung Info" and using getprop in terminal emulator.
Okay, flash stock KK4 rom, no need to flash CM10.1, but flash Gamerzrom 4.0 twice.
I was getting CM10.1 from Gamerzrom 3.0 installation instructions for those coming from GB. I was thinking going back to KK4 would reset the partition scheme to GB. I guess the double flash of GLE4.0 takes care of the repartitioning back to JB layout.
Thank you.
Click to expand...
Click to collapse
That's exactly it, whether you flash cm or gamerz twice, it will do the same thing and repartition. Just don't forget the gapps after.
BWolf56 said:
That's exactly it, whether you flash cm or gamerz twice, it will do the same thing and repartition. Just don't forget the gapps after.
Click to expand...
Click to collapse
Thanks, I wouldn't dare forget GAPPS.
In fact, I have already downloaded both GAPPS and the ROM -- that was about 6 hours ago. I probably will not flash until Monday. :{​
You know, I am a bit surprised at how regularly posts are made to the Captivate forum. More often than I would have expected.
dawgdoc said:
Thanks, I wouldn't dare forget GAPPS.
In fact, I have already downloaded both GAPPS and the ROM -- that was about 6 hours ago. I probably will not flash until Monday. :{​
You know, I am a bit surprised at how regularly posts are made to the Captivate forum. More often than I would have expected.
Click to expand...
Click to collapse
While it's an old device, it's really great and some of us keep supporting it
Mixed Results with increased understanding
Well I went through the process I outlined above, or tried to do so.
I downloaded a One-Click stock rom, android 2.3.5, from this thread. It is actually the same leaked stock rom I used two years ago. I flashed it twice per instructions to get the bootloader, doing so to correct my unknown bootloader issue. After this was installed I used a "Samsung Info" app to verify bootloader and modem. The modem was KK4, yet the bootloader was still unknown. I repeated the process twice more with the same results.
Rather than download a different stock GB rom I proceeded with the remainder of my plan. I flashed Gamerzrom Legend Edition 4.0 from here on the recommendation of @BWolf56. I wiped, formatted, and then flashed twice as he recommended. The ROM didn't boot, but not to worry I repeated the process. Still no boot. I next went ahead and flashed CM 10.1.3 and booted into it. The bootloader was still unknown and the modem was now listed as KG3, an i9000 modem, again. My guess is CM did this since this how it was listed before I went back to stock. I now went back to Gamerzrom and successfully flashed it. (Still showing bootloader unknown and modem as KG3.)
I am setting up the phone this evening. So far in addition to installing ROMs and adjusting settings I have verified wifi works. Later tonight I will be testing the GPS and bluetooth. With the "wrong" modem my results could be decremated, but I don't expect them to be. When I was previously on CM 10.1.3 and 10.2.1 and on the KG3 modem all worked. Bluetooth, wifi, and GPS worked that is, I didn't try calls because I wasn't using it as a phone and didn't have an appropriate sized sim to borrow.
If I need this device as a phone I will first try it as is with bootloader unknown and modem as KG3. If that doesn't work I will flash an i897 modem, probably the KK1 modem, and see how that works. If that doesn't do the trick I will try an earlier GB stock One-Click rom, either KK1 or KJ3.
dawgdoc said:
Well I went through the process I outlined above, or tried to do so.
I downloaded a One-Click stock rom, android 2.3.5, from this thread. It is actually the same leaked stock rom I used two years ago. I flashed it twice per instructions to get the bootloader, doing so to correct my unknown bootloader issue. After this was installed I used a "Samsung Info" app to verify bootloader and modem. The modem was KK4, yet the bootloader was still unknown. I repeated the process twice more with the same results.
Rather than download a different stock GB rom I proceeded with the remainder of my plan. I flashed Gamerzrom Legend Edition 4.0 from here on the recommendation of @BWolf56. I wiped, formatted, and then flashed twice as he recommended. The ROM didn't boot, but not to worry I repeated the process. Still no boot. I next went ahead and flashed CM 10.1.3 and booted into it. The bootloader was still unknown and the modem was now listed as KG3, an i9000 modem, again. My guess is CM did this since this how it was listed before I went back to stock. I now went back to Gamerzrom and successfully flashed it. (Still showing bootloader unknown and modem as KG3.)
I am setting up the phone this evening. So far in addition to installing ROMs and adjusting settings I have verified wifi works. Later tonight I will be testing the GPS and bluetooth. With the "wrong" modem my results could be decremated, but I don't expect them to be. When I was previously on CM 10.1.3 and 10.2.1 and on the KG3 modem all worked. Bluetooth, wifi, and GPS worked that is, I didn't try calls because I wasn't using it as a phone and didn't have an appropriate sized sim to borrow.
If I need this device as a phone I will first try it as is with bootloader unknown and modem as KG3. If that doesn't work I will flash an i897 modem, probably the KK1 modem, and see how that works. If that doesn't do the trick I will try an earlier GB stock One-Click rom, either KK1 or KJ3.
Click to expand...
Click to collapse
Modem doesn't affect BT so it should be fine. It's odd that Gamerz didn't boot but glad it turned out fine. Also, having a different modem won't change anything about the bootloaders but that being said, I highly doubt it would stop you from using it as a phone.
You're seeing I9000 modems cause the ROMs were often built off the international version of the Captivate. Both I897 and I9000 work well on the device and you can flash whichever one gives you the best results in terms of networking (which you don't seem to be using anyway).
BWolf56 said:
Modem doesn't affect BT so it should be fine. It's odd that Gamerz didn't boot but glad it turned out fine. Also, having a different modem won't change anything about the bootloaders but that being said, I highly doubt it would stop you from using it as a phone.
You're seeing I9000 modems cause the ROMs were often built off the international version of the Captivate. Both I897 and I9000 work well on the device and you can flash whichever one gives you the best results in terms of networking (which you don't seem to be using anyway).
Click to expand...
Click to collapse
True, the kernel controls BT and wifi. I'm not sure why I was mentioning BT w/ modem.
I think I didn't organize my thoughts too well in that last paragraph. Closer to what I meant was that if needed as a phone I would try it as is >> unknown bootloader and KG3 modem. If I had any troubles with it working I would try a different modem. This is where I was erroneously thinking that the i9000 modem may turn be a problem. If that didn't fix it then I would go with another stock ROM to give another go at fixing the bootloader issue. I actually think/hope it would work as it currently is. The phone has repeatedly booted, so at least the sbl (?) secondary boot loader partition is intact.
BTW, the GPS seems to be working well, even though I have a 10/08 build device. Bluetooth, on the other hand, is not pairing with my Linux laptop nor a cheap bluetooth speaker. The same held true when I was on CM 10.2.1 with the cappy. Both, the laptop and speaker, pair with my SGS3.
Could the reason the Gamerzrom didn't flash straight off is that I was coming from a stock TouchWiz 2.3.5 rom instead of from any JB rom? Thank you for helping.
dawgdoc said:
True, the kernel controls BT and wifi. I'm not sure why I was mentioning BT w/ modem.
I think I didn't organize my thoughts too well in that last paragraph. Closer to what I meant was that if needed as a phone I would try it as is >> unknown bootloader and KG3 modem. If I had any troubles with it working I would try a different modem. This is where I was erroneously thinking that the i9000 modem may turn be a problem. If that didn't fix it then I would go with another stock ROM to give another go at fixing the bootloader issue. I actually think/hope it would work as it currently is. The phone has repeatedly booted, so at least the sbl (?) secondary boot loader partition is intact.
BTW, the GPS seems to be working well, even though I have a 10/08 build device. Bluetooth, on the other hand, is not pairing with my Linux laptop nor a cheap bluetooth speaker. The same held true when I was on CM 10.2.1 with the cappy. Both, the laptop and speaker, pair with my SGS3.
Could the reason the Gamerzrom didn't flash straight off is that I was coming from a stock TouchWiz 2.3.5 rom instead of from any JB rom? Thank you for helping.
Click to expand...
Click to collapse
BT not working can be cause it wasn't updated in so long or kernel issue. Or could simply be that it doesn't work with your specific devices.
I flashed mine off stock KK4 (same one you flashed), tried to boot without flashing it twice, which of course didn't work but then went back in recovery, re-flashed and it booted just fine.

Categories

Resources